DebianThis forum is for the discussion of Debian Linux.
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.
Great! As for your other question, both your 2.4.x and 2.6.x kernels will check /etc/modules. Some modules are specific to a one of those kernels, so you may see an error message during boot up if you have a module listed that is not part of the kernel. After booting up, you can see what modules are loaded using the command "lsmod". You can see what modules are available by going to the directory /lib/modules/<kernel version> Your 2.4.x and 2.6.x kernels will have separate directories containing their modules.
Thanks for posting this "Debian Way" compile. I had done a few compiles from source on my laptop on a Knoppix HD install the "normal" way without problems, but I recently "upgraded " said laptop to Woody (stable) from CD & decided to try a 2.4.18 recompile using your excellent tutorial. I'm getting a weird error in the "make xconfig" stage. The only thing I can think of is that I'm recompiling the same kernel that I'm using, but that seems a bit farfetched. Does anyone recognize the error?? Is it indicating a filesystem misconfigure??
I don't read chinese, but it appears that the guide I posted here in this forum was copied word for word and presented as that of someone else. Oh well, it's "open source" I guess. They removed my signature at the end, but I think linuxquestions should at least be credited.
If the kernel doesn't work, perhaps you could post the error messages you see and someone may be able to offer some help. By the way "mykernelname" was meant to refer to "my kernel name". You can put a different name there. It is just whatever your want appended to the kernel version number. Debian puts things like "-386-1" as append to versions.
i understand but while i was posting this reply it finally worked without the messages, but the warning messages were about a certain .o file was depreciated or something about no cast i don't know too much aboiut this linux operating system as you can see i am a newbie. I do have something that i came accross in the logs though: quite off the subject of the thread sorry. :
I think so, but I don't know, because I couldn't get the kernel to work without initrd. I thought you just needed to compile in support for the disk (IDE in my case) and root filesystem to obviate the need for initrd. When I tried it, the kernel wouldn't boot. I just configured everything sticking close to the original way the Debian kernel was. I figured the Debian developers know better than me..
ok i'm doing this again on a different computer and having problems with ssh i can't ssh with it when i'm in the same room using 2.6.7 after followed the directions above, on my other computer i had no problems but when i switch to the old kernel i have no problem sshing to the box any ideas?????????? i don't even know what to put as an error message.. sorry
I was reading another post and noticed happytux said for the 2.6 kernel you need the line:
none /sys sysfs defaults 0 0
in /etc/fstab. I added that line to /etc/fstab when I upgraded my kernel, but I forgot to mention it in the above steps at the start of this post. I edited my original post to include this step. Other people have had success following the steps I wrote, so perhaps fstab may be automatically edited when you use apt-get to upgrade to a 2.6.x kernel, but I am not sure.
Location: Europe:Salzburg Austria USA:Orlando,Florida;
Originally posted by m_yates I was reading another post and noticed happytux said for the 2.6 kernel you need the line:
in /etc/fstab. I added that line to /etc/fstab when I upgraded my kernel, but I forgot to mention it in the above steps at the start of this post. I edited my original post to include this step. Other people have had success following the steps I wrote, so perhaps fstab may be automatically edited when you use apt-get to upgrade to a 2.6.x kernel, but I am not sure. [/QUOTE]
when you do a fresh install of 2.6 kernel...is
quote:none /sys sysfs defaults 0 0
necessary in /etc/fstab or only if upgrading thru apt-get install...?