Re: [PATCH] make miniconfig (take 2)

[Rob Landley <rob@landley.net>]

On Friday 25 November 2005 16:09, Pavel Machek wrote:
> Ouch, I guess I killed my .config :-(. It seems that interrupted
> miniconfig.sh leaves .config in close to empty state...

That's why it insists you rename it in order to run it.

I intend to fix that somewhat in a newer version of the sucker by having the 
script intercept signals and restore .config on the way out, but it can't be 
fully reliable (not against kill -9) because kconfig overwrites .config and 
the script is repeatedly running allnoconfig.  (I can probably bypass the 
makefile and feed it some strange command line argument, but what Kconfig to 
run it on gets us into architecture dependence issues the make file handles 
for us...)

> I'm not sure what I did wrong last time, it worked this time. My
> miniconfig is 6K instead of 46K, good. Still its quite long. Thanks!

You mentioned you set a lot of options. :)

I agree scripts/miniconfig.sh is clumsy.  I'm thinking about improvements 
(both to how it works and to the user interface), but I need to catch up on 
some other stuff first...

>        Pavel

Rob
-- 
Steve Ballmer: Innovation!  Inigo Montoya: You keep using that word.
I do not think it means what you think it means.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/