Hello,

I checked the actual kernel-konfiguration with `make menuconfig`.

Question:
Is there a way to list or printout ALL custom kernel konfigurations? How?



Thank's a lot in advance for every feedback!

John

I guess I don't understand your question, John. Trying to list ALL custom kernel configs to me sounds like trying to list all prime numbers, a tough job. In my case, I want to use the same kernel on several different computers around here, so I start with the config from the kernel-generic-smp package, then change what I want, normally just "CONFIG_HZ_1000=y" & "CONFIG_APM=n". Then I go down to the filesystem section & build ext2 & ext3 into the kernel, instead of as modules, so that I won't have to use an initrd. I started with the config file from Slackware 12 & have used it in a number of kernels since; it works quite well in several different machines.
Regards,
Bill

If you're trying to show everything you've changed, you could do a `diff` on your new .config and the original .config included with Slackware (or whatever .config you started with). This would show all of the differences. For example:
Admittedly this will be VERY messy, especially if you are using .config files from two different kernel versions (where the names of some options may be changed, some options may have been removed, and some added).

Thank's a lot for te helpful feedback! At the moment I would be happy to be able to compare the the .config of the same kernel-versions.

Question:
Were do I find/download the "original" .config in order to be able to compare it with the .config of a "Slackwaree remaster"?


Thank's a lot in advance for your help!

John

The config files for the kernels shipped with slackware can be found under the kernels dir on the CD, or
in the same dir on a mirror site, e.g.:

ftp://ftp.slackware.com/pub/slackwar...e-12.0/kernels

And if you have customized a kernel, your config is "/usr/src/linux-2.6.XX.YY/.config".
Regards,
Bill

rather it is in /lib/modules/$(uname -r)/source

Six of one, half a dozen of another.
Regards,
Bill

Actually TSquaredF, if you don't build kernels in /usr/src, your method doesn't work. duryodhan's method is more foolproof. I'm just saying this as an idiot that builds his kernels as an unprivileged user in a special folder in my home directory to avoid screwing anything up and remaining logged in as root for too long. But if you're 'normal', /usr/src/linux-2.6.XX.YY/.config will work.

Yes, you are right. I need to change the way I compile kernels.
Regards,
Bill

Im trying unsuccessfully (e.g. with 'locate .config') to find the .config on a system booted with a Slackware/Slax LiveCD. (I do know that normally the .config can be found in e.g. # cd /usr/src/linux-2.6.19.5)


Questions:
1.
Where(path) is the .config normally stored on a Slackware based LiceCD?

2.
And what's the best approach to find the kernel config file(.config) ?




Thank's a lot in advance for your help!

John

I would guess that the live cd doesn't contain the sources at all. You should be able to get the configuration of the running kernel, though, by looking at
the entry in /proc/config.gz(if the kernel was compiled with proc-config support) with this command:
'zcat /proc/config.gz'

Thank you very much for your help, 'zcat /proc/config.gz' does work with that LiveCD :-)

But the size of the LiveCD config ('zcat /proc/config.gz') is only about 20k and the original .config (downloaded from ftp://ftp.slackware.com/pub/slackwar.../kernels)found in the folder huge.s is about 70kb.


Therefore the output of the command

$ diff .config.old .config > CustomKernel.txt

is very confusing for me..

Questions:
Is it required to delete all non existent lines in the .config (downloaded from ftp://ftp.slackware.com/pub/slackwar...e-12.0/kernels) in oder to be able to compare it with the .config gfrom the LiveCD ('zcat /proc/config.gz')? Am I doing something wrong?

Or should such a compare task be done with an other tool?



Thank you very much for any help!

John

The info in /proc/config only contains the lines which are marked with 'y' or 'm', that is, only the options which were chosen to be hard-linked or compiled as modules. The full .config file contains other lines like comments, which begin with '#' and also the options which are not selected, which have this syntax:
# CONFIG_M386 is not set.

If you use the command 'cat .config |grep -v '^#^' it should give an output very similar to what's in /proc/config. Or, you could do this:
zcat /proc/config.gz > .config
then run:
make oldconfig
The .config should then have a more normal look (it gets re-written by the oldconfig rule).