Originally Posted by ve1drg
I was just thinking..... when you install slackware in the normal fashion, you never have to also go to the 'extra' disk/directory to separately install the modules. Whey in the world do you have to do that when you select a different kernel than the default one - at the start of the installation process?
I know that when I go and get a new kernel and install it in Slackware or any other distribution, the installation process automatically creates the necessary modules. But it appears that with Slackware - if you choose other than the default installation kernel that you are going to have to go and find the modules after you finished installing slackware. In other words, after you are all finished putting on slackware you than have to go and look for the related/necessary moduules?????
That does not sound right to me!!!
There is no more to it than reading what is actually on your screen when you boot the install CD... the opening screen tells you to press F2 and F3 for more information.
In the F3 screen (listing the choice of boot kernels) you will notice these two lines:
huge26.s - A loaded 2.6 kernel (requires modules from /extra)
test26.s - A loaded 2.6 kernel (needs modules from /testing)
You don't have to boot the CD in order to read that screen - look at http://slackware.osuosl.org/slackwar...solinux/f3.txt
You should also read the RELEASE_NOTES for Slackware 11.0 (yeah I hear you thinking 'who reads those' well too bad if you don't). That file states (right behind the reasons for adding 2.6 kernels as a convenience in the installer):
Also, the kernel module packages for 2.6.x are not part of the
standard installation, so if you install using huge26.s or test26.s
kernel you'll have to install the corresponding kernel-modules package
when you're done. They can be found under /extra/linux-220.127.116.11/ (or
ISO number two under /extra/linux-18.104.22.168), or
/testing/packages/linux-2.6.18/ (or ISO number four under