devfs
[Top] [All Lists]

Re: devfs newbie: dissapearing or somtimes not created cdrom

To: "Rob MacGregor" <rob_macgregor@xxxxxxxxxxx>
Subject: Re: devfs newbie: dissapearing or somtimes not created cdrom
From: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Date: Fri, 28 Sep 2001 10:04:48 -0600
Cc: devfs@xxxxxxxxxxx
In-reply-to: <F1456H06Ym8Es5FEnoL00009de3@hotmail.com>
References: <F1456H06Ym8Es5FEnoL00009de3@hotmail.com>
Sender: owner-devfs@xxxxxxxxxxx
Rob MacGregor writes:
> >From: C R Johnson <iamcliff@xxxxxxxxxxxxx>
> >
> >I am using the SGI xfs kernel 2.4.2-SGI_XFS_1.0smp with devfs.
> >
> >If I boot with a cdrom in the drive, the system comes up with the drive
> >mounted and working.
> >If I boot without a cdrom in the drive, I get no entry in /dev/cdroms,
> >and hence no working cdrom.
> >Likewise if I unmount a cdrom after booting and leave the drive empty
> >for a number of hours, the device /dev/cdroms/....
> >vanishes and I am once again without my cdrom drive.
> >
> >What do I have to do to either keep the device from dissapearing or how
> >do I (re-)create it in the event it does not exist.
> >
> >This does not seem to be in the FAQ.
> 
> I suspect you'll find that the cdrom drive support is compiled as a module.  
> When the module hasn't been used for some time it'll be removed and devfs 
> will unregister it.  That's what happened to me with my printer and tape 
> drive.  However reloading the modules solved this.
> 
> The solutions I found are:
> 
> 1) Compile into the kernel.
> 2) Have the module load without the autoclean flag (put them in 
> /etc/modules, probably).

You can also configure devfsd to autoload the module, so that when you
attempt to access /dev/cdroms or /dev/cdroms/... the appropriate
module(s) get loaded.

                                Regards,

                                        Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current:   rgooch@xxxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>