From: Michael Witten <mfwitten@gmail.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Richard Yao <ryao@ic.sunysb.edu>, linux-kernel@vger.kernel.org
Subject: Re: UNIX Compatibility
Date: Tue, 24 May 2011 13:54:31 +0000 [thread overview]
Message-ID: <BANLkTimEZUSbV9wiQZvzCeztdfeMwaMJwA@mail.gmail.com> (raw)
In-Reply-To: <A7E21A2F-4338-465D-933A-66B0C4D15BE1@mit.edu>
On Tue, May 24, 2011 at 13:06, Theodore Tso <tytso@mit.edu> wrote:
>
> On May 24, 2011, at 7:49 AM, Richard Yao wrote:
>
>> I know that the system call codes used by Linux are not 100% UNIX
>> compatible. Is there anything else in the kernel that is not UNIX
>> compatible? Would modifying these things for UNIX compatibility break
>> anything in userland provided that it is recompiled against the
>> modified sources?
>
> What do you mean by "UNIX compatible?" API compatibility?
> ABI compatibility? Which Unix? Solaris and HPUX and AIX
> are systems which are allowed to use the Unix(tm) trademark,
> but them are not compatible with each other.
>
> So the question you are asking is not well defined.
>
> Also, why are you asking it? What problem are you trying to solve?
> At this point, Linux is running on far more servers than any of the
> Legacy Unix systems out there, and the ones which are still in
> development (i.e., Solaris and AIX) are have recently been worrying
> about adding Linux compatibility layers (usually at the API level).
Surely something as precarious as hegemony is nothing to boast about.
next prev parent reply other threads:[~2011-05-24 13:55 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 [this message]
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
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=BANLkTimEZUSbV9wiQZvzCeztdfeMwaMJwA@mail.gmail.com \
--to=mfwitten@gmail.com \
--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®