On Sat, 5 Oct 2002, Steve Kargl wrote: > > In message <[EMAIL PROTECTED]>, 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
