In the process of trying to link /dev/cdrom to /dev/hdd, a mistake was (obviously) made, and now /dev/hdd , /dev/cdrom , and /dev/dvd are all reported as broken links and denoted with "X" icons... I tried to use MAKEDEV to fix at least /dev/hdd, but that seemingly did nothing...
How do I fix this problem, and return the files to their original values?
Thanks.
Gveto

Don't you want to mount like this:

mount /dev/cdrom /mnt/cdrom

and not hdd?

I've never seen hdd used. Usually there's a number referring to the partition you're mounting.

Not a mount question....sorry. Let me work on it...

So it looks like you symlinked /dev/hdd to /dev/cdrom instead of the other way around then. I'd fix it by removing the symlink /dev/hdd and then try running MAKEDEV, that's how I fixed it when I did a similar mistake

Oh, and just to be completely safe, I grabbed MAKEDEV, and ran it in a different directory, then moved the /dev/hdd back to my /dev directory:
mv /home/temp/hdd /dev/hdd

But the key here is that you need to remove the bad symlink (which is a symlink to a symlink of itself right now) and then make the new device.

Cool

Hey - thanks for the quick reply.
I did some research on block devices, and found that MAKEDEV was what I needed, and I tried that (in the /dev directory, though) with no avail as mentioned above... This was before I posted. So, I copied MAKEDEV in to a temporary directory, and tried to run it from there from shell:

And nothing happens... Shouldn't this create all of the block device files since I specified no specific devices? Nothing is created in the directory....
And what worries me is that the file MAKEDEV size is listed as 0 bytes...
So, I downloaded the MAKEDEV .rpm for my distribution (RH 8.0), and it says that that package is already installed... Fair enough, but shouldn't this file have something in it?
Please, oh Linux gurus... Tell me where I'm going wrong!
Thanks.
Gveto

I got my MAKEDEV from the LFS files. Here's a link:
ftp://ftp.linuxfromscratch.org/lfs-p...AKEDEV-1.7.bz2

Then extract it, wherever you want, probably that temp directory, then run:
./MAKEDEV -v generic

This *should* create those devices in that temp directory. Then you *should* as root, be able to move the needed missing device to the /dev directory.

The only problem I can think you might have is if RH is using DevFS, in which case you should simply be able to fix it with a reboot I'd think.

Cool