Knowing what options a kernel was compiled with

Knowing what options a kernel was compiled with

[Jacob Anawalt]

Is there a way to know what options a running kernel was compiled with,
if you dont have access to the source or configure files it was compiled
off of?

In particular, I am trying to discover if 'advanced router' and 'equal
cost multi path' options are compiled into RH7 kernel-2.2.16-22. I would
also like to know if there is a way to discover this information for
other settings that do not have a /proc entry or other visible object
(eg modules).

I am not following this list currently, so if you would please include
my email in the replies, I would appreciate it.

tia,
Jacob Anawalt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Knowing what options a kernel was compiled with

[Keith Owens]

On Sat, 27 Jan 2001 22:21:41 -0700, 
Jacob Anawalt <anawaltaj@qwest.net> wrote:
>Is there a way to know what options a running kernel was compiled with,
>if you dont have access to the source or configure files it was compiled
>off of?

No.  You have to insist that whoever distributes the kernel binary also
distributes the .config file that it was compiled with.

Don't bother arguing that the kernel should record this info, it has
been discussed before and rejected.  This is a problem for the
distributors, not for the kernel.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Knowing what options a kernel was compiled with

[Matthew Pitts]

On Sun, 28 Jan 2001 16:06:57 +1100
 Keith Owens <kaos@ocs.com.au> wrote:
> On Sat, 27 Jan 2001 22:21:41 -0700, 
> Jacob Anawalt <anawaltaj@qwest.net> wrote:
> >Is there a way to know what options a running kernel was
> compiled with,
> >if you dont have access to the source or configure files
> it was compiled
> >off of?
> 
> No.  You have to insist that whoever distributes the
> kernel binary also
> distributes the .config file that it was compiled with.
> 
> Don't bother arguing that the kernel should record this
> info, it has
> been discussed before and rejected.  This is a problem
> for the
> distributors, not for the kernel.
Keith and Jacob,
Some distributions DO include the config. It may be located
in the /boot dir with a name CONFIG-2.2.10 or similar. I
know that Caldera 2.3 shiped that way(2.4 may also). If you
have the install CDROM, the kernel source install may have
it (e.g. Linux-Mandrake 7.x).

Matthew
mpitts@suite224.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Knowing what options a kernel was compiled with

[Keith Owens]

On Sun, 28 Jan 2001 00:13:48 -0500, 
"Matthew Pitts" <mpitts@suite224.net> wrote:
>Some distributions DO include the config. It may be located
>in the /boot dir with a name CONFIG-2.2.10 or similar. I
>know that Caldera 2.3 shiped that way(2.4 may also). If you
>have the install CDROM, the kernel source install may have
>it (e.g. Linux-Mandrake 7.x).

I know that some distributions ship .config but not all do.  A long way
down on my TODO list is "submit a requirement to FHS that .config,
System.map and other kernel related text files must be shipped in
directory <foo>".  I would like <foo> to be /lib/modules/`uname -r`
since that directory is already kernel specific, but we have to handle
kernels without modules and disks with restricted size in /lib.
However that discussion is best held on the FHS/LSB lists, not l-k.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Knowing what options a kernel was compiled with

[Andreas Ehliar]

On Sun, Jan 28, 2001 at 04:29:06PM +1100, Keith Owens wrote:
> On Sun, 28 Jan 2001 00:13:48 -0500, 
> "Matthew Pitts" <mpitts@suite224.net> wrote:
> >Some distributions DO include the config. It may be located
> >in the /boot dir with a name CONFIG-2.2.10 or similar. I
> >know that Caldera 2.3 shiped that way(2.4 may also). If you
> >have the install CDROM, the kernel source install may have
> >it (e.g. Linux-Mandrake 7.x).
> 
> I know that some distributions ship .config but not all do.  A long way
> down on my TODO list is "submit a requirement to FHS that .config,
> System.map and other kernel related text files must be shipped in
> directory <foo>".  I would like <foo> to be /lib/modules/`uname -r`
> since that directory is already kernel specific, but we have to handle
> kernels without modules and disks with restricted size in /lib.
> However that discussion is best held on the FHS/LSB lists, not l-k.

Speaking of .config, wouldn't it make sense to add some comments to the
beginning of that file detailing at least the kernel version this config
file was generated for?
Other information like the time the file was generated could be useful as well.

regards
Andreas Ehliar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Knowing what options a kernel was compiled with

[Jacob Anawalt]

Matthew and Keith,

Thank you to both of you for your input, info, and quick responses. I
just wanted to make shure there weren't tricks still in the bag that I
hadn't learned about in this area. I'll look for the config file.

Jacob Anawalt

Matthew Pitts wrote:

> On Sun, 28 Jan 2001 16:06:57 +1100
>  Keith Owens <kaos@ocs.com.au> wrote:
> > On Sat, 27 Jan 2001 22:21:41 -0700,
> > Jacob Anawalt <anawaltaj@qwest.net> wrote:
> > >Is there a way to know what options a running kernel was
> > compiled with,
> > >if you dont have access to the source or configure files
> > it was compiled
> > >off of?
> >
> > No.  You have to insist that whoever distributes the
> > kernel binary also
> > distributes the .config file that it was compiled with.
> >
> > Don't bother arguing that the kernel should record this
> > info, it has
> > been discussed before and rejected.  This is a problem
> > for the
> > distributors, not for the kernel.
> Keith and Jacob,
> Some distributions DO include the config. It may be located
> in the /boot dir with a name CONFIG-2.2.10 or similar. I
> know that Caldera 2.3 shiped that way(2.4 may also). If you
> have the install CDROM, the kernel source install may have
> it (e.g. Linux-Mandrake 7.x).
>
> Matthew
> mpitts@suite224.net

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Knowing what options a kernel was compiled with

[roger]

Well, even if the config file hasn't been included you can
presumably _write_ the config file from the kernel setup
program...and that is _probably_ the configuration of the
kernel you are running n'est-ce-pas?

Roger.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Knowing what options a kernel was compiled with

[Chmouel Boudjnah]

"Matthew Pitts" <mpitts@suite224.net> writes:

> Some distributions DO include the config. It may be located
> in the /boot dir with a name CONFIG-2.2.10 or similar. I
> know that Caldera 2.3 shiped that way(2.4 may also). If you
> have the install CDROM, the kernel source install may have
> it (e.g. Linux-Mandrake 7.x).

no in Mandrake 7.x it shipped with the documentation of the kernel
package.

-- 
MandrakeSoft Inc                     http://www.chmouel.org
                      --Chmouel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

RE: Knowing what options a kernel was compiled with

[Torrey Hoffman]

Should someone submit a patch to copy the .config to a standard location as
part of "make install" or "make modules_install"? If included in the
official sources, that good example would encourage the distribution
maintainers do the same. 

Torrey Hoffman


>-----Original Message-----
>From: Keith Owens [mailto:kaos@ocs.com.au]
>[...]
>I know that some distributions ship .config but not all do.  A long way
>down on my TODO list is "submit a requirement to FHS that .config,
>System.map and other kernel related text files must be shipped in
>directory <foo>". 
>[...]

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Knowing what options a kernel was compiled with

[mirabilos]

From: "Torrey Hoffman" <torrey.hoffman@myrio.com>
> Should someone submit a patch to copy the .config to a standard location as
> part of "make install" or "make modules_install"? If included in the
> official sources, that good example would encourage the distribution
> maintainers do the same. 
> 
> Torrey Hoffman

I dont do make install because it could do something unwanted.
modules_install isn't good either because some prefer monolithic
kernels. But split-include could do the job, as it's called as of 2.2
for each compile.

-mirabilos

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12+(proprietary extensions) # Updated:20010129 nick=mirabilos
GO/S d@ s--: a--- C++ UL++++ P--- L++$(-^lang) E----(joe) W+(++) loc=.de
N? o K? w-(+$) O+>+++ M-- V- PS+++@ PE(--) Y+ PGP t+ 5? X+ R+ !tv(silly)
b++++* DI- D+ G(>++) e(^age) h! r(-) y--(!y+) /* lang=NASM;GW-BASIC;C */
------END GEEK CODE BLOCK------


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Knowing what options a kernel was compiled with

[Ville Herva]

On Mon, Jan 29, 2001 at 08:56:12PM -0000, you [mirabilos] claimed:
> From: "Torrey Hoffman" <torrey.hoffman@myrio.com>
> > Should someone submit a patch to copy the .config to a standard location as
> > part of "make install" or "make modules_install"? If included in the
> > official sources, that good example would encourage the distribution
> > maintainers do the same. 

I find this neat:

http://www.it.uc3m.es/~ptb/proconfig/

It created /proc/config entry with obvious functionality, but wastes
pretty little ram.


-- v --

v@iki.fi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Knowing what options a kernel was compiled with

[Keith Owens]

On Mon, 29 Jan 2001 12:41:31 -0800, 
Torrey Hoffman <torrey.hoffman@myrio.com> wrote:
>Should someone submit a patch to copy the .config to a standard location as
>part of "make install" or "make modules_install"? If included in the
>official sources, that good example would encourage the distribution
>maintainers do the same. 

Not until FHS decide what that standard location is.  An entry in FHS
will carry far more weight with distributors than a kernel Makefile
patch.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/