From: Donald Musser <dmjmusser@...>
Date: 2007-01-26T04:38:53+09:00
Subject: Re: A Ruby Operating System (no bashing please)

------=_Part_31716_12048867.1169753929439
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Well, I can't really speak to how you should go about it, but it does sound
pretty interesting. I'd love to see it in action if you get it running =3D)=
.

~Myles

On 1/25/07, Andr=E9 <andre.nho@gmail.com> wrote:
>
> Hello,
>
> this post might sound strange, but after working with ruby for so long,
> I've been thinking about writing a ruby operating system. I've been
> thinking about doing my M.D. thesis about it, but I want to hear some
> of your opinions.
>
> First of all, the philosophical questions :-)
>
> - Does it make any sense? (that is, does it sound useful?)
> - It has been done before?
>
> And then the technical stuff. I though about doing things this way:
>
> 1. Make the ruby VM run on bare metal. (that is, a ruby VM operating
> system)
> 2. Make the standard ruby libraries
> 3. Make SO libraries
>
> For step 1, the logical approach (for me) would be something like this:
>
> 1. Get the ruby source.
> 2. Write a replacement for every libc function ruby uses.
> 3. Compile ruby into a kernel and boot it.
>
> Does this sound like a logic approach? Or there's any better way to do
> it, or I should go for a different path here?
>
> Thank you in advance,
>
> Andr=E9
>
>
>

------=_Part_31716_12048867.1169753929439--