Xuan Baldauf writes:
>
>
> Richard Gooch wrote:
>
> > Xuan Baldauf writes:
> > >
> > >
> > > Jeremy Brown wrote:
> > >
> > > > Xuan Baldauf wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > Setting "include /etc/modules.conf" in /etc/modules.devfs does not
> > > > > work
> > > > > for me. After tracking the problem down, I set the include to the
> > > > > start
> > > > > of the file and then it worked.
> > > > >
> > > > > My system:
> > > > >
> > > > > SuSE6.3
> > > > > Linux desktop 2.4.0-test5 #1 Fri Jul 28 19:12:56 CEST 2000 i586
> > > > > unknown
> > > > > modprobe version 2.3.6
> > > > >
> > > > > I hope that is enough to indentifiy the real problem source (maybe I
> > > > > have a too old or too new modprobe?)
> > > > >
> > > > > Xuân. :o)
> > > >
> > > > I have experienced exactly the same behavior on TurboLinux 6.0 with
> > > > modutils 2.3.11-1. Do you also see a stream of "Cannot locate module
> > > > /dev/<something>" at boot?
> > >
> > > I do this too, but also when placing "include /etc/modules.conf" to the
> > > top
> > > of /etc/modules.devfs. But I'm sure this time the remaining problem is
> > > somewhere in the init scripts, a process wants to access /dev/xconsole
> > > where
> > > no xconsole is. I have to track it down.
> >
> > It was a modutils bug, fixed in 2.3.12.
> >
> > BTW: I'm on holidays at the moment, so people shouldn't expect any
> > replies soon :-)
>
> So have a pleasent time. :o) When you're back, you can tell me, where to
> place the
> "include" statement when using modutils 2.3.12. But it works for me, so there
> is
> no real need to change. :o)
At the end, of course, just like it is in the modules.devfs I ship.
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|