Re: what kind of non microconroller app are done in forth?

On Apr 17, 8:31 am, gavino <gavcom...@[EMAIL PROTECTED]
> wrote:

<snip>

> is anyone at al trying to create a i686 operating system done in
> forth? like linux?

Like linux? You mean strip down a linux system to boot up a kernel and
just a forth with bare minimal niceties? I think the Gforth guys have
something like that - check their site. Or do you mean

http://www.forthos.org/

While there take a look at:

http://www.menuetos.net/

I expect there's a lot of juicy code to be gleaned from these 2
projects.

I've been meaning to take a look at these but been way too busy at
work and in my free time trying to ****t Albert's ciforth to OS X. A
great way to learn forth and more about its innards, I discovered by
the way, if you've not looked at Albert's forth I recommend you do -
it's small, simple and quite elegant.

It may be best to boot off another 'host' OS linux/windows/xx if
you've a 386 or better and run your forth there.

It may be that writing an entire modern OS may be a surmountable
obstacle that you could 'solo'.

But you go do that and you're stuck with.... the problem of....

It looks like WAY WAY too much work to write device drivers etc... I
mean, look every PC's gonna be different, you're gonna have one with
this network card, that GFX card etc, mmmm... PCI bus...mmm... USB...
Sounds like a royal pain. How you gonna cover all the devices people
are reasonably expected to have? Even writing drivers for just the
stuff you own yourself's gonna be a right pain.

Then you got to convince everyone your OS is the next great thing and
to come and write drivers, utils and apps for it etc..

= Dead OS.

Time invested in writing a modern OS is no small thing.

I reckon it's way tuffer today to code an OS for an IA-32 or AMD64
than chugging out code for a Z80 or 6502 or a 6800. Unless of course,
you restrict it to just doing simple things, which sometimes may be a
good idea, but then why not just use something smaller and less
sophisticated?

So you see the problem?

Is the _time_spent_ worth the _effort_?

Linus was in the right place and the right time with pretty damned
good code...

I don't know I may be talking bollocks, but I'm sure those who are
more 'long in the tooth' will chime in.

Here, you got some free time? Got a mac? Why not you help me debug
that thing that's been a thorn in my side for the past couple of
days.. (linux execve <--> OSX/BSD execve - in the word SYSTEM) don't
flipping know what I'm doing wrong and haven't had a decent 2-3 hours
to sit down to it till .. God, Thursday.. work = ftl :(.

Robert Spykerman