SqueakNOS August 2006

squeaknos@lists.squeakfoundation.org

3 participants
4 discussions

New release: SqueakNOS-08-Aug-2006.iso
by Gerardo Richarte 10 Aug '06

10 Aug '06

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

3 5

SqueakNOS-gera.39: Realtek8139PCIDevice initialized by default (when found)
by Gerardo Richarte 08 Aug '06

08 Aug '06

Name: SqueakNOS-gera.39 Author: gera Time: 8 August 2006, 4:35:29 pm UUID: 9a46dc1c-28be-46e5-92cb-b03407ac5830 Ancestors: SqueakNOS-gera.38 Computer class>>initialize Moved startUp for ExternalObject (ExternalAddress) earlier in the StartUpList, so it's initialized before Computer. If you file in this in a SqueakNOS-aware image you may have problems, and may need to manually tweak the startUp list. I'll test it latter, and try to fix it if real. Computer class>>startUpPCComputer Install Realtek8139PCIDevice (if detected), and initializes Computer networkingStack

1 0

New Article: Building, changing, booting and installing.
by Gerardo Richarte 04 Aug '06

04 Aug '06

*Posted 4 Aug 2006 by gera <http://people.squeakfoundation.org/person/gera/>* (Journeyer) To roll your own version of SqueakNOS, either changing the native side or the .image side, you need to know how to rebuild and boot it. This process should be as easy and fast as possible. This article will explain the building process and the boot process, describing how to rebuild everything from scratch, how to create a new .iso image, and how to use GRUB to boot SqueakNOS from a fat/vfat, NTFS, ext2/3 or other file system, from either a harddisk or USB disk. http://people.squeakfoundation.org/article/61.html Index: *Quickly rebuilding and trying *Booting from other than a CD **General GRUB instructions *Chaining GRUB with Windows 2000/XP/2003 bootloader* *Chaining GRUB with LILO **Chaining GRUB with SYSLINUX **Chaining GRUB with another GRUB **Chaining GRUB with DOS or Windows 9x/ME **Installing SqueakNOS' GRUB as bootloader **Booting SqueakNOS from a USB disk* *Last notes on using GRUB **SqueakNOS components * *What now? * * enjoy as much as possible! gera * *PS: I accidentally posted a draft version of the article a few days ago, now, thanks to Ken Causey I was able to replace it with this finished version. *

1 0

New release: RTL8139 support, TCP/IP "working", native improvements
by Gerardo Richarte 02 Aug '06

02 Aug '06

Stef dijo: > are you writing tests for SqueakNet? > Because this is a cool project and with tests we could really build > on top of it. > > Hi Stef! The truth is that Luciano is doing all the work in NetSqueak. And yes, he's doing lots of tests (lots and interesting). Let me copy here he's last commit log to http://www.squeaksource.com/Net.html. For every thing he does, he does tests. The last thing he implemented for testing is the RealisticLoopback InternalNetworkDevice. A subclass of Loopback which implements drops, corruption and delays. To test how the stack behaves in this cases. On the other side, for SqueakNOS I'm not writing no tests. I don't really know how to write tests for the HardwareDevices, but the truth is that I have not yet felt the magic of tests, so I'm not pushing it too hard... mea culpa. ok, the commit log for your pleasure: Name: Net-len.13 Author: len Time: 1 August 2006, 2:02:21 pm UUID: dcfbc174-bcdb-4690-8af7-b46ab4704681 Ancestors: Net-len.12 - Implemented delayed ACKs in TCP. - New tests for TCP. - Timers now are working. - Refactored InterfaceConduit/ProtocolStack... the two of them are now one: NetInterface. I don't know yet if this is good enough, but I had to do this change because I needed to start and stop timers (TCP, IP reassembly and ARP timers), and the same object that understands #up and #down (the interface) and manages the process that handles incomming packets seems to be the right object to start and stop timers. All processes that are required for the networking stack are started and stopped sending #up and #down to the network interface.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

SqueakNOS August 2006