Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I want super moutn disabled (supermount -i diable) because every time I load a game with WineX i get the cd error. I saw a lot of people with the same problem but all their solutions did not work. I have a burner which is inaccessible with the default fstab. If you post please include things liek why this goes here. All the fstab sites I looked at looked similiar to this
Well, really from that page, it would seem that should explain it all quite well. Here's what I'd put in place of the cdrom entry:
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
and for your burner:
/dev/cdrw /mnt/cdrom2 iso9660 noauto,owner,ro 0 0
Because those are similar to my entries
I believe by removing those supermount options from your fstab will make it so that you don't use supermount for those particular devices. This would be good if you wanted to continue to use it for other devices, meaning you didn't want to disable it completely.
You will also need to make the symlinks if your distro hasn't:
ln -sf /dev/hdc /dev/cdrom
And for your burner drive:
ln -sf /dev/scd0 /dev/cdburner
ln -sf /dev/scd0 /dev/cdrw
Don't forget to logout and back in. And this should all be done as root btw.
Well, if you make the symlinks I talked about, then /dev/cdrom will actually be pointing to your correct cdrom device, /dev/hdc
If you cdrom device is /dev/hdd then replace that in the symlink I provided. To find out which one, simply do this as root:
and see if you cdrom device ejects. If it does, then you are good to go.
If you only want to get rid of automount you can fire up
mcc (be root) choose; moint points , your cd device, options
there you can change that.
For experimenting anyways, back up your fstab, take the lines
concerning the removable media like cd or floppy out , save it
reboot and then use them from command line only.
That makes sure no supermount or automount daemon is
oh for the difference in fstab entries; if you use the proper symlinking the /dev/cdrom should work fine but mandrake uses
/mnt/cdrom redhat and some others /dev/cdrom
with supermount -i diable it gets rid of the supermount in fstab. I can mount cdrom. I can ls and see contents of cd in cdrom. This is what I get when I try to mount cdrom2 with mount cdrom2 (this is doen in mnt dir)
mount: wrong fs type, bad option, bad superblock on /dev/scd0,
or too many mounted file systems
when I mount -t cdrom2 I can then cd to cdrom2 but i can not see contents of the cdrom. same when i mount /dev/scd0. Any ideas?
did you get that from the cdrecord -scanbus? Where it shows up as the 3rd? Wouldn't the symbolic links that it creates be correct if I could burn cd's? Or is that the sd03 that it burns to and the sym links to the cdrom device are bad? Would they need to be updated to read scd3 instead of 0? I have given up on the cdrecorder so far because everytime I insert a cd it ejects it. No matter what format it is. But if this is a possible solution I will give that a try. I thought it was a broken piece of gear.