[Top] [All Lists]

[Richard Gooch <rgooch@atnf.csiro.au>] Re: Module autoload with devfs

To: linux-xfs@xxxxxxxxxxx
Subject: [Richard Gooch <rgooch@atnf.csiro.au>] Re: Module autoload with devfs
From: Ed McKenzie <eem12@xxxxxxxxxxx>
Date: 08 Apr 2001 02:32:19 -0400
Sender: owner-linux-xfs@xxxxxxxxxxx
--- Begin Message ---
To: Ed McKenzie <eem12@xxxxxxxxxxx>
Subject: Re: Module autoload with devfs
From: Richard Gooch <rgooch@xxxxxxxxxxxxx>
Date: Sun, 8 Apr 2001 15:50:09 +1000
In-reply-to: <20010405111815.A9140@eem12.resnet.cornell.edu>
References: <20010405111815.A9140@eem12.resnet.cornell.edu>
Ed McKenzie writes:
> Richard,
>       I've enabled autoload in devfsd.conf as described in the devfs
> FAQ, but it doesn't seem to do anything for me. Opening /dev/fb0
> doesn't modprobe matroxfb_base, even though alias fb0 matroxfb_base is in
> modules.conf, and all this works when devfs is disabled. Any hints, or
> is this feature not yet implemented?

alias   /dev/fb0        matroxfb_base


>       I've also noticed that my cdroms will sometimes get numbered
> in strange ways, e.g. cdrom0 and cdrom2 rather than zero and
> one. What causes this?

It's a side-effect of module autoloading and unloading. I have a plan
to fix that. In the meantime, just mount the cdrom driver at boot.


Permanent: rgooch@xxxxxxxxxxxxx
Current:   rgooch@xxxxxxxxxxxxxxx

--- End Message ---
<Prev in Thread] Current Thread [Next in Thread>