mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Hards <bhards@bigpond.net.au>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: kernel ABI [was something about Compile Bogons...]
Date: Thu, 25 Jul 2002 18:23:55 +1000	[thread overview]
Message-ID: <200207251823.55466.bhards@bigpond.net.au> (raw)
In-Reply-To: <20020725085702.C7336@flint.arm.linux.org.uk>

On Thu, 25 Jul 2002 17:57, Russell King wrote:
> On Thu, Jul 25, 2002 at 02:32:52PM +1000, Brad Hards wrote:
> > Some applications talk to the kernel (eg via ioctl()). This is related to
> > the kernel version that is running (not anything to do with the libs).
>
> And ioctl() is an evil interface, and anything which changes in an
> already defined ioctl is an ABI change, which aren't allowed in stable
> kernel series.
ioctl() is a damn evil interface that we are stuck with.
Changing an already defined ioctl isn't a sufficient condition.
If you have a program that is testing for a certain kernel
capability (ioctl, socket, whatever), and it is present in the
headers, then it needs to be present in the kernel that the
program will run under. So you can't add anything to the
ABI (as described by the headers) in a stable series either.

> > 3. Things that are related to the kernel that is running.
> > This is probably /usr/include/linux
>
> No.  Search the lkml archives.  You'll find several people, including
> Linus telling people otherwise.
I didn't express it well. My point is that the include files should be
refactored to provide only the kernel ABI in /usr/include/linux.
If it isn't part of the kernel ABI, then it isn't strictly part of Linux,
and the naming should support that.

Then /usr/include/linux (or linux-abi, whatever) really _should_ be
a symlink to the currently running kernel headers describing the
ABI.

But certainly not the way it is now, where symlinking /usr/include/linux
to /usr/src/kernels/linux-2.x.y.z-rcA/include is the path to madness.


-- 
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.

  reply	other threads:[~2002-07-25  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24  8:29 Compile Bogons in 2.4.19-rc3 with Caldera OpenLinux 3.1's patched 2.95.2 D.A.M. Revok
     [not found] ` <20020724084749.GC15043@dreams.soze.net>
2002-07-24  9:03   ` D.A.M. Revok
2002-07-24  9:16     ` Russell King
2002-07-24  9:23       ` D.A.M. Revok
     [not found]       ` <E17XIMe-0001kA-00@caramon.arm.linux.org.uk>
2002-07-24  9:26         ` Russell King
2002-07-25  4:32       ` Brad Hards
2002-07-25  7:57         ` Russell King
2002-07-25  8:23           ` Brad Hards [this message]
2002-07-24  9:31 ` Alex Riesen

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=200207251823.55466.bhards@bigpond.net.au \
    --to=bhards@bigpond.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®