I've seen that problem when using a CDRW (and I think the session wasn't
closed)
The problem was that the system NEEDED to mount it ro and should have
detected that... Perhaps specifying 'ro' on the fstab line would work
for ya...
On 04 Sep 2001 11:23:21 -0500, Tom Brinkman wrote:
> On Tuesday 04 September 2001 09:46 am, David Durham escribi�:
> > Hi... I installed the newest kernel to day, 2.4.8-18, because I
> > wanted to try supermount.
> > Well, it installed fine and I did a `supermount -i enable` (as root)
> > and rebooted.
> > I stuck a data cd in and typed `ls /mnt/cdrom` (as root) and didn't
> > see anything... Then I did a `modprobe supermount` because it wasn't
> > listed in `lsmod` (what, again, do I need to do to make it always
> > load supermount?). Still nothing.
> > Is the format for /etc/fstab still to same?
> > My line for /mnt/cdrom:
> > /mnt/cdrom /mnt/cdrom supermount
> > fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0 0
> > I can manually mount the cdrom, `mount /mnt/cdrom` and it works fine
> > Any ideas? I'm just hoping I didn't miss a thread about it...
>
> I did just the same as you, but with the addition of trimming my
> fstab line from fs=iso9660,dev=/dev/cdrom,ro,nosuid,noauto,nodev,exec 0
> 0, to just fs=iso9660,dev=/dev/cdrom 0 0 That appeared to get
> supermount working, but when I tried to access a CD in Konqueror, the
> system locked up jelly tight. Had to reboot to get it back. Same thing
> happened trying again in a terminal.
>
> Evidently Texstar's had a little better luck
> http://pclinuxonline.com/article.php?sid=434&mode=thread&order=0&thold=0
>
> --
> Tom Brinkman Galveston Bay
>
>
