This release was reorganized for a clearer distribution and to be in synch with the article "SqueakNOS: Building, changing, booting and installing." http://people.squeakfoundation.org/article/61.html.
It also has Lance and Realtek8139 network cards initialization by default, as well as TCP/IP stack initialization, except for setting up the IP address, which should be done from the Workspace.
gera
Nice work GERA !
I was testing last two images by WMWare Player on Windows and it seems network is in progress. If i will get time i will try to test it more. First look - try to enhance mouse cursor flickering.
This is huge project and i see it like if you are trying to fit an elephant through the eye of the needle. Question is, if after all this work there will raise new small elephant or something else ...
I am affraid that we cannot quickly move over linux kernel and hw support. Maybe some translation from C to ST will be helpful or at least some cooperation with Exupery - direct machine code translation project.
Do you have this kind of questions already solved ? This will also need disk or usb storage support for self surviving i think. Anyway i like this idea of NOS. I wish good luck and lot of effort to your work.
Jan Barger www.barnet.sk
I want to clear a little bit my opinion and ask a question:
Do you plan to go still the old "GCC" and "C" way ?
Because in this case i dont see any real motivation of this kind of distr. and future improvement over standard linux Squeak distribution ...
Jan Barger
Hi Barget,
For me, the point of SqueakNOS is to proove that we can get rid of the operating system. We were inspired by the definition of operating system given by Dan Ingalls in the article "Design Principles Behind Smalltalk" that appeared in the BYTE in August of 1981 (http://www.ipa.net/~dwighth/smalltalk/byte_aug81/design_principles_behind_sm...):
"Operating System: An operating system is a collection of things that don't fit into a language. There shouldn't be one."
In SqueakNOS we've brought the hardware to the semantic realm of the Smalltalk image. Hardware parts are now Smalltalk objects that we can talk to with messages, and everything is surprisingly simple and elegant. Even hardware interrupts are handled in Smalltalk code. We didn't really need an operating system after all, and Dan Ingalls was (of course) right.
Linux has drivers for lots of hardware that SqueakNOS will probably never support. This may be just an exercise in futility. I don't know if this will end up being useful in a comercial project. But who cares? We're having fun :)
Salut! Luciano
On 8/9/06, barger barger@barnet.sk wrote:
I want to clear a little bit my opinion and ask a question:
Do you plan to go still the old "GCC" and "C" way ?
Because in this case i dont see any real motivation of this kind of distr. and future improvement over standard linux Squeak distribution ...
Jan Barger
I just think that if you can include and use EXUPERY some way for direct machine code compilation and translation, you can in future recompile all VM without use of GCC and translation from ST to C. This idea can put more power to your project and its finalization, and i think that this way you can make a real big improvement.
Jan Barger
Hi Jan, Sorry, I completly missed your point. I thought you were thinking about reusing parts of the linux kernel and linux drivers. Actually, what you're suggesting would be fantastic!
Luciano
On 8/10/06, barger barger@barnet.sk wrote:
I just think that if you can include and use EXUPERY some way for direct machine code compilation and translation, you can in future recompile all VM without use of GCC and translation from ST to C. This idea can put more power to your project and its finalization, and i think that this way you can make a real big improvement.
Jan Barger
squeaknos@lists.squeakfoundation.org
-
barger -
Gerardo Richarte -
luciano