From: "Rick A. Hohensee" <rickh@Capaccess.org>
To: linux-kernel@vger.kernel.org
Subject: Forth interpreter as kernel module
Date: Fri, 05 Apr 2002 20:22:10 -0500 [thread overview]
Message-ID: <fc.00858412003a290a00858412003a290a.3a291d@Capaccess.org> (raw)
Two Forths in Linuxspace now? That's 3 stack machines. Heheheheh,
MAKE YOUR TIME. ALL YOUR BASE ARE BELONG TO KSPAMD.
Does the pforth version run as a kernel daemon like H3rL does?
Phil Burk is I believe still affiliated with Mills College. He'd love to
hear about this. Mike Haas too, probably. Mike Haas wrote the kernel of
Amiga JForth and Phil wrote all the music stuff. I added all the Linux
syscalls to the PForth in cLIeNUX mostly out of nostalgia for JForth, a
"...once in a paradigm thing." Jack "jax" Woehr (sp?). Phil was quite
pleased to hear there's a PForth out there with 160 Linux syscalls as
primitives.
That PForth is in ftp://linux01.gwdg.de/pub/cLIeNUX/interim along with
H3rL, Hohensee's 3-ring Linux, which is a Linux kernel with a 3-stack
machine in 0wnerland. Read ./ABOUT .
Alan,
an Open Firmware IN kernelspace has the potential to have the
functionality of Open Firmware, AND serve as something like an Open Driver
Initiative, with a performance hit perhaps, depending on how the Forth is
implemented. There are native compiling Forths, but they're not nice tiny
little things.
Ed,
As far as security is concerned, a Forth on say vt1 (it's on vt1 here,
er, it's H3sm, a 3-stack machine, but anyway...) is no worse really than
root. As far as how a Forth compares to a kdb, it doesn't. Forth is a
debugger, a compiler, an interpreter, AND a desert topping. A forth won't
have the niceties of an evolved unix tool, but you can write them
interactively. And write things you can't imagine until the problem pops
up, like that thing Torvalds did recently for sniffing at some
Torvaldsianly obscure cache tree buffer tree page cache buffer thing. You
can write stuff like that with the same interactivity you associate with
shell scripting.
More to the point, Forth can be a great personalizer of unix/Linux. Sure,
you don't want a Forth in your DNS box. (I do, but...) You do want a Forth
in your multimedia box. Bigtime. Which is why the "forth" command in
cLIeNUX is upforth, PForth with a unix Jones.
If Forth in Linux is going to go somewhere, Mitch Bradley might want to
comment. He's the author of OpenBoot, and I find that some of my best
Forth-on-unix ideas, he had 15 years ago. He left Sun and does Bradley
Forthworks or Forthware, last I heard. Post to comp.lang.forth too.
Rick Hohensee
Birth Of Kspamd reenactment...
imagine each space as *exactly* one second elapsed between string
outputs...
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM SPAM
SPAM SPAM SPAM SPAM SPAM SPAM SPAM<cursor>
next reply other threads:[~2002-04-06 1:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 1:22 Rick A. Hohensee [this message]
2002-04-06 5:10 ` M. Edward Borasky
2002-04-06 16:05 ` Rick A. Hohensee
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 8:53 Rick A. Hohensee
2002-04-07 10:05 forth " Rick A. Hohensee
2002-04-04 23:49 David N. Welton
2002-04-04 23:59 ` M. Edward (Ed) Borasky
2002-04-05 0:19 ` Alan Cox
2002-04-05 2:51 ` Eric W. Biederman
2002-04-05 18:16 ` benh
2002-04-07 20:50 ` Segher Boessenkool
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=fc.00858412003a290a00858412003a290a.3a291d@Capaccess.org \
--to=rickh@capaccess.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®