Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Oct 2002 15:01:06 +1000 (EST)
From:      Bruce Evans <bde@zeta.org.au>
To:        Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc:        Poul-Henning Kamp <phk@critter.freebsd.dk>, <freebsd-current@FreeBSD.ORG>
Subject:   Re: devfs oddity?
Message-ID:  <20021006144225.G15291-100000@gamplex.bde.org>
In-Reply-To: <20021005223947.GA17512@troutmask.apl.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 5 Oct 2002, Steve Kargl wrote:

> > In message <20021005221611.GA17396@troutmask.apl.washington.edu>, Steve Kargl w
> > rites:
> > >root[208] cdcontrol play
> > >cdcontrol: no CD device name specified, defaulting to /dev/cd0c
> > >cdcontrol: /dev/cd0cc: No such file or directory
> > >
> > >Why is an extra "c" appended to cd0c?

The first "c" is part of the standard name for the whole of a (labelled)
disk device.  phk is busily breaking this standard.  The second "c" is
because cdcontrol tries tacking on a "c" in case the user forgot it.
Here the user didn't specify a device name, so the default of "cd0c"
was tried, and since that was broken recently, it doesn't work, and
a "c" is tacked on to it.  The user can work around this easily enough
by specifying the device, except in the !DEVFS case when the device
doesn't exist.

> Okay.  This just started with a kernel built from
> sources of Friday vintage (without GEOM).  My previous
> kernel from Sun Sep 8 08:53:47 PDT 2002 does not have
> this problem.  Building and running a kernel in the
> the time between and Sep 8 and new has been an adventure.

This is because rev.1.62 of scsi_cd.c axed labelling support.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




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