cdrom problem

into the Black Sun and said:

What does the last sentence mean? Write in your native language (or use Babelfish) if you're not comfortable with English; there are a few German, French, and Spanish speakers here. Anyway, read on for some more ideas about what could be going on....

"noauto" is not specified. That means the boot scripts will try to mount the device at boot time. This is *not* a good idea for any removable media device. Put noauto in. You will then have to "mountmnt-cdrom" or click on the CD-ROM icon on KDE's desktop to mount the device, but that's no big deal.

The options line is a little off. Most people will want "users" and only "users". The iocharset and codepage options are things that I have never found useful, and most CD-R* media don't need umask= since the kernel's filesystem layer uses Joliet extensions in preference to Rock Ridge even if both are present. I think you want a line sort of like this:

dev-hdd mnt-cdrom auto noauto,ro,users 0 0

supermount tends to cause more problems than it solves. Whatever....

"umount" lost its N sometime in the 1970s. (If you find it, please mail it to Ken Thompson.) Something has a file open undermnt-cdrom-, or hasmnt-cdromor something under that as its current directory. Konqueror seems to do this for some reason; try closing all Konqueror windows and umounting again. If that doesn't help, "lsof +Dmnt-cdrom" executed as root should show what's using the directory. lsof is a really powerful-useful tool; check its man page for lots of info. HTH,

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong