Re: kerneld message / Workaround
On Mon, 17 Jul 2000, brian moore wrote:
> On Sat, Jul 15, 2000 at 11:51:06AM +0100, Jonathan Heaney wrote:
> > David Wright wrote:
> > > The scripts /etc/init.d/{kerneld,modutils} have to be able to handle
> > > both 2.0 and 2.2 kernels with kerneld or kmod. You will see they do
> > > this by testing for the presence of /proc/sys/kernel/modprobe which
> > > only exists under 2.2.
>
> But doesn't -always- exist on 2.2:
>
> [narvi:/etc/init.d] 11:26:37am 136 % ls -l /proc/sys/kernel/modprobe
> ls: /proc/sys/kernel/modprobe: No such file or directory
> [narvi:/etc/init.d] 11:26:39am 137 % uname -a
> Linux narvi 2.2.16 #6 Fri Jun 23 13:51:08 PDT 2000 i686 unknown
>
> You need to have 'CONFIG_KMOD' set in your kernel build to have it,
> which I don't.
>
> Seems to me that the logic on that is broken. /proc/sys/kernel/modprobe
> is not a good way to determine whether kerneld should be run.
What I think is that you are wrong. If you have compiled your kernel with
'CONFIG_KMOD' defined, then you would have kmod built into your
kernel. "kmod" is a REPLACEMENT for kerneld, remember?
> Perhaps you should file a bug on it?
Don't be that fast.
Regards,
Pavel
Reply to: