The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: kevin.bowling@kev009.com
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] cat -v and other complaints
Date: Thu, 30 Aug 2018 12:59:07 +1000	[thread overview]
Message-ID: <CAKr6gn3LUB5rxMrj5p8ko1ZUJypaYHybEUuZBJJkfzNJHsyJFA@mail.gmail.com> (raw)
In-Reply-To: <CAK7dMtDgkkkP1kGbGRt48ON1BrMkN2GSsi8bfe=EeOGT3O8esw@mail.gmail.com>

if you staid inside the reservation (so to speak) I think AIX made
huge sense. I ran the BSD/RT stuff, it was very fine. The
documentation was rigorous. If you stuck to the docs, you couldn't go
wrong. But it was a frozen moment in time and as X10/X11 moved on, the
RT port got older and older.

the uni I worked at had a dying IBM mainframe. I think if we'd
committed more to the IBM model and dived in, AIX would have worked
well. But psych, compsci, engineering, arts/liberal-arts all went to
Suns and the computer centre (where I was) had been DEC10/Vax as well
as IBM)

We were half-pregnant. Its a difficult state to be in.

I don't really want to knock AIX, I think compared to the choices HPUX
made, or Apollo Domain/OS made, the AIX choices were more self
consistent. The unit I ran briefly in the research centre was rock
solid and most of my complaints are 'principle of least surprise
broken' coming from non-AIX world. I think if you were in it, it was
fine.

But really, thats the same thing about Solaris. I personally preferred
SunOS but the company backed this other model, and if you were in it,
the kickstart mechanism to do canned machine deployment, and disk
config, and all that goodness, It was fine. I jumped ship well before
Sun moved into the 'mainframe' world but I knew people who ran huge
non-stop high transactional services on the E1000 series, and were
very very happy.

Tandem (to riff on that) had its niche. I love the story about sales
engineers in the east coast pulling cards on the demo machine to show
"look it works" live and the West coast maintenance people tearing
their hair out at automatic supply-chain logistics shipping parts over
to fix the borked node.. (this is an Aussie story) But I never had to
handle the OS.

SCO, I did have to work on. As long as you stayed inside the
reservation.. No I can't go there. SCO was just awful.

  reply	other threads:[~2018-08-30  2:59 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 14:25 Clem Cole
2018-08-29 22:34 ` Dave Horsfall
2018-08-29 23:36   ` Larry McVoy
2018-08-30  1:14     ` Clem cole
2018-08-30  1:15       ` Clem cole
2018-08-30  2:43       ` Kevin Bowling
2018-08-30  2:59         ` George Michaelson [this message]
2018-08-31  0:27         ` Dave Horsfall
2018-08-31  0:41           ` Dan Cross
2018-08-31  1:58             ` Larry McVoy
2018-08-31 11:38           ` ron
2018-08-31 14:41           ` [TUHS] UNIX System names - since UNIX was a Trademark Clem Cole
2018-08-31 15:13             ` Eric Wayte
2018-08-31 15:17             ` William Pechter
2018-08-31 15:25               ` Clem Cole
2018-09-01  0:10               ` John P. Linderman
2018-09-01  0:18                 ` ron
2018-09-01  0:55                   ` Nemo
2018-09-01  7:37                     ` Dave Horsfall
2018-09-01 13:54                       ` Nemo
2018-09-01 17:03                       ` Paul Winalski
2018-09-03  1:14                         ` Robert Brockway
2018-09-30 20:57                 ` Lyndon Nerenberg
2018-10-01 16:26                   ` Paul Winalski
2018-09-01  0:00             ` Dave Horsfall
2018-08-31 21:56 ` [TUHS] cat -v and other complaints Cág
2018-09-01  3:37   ` Andrew Warkentin
2018-09-03 18:04     ` Cág
2018-09-03 18:11       ` Kurt H Maier
2018-09-03 18:56         ` Cág
2018-09-04  6:10           ` Andy Kosela
2018-09-04  6:41             ` ron minnich
2018-09-04  9:34               ` Andy Kosela
2018-09-04 10:23                 ` Dan Cross
2018-09-04 14:22                 ` ron minnich
2018-09-06 20:02                   ` Andy Kosela
2018-09-06 20:49                     ` ron minnich
2018-09-06 21:55                       ` Andy Kosela
2018-09-07  1:59                         ` Dan Cross
2018-09-07  4:40                           ` Andy Kosela
2018-09-30 21:32           ` Lyndon Nerenberg
2018-09-03 20:08         ` Bakul Shah
2018-09-03 20:41           ` Kurt H Maier
2018-09-03 21:46             ` Bakul Shah
2018-09-04  0:52               ` Kurt H Maier
2018-09-06 20:29 Norman Wilson
2018-09-06 22:16 ` Andy Kosela
2018-09-08 12:02 [TUHS] [TUHS} " Doug McIlroy
2018-09-08 13:36 ` Will Senn
2018-09-08 14:22   ` [TUHS] " Ralph Corderoy
2018-09-08 16:10     ` Arthur Krewat

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=CAKr6gn3LUB5rxMrj5p8ko1ZUJypaYHybEUuZBJJkfzNJHsyJFA@mail.gmail.com \
    --to=ggm@algebras.org \
    --cc=kevin.bowling@kev009.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).