linux-kernel - Re: mismatch between default and defconfig LOG_BUF

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

Message-ID: <Pine.LNX.4.64.0611280554430.15533@localhost.localdomain>
Date:	Tue, 28 Nov 2006 05:55:42 -0500 (EST)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Arjan van de Ven <arjan@...radead.org>
cc:	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: mismatch between default and defconfig LOG_BUF_SHIFT values

On Tue, 28 Nov 2006, Arjan van de Ven wrote:

> > ...
> >
> >   is it worth trying to bring the Kconfig.debug default values into
> > line with the defconfig file values, to avoid any possible confusion?
>
> I don't think so. defconfig is just there to get some working
> system. You should really pay attention to the config options you
> care about, and select the value YOU want. Neither defconfig nor the
> "default value" matter in that. Of course especially the "default
> value" should be a sane one, but it is in this case.. your system
> boots and works fine.
>
> defconfig also tends to be the config used by the arch maintainer,
> eg the one he uses for his system. He might very well have different
> preferences than you have...

fair enough.  i didn't *think* there was any technical reason why
those values had to match, i just thought i'd ask.

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