On Wed, Jul 21, 2004 at 08:41:31PM +0200, Wim De Smet wrote:
> On Wed, 21 Jul 2004 12:17:40 -0600, CW Harris <[EMAIL PROTECTED]> wrote:
> > On Wed, Jul 21, 2004 at 07:55:27PM +0200, Wim De Smet wrote:
> > > Hi,
> > >
> > [...]
> > >
> > > You normally don't need a modprobe.conf, everything should be in
> > > /etc/modprobe.d. modprobe.conf is just an empty file on my system. I'm
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > Is this true? Mine (a mostly Sarge with module-init-tools 3.0-pre2-1) has:
> >
> > # This line loads the part of the modprobe configuration managed with
> > # update-modules(8) and built from the contents of /etc/modprobe.d/.
> > include /lib/modules/modprobe.conf
> > ^^^^^^^^^^^^^^^^^^
> > Which seems very important to me (not a GURU here).
> >
>
> module-init-tools in sarge is 3.1-pre5. Maybe it has something to do
> with the older version, or maybe you need this if you use udev or
^^^^^^^^^
Yes that was it. I see in the changelog that between 3.0 and 3.1
modprobe.conf is no longer used since /etc/modprobe.d/* files are parsed
directly without the need for update-modules to process them.
--
Chris Harris <[EMAIL PROTECTED]>
-------------------------------------------
GNU/Linux --- The best things in life are free.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
