The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] TUHS Digest, Vol 44, Issue 3
Date: Fri, 21 Dec 2007 18:18:33 -0800	[thread overview]
Message-ID: <20071222021832.GA27487@bitmover.com> (raw)
In-Reply-To: <mailman.3.1198288801.19979.tuhs@minnie.tuhs.org>

> Date: Fri, 21 Dec 2007 12:58:40 +0000
> From: Tim Bradshaw <tfb at tfeb.org>
> Subject: Re: [TUHS] HP Apollo Series 400 and DOMAIN/OS...
> To: Wilko Bulte <wb at freebie.xs4all.nl>
> Cc: tuhs at tuhs.org, asbesto <asbesto at freaknet.org>
> Message-ID: <CAC4A7E7-B4E5-41FA-BA05-7707366B6215 at tfeb.org>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
> 
> On 21 Dec 2007, at 12:31, Wilko Bulte wrote:
> >
> > You could have DomainOS take a BSD or a SysV personality.  Very  
> > interesting.
> 
> Very tangentially, Masscomp's RTU (real time Unix) could do this  
> too.  Other than that I think it is definitely something best  
> forgotten, as it was pretty horrid (although my memory may be biassed  
> by the awfulness of the HW)

Oh, I have fond memories of the Masscomp.  That's where I learned how to
do sys admin (recovered from an rm -rf /) as well as networking (based
on 4.1c BSD as I recall, plus hacks).  Masscomp had a really nicely redone
version of the socket programming docs that was most helpful at the time.

I was ..!uwvax!geowhiz!geophys!lm as I recall and all the geo* were 
Masscomps.

Ah, the joys of 20 users on a 40MB disk.  That's why I wrote something
that turned Honeyman's time optimal but space worst case pathalias
db into O(time optimal) as well as O(space best case).  Only dynamic
programming alg I've ever done and written up.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com



       reply	other threads:[~2007-12-22  2:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3.1198288801.19979.tuhs@minnie.tuhs.org>
2007-12-22  2:18 ` Larry McVoy [this message]
2007-12-22 10:06   ` Wilko Bulte

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=20071222021832.GA27487@bitmover.com \
    --to=lm@bitmover.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).