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 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.
Thanks for finding that out. Of course, the 2.2 kernel documentation does say that you should configure kmod. > 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. > > Perhaps you should file a bug on it? Maybe, but I tend towards the idea that if you decide to go your own way on this, it's not a lot to expect you to have to modify the startup script too. > > And what about 2.4test kernels (that I'm running) ? I don't have a > > /proc/sys/kernel/modprobe - what should I do????? How do the magic > > scripts in /etc/init.d deal with that???? > > They run kerneld. Wrongly. Ditto. (Maybe, ... too.) Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.