On Sun, Feb 11, 2001 at 02:49:10PM -0500, Glenn Becker wrote: > > All, > > I try to tune in to any discussions of how to compile a new / custom > kernel on the list, but I was wondering ... is there a convenient doc on > how to do this the Debian way? I am currently running 2.2.17 & don't feel > any great *need* to upgrade/date, but would like the know-how. hm, read a little bit /usr/src/linux/Documentation (IIRC) there are several docs for you. One important ist the changes file.
A normal way to compile a new Kernel ist: cd /usr/src/linux (linux ist offten a symlink to your latest kernel sources) make config/menuconfig/xconfig (choose one) make dep clean bzImage modules modules_install Then you've to wait some time. cp System.map /boot/System.map-<your-kernel-version> then link to /boot/System.map with ln -s Now it's time to copy your Kernel cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-<your-kernel-version> O.K. know link your Kernel to /boot/vmlinuz with ln -s So your kernel should know be in a good position. Now read man lilo.conf and edit /etc/lilo.conf. Reinstall lilo with the lilo command on the commandline and reboot. That's the shortest way to a new kernel. If you don't like to recompile your modutils etc. for Kernel 2.4.x stay with a 2.2.x Kernel (latest 2.2.18) Cu, Sven -- Ich weiß nicht, wieso ihr euch so echauffiert. Die Warnung ist doch wirklich deutlich zu lesen auf der Packung. Da steht in großen, deutlichen Lettern: "Microsoft". NATÜRLICH funktioniert das nicht. Mehr als warnen können sie euch nicht. [Fefe in de.alt.sysadmin.recovery]
