All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: "Ted Ts'o" <tytso@mit.edu>
Cc: Michael Witten <mfwitten@gmail.com>,
	Mike Galbraith <efault@gmx.de>, Richard Yao <ryao@ic.sunysb.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: UNIX Compatibility
Date: Wed, 25 May 2011 17:06:12 -0400	[thread overview]
Message-ID: <25621.1306357572@localhost> (raw)
In-Reply-To: Your message of "Wed, 25 May 2011 10:36:02 EDT." <20110525143602.GE8476@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]

On Wed, 25 May 2011 10:36:02 EDT, "Ted Ts'o" said:

> And of course, the supreme irony is that if your OS is encumbered with
> AT&T copyrighted code, you can use the Unix trademark even if you are
> not conformant to the Single Unix Specification.  (There's an escape
> clause for AT&T derived-Unix systems, which are automatically "Unix"
> even if they fail the SUS.)
> 
> Given all of that, what _use_ is the Single Unix Specification at this
> point?  What's the _point_?

We're pretty shameless in mugging other operating systems for good new ideas
(witness the recent patches stealing SEEK_HOLE and SEEK_DATA from Solaris), but
most of the time, the neat stuff like that isn't part of SUS anyhow, because only
one or two Unix-derived systems implemented the function.

Single most useful thing left in SUS?  The few places we're *really* divergent from SUS,
we can usually go back and read the SUS spec for the function in question and remind
ourself that yes, we diverged for a reason - the spec was on total crack. :)


[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2011-05-25 21:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 11:49 UNIX Compatibility 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 [this message]
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=25621.1306357572@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfwitten@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.