Re: UNIX Compatibility

Ted Ts'o
2011-05-25T14:36:09Z

On Wed, May 25, 2011 at 02:20:09PM +0000, Michael Witten wrote:
>
> Ted just got finished telling Richard that Richard thinks about tiny,
> nit-picky, really stupid stuff on which only egg-headed paper pushers
> waste time that they'll never get back.

There are people who spend hours and hours worrying about the fact
that if you try to unlink a directory, Linux will return EISDIR
instead of EPERM. They will kill forests of trees, and cause tons and
tons of carbon dioxide to be released into the atmosphere travelling
to distant meetings in Singapore, Zurich, Japan, etc., to debate
standards that specify this kind of detail. How much value does this
really add to the Linux ecosystem? What would you call these people?

Now that the people who tried to lobby governments and academic
institutions (mostly in Europe) not to use Linux, all in the name of,
"because it's not Unix" are largely in full retreat, the answer is,
why, pretty much none. This kind of requirement is largely gone in
most procurement contracts.

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_?

And what name would you propose to call people who are worried about
whether or not Linux is "Unix compatible" (whatever the hell that
means)? Especially when the rest of the world is worried about being
"Linux compatible", and a huge amount of software is targetted first
for Linux.

This idea that Linux needs to care about being "Unix compatible" keeps
coming back from the grave, like some Buffy-the-vampire-slayer
monster. It's time to slay it.

- Ted