From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010808
Description of problem:
I'm using kickstart install over NFS. The /dev/cdrom link does not
get created automatically. Isn't it supposed to do that?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Do kickstart install
Actual Results: The thing checking fstab complains about not finding
and it really isn't there.
Yes, it is supposed to make a /dev/cdrom link. I don't know why it wouldn't.
What kind if cdrom drive is in the machine?
hdc: CD-ROM 50X, ATAPI CD/DVD-ROM drive
In other words plain old cd-rom drive. I have now installed RH 7.1 into about
15 computers, all with the same symptoms. With Red Hat 6.2, no problems.
And now that I think a bit more, I recall that there appears on one VC
messages like "cannot open cd-rom". I didn't pay much attention to them,
because I'm installing over NFS.
This is very strange because I have never seen this in any of my testing and I
do NFS installs every day...
Are these DVD drives? I've seen one other report of a DVD drive having problems.
No, they are all common cd-rom drives. Is there any additional information I
could provide to you?
Are you not installing or not enabling the kudzu service? The /dev/cdrom link
is created by kudzu during the boot process
I am installing kudzu and it is invoked normally when I boot up.
Next week I'm going to make a couple of new installs. I then check more
thoroughly if the link gets created at all, is kudzu removing it or
something like that.
Changing component to kudzu
What does 'kudzu -p -c cdrom' say?
desc: "SAMSUNG CD-ROM SC-152C"-
Hi! I finally figured out what was the problem. Local install script added
/dev/cdrom /mnt/cdrw fstab entry and that somehow made kudzu fail.
Ah, updfstab won't make the link if an entry already exists in /etc/fstab that
it didn't write.