Menu
▾
▴
colinux-devel — Cooperative Linux development mailing list
You can subscribe to this list here.
| 2004 |
Jan
(64) |
Feb
(530) |
Mar
(266) |
Apr
(580) |
May
(360) |
Jun
(161) |
Jul
(185) |
Aug
(164) |
Sep
(123) |
Oct
(160) |
Nov
(59) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(156) |
Feb
(95) |
Mar
(124) |
Apr
(81) |
May
(79) |
Jun
(179) |
Jul
(35) |
Aug
(64) |
Sep
(56) |
Oct
(57) |
Nov
(18) |
Dec
(41) |
| 2006 |
Jan
(65) |
Feb
(37) |
Mar
(59) |
Apr
(73) |
May
(65) |
Jun
(27) |
Jul
(54) |
Aug
(76) |
Sep
(103) |
Oct
(23) |
Nov
(45) |
Dec
(29) |
| 2007 |
Jan
(41) |
Feb
(47) |
Mar
(61) |
Apr
(24) |
May
(14) |
Jun
(6) |
Jul
(23) |
Aug
(30) |
Sep
(16) |
Oct
(9) |
Nov
(53) |
Dec
(36) |
| 2008 |
Jan
(19) |
Feb
(49) |
Mar
(74) |
Apr
(21) |
May
(24) |
Jun
(5) |
Jul
(9) |
Aug
(53) |
Sep
(26) |
Oct
(23) |
Nov
(32) |
Dec
(19) |
| 2009 |
Jan
(47) |
Feb
(49) |
Mar
(39) |
Apr
(61) |
May
(28) |
Jun
(19) |
Jul
(12) |
Aug
(10) |
Sep
(31) |
Oct
(16) |
Nov
(60) |
Dec
(26) |
| 2010 |
Jan
(17) |
Feb
(9) |
Mar
(32) |
Apr
(11) |
May
(24) |
Jun
(33) |
Jul
(5) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(17) |
Dec
(7) |
| 2011 |
Jan
(12) |
Feb
(16) |
Mar
(2) |
Apr
(12) |
May
(5) |
Jun
(10) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(11) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2013 |
Jan
|
Feb
(7) |
Mar
(4) |
Apr
(10) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(3) |
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Ian C. B. <ia...@bl...> - 2004-01-31 06:14:37
|
On Thu, Jan 29, 2004 at 01:26:52AM +0000, Nuno Silva wrote: > >At the moment, UML is the hosting platform of choice for virtual Linux > > I can be wrong, but I think that coLinux doesn't play in this field > (virtual servers for *untrusted* root users) because, unlike UML or XEN, > the "virtual" linux can bring the host down. A UML may be run as a Honeypot. There really hasn't been talk of using Xen for the same on the list. Honestly, this isn't what I'm looking for. I'm not suggesting giving root to untrusted users for hosting purposes. Even with the fairsched kernel patch on a SKAS enabled host, users may still monopolize system resources with UML (namely system IO). It's actually easier to provision independant "virtual servers" in a virtual networked topology rather than pile layer after layer of complexity onto a single image. With separate IP stacks, you can intermix LVS servers and iptables firewall boxes between content hosting images and VMWare servers. We are doing this with UML and VMWare now, but the performance really could use some help (particularly when UML images become IO bound). > Disabling interrupts and entering and endless loop or /bin/cat > /dev/random > /proc/kmem or some other havoc will do this... In an ideal world, a virtual image would be sandboxed off from other images and the host kernel. From a management perspective, I would rather have a dozen "just as insecure" but separate images serving simplified purposes than one large complex system. You can always lock down and compartmentalize those insecure kernels using standard techniques. > Even with this possible drawback, the system is very usefull for running > "trusted" linux systems at (near) hardware speed. Precisely what I am looking for. > >I would LOVE to have a Linux self-hosted, ring 0 device driver driven, > > Me too :-) And, as you said, there are some solutions right now, each > with their pro's and con's. Getting a Linux/x86 native host port working would be a great first step. Is anyone actively working on this at the moment? I would love to help any way I can. - Ian C. Blenke <ia...@bl...> |
|
From: Nuno S. <nun...@vg...> - 2004-01-31 05:18:28
|
Hi! Ian C. Blenke wrote: > On Thu, Jan 29, 2004 at 12:42:30AM +0200, Shachar Shemesh wrote: [..] > parallel with OTHER kernels. Think of Linux X86 images running on a > Linux X86 host without UML or VMWare, running Linux PPC images on a Darwin > box, or Linux Sparc images on a Solaris box - why limit this > architecture purely to Microsoft? > Agreed. [..] > > To truely grasp the importance what CoLinux offers, think hugely > scalable hosting farm. The closest thing to CoLinux at the moment is > really the Xen Hypervisor: > > http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ > > Unfortunately, Xen isn't cross architecture, and you need to retrofit > other kernels to run under it (see the Windows XP port limited to > academic source licensees, or the recent NetBSD port to the same). > > At the moment, UML is the hosting platform of choice for virtual Linux I can be wrong, but I think that coLinux doesn't play in this field (virtual servers for *untrusted* root users) because, unlike UML or XEN, the "virtual" linux can bring the host down. Disabling interrupts and entering and endless loop or /bin/cat /dev/random > /proc/kmem or some other havoc will do this... Reality check: I'm I right? Even with this possible drawback, the system is very usefull for running "trusted" linux systems at (near) hardware speed. > > I would LOVE to have a Linux self-hosted, ring 0 device driver driven, Me too :-) And, as you said, there are some solutions right now, each with their pro's and con's. Regards, Nuno Silva |
|
From: Ian L. <Ian...@mq...> - 2004-01-31 05:18:22
|
Hello Dan, > Primarily, the requirement is creating a root block file system (using > the loopback block device), while changing the disto to use newly added > devices nodes /dev (cobd0, cobd1, etc...) instead of the /dev/hd* nodes. > > The closest examples for this now are the file system images distributed > with User Mode Linux. However, these images sometimes miss the /dev/console > node which causes the init process to fail (this also happens with the > regular non-UML Linux kernel). Creating that node fixes the problem. I've just whipped thru the docs again; is there any info on the devices and their numbering. Are they literally the same as the UML distros? > Yesterday I was under the impression that the binaries are stable enough > to be released. I hope to release some example binaries soon, so you > and the others can experiment with it. This would be good. I have never had to build a CYGWIN dev environment .. this would save a lot of time - methinks. Would the binary bits be GPL? -- 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/ |
|
From: Ian L. <Ian...@mq...> - 2004-01-31 04:52:45
|
> If there were a way to run CoLinux on an OpenSSI Linux cluster > right now, you better believe we would already be doing it. Yum, server consolidation fantasy land ... and you think SCO hates GPL now ... ;-) -- 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/ |
|
From: Steven E. <ste...@ya...> - 2004-01-31 04:28:23
|
--- Shachar Shemesh <win...@sh...> wrote: > While it's certainly an exiting project, I understood that it was NOT > > based on the Windows subsystem mechanism, but rather hacking your way > > into Windows NT's ring 0 using a device driver. While I'm a great fan > of > "if it works", wouldn't it be nicer, long run, to have a proper > subsystem of it? As one of the other comments said the Windows POSIX subsystem model has some limitations. I would like to bring CoLinux to the point that it ties in as well to Windows and ReactOS as SFU does. > Also, what are you planning on doing with graphic applications? > CoLinux > works by running a X server on the windows machine. That's probably > not > the best solution there is. How is the ReactOS windowing back-end > implemented? We are looking at that currently. ReactOS's TCP/IP implemetation is lacking so running XFree/Cygwin is not a option atm. Once we get TCP/IP going than any Xserver for Windows should do but I would like to bring libw11 in to ReactOS and implement a Xserver as a core OS componate. LibW11 if you dont know about it sits on top of User32/GDI and translates all of the XLib calls to Win32 calls. I we can make a faster/lighter Xserver reusing this code. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ |
|
From: Steven E. <ste...@ya...> - 2004-01-31 02:21:13
|
One of the ReactOS developers is working on OpenMosix + CoLinux now. Thanks Steven --- Favre Benoit <ben...@li...> wrote: > hello, > do you think that the MOSIX kernel patch would work with coLinux. > > I work in a university where thousands of windows computers are > unused during > night and hollyday time. A "screensaver" version of coLinux with > MOSIX > support could lead to great supercomputing clusters with a very > simple > deployment (i currently use clusterknoppix, the mosix/knoppix > distribution > but it implies a machine reboot). > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ |
|
From: Szalai F. <sz...@ei...> - 2004-01-30 20:31:24
|
On Wed, 2004-01-28 at 23:12, Dan Aloni wrote: > I think you misunderstood the Makefile strategy in the coLinux tree. > > The tree is actually a flat tree. The top Makefile includes the subdir > Makefiles, and so on. There is no recursive invocation of make, so the > 'all' target is evaluated several times if that patch applied. Ok, I understand! I will keep in my mind if I do somthing else with Makefiles. It was just a hot-fix. -- Regards Feri |
|
From: Dan A. <da...@gm...> - 2004-01-30 19:18:40
|
On Fri, Jan 30, 2004 at 10:53:10AM -0800, ePAc wrote: > now i'm stuck. it appears that since Jan 4th 2004, the Windows DDK is > payware. you can buy the CD, but no longer download it unless you have > access to MSDN (about $700 for the basic new subscription to the required > level to get the DDK). that's a little arsh for something that used to be > free... > Yeah, that's a problem. We currently depend on the DDK in order to link the sys file in the final linkage stage of the driver. <cough> ed2k://|file|Microsoft Windows 2000 DDK - Driver Development Kit.exe|68905688|661645e0c800fa55604765ad41844668| </cough> Some background: Fortunately, the cygwin gcc toolchain outputs a valid COFF file to be passed as input to Microsoft's linker, so that coLinux's build system basicly compiles the driver using the toolchain just until the final stage where it produces driver.o. Then, that file is passed to the DDK in order to be linked into linux.sys. I thought about 2 methods that can help us get rid of this dependency. * Try to use the cygwin toolchain solely in order to link a valid linux.sys. ReactOS's developers use this method in order to link their Windows-compatible drivers that load on ReactOS. However, Windows does more sanity checks when loading a driver than ReactOS, and because of that, I have yet managed to produced a .sys file that Windows will accept using this method. * Write a util that converts a .o file to a .sys file. After driver.o is linked with libntoskrnl.a and libhal.a using cygwin's ld, an .o file with no undefined symbols is produced - which means that no other input files are needed, and this .o file contains all the information that is needed in order to produce the .sys. Which method sounds more plausible? The first probably involves modifying existing binutils code. The second involves writing a separate util, but requires a rather complete knowledge about the file format and structures. -- Dan Aloni da...@gm... |
|
From: ePAc <ep...@ko...> - 2004-01-30 18:52:51
|
so i went to see where i could get the requisite for compiling the project. with the help of the previous discussion, i managed to snatch the proper "mxml" package (not the miniXML perl package). now i'm stuck. it appears that since Jan 4th 2004, the Windows DDK is payware. you can buy the CD, but no longer download it unless you have access to MSDN (about $700 for the basic new subscription to the required level to get the DDK). that's a little arsh for something that used to be free... now that said, i can't wait for the release of the binary.. :o) Thanks, Jok --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ |
|
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/ |
|
From: Ian L. <Ian...@mq...> - 2004-01-29 11:15:46
|
> According to Ian Latter, The openMosix patch already applies nicely > along with the Cooperative patch. I think is a good chance the MOSIX > patch will get along as well. Err ... not quite "nicely" ;-) You both shoot for the same entry point to the system call code. And with it patched, there still remains a couple of questions (that I hope to be able to answer before/on the weekend); - will freeswan patch into it nicely - will it run when its built ;-) The world becomes an interesting place when linux is a virtual operating environment, in which it runs as a piece of a larger virtual Single System Image. -- 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/ |
|
From: Ian L. <Ian...@mq...> - 2004-01-29 09:07:13
|
> > Interesting. Adding a Windows box to an openMosix cluster sounds quite > > useful. I never thought about the use for coLinux. > > Interesting. I'm not sure how feasible it is, however, at this > stage. The first obstacle I can see is network support - does coLinux > support shared access to the NIC? Sure - status page says that it "works" - apparently we have access via the Win32 TAP driver; http://www.colinux.org/?section=status -- 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/ |
|
From: Dan A. <da...@gm...> - 2004-01-29 05:10:09
|
On Tue, Jan 27, 2004 at 07:50:45AM +1000, Ian Latter wrote: > Hello, > > I contact this list as there is no relevant FAQ, Forum notes, User > mailling list, mailling list archives or CVS files -- that I can see. I > am one of three maintainers for the CHAOS live linux CD. CHAOS > specialises in being "the supercomputer for your wallet", booting > openMosix from a business-card sized disc. I would very much > like CHAOS to run as an application under Windows2K/XP .. as > would the openMosix community. Interesting. Adding a Windows box to an openMosix cluster sounds quite useful. I never thought about the use for coLinux. 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 have downloaded the only source code that is publically listed > (at sourceforge). It patches roughly with kernel 2.4.24 and the > beta openMosix 2.4.24 patch -- I've cleaned up the edges, it all > looks pretty good. > > However, the patch file "linux" from the colinux package adds > an include reference to linux/include/asm-i386/io.h for the file > linux/colinux.h ... but the patch file (nor any of the supplied source > code) includes linux/colinux.h linux/cooperative.h was previously linux/colinux.h. I renamed that header at one point and forget about that include instance. > 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. -- Dan Aloni da...@gm... |
|
From: Ian C. B. <ia...@bl...> - 2004-01-29 00:28:21
|
On Thu, Jan 29, 2004 at 12:42:30AM +0200, Shachar Shemesh wrote: > While it's certainly an exiting project, I understood that it was NOT > based on the Windows subsystem mechanism, but rather hacking your way > into Windows NT's ring 0 using a device driver. While I'm a great fan of > "if it works", wouldn't it be nicer, long run, to have a proper > subsystem of it? Why work within Microsoft's cludgy POSIX subsystem shenanigans? There's something very alluring to having a Linux kernel running at ring 0 in parallel with OTHER kernels. Think of Linux X86 images running on a Linux X86 host without UML or VMWare, running Linux PPC images on a Darwin box, or Linux Sparc images on a Solaris box - why limit this architecture purely to Microsoft? > Also, what are you planning on doing with graphic applications? CoLinux > works by running a X server on the windows machine. That's probably not > the best solution there is. How is the ReactOS windowing back-end > implemented? I'm more interested in running headless servers myself. If I *really* need a head, I have ssh tunnelled X11 or tight VNC sessions. To truely grasp the importance what CoLinux offers, think hugely scalable hosting farm. The closest thing to CoLinux at the moment is really the Xen Hypervisor: http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ Unfortunately, Xen isn't cross architecture, and you need to retrofit other kernels to run under it (see the Windows XP port limited to academic source licensees, or the recent NetBSD port to the same). At the moment, UML is the hosting platform of choice for virtual Linux servers - but there are real speed and minor irritating stability issues. Xen has its own LVM like virtual disk system in 1.2 - there is only planned support for UBD style devices, and all domains must access the disk simultaneously. Both Plex86 and Fabrice Bellard's QEMU have slightly modified kernels that can run across platforms and virtualize kernels in a somewhat similar way (though on a simulated or vitualized system without a ring 0 driver hack). I would LOVE to have a Linux self-hosted, ring 0 device driver driven, generic virtual machine subsystem for Linux that does not require Jeff Dyke's user-space hacks to work (no offense intended toward Jeff Dyke's incredible accomplishments with UML). There are a suprising number of people quietly following this train of thought. The early adopters are already running farms of hundreds (soon to be thousands) of virtual machines in clustered Linux farms. If there were a way to run CoLinux on an OpenSSI Linux cluster right now, you better believe we would already be doing it. - Ian C. Blenke <ia...@bl...> |
|
From: Dan A. <da...@gm...> - 2004-01-28 22:58:44
|
On Tue, Jan 27, 2004 at 06:56:40AM +0900, Digital Infra, Inc. wrote: > The first! Hmmm, Okajima, that looks like a Slashdot first post comment. Sorry, but you missed it by a few days :). Now, let's return to be on topic in this list, shall we? -- Dan Aloni da...@gm... |
|
From: Shachar S. <win...@sh...> - 2004-01-28 22:53:35
|
Steven Edwards wrote: >My plan is to work with the CoLinux team to integrate CoLinux in to >Windows and ReactOS as a POSIX subsystem. They are very interested in >working with us on this project and have linked to reactos.com on the >website. > > My entire experience with CoLinux has to do with Dan Aloni grabbing me at a random hall a few weeks ago and telling me about it (actually - the first he did it was about half a year ago, but he really got my attention, making me late for a meeting, this time around). While it's certainly an exiting project, I understood that it was NOT based on the Windows subsystem mechanism, but rather hacking your way into Windows NT's ring 0 using a device driver. While I'm a great fan of "if it works", wouldn't it be nicer, long run, to have a proper subsystem of it? Also, what are you planning on doing with graphic applications? CoLinux works by running a X server on the windows machine. That's probably not the best solution there is. How is the ReactOS windowing back-end implemented? Shachar |
|
From: Dan A. <da...@gm...> - 2004-01-28 22:48:30
|
On Wed, Jan 28, 2004 at 02:50:36PM +0100, Favre Benoit wrote: > hello, > do you think that the MOSIX kernel patch would work with coLinux. > > I work in a university where thousands of windows computers are unused during > night and hollyday time. A "screensaver" version of coLinux with MOSIX > support could lead to great supercomputing clusters with a very simple > deployment (i currently use clusterknoppix, the mosix/knoppix distribution > but it implies a machine reboot). According to Ian Latter, The openMosix patch already applies nicely along with the Cooperative patch. I think is a good chance the MOSIX patch will get along as well. -- Dan Aloni da...@gm... |
|
From: Dan A. <da...@gm...> - 2004-01-28 22:13:04
|
On Wed, Jan 28, 2004 at 12:12:56PM +0100, Szalai Ferenc wrote: > Hi > > I attached a small patch which basically make some little changes in > Makefiles of CoLinux to be the compileing more easiest. I think you misunderstood the Makefile strategy in the coLinux tree. The tree is actually a flat tree. The top Makefile includes the subdir Makefiles, and so on. There is no recursive invocation of make, so the 'all' target is evaluated several times if that patch applied. But it will work quite well if you move these declarations to the 'ifeq $(BUILD_ROOT) ... else' block. This way they would get prepended at the beginning of the evaluation, and only for the evaluation from that directory. I'd add that, thanks. > I agree with Jeff Lawson who said that just refer to MiniXML in README > isn't enough because there is a PHP/PERL based MiniXML project as well > (and the eg. the google will found this first) > > I think our library is found here: > http://www.easysw.com/~mike/mxml/ Yep, I'll fix that. -- Dan Aloni da...@gm... |
|
From: Dan A. <da...@gm...> - 2004-01-28 21:59:10
|
Hey everyone, This patch against the previously released tarball, adds the missing files, fixes the colinux.h include, and adds a few more stuff. This weekend I plan to do some advancements, some of them, include getting rid of the DDK build dependency. There are numerous ways in which you can help with that, I'll write more about it ahead. diff -urN colinux-20040119/ChangeLog colinux-20040128/ChangeLog --- colinux-20040119/ChangeLog 1970-01-01 02:00:00.000000000 +0200 +++ colinux-20040128/ChangeLog 2004-01-27 01:01:26.000000000 +0200 @@ -0,0 +1,4 @@ +Version 0.5.2 + * Added some missing files to the build tree + * doc/cygwin-cross-build - How to build a cygwin cross compilation tools + on Linux. diff -urN colinux-20040119/conf/README colinux-20040128/conf/README --- colinux-20040119/conf/README 1970-01-01 02:00:00.000000000 +0200 +++ colinux-20040128/conf/README 2004-01-19 17:42:07.000000000 +0200 @@ -0,0 +1,4 @@ +This directory contains example configuration files for the coLinux daemon. + +It also contain a configuration file that can be used as a .config for +compling the cooperative Linux kernel. \ No newline at end of file diff -urN colinux-20040119/conf/default.colinux.xml colinux-20040128/conf/default.colinux.xml --- colinux-20040119/conf/default.colinux.xml 1970-01-01 02:00:00.000000000 +0200 +++ colinux-20040128/conf/default.colinux.xml 2004-01-19 17:22:03.000000000 +0200 @@ -0,0 +1,8 @@ +<?xml version="1.0" encoding="UTF-8"?> +<colinux> + <block_device index="0" path="\DosDevices\c:\colinux\root_fs" enabled="true"> + <block_device index="1" path="\DosDevices\c:\colinux\swap_device" enabled="true"> + </block_device> + <bootparams>init=/bin/bash</bootparams> + <image path="vmlinux"></image> +</colinux> diff -urN colinux-20040119/conf/linux-config colinux-20040128/conf/linux-config --- colinux-20040119/conf/linux-config 1970-01-01 02:00:00.000000000 +0200 +++ colinux-20040128/conf/linux-config 2004-01-26 23:13:01.000000000 +0200 @@ -0,0 +1,515 @@ +# +# Automatically generated make config: don't edit +# +CONFIG_X86=y +# CONFIG_SBUS is not set +CONFIG_UID16=y + +# +# Code maturity level options +# +CONFIG_EXPERIMENTAL=y + +# +# Loadable module support +# +CONFIG_MODULES=y +CONFIG_MODVERSIONS=y +CONFIG_KMOD=y + +# +# Processor type and features +# +CONFIG_M386=y +# CONFIG_M486 is not set +# CONFIG_M586 is not set +# CONFIG_M586TSC is not set +# CONFIG_M586MMX is not set +# CONFIG_M686 is not set +# CONFIG_MPENTIUMIII is not set +# CONFIG_MPENTIUM4 is not set +# CONFIG_MK6 is not set +# CONFIG_MK7 is not set +# CONFIG_MK8 is not set +# CONFIG_MELAN is not set +# CONFIG_MCRUSOE is not set +# CONFIG_MWINCHIPC6 is not set +# CONFIG_MWINCHIP2 is not set +# CONFIG_MWINCHIP3D is not set +# CONFIG_MCYRIXIII is not set +# CONFIG_MVIAC3_2 is not set +# CONFIG_X86_CMPXCHG is not set +# CONFIG_X86_XADD is not set +CONFIG_X86_L1_CACHE_SHIFT=4 +CONFIG_RWSEM_GENERIC_SPINLOCK=y +# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set +CONFIG_X86_PPRO_FENCE=y +# CONFIG_X86_F00F_WORKS_OK is not set +# CONFIG_X86_MCE is not set +# CONFIG_TOSHIBA is not set +# CONFIG_I8K is not set +# CONFIG_MICROCODE is not set +# CONFIG_X86_MSR is not set +# CONFIG_X86_CPUID is not set +# CONFIG_EDD is not set +CONFIG_NOHIGHMEM=y +# CONFIG_HIGHMEM4G is not set +# CONFIG_HIGHMEM64G is not set +# CONFIG_HIGHMEM is not set +# CONFIG_MATH_EMULATION is not set +# CONFIG_MTRR is not set +# CONFIG_SMP is not set +CONFIG_X86_UP_COPIC=y +CONFIG_X86_COPIC=y +# CONFIG_X86_TSC_DISABLE is not set +CONFIG_X86_TSC=y + +# +# General setup +# +CONFIG_NET=y +# CONFIG_PCI is not set +# CONFIG_ISA is not set +# CONFIG_EISA is not set +# CONFIG_MCA is not set +# CONFIG_HOTPLUG is not set +# CONFIG_PCMCIA is not set +# CONFIG_HOTPLUG_PCI is not set +CONFIG_SYSVIPC=y +# CONFIG_BSD_PROCESS_ACCT is not set +CONFIG_SYSCTL=y +CONFIG_KCORE_ELF=y +# CONFIG_KCORE_AOUT is not set +CONFIG_BINFMT_AOUT=y +CONFIG_BINFMT_ELF=y +CONFIG_BINFMT_MISC=y +# CONFIG_PM is not set +# CONFIG_APM_IGNORE_USER_SUSPEND is not set +# CONFIG_APM_DO_ENABLE is not set +# CONFIG_APM_CPU_IDLE is not set +# CONFIG_APM_DISPLAY_BLANK is not set +# CONFIG_APM_RTC_IS_GMT is not set +# CONFIG_APM_ALLOW_INTS is not set +# CONFIG_APM_REAL_MODE_POWER_OFF is not set +CONFIG_COOPERATIVE=y + +# +# ACPI Support +# +# CONFIG_ACPI is not set + +# +# Memory Technology Devices (MTD) +# +# CONFIG_MTD is not set + +# +# Parallel port support +# +# CONFIG_PARPORT is not set + +# +# Plug and Play configuration +# +# CONFIG_PNP is not set + +# +# Block devices +# +# CONFIG_BLK_DEV_FD is not set +CONFIG_BLK_DEV_LOOP=y +# CONFIG_BLK_DEV_NBD is not set +CONFIG_BLK_DEV_RAM=y +CONFIG_BLK_DEV_RAM_SIZE=4096 +# CONFIG_BLK_DEV_INITRD is not set +CONFIG_BLK_DEV_PBD=y +CONFIG_BLK_STATS=y + +# +# Multi-device support (RAID and LVM) +# +# CONFIG_MD is not set + +# +# Networking options +# +CONFIG_PACKET=y +# CONFIG_PACKET_MMAP is not set +CONFIG_NETLINK_DEV=y +# CONFIG_NETFILTER is not set +# CONFIG_FILTER is not set +CONFIG_UNIX=y +CONFIG_INET=y +# CONFIG_IP_MULTICAST is not set +# CONFIG_IP_ADVANCED_ROUTER is not set +# CONFIG_IP_PNP is not set +# CONFIG_NET_IPIP is not set +# CONFIG_NET_IPGRE is not set +# CONFIG_ARPD is not set +# CONFIG_INET_ECN is not set +# CONFIG_SYN_COOKIES is not set +# CONFIG_IPV6 is not set +# CONFIG_KHTTPD is not set + +# +# SCTP Configuration (EXPERIMENTAL) +# +CONFIG_IPV6_SCTP__=y +# CONFIG_IP_SCTP is not set +# CONFIG_ATM is not set +# CONFIG_VLAN_8021Q is not set + +# +# +# +# CONFIG_IPX is not set +# CONFIG_ATALK is not set + +# +# Appletalk devices +# +# CONFIG_DECNET is not set +# CONFIG_BRIDGE is not set +# CONFIG_X25 is not set +# CONFIG_LAPB is not set +# CONFIG_LLC is not set +# CONFIG_NET_DIVERT is not set +# CONFIG_ECONET is not set +# CONFIG_WAN_ROUTER is not set +# CONFIG_NET_FASTROUTE is not set +# CONFIG_NET_HW_FLOWCONTROL is not set + +# +# QoS and/or fair queueing +# +# CONFIG_NET_SCHED is not set + +# +# Network testing +# +# CONFIG_NET_PKTGEN is not set + +# +# Telephony Support +# +# CONFIG_PHONE is not set + +# +# ATA/IDE/MFM/RLL support +# +# CONFIG_IDE is not set +# CONFIG_BLK_DEV_IDE_MODES is not set +# CONFIG_BLK_DEV_HD is not set + +# +# SCSI support +# +# CONFIG_SCSI is not set + +# +# Fusion MPT device support +# +# CONFIG_FUSION_BOOT is not set +# CONFIG_FUSION_ISENSE is not set +# CONFIG_FUSION_CTL is not set +# CONFIG_FUSION_LAN is not set + +# +# I2O device support +# +# CONFIG_I2O is not set + +# +# Network device support +# +CONFIG_NETDEVICES=y + +# +# ARCnet devices +# +# CONFIG_ARCNET is not set +# CONFIG_DUMMY is not set +# CONFIG_BONDING is not set +# CONFIG_EQUALIZER is not set +# CONFIG_TUN is not set +# CONFIG_ETHERTAP is not set + +# +# Ethernet (10 or 100Mbit) +# +# CONFIG_NET_ETHERNET is not set + +# +# Ethernet (1000 Mbit) +# +# CONFIG_ACENIC_OMIT_TIGON_I is not set +# CONFIG_E1000_NAPI is not set +CONFIG_COOPERATIVE_CONET=y +# CONFIG_FDDI is not set +# CONFIG_HIPPI is not set +# CONFIG_PPP is not set +# CONFIG_SLIP is not set + +# +# Wireless LAN (non-hamradio) +# +# CONFIG_NET_RADIO is not set + +# +# Token Ring devices +# +# CONFIG_TR is not set +# CONFIG_NET_FC is not set +# CONFIG_SHAPER is not set + +# +# Wan interfaces +# +# CONFIG_WAN is not set + +# +# Amateur Radio support +# +# CONFIG_HAMRADIO is not set + +# +# IrDA (infrared) support +# +# CONFIG_IRDA is not set + +# +# ISDN subsystem +# +# CONFIG_ISDN is not set + +# +# Input core support +# +# CONFIG_INPUT is not set +CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 +CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 + +# +# Character devices +# +CONFIG_VT=y +CONFIG_VT_CONSOLE=y +# CONFIG_SERIAL is not set +# CONFIG_SERIAL_NONSTANDARD is not set +CONFIG_UNIX98_PTYS=y +CONFIG_UNIX98_PTY_COUNT=256 + +# +# I2C support +# +# CONFIG_I2C is not set + +# +# Mice +# +# CONFIG_BUSMOUSE is not set +# CONFIG_MOUSE is not set + +# +# Joysticks +# +# CONFIG_INPUT_GAMEPORT is not set + +# +# Input core support is needed for gameports +# + +# +# Input core support is needed for joysticks +# +# CONFIG_QIC02_TAPE is not set +# CONFIG_IPMI_HANDLER is not set + +# +# Watchdog Cards +# +# CONFIG_WATCHDOG is not set +# CONFIG_SCx200_GPIO is not set +# CONFIG_NVRAM is not set +# CONFIG_RTC is not set +# CONFIG_DTLK is not set +# CONFIG_R3964 is not set +# CONFIG_APPLICOM is not set + +# +# Ftape, the floppy tape device driver +# +# CONFIG_FTAPE is not set +# CONFIG_AGP is not set + +# +# Direct Rendering Manager (XFree86 DRI support) +# +# CONFIG_DRM is not set +# CONFIG_MWAVE is not set + +# +# Multimedia devices +# +# CONFIG_VIDEO_DEV is not set + +# +# File systems +# +# CONFIG_QUOTA is not set +# CONFIG_AUTOFS_FS is not set +CONFIG_AUTOFS4_FS=y +# CONFIG_REISERFS_FS is not set +# CONFIG_ADFS_FS is not set +# CONFIG_AFFS_FS is not set +# CONFIG_HFS_FS is not set +# CONFIG_HFSPLUS_FS is not set +# CONFIG_BEFS_FS is not set +# CONFIG_BFS_FS is not set +CONFIG_EXT3_FS=y +CONFIG_JBD=y +# CONFIG_JBD_DEBUG is not set +CONFIG_FAT_FS=m +CONFIG_MSDOS_FS=m +# CONFIG_UMSDOS_FS is not set +CONFIG_VFAT_FS=m +# CONFIG_EFS_FS is not set +# CONFIG_CRAMFS is not set +CONFIG_TMPFS=y +CONFIG_RAMFS=y +CONFIG_ISO9660_FS=m +CONFIG_JOLIET=y +CONFIG_ZISOFS=y +# CONFIG_JFS_FS is not set +# CONFIG_MINIX_FS is not set +# CONFIG_VXFS_FS is not set +# CONFIG_NTFS_FS is not set +# CONFIG_HPFS_FS is not set +CONFIG_PROC_FS=y +# CONFIG_DEVFS_FS is not set +CONFIG_DEVPTS_FS=y +# CONFIG_QNX4FS_FS is not set +# CONFIG_ROMFS_FS is not set +CONFIG_EXT2_FS=y +# CONFIG_SYSV_FS is not set +# CONFIG_UDF_FS is not set +# CONFIG_UFS_FS is not set + +# +# Network File Systems +# +# CONFIG_CODA_FS is not set +# CONFIG_INTERMEZZO_FS is not set +# CONFIG_NFS_FS is not set +# CONFIG_NFSD is not set +# CONFIG_SUNRPC is not set +# CONFIG_LOCKD is not set +# CONFIG_SMB_FS is not set +# CONFIG_NCP_FS is not set +CONFIG_ZISOFS_FS=m + +# +# Partition Types +# +# CONFIG_PARTITION_ADVANCED is not set +CONFIG_MSDOS_PARTITION=y +# CONFIG_SMB_NLS is not set +CONFIG_NLS=y + +# +# Native Language Support +# +CONFIG_NLS_DEFAULT="iso8859-1" +# CONFIG_NLS_CODEPAGE_437 is not set +# CONFIG_NLS_CODEPAGE_737 is not set +# CONFIG_NLS_CODEPAGE_775 is not set +# CONFIG_NLS_CODEPAGE_850 is not set +# CONFIG_NLS_CODEPAGE_852 is not set +# CONFIG_NLS_CODEPAGE_855 is not set +# CONFIG_NLS_CODEPAGE_857 is not set +# CONFIG_NLS_CODEPAGE_860 is not set +# CONFIG_NLS_CODEPAGE_861 is not set +# CONFIG_NLS_CODEPAGE_862 is not set +# CONFIG_NLS_CODEPAGE_863 is not set +# CONFIG_NLS_CODEPAGE_864 is not set +# CONFIG_NLS_CODEPAGE_865 is not set +# CONFIG_NLS_CODEPAGE_866 is not set +# CONFIG_NLS_CODEPAGE_869 is not set +# CONFIG_NLS_CODEPAGE_936 is not set +# CONFIG_NLS_CODEPAGE_950 is not set +# CONFIG_NLS_CODEPAGE_932 is not set +# CONFIG_NLS_CODEPAGE_949 is not set +# CONFIG_NLS_CODEPAGE_874 is not set +# CONFIG_NLS_ISO8859_8 is not set +# CONFIG_NLS_CODEPAGE_1250 is not set +# CONFIG_NLS_CODEPAGE_1251 is not set +# CONFIG_NLS_ISO8859_1 is not set +# CONFIG_NLS_ISO8859_2 is not set +# CONFIG_NLS_ISO8859_3 is not set +# CONFIG_NLS_ISO8859_4 is not set +# CONFIG_NLS_ISO8859_5 is not set +# CONFIG_NLS_ISO8859_6 is not set +# CONFIG_NLS_ISO8859_7 is not set +# CONFIG_NLS_ISO8859_9 is not set +# CONFIG_NLS_ISO8859_13 is not set +# CONFIG_NLS_ISO8859_14 is not set +# CONFIG_NLS_ISO8859_15 is not set +# CONFIG_NLS_KOI8_R is not set +# CONFIG_NLS_KOI8_U is not set +# CONFIG_NLS_UTF8 is not set + +# +# Console drivers +# +CONFIG_COOPERATIVE_CONSOLE=y +# CONFIG_VIDEO_SELECT is not set +# CONFIG_MDA_CONSOLE is not set + +# +# Frame-buffer support +# +# CONFIG_FB is not set + +# +# Sound +# +# CONFIG_SOUND is not set + +# +# USB support +# + +# +# Support for USB gadgets +# +# CONFIG_USB_GADGET is not set + +# +# Bluetooth support +# +# CONFIG_BLUEZ is not set + +# +# Kernel hacking +# +CONFIG_DEBUG_KERNEL=y +# CONFIG_DEBUG_STACKOVERFLOW is not set +# CONFIG_DEBUG_HIGHMEM is not set +# CONFIG_DEBUG_SLAB is not set +# CONFIG_DEBUG_IOVIRT is not set +# CONFIG_MAGIC_SYSRQ is not set +# CONFIG_DEBUG_SPINLOCK is not set +CONFIG_FRAME_POINTER=y +CONFIG_LOG_BUF_SHIFT=0 + +# +# Cryptographic options +# +# CONFIG_CRYPTO is not set + +# +# Library routines +# +CONFIG_CRC32=m +CONFIG_ZLIB_INFLATE=m +CONFIG_ZLIB_DEFLATE=m diff -urN colinux-20040119/doc/cygwin-cross-build colinux-20040128/doc/cygwin-cross-build --- colinux-20040119/doc/cygwin-cross-build 1970-01-01 02:00:00.000000000 +0200 +++ colinux-20040128/doc/cygwin-cross-build 2004-01-27 01:29:39.000000000 +0200 @@ -0,0 +1,51 @@ +Building Cygwin cross compilation tools for Linux +================================================= + +First, choose an installation directory, for example: /usr/local/w32build. +I'd refer to that directory as $PREFIX from this point in the document. + +Download the latest base cygwin tarball from cygwin.com, for example, +http://mirrors.xmission.com/cygwin/release/cygwin/cygwin-1.5.7-1.tar.bz2 + +Extract that tarball to the installation directory in this manner: + + tar -xjf cygwin-1.5.7-1.tar.bz2 + rename usr i686-pc-cygwin + +Now you have a ready $PREFIX/i686-pc-cygwin directory. + + +Download binutils from GNU's website. Configure, build and install with: + + ./configure --target=i686-pc-cygwin --prefix=$PREFIX + make + make install + + +Download the latest gcc sources, both the gcc-core and gcc-g++ parts. Extract +those in a separate directory, and build gcc using this procedure: + + ./configure --prefix=$PREFIX -host=i686-pc-linux-gnu --target=i686-pc-cygwin --enable-languages=c,c++ + +Run make, but it would fail at some point: + + make + +It's a chicken and egg problem. It fails because the i686-pc-cygwin-* compiler +is not installed yet in $PREFIX (and accessable from $PATH). Run (with the +proper privlieges): + + make install + +Make sure that i686-pc-cygwin-gcc is accessable from $PATH. In gcc's build +directory, run again: + + make + +It should now properly build the standard libs with the start object files. +And then again run (with the proper privlieges): + + make install + +To test it, try to produce a .exe file from a 'void main(){}' C program, +using i686-pc-cygwin-gcc. diff -urN colinux-20040119/patch/linux colinux-20040128/patch/linux --- colinux-20040119/patch/linux 2004-01-19 18:25:41.000000000 +0200 +++ colinux-20040128/patch/linux 2004-01-27 00:04:02.000000000 +0200 @@ -3326,7 +3326,7 @@ #define __TSS(n) (((n)<<2) + __FIRST_TSS_ENTRY) diff -X bin/dontdiff -urN linux/include/asm-i386/dma.h linux/include/asm-i386/dma.h --- linux/include/asm-i386/dma.h 2004-01-05 05:39:23.000000000 +0200 -+++ linux/include/asm-i386/dma.h 2003-12-20 03:01:30.000000000 +0200 ++++ linux/include/asm-i386/dma.h 2004-01-26 23:39:36.000000000 +0200 @@ -268,6 +268,8 @@ * * Assumes DMA flip-flop is clear. @@ -3347,7 +3347,7 @@ extern int request_dma(unsigned int dmanr, const char * device_id); /* reserve a DMA channel */ diff -X bin/dontdiff -urN linux/include/asm-i386/io.h linux/include/asm-i386/io.h --- linux/include/asm-i386/io.h 2004-01-05 05:39:23.000000000 +0200 -+++ linux/include/asm-i386/io.h 2003-12-26 18:28:26.000000000 +0200 ++++ linux/include/asm-i386/io.h 2004-01-27 00:00:07.000000000 +0200 @@ -2,6 +2,7 @@ #define _ASM_IO_H @@ -3356,18 +3356,15 @@ /* * This file contains the definitions for the x86 IO instructions -@@ -46,6 +47,10 @@ +@@ -45,6 +46,7 @@ + #ifdef __KERNEL__ #include <linux/vmalloc.h> ++#include <linux/cooperative.h> -+#ifdef CONFIG_COOPERATIVE -+#include <linux/colinux.h> -+#endif -+ /* * Temporary debugging check to catch old code using - * unmapped ISA addresses. Will be removed in 2.4. -@@ -121,6 +126,10 @@ +@@ -121,6 +123,10 @@ static inline void * ioremap (unsigned long offset, unsigned long size) { @@ -3378,7 +3375,7 @@ return __ioremap(offset, size, 0); } -@@ -146,6 +155,10 @@ +@@ -146,6 +152,10 @@ static inline void * ioremap_nocache (unsigned long offset, unsigned long size) { @@ -3389,7 +3386,7 @@ return __ioremap(offset, size, _PAGE_PCD); } -@@ -308,6 +321,8 @@ +@@ -308,6 +318,8 @@ #endif /* __KERNEL__ */ @@ -3398,7 +3395,7 @@ #ifdef SLOW_IO_BY_JUMPING #define __SLOW_DOWN_IO "\njmp 1f\n1:\tjmp 1f\n1:" #else -@@ -427,4 +442,19 @@ +@@ -427,4 +439,19 @@ __OUTS(w) __OUTS(l) @@ -3443,7 +3440,7 @@ #define NR_IRQS 16 diff -X bin/dontdiff -urN linux/include/asm-i386/mmu_context.h linux/include/asm-i386/mmu_context.h --- linux/include/asm-i386/mmu_context.h 2004-01-05 05:37:17.000000000 +0200 -+++ linux/include/asm-i386/mmu_context.h 2003-12-20 02:42:52.000000000 +0200 ++++ linux/include/asm-i386/mmu_context.h 2004-01-26 23:39:35.000000000 +0200 @@ -41,6 +41,7 @@ #endif set_bit(cpu, &next->cpu_vm_mask); @@ -3521,7 +3518,7 @@ #define VM_DATA_DEFAULT_FLAGS (VM_READ | VM_WRITE | VM_EXEC | \ diff -X bin/dontdiff -urN linux/include/asm-i386/pgalloc.h linux/include/asm-i386/pgalloc.h --- linux/include/asm-i386/pgalloc.h 2004-01-05 05:37:14.000000000 +0200 -+++ linux/include/asm-i386/pgalloc.h 2003-12-20 02:42:48.000000000 +0200 ++++ linux/include/asm-i386/pgalloc.h 2004-01-26 23:39:33.000000000 +0200 @@ -11,8 +11,13 @@ #define pte_quicklist (current_cpu_data.pte_quick) #define pgtable_cache_size (current_cpu_data.pgtable_cache_sz) @@ -3558,7 +3555,7 @@ #endif /* _I386_PGTABLE_2LEVEL_H */ diff -X bin/dontdiff -urN linux/include/asm-i386/pgtable.h linux/include/asm-i386/pgtable.h --- linux/include/asm-i386/pgtable.h 2004-01-05 05:37:14.000000000 +0200 -+++ linux/include/asm-i386/pgtable.h 2003-12-20 02:42:48.000000000 +0200 ++++ linux/include/asm-i386/pgtable.h 2004-01-26 23:39:33.000000000 +0200 @@ -320,8 +320,13 @@ #define page_pte(page) page_pte_prot(page, __pgprot(0)) @@ -3576,7 +3573,7 @@ #define pgd_index(address) ((address >> PGDIR_SHIFT) & (PTRS_PER_PGD-1)) diff -X bin/dontdiff -urN linux/include/asm-i386/processor.h linux/include/asm-i386/processor.h --- linux/include/asm-i386/processor.h 2004-01-05 05:37:14.000000000 +0200 -+++ linux/include/asm-i386/processor.h 2003-12-13 17:17:01.000000000 +0200 ++++ linux/include/asm-i386/processor.h 2004-01-26 23:39:33.000000000 +0200 @@ -181,8 +181,18 @@ #define X86_CR4_OSFXSR 0x0200 /* enable fast FPU save and restore */ #define X86_CR4_OSXMMEXCPT 0x0400 /* enable unmasked SSE exceptions */ @@ -3625,7 +3622,7 @@ #endif diff -X bin/dontdiff -urN linux/include/linux/console.h linux/include/linux/console.h --- linux/include/linux/console.h 2004-01-05 05:37:20.000000000 +0200 -+++ linux/include/linux/console.h 2003-12-13 17:33:48.000000000 +0200 ++++ linux/include/linux/console.h 2004-01-26 23:39:38.000000000 +0200 @@ -55,6 +55,7 @@ extern const struct consw dummy_con; /* dummy console buffer */ extern const struct consw fb_con; /* frame buffer based console */ @@ -3636,7 +3633,7 @@ diff -X bin/dontdiff -urN linux/include/linux/cooperative.h linux/include/linux/cooperative.h --- linux/include/linux/cooperative.h 1970-01-01 02:00:00.000000000 +0200 -+++ linux/include/linux/cooperative.h 2003-12-27 11:46:21.000000000 +0200 ++++ linux/include/linux/cooperative.h 2004-01-24 10:19:19.000000000 +0200 @@ -0,0 +1,173 @@ +#ifndef __LINUX_COOPERATIVE_H__ +#define __LINUX_COOPERATIVE_H__ diff -urN colinux-20040119/src/colinux/os/winnt/build/Makefile colinux-20040128/src/colinux/os/winnt/build/Makefile --- colinux-20040119/src/colinux/os/winnt/build/Makefile 1970-01-01 02:00:00.000000000 +0200 +++ colinux-20040128/src/colinux/os/winnt/build/Makefile 2004-01-19 18:33:28.000000000 +0200 @@ -0,0 +1,85 @@ +# Standard Makefile header +ifeq ($(BUILD_ROOT),) +BUILD_ROOT=../../../.. +include $(BUILD_ROOT)/Makefile +else +BUILD_PATH := $(BUILD_PATH)/build +#----------------------------------------------------------------- + +LOCAL_TARGETS = $(BUILD_PATH)/driver.o + +$(BUILD_PATH)/driver.o : \ + $(BUILD_ROOT)/colinux/common/common.o \ + $(BUILD_ROOT)/colinux/kernel/kernel.o \ + $(BUILD_ROOT)/colinux/os/current/kernel/kernel.o \ + $(BUILD_ROOT)/colinux/arch/current/arch.o \ + + $(TOOL_LD_RELOC) + +DRIVER_TARGET := $(BUILD_PATH)/linux.sys + +WINDIR=$(WINUSER)@$(WINBOX):$(WINREMOTEDIR) +WINBOX_SCP=scp -i ~/.ssh/locallan +WINBOX_SSH=ssh -X -l $(WINUSER) -i ~/.ssh/locallan $(WINBOX) +WINLINK=$(WINBOX_SSH) /cygdrive/c/NTDDK/bin/link.exe + +WINLINK_FLAGS= \ + /machine:ix86 \ + /STACK:262144,4096 \ + /MERGE:_PAGE=PAGE \ + /MERGE:_TEXT=.text \ + /SECTION:INIT,d \ + /OPT:REF \ + /OPT:ICF \ + /IGNORE:4001,4037,4039,4044,4065,4070,4078,4087,4089,4198 \ + /INCREMENTAL:NO \ + /FULLBUILD \ + /FORCE:MULTIPLE \ + /NOCOMMENT \ + /release \ + /NODEFAULTLIB \ + /debug:FULL \ + /debugtype:cv \ + /version:5.00 \ + /osversion:5.00 \ + /optidata \ + /driver \ + /align:0x1000 \ + /filealign:0x1000 \ + /subsystem:native,5.00 \ + /base:0x10000 \ + /entry:DriverEntry@8 \ + +WINLINK_LIBS= \ + C:\\\\NTDDK\\\\libfre\\\\i386\\\\ntoskrnl.lib \ + C:\\\\NTDDK\\\\libfre\\\\i386\\\\hal.lib \ + C:\\\\NTDDK\\\\libfre\\\\i386\\\\wmilib.lib \ + +$(DRIVER_TARGET): $(BUILD_PATH)/driver.o + $(WINBOX_SCP) $^ $(WINDIR) + $(WINLINK) /out:$(notdir $@) $(WINLINK_FLAGS) $(notdir $^) $(WINLINK_LIBS) + $(WINBOX_SCP) $(WINDIR)$(notdir $@) $@ + +LOCAL_TARGET += $(DRIVER_TARGET) +LOCAL_FILES = \ + $(DRIVER_TARGET) \ + $(BUILD_ROOT)/../../linux/vmlinux \ + $(BUILD_ROOT)/colinux/os/current/user/daemon/colinux-daemon.exe \ + $(BUILD_ROOT)/colinux/os/current/user/console/colinux-console.exe \ + +colinux: $(LOCAL_FILES) + +upload: $(LOCAL_FILES) + $(WINBOX_SCP) $^ $(WINDIR) + +upload_console: $(BUILD_ROOT)/colinux/os/current/user/console/colinux-console.exe + $(WINBOX_SCP) $^ $(WINDIR) + +driver : $(BUILD_PATH)/driver.o + +CLEAN_FILES := $(CLEAN_FILES) \ + $(LOCAL_TARGETS) $(BUILD_PATH)/kernel.o + +#----------------------------------------------------------------- +BUILD_PATH := $(shell dirname $(BUILD_PATH)) +endif -- Dan Aloni da...@gm... |
|
From: Favre B. <ben...@li...> - 2004-01-28 13:54:00
|
hello,
do you think that the MOSIX kernel patch would work with coLinux.
I work in a university where thousands of windows computers are unused during
night and hollyday time. A "screensaver" version of coLinux with MOSIX
support could lead to great supercomputing clusters with a very simple
deployment (i currently use clusterknoppix, the mosix/knoppix distribution
but it implies a machine reboot).
regards,
--
Benoit Favre
tel: +33 (0)6 63 20 02 14
+33 (0)4 90 84 35 77
mail: ben...@li...
|
|
From: Szalai F. <sz...@ei...> - 2004-01-28 11:13:18
|
Hi I attached a small patch which basically make some little changes in Makefiles of CoLinux to be the compileing more easiest. I agree with Jeff Lawson who said that just refer to MiniXML in README isn't enough because there is a PHP/PERL based MiniXML project as well (and the eg. the google will found this first) I think our library is found here: http://www.easysw.com/~mike/mxml/ -- Regards Feri |
|
From: Jon S. <co...@pu...> - 2004-01-28 05:12:44
|
Is there an actual download somewhere? I just came across the site and = thought it looked interesting. But the one file that does work is = corrupted since it isn't a complete file. Thanks. |
|
From: Dan A. <da...@gm...> - 2004-01-27 21:02:41
|
Hello, As some of you noticed, the first public release of the coLinux sources was missing some files. This will be fixed in the next tarball. I must say that I am overwhelmed by the amount of E-Mails that I have received concerning this project and the numerous people who have volunteered to help. Your attention is very appreciated. I will also release my notes about how to set up a build enviroment for coLinux. Also, please note that the currently unreleased binaries are composed of several parts in order to work: 1. A vmlinux file. 2. The Windows linux.sys driver. 3. A root file system 4. Two programs (colinux-daemon.exe and colinux-console.exe) 5. The Win32TAP driver from the OpenVPN project, which is currently must be installed for the daemon to work. It provides the coLinux system with the virtual network link. Thank you for your patience. -- Dan Aloni da...@gm... |
|
From: Steven E. <ste...@ya...> - 2004-01-27 20:38:36
|
Hello All, Now that the word is out its time to fill you guys in. Over the past few months I have been working with a Project called Cooperative Linux. Cooperative Linux allows you to the Linux kernel as a process under Windows NT/2K. With CoLinux you can run any linux application under Windows. http://www.colinux.org/?section=screenshots My plan is to work with the CoLinux team to integrate CoLinux in to Windows and ReactOS as a POSIX subsystem. They are very interested in working with us on this project and have linked to reactos.com on the website. http://www.colinux.org Currently CoLinux depends on a driver that allows it to use the hardware MMU. It also currently depends on cygwin to be compiled. The first steps for developing this for ReactOS and other Win32 hosts will be to remove the cygwin dependancy. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ |
|
From: Jeff L. <jl...@bo...> - 2004-01-27 13:48:39
|
In the source tarball colinux-20040119.tar.gz it seems that there might be some files missing. In particular, I can't seem to find this file: src/colinux/os/winnt/build/Makefile (and anything else that is supposed to be in the winnt/build directory). I believe that Makefile is supposed to contain the main "colinux" and "upload" targets that are mentioned in the doc/building file. Additionally the pre-maid (sic) Linux kernel configuration file "../colinux/conf/kernel-config" mentioned in doc/building seems to have been omitted as well. I was able to create my own Linux config after applying the patch and selecting the CONFIG_COOPERATIVE and CONFIG_COOPERATIVE_CONSOLE options and disable most other unnecessary features however. I also encountered a gcc warning in src/colinux/arch/i386/passage.c due to its use of memset() without including the <string.h> header. Adding an include to that eliminated the warning. I would also recommend mentioning the URL to the "Minimal XML (mxml)" library (which is incorrectly referenced as "MiniXML") in the doc/building file. There is another library (for PHP and Perl) that is called "MiniXML" and would likely confuse people attempting to search for it. The URL to the correct project is http://mxml.sourceforge.net/ This project looks very promising. I have been aware of uml-win32 for many months already and been attempting to bring its kernel patches back up-to-date with some assistance from Chandan. However, its extensive changes to the Linux kernel source make it very difficult to maintain. Thanks. |
81 messages has been excluded from this view by a project administrator.
