From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Paul Jackson <pj@sgi.com>,
kangur@polcom.net, mmazur@kernel.pl,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.3.0
Date: Mon, 08 Mar 2004 10:37:15 -0500 [thread overview]
Message-ID: <404C932B.8050307@nortelnetworks.com> (raw)
In-Reply-To: m3hdwzwfcp.fsf@defiant.pm.waw.pl
Krzysztof Halasa wrote:
> Paul Jackson <pj@sgi.com> writes:
>
>
>>>You're talking about the kernel development ...
>>>
>>No. I mean that even the C API that the kernel presents to
>>user code will sometimes change or have parts disappear.
>>
>
> And it can be caused by changing kernel config?
>
> Care to show an example?
Generally it cannot be caused by changing kernel config (although kernel
config can cause syscalls to be valid or not).
However, new kernel versions can add/remove stuff. Usually stuff isn't
removed for a while after its deprecated, but there have been instances
where stuff has been added/changed/removed during unstable kernel
development.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2004-03-08 15:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 18:42 [ANNOUNCE] linux-libc-headers 2.6.3.0 Mariusz Mazur
2004-02-29 20:19 ` H. Peter Anvin
2004-02-29 20:30 ` Mariusz Mazur
2004-02-29 21:03 ` H. Peter Anvin
2004-02-29 21:21 ` Mariusz Mazur
2004-02-29 21:33 ` Måns Rullgård
2004-03-01 14:42 ` Chris Friesen
2004-03-01 18:10 ` Krzysztof Halasa
2004-03-03 12:49 ` Måns Rullgård
2004-03-03 15:22 ` Sam Ravnborg
2004-03-03 16:49 ` Krzysztof Halasa
2004-03-04 16:50 ` Jeff Garzik
2004-03-04 18:49 ` [Linuxabi] " H. Peter Anvin
2004-03-04 4:43 ` [Linuxabi] " H. Peter Anvin
2004-03-03 18:08 ` [ANNOUNCE] " Mariusz Mazur
2004-03-03 19:20 ` Grzegorz Kulewski
2004-03-04 14:13 ` Krzysztof Halasa
2004-03-04 20:49 ` Mariusz Mazur
2004-03-04 21:27 ` Chris Friesen
2004-03-04 22:52 ` Mariusz Mazur
2004-03-04 23:32 ` Chris Friesen
2004-03-05 17:02 ` Krzysztof Halasa
2004-03-05 23:44 ` Grzegorz Kulewski
2004-03-06 22:30 ` Krzysztof Halasa
2004-03-07 1:15 ` Paul Jackson
2004-03-07 19:00 ` Krzysztof Halasa
2004-03-08 1:28 ` Paul Jackson
2004-03-08 15:03 ` Krzysztof Halasa
2004-03-08 15:37 ` Chris Friesen [this message]
2004-03-08 20:27 ` Krzysztof Halasa
2004-02-29 21:25 ` Benjamin Herrenschmidt
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=404C932B.8050307@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=kangur@polcom.net \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mmazur@kernel.pl \
--cc=pj@sgi.com \
/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