On Friday 17 April 2009 07:48:49 Thomas Chef wrote: > A few questions: > - When I recompile the kernel and replace an existingly (in lilo) > configured kernel, do I have to rerun lilo ?
Yes, you must rerun lilo from a working installation. lilo does not understand filesystems, so rerunning lilo tells the boot loader the exact location of the kernel image on disk (in terms of block numbers). This changes with every recompile. grub OTOH, does understand filesystems and you can point it at a kernel image file and it works. grub is the preferred choice for most distros for this reason. Also, you can select the file image and edit options to use at boot time > - Neil: How have you > configured your frambuffer support in lilo/grub ? The handbook is some what > confusing in this matter I think ? Kernel documentation is extremely confusing in this regard :-) It normally involves a "vga=" element in your boot options Check <kernel source>/Documentation/fb/* for more info > - How much do I earn in speed by > optimising and removing unneeded options in the kernel ? Or is it just > kernel-size ? You earn absolutely no speed improvements whatsoever. That would be like uninstalling Opera and expecting Firefox to go fast. What you gain is kernel size, compilation speed (can make a big difference on Gentoo) and some sanity in /lib/modules - you don't actually need 1000 modules there when you only use 10. Building everything in a generic kernel is useful for binary distros like Ubuntu, that have to support everything their users might have but the devs cannot know in advance what that is. So they have complex auto-detect systems that run at startup and load the correct drivers. You DO know what you have, so your life is made much easier by simply building only what you will need. -- alan dot mckinnon at gmail dot com
