Re: Using kerneld in Slink
On Sun, 18 Apr 1999, Wichert Akkerman wrote:
> Previously Jor-el wrote:
> > The test for /proc/sys/kernel/modprobe is, I assume, for detecting
> > whether kmod is running, and this is not the case when using the default
> > kernel in Slink. Hence the kerneld script exits immediately after the test
> > fails without starting kerneld. Thus even if /etc/modules has the "auto"
> > entry, kerneld doesnt start up unless the abovementioned test is commented
> > out.
>
> Which is how it should be. kmod is started as soon as the kernel boots,
> so the `auto' option in /etc/modules is now obsolete. In fact
> /etc/modules can almost be considered obsolete, it has very few uses
> now. And like I already explained to you: even if you run kerneld on a
> 2.2 kernel it has absolutely no use, since the kernel simply doesn't use
> it anymore.
>
Wichert,
I reread your previous note to me. It seemed to imply that kmod is
only for the 2.2 kernels - when running the 2.0.x kernels, kerneld is what
is used. Is that not the case? If so, what I described is still a problem
because kerneld is not being started up under the 2.0.x kernel.
Jor-el
Reply to: