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 have made many attempts in the past to update the linux kernel and read plenty on it but I always fail. What could be going wrong.
Right now I have 2.4.9-e.3 and want to update to 2.6.9
Does the source of the old kernel have to be installed before updating to the new Kernel.
This seems to be a huge step. A lot of packages will need to be updated. A lot of things can go wrong. Have a look at /usr/src/linux-2.6.9/Documentation/Changes for the requirements:
Current Minimal Requirements
Upgrade to at *least* these software revisions before thinking you've
encountered a bug! If you're unsure what version you're currently
running, the suggested command should tell you.
Again, keep in mind that this list assumes you are already
functionally running a Linux 2.4 kernel. Also, not all tools are
necessary on all systems; obviously, if you don't have any PCMCIA (PC
Card) hardware, for example, you probably needn't concern yourself
o Gnu C 2.95.3 # gcc --version
o Gnu make 3.79.1 # make --version
o binutils 2.12 # ld -v
o util-linux 2.10o # fdformat --version
o module-init-tools 0.9.10 # depmod -V
o e2fsprogs 1.29 # tune2fs
o jfsutils 1.1.3 # fsck.jfs -V
o reiserfsprogs 3.6.3 # reiserfsck -V 2>&1|grep reiserfsprogs
o xfsprogs 2.6.0 # xfs_db -V
o pcmcia-cs 3.1.21 # cardmgr -V
o quota-tools 3.09 # quota -V
o PPP 2.4.0 # pppd --version
o isdn4k-utils 3.1pre1 # isdnctrl 2>&1|grep version
o nfs-utils 1.0.5 # showmount --version
o procps 3.2.0 # ps --version
o oprofile 0.5.3 # oprofiled --version
You may want to consider to renew the complete system ?!
I have extracted the file to /usr/src/linux-2.6.9 and entered that directory. SU to root.
Then I use make menuconfig and set up the options, saved my configuration file on exit.
Then make dep. It tells me that its not required at this time.
I then type make bzImage. I recieve an error message saying:
You don't need to run grub after you've installed a new kernel, just edit /boot/grub/menu.lst (or whatever it's config file is called on your system) so that it points to your new kernel. If you try a 2.6 kernel make sure you update your version of module init tools as the module handling is completely different in 2.6 kernels.
Originally posted by Andrew Benton You don't need to run grub after you've installed a new kernel, just edit /boot/grub/menu.lst (or whatever it's config file is called on your system) so that it points to your new kernel. If you try a 2.6 kernel make sure you update your version of module init tools as the module handling is completely different in 2.6 kernels.
Thanks for your help, I am trying to edit the grub.conf file to include /boot/initrd-2.4.12 but the file is not there. Do I have to move that file form somewhere else or does this mean that installation failed?
What modules you need/want to include depends on your kernel configuration.
If you didn't include the filesystem driver into the kernel for example, you'll need to include the module into initrd.
If the filesystem of / (root) is reiserfs, and CONFIG_REISERFS_FS=m you need to add reiserfs to the -m option. Same for ext2 etc.
The same applies to all modules that need to be present at an early stage of the boot process (e.g. HDD controller driver, framebuffer devices etc.). If they are included into the kernel and not confugured as modules, you may leave this empty.
Your rootdevice should be obvious: it's the device that is mounted to / in /etc/fstab.
Have a look in man mkinitrd for all these options.
That looks good to me, but the thing I have a problem with is this - why would you build support for your root filesystem as a module? Are you not expecting to reboot? In fact, why would you make anything as a module? If you need support for something, complie it into the kernel. If you don't need a particular feature, why waste time compiling it?
Originally posted by Andrew Benton That looks good to me, but the thing I have a problem with is this - why would you build support for your root filesystem as a module? Are you not expecting to reboot? In fact, why would you make anything as a module? If you need support for something, complie it into the kernel. If you don't need a particular feature, why waste time compiling it?
Only if you did what Andrew said: if you've compiled everything you need at boottime into the kernel and not as modules.
Andrew: I fully agree with what you've said! But it's not impossible to have your root filesystem as module. It is simply not necessary if you compile the kernel for yourself. But some people clone the kernel configuration from the standard kernel of their distribution and these are often compiled with these things as modules to have a small but flexible kernel.