From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] PDP-11/70 SPL (was: Early non-Unix filesystems?)
Date: Mon, 28 Mar 2016 07:03:13 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.11.1603280700560.15730@aneurin.horsfall.org> (raw)
In-Reply-To: <20160327112543.EF59D18C0A3@mercury.lcs.mit.edu>
On Sun, 27 Mar 2016, Noel Chiappa wrote:
> > why SPL should work that way.
>
> So that when doing:
>
> SPL 0
> WAIT
>
> you don't lose by having the interrupt happen between the SPL and the WAIT?
That makes sense, and someone forgot to document it...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2016-03-27 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 11:25 Noel Chiappa
2016-03-27 20:03 ` Dave Horsfall [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-28 13:50 Noel Chiappa
2016-03-28 14:32 ` William Pechter
2016-03-28 21:43 ` Dave Horsfall
[not found] <mailman.167.1459043447.15972.tuhs@minnie.tuhs.org>
2016-03-27 10:05 ` Johnny Billquist
2016-03-27 19:59 ` Dave Horsfall
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=alpine.BSF.2.11.1603280700560.15730@aneurin.horsfall.org \
--to=dave@horsfall.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).