Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Mar 2001 08:36:52 -0600
From:      David Kelly <dkelly@hiwaay.net>
To:        Wayne Pascoe <wayne@penguinpowered.org.uk>
Cc:        Byron Schlemmer <byron.schlemmer@realtime.co.uk>, freebsd-questions@freebsd.org
Subject:   Re: CD Writing Woes
Message-ID:  <20010313083652.A10800@grumpy.dyndns.org>
In-Reply-To: <m1itlef4po.fsf@zaphod.realtime.co.uk>; from wayne@penguinpowered.org.uk on Tue, Mar 13, 2001 at 08:33:39AM %2B0000
References:  <200103130159.f2D1xWe06912@grumpy.dyndns.org> <m1itlef4po.fsf@zaphod.realtime.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 13, 2001 at 08:33:39AM +0000, Wayne Pascoe wrote:
> David Kelly <dkelly@grumpy.dyndns.org> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010313083652.A10800>