From: david@lang.hm
To: Richard Yao <ryao@ic.sunysb.edu>
Cc: Theodore Tso <tytso@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: UNIX Compatibility
Date: Tue, 24 May 2011 11:23:34 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1105241116190.23692@asgard.lang.hm> (raw)
In-Reply-To: <BANLkTi=q7tDVkahrnng7+BJhvxh=gx71ng@mail.gmail.com>
On Tue, 24 May 2011, Richard Yao wrote:
> With that out of the way, I am under the impression that the Linux
> kernel code is in some way incompatible with the Single Unix
> Specification (i.e. the thing required for an OS to be certified as
> being UNIX).
I beleive it's less a matter of being incompatible and more a matter of
not having been certified as being compatible.
a historic note: at the time that Linux was getting started, getting
certified as Unix was a very expensive undertaking (and Linux definantly
did not comply in the early days anyway). Even getting the full specs was
an expensive thing (at least for an individual)
as such, there are probably some differences that crept in (like the error
codes you refer to below), but the biggest difference is that there are
additional system calls available on Linux compared to Unix
That being said, the differences are minor enough that many flavors of
Unix have implemented Linxu compatibility layers to support unmodified
linux binarires, and recompiling code written for Unix almost always 'just
works' on Linux (the biggest issue is usually libraries)
> It seems Linus Torvalds wanted to use the UNIX System V call codes
> when he was working on Linux 0.0.1, but he lacked a reference at the
> time, so he only got them partially right. Considering that the error
> codes were originally intended to be compatible with UNIX System V, it
> might be worth changing them to match. The Linux 3.0 change would
> probably be a good time for this.
and what exactly would the advantage be of breaking backwards
compatibility with all existing linux code?
I don't see any real advantage.
David Lang
prev parent reply other threads:[~2011-05-24 18:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 11:49 Richard Yao
2011-05-24 13:06 ` Theodore Tso
2011-05-24 13:54 ` Michael Witten
2011-05-24 14:49 ` Richard Yao
2011-05-24 18:16 ` Ted Ts'o
2011-05-24 18:31 ` Michael Witten
2011-05-25 4:18 ` Mike Galbraith
2011-05-25 14:20 ` Michael Witten
2011-05-25 14:36 ` Ted Ts'o
2011-05-25 15:17 ` Michael Witten
2011-05-25 17:38 ` Ted Ts'o
2011-05-25 20:33 ` Casey Schaufler
2011-05-26 11:30 ` Bernd Petrovitsch
2011-05-26 11:30 ` Bernd Petrovitsch
2011-05-26 12:07 ` Valdis.Kletnieks
2011-05-26 12:24 ` Bernd Petrovitsch
2011-05-26 13:35 ` Ted Ts'o
2011-05-25 21:06 ` Valdis.Kletnieks
2011-05-25 14:38 ` Ted Ts'o
2011-05-25 15:17 ` Mike Galbraith
2011-05-25 15:21 ` Michael Witten
2011-05-24 18:23 ` david [this message]
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=alpine.DEB.2.02.1105241116190.23692@asgard.lang.hm \
--to=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=ryao@ic.sunysb.edu \
--cc=tytso@mit.edu \
/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®