linux-kernel - Re: UNS: Re: [PATCH] kconfig: add *_silentdefconfig feature for config targets

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: <20071022150015.72d9ebef@ephemeral>
Date:	Mon, 22 Oct 2007 15:00:15 -0400
From:	Andres Salomon <dilinger@...ued.net>
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	kbuild-devel@...ts.sourceforge.net, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: UNS: Re: [PATCH] kconfig: add *_silentdefconfig feature for
 config targets

On Tue, 21 Aug 2007 18:21:55 +0200 (CEST)
Roman Zippel <zippel@...ux-m68k.org> wrote:

> Hi,
> 
> On Tue, 21 Aug 2007, Andres Salomon wrote:
> 
> > > I would really like to avoid another input mode.
> > > I think it be better to implement this as a combination of "-s -D 
> > > <default>" and the silent mode is adjusted to read another config
> > > instead of .config if defconfig_file is set.
> > > 
> > 
> > As would I; however, that requires using getopt() (or equivalent).
> > I wasn't sure if there was some opposition to this..
> 
> I'm not sure how getopt() would change much (besides changing the
> "if" to a "while"), but I don't really mind either way.
> 

It would allow more flexibilty; being able to specify multiple
arguments, for example.  Unfortunately, I haven't had much time to work
on this, but I did do the getopt patch.  Since it's been sitting on my
drive for a while, I should probably send it out before I lose it.  :)
-
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/