From: jnc at mercury.lcs.mit.edu (Noel Chiappa)
Subject: [COFF] [TUHS] man-page style
Date: Mon, 19 Nov 2018 12:53:31 -0500 (EST) [thread overview]
Message-ID: <20181119175331.A0A9A18C076@mercury.lcs.mit.edu> (raw)
> From: Grant Taylor
> Thank you for the reply
Sure; I love to yap about stuff like this.
> I occasionally bump into some Multicians and am always pleasantly
> surprised at how different their world is.
Yes, it's very unlike most of what's been done since. Some of it (e.g. a
strictly ordered set of rings for protection) was wrong, but there's a lot of
good stuff there yet to be mined.
>> Which is a pity, because when done correctly (which it was - Intel
>> hired Paul Karger to architect it)
Ooops, it was Roger Schell, I get them mixed up all the time. His oral
history, here:
https://conservancy.umn.edu/handle/11299/133439
is a Must Read.
>> it's just what you > need for a truly secure system (which Multics also
>> had) - but that's another long message.
> If you're ever feeling bored and would like to share that story.
OK, soon.
> From: Bakul Shah
> All of this would be easily possible on the Mill arch. if ever it gets
> built. Mill has segments and protected function calls.
What I found about that mostly talked about the belt stuff. Do you happen to
have a pointer to the segment/call stuff?
> set-uid has its own issues. Plan9 doesn't have it.
Ah, what were the issues (if you happen to know)?
Noel
next reply other threads:[~2018-11-19 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 17:53 jnc [this message]
2018-11-19 19:48 ` bakul
-- strict thread matches above, loose matches on Subject: below --
2018-11-17 20:09 jnc
2018-11-18 5:33 ` gtaylor
2018-11-18 6:28 ` bakul
2018-11-18 21:24 ` tytso
[not found] <20181116192941.DFB6218C073@mercury.lcs.mit.edu>
2018-11-16 20:46 ` gtaylor
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=20181119175331.A0A9A18C076@mercury.lcs.mit.edu \
--to=coff@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).