linux-kernel - Re: 22bb1be4d27... breaks hal (and NM)

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]

Message-Id: <1216901290.13587.54.camel@johannes.berg>
Date:	Thu, 24 Jul 2008 14:08:09 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Pierre Ossman <drzeus-list@...eus.cx>,
	"John W. Linville" <linville@...driver.com>,
	Jean Tourrilhes <jt@....hp.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: 22bb1be4d27... breaks hal (and NM)

On Thu, 2008-07-24 at 13:57 +0200, Peter Zijlstra wrote:

> So you're not considering HAL as shipped by most (if not all) distros as
> anyone?
> 
> If everybody would act like that, the next kernel wouldn't even manage
> to get rudimentary user-space up and running. Like we already changed
> all those systemcalls in glibc-head, who needs this kernel to boot on
> your old stuff anyway..
> 
> Common,.. this is rediculous.

What the hell is wrong with you guys? I used to think it's accepted
practice to introduce a config option you can change away from the
default if you already know you are using new software that doesn't need
it, and if you are clueless just don't fucking touch the default until I
decide it's time to flip the default/remove the option because distros
are shipping new versions of the dependent software.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)