From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] [TUHS] man-page style
Date: Sat, 17 Nov 2018 22:33:04 -0700 [thread overview]
Message-ID: <e54f2e3d-c194-8cec-5406-5ec0b2c7a369@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20181117200908.2FAF918C073@mercury.lcs.mit.edu>
On 11/17/2018 01:09 PM, Noel Chiappa wrote:
> Sure. (Note that I'm not on COFF, so if anyone replies, please make sure
> I'm CC'd directly.)
Thank you for the reply Noel. I found this to be an interesting read.
I occasionally bump into some Multicians and am always pleasantly
surprised at how different their world is.
> The 386-Pentium actually had support for many segments, but I gather
> they are in the process of deleting it in the latest machines because
> nobody's using it. Which is a pity, because when done correctly (which
> it was - Intel hired Paul Karger to architect it) 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. ():-)
Thank you again for typing the message and sending it to a mailing list
that you're not subscribed to. If we're ever in a pub together, I owe
you a round.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4008 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20181117/d5f094b1/attachment.bin>
next prev parent reply other threads:[~2018-11-18 5:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 20:09 jnc
2018-11-18 5:33 ` gtaylor [this message]
2018-11-18 6:28 ` bakul
2018-11-18 21:24 ` tytso
-- strict thread matches above, loose matches on Subject: below --
2018-11-19 17:53 jnc
2018-11-19 19:48 ` bakul
[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=e54f2e3d-c194-8cec-5406-5ec0b2c7a369@spamtrap.tnetconsulting.net \
--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).