Date: Fri, 7 Jan 2000 15:07:33 +0100 (CET) From: Soren Schmidt <sos@freebsd.dk> To: darius@dons.net.au (Daniel 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: <200001071407.PAA07994@freebsd.dk> In-Reply-To: <3875EBA2.51CCF3B8@dons.net.au> from "Daniel O'Connor" at "Jan 8, 2000 00:05:30 am"
next in thread | previous in thread | raw e-mail | index | archive | help
It seems Daniel O'Connor wrote: > > > Soren Schmidt wrote: > > Hmm, thats not foolproof either. What would you set it to ? > > The default? :) > (Power on default..) Hmm, could do that, but chances are it will be just as bad as the one burcd left it in... > Hmm.. basically I was just wondering if you could end up in a state > where you nuked a cdburning with -9 and consequently couldn't mount a CD. The drive will most likely be so confused that you cant use it for anything without a reboot anyway, at least its been that 9 out of 10 times I've broken off the process... > > 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. > > Well, there are reasons for stopping a burn even if you are going to > screw the disk up.. Sure, but the odds for using the drive afterwards are minimal, sadly... -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?200001071407.PAA07994>