On Fri, 2003-03-07 at 12:24, Buchan Milne wrote:
> On Fri, 7 Mar 2003, James Sparenberg wrote:
> 
> >    I've had this problem on some systems (with a number of distro's) and
> > the problem was that the correct symlink in /dev isn't created. 
> 
> You will note that was dealt with earlier (modprobe ide-cd if root is the 
> only person to have logged in).

No on these boxes the symlink wasn't created no matter who logged in....
notably RH 7.0 7.1 off the top of my head.  I've also had this happen
with MDK on the odd occasion.  Yes MDK does do it correctly but rather
than re-install I just did what was missed.  (MDK 8.0 and 8.1 did this
on several machines.) But on the couple that did have to be reinstalled
for whatever reason (hdd gone south etc) the next time it was created. 
I've found it to be a random oops not a reproducible bug.  But after
close to 3000 OS installs in the last year alone, I've seen a few of
them.

James

> 
> > The
> > default in eject is to eject /dev/cdrom   but if the real device for
> > your ide-scsi is say scd0 ejecting /dev/cdrom won't work.  Try this if
> > for example your real device is /dev/scd0 then type eject scd0 .... if
> > it ejects then you have the symlink problem.  Two fixes either create a
> > little script that does the eject scd0  or create the symlink.
> 
> I was running eject on /dev/hdc, which is the only possible device file 
> for the drive (no ide-scsi emulation). Reboot, and it seems to be better 
> ... but we'll see what happens ...


Reply via email to