slackware_slackware 安装_slackware 停止开发(7)

init4

Slackware boot scripts

Slackware uses BSD-style init scripts as opposed to System V style boot scripts. What the heck does that mean to the new Slackware user? It's the process by which Slackware handles the booting and shutdown of the system. With the BSD-style init scripts, you'll find a single script for each runlevel in /etc/rc.d/. For example, if you want to boot into runlevel 4, Slackware runs the /etc/rc.d/rc.4 script. System V boot scripts use a directory for each runlevel containing each script that must be run at that runlevel. To each their own... they both have their benefits and drawbacks. Just remember that Slackware's boot scripts are located in /etc/rc.d/.

If you notice, there are some init scripts that are executable that you might not need and some that you might want. You can disable/enable these Slackware boot scripts by changing the executable bit:

chmod-xrc.(scriptname)

chmod+xrc.(scriptname)

One thing that jumped out at me was, since I installed the new 2.6 kernel, the old rc.modules-2.4.33.3 module loading boot script is still executable. I don't need this to run since I'm using the new 2.6 kernel that I've installed, so:

chmod-xrc.modules-2.4.33.3

Also, the symbolic link rc.modules still pointed to the old 2.4 modules script, so I removed that and re-linked rc.modules to the 2.6 script:

rmrc.modules

ln-src.modules-2.6.17.13rc.modules

CPU Frequency Scaling

If you've got a laptop or a newer CPU that supports dynamic frequency scaling, then you'll have to recompile the generic kernels Slackware provides - it's not supported by default. If you didn't install the 2.6 kernel source earlier on, you'll have to do that now. You can find the source and header packages in the /extra directory on the DVD.

本文来自电脑杂谈，转载请注明本文网址：
http://www.pc-fly.com/a/jisuanjixue/article-29548-7.html