The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] PDP-11/70 SPL (was: Early non-Unix filesystems?)
Date: Mon, 28 Mar 2016 06:59:43 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.11.1603280640080.15730@aneurin.horsfall.org> (raw)
In-Reply-To: <56F7B06F.6040005@update.uu.se>

On Sun, 27 Mar 2016, Johnny Billquist wrote:

> I do not have any experience either way. I have never checked this. I'm 
> just saying that it don't make sense in my head, and the processor 
> handbook do not describe such a property of SPL. But now that I know, 
> I'm going to try and find out.

I'll say it again: it's *definitely* how SPL worked (at least, on the 
11/70 that I hung; too many witnesses...).  Somewhere Out There (tm) is a 
little self-relocating program that completely filled user memory with SPL 
(including overwriting itself; the last act it did was to overwrite 
itself, and was sheer genius).  I saw it in a ;login: newsletter, so it 
*might* be in AUUGN...  When the PC wrapped around, it was SPLs all the 
way down :-)

> It would also be interesting if anyone can come up with a good reason 
> why SPL should work that way.

Likely a firmware bug?

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."


  reply	other threads:[~2016-03-27 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.167.1459043447.15972.tuhs@minnie.tuhs.org>
2016-03-27 10:05 ` Johnny Billquist
2016-03-27 19:59   ` Dave Horsfall [this message]
2016-03-27 11:25 Noel Chiappa
2016-03-27 20:03 ` Dave Horsfall
2016-03-28 13:50 Noel Chiappa
2016-03-28 14:32 ` William Pechter
2016-03-28 21:43 ` 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.1603280640080.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).