From owner-freebsd-questions Tue Mar 13 6:36:59 2001 Delivered-To: freebsd-questions@freebsd.org Received: from grumpy.dyndns.org (user-24-214-76-236.knology.net [24.214.76.236]) by hub.freebsd.org (Postfix) with ESMTP id DF95137B72D for ; Tue, 13 Mar 2001 06:36:56 -0800 (PST) (envelope-from dkelly@grumpy.dyndns.org) Received: (from dkelly@localhost) by grumpy.dyndns.org (8.11.2/8.11.2) id f2DEaqw10828; Tue, 13 Mar 2001 08:36:52 -0600 (CST) (envelope-from dkelly) Date: Tue, 13 Mar 2001 08:36:52 -0600 From: David Kelly To: Wayne Pascoe Cc: Byron Schlemmer , freebsd-questions@freebsd.org Subject: Re: CD Writing Woes Message-ID: <20010313083652.A10800@grumpy.dyndns.org> References: <200103130159.f2D1xWe06912@grumpy.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from wayne@penguinpowered.org.uk on Tue, Mar 13, 2001 at 08:33:39AM +0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 13, 2001 at 08:33:39AM +0000, Wayne Pascoe wrote: > David Kelly writes: > > > What do you think the -m option does? Its not in my burncd manpage. > > Suspect burncd has attempted to read a file named -m, and maybe > > succeded and wrote it at the start of your cd-r. > > >From the burncd manpage > -m close disk in multisession mode (otherwise disk is closed > as singlesession). OK, I see that was added in the past month. > one thing that we forgot to mention, is that if we use burncd with the > fixate option, at the end of the write (both when using -t to test and > when doing a real write), we get an IO error (something about > IOCLOSECD). If we don't use fixate, we don't get the error, but then > the CD won't mount anywhere either. While I think what you describe should work I think the -m and fixate are contradicting each other for a single pass burn. Once you fixate you can not append to the media yet the -m is preparing for a future append eventually followed by fixate. > Attempting to mount a cd after writing it has caused page faults and > subsequent reboots on all three attempts now. Every now and then when somebody pipes up, "I want a project!" I suggest a userland super error checked removable media daemon. One that won't break on broken media. One that could easily control who and what was mounted. Either replace the existing iso9660 code with something slow and error checked for saftey, or override it in the external daemon. Something like mediad on SGI Irix. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message