[SOLVED] A new Slackware use need help about kernel and initrd
SlackwareThis Forum is for the discussion of Slackware 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.
A new Slackware use need help about kernel and initrd
First of all I apologize for my bad English, but now come to my questions.
I'm new to linux and I recently installed slackware64 14.0 on my laptop. I followed the slackbook at www.slackbook.com and the documentation at docs.slackware.com to configure what i can, but I would like to understand a few things about the kernel and the initrd. After creating the initrd with the utility mkinitrd_command_generator.sh and started the generic kernel, now I want to understand the function of the initrd and when i need to recreate it. For example, if I upgrade my kernel to a new version I have to recreate the initrd? Or I can use the same?
About to the kernel, if I want to compile the kernel using only the necessary modules for my hardware where should I start? I know that the process of compiling the kernel is more or less in this manner http://stackoverflow.com/questions/8869931/compiling-the-2-6-0-kernel-on-slackware and that there are different ways to configure the kernel as the "config file" or "xconfig" "menuconfig" but how do I find during this process the modules strictly necessary?
Thanks in advance for your answers and i will appreciate any links, HowTo or resource that can help me
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Originally Posted by Nitrogen1
if I want to compile the kernel using only the necessary modules for my hardware where should I start?
Don't do that, it's useless as you won't see any performance increase.
You still want to do that? Follow Alien BOB's guide as suggested by jmccue, but after "make oldconfig" run "make localmodconfig". This will remove all modules not currently loaded, so plug-in all your removable devices before, otherwise you won't have support for them. If you don't have enough slots (e.g. USB ports), you can unplug a device then plug-in another, provided each device stays plugged-in in at least 30 seconds so that the kernel have enough time to load modules it needs. If for some reason a module doesn't get automatically loaded you will have to "modprobe" it manually instead.
Last edited by Didier Spaier; 09-17-2013 at 03:30 PM.
Reason: Typo corrected
[...] now I want to understand the function of the initrd and when i need to recreate it. For example, if I upgrade my kernel to a new version I have to recreate the initrd? Or I can use the same?
Purpose of initrd is to include as many kernel modules and utilities, which are not included in kernel itself, as needed to boot system. Huge kernel includes almost everything and it's capable of booting by itself most of the time, while generic kernel needs initrd to boot.
Originally Posted by jmccue
You should recreate a new initrd and reinstall lilo.
I believe it's a typo. You only need to run lilo to update MBR, not reinstall, after every change with kernel or initrd.
Nicolas, loading your files in Firefox, one was recognized as Windows-1252 and the other one as UTF-8, though both be encoded in ISO-8859-1 (as set in vim and confirmed by iconv here). There is nothing we can actually do about that (probing the encoding of a file is too tricky), but I'd suggest you always use UTF-8. As a reminder, converting an existing file is just a matter of: