RE: Getting config from kernel
Joe Emanaker said: A file called '.config' is generated at the top of your kernel source tree This file will still be there after you've compiled the kernel, so all you need to do is copy it to a safe location and drop it back in when you want to generate the same kernel. Which only leaves the question: where can I get the one that was used to generate the kernel in the current kernel-package? You've probably guessed it by now: there isn't one because the initial kernel's precompiled. I don't know of a definitive way of recreating such a file. I can suggest only that you look at what hardware's recognised and which daemons are started at boot-time (run /etc/dmesg), and look around /proc for recognised devices and interrupts. Does someone on the list know a better way? Casper Boden-Cummins. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Getting config from kernel
Okay, I sent this to the list once already, but I'm not sure it got through. I'm trying to get IP aliasing going on my brand spankin' new Debian 1.1 box. Unfortunately, it doesn't appear to have been compiled in, nor could I find a module for it in /lib/modules/current/ipv4. I tried getting the linux-source package and doing make modules, but, when I tried to insmod ip_alias.o, it told me that my 2.06 modules don't match my linux 2.0.6 (even though I'm using the 2.0 version of the modules package, which was supposed to fix that bug). So, I've resigned myself to recompiling the kernel. However, I'm worried that, during the QA of make config, I'll accidentally say no to a driver that I need. For example, with my network card, I'm not exactly sure which driver is driving it, but I know that the card is working with the stock 2.0.6 kernel that came with debian. Since I'm doing this over the net, and since I'd like to avoid having to pay a visit to the physical machine if at all possible, I'd like to make sure that all my necessary drivers are compiled in. The way I'd really like to do this is to be able to somehow extract or ftp a copy of the config file used to make the stock debian kernel. Then, I'd know that I was starting from something that I *know* works, and I could then make incremental changes to that. So, a few questions: 1 - Any ideas on how to get ip_alias.o to load? 2 - Where is the information generated by make config kept? For example, suppose I forgot to compile in *one* crucial driver, and I don't want to go through the grueling QA that make config puts me through. Where can I make that one-line change and then go on to make depend, etc.? 3 - Is there any way I can extract or obtain a copy of what config was used to generate the 2.0.6 kernel that I'm using? - Joe -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
RE: Getting config from kernel
Joe Emenaker wrote: Okay, I sent this to the list once already, but I'm not sure it got through. I was hoping someone else would answer this, because I only have vague details in my head. (If we only used Debian at the office...) Can't help with the IP aliasing, but: So, I've resigned myself to recompiling the kernel. However, I'm worried that, during the QA of make config, I'll accidentally say no to a driver that I need. The way I'd really like to do this is to be able to somehow extract or ftp a copy of the config file used to make the stock debian kernel. 2 - Where is the information generated by make config kept? For example, suppose I forgot to compile in *one* crucial driver, and I don't want to go through the grueling QA that make config puts me through. Where can I make that one-line change and then go on to make depend, etc.? 3 - Is there any way I can extract or obtain a copy of what config was used to generate the 2.0.6 kernel that I'm using? A file called '.config' is generated at the top of your kernel source tree, which contains a list of all the selected compilation options from make config, make xconfig or make menuconfig, in the form IP_ALIASING=yes BLAH_BLAH=module FOOBARWIZ=no This file will still be there after you've compiled the kernel, so all you need to do is copy it to a safe location and drop it back in when you want to generate the same kernel. Casper Boden-Cummins. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Getting config from kernel
I'm trying to get IP aliasing going on my brand spankin' new Debian 1.1 box. Unfortunately, it doesn't appear to have been compiled in, nor could I find a module for it in /lib/modules/current/ipv4. I just got this working... Pretty nifty feature if you ask me... So, a few questions: 1 - Any ideas on how to get ip_alias.o to load? Nope... 2 - Where is the information generated by make config kept? For example, suppose I forgot to compile in *one* crucial driver, and I don't want to go through the grueling QA that make config puts me through. Where can I make that one-line change and then go on to make depend, etc.? It's kept in linux/.config . I believe that make config actually looks at your current kernel to figure out a default if you don't already have a .config.. I say this because every time I compile a fresh kernel it already has 'Y' on the correct network card. Also, you should be able just modify the line or two in that file to turn on ip aliasing, given a working kernel source (ie. one that finds your network card.) Just my $.02 Mike -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
