From: plan9@sigint.cs.purdue.edu
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Mt. Xinu
Date: Tue, 14 Feb 2006 16:42:26 -0500 [thread overview]
Message-ID: <20060214214226.GF23352@sigint.cs.purdue.edu> (raw)
In-Reply-To: <ACD7AFF1-DE58-4A7C-9880-27E2DCE5A38E@orthanc.ca>
On Fri, Feb 10, 2006 at 07:46:19PM -0800, Lyndon Nerenberg wrote:
>
> On Feb 10, 2006, at 7:40 PM, quanstro@quanstro.net wrote:
>
> >mt xinu 4.3bvd (sic).
>
> Whatever was the magic of the Mt. Xinu releases? I've worked on
> generic 4.2 as well as Ultrix 1.*, but nobody was ever able to
> explain the difference ...
AFAICT, it's just BSD with NFS bolted on. We're still running it on a
MicroVAX, though we're now down to only one working Eagle:
Feb 14 13:05:33 merlin vmunix: 4.3 BSD + NFS UNIX #19: Thu Oct 6 14:48:43 EST
+2005
Feb 14 13:05:33 merlin vmunix: real mem = 8355840
Feb 14 13:05:33 merlin vmunix: avail mem = 7001088
Feb 14 13:05:33 merlin vmunix: using 255 buffers containing 522240 bytes of
+memory
Feb 14 13:05:33 merlin vmunix: uba0 at tr0
Feb 14 13:05:33 merlin vmunix: uda0 at uba0 csr 172150 vec 774, ipl 17
Feb 14 13:05:33 merlin vmunix: ra0 at uda0 slave 0
Feb 14 13:05:33 merlin vmunix: ra0: raeagle
Feb 14 13:05:33 merlin vmunix: dhu0 at uba0 csr 160020 vec 300, ipl 17
Feb 14 13:05:33 merlin vmunix: dhu1 at uba0 csr 160040 vec 310, ipl 17
Feb 14 13:05:33 merlin vmunix: qe0 at uba0 csr 174440 vec 770, ipl 17
Feb 14 13:05:33 merlin vmunix: qe0: hardware address 08:00:2b:0d:44:a7
Feb 14 13:05:33 merlin vmunix: root fstype ufs
Feb 14 13:05:37 merlin savecore: reboot after panic: Segmentation fault
Old CS profs. never die-- they just make you maintain their old stuff
forever. :)
ObPlan9: someone should port Plan 9 to the MicroVAX!
next prev parent reply other threads:[~2006-02-14 21:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 3:40 [9fans] More 'Sam I am' quanstro
2006-02-11 3:46 ` [9fans] Mt. Xinu Lyndon Nerenberg
2006-02-14 21:42 ` plan9 [this message]
2006-02-14 22:03 ` Brantley Coile
2006-02-14 22:48 ` Bruce Ellis
2006-02-15 4:39 ` Jim McKie
2006-02-15 6:29 ` Bruce Ellis
2006-02-15 13:04 ` namec (was Re: [9fans] Strange date/time on some created files) rog
2006-02-15 13:07 ` rog
2006-02-11 3:53 [9fans] Mt. Xinu quanstro
2006-02-11 4:09 ` Lyndon Nerenberg
2006-02-14 21:43 ` plan9
2006-02-11 10:25 ` Richard Miller
2006-02-11 4:25 quanstro
2006-02-11 4:34 ` Lyndon Nerenberg
2006-02-11 16:26 ` Jack Johnson
2006-02-11 4:47 quanstro
2006-02-11 4:54 ` Lyndon Nerenberg
2006-02-15 1:57 dmr
2006-02-15 2:00 dmr
2006-02-15 3:55 ` Jim McKie
2006-02-15 13:50 ` Marina Brown
2006-02-15 17:30 ` Bruce Ellis
2006-02-20 23:24 ` jmk
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=20060214214226.GF23352@sigint.cs.purdue.edu \
--to=plan9@sigint.cs.purdue.edu \
--cc=9fans@cse.psu.edu \
/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).