From: David Daney <david.daney@cavium.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andi Kleen <andi@firstfloor.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: Mon, 22 Aug 2011 12:03:36 -0700 [thread overview]
Message-ID: <4E52A808.20207@cavium.com> (raw)
In-Reply-To: <1314038740.2531.8.camel@edumazet-laptop>
On 08/22/2011 11:45 AM, Eric Dumazet wrote:
> Le lundi 22 août 2011 à 11:30 -0700, Linus Torvalds a écrit :
>> On Fri, Aug 19, 2011 at 4:15 PM, Andi Kleen<andi@firstfloor.org> wrote:
>>>
>>> Reposting due to popular demand. Several other people are running
>>> into the same problem with all kinds of software.
>>
>> I have heard this several times now, but nobody actually ever says
>> *what* is broken.
>>
>> The Fedora people seem to have done the 2.6.40 thing without any
>> actual reason, for example (the two programs they claim were broken
>> were things that they had already fixed in rawhide, afaik).
>>
>> I'm not at all interested in these kinds of "all kinds of software" reports.
>>
>> Details. Examples. Name the f&*cking names already. Shame them publicly.
>
> For example, all kind of management software from HP doesnt work, unless
> we pretend to run a 2.6 kernel.
>
> $ uname -a
> Linux svivoipvnx001 3.0.0-08107-g97cd98f #1062 SMP Fri Aug 12 18:11:45
> CEST 2011 i686 i686 i386 GNU/Linux
>
> $ hpacucli ctrl all show
>
> Error: No controllers detected.
>
Perhaps the 3.x version change patch should be reverted on the
never-ever-break-userspace grounds. :-) It would appear that the 2.6
version information has become a de facto part of the kernel's ABI.
David Daney
next prev parent reply other threads:[~2011-08-22 19:03 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 [this message]
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
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=4E52A808.20207@cavium.com \
--to=david.daney@cavium.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=eric.dumazet@gmail.com \
--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