DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
-- This next part I only did during my first attempt at a kernel compile, because someone in irc mentioned this : 'From the kernel source README: "Do NOT use the /usr/src/linux area! This area has a (usually incomplete) set of kernel headers that are used by the library header files. They should match the library, and not get messed up by whatever the kernel-du-jour happens to be." That's why I don't symlink the kernel source to /usr/src/linux anymore --
Code:
ln -s linux-2.6.23.8 linux && cd /usr/src/linux
Code:
make clean
make mrproper
cp /boot/config-`uname -r` ./.config
make menuconfig
-- Now I load the config file for my current kernel, and then make changes to the config --
-- After --append-to-version= I write a name for the kernel, it begins with a minus (-) and has no have whitespace.
Then the kernel compiles (usually) and I install it like --
Code:
dpkg -i fake_kernel_name.deb
dpkg -i fake_kernel_headers_name.deb
shutdown -r now
That's how I usually do it. The guide I learned to do all this from is here.
Oh, I don't recognise anything after make "menuconfig"
I see debian package manager,
I guess that's a good example of difference between distributions.
If you use the "Debian" way of compiling a kernel, it's cleaner because you get a kernel packaged correctly for Debian and tracked properly by the base system. With a generic installation, the kernel will still work, but won't be tracked by the package manager.
While I used to believe that compiling a custom kernel is the best way to go, it's usually a bad idea unless you absolutely cannot do without a feature not enabled in the stock kernel.
Last edited by vharishankar; 08-18-2008 at 02:22 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.