wow, great.
think it would be good to command through the Nash. Now I'm on my way to my
company on the subway station. and checking out the Nash from SVN
Repository. :)
I think you made another great step toward the elaborate SharpOS.
good
--
wonbear
On 9/13/07, William Lahti <[EMAIL PROTECTED]
I'd like to introduce you all to a project I've been working on for
about a day and a half. It's a command shell, similar to BASH or other
POSIX shells, written (of course) in C#. I call it Nash.
It uses only the Console interface, so no special libraries are
needed. It's got support for variables
in the svn:
sandbox\logicalerror\KernelScheduling
I've put some threading/scheduling concept code.
It's far from done & complete, but it's a start. (nothing is set in
stone either)
Any ideas, comments, additions are welcome.
On 9/11/07, William Lahti <[EMAIL PROTECTED]> wrote:
> The sharpws-server part was never compilable on my machine, because I
> hadn't gotten to that point yet.
Yes i noticed & no problem ;)
> Clients would then need to link to 2 libraries instead of 1. So I'd
> prefer not to, but it's not that bi
Well i think, just like JaeHyun Roh mentioned, that we should write a
simple round-robin/FIFO scheduler first and go from there.
If the scheduler is abstracted properly it shouldn't be too hard to
experiment with other schedulers..
I wouldn't be suprised if we have to go trough a couple of iteratio
>> > Going with MPL only is IMHO a bad idea.
>
> MPL is the pragmatic choice. Chriss is a much bigger stakeholder here
> than me though.
To be clear - since its a double quote - thats not my quote. :)
> "Users" are _not_ "coerced" to contribute back. _Developers_ are. So
> if you are just using t
