The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Peter Weinberger (温博格) via TUHS" <tuhs@tuhs.org>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org, segaloco@protonmail.com
Subject: [TUHS] Re: Other POSIX Candidates?
Date: Tue, 6 Aug 2024 09:29:20 -0400	[thread overview]
Message-ID: <CAOUkXSrhE5WoarCXHA3PBtBj=i+-3d3h-Zrb2dSYrnpnn-5mrw@mail.gmail.com> (raw)
In-Reply-To: <202408060639.4766dk6x480855@freefriends.org>

and the folks from PARC wanted a more RPC-based open OS, according to
my not-yet-fully-retrieved memories.

On Tue, Aug 6, 2024 at 2:40 AM <arnold@skeeve.com> wrote:
>
> segaloco via TUHS <tuhs@tuhs.org> wrote:
>
> > Another way to put it would be as a chicken and egg, which came first, ...
> > ..., or the ongoing need for UNIX standardization finding sponsorship
> > by the working groups, IEEE, etc.?
>
> This.
>
> Try to understand what things were like at the time. There were
> a ton of competing Unix systems, all different:
>
> - IBM: AIX on the mainframe and PS/2, which were different from
>   AIX on the RT/PC and later RS/6000 (workstations).
>
> - DEC: Ultrix on minicomputers and microvaxen, and later on MIPS
>   based workstations
>
> - Data General: DG/UX on their minicomputers.
>
> - Pyramid: A BSD/System V hybrid RISC minicomputer
>
> - Sun: Workstations, 680x0 based and later SPARC based, and servers.
>   Initially BSD based, later SVR4 based.
>
> - Workstations from HP, Tektronix, NBI, others I've probably forgotten,
>   3B2 and 3B1/Unix PC from AT&T... The list goes on and on and on.
>
> Things split roughly along BSD/System V lines, but code wasn't portable.
> Did you use bcopy() or memcpy()? index() or strchr()? There was lots
> of mixing and matching happening, too.
>
> There was a crying need for a standard. The mess is what begot GNU
> Autoconf, which made a difference at the time. Having the ANSI C standard
> also helped.
>
> HTH,
>
> Arnold

  reply	other threads:[~2024-08-06 13:29 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 [this message]
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
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='CAOUkXSrhE5WoarCXHA3PBtBj=i+-3d3h-Zrb2dSYrnpnn-5mrw@mail.gmail.com' \
    --to=tuhs@tuhs.org \
    --cc=arnold@skeeve.com \
    --cc=pjw@google.com \
    --cc=segaloco@protonmail.com \
    /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).