From: Keith Owens <kaos@ocs.com.au>
To: Torrey Hoffman <torrey.hoffman@myrio.com>
Cc: Matthew Pitts <mpitts@suite224.net>,
Jacob Anawalt <anawaltaj@qwest.net>,
linux-kernel@vger.kernel.org
Subject: Re: Knowing what options a kernel was compiled with
Date: Tue, 30 Jan 2001 12:00:16 +1100 [thread overview]
Message-ID: <26703.980816416@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 29 Jan 2001 12:41:31 -0800." <4461B4112BDB2A4FB5635DE1995874320223F3@mail0.myrio.com>
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/
next prev parent reply other threads:[~2001-01-30 1:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 20:41 Knowing what options a kernel was compiled with Torrey Hoffman
2001-01-29 20:56 ` mirabilos
2001-01-29 21:01 ` Ville Herva
2001-01-30 1:00 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-28 5:21 Jacob Anawalt
2001-01-28 5:06 ` Keith Owens
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
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=26703.980816416@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=anawaltaj@qwest.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpitts@suite224.net \
--cc=torrey.hoffman@myrio.com \
/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