SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Guys I am performing the following steps to compile the 2.6.0 kernel...
1.) make xconfig
2.) make bzImage
3.) make modules
4.) make modules_install
5.) updating lilo and running lilo
Are these the correct steps to compile the 2.6.0 kernel? The reason that I am asking this question is that I have read conflicting steps in other posts.
Are these the same steps needed for compiling any kernel(2.4, 2.6 etc)?
I still dont really know when ur sposed to do the system.map thing... I've never once done it, and everything works great for me... but a friend of mine HAS to do it, or usually ends up with kernel panics and weird problems!!!
CodeWarrior, the steps u mentioned are right... that's what i did and am running the kernel without any probs. to avoid major problems, import the config file from /boot/config file.(that is the default provided by the distro.) then, make changes to the config.. and follow the rest of the steps. copy the bzImage from the arch subdir, and also System.map to /boot. then edit lilo.conf and run lilo. now the new kernel should load properly. ATB.
make install does all of this AND runs /sbin/lilo. There are, however, a few changes that must be done first in order for make install to work.
** See Edit below for correction **
1) /usr/src/linux/Makefile must have line #450 uncommented.
2) If you plan to keep your existing kernel in case things go wrong (good idea), then you'll want to add the proper entries in /etc/lilo.conf.
That's it, and make install works every time. I don't see the point either, but some like to do things the "old school" way...nothing wrong with either.
EDIT: the .config in /boot is pointless unless you're copying it there for backup purposes. make install does NOT do anything with this. It is just a default config for whichever kernel you installed at installation. Anytime the config is changed, it resides in /usr/src/linux.
go to your source file (ie: /usr/src/linux-2.6.0)
do make mrproper
copy old defconfig from /linux-2.4.23/arch/i386/boot, go to ~/linux-2.6.0/arch/i386/boot, delete resident defconfig, paste in "old" defconfig. do:
when the config prompt comes up, hold the Enter key down till your root prompt returns. do:
make && make bzImage && cp /usr/src/linux-2.6.0/arch/i386/boot/bzImage /boot/vmlinuz-2.6.0 && make modules && make modules_install && make install
write in your new linux boot entry in lilo.conf, do
lilo && reboot
only if you uncomment the makefile export line; ( in the event you're slammed with the SuSE style write-over of /boot/vmlinuz) you may want to keep your old vmlinuz, and boot back to that if you grenaded your new boot.. thus the cp ~/boot/bzImage. beentheredonethat--bad habits die hard.