On Sunday 22 October 2006 18:02, cothrige wrote:
[...]
In the past, as a Slackware user, I never installed an OS where I
didn't immediately compile a new kernel. Slack uses a 2.4 kernel, and
I use some peripheral items which seem to require, or at least greatly
prefer a 2.6 kernel. The process I used was very simple, and I got
quite used to it. I downloaded the sources from www.kernel.org and
opened them up in /usr/src/. I then would run 'make menuconfig',
'make' and 'make modules_install.' I copied the bzImage into /boot,
as well as the System.map and config file. I edited lilo.conf, ran
/sbin/lilo and rebooted into the new kernel. All usually went well
and I rarely had to look back.
[...]
Or, is there maybe a Debian tool to compile a kernel which is
intended to be used rather than this "classic" method? While things
seem fine with the kernel installed from apt, better than fine
actually, I figure the day is going to come when I will need to
compile a new kernel, and I would like to know if possible what to
expect. Not to mention just plain how to do it.
[...]
Hi Patrick,
I always compile my own kernels the Debian (testing) way like this:
-Install the latest Debian linux-source package (currently
linux-source-2.6.17); or you can use vanilla source as you describe