From owner-freebsd-current Thu Jan 6 9:29:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 7450714C80 for ; Thu, 6 Jan 2000 09:28:38 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id SAA01007; Thu, 6 Jan 2000 18:29:05 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001061729.SAA01007@info.iet.unipi.it> Subject: Re: wormcontrol replacement coming! In-Reply-To: <200001061723.SAA11762@freebsd.dk> from Soren Schmidt at "Jan 6, 2000 06:23:54 pm" To: Soren Schmidt Date: Thu, 6 Jan 2000 18:29:04 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I've just done a replacement for wormcontrol that allows burning CDR/CDRW > > > with just one command. Its simpleminded but it works. btw for the records -- on 2.2.x i noticed i needed some wait between the transfer of data to CDR, and the "fixate" command (in other words, the fixation would often immediately fail if done within the same wormcontrol instance in charge of the data transfer.) I got lazy and instead of investigating the problem i realised that issuing the "wormcontrol fixate data" manually after the previous one was done did fix things, so i have no idea if it was related with my port of the worm support to 2.2.x, with the possible absence of closing and reopening the device, or with just the delay between the commands. Any idea ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message