Quote:
|
Originally Posted by duryodhan
ok I will try out what you said but I still dont understand how only by installing the kernel and modules a new kernel will be loaded whereas there is a looong guide on how to do it in Shilo's Guide.
|
that's why i choose slackware now:
on mdk [mandriva] it's all tippy toes:
install source; headers; a bunch of devel (if not all); cd to /usr/src/linux* ...
make mrproper
and in the 2.4 era (I consider the 2.6 era as of 2.6.8)
you had to make depmod and so on,
and even then, if you did go trough kernel-building to add something you discover that not only it won't patch but the kernel is already 'overpatched' by far...
now:
i drop the tarball's contet in /usr/src/linux*
go there and make patches if needed (bootsplash I miss)
menuconfig my favorite options on a vanilla kernell and build it...
after that,
make the modules otside of the tree.
install them in /lib/modules/...
nad run the vanilla-unpatched (except bootsplash) with add-on modules.
1. patching works out of the box
2. building works out of the box
3. new kernel works (*) out of the box
4. modules don't spoil the vanilla kernel (not even nvidia)
(*) first one makes:
1. modules
2. modules_install
3. bzImage
4.a install
4.b check /etc/lilo.conf
5. run lilo (twice at least)
6. check if you did run lilo
7. reboot
once upon a time ...
