1. Re: EuOS
I disagree. It would be possible to write much of an OS in Euphoria with 2
conditions:
1. Euphoria is converted into C or Assembly
2. C or Assembly is used where Euphoria is incapable of handeling it
The first is pretty easy, I would think. I have code to process Euphoria
code, so all I have to do is make it convert it.
The second is not all that hard. I have experience with C and Assembly, and
I have been reading a book called Developing Your Own 32-Bit Operating
System, from which I think I could get enough info to write some low-level
routines.
Jeffrey Fielding
JJProg at cyberbury.net
> [EuOS]
> Although I think the participants may be way over their heads and will
> abandon the project at the first sign of moths in the tubes, here's my
1/50 of
> a dollar, US variety. Wha'chall seem to be doin' is making a *shell*
rather
> than an OS. Now that's not bad, as WinDeath is anything but a good shell
> and UNIX/LINUX already has so many, what's one more. And Euphoria is a
> great language to shell with, because of its size and speed (far superior
to
> the aforementioned shells). An OS needs to be developed from the ground
> up, not the shell down. The first step in an OS is the file system.
OSes used
> to be called DOSes (on all model of systems), meaning Disk Operating
> System. Currently, there are about 15 file systems in popular use, and
> countless more available. In order to have a DOS worth anything, it need
to
> be able to access at least two of these file systems, plus its own unique
file
> system if one exists. ($.02=read the Linux DOCS b/4 you begin. Very
> good information about file systems.) Next, the boot program needs to be
> called (LILO for Linux, IO.SYS for MS-DOS and (?) Win9x). This defines
the
> hardware interface -- i.e. port access, bus control, multitasking, memory
> management, application management, video management, etc. Finally it
> calls the shell. The shell can then access all the utilities and
applications.
> Now, the file system and boot program must be coded in machine byte
> code, and written to the disk boot sector and disk allocation table (or
> something like that) byte by byte. Using Euphoria's or WinDeath's file
calls
> will only reinforce the error-laden Windows file system. So I would
strongly
> recommend sitting down with a nice cup of milk and reading the 10,000 or
> so pages of Linux documentation before you begin an OS. That should tell
> you just about all you need to know about building one. Otherwise, an
> alternative to the present shells is a very good idea (and leave the
hardware
> to someone who doesn't know what he's doing <glances at Bill>.)
