Is there any potential problem with changing the fstab line that reads the cdrom to /dev/hdc rather than the traditional /dev/cdrom ?

I was having trouble creating a symbolic link to /dev/hdc from /dev/cdrom. Upon reboot the fstab would always say there was an unexpected file type for the cdrom.

Changing the /dev/cdrom to /dev/hdc fixed it, and I can now

$ mount /etc/cdrom


My fstab line looks like this:
/dev/hdc /mnt/cdrom/ iso9660 noauto,user,kudzu,ro, exec,unhide 0,0

and if i run ls -l /dev/cdrom, I get
lrwxrwxrwx 1 root root 8Dec 21 06:16 hdc -> /dev/hdc

Thanks.

ok, i have some questions for you ? i hope these are typo's but i have to ask.
whay are you trying to mount the cdrom in /etc/cdrom when the fstab say /mnt/cdrom?
remove the / after mnt/cdrom in the fstab.
Why do you have kudzu and unhide as options?
also remove the , between the 0 0.
i think you should take a look at man fstab to know what options to put where in the fstab file.

Thanks for your reply. Sorry, but those were typos. I wrote it at 6am after an allnighter.

It's $ mount /mnt/cdrom that I run.

The line is written without the extra "/" and ","

Kudzu came as a default, and from what I've read maintains the file. It can be taken out.

I really don't understand what unhide does, just saw it in some others fstab files and added while I was trying different stuff.

Again, sorry about those typos!!

But does using /dev/hdc instead of /dev/cdrom (with cdrom having a symbolic link) present any problems?

Thanks.

i dont think so, as long as everything works ok

Thanks, I'll leave it alone until I run into problems. So good so far.

yeah, that's totally normal, it's only a soft link to another file, and has absolutely no effect at all on how it works, hdc is the actusal device, so whatever is linked to that device will behave exactly the same. its only done generally make it easier to understand