This used to be a problem in older RedHat distributions. Use the user option of the filesystem, in /etc/fstab. Here's an example:

# device    mountpoint    filesystemtype    options            dump fsckorder

/dev/hda5     /              ext2             defaults                    1   1
/dev/hda7     /home          ext2             defaults                    1   2
/dev/hda6     swap           swap             defaults                    0   0
/dev/fd0      /mnt/floppy    msdos            noauto,rw,user              0   0
/dev/fd0      /floppy_ext2   ext2             noauto,rw,user              0   0      
/dev/hdb      /mnt/cdrom     iso9660          noauto,ro,user,unhide,exec  0   0
/dev/hda1     /DOS           msdos            noauto,rw,user              0   0
none          /proc          proc             defaults                    0   0

---------------------------

I have a strange problem. I have downloaded several versions of linux (debian, SME Server, Trustix, and also non linux FreeBSD). All these .iso's were bootable, and their checksum were corrrect. However, my computer can't boot them.
So you might think that my computer can't boot from CD? Wrong. I have burnt a DOS Boot disk that works fine to boot from.

So you think I downloaded wrong .iso's? No. In fact, about 1/30 times I can boot these linux CD's.

So you think I use bad quality CDs? No. On one rw I burnt my third copy of a SME Server .iso, with correct md5sum. CD couldn't be read, just like the other two copies. Then, I erased this CD, put
the DOS Boot CD in, and it worked. Then I downloaded trustix, burnt it on a new CD, and guess what. Can't boot. These CDs could also be read when I booted windows, but not when I booted DOS.

Also, fyi, the few times I have been able to boot from my linux CDs, every time the installers have said that my CD-ROM is empty and that they can't find the install CD, which was the CD they were installed from.

One version of linux worked actually, puppy linux, which you don't install. It runs the whole OS into memory.

My hardware:
Intel Pentium 200 mmx
160 MB RAM
ACORP-5TX32 VER.B (mb)
Tseng Labs ET6000/ET6100 PCI (gfx)
D-Link DFE-530TX PCI Fast Ethernet Adapter (rev. C)
SAMSUnG SCR-2030 JS102 (CD-ROM)
LG StudioWorks 76i (display)

Creative AWE64 16-bit Audio
Voodoo Graphics 3D Accelerator
 

Who did you burn those ISO files??? I hope you know that you have to burn them as image files, NOT data files...
 

Ok you've burnt the iso ok as you state 1 in 30 it will go. There is more than one method of making an iso bootable, which is why you are noting a difference. I'm guessing the dos bootable cd is burnt in a "easy to read" format.

I would suggest a lens cleaner cd, to clean the lens. Burning doesn't seem bothered by it, but I guess the intensity of the laser to burn is less troubled.
 

yes I burnt them correctly. I have burnt them with nero 6, and used the exact same CD-rw several times, every time I use any linux/freeBSD (except puppy) bootable CD I get boot failure. Every time I write a DOS Boot or puppy linux I can boot. I have opened the CD-ROM with screwdrivers (not just the computer, but the actual CD drive), cleant the lense with a piece of cloth, updated to newest BIOS, changed IDE channel, and still I have the exact same results.

You did well to clean the lens with a cloth. Ok sounds like the read on the cdrw is on its way out.
 

I've seen similar problems with cd roms. Hard to pick up in a plain old cd rom, and a tendency to blame the media format and disc media. This is until problems occur with discs that previosly played ok. Your boot up description where sometimes (that includes 1 in 30) the cd will boot, suggest that its failing to read. Unluckily cleaning didn't help.
 

SAMSUnG SCR-2030 JS102 (CD-ROM)
Try a different drive. From my experience having built PCs in a computer shop, samsung cdroms are pants. We ended up calling the Samsung Forty Speed drives Samsung Faulty Speed!

Have a Linux Issue?
Do you have a Linux Question?

Linux Home: Linux System Administration Hints and Tips