Subject: Re: UNIX Compatibility
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Theodore Tso <tytso@MIT.EDU>
In-Reply-To: <BANLkTin4wu1HNDeo8Rv7iddM9KkgZdhfgA@mail.gmail.com>
Date: Tue, 24 May 2011 09:06:28 -0400
Cc: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 7bit
Message-Id: <A7E21A2F-4338-465D-933A-66B0C4D15BE1@mit.edu>
References: <BANLkTin4wu1HNDeo8Rv7iddM9KkgZdhfgA@mail.gmail.com>
To: Richard Yao <ryao@ic.sunysb.edu>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1213
Lines: 29


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).

-- Ted

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/