From: Tom H <tomh0665@gmail.com>
To: Regid Ichira <regid23@nt1.in>
Cc: Debian User <debian-user@lists.debian.org>,
debian-kernel@lists.debian.org, linux-config@vger.kernel.org
Subject: Re: linux's make oldconfig: Save in addition to [N/m/y/?], and ctrl-[C/\] to abort
Date: Wed, 11 Sep 2013 08:10:31 -0400 [thread overview]
Message-ID: <CAOdo=SzZ=PUpeJGLVs7PJ3nDO1AoGQbWAZ87H_RfNd3vo6v2oA@mail.gmail.com> (raw)
In-Reply-To: <20130910223309.GE8821@nt1.in>
On Tue, Sep 10, 2013 at 6:33 PM, Regid Ichira <regid23@nt1.in> wrote:
> On Mon, Sep 09, 2013 at 09:55:08PM -0400, John D. Hendrickson and Sara Darnell wrote:
>>
>> 2) you can run make oldconfig to get a recycled config without
>> running in text interactive mode [y/n/m]. read the directions.
>
> Do you mean the yes pipe that Tom H <tomh ... gmail.com> was
> referring to ealier in this thread? But you can not get a thoughtful
> config file by that manner. I mean, I don't want a kernel with lots
> of features I don't need. And I am trying to both config the kernel
> AND learn what new features that are of interest to me were added.
I wasn't suggesting that you use the config generated by 'yes "" |
...' only that you use it to list the new config options.
Looking at "make help", there's (now?) a "make listnewconfig" option
to do just that.
Regarding interrupting "make oldconfig", I don't see any option at the
moment except run "make menuconfig", set some options, save the
config, exit, and return to make menuconfig" later.
prev parent reply other threads:[~2013-09-11 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 10:52 linux's make oldconfig: Save in addition to [N/m/y/?], and ctrl-[C/\] to abort Regid Ichira
2013-09-07 23:55 ` Tom H
2013-09-08 1:06 ` Regid Ichira
[not found] ` <20130910223309.GE8821@nt1.in>
2013-09-11 12:10 ` Tom H [this message]
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='CAOdo=SzZ=PUpeJGLVs7PJ3nDO1AoGQbWAZ87H_RfNd3vo6v2oA@mail.gmail.com' \
--to=tomh0665@gmail.com \
--cc=debian-kernel@lists.debian.org \
--cc=debian-user@lists.debian.org \
--cc=linux-config@vger.kernel.org \
--cc=regid23@nt1.in \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).