From: ron@ronnatalie.com (Ron Natalie)
Subject: UNIX version 2*pi
Date: Tue, 17 Oct 2017 14:23:49 -0400 [thread overview]
Message-ID: <07b401d34775$14e230b0$3ea69210$@ronnatalie.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1710171703250.30357@aneurin.horsfall.org>
One of my predecessors at JHU decided 6.06 was a nice symmetrical number and
stuck the version there through many kernel changes. When he left, our
release numbers started forward again.
The BRL/JHU kernel was based on V6. It had a kludge to allow more that
256 users but eventually, we widened the UID/GID to 16 bits each. We then
added a the ability to mount either V6 or V7 file systems (we had a lot of
removable V6 FS media).
-----Original Message-----
From: TUHS [mailto:tuhs-bounces@minnie.tuhs.org] On Behalf Of Dave Horsfall
Sent: Tuesday, October 17, 2017 2:09 AM
To: The Eunuchs Hysterical Society
Subject: Re: UNIX version 2*pi
On Tue, 17 Oct 2017, Don Hopkins wrote:
> McGill University EE UNIX lab systems administration, PDP-11 running
> UNIX version 2*pi (>6, <7, irrational)
Sounds like the one I was maintaining at UNSW: Edition 6, with the bits of
Edition 7 that would fit on an 11/40 and 11/60, plus local AUSAM stuff.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
suffer."
next prev parent reply other threads:[~2017-10-17 18:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 11:58 [TUHS} Running V8 Doug McIlroy
2017-10-16 15:41 ` Don Hopkins
2017-10-17 11:47 ` Tony Finch
2017-10-17 14:30 ` Larry McVoy
2017-10-17 14:50 ` Don Hopkins
2017-10-16 16:28 ` Clem Cole
2017-10-16 16:39 ` [TUHS} Running V8 ... [ really basic tools ] Jon Steinhart
2017-10-16 19:16 ` Ian Zimmerman
2017-10-16 19:28 ` Jon Steinhart
2017-10-17 1:15 ` Ian Zimmerman
2017-10-17 4:20 ` UNIX version 2*pi Don Hopkins
2017-10-17 6:08 ` Dave Horsfall
2017-10-17 18:23 ` Ron Natalie [this message]
2017-10-18 2:46 ` Dave Horsfall
2017-10-18 10:15 ` Ron Natalie
2017-10-16 16:38 ` [TUHS} Running V8 Will Senn
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='07b401d34775$14e230b0$3ea69210$@ronnatalie.com' \
--to=ron@ronnatalie.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).