From: Ian L. <Ian...@mq...> - 2004-01-30 17:38:09
|
Hello Dan, First up - I don't know why my message took 2.5 days to get through to the list ... seems that the headers show it getting bogged down at sourceforge someplace. I saw that you started the archives and responded to the forum comments between when I sent the message and when it arrived. > Interesting. Adding a Windows box to an openMosix cluster sounds quite > useful. I never thought about the use for coLinux. Very powerful stuff ... to be able to avoid booting over to Linux would be a real boon for the cluster communities. CHAOS is GPL, and binary ISOs are available from the web site; http://itsecurity.mq.edu.au/chaos/ If we can get your project running with CHAOS, we would make an ISO image for it and advertise it the respective communities. Note, too, to one of the forum comments, CHAOS runs FreeSWAN for all of its cluster communications. So if we get it working, there will be demonstrable proof the ipsec runs neatly over this architecture also. > About source control, I am currently contemplating about whether to use > CVS or BitKeeper, but I'm open to other suggestions as well. Until then, > it would be tarballs and diffs. I don't have a preference ... I haven't worked with either (and I really should). > linux/cooperative.h was previously linux/colinux.h. I renamed that > header at one point and forget about that include instance. Ok .. thanks. > > Can someone with CVS access please supply me with the > > colinux.h file -- or -- could the public source bundle please be > > updated to include this file (or remove the reference). > > See the patch I sent to the mailing list today. Can't wait to test it ... there's a heck of a lot of compiling work to do before I can get up to a testable image. Thanks for your help .. and rock-on with this project (very cool). -- Ian Latter Internet and Networking Security Officer Macquarie University Meet me at the Australian Unix and open systems User Group (AUUG) Security Symposium; 2004 http://www.auug.org.au/events/2004/security/ |