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 am trying to use any 2.6 kernel in my LFS system, but I get some funky errors at boot time. First of all, two or three long number/letter sequences are puked out at the top of the regular messages produced at boot. Then I get the following:
fsck.ext2: No such file or directory blah blah....I am told that the superblock might be corrupt.
1) It boots just fine using 2.4.24
2) When I run e2fsck -b (backup superblock as stated by mke2fs -n) -y /dev/yada I am told that the system was not cleanly unmounted and e2fsck then does its magic. But I can run e2fsck again using the same parameters and it tells me again that the disk was not cleanly unmounted. I am confused. Did nothing get fixed?
All of my software is above the minimum requirements as stated in the Documenation/Changes directory of the kernel source.
I have my LFS system on a logical partition. Could that cause problems? The disk itself is 120 GB, but I have to assume that as long as the boot loader finds the partition, I should be fine.
At one point I was trying to use the new bttv module while booting under 2.4.24, but the module wouldnt initialize correctly, and I was unable to remove it before halting. My system hung. I powered off and when I rebooted, fsck checked the root partition. To tell the truth in my drive to get that module to work this happened a few times.
Finally, if a superblock is corrupted, then copying the entire system to another partition means that that new partition contains a corrupted superblock too, right?
I am tempted to reinstall LFS using 2.6 headers (no I don't think that has anything to do with this necessarily, but...then again I am rather ignorant about this whole business)
Cool. I fixed my own idiocy. I thought that I would post this anyway.
I simply had not included advanced support for hard disks in my kernel. Thats it! Heh. I have slack installed on my system. It works fine using 2.6.0 and is on the same harddisk. I should have suspected something because at boot time my swap partition was giving me an error too. Anyway I just copied the config file to double check and sure enough I needed support for harddisks for x86 machines.