From: Arjan van de Ven <arjanv@redhat.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to check the kernel compile options ?
Date: Mon, 04 Feb 2002 18:14:36 +0000 [thread overview]
Message-ID: <3C5ECF8C.1744549C@redhat.com> (raw)
In-Reply-To: <E16XmqC-0007lb-00@the-village.bc.nu> <3C5EC104.A3412D56@uni-mb.si> <E16Xmjc-0001uS-00@Princess> <E16XnUr-0004mf-00@starship.berlin>
> > What he is saying is that you can't do that, generically. Some options are
> > available at runtime through /proc, but most are not. You need to check what
> > happend back at compile time.
>
> Right, there is a religious issue here: some core kernel hackers believe
> that it is wrong to encode kernel configuration in the kernel, and that
> is why it's not available. Technically it is not difficult, nor is it
> difficult to make it memory-efficient.
It's silly to put it permanently in unswappable memory; putting it in
/lib/modules/`uname -r/
somewhere does make tons of sense instead.
next prev parent reply other threads:[~2002-02-04 18:14 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 16:01 How to check the kernel compile options ? David Balazic
2002-02-04 16:54 ` Alan Cox
2002-02-04 17:02 ` David Balazic
2002-02-04 17:23 ` Alan Cox
2002-02-04 17:12 ` David Balazic
2002-02-04 17:16 ` Allan Sandfeld
2002-02-04 18:05 ` Daniel Phillips
2002-02-04 18:14 ` Arjan van de Ven [this message]
2002-02-04 18:24 ` Ben Greear
2002-02-04 18:24 ` Daniel Phillips
2002-02-04 22:11 ` H. Peter Anvin
2002-02-04 23:46 ` Daniel Phillips
2002-02-04 23:34 ` J.A. Magallon
2002-02-04 18:09 ` Samuli Suonpaa
2002-02-04 17:34 ` Thomas Capricelli
2002-02-04 17:50 ` David Relson
2002-02-04 18:22 ` H. Peter Anvin
2002-02-05 22:02 ` Alex Bligh - linux-kernel
2002-02-05 22:13 ` H. Peter Anvin
2002-02-06 9:15 ` Daniel Phillips
2002-02-07 4:13 ` Mike Touloumtzis
2002-02-07 9:32 ` Marco Colombo
2002-02-07 13:18 ` Daniel Phillips
2002-02-07 18:26 ` Mike Touloumtzis
2002-02-07 19:19 ` Daniel Phillips
2002-02-07 20:34 ` Mike Touloumtzis
2002-02-07 20:54 ` Daniel Phillips
2002-02-07 21:08 ` Mike Touloumtzis
2002-02-07 21:33 ` Daniel Phillips
2002-02-07 23:58 ` John Alvord
2002-02-09 21:59 ` Alex Bligh - linux-kernel
2002-02-07 21:08 ` Daniel Phillips
2002-02-07 21:41 ` Mike Touloumtzis
2002-02-07 22:09 ` Daniel Phillips
2002-02-07 22:13 ` Mike Touloumtzis
2002-02-07 22:27 ` Daniel Phillips
2002-02-08 20:53 ` Horst von Brand
2002-02-09 12:22 ` Daniel Phillips
2002-02-11 16:07 ` Randy.Dunlap
2002-02-09 21:39 ` Alex Bligh - linux-kernel
2002-02-06 16:37 ` Bill Davidsen
2002-02-04 18:34 ` David Relson
2002-02-04 21:09 ` Keith Owens
2002-02-05 16:30 ` Thomas Capricelli
2002-02-04 22:12 ` H. Peter Anvin
[not found] <0C01A29FBAE24448A792F5C68F5EA47D217218@nasdaq.ms.ensim.com>
2002-02-12 21:26 ` Paul Menage
-- strict thread matches above, loose matches on Subject: below --
2002-02-06 4:55 Rick A. Hohensee
2002-02-05 23:56 Andries.Brouwer
2002-02-06 0:14 ` Ian S. Nelson
2002-02-06 0:19 ` H. Peter Anvin
2002-02-06 0:20 ` Alan Cox
2002-02-06 10:36 ` Christoph Rohland
2002-02-06 14:16 ` Alan Cox
2002-02-06 15:31 ` Christoph Rohland
2002-02-06 22:13 ` Alex Bligh - linux-kernel
2002-02-06 15:59 ` Randy.Dunlap
2002-02-06 16:32 ` Padraig Brady
2002-02-09 18:15 ` Bill Davidsen
2002-02-11 0:29 ` Daniel Phillips
2002-02-11 19:05 ` Bill Davidsen
2002-02-11 21:17 ` Alex Bligh - linux-kernel
2002-02-12 0:32 ` Daniel Phillips
2002-02-12 16:38 ` Bill Davidsen
2002-02-12 17:23 ` Daniel Phillips
2002-02-12 17:26 ` Padraig Brady
2002-02-12 18:32 ` Bill Davidsen
2002-02-12 21:06 ` Andreas Dilger
2002-02-12 22:10 ` Ville Herva
2002-02-12 22:33 ` Andreas Dilger
2002-02-13 0:49 ` Randy.Dunlap
2002-02-13 2:35 ` Andreas Dilger
2002-02-12 18:26 ` Bill Davidsen
2002-02-13 14:19 ` Horst von Brand
2002-02-13 15:58 ` Daniel Phillips
2002-02-13 23:00 ` Bill Davidsen
2002-02-13 16:25 ` Richard B. Johnson
2002-02-13 18:09 ` Randy.Dunlap
2002-02-13 18:26 ` Daniel Phillips
2002-02-13 18:27 ` Richard B. Johnson
2002-02-13 18:35 ` Daniel Phillips
2002-02-13 18:40 ` Randy.Dunlap
2002-02-13 21:51 ` Bill Davidsen
2002-02-13 22:02 ` Richard B. Johnson
2002-02-13 23:08 ` Bill Davidsen
2002-02-13 23:21 ` Ben Greear
2002-02-13 23:39 ` Andreas Dilger
2002-02-13 22:17 ` Ben Greear
2002-02-13 23:13 ` Bill Davidsen
2002-02-14 16:48 ` Randy.Dunlap
2002-02-15 22:51 ` Andreas Dilger
2002-02-15 23:04 ` Randy.Dunlap
2002-02-16 1:10 ` Randy.Dunlap
2002-02-19 11:14 ` Andreas Dilger
2002-02-16 0:58 ` Andreas Ferber
2002-02-22 19:56 ` Randy.Dunlap
2002-02-23 7:02 ` Andreas Ferber
2002-02-26 6:30 ` Andreas Ferber
2002-03-01 21:01 ` Randy.Dunlap
2002-02-14 1:02 ` Daniel Phillips
2002-02-17 12:11 ` Bill Davidsen
2002-02-12 17:35 ` Chris Friesen
2002-02-11 18:37 ` Randy.Dunlap
2002-02-11 19:26 ` Bill Davidsen
2002-02-06 16:26 ` Ville Herva
2002-02-06 17:26 ` Thomas Capricelli
2002-02-06 18:16 ` David Relson
2002-02-07 7:56 ` Ville Herva
2002-02-07 9:12 ` Thomas Capricelli
2002-02-07 12:22 ` Ville Herva
2002-02-07 21:11 ` Horst von Brand
2002-02-08 8:25 ` Ville Herva
2002-02-07 8:52 ` Horst von Brand
2002-02-06 11:29 ` Marco Colombo
2002-02-06 13:26 ` Horst von Brand
[not found] <fa.c5n369v.1a10827@ifi.uio.no>
2002-02-04 16:21 ` Giacomo Catenazzi
2002-02-04 16:01 David Balazic
2002-02-04 21:47 ` Matti Aarnio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C5ECF8C.1744549C@redhat.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox