From: Keith Owens <kaos@ocs.com.au>
To: Jacob Anawalt <anawaltaj@qwest.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Knowing what options a kernel was compiled with
Date: Sun, 28 Jan 2001 16:06:57 +1100 [thread overview]
Message-ID: <4504.980658417@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 27 Jan 2001 22:21:41 PDT." <3A73AC65.FC9DD8C@qwest.net>
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/
next prev parent reply other threads:[~2001-01-28 5:07 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 [this message]
2001-01-28 5:13 ` Matthew Pitts
2001-01-28 5:29 ` Keith Owens
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=4504.980658417@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=anawaltaj@qwest.net \
--cc=linux-kernel@vger.kernel.org \
/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