From: Oliver Falk <oliver@linux-kernel.at>
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org, axp-list@redhat.com,
Jay Estabrook <jay.estabrook@hp.com>,
ac-admin@lists.anotherbloody.com
Subject: Re: 2.6.23 alpha unistd.h changes
Date: Tue, 18 Sep 2007 10:47:31 +0200 [thread overview]
Message-ID: <46EF90A3.2050109@linux-kernel.at> (raw)
In-Reply-To: <20070917214107.GB27980@stusta.de>
On 09/17/2007 11:41 PM, Adrian Bunk wrote:
> On Mon, Sep 17, 2007 at 10:33:07PM +0200, Oliver Falk wrote:
>> Hi!
>
> Hi Oliver!
>
>> ...
>> As these additions are quite new to upstream kernel, but at Alphacore we
>> have patched it since a while now (I don't know about other Alpha ports;
>> Debian folks may speak up now!), I would suggest to use the same
>> 'ordering' of the syscalls upstream and add the new syscalls that we had
>> not in place, but are now upstream to the end of our 'old' list.
>> ...
>
> I just checked:
>
> It seems Debian didn't patch them into the kernel at all, and since two
> months Debian unstable ships kernel 2.6.22 with the upstream syscall
> numbers.
That's possible a problem. Right. Someone with contacts to Debian here?
If Debian hasn't rebuilt glibc against the new headers, we could change
it without problems.
If not, we have a problem on AC... Anyone with a glibc that was compiled
against our patched unistd.h (so including the new syscall numbers),
will not be able to upgrade the kernel, but also needs to upgrade glibc
and then *must* reboot :-(
Best,
Oliver
next prev parent reply other threads:[~2007-09-18 8:53 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 ` [AC-Admin] " Oliver Falk
2007-09-17 21:41 ` Adrian Bunk
2007-09-18 8:47 ` Oliver Falk [this message]
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=46EF90A3.2050109@linux-kernel.at \
--to=oliver@linux-kernel.at \
--cc=ac-admin@lists.anotherbloody.com \
--cc=axp-list@redhat.com \
--cc=bunk@kernel.org \
--cc=jay.estabrook@hp.com \
--cc=linux-kernel@vger.kernel.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