From: Larry McVoy <lm@mcvoy.com>
To: Rob Pike <robpike@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Porting the SysIII kernel: boot, config & device drivers
Date: Sat, 31 Dec 2022 17:24:53 -0800 [thread overview]
Message-ID: <20230101012453.GB5825@mcvoy.com> (raw)
In-Reply-To: <CAKzdPgzcPVdm_x+WxG7VpssNY7fbr-c2S1ax4S9UOgPPDapOrQ@mail.gmail.com>
On Sun, Jan 01, 2023 at 12:02:12PM +1100, Rob Pike wrote:
> A theory about organizations, inspired by OpenBoot.
>
> "I have nothing to do at the moment, why don't I put a FORTH
> interpreter into the boot ROM? And then I'll make it an industry standard.
Yeah, that was Mitch's baby and you have the details as right as I can
remember.
I barfed at Forth, I've coded in Forth and didn't care for it. I didn't
like lisp either but I could sort of see why some people get all worked
up for lisp, wasn't for me, but I could see the point. I never saw the
point of Forth for anything.
But, for whatever reason, Mitch did. Yuck. The one time it was useful
in my memory, was during bringup and the kernel debugger wasn't working
yet. So Mitch, or someone, coded up forth code to walk kernel data
structures, a set of a dump_$whatever. Briefly useful.
Over all, I agree with everything Rob said.
next prev parent reply other threads:[~2023-01-01 1:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 18:25 [TUHS] " Paul Ruizendaal
2022-12-30 18:56 ` [TUHS] " Steve Nickolas
2022-12-31 14:59 ` Dan Cross
2022-12-31 19:08 ` Clem Cole
2022-12-31 21:10 ` Dan Cross
2022-12-31 21:39 ` Clem Cole
2022-12-31 21:52 ` Dan Cross
2022-12-31 23:25 ` Dave Horsfall
2023-01-01 1:02 ` Rob Pike
2023-01-01 1:16 ` George Michaelson
2023-01-01 1:40 ` Larry McVoy
2023-01-01 2:29 ` Warner Losh
2023-01-01 1:24 ` Larry McVoy [this message]
2022-12-31 22:38 ` Theodore Ts'o
2022-12-31 22:55 ` Marc Donner
2023-01-01 3:55 ` Dan Cross
2023-01-01 20:29 ` Paul Ruizendaal
2023-01-01 21:26 ` G. Branden Robinson
2023-01-01 21:31 ` Rob Pike
2022-12-31 21:11 ` Paul Ruizendaal
2022-12-31 20:02 ` Paul Ruizendaal
2022-12-31 21:04 ` Warner Losh
2022-12-31 21:41 ` Dan Cross
2023-01-01 3:08 ` Warner Losh
2023-01-01 4:40 ` Dan Cross
2023-01-01 8:05 ` Jonathan Gray
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=20230101012453.GB5825@mcvoy.com \
--to=lm@mcvoy.com \
--cc=robpike@gmail.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).