From: Greg KH <greg@kroah.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] Add a personality to report 2.6.x version numbers
Date: Fri, 26 Aug 2011 14:43:29 -0700 [thread overview]
Message-ID: <20110826214329.GA6325@kroah.com> (raw)
In-Reply-To: <1313795710-30827-1-git-send-email-andi@firstfloor.org>
On Fri, Aug 19, 2011 at 04:15:10PM -0700, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.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.
>
> -Andi
>
> --
>
> I ran into a couple of programs which broke with the new Linux 3.0 version.
> Some of those were binary only. I tried to use LD_PRELOAD to work
> around it, but it was quite difficult and in one case impossible
> because of a mix of 32bit and 64bit executables.
>
> This patch adds a UNAME26 personality that makes the kernel
> report a 2.6.40+x version number instead. The x is the x in 3.x.
>
> I know this is somewhat ugly, but I didn't find a better workaround,
> and compatibility to existing programs is important.
>
> Some programs also read /proc/sys/kernel/osrelease. This can be worked
> around in user space with mount --bind (and a mount namespace)
>
> To use:
>
> wget ftp://ftp.kernel.org/pub/linux/kernel/people/ak/uname26/uname26.c
> gcc -o uname26 uname26.c
> ./uname26 program
I hate to ask, but can you put a proper copyright and license on this
file so that distros can distribute it?
thanks,
greg k-h
next prev parent reply other threads:[~2011-08-26 21:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 23:15 [PATCH] Add a personality to report 2.6.x version numbers Andi Kleen
2011-08-21 22:28 ` Arnaud Lacombe
2011-08-21 22:37 ` Jesper Juhl
2011-08-21 23:15 ` Andi Kleen
2011-08-21 23:13 ` Andi Kleen
2011-08-21 23:32 ` Arnaud Lacombe
2011-08-22 0:11 ` Andi Kleen
2011-08-22 1:04 ` Arnaud Lacombe
2011-08-22 1:46 ` Andi Kleen
2011-08-22 9:54 ` Américo Wang
2011-08-22 18:30 ` Linus Torvalds
2011-08-22 18:45 ` Eric Dumazet
2011-08-22 19:03 ` David Daney
2011-08-22 19:34 ` Andi Kleen
2011-08-23 13:15 ` Colin Walters
2011-08-23 16:11 ` Andi Kleen
2011-08-23 16:20 ` Colin Walters
2011-08-23 17:35 ` Arnaud Lacombe
2011-08-24 14:19 ` Alexey Dobriyan
2011-08-24 17:02 ` Arnd Bergmann
2011-09-13 14:12 ` Pavel Machek
2011-09-13 14:36 ` Stratos Psomadakis
2011-09-13 15:50 ` Andi Kleen
2011-09-13 23:06 ` Stratos Psomadakis
2011-08-23 6:00 ` [PATCH] setarch: Add --uname-2.6 option for personality flag UNAME26 Ben Hutchings
2011-08-23 10:16 ` Karel Zak
2011-08-23 12:15 ` Ben Hutchings
2011-08-26 21:43 ` Greg KH
2011-08-29 9:17 ` Karel Zak
2011-08-23 12:44 ` [PATCH] Add a personality to report 2.6.x version numbers Arnd Bergmann
2011-08-26 21:43 ` Greg KH [this message]
2011-08-26 22:25 ` Andi Kleen
2011-08-26 22:35 ` Greg KH
2011-08-27 16:36 ` Jesper Juhl
-- strict thread matches above, loose matches on Subject: below --
2011-07-07 23:42 Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110826214329.GA6325@kroah.com \
--to=greg@kroah.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox