linux-kernel - Re: Heads-up: Linux make menuconfig .config vs. XDG_CONFIG_HOME ~/.config/ clash

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]

Date:	Fri, 03 Jun 2011 10:25:46 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Andreas Mohr <andi@...as.de>
Cc:	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
	Roman Zippel <zippel@...ux-m68k.org>,
	Waldo Bastian <bastian@....org>, Ryan Lortie <desrt@...rt.ca>,
	Lennart Poettering <lennart@...ttering.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Heads-up: Linux make menuconfig .config vs. XDG_CONFIG_HOME ~/.config/
 clash - perhaps resolve it while 3.0 appears?

On 2.6.2011 20:24, Andreas Mohr wrote:
> I just discovered a Linux kernel make menuconfig .config file
> accidentally situated in the home directory of a shell account
 > [...]
> "$XDG_CONFIG_HOME defines the base directory relative to which user
> specific configuration files should be stored. If $XDG_CONFIG_HOME is
> either not set or empty, a default equal to $HOME/.config should be
> used."

PEBKAC :-). BTW, did you really run into such problem yourself, or is it 
more a "what if"?


> It may thus be strongly advisable to rename the default name of the
> make menuconfig kernel .config file (perhaps .config_lx / .config_linux ?)
> to completely sidestep such a (mostly user-triggered)
> problematic clash in future.

No. The name ".config" is documented in the linux source as well as so 
many howtos and books, that we should not change it just for the fun of 
it. Arguably, a non-dot filename might have been a better choice, but 
".config" has been chosen, so we have to live with it.


> And (I cannot help but think of this) now that lx 3.0 is in -rc
> this might still be an especially appropriate moment to do it ;)

Linus made it clear that 3.0 is just a change in versioning, not an 
excuse for doing incompatible changes. (Incompatible changes can 
possibly happen in any release, but they need to be justified and need 
to be ready *before* -rc1.)

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