On Fri, 07 Jan 2005 11:44, SnapafunFrank wrote:
SnapafunFrank wrote: My concern here is that I can find the ways to do these things BUT do they apply with this latest kernel and my system anymore?
Thoughts anyone?
Ok this seems to be degenerating a little. The 2.6 kernel makes it ever easier to customise and build your own kernels. Once you have the source installed (doesnt matter where), just change into the directory and you're ready to roll your own ;) the basic steps are make mrproper --> clean the source tree make menuconfig --> te easiest way to configure imho make --> builds the kernel make install --> installs the kernel to /boot make modules_install --> installs any kernel modules and you're done. You will need to create an entry for this kernel in you boot manager. eg in grub add a new menu entry to point to vmlinuz. Your old entry should point to the full kernel name you normally use. (establish this at the command line by typing uname -r) A couple of things you may want to decide are whether you want a 'modularised' kernel or one with everything built in, a so called 'monolithic' kernel. The monolithic kernel is easier in some ways because all the support options you choose are already there, you dont have to figure out which modules to load when you reboot. However a modularised kernel uses less memory (if you have lots this doesnt matter so much) and can be significantly more secure. Also if you dont have module support, things like the nvidia kernel module, which is compiled seperately, are rendered useless. My recomendation is to use modules :) An initrd is designed to offer modules to the kernel that may not be accesible from the normal module tree ( eg /lib/modules/linux-<kernelversion> created when you run 'make modules_install'. You can avoid using initrds by compiling support for certain key things such as disk format (eg ext3, reiserfs etc) and any other special requirements the kernel needs to pull up the system to a basic level so 'init' (the program that loads you system runlevel) can take over. -- "Note that if I can get you to \"su and say\" something just by asking, you have a very serious security problem on your system and you should look into it." (By Paul Vixie, vixie-cron 3.0.1 installation notes)