Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 load the kernel 2.6.7 on a HP DL380 G3 server.
I have compile numerous times with various otpions but with no success, I always get a blank screen when I choose the compiled version in the grub although the system seems to be loading in the background I cannot see a thing. I think that the parttions are not mounting because I cannot see anything in the logs. I am using SUSE Linux Enterprise version 8. Can anybody help me!
In theory you don't need it if you have support for your disks (IDE or SCSI) and filesystem built into the kernel. However, I never got the 2.6 kernel to work without an initrd, so I just use it. The Debian kernel comes with an initrd and it was simpler for me to just keep using the initrd when I compiled my custom kernel. When I was using the 2.4 kernel, I just built in support for my filesystem and IDE and I didn't need an initrd, but that didn't work the same way with the 2.6 kernel. I didn't spend a lot of time trying to figure out why. Perhaps there is some other module needed.