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: <20150710134140.GA27233@amd>
Date:	Fri, 10 Jul 2015 15:41:41 +0200
From:	Pavel Machek <pavel@....cz>
To:	John Stoffel <john@...ffel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Andy Lutomirski <luto@...nel.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Kees Cook <keescook@...omium.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Borislav Petkov <bp@...en8.de>,
	Austin S Hemmelgarn <ahferroin7@...il.com>,
	Brian Gerst <brgerst@...il.com>,
	Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: [PATCH] x86/kconfig/32: Make CONFIG_VM86 default to n and remove
 EXPERT

On Thu 2015-07-09 15:42:27, John Stoffel wrote:
> >>>>> "Linus" == Linus Torvalds <torvalds@...ux-foundation.org> writes:
> 
> Linus> On Thu, Jul 9, 2015 at 11:51 AM, Arjan van de Ven <arjan@...ux.intel.com> wrote:
> >> 
> >> I would rather do BOTH the default n AND the EXPERT
> 
> Linus> That basically makes it impossible for "normal people" to test it. You
> Linus> have to mark yourself as expert, and then get the rest of the
> Linus> configuration right. Not a good idea.
> 
> Linus> The kernel config is probably our biggest problem for getting
> Linus> people to test. Building the kernel? Easy. Installing it? "make
> Linus> install; make modules_install". Not that hard, unless your
> Linus> distro has screwed it up (which has happened, I'm looking at
> Linus> you, Ubuntu).
> 
> The big problem with the kernel config is the piles and piles of crap
> which makes finding the common cases really really hard, and I've been
> following this list and building kernels off and on now for 12+
> years.

And you are lucky not to work on embedded stuff.

If I lost configs for n900, I'd probably not be able to come with
something working...

Given that we already have device trees... it would be nice to
separate real config *options* (like do you want penguin logo on
console? How big font?) from options you need to get right to get
useful hardware configuration, and parse the later ones from dts..

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ