From: <ron@ronnatalie.com>
To: "'Clem Cole'" <clemc@ccc.com>, "'Will Senn'" <will.senn@gmail.com>
Cc: 'The Eunuchs Hysterical Society' <tuhs@tuhs.org>
Subject: Re: [TUHS] Upgrading from 11/40 to 11/45 in Unix v6
Date: Mon, 31 Dec 2018 10:05:13 -0500 [thread overview]
Message-ID: <224401d4a11a$3c30a6b0$b491f410$@ronnatalie.com> (raw)
In-Reply-To: <CAC20D2NyvcyhdFR7R0SGQSYED0mMZQDXaRyB8VfXaNCZgzFF-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
Yep, and notwithstanding split I/D, we switched to -n (410 magic) read-only code space.
Of course, the kludge nargs() function didn’t work at all in split-I/D mode unless you made a hack to the processor to change the behavior of MFPI.
[-- Attachment #2: Type: text/html, Size: 2204 bytes --]
next prev parent reply other threads:[~2018-12-31 15:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 2:25 Will Senn
2018-12-31 2:43 ` Clem cole
2018-12-31 3:31 ` Will Senn
2018-12-31 14:55 ` Clem Cole
2018-12-31 15:05 ` ron [this message]
2018-12-31 15:53 ` Clem Cole
2018-12-31 17:30 ` ron
2018-12-31 18:20 ` Paul Winalski
2018-12-31 23:36 ` [TUHS] Useful Unix tools + Usenix tapes Warren Toomey
2019-01-01 1:30 ` Clem cole
2019-01-01 1:58 ` Clem cole
2019-01-01 2:00 ` Clem cole
2019-01-01 2:08 ` Nigel Williams
2019-01-01 2:17 ` Warren Toomey
2019-01-01 8:18 ` Warren Toomey
2018-12-31 2:47 ` [TUHS] Upgrading from 11/40 to 11/45 in Unix v6 Clem cole
2018-12-31 3:08 ` Will Senn
2018-12-31 3:15 ` Clem cole
2018-12-31 6:51 Noel Chiappa
2018-12-31 15:06 ` Will Senn
2018-12-31 15:50 ` Clem Cole
2018-12-31 15:53 ` Warner Losh
2018-12-31 15:59 ` Clem Cole
2019-01-01 1:56 ` Eric Allman
2018-12-31 17:20 Noel Chiappa
2018-12-31 18:38 Noel Chiappa
2018-12-31 20:06 ` Warner Losh
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='224401d4a11a$3c30a6b0$b491f410$@ronnatalie.com' \
--to=ron@ronnatalie.com \
--cc=clemc@ccc.com \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.com \
/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).