From: ralf@uni-koblenz.de
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: The Forth may be with you ...
Date: Wed, 20 May 1998 16:37:47 +0200 [thread overview]
Message-ID: <19980520163747.16398@uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.3.95.980519224917.10762B-100000@lager.engsoc.carleton.ca>; from Alex deVries on Tue, May 19, 1998 at 10:52:08PM -0400
On Tue, May 19, 1998 at 10:52:08PM -0400, Alex deVries wrote:
> On Wed, 20 May 1998 ralf@uni-koblenz.de wrote:
> > for the fun of it and because I needed something that is programable,
> > interactive and small (92kb including the full dictionay) I ported pforth
> > v19 to run on the raw ARC firmware. If anybody is interested in this
> > toy, tell me. Even you even have an alibi application for this toy,
> > tell me asap :-)
>
> Alright, I'll bite.
>
> Exactly what is this useful for? Could we use this as a LILO replacement
> for SGI/Linux?
Well, I was fed up of compiling test programs for the ARC firmware to play
with it, reboot crash the box and start all over again.
What could it be usefull for? It's a full programming language including
development environment, so you can basically do anything with it. If you
wish, knit your own OpenFirmware from it? And yes, you could brew a LILO
equivalent from it.
The question is still if we need such a thing. It's a overkill solution
with small resource footprint and absolute flexibility. But then it might
be what makes it attractive.
Ralf
prev parent reply other threads:[~1998-05-20 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-20 1:17 The Forth may be with you ralf
1998-05-20 2:52 ` Alex deVries
1998-05-20 14:37 ` ralf [this message]
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=19980520163747.16398@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=adevries@engsoc.carleton.ca \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.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