From: "Franco \"Sensei\"" <senseiwa@tin.it>
To: arjanv@redhat.com
Cc: David Lang <david.lang@digitalinsight.com>,
Krzysztof Halasa <khc@pm.waw.pl>, Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org
Subject: Re: [INFO] Kernel strict versioning
Date: Thu, 14 Apr 2005 17:33:34 -0500 [thread overview]
Message-ID: <425EEFBE.7080106@tin.it> (raw)
In-Reply-To: <1113508514.6293.82.camel@laptopd505.fenrus.org>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
Arjan van de Ven wrote:
> this is a joke right? If you really think this you have no idea what ABI
> stability means and how extremely hard it is to even sort of remotely
> approach it.
I know it's really hard, the only way of possibly having ABI is plannig
things really carefully about every single thing, so knowing every
single piece... It's freakin' hard.
> Trust me. It's *extremely* hard to impossible. Several security fixes
> can only be fixed this way. And it's REALLY fragile even if for other
> fixes. And I am very glad that the linux kernel people in general decide
> to not go for abi stability, the hacks that would be needed would be so
> obscene and the gains very very minimal. (it's open source, you have the
> source after all!)
The gains are simply a rough reuse of older modules! Just joking...
I was simply wondering how guys like beos/haiku (it's a microkernel... i
know... don't even think about starting a flame) could get ABI/API... I
mean, if it's true that they have... I don't think it's because of c++
instead of plain c...
--
Sensei <mailto:senseiwa@tin.it> <pgp:8998A2DB>
<icqnum:241572242>
<yahoo!:sensei_sen>
<msn-id:sensei_sen@hotmail.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-04-14 22:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 18:08 [INFO] Kernel strict versioning Franco "Sensei"
2005-04-08 19:05 ` Adrian Bunk
2005-04-12 1:02 ` Franco "Sensei"
2005-04-12 1:50 ` Adrian Bunk
2005-04-12 2:54 ` Franco "Sensei"
2005-04-12 11:28 ` Krzysztof Halasa
2005-04-12 17:22 ` Franco "Sensei"
2005-04-12 18:03 ` David Lang
2005-04-14 16:52 ` Franco "Sensei"
2005-04-14 17:57 ` David Lang
2005-04-14 19:41 ` Franco "Sensei"
2005-04-14 19:55 ` Arjan van de Ven
2005-04-14 22:33 ` Franco "Sensei" [this message]
2005-04-14 23:29 ` Al Viro
[not found] ` <425F33C2.8020301@tin.it>
2005-04-15 5:02 ` Al Viro
2005-04-14 20:01 ` Adrian Bunk
2005-04-14 22:51 ` Franco "Sensei"
2005-04-14 20:34 ` Horst von Brand
2005-04-14 22:45 ` Franco "Sensei"
2005-04-12 22:04 ` Krzysztof Halasa
2005-04-14 17:04 ` Franco "Sensei"
2005-04-12 22:43 ` Adrian Bunk
2005-04-14 17:40 ` Franco "Sensei"
2005-04-14 20:15 ` Adrian Bunk
2005-04-14 22:26 ` Franco "Sensei"
[not found] <3R6fp-7Qs-15@gated-at.bofh.it>
[not found] ` <3R71T-4S-15@gated-at.bofh.it>
[not found] ` <3Si4Q-Nh-21@gated-at.bofh.it>
[not found] ` <3SiRe-1eq-9@gated-at.bofh.it>
[not found] ` <3SjNh-1Yq-3@gated-at.bofh.it>
[not found] ` <3Ss48-qG-1@gated-at.bofh.it>
[not found] ` <3SxGA-5mR-29@gated-at.bofh.it>
2005-04-12 21:52 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
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=425EEFBE.7080106@tin.it \
--to=senseiwa@tin.it \
--cc=arjanv@redhat.com \
--cc=bunk@stusta.de \
--cc=david.lang@digitalinsight.com \
--cc=khc@pm.waw.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.