Ian Latter has reposted the CosMos v0.1.5.0

Ian Latter has reposted the CosMos v0.1.5.0 installation file on his http://midnightcode.org/projects/chaos/ site.

No, this is not an updated version, but Ian has reposted it after recieving a number of requests for CosMos which is no longer available from its original site.  The CosMos setup-0.1.5.0.exe is a Windows installation exe.  I tested it when it was first released, as I recall, and had no problem using it.  (Note that Andreas Schäfer and Christian Kauhaus have more current and somewhat related work, The Harpy Project, on running coLinux with openMosix.)  

Bruce

The current file is:

CosMos v0.1.5.0  August 16, 2004 reposted at:
http://midnightcode.org/projects/chaos/code/setup-0.1.5.0.exe 
http://midnightcode.org/projects/chaos/code/setup-0.1.5.0.exe.md5 

below is a snippet from the original List postings to openmosix-general and openmosix-devel August 15, 2004 (with the file location updated):
...
 CosMos-0.1.5.0;
      Brief:  A virtual (Linux and openMosix) cluster node for Win32 platforms - CosMos is the supercomputer for your workstations.
      Packages; Linux-2.4.26 kernel with openMosix-2.4.26-20040706 and openmosix-tools-0.3.6-2.
      Software; http://midnightcode.org/projects/chaos/code/setup-0.1.5.0.exe 
      Size; 4.7Mbytes
      MD5; dd8d4722526c8dfd293d29f2765aa388
      or http://midnightcode.org/projects/chaos/code/setup-0.1.5.0.exe.md5 

  CHAOS-1.5 and CosMos-0.1.5.0 are compatible, and both can partake in the same openMosix cluster.

  CosMos is experimental.  There are a lot of things we still don't know about openMosix on coLinux - such as why programs don't auto-migrate away from Windows cluster nodes.  However, if you have a hard/dedicated master/central/head node, then programs will migrate from that head node, to Win32 nodes correctly -- from experiments done to date.

  To get CosMos to work on Windows using the PCAP driver, you need to specify the name of the Win32 NIC that you are going to bridge with.  I have tried to autodetect this, but the detection is not in sync with the coLinux bridge driver, so you may need to experiment.  Tips for connectivity;

  -- choose "other" from the select list .. and type a name ...
  -- enter names that are brief but matching your NIC (Ie; instead of "Intel(R) PRO/100 VM Network Connection", just type "Intel").
  -- if your NIC is bridged using a Microsoft bridge adapter, then the name of your NIC is actually "Microsoft"
  -- many systems will default to the name "Local Area Connection".
  -- If all else fails, boot a node using "Power On Debug" and see what error coLinux aborts with (it lists the adapters on startup).

  The only configuration GUI for CosMos is in the installer.  If you don't want to uninstall and reinstall, then see config.xml in the installed directory.

  See the coLinux FAQs at http://www.colinux.org/ if you need more help.

  My only concern with the release of these two versions is that the DHCP leasing hasn't been tested well.  It works, but I'm not certain that it retains its lease correctly.  Test it before deploying it in production environments.
... 
Regards,

Ian Latter
http://midnightcode.org/ 






-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click