kernel is used, additional packages must be added after the
installation -- at the very least the kernel-modules package.
Possibly also the kernel-headers to provide /usr/include/sound
used to compile ALSA applications.
extra/linux-smp-2.6.17.13/
- added a 2.6.17.13 kernel, modules,
and headers with SMP and hyperthreading support, optimized for
i686 or better cores (including dual core CPUs).
Installation and Configuration, cont.
Conversely, a small number of packages have been removed, replaced or merged since 10.2:
- ap/sgml-tools (replaced with linuxdoc-tools)
- d/python-demo (merged with python package)
- d/python-tools (merged with python package)
- l/db3 (moved to /pasture)
- l/db31 (moved to /pasture)
- l/db4-
- (moved to /pasture)
- n/nail (renamed to mailx - see "Package Additions")
- xap/abiword (became a pure Gnome app)
- xap/mozilla (replaced with seamonkey)
- xap/xvim (renamed to vim-gvim) - see note above in "Package
Additions"
Still, not a bad install footprint weighing in at 3GB for a completely full install. Of you can tailor the package selection during install to only add the software you want. Not everyone needs Apache or MySQL if they're just running a workstation. Anyway, on to the install!

First, I booted the Slackware 11.0 Install DVD using the default sata.i kernel. This is a new-ish laptop so the hardware is pretty current and does have a SATA hard drive. Unfortunately, the default sata.i kernel didn't support the controller on my laptop which I could tell because the system went into "compatibility mode" and disk operations were MUCH slower. A quick glance over at the debug terminal (ALT-F4) and I could see how slow the partition formatting progress was so I stopped the format and rebooted to see the list of other possible pre-compiled kernels to choose from. The 2.6-series kernel does support SATA very well so I chose the huge26.i kernel for my installation. This worked and the resulting formatting and software install went by very quickly. I also chose the huge26.i kernel for my default kernel, as well.
The 2.6 modules aren't installed by default so you'll have to mount the DVD and install the 2.6 modules in the /extra directory. The lack of modules means that your sound won't be working among other things, so you'll definitely want to fix that post install. If you stick with the 2.4 kernel, all the modules are correctly installed and you won't run into this problem.
Also install the 2.6 headers and source so you can recompile the kernel and any other software included in the /extra directory that you'd like to have. If you also install the generic 2.6 precompiled kernel in this directory, don't forget to re-run LILO to update the boot manager.
After I installed the modules, I rebooted and my sound card was detected. But it's muted by default, so you'll have to run the alsamixer program as root, un-mute the sound and adjust the volume levels as desired. I put everything at 65% and it's pretty loud. This is one of those things that might confuse newbies at first. Most newer distro's take care of these little things post-install for you.
Don't forget to create a normal user account for yourself since the Slackware installer doesn't do this. Log in as root and issue the adduser command. Follow the prompts and accept the default options - really the only thing you should type in is the desired username and your password. Hit the Enter key for everything else unless you just want to put in your room and phone numbers.
Slackware boots into runlevel 3 by default, which means you're sitting at the command line interface when you boot up. Again, newbies might be confused about what exactly to do at this point. You can change runlevels by editing the /etc/inittab and specifying runlevel 4 if you want X11 and the nice GUI login screen started automatically. You can, of course, simply change into another runlevel with the init command from the shell:
init 4
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/.
如果您对本文有任何疑问或者建议,请到讨论区发表您的意见:
>>
论坛入口 <<
上一篇:slackware 11.0 安装及基本配置 下一篇:Slackware Linux启动过程详解
【文章评论】
【收藏本文】
【推荐好友】
【打印本文】
【我要投稿】 【论坛讨论】