1) i compiled custom kernel and it went good but
when i look at rc.d directory i see a link rc.modules->rc.modules-2.6.21.5-smp
what should i do with this link ? there is another file rc.modules-2.6.21.5 (none smp)
and in my current kernel doesn't include smp

2) i put a file under /etc/rc.d/ and made it executable with chmod
all it does is some modprobe calls , but in startup this doesn't run
why doesn't it run ??

you can see in rc.S (or/and M) how the startup works. there is no harm with running rc.modules ( you might get a few errors though, if you omitted some modules ).

you also need to make a call from rc.local to your script to run it.

For #2

You have to add some lines in your rc.M

Example:

I have a little script in rc.d directory called `rc.smbmounts'
nothing special it just mounts my samba shares.

In orther to make it automatically execute, besides making it
executable I added this lines to rc.M:
right at the end of the script. And done. my shares mounts
automatically. Of course there is always a better way. Its
a matter of taste.

Good luck

-W

aren't they going to write about the changes that happened in slackware12.0
in slackbook or other documentation form? (besides the release changelog ..)

http://slackware.osuosl.org/slackware-12.0/


btw, these are not changes from 11.0 to 12.0.

In rc.S you will find:

# This loads any kernel modules that are needed. These might be required to
# use your ethernet card, sound card, or other optional hardware.
# Priority is given first to a script named "rc.modules.local", then
# to "rc.modules-$FULL_KERNEL_VERSION", and finally to the plain "rc.modules".
# Note that if /etc/rc.d/rc.modules.local is found, then that will be the ONLY
# rc.modules script the machine will run, so make sure it has everything in
# it that you need.

(with the code that follows these notes)

So what i did was rename rc.modules-2.6.21.5-smp (or whatever it was) to rc.modules, (remove the symlink first).
Then edit your rc.modules to suit yourself. Now, whatever kernel you compile, rc.modules will load.
Of course you can enter your own stuff in there as well if udev didn't take care of it. Some people will say do this in rc.modules.local, you can decide for yourself.

tobyl

Hi,

Did you read the Slackware 12.0 CHANGES_AND_HINTS.TXT, UPGRADE.TXT and RELEASE_NOTES?

1) If it's a hanging symlink, delete it. You should then copy or symlink rc.modules-2.6.21.5 to rc.modules.

2) There are several ways of doing what you want to do. The simplest being to add your modprobe calls to rc.local.