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.
no , i m not using initrd and i didnot compile support for the filesystem into kernel.
infact i didnt made any changes in filesystem during configuration.
Well, there's your problem, then. How is the kernel supposed to mount the root filesystem if it doesn't have a driver for it? Either use mkinitrd to make an initrd with the filesystem module on it or compile support for your root filesystem directly into the kernel.
BTW, VFS is a sort of "meta-filesystem" in the kernel. It presents a unified interface to all the different types of filesystems such a Reiser, Ext2/2, vfat, etc.
Just keep at least 2 kernels, One that you know will work and then one to learn.I compile support "*" for the filesystem and chipset ide drive etc. Anything that you want right away into the kernel and then you don't need an initrd.It just takes a little practice. At first it looks so confusing, so many options.
I was compiling a kernel also yesterday on Slackware 10.2, and had the same error. I found that it was easiest to compile support for the filesystem into the kernel. Since I am new, I used make xconfig so that I would have an easier time configuring the kernel, I would suggest that method for other new people also.
There's an option "root=LABEL=blahblah" which I've never been able to get to work.
With experience i notice that "root=LABEL=..." works when u have only the original kernel on your system.
But as soon as u compile it and name it something else and assign it root=/dev/hdax ( i.e you are keeping both the kernels ), when u try to get into the newly one...it doesn't boot and throws error.
The solution for it is that you should change that "root=LABEL=..." to its full path name, i.e like root=/dev/hdax.
and then give the new kernel its own path.
now the new kernel will work fine.
The LABEL stuff only works when you have support for it compiled into the kernel. Frankly, I find it a bit of a pain and just do things ruudra's way and change it to the appropriate /dev/hdXX. I suppose it can be useful if you're constantly changingyour partitions, but I've noticed weird behavior when you try to put two hard drivex containing partitions with the same LABEL in a system (e.g. when trying to recover files off of a dying hard drive).