From: Steve Nickolas <usotsuki@buric.co>
To: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX "Machine Layer" Standards
Date: Thu, 20 Apr 2023 16:18:04 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2304201616050.20132@sd-119843.dedibox.fr> (raw)
In-Reply-To: <5A9q989Xqp3qAU5v84HciEjrFF9tcvviKQYlxhwTCbnDjEARnMx_BtNkzqXR_0Y0nAkzCdaSR6KGqWCQgwjUW_ydfz6iQSFKRvTnhGiqyc0=@protonmail.com>
On Thu, 20 Apr 2023, segaloco via TUHS wrote:
> Anywho, I'm kinda at a standstill on this project right now while I work
> on a few other things, namely a disassembly of Dragon Quest for the
> Famicom (embedded console games are a lot like operating systems) and
> manual page diffing stuff, but I'm hoping to carve out some time this
> summer, maybe even a little coding retreat from work for a few weeks, to
> hammer out a true project plan on paper so I can start working on more
> of this in earnest. I'm not sure yet if I'll be headed down the "get
> UNIX going" or "get my kernel going" route first when I get there, but
> either way, I'm sure we'll have plenty to talk about in the coming year.
Funny you mention Dragon Warrior, that's been something that's breaking my
brain from two different directions lately (since I'm trying to port it to
the Apple //e and the Nabu, and I'm completely in the weeds for both). XD
I haven't worked much on my own Unix stuff lately because the Nabu stuff's
taken a lot of my brainpower.
-uso.
next prev parent reply other threads:[~2023-04-20 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 15:57 Paul Ruizendaal
2023-04-20 18:57 ` segaloco via TUHS
2023-04-20 20:18 ` Steve Nickolas [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-21 14:37 Noel Chiappa
2023-04-21 17:58 ` John Cowan
2023-04-21 20:36 ` Clem Cole
2023-04-20 14:56 Paul Ruizendaal
2023-04-20 16:04 ` Warner Losh
2023-04-20 19:04 ` segaloco via TUHS
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.DEB.2.21.2304201616050.20132@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--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).