linux-kernel - Re: Cloning arch-independant KConfig

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100813013059.GJ22777@mail.oracle.com>
Date:	Thu, 12 Aug 2010 18:30:59 -0700
From:	Joel Becker <Joel.Becker@...cle.com>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Cloning arch-independant KConfig

On Fri, Aug 13, 2010 at 03:20:52AM +0200, Sam Ravnborg wrote:
> Today there are a few ways you can do so already.
> Say that you have saved away the known good one as "good", which is
> a direct copy of your .config.
> 
> Then you can do for example:
> KCONFIG_ALLCONFIG=good make alldefconfig
> 
> This will produce a config wich is almost equal to what you had before,
> and with defaults for all new stuff.
> I tested it where I used a sparc defconfig as input to a i386
> config and it just worked.

	That seems pretty reasonable.

> cat .config good > new
> mv new .config
> make menuconfig
> 
> This will trigger a lot of override warnings - which you just ignore.
> Resulting config is then mostly from "good".

	The problem with this, which I've definitely done before, is I
never know what paths in menuconfig to look down.  The alldefconfig
choice seems saner because it provides a dirt-simple CPU setup.

Joel

-- 

"Can any of you seriously say the Bill of Rights could get through
 Congress today?  It wouldn't even get out of committee."
	- F. Lee Bailey

Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker@...cle.com
Phone: (650) 506-8127
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/