My hardy installation, with a dvd writer. [EMAIL PROTECTED]:~$ ls -l /dev/cd* lrwxrwxrwx 1 root root 3 2008-05-21 17:14 /dev/cdrom -> hda lrwxrwxrwx 1 root root 3 2008-05-21 17:14 /dev/cdrw -> hda
This was an upgrade from gutsy, though. Steve On Fri, 23 May 2008 13:57:52 +1200 Roger Searle <[EMAIL PROTECTED]> wrote: > Yes, I have trusted (and installed) all updates offered via the adept > notifier. I am almost certain [1] that this has been broken since day 1 > - certainly within a very small number of days. > > I definitely know I had a /dev/cdrom under gutsy, I have no idea why I > now do not. udev is now on my list to read up on. > > [1] I must admit to a degree of that early onset memory thing what ever > it is called... > > > Christopher Sawtell wrote: > > My updated instance of the Heron produces the /dev/dcrom link. Have > > you done any updates since installation? > > > > On Fri, May 23, 2008 at 8:57 AM, Nick Rout <[EMAIL PROTECTED]> wrote: > > > >> Read up on writing udev rules. Or put it in a startup script. Or look > >> for a config file for eject. > >> > >> On Fri, May 23, 2008 at 8:56 AM, Roger Searle <[EMAIL PROTECTED]> wrote: > >> > >>> Hi, I make good use of the eject command which up to gutsy would work on > >>> it's own without specifying a device, however on upgrading to hardy fails: > >>> > >>> eject: unable to find or open device for: `cdrom' > >>> > >>> seemingly because there is no /dev/cdrom file in hardy. There is a > >>> cdrom1, > >>> cdrw1, dvd1, dvdrw1 etc, which are links to scd0. I can create the cdrom > >>> link easily enough and then eject works fine. The problem is that the > >>> link > >>> will not survive a reboot and I am wondering if anyone could indicate why, > >>> or how I might resolve this. > >>> > >>> Cheers, > >>> Roger > >>> > >>> > > > > > > > >
pgpOz9foBjFDI.pgp
Description: PGP signature
