linux-kernel - Re: [PATCH] Add ``cloneconfig'' target

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

Message-ID: <AANLkTi=+AU3gJJOov8R1fNcZVE7iNpbTLDuMB5PHUk8s@mail.gmail.com>
Date:	Sat, 26 Feb 2011 18:03:13 -0500
From:	Arnaud Lacombe <lacombar@...il.com>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Jeff Mahoney <jeffm@...e.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Roman Zippel <zippel@...ux-m68k.org>,
	linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] Add ``cloneconfig'' target

Hi,

On Sat, Feb 26, 2011 at 5:18 PM, Sam Ravnborg <sam@...nborg.org> wrote:
> On Sat, Feb 26, 2011 at 02:47:01PM -0500, Arnaud Lacombe wrote:
>> Hi,
>>
>> On Fri, Feb 25, 2011 at 1:07 AM, Sam Ravnborg <sam@...nborg.org> wrote:
>> > We already have something remotely similar in kconfig.
>> > We use the following list:
>> > config DEFCONFIG_LIST
>> >        string
>> >        depends on !UML
>> >        option defconfig_list
>> >        default "/lib/modules/$UNAME_RELEASE/.config"
>> >        default "/etc/kernel-config"
>> >        default "/boot/config-$UNAME_RELEASE"
>> >        default "$ARCH_DEFCONFIG"
>> >        default "arch/$ARCH/defconfig"
>> >
>> I may argue that anything within the Linux tree which point
>> _by_default_ to something outside the tree itself is broken.
> The above allows the average user to just type "make menuconfig"
> and then the configuration of the current kernel is presented to
> the user.
I'm sure there is a way to do this from the Kbuild and not from the Kconfig.

> This is convinient in many cases.
this is a subjective point of view. I do build a lot of kernel for
anything but the current machine I'm using.

> We know the /proc/config.gz is an incresingly popular way to gain
> access to the configuration of the running kernel. So extending
> the already know and working way to obtaing the configuration
> of the running kernel to suppport /proc/config.gz is logical.
Then again, this should be doable from Kbuild.

> The fact that the configuration is gzipped does not warrant
> a new option to deal with this that almost duplicate the
> existing functionality.
>
agree.

 - Arnaud
--
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/