linux-kernel - Re: [PATCH] Add a personality to report 2.6.x version numbers

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: <alpine.LNX.2.00.1108220033240.8284@swampdragon.chaosbits.net>
Date:	Mon, 22 Aug 2011 00:37:05 +0200 (CEST)
From:	Jesper Juhl <jj@...osbits.net>
To:	Arnaud Lacombe <lacombar@...il.com>
cc:	Andi Kleen <andi@...stfloor.org>, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH] Add a personality to report 2.6.x version numbers

On Sun, 21 Aug 2011, Arnaud Lacombe wrote:

> Hi,
> 
> On Fri, Aug 19, 2011 at 7:15 PM, Andi Kleen <andi@...stfloor.org> wrote:
> > From: Andi Kleen <ak@...ux.intel.com>
> >
> > Reposting due to popular demand. Several other people are running
> > into the same problem with all kinds of software.
> >
> > Only change is rebase against current master.
> >
> FWIW, couldn't this be made a boot option ?
> 
> That might help some distros, say Fedora, who actually ships
> 2.6.40+x-branded kernels, or allow people to use no longer supported
> distros with recent kernels.
> 
> About this last point, once functional, I intend to upgrade my trixbox
> install (based on 2.6.18) to a 3.x-ish kernel, that might be fun...
> 

Just a random thought.
Since this is purely to be backwards compatible with binary only software 
that makes bad assumptions about the kernel version (as far as I can 
tell at least), shouldn't we make it explicit from the beginning that this 
will have a limited life time by adding it to 
Documentation/feature-removal-schedule.txt with a removal date at 
somewhere soon(ish) like 3.6 (or something) at day one?
I can't imaging we'd want to support something like this forever going 
forward... or..?

-- 
Jesper Juhl <jj@...osbits.net>       http://www.chaosbits.net/
Don't top-post http://www.catb.org/jargon/html/T/top-post.html
Plain text mails only, please.

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