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
Quoting brian moore ([EMAIL PROTECTED]):
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
On Tue, Jul 18, 2000 at 01:05:42PM +0300, Pavel M. Penev wrote:
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
On Tue, 18 Jul 2000, brian moore wrote:
Perhaps you should file a bug on it?
Don't be that fast.
Why not? A bug is a bug. 'man kerneld' is quite clear that kerneld
should -not- be run on a 2.2 kernel. Yet /etc/init.d/kerneld is quite
happy to run it on a 2.2 kernel because it
Quoting Jonathan Heaney ([EMAIL PROTECTED]):
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
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
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.
Perhaps you have a problem with your /proc
On Thu, Jul 13, 2000 at 23:41:42 +0200, Erik van der Meulen wrote:
After the reboot all seems well, except a message during boot:
kerneld: you almost certainly don't want to be running kerneld
with = 2.2.x
Thanks a lot for the various responses. I did a: mv kerneld
Quoting Erik van der Meulen ([EMAIL PROTECTED]):
After the reboot all seems well, except a message during boot:
kerneld: you almost certainly don't want to be running kerneld
with = 2.2.x
Thanks a lot for the various responses. I did a: mv kerneld kerneld.old
in
9 matches
Mail list logo
