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 runniung slackware 8.0 (zipslack), and I downloaded the kernel source files to compile my modem drivers into, but I don't know how to install the source...the file name is
Installpkg won't install it, it says it's corrupt, what do i do? Re-download or use another tool??
After you install RH 7.1 for the first time...there's NO .config to be found anywhere (not even the /usr/src/linux directory).
Everybody probably knew that.
SO... You say (and everyone has too) to run "make oldconfig" to create a .config file of your current system configuration.
(this is where I think things don't match up...)
When I do this on my system (RH 7.1)...all it does is ask me questions about my system (more than half of which I have NO clue about...and I'm sure most newbies don't either)...so I answered the questions (y or n) as best I could....BUT of course...that's not good enough. After compiliing that config, I got a bunch of things failing at boot up. Then I just re-install RH and try again.
SO...when you guys are saying...."run the make oldconfig" to create a .config file of your current system configuration...is this what you guys had in mind??
When I first heard someone say this, this is what I imagined it would do: Linux would magically look at my current system and spit out a .config file that matches my systems current (working) condifguration without having to ask me any questions at all.
NOW, if what I just said IS the way its suppose to work...would someone please tell me. Because so far...that has not been the way it works for me.
NOW HEAR THIS, in my quest to find out what my current configuration is, I looked and looked...and found a directory in /usr/src/linux called "configs" (/usr/src/linux/configs). In here, theres a bunch of xxx.config files...and one of them named:
There are others for i386, etc....but my system is i686.
SO, I looked into this config file and found this has settings that seem to match what I deemed my system to be set as. I have loaded this config file in my xconfig and have saved it (so now I have a .config file in my .usr/src/linux directory). I have yet to compile it to see if this time, my system will boot up without any problems. As soon as I do...I'll post....
Yeah, those kernel*.config files found in /usr/src/linux-x.x/configs does work when you compile using them.
Be warned: These config files will practically turn on everything in your system, so compile time increases tremendously.
The upside: For those of you who don't have a working copy of a .config file for your system, can use this a basis. Then, later on turn off those options you're not using. And those you aren't sure of, use trial and error to figure it out - if something goes wrong, just turn it back on.
Anyhow, how this helped me:
My situation was: I'm trying to configure IP MASQ, but the process includes patching my kernel. That, of course, meant also compiling. My problem was: At compile time, since I didn't have a .config file, compiling would create one for me by asking me all this questions about my system (half of which I knew nothing about). OR, if I did go into xconfig or menuconfig before I compiled, it creates a .config file that doesn't reflect my current system. Therefore, after compilation, I was left with a bad kernel.
Using these kernel*.config files (although generic) gave me a working configuration. So when I patched my kernel, I used these .config files when I compiled the kernel.
Any feedback would be greatly appreciated...as always.