public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Why did oldconfig's behavior change in 2.6.15-rc1?
Date: Sat, 12 Nov 2005 17:31:25 -0600	[thread overview]
Message-ID: <200511121731.25982.rob@landley.net> (raw)
In-Reply-To: <200511121656.29445.rob@landley.net>

On Saturday 12 November 2005 16:56, Rob Landley wrote:
> Linus says if we're going to test something, test -rc1, so I did.
>
> It went boing.
>
> I'm still trying to get -skas0 working on x86-64, but this was a standard
> x86 build...
>
> Rob

Very, very strange:

> make ARCH=um allnoconfig
> cat >> .config << EOF
CONFIG_MODE_SKAS=y
CONFIG_BINFMT_ELF=y
CONFIG_HOSTFS=y
CONFIG_SYSCTL=y
CONFIG_STDERR_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_UBD=y
CONFIG_TMPFS=y
CONFIG_SWAP=y
CONFIG_LBD=y
CONFIG_EXT2_FS=y
CONFIG_PROC_FS=y
EOF
> make ARCH=um oldconfig
> grep SKAS .config
# CONFIG_MODE_SKAS is not set

Why did oldconfig switch off CONFIG_MODE_SKAS?  It didn't do that before.  
Hmmm...  Rummage, rummage...  Darn it, it's position dependent.  _And_ 
version dependent.

Ok, now I have to put the new entries at the _beginning_.  Appending them 
doesn't work anymore, it now ignores any symbol it's already seen, so you 
can't easily start with allnoconfig, switch on just what you want, and expect 
oldconfig to do anything intelligent.

That kinda sucks.  Oh well, I can have sed rip out the old symbols before I 
append the new ones.  Here's hoping it's not _that_ position dependent...

Rob

       reply	other threads:[~2005-11-12 23:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200511121656.29445.rob@landley.net>
2005-11-12 23:31 ` Rob Landley [this message]
2005-11-12 23:41   ` Why did oldconfig's behavior change in 2.6.15-rc1? Sam Ravnborg
2005-11-12 23:49   ` Roman Zippel
2005-11-13  0:50     ` [uml-devel] " Rob Landley

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=200511121731.25982.rob@landley.net \
    --to=rob@landley.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.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