linux-kernel - Re: + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree

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

Message-Id: <200610021123.k92BNQRn013051@harpo.it.uu.se>
Date:	Mon, 2 Oct 2006 13:23:26 +0200 (MEST)
From:	Mikael Pettersson <mikpe@...uu.se>
To:	galibert@...ox.com, mikpe@...uu.se
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org, rdunlap@...otime.net,
	rossb@...gle.com, sam@...nborg.org
Subject: Re: + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree

On Mon, 2 Oct 2006 12:42:09 +0200, Olivier Galibert wrote:
> On Mon, Oct 02, 2006 at 09:08:08AM +0200, Mikael Pettersson wrote:
> > All that's needed is to standardise the location of the
> > config file; /lib/modules/`uname -r`/config.gz seems a
> > reasonable choice.
> 
> It's already /boot/config-`uname -r`, why change?

I just wanted to show that the instant /proc/config.gz gets implemented
as a loadable module, it no longer needs to be in the kernel at all,
and in the heat of the moment I forgot about the /boot/config-`uname -r`
convention. I am certainly not suggesting that that convention should be changed.

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