The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Kevin Bowling <kevin.bowling@kev009.com>
Cc: segaloco <segaloco@protonmail.com>, tuhs@tuhs.org
Subject: [TUHS] Re: Other POSIX Candidates?
Date: Wed, 7 Aug 2024 23:56:55 -0400	[thread overview]
Message-ID: <20240808035655.GE4511@mit.edu> (raw)
In-Reply-To: <CAK7dMtAwvuZqXXN28DxeL63xsd_zRAYJN3ft3y6JFs2eQt96ZA@mail.gmail.com>

On Wed, Aug 07, 2024 at 06:25:12PM -0700, Kevin Bowling wrote:
> 
> Relevant to Clem's point, it seems like the iBCS
> https://en.wikipedia.org/wiki/Intel_Binary_Compatibility_Standard served to
> try and provide some uniformity for ISVs providing binary software on a
> variety of x86 UNIX.  The bit it says about Linux having support is true
> too, I have some old boxed Linux distros and that is one of the features
> they advertise.

Around 1994, MIT purchased a site license for a proprietary
spreadsheet program for SCO because we knew it would work on Linux
(and we had a lot of Linux usage on campus; we had ported a good chunk
of the Project Athena infrastruture, including the Andrew File System
to Linux).

An amusing anecdote; I worked with one of their primary software
developers so we could get a custom build of the software that would
only work if the IP address of the machine was 18.X.Y.Z, since MIT had
class A network.  This person would eventually become one of the
founders of Red Hat, and I told him that we were purchasing it
intended to run it on Linux.  He told me that this would be perfectly
fine, because he had compiled the iBCS binary on Linux.  Turns out the
development environment on Linux was far more developer friendly (at
least in his eyes) than SCO, so he was building a SCO/iBCS binary on
Linux.  Since he had done his basic automated regression testing on
Linux with iBCS emulation, and only later sent the binary to do QA on
the SCO client, he was quite confident that it work just _fine_ on our
student's Linux desktops.

       	   	      	    	   - Ted

  reply	other threads:[~2024-08-08  3:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06  3:26 [TUHS] " segaloco via TUHS
2024-08-06  3:38 ` [TUHS] " George Michaelson
2024-08-06  6:39 ` arnold
2024-08-06 13:29   ` Peter Weinberger (温博格) via TUHS
2024-08-06 17:31     ` Rik Farrow
2024-08-06 18:04       ` Marc Rochkind
2024-08-06 18:09         ` arnold
2024-08-06 18:36           ` Heinz Lycklama
2024-08-06 18:45             ` segaloco via TUHS
2024-08-06 19:31               ` Clem Cole
2024-08-08  1:25                 ` Kevin Bowling
2024-08-08  3:56                   ` Theodore Ts'o [this message]
2024-08-08  8:46                     ` Marc Donner
2024-08-08 16:09                       ` Charles H Sauer (he/him)
2024-08-06 19:07           ` Paul Winalski
2024-08-06 18:18         ` Rik Farrow
2024-08-07  4:06       ` Theodore Ts'o
2024-08-07 20:56         ` Steffen Nurpmeso
2024-08-07 23:47           ` Theodore Ts'o
2024-08-09  0:53             ` Steffen Nurpmeso
2024-08-06 18:19 ` Clem Cole
2024-08-06 18:23   ` Clem Cole
2024-08-06 18:49   ` G. Branden Robinson
2024-08-06 18:55     ` Clem Cole

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=20240808035655.GE4511@mit.edu \
    --to=tytso@mit.edu \
    --cc=kevin.bowling@kev009.com \
    --cc=segaloco@protonmail.com \
    --cc=tuhs@tuhs.org \
    /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;
as well as URLs for NNTP newsgroup(s).