| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 24 May 2011 13:54:31 +0000 From: Michael Witten <mfwitten@...il.com> To: Theodore Tso <tytso@....edu> Cc: Richard Yao <ryao@...sunysb.edu>, linux-kernel@...r.kernel.org Subject: Re: UNIX Compatibility On Tue, May 24, 2011 at 13:06, Theodore Tso <tytso@....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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists