Date: Fri, 7 Jan 2000 14:12:04 +0100 (CET) From: Soren Schmidt <sos@freebsd.dk> To: darius@dons.net.au (Daniel J. O'Connor) Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, sos@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/burncd burncd.c Message-ID: <200001071312.OAA94748@freebsd.dk> In-Reply-To: <XFMail.000107225320.darius@dons.net.au> from "Daniel J. O'Connor" at "Jan 7, 2000 10:53:20 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
It seems Daniel J. O'Connor wrote: > > On 07-Jan-00 Soren Schmidt wrote: > > Good point, yes it will leave the blocksize wrong (also in the old version), > > and can leave your burner in a wierd state. > > I'll do some signal catching to prevent this... > > Shouldn't that be done in the driver? > > ie on close() or something? Hmm, thats not foolproof either. What would you set it to ? The problem is that I need to get the driver to be able to read all formats (ie different blocksizes) for some of the things I have in the pipeline (reading of all CD formats, packet, DVD-RAM), but I need to tell the driver the size up front, or the read will fail. So the caller will have to set the blocksize to what it wants, and if close resets it, it would then have to do it on each open, which is not desireable on mounts fx. Another thing is that it is very unwise to kill the burning process, it is garantied to leave the medium useless, that was why I'd do signal catching to prevent that. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001071312.OAA94748>