From: Ralph Corderoy <ralph@inputplus.co.uk>
To: scj@yaccman.com
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Early multiprocessor Unix
Date: Sun, 06 Aug 2023 10:57:17 +0100 [thread overview]
Message-ID: <20230806095717.0D9BA220FE@orac.inputplus.co.uk> (raw)
In-Reply-To: <4726704a3c0e056d6e4d5dd1dc582116@yaccman.com>
Hi Steve,
> We built an "editor" for a.out files that would read the file in,
> respond to a series of requests, relocate the instructions correctly,
> and then branch to the line of code that it had been about to execute.
What level of granuality were these requests? Could you give a rough
example or two. Was it sed like, with labels and testing branches? Did
the requests operate on matched instructions instead of lines?
--
Cheers, Ralph.
next prev parent reply other threads:[~2023-08-06 9:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 13:24 [TUHS] " Paul Ruizendaal
2022-11-28 13:42 ` [TUHS] " Larry Stewart
2022-11-28 14:05 ` Clem Cole
2022-11-28 14:13 ` Clem Cole
2022-11-28 14:19 ` Warner Losh
2023-08-06 14:19 ` Warner Losh
2022-11-28 14:16 ` Warner Losh
2022-11-28 14:50 ` Clem Cole
2022-11-28 16:30 ` Paul Winalski
2022-11-28 16:49 ` Clem Cole
2023-08-06 14:12 ` Warner Losh
2022-11-28 16:52 ` Jonathan Gray
2022-11-29 9:39 ` Jonathan Gray
2022-11-29 15:54 ` [TUHS] First supercomputer UNIX: The Denelcor HEP (was Early multiprocessor Unix) Ron Natalie
2022-11-29 17:00 ` [TUHS] " Jon Steinhart
2022-11-29 20:53 ` steve jenkin
2023-08-05 23:00 ` [TUHS] Re: Early multiprocessor Unix scj
2023-08-06 0:54 ` Larry McVoy
2023-08-06 6:52 ` Paul Ruizendaal
2023-08-06 9:28 ` Ronald Natalie
2023-08-06 9:57 ` Ralph Corderoy [this message]
2022-11-30 2:55 Rudi Blom
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=20230806095717.0D9BA220FE@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=scj@yaccman.com \
--cc=tuhs@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).