🚀 go-pugleaf

also   when I ran the setup for  Red Hat 6.0  to try a reinstall it did'nt
detect a
CD Rom either ..   something about block device  again...

;-(

noel wrote in message <89ogta$hg7$1@kermit.esat.net>...
>
>I seem to have the same /dev configuration  (and dates) as your
installation
>so thats ok
>also the fstab file is fine.
>
>I don't have a file   isofs.o   in my  /lib/modules/kernel-ver/fs
>directory.  Do I need this file??
>(someone mentioned this to me)
>
>The CDRom is functioning ok as I ran the win NT setup disks and it detected
>an  ATAPI  (PCI) cdrom controller.
>
>strange..
>
>thanks
>n.
>
>steyaert@my-deja.com wrote in message <896al2$stc$1@nnrp1.deja.com>...
>>I'm not certain someone else can't give you a better answer, but:
>>
>>First off, do an ls -la /dev/cdrom
>>
>>This should show you a line like:
>>
>>lrwxrwxrwx   1 root     root            3 Feb  7 06:23 /dev/cdrom -> hdc
>>
>>Your results will vary based upon the hardware that you have.  What
>>this shows is that /dev/cdrom is a link to /dev/hdc, so do the same
>>thing with your device:
>>
>>brw-------   1 oracle   disk      22,   0 May  5  1998 /dev/hdc
>>
>>It should show up as a block device.  Again, based upon hardware, the
>>22, 0 that shows up for me will probably not match yours.  It should
>>show up with at least the brw at the beginning.  If you have one that
>>shows up as c, your device was corrupted.  If you don't have a backup,
>>you could try removing the device and re-creating with mknod.  (See the
>>man pages for information.)  But, since it was corrupted in device
>>type, it may have lost its major and minor node information, also.  In
>>this case, you can try playing around, but you are probably better off
>>reloading.
>>
>>Secondly, in the /etc/fstab file, you should have a line similar to:
>>
>>/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,ro
>>0 0
>>
>>If your file does not match, you probably have a problem with your
>>configuration.
>>
>>Third, does the CD-ROM still work?  Do you strictly have one OS on the
>>box or multiple?  It may be that the CD just failed, and you have found
>>it by chance with this error.  (Does the mount appear to access the CD?)
>>
>>Lastly, depending on how much you have loaded, just like with good old
>>Win95, sometimes reloading is a very easy fix.  Linux loads pretty
>>quick.  It just depends on what other uses you make of your system.
>>
>>Terry Steyaert
>>steyaert@my-deja.com
>>
>>In article <8965l3$5aa$1@kermit.esat.net>,
>>  "noel" <maccelt@hotmail.com> wrote:
>>>
>>> Hello,
>>>
>>> I'm in trouble again.   My cdrom on RH6.0 used to mount using command-
>>line
>>> or linuxconf.
>>>
>>> Now suddenly its stopped working -   when I try to mount using  "mount
>>> /mnt/cdrom"  I
>>> get rebuffed with :
>>>
>>>    #mount  /mnt/cdrom
>>>      mount:  the kernel does not recognize /dev/cdrom as a block
>>device
>>>                     (maybe 'insmod driver'? )
>>>
>>> # insmod iso9660
>>>     insmod:  iso9660: no module by that name found.
>>>
>>> Linuxconf tells me its mounted successfully but obviously is failing
>>in the
>>> background.
>>>
>>> It is unfortunate for me that Linux is giving me these problems as I
>>am only
>>> a beginner
>>> really.   sigh!
>>>
>>> thanks for expert advice...
>>> noel
>>> macloch@hotmail.com
>>>
>>>
>>
>>
>>Sent via Deja.com http://www.deja.com/
>>Before you buy.
>
>