The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Arrigo Triulzi <arrigo@alchemistowl.org>
To: Jon Forrest <nobozo@gmail.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] The origin of /home
Date: Thu, 27 Sep 2018 17:54:51 +0200	[thread overview]
Message-ID: <309587CA-4C65-4AFA-ADFF-0E99B430D191@alchemistowl.org> (raw)
In-Reply-To: <4caca587-4945-c8be-5a35-c9f0ecfdd08b@gmail.com>

On 27 Sep 2018, at 17:36, Jon Forrest <nobozo@gmail.com> wrote:
> Right, and I am that Jon Forrest

Well, made a fool of myself there!

> It's been a while, but what I remember is that DEC actually published
> their own method for doing this but it was surprisingly cumbersome.
> What I described was incredibly simple but effective. I ran many
> Alphas this way with no problems at all.

On OSF/1 T1.0, which is what we got shipped with our first Alphas, we were categorically told by REO that we were on our own. At the time there were four Alphas in the UK: three were ours and one was at REO running OpenVMS in the morning and OSF/1 in the afternoon (or vice-versa) and we spent a long weekend napping on the machine room floor and on caffeine trying to figure out how to get /usr mounted despite the SIA startup script as we had no choice and the cluster needed to be up as it had cost a small fortune.

The later DEC solution I recall requiring more disk space on the clients, which we didn’t have, but I’m sure that later ships with sufficient disk space had less issues.

Another weekend was spent getting TeX and LaTeX running with ghostscript MX’d from the Ultrix MIPS binary as we just couldn’t get it to compile. That it even worked using MX remains one of the most beautiful surprises of that install.

Arrigo 


  reply	other threads:[~2018-09-27 15:55 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 12:08 Cág
2018-09-27 12:30 ` Alec Muffett
2018-09-27 12:58 ` Donald ODona
2018-09-27 13:54   ` John P. Linderman
2018-09-27 14:09     ` Ronald Natalie
2018-09-27 14:18     ` Jon Forrest
2018-09-27 14:28       ` Arrigo Triulzi
2018-09-27 15:36         ` Jon Forrest
2018-09-27 15:54           ` Arrigo Triulzi [this message]
2018-09-27 18:49             ` Jon Forrest
2018-09-28  0:50               ` Theodore Y. Ts'o
2018-10-01  1:52                 ` Lyndon Nerenberg
2018-10-10  2:38               ` Dave Horsfall
2018-10-10  3:07                 ` Grant Taylor via TUHS
2018-09-27 17:33   ` Donald ODona
2018-09-27 14:47 ` Dan Cross
2018-09-27 17:20   ` arnold
2018-09-27 20:42   ` Cág
2018-09-27 21:07     ` Dan Cross
2018-09-27 22:04       ` Clem Cole
2018-09-27 22:18         ` Henry Bent
2018-09-28  8:33   ` Tony Finch
2018-09-28 18:23     ` Jeremy C. Reed
2018-09-28 16:02 ` Nemo
2018-09-28 16:15   ` Grant Taylor via TUHS
2018-09-28 17:28     ` Arthur Krewat
2018-09-28 19:38       ` Grant Taylor via TUHS
2018-09-28 19:47       ` Grant Taylor via TUHS
2018-09-28 20:30         ` Arthur Krewat
2018-09-28 20:00     ` Nemo
2018-09-28 21:07       ` Grant Taylor via TUHS
2018-09-27 14:31 Noel Chiappa
2018-09-27 15:33 Noel Chiappa
2018-09-27 20:15 ` Dan Cross
2018-09-27 23:14 Noel Chiappa
2018-09-28  5:27 ` Lars Brinkhoff
2018-09-28  2:39 Doug McIlroy
2018-10-10 14:43 Norman Wilson
2018-10-10 16:26 ` arnold
2018-10-11 19:10   ` Lyndon Nerenberg
2018-10-10 17:08 ` Grant Taylor via TUHS
2018-10-11  0:22   ` Steve Nickolas
2018-10-11  2:33     ` David Arnold
2018-10-10 15:26 Noel Chiappa
2018-10-10 15:45 ` Clem Cole
2018-10-10 15:48   ` David
2018-10-13  6:58   ` Michael Kjörling
2018-10-12  0:15 ` Dave Horsfall

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=309587CA-4C65-4AFA-ADFF-0E99B430D191@alchemistowl.org \
    --to=arrigo@alchemistowl.org \
    --cc=nobozo@gmail.com \
    --cc=tuhs@minnie.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).