From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] PDP-11/70 SPL (was: Early non-Unix filesystems?)
Date: Mon, 28 Mar 2016 09:50:40 -0400 (EDT) [thread overview]
Message-ID: <20160328135040.7CF8D18C0B6@mercury.lcs.mit.edu> (raw)
> From: Dave Horsfall
> That makes sense, and someone forgot to document it...
Or perhaps it was added precisely to get rid of the window, and then someone
discovered that it could be used to freeze the system, so they decided they'd
better not document it?
If the system had MOS memory, and you had to power cycle the machine to get it
out of this state, there wouldn't be any evidence left of who did the deed
(unless the system was writing extensive audit trailing to disk), so it would
be a great 'system assasin' (aka vandal) tool.
Noel
PS: I guess this is more PDP-11ish than UNIXish - apologies for the off-topic!
next reply other threads:[~2016-03-28 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 13:50 Noel Chiappa [this message]
2016-03-28 14:32 ` William Pechter
2016-03-28 21:43 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2016-03-27 11:25 Noel Chiappa
2016-03-27 20:03 ` 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=20160328135040.7CF8D18C0B6@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.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).