linux-kernel - Re: rfc: nonint

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]

Date:	Wed,  5 Mar 2008 17:37:22 -0800 (PST)
From:	Roland McGrath <roland@...hat.com>
To:	Dave Jones <davej@...emonkey.org.uk>
Cc:	sam@...nborg.org, Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: rfc: nonint_oldconfig

> There's also an additional target that does the same, but
> ignores any options defined in the local configs that the kernel
> being configured doesn't know about.

I added this one (loose_nonint_oldconfig target, -B option to conf).
It is the noninteractive equivalent of taking your old .config after a
source upgrade, running 'make oldconfig' and hitting return a lot.
(If options from your old .config went away, you get harmless warnings.
If new options appeared, you get the defaults for those.)
That's what I do in my hand builds after a git pull (hit return a lot).

The benefit of 'make loose_nonint_oldconfig' is it lets me do the same
thing with scripted rpm builds made from fresh git snapshot code.  These
builds use a .config chosen for the Fedora production kernel, but a new
code snapshot (sometimes with and sometimes without the Fedora patches to
the kernel).  The Fedora patches sometimes add nonstandard config options,
and the bleeding edge kernel snapshot I try sometimes had added new config
options that Fedora's kernel configs do not yet set or clear explicitly.

For development, it is very handy to just get a build that approximates the
Fedora config for the stable kernel but uses the latest development kernel
source.  99% of the time the default for new options works fine for my
purposes.  When a new kernel is imported for proper Fedora builds, then
we'll update the standard configs with tested settings for the new source.
Having to tweak those every time I want to spin a testing kernel rpm would
be a waste.

Thanks,
Roland
--
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/