From: Keith Owens <kaos@ocs.com.au>
To: "Matthew Pitts" <mpitts@suite224.net>
Cc: Jacob Anawalt <anawaltaj@qwest.net>, linux-kernel@vger.kernel.org
Subject: Re: Knowing what options a kernel was compiled with
Date: Sun, 28 Jan 2001 16:29:06 +1100 [thread overview]
Message-ID: <4687.980659746@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sun, 28 Jan 2001 00:13:48 CDT." <web-2874335@suite224.net>
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/
next prev parent reply other threads:[~2001-01-28 5:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 5:21 Knowing what options a kernel was compiled with Jacob Anawalt
2001-01-28 5:06 ` Keith Owens
2001-01-28 5:13 ` Matthew Pitts
2001-01-28 5:29 ` Keith Owens [this message]
2001-01-28 12:16 ` Andreas Ehliar
2001-01-28 5:43 ` Jacob Anawalt
2001-01-28 8:26 ` roger
2001-01-28 10:37 ` Chmouel Boudjnah
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 20:41 Torrey Hoffman
2001-01-29 20:56 ` mirabilos
2001-01-29 21:01 ` Ville Herva
2001-01-30 1:00 ` Keith Owens
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=4687.980659746@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=anawaltaj@qwest.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpitts@suite224.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