Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I'm wondering if I'd like to use 2 kernel(2 different versions), for example I'm not sure whether the new kernel works or not, in this case how should I deal with the System.map? If I change System.map symbolic link to the new kernel's System.map, what'll happen when I boot with the old kernel?
Originally posted by iaMMai
If the system can look after itself,then why have we always copy the corresponding System.map to /boot and change the symbolic link
Bloody good question for second post.
Unnecessary in your case - RH adjusts the link for you each boot. Hence my request for your distro.
Have a look at /etc/rc.d/rc.sysinit if you're interested.
I never bother with the symlink, but I do like to keep kernel/config/Sysmap together in /boot with the kernel level in the name. Gentoo documents it this way, and it works. I probably have around 6 kernels in /boot at any time - helps if they are self-documenting.
Can I ask you another question: what maybe the cause, if the net doesn't work with the new kernel? the network configuration is the same as in case of the old kernel, and I think I have choosen all(or not? :-) ) necessary components for the networking when configuring the kernel in Networking options menu.
what maybe the cause, if the net doesn't work with the new kernel?
Many potential causes! Start with the hardware first: is the driver present and is it loaded correctly? Continue with the logfiles (bootlog, messages, warn etc.)...sorry, can't be more specific if you aren't as well
Seems like you missed something - if it was a loadable module, you should still be getting it.
dmesg | less
to see if there are any relevant messages on start-up.
Mind you, RH is a fairly old 2.4 - if you are going to a current kernel, that is quite a jump.
Basically a matter of "eyeballing" the config I suspect.
If you started out with a different kernel version, (there isn't a .config then in the beginning) you should copy your last .config file and run "make oldconfig" to pick up your old configuration options, and select new options that were not present in the old kernel. Then fine tune it with "make xconfig" or one of the alternatives. Old pro's at this often use an editor to make changes, and then run "make oldconfig" to validate their changes.