On Tue, 25 Apr 2000, [EMAIL PROTECTED] wrote about, Re: modules:
> On Tue, 25 Apr 2000, Alexander 'Loki' Agibalov wrote:
>
> >
> > LOL, of course, I've read it!
> > But there's just an explanation of what kmod is...
>
> And why you don't want to run kerneld any more.
> >
> > well, I removed /etc/conf.modules file and
> > commented the lines in /sbin/init.d/boot which refer to
> > kerneld, but still when the system starts up or when I change
> > runlevel from "single" to any other I see the message that
> > "I definetly wouldn't want to run kerneld on kernel > something..."
> > And my current kernel is even compiled w/o modules support
> >
> Something in the startup rc files is trying to run kerneld, I think.
> All the distros I know put them in /etc/rc.d, but I admit SuSE is a
> little different. Start from /etc/inittab and see what runs when going
> multi user....how did you comment them? I don't know what /* */ will
> do, but # should work.
> >
> Lawson
I have not been following this thread as i have been away on holiday, but i
did read some messages and saw a few answers which is why i did not
respond, but i think i know why you have this problem, if it could even be
called a problem.
Firstly, it is beter to use modules than have a large kernel, but its more
of a "whatever the user wants" thing.
Secondly i also cannot comment on SUSE, but i have a recolection it is just
about the same as Redhat.
Redhat starts the modules stuff in /etc/rc.d/rc.sysinit, if you took
Lawsons advice you would have seen what it is called in SUSE as its the
first file called in /etc/inittab.
Redhat checks to see if the kernel version has modues defined, it checks
for the makeconfig option;
CONFIG_MODULES=y
Then kerneld will always be started automaticly, considering what you have
typed in your previous mails i suspect you have said "y" to that option and
compiled your kernel accordingly, so the configuration scripts are doing
there job in the way they are expected to.
You have (as i see it) 2 choises,
1) Compile another kernel with the above option answered as "n"
2) Use the following in /etc/rc.d/rc.local, i would place it as the first
entry.
/COMMENT/
Please note which quotes are used, you must use a ` not a '
/End comment/
#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local setup commands in here:
PID=`ps ax | grep kerneld | grep -v grep | wc -c`
if [ "$PID" -gt "0" ]; then
kill $PID
echo "kerneld has been killed..."
else
echo "No kerneld process found, please check with ps ax"
fi
> Don't get suckered in by the comments -- they can be terribly
> misleading. Debug only code.
> -- Dave Storer
>
>
>
>
> ________________________________________________________________
> YOU'RE PAYING TOO MUCH FOR THE INTERNET!
> Juno now offers FREE Internet Access!
> Try it today - there's no risk! For your FREE software, visit:
> http://dl.www.juno.com/get/tagj.
>
> -
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
