linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <20100812233837.GG22777@mail.oracle.com>
Date:	Thu, 12 Aug 2010 16:38:37 -0700
From:	Joel Becker <Joel.Becker@...cle.com>
To:	Sam Ravnborg <sam@...nborg.org>, linux-kernel@...r.kernel.org
Subject: Cloning arch-independant KConfig

Sam,
	I guess this is either a feature request or just wondering
whether KConfig supports this idea.
	Often I have a wonderful minimal .config that builds a test
kernel.  It only compiles the things I want in my kernel and modules,
nothing more.  Usually I start from a distro kernel and then keep
turning things off until I reach some minimum.
	However, when I get a new machine of a different architecture, I
can't bring that work forward.  If I take this .config to that arch, the
oldconfig just breaks.  I don't get good defaults for the arch-specific
stuff.  Conversely, if I start from a distro .config for the new arch, I
have to repeat all the whittle-down work.
	Is there any way to "extract" the non-arch-specific config
values?  Essentially, all the "use USB, build ext3, give me these
network cards" fields should be kept, but I want to start from a default
architecture config.

Joel

-- 

"Friends may come and go, but enemies accumulate." 
        - Thomas Jones

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/