From: "mirabilos" <eccesys@topmail.de>
To: "Torrey Hoffman" <torrey.hoffman@myrio.com>,
"'Keith Owens'" <kaos@ocs.com.au>,
"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: Mon, 29 Jan 2001 20:56:12 -0000 [thread overview]
Message-ID: <032601c08a36$0c8d5570$0100a8c0@homeip.net> (raw)
In-Reply-To: <4461B4112BDB2A4FB5635DE1995874320223F3@mail0.myrio.com>
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/
next prev parent reply other threads:[~2001-01-29 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 20:41 Torrey Hoffman
2001-01-29 20:56 ` mirabilos [this message]
2001-01-29 21:01 ` Ville Herva
2001-01-30 1:00 ` Keith Owens
-- 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='032601c08a36$0c8d5570$0100a8c0@homeip.net' \
--to=eccesys@topmail.de \
--cc=anawaltaj@qwest.net \
--cc=kaos@ocs.com.au \
--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
Powered by JetHome