Hi, I would like to know if it is possible to know what options were used to compile a kernel ( i.e. the kind of options you make when you do a "make xconfig"), only from the resulting binary ? Thanks, CP -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
under the source directory, try: make oldconfig Louis Fung C Hennessy wrote:
Hi, I would like to know if it is possible to know what options were used to compile a kernel ( i.e. the kind of options you make when you do a "make xconfig"), only from the resulting binary ?
Thanks, CP
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Louis Fung wrote:
under the source directory, try: make oldconfig
I should have been more precise, I have a compiled kernel and I would like to know what options were used to compile it. However I do not have the config file of this compilation. Anyone any idea ? Should I look at the symbols compiled into the kernel ?? Thanks, CP -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
* C Hennessy (CP.Hennessy@iname.com) [20000104 00:37]:
know what options were used to compile a kernel ( i.e. the kind of options you make when you do a "make xconfig"), only from the resulting binary ?
There is no way to get that info easily. This has been discussed a few times
on linux-kernel but never led to results that went into the kernel. If I do
remember correctly there was even a patch posted that would make that info
available as a pseudo file under /proc.
--
Philipp Thomas
participants (3)
-
CP.Hennessy@iname.com
-
louisfung@mindspring.com
-
pthomas@suse.de