The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: brantley@coraid.com (Brantley Coile)
Subject: [TUHS] Redoing "V6on286" or porting V7...?
Date: Mon, 14 Nov 2005 17:59:09 -0500	[thread overview]
Message-ID: <7f751188511736b493ffdb538b5b0505@coraid.com> (raw)
In-Reply-To: <20051114213446.69396F7@minnie.tuhs.org>

you're right.  i was thinking of mini-Unix.  my point was just
that you can do a lot with very little.

> Brantley Coile:
> 
>   i don't know that it's a squese.  a version of v6 ran on an lsi-11
>   with very little ram.
> 
> =======
> 
> If you're thinking of Mini-UNIX, it's a bit of a stretch to call
> it `V6 running on an LSI-11.'  I think the original LSI-11 had no
> memory management; in any case, Mini-UNIX didn't use it, but was
> a throwback to the early days of the PDP-7 and the 11/20 (neither
> of which had memory management).  Only one process could be in
> memory at a time; to let another process run meant swapping the
> first completely out of memory.
> 
> I believe there's a paper in the 1978 all-UNIX issue of the Bell
> Systems Technical Journal about Mini-UNIX or its immediate
> predecessor.  As I recall, there were additional compromises;
> e.g. the shell quietly translated
> 	a | b
> to
> 	a >tempfile; b <tempfile; rm tempfile
> because that was much faster than the thrashing that often
> resulted from trying to let a and b run concurrently.
> 
> Mini-UNIX might be a simpler starting point to get a system
> running on a 286.  Just don't think of it as full V6; it's not.
> 
> Norman Wilson
> Toronto ON
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs




  reply	other threads:[~2005-11-14 22:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 21:34 Norman Wilson
2005-11-14 22:59 ` Brantley Coile [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-09 17:26 Lyrical Nanoha
2005-11-09 21:54 ` M. Warner Losh
2005-11-09 22:03 ` Brantley Coile
2005-11-12  6:13   ` Albert Cahalan
2005-11-12 13:18     ` Brantley Coile
2005-11-13 20:16       ` Peter Jeremy
2005-11-14  9:38         ` Wesley Parish
2005-11-14 15:45         ` Brantley Coile
     [not found]         ` <8a61b612cf43394f33e6531339fe4263@coraid.com>
2005-11-14 19:49           ` Peter Jeremy
2005-11-14 20:31             ` Brantley Coile
2005-11-16 21:41             ` Lyrical Nanoha
     [not found]               ` <17277.62390.986234.433543@hod.localdomain>
2005-11-18 17:59                 ` Lyrical Nanoha
2005-11-19  4:17                   ` Brantley Coile
2005-11-15  3:08         ` Greg Haerr
2005-11-15  3:40           ` Peter Jeremy
2005-11-15 13:30             ` Brantley Coile

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=7f751188511736b493ffdb538b5b0505@coraid.com \
    --to=brantley@coraid.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).