From: Oliver Falk <oliver@linux-kernel.at>
To: Sergey Tikhonov <tsv@solvo.ru>
Cc: Linux on Alpha processors <axp-list@redhat.com>,
ac-admin@lists.anotherbloody.com, Adrian Bunk <bunk@kernel.org>,
ink@jurassic.park.msu.ru, linux-kernel@vger.kernel.org,
Jay Estabrook <jay.estabrook@hp.com>
Subject: Re: [AC-Admin] Re: 2.6.23 alpha unistd.h changes
Date: Tue, 18 Sep 2007 14:20:56 +0200 [thread overview]
Message-ID: <46EFC2A8.9070009@linux-kernel.at> (raw)
In-Reply-To: <46EF962E.9010706@solvo.ru>
On 09/18/2007 11:11 AM, Sergey Tikhonov wrote:
> Oliver Falk wrote:
>> On 09/17/2007 11:22 PM, Adrian Bunk wrote:
>>
>>> On Mon, Sep 17, 2007 at 10:33:07PM +0200, Oliver Falk wrote:
>>>
>>>> At Alphacore we used to patch the kernel headers for a while now; We
>>>> added syscalls __NR_openat (447) until __NR_tee (466).
>>>>
>>> Why did your numbers differ from the numbers that were used in the
>>> upstream kernel?
>>>
>>
>> Afaik, our patch was done a while ago and nobody every submitted it
>> upstream - don't know why...
>>
> Yes, it was done by me and I had no info how to push the updates to
> upstream, sorry. (by that time,
> there were no latest "distribution" available with those changes).
>> At AC, we follow RH/Fedora packages and there we had glibc-kernheaders -
>> where our patch originates. When the glibc/kernel packages changed and
>> glibc-kernheaders died, I patched the syscalls into kernel headers; Not
>> thinking that I better submit it upstream. :-(
>>
> Yea, now there is more interest and it is better to do it right. :)
To make it easy for everyone....
There should not be many AC users that run the latest versions of
everything.
I will keep the sorting of the syscalls as they are - no change required
upstream.
People who want new kernel or new glibc will then also need to update
the other. DOT. POINT. END. :-)
Kernel 2.6.23 will also require new aboot.... So many things....
Since online upgrading from AC3 to FC8axp will not be supported anyway
(because of various reasons and now 2 more of them), I can live with
that decision finally.
Thx everyone...
Best,
Oliver
next prev parent reply other threads:[~2007-09-18 12:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 20:33 2.6.23 alpha unistd.h changes Oliver Falk
2007-09-17 20:51 ` Oliver Falk
2007-09-17 21:15 ` H. Peter Anvin
2007-09-18 8:49 ` Oliver Falk
2007-09-17 21:22 ` Adrian Bunk
2007-09-18 8:54 ` Oliver Falk
2007-09-18 9:11 ` Sergey Tikhonov
2007-09-18 12:20 ` Oliver Falk [this message]
2007-09-17 21:41 ` Adrian Bunk
2007-09-18 8:47 ` Oliver Falk
2007-09-18 14:07 ` Adrian Bunk
2007-09-18 15:44 ` Oliver Falk
2007-09-18 8:35 ` 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=46EFC2A8.9070009@linux-kernel.at \
--to=oliver@linux-kernel.at \
--cc=ac-admin@lists.anotherbloody.com \
--cc=axp-list@redhat.com \
--cc=bunk@kernel.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jay.estabrook@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tsv@solvo.ru \
/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