linux-kernel - Re: 2.6.22.7 autoconf.h is screwed up

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 24 Sep 2007 13:57:49 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Jaswinder Singh <jaswinderlinux@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.22.7 autoconf.h is screwed up

On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote:
> Hi all,
> 
> 2.6.22.7's include/linux/autoconf.h is completely screwed up as
> compare to 2.6.10's autoconf.h .
> 
> 2.6.22.7 totally changed the meaning of autoconf.h

autoconf.h has always been autogenerated. And autoconf.h has always
been used to publish the configuration to .c files.

What changed between 2.6.10 and 26.22 are the algorithm used to
produce autoconf.h.
The interface to the kernel configuration is .config - and overwriting
.config is an easy way to introduce a new config.
autoconf.h is not suitable for this purpose and thus
the actual layout does not matter.

If you used to use autoconf.h for distributing kernel versions before
I recommend you to use .config for now on. This should to my best
knowlege also work for your 2.6.10 kernel.

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