🚀 go-pugleaf

Shouldn't that line read like this? :

> >/dev/hdc        /cdrom       iso9660     defaults,noauto,ro   1   1

I have never used a partition identifier (i.e. the '4' on '/dev/hdc4') for
mounting a CD-ROM.  I think the mount version is a bit of a red herring -
it's the kernel code that accesses the CD-ROM on /dev/hdcX that's
important.

-- 
PDG
---------
Spam to /dev/null.  Real mail to me by taking the "no_spam_please." out of
my address.

Michael Talbot-Wilson <talmg@atom.forensic.sa.gov.au> wrote in article
<slrn67qna2.rdb.talmg@atom.forensic.sa.gov.au>...
> In article <87yb2khpum.fsf@mars.mds.rmit.edu.au>, Marcelo Cantos wrote:
> >Help!!
> >
> >I used to be able to read my CD-ROM drive.  Suddenly (for no reason I
> >can fathom), I am getting the following output:
> >
> >----------------------------------------------------------------
> ># cat /etc/fstab
> >/dev/hda4        swap         swap        defaults          1   1
> >/dev/hda3        /            ext2        defaults          1   1
> >/dev/hda1        /dosc        vfat        defaults          1   1
> >/dev/hda5        /dosd        vfat        defaults          1   1
> >/dev/hdb4        /zip         vfat        defaults,noauto   1   1
> >/dev/hdc1        /cdrom       iso9660     defaults,noauto,ro   1   1
> >none             /proc        proc        defaults          1   1
> ># mount /cdrom
> >mount: wrong fs type, bad option, bad superblock on /dev/hdc1,
> >       or too many mounted file systems
> >       (aren't you trying to mount an extended partition,
> >       instead of some logical partition inside?)
> >
> >#
> >----------------------------------------------------------------
> >
> >I have kernel 2.0.31 (it also fails on 2.0.30), and yes I _do_ a have
> 
> Suddenly, for no reason you can fathom, but it has never worked on
> 2.0.30 and 2.0.31?  What version did it work on?
> 
> >CD in the drive.  Also, the ZIP drive (/dev/hdb4) mounts fine before
> >or after I attempt to mount the CD-ROM.
> 
> What version of mount?
>