From: Dan A. <da...@gm...> - 2004-02-25 03:24:56
|
This release brings the context switching code of coLinux much closer to completeness. It's the most sensitive code in this project but the most important one. I'd like to thank Alejandro R. Sedeno for the quick but excellent pcap-based Bridged Ethernet contribution, and also others who helped to debug other stuff that led to this release. * Version 0.5.4 AKA "Focal Segmental Glomerulosclerosis" (%gs/%fs) release * Fixed an issue with i686-optimized pthread and the preservation of %gs and %fs. The crashes that were caused by the i686 Gentoo image should now disappear. WINE would also work now ;) * cobd: Fixed accessing large block devices (1GB >). cobd0 was passing wrong information to userspace. * conet: Statistics are now gathered (patch by Pat Erley) * Tuned the time conversion between Windows and Linux. The machine is now initialized with the right date, not 4 days backwards. * Applied a configuration parsing fix (patch by Ballard Jonathan) * Some improvements of the switch code. We now preserve more registers, (MMX/SSE/SSE2/FP), and coLinux now has its own GDT. These changes should assure stability on more systems and processors. This fix also appears to solve the problem where processes were stuck on nanosleep() calls. * conet-pcap: pcap-based daemon (contributed by Alejandro R. Sedeno). * Network configuration is now handled in the coLinux configuration XML. For backward compatibility, add: <network index="0" name="TAP" type="tap"></network> If you want to use pcap (i.e, bridged Ethernet), add: <network index="0" name="XXXX" type="bridged"></network> (Where XXXX is a substring of your network adapter's name) Optional attributes: mac="XX:XX:XX:XX:XX:XX" - specifies the MAC address of the interface in the Linux side. Recommended on bridged networking setups, where more than one Windows machine will be running coLinux on the same subnet. I also prepared the ground for supporting more than one network device (i.e, eth1, eth2, etc.), but it is not yet completed. * linux: avoid more I/O in time.c. A side note: For the non-developers and developers among you: would anyone like to update the doc/running file, and whatever documentation files you see fit? -- Dan Aloni da...@gm... |
From: Alejandro R. S. <asedeno@MIT.EDU> - 2004-02-25 03:37:55
|
> * conet-pcap: pcap-based daemon (contributed by Alejandro R. Sedeno). This option only works with 802.3 (wired) networks, not 802.11 networks (or others for that matter). -Alejandro |
From: Christophe T. <ch...@ae...> - 2004-02-25 04:01:18
|
Hey Alejandro, Is it because of the fact that you need to put the card in promiscuous mode (or whatever that name is)? Because some 802.11 wireless PCMCIA cards support that mode fine. -Christophe ----- Original Message ----- From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> To: "Cooperative Linux Development" <col...@li...> Sent: Tuesday, February 24, 2004 7:28 PM Subject: Re: [coLinux-devel] coLinux 0.5.4 > > * conet-pcap: pcap-based daemon (contributed by Alejandro R. Sedeno). > > This option only works with 802.3 (wired) networks, not 802.11 networks > (or others for that matter). > > -Alejandro > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Alejandro R. S. <asedeno@MIT.EDU> - 2004-02-25 05:24:20
|
Nope, it's because I'm using winPCap to write out raw network frames, and passing incoming frames back to coLinux. coLinux's ethenet device believes it's on a wired network. As such it reads and writes 802.3 frames, which differ in form from 802.11 frames. -Alejandro On Tue, 2004-02-24 at 22:50, Christophe Thibault wrote: > Hey Alejandro, > > Is it because of the fact that you need to put the card in promiscuous mode > (or whatever that name is)? Because some 802.11 wireless PCMCIA cards > support that mode fine. > > -Christophe > > ----- Original Message ----- > From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> > To: "Cooperative Linux Development" <col...@li...> > Sent: Tuesday, February 24, 2004 7:28 PM > Subject: Re: [coLinux-devel] coLinux 0.5.4 > > > > > * conet-pcap: pcap-based daemon (contributed by Alejandro R. Sedeno). > > > > This option only works with 802.3 (wired) networks, not 802.11 networks > > (or others for that matter). > > > > -Alejandro > > > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Christophe T. <ch...@ae...> - 2004-02-25 05:54:59
|
I can't get the bridged (winpcap) networking to work, the colinux-bridged-net-daemon.exe crashes everytime I run colinux-daemon. I have the following line in my default.colinux.xml: <network index="0" type="bridged" name="Area"></network> 'name' is supposed to be a substring of one of the names of the adapters in Windows's configuration, right? I even tried with: <network index="0" type="bridged" name="Area" mac="44:55:12:18:0A:12"></network> And same thing happens. From the log: colinux: launching net daemons daemon: launching daemon for conet0 executing: colinux-bridged-net-daemon -i 0 -n Area -mac 44:55:12:18:0a:12 conet0: initialized 49 [main] colinux-bridged-net-daemon 1756 handle_exceptions: Exception: STA TUS_ACCESS_VIOLATION 649 [main] colinux-bridged-net-daemon 1756 open_stackdumpfile: Dumping stack trace to colinux-bridged-net-daemon.exe.stackdump co_message_switch: freeing rule for 8 daemon: module disconnected: conet0 -Christophe ----- Original Message ----- From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> To: "Christophe Thibault" <ch...@ae...> Cc: "Cooperative Linux Development" <col...@li...> Sent: Tuesday, February 24, 2004 9:15 PM Subject: Re: [coLinux-devel] coLinux 0.5.4 > Nope, it's because I'm using winPCap to write out raw network frames, > and passing incoming frames back to coLinux. coLinux's ethenet device > believes it's on a wired network. As such it reads and writes 802.3 > frames, which differ in form from 802.11 frames. > > -Alejandro > > On Tue, 2004-02-24 at 22:50, Christophe Thibault wrote: > > Hey Alejandro, > > > > Is it because of the fact that you need to put the card in promiscuous mode > > (or whatever that name is)? Because some 802.11 wireless PCMCIA cards > > support that mode fine. > > > > -Christophe > > > > ----- Original Message ----- > > From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> > > To: "Cooperative Linux Development" <col...@li... > > > Sent: Tuesday, February 24, 2004 7:28 PM > > Subject: Re: [coLinux-devel] coLinux 0.5.4 > > > > > > > > * conet-pcap: pcap-based daemon (contributed by Alejandro R. Sedeno). > > > > > > This option only works with 802.3 (wired) networks, not 802.11 networks > > > (or others for that matter). > > > > > > -Alejandro > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > Build and deploy apps & Web services for Linux with > > > a free DVD software kit from IBM. Click Now! > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > |
From: Alejandro R. S. <asedeno@MIT.EDU> - 2004-02-25 06:18:08
|
Assumption: You're trying to make it work with a connection called "Local Area Network" Perhaps the documentation needs to be a little clearer on what name means. It's refering to the description windows has for your NIC. Two ways to obtain that: 1) (GUI, XP) Highlight 'Local Area Network' in 'Network Connections', it's the last line in the Detail's box on the side. 2) (CLI) 'ipconfig /all'. It's the 'Description' line. Also, I'm noticing a sign extension bug has worked its way into the code. I'm going to try and patch it, sometime tonight. In the mean time, try to use MAC octets between 00 and 79. You'll know you're running into this bug if you see a line like: executing: colinux-bridged-net-daemon -i 0 -n foo -mac xx:xx:ffffff87... -Alejandro On Wed, 2004-02-25 at 00:44, Christophe Thibault wrote: > I can't get the bridged (winpcap) networking to work, the > colinux-bridged-net-daemon.exe crashes everytime I run colinux-daemon. > > I have the following line in my default.colinux.xml: > > <network index="0" type="bridged" name="Area"></network> > > 'name' is supposed to be a substring of one of the names of the adapters in > Windows's configuration, right? I even tried with: > > <network index="0" type="bridged" name="Area" > mac="44:55:12:18:0A:12"></network> > > And same thing happens. From the log: > > colinux: launching net daemons > daemon: launching daemon for conet0 > executing: colinux-bridged-net-daemon -i 0 -n Area -mac 44:55:12:18:0a:12 > conet0: initialized > 49 [main] colinux-bridged-net-daemon 1756 handle_exceptions: Exception: > STA > TUS_ACCESS_VIOLATION > 649 [main] colinux-bridged-net-daemon 1756 open_stackdumpfile: Dumping > stack > trace to colinux-bridged-net-daemon.exe.stackdump > co_message_switch: freeing rule for 8 > daemon: module disconnected: conet0 > > -Christophe > > > ----- Original Message ----- > From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> > To: "Christophe Thibault" <ch...@ae...> > Cc: "Cooperative Linux Development" <col...@li...> > Sent: Tuesday, February 24, 2004 9:15 PM > Subject: Re: [coLinux-devel] coLinux 0.5.4 > > > > Nope, it's because I'm using winPCap to write out raw network frames, > > and passing incoming frames back to coLinux. coLinux's ethenet device > > believes it's on a wired network. As such it reads and writes 802.3 > > frames, which differ in form from 802.11 frames. > > > > -Alejandro > > > > On Tue, 2004-02-24 at 22:50, Christophe Thibault wrote: > > > Hey Alejandro, > > > > > > Is it because of the fact that you need to put the card in promiscuous > mode > > > (or whatever that name is)? Because some 802.11 wireless PCMCIA cards > > > support that mode fine. > > > > > > -Christophe > > > > > > ----- Original Message ----- > > > From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> > > > To: "Cooperative Linux Development" <col...@li... > > > > > Sent: Tuesday, February 24, 2004 7:28 PM > > > Subject: Re: [coLinux-devel] coLinux 0.5.4 > > > > > > > > > > > * conet-pcap: pcap-based daemon (contributed by Alejandro R. > Sedeno). > > > > > > > > This option only works with 802.3 (wired) networks, not 802.11 > networks > > > > (or others for that matter). > > > > > > > > -Alejandro > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > Build and deploy apps & Web services for Linux with > > > > a free DVD software kit from IBM. Click Now! > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > _______________________________________________ > > > > coLinux-devel mailing list > > > > coL...@li... > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > Build and deploy apps & Web services for Linux with > > > a free DVD software kit from IBM. Click Now! > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > |
From: Christophe T. <ch...@ae...> - 2004-02-25 06:25:37
|
Still the same, as I'm on w2k, I did a "ipconfig /all" and the description line: Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Controller So, I tried "NVIDIA", "MCP", and even "" for the name in the XML, still crashes. -Christophe ----- Original Message ----- From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> To: "Christophe Thibault" <ch...@ae...> Cc: "Cooperative Linux Development" <col...@li...> Sent: Tuesday, February 24, 2004 10:09 PM Subject: coLinux 0.5.4: clarification and bug warning > Assumption: You're trying to make it work with a connection called > "Local Area Network" > > Perhaps the documentation needs to be a little clearer on what name > means. It's refering to the description windows has for your NIC. Two > ways to obtain that: > > 1) (GUI, XP) Highlight 'Local Area Network' in 'Network Connections', > it's the last line in the Detail's box on the side. > > 2) (CLI) 'ipconfig /all'. It's the 'Description' line. > > Also, I'm noticing a sign extension bug has worked its way into the > code. I'm going to try and patch it, sometime tonight. In the mean time, > try to use MAC octets between 00 and 79. You'll know you're running into > this bug if you see a line like: > > executing: colinux-bridged-net-daemon -i 0 -n foo -mac xx:xx:ffffff87... > > -Alejandro > > On Wed, 2004-02-25 at 00:44, Christophe Thibault wrote: > > I can't get the bridged (winpcap) networking to work, the > > colinux-bridged-net-daemon.exe crashes everytime I run colinux-daemon. > > > > I have the following line in my default.colinux.xml: > > > > <network index="0" type="bridged" name="Area"></network> > > > > 'name' is supposed to be a substring of one of the names of the adapters in > > Windows's configuration, right? I even tried with: > > > > <network index="0" type="bridged" name="Area" > > mac="44:55:12:18:0A:12"></network> > > > > And same thing happens. From the log: > > > > colinux: launching net daemons > > daemon: launching daemon for conet0 > > executing: colinux-bridged-net-daemon -i 0 -n Area -mac 44:55:12:18:0a:12 > > conet0: initialized > > 49 [main] colinux-bridged-net-daemon 1756 handle_exceptions: Exception: > > STA > > TUS_ACCESS_VIOLATION > > 649 [main] colinux-bridged-net-daemon 1756 open_stackdumpfile: Dumping > > stack > > trace to colinux-bridged-net-daemon.exe.stackdump > > co_message_switch: freeing rule for 8 > > daemon: module disconnected: conet0 > > > > -Christophe > > > > > > ----- Original Message ----- > > From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> > > To: "Christophe Thibault" <ch...@ae...> > > Cc: "Cooperative Linux Development" <col...@li...> > > Sent: Tuesday, February 24, 2004 9:15 PM > > Subject: Re: [coLinux-devel] coLinux 0.5.4 > > > > > > > Nope, it's because I'm using winPCap to write out raw network frames, > > > and passing incoming frames back to coLinux. coLinux's ethenet device > > > believes it's on a wired network. As such it reads and writes 802.3 > > > frames, which differ in form from 802.11 frames. > > > > > > -Alejandro > > > > > > On Tue, 2004-02-24 at 22:50, Christophe Thibault wrote: > > > > Hey Alejandro, > > > > > > > > Is it because of the fact that you need to put the card in promiscuous > > mode > > > > (or whatever that name is)? Because some 802.11 wireless PCMCIA cards > > > > support that mode fine. > > > > > > > > -Christophe > > > > > > > > ----- Original Message ----- > > > > From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> > > > > To: "Cooperative Linux Development" <col...@li... > > > > > > > Sent: Tuesday, February 24, 2004 7:28 PM > > > > Subject: Re: [coLinux-devel] coLinux 0.5.4 > > > > > > > > > > > > > > * conet-pcap: pcap-based daemon (contributed by Alejandro R. > > Sedeno). > > > > > > > > > > This option only works with 802.3 (wired) networks, not 802.11 > > networks > > > > > (or others for that matter). > > > > > > > > > > -Alejandro > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > Build and deploy apps & Web services for Linux with > > > > > a free DVD software kit from IBM. Click Now! > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > _______________________________________________ > > > > > coLinux-devel mailing list > > > > > coL...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > Build and deploy apps & Web services for Linux with > > > > a free DVD software kit from IBM. Click Now! > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > _______________________________________________ > > > > coLinux-devel mailing list > > > > coL...@li... > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > |
From: Christophe T. <ch...@ae...> - 2004-02-25 06:35:21
|
Oh btw, I also see this in the debug log: "bridged-net-daemon: No matching adapter" So it can't find the right adapter even though the description is correct and the deamon is launched with the right parameters... -Christophe ----- Original Message ----- From: "Christophe Thibault" <ch...@ae...> To: "Alejandro R. Sedeno" <asedeno@MIT.EDU> Cc: "Cooperative Linux Development" <col...@li...> Sent: Tuesday, February 24, 2004 10:14 PM Subject: [coLinux-devel] Re: coLinux 0.5.4: clarification and bug warning > Still the same, as I'm on w2k, I did a "ipconfig /all" and the description > line: > > Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Controller > > So, I tried "NVIDIA", "MCP", and even "" for the name in the XML, still > crashes. > > -Christophe > > ----- Original Message ----- > From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> > To: "Christophe Thibault" <ch...@ae...> > Cc: "Cooperative Linux Development" <col...@li...> > Sent: Tuesday, February 24, 2004 10:09 PM > Subject: coLinux 0.5.4: clarification and bug warning > > > > Assumption: You're trying to make it work with a connection called > > "Local Area Network" > > > > Perhaps the documentation needs to be a little clearer on what name > > means. It's refering to the description windows has for your NIC. Two > > ways to obtain that: > > > > 1) (GUI, XP) Highlight 'Local Area Network' in 'Network Connections', > > it's the last line in the Detail's box on the side. > > > > 2) (CLI) 'ipconfig /all'. It's the 'Description' line. > > > > Also, I'm noticing a sign extension bug has worked its way into the > > code. I'm going to try and patch it, sometime tonight. In the mean time, > > try to use MAC octets between 00 and 79. You'll know you're running into > > this bug if you see a line like: > > > > executing: colinux-bridged-net-daemon -i 0 -n foo -mac xx:xx:ffffff87... > > > > -Alejandro > > > > On Wed, 2004-02-25 at 00:44, Christophe Thibault wrote: > > > I can't get the bridged (winpcap) networking to work, the > > > colinux-bridged-net-daemon.exe crashes everytime I run colinux-daemon. > > > > > > I have the following line in my default.colinux.xml: > > > > > > <network index="0" type="bridged" name="Area"></network> > > > > > > 'name' is supposed to be a substring of one of the names of the adapters > in > > > Windows's configuration, right? I even tried with: > > > > > > <network index="0" type="bridged" name="Area" > > > mac="44:55:12:18:0A:12"></network> > > > > > > And same thing happens. From the log: > > > > > > colinux: launching net daemons > > > daemon: launching daemon for conet0 > > > executing: colinux-bridged-net-daemon -i 0 -n Area -mac > 44:55:12:18:0a:12 > > > conet0: initialized > > > 49 [main] colinux-bridged-net-daemon 1756 handle_exceptions: > Exception: > > > STA > > > TUS_ACCESS_VIOLATION > > > 649 [main] colinux-bridged-net-daemon 1756 open_stackdumpfile: > Dumping > > > stack > > > trace to colinux-bridged-net-daemon.exe.stackdump > > > co_message_switch: freeing rule for 8 > > > daemon: module disconnected: conet0 > > > > > > -Christophe > > > > > > > > > ----- Original Message ----- > > > From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> > > > To: "Christophe Thibault" <ch...@ae...> > > > Cc: "Cooperative Linux Development" > <col...@li...> > > > Sent: Tuesday, February 24, 2004 9:15 PM > > > Subject: Re: [coLinux-devel] coLinux 0.5.4 > > > > > > > > > > Nope, it's because I'm using winPCap to write out raw network frames, > > > > and passing incoming frames back to coLinux. coLinux's ethenet device > > > > believes it's on a wired network. As such it reads and writes 802.3 > > > > frames, which differ in form from 802.11 frames. > > > > > > > > -Alejandro > > > > > > > > On Tue, 2004-02-24 at 22:50, Christophe Thibault wrote: > > > > > Hey Alejandro, > > > > > > > > > > Is it because of the fact that you need to put the card in > promiscuous > > > mode > > > > > (or whatever that name is)? Because some 802.11 wireless PCMCIA > cards > > > > > support that mode fine. > > > > > > > > > > -Christophe > > > > > > > > > > ----- Original Message ----- > > > > > From: "Alejandro R. Sedeno" <asedeno@MIT.EDU> > > > > > To: "Cooperative Linux Development" > <col...@li... > > > > > > > > > Sent: Tuesday, February 24, 2004 7:28 PM > > > > > Subject: Re: [coLinux-devel] coLinux 0.5.4 > > > > > > > > > > > > > > > > > * conet-pcap: pcap-based daemon (contributed by Alejandro R. > > > Sedeno). > > > > > > > > > > > > This option only works with 802.3 (wired) networks, not 802.11 > > > networks > > > > > > (or others for that matter). > > > > > > > > > > > > -Alejandro > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > Build and deploy apps & Web services for Linux with > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > _______________________________________________ > > > > > > coLinux-devel mailing list > > > > > > coL...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > Build and deploy apps & Web services for Linux with > > > > > a free DVD software kit from IBM. Click Now! > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > _______________________________________________ > > > > > coLinux-devel mailing list > > > > > coL...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Christophe T. <ch...@ae...> - 2004-02-25 06:55:43
|
Ok, after some chat with Alejandro, we realised that either my version of winpcap installed was too old or even it wasn't installed even though I was sure it was. Anyhow, a quick passage to http://winpcap.polito.it/ , a reinstall of winpcap version 3.1 beta and everything works fine now. I'd suggest to put in the documentation a link to winpcap's homepage and put a note that if no adapters are found by the daemon, to make sure latest version is installed. :) -Christophe |
From: Christophe T. <ch...@ae...> - 2004-02-25 04:11:50
|
Noticed a typo in default.colinux.xml supplied in the binary zip: <network index="0" type="tap" name="TAP"</network> It's missing the closing > on the network tag. -Christophe ----- Original Message ----- From: "Dan Aloni" <da...@gm...> To: "Cooperative Linux Development" <col...@li...> Sent: Tuesday, February 24, 2004 7:16 PM Subject: [coLinux-devel] coLinux 0.5.4 > This release brings the context switching code of coLinux much closer to > completeness. It's the most sensitive code in this project but the most > important one. > > I'd like to thank Alejandro R. Sedeno for the quick but excellent > pcap-based Bridged Ethernet contribution, and also others who > helped to debug other stuff that led to this release. > > * Version 0.5.4 AKA "Focal Segmental Glomerulosclerosis" (%gs/%fs) release > * Fixed an issue with i686-optimized pthread and the preservation of > %gs and %fs. The crashes that were caused by the i686 Gentoo image > should now disappear. > WINE would also work now ;) > * cobd: Fixed accessing large block devices (1GB >). cobd0 was passing > wrong information to userspace. > * conet: Statistics are now gathered (patch by Pat Erley) > * Tuned the time conversion between Windows and Linux. The machine is > now initialized with the right date, not 4 days backwards. > * Applied a configuration parsing fix (patch by Ballard Jonathan) > * Some improvements of the switch code. We now preserve more > registers, (MMX/SSE/SSE2/FP), and coLinux now has its own GDT. > These changes should assure stability on more systems and processors. > This fix also appears to solve the problem where processes were > stuck on nanosleep() calls. > * conet-pcap: pcap-based daemon (contributed by Alejandro R. Sedeno). > * Network configuration is now handled in the coLinux configuration > XML. > For backward compatibility, add: > <network index="0" name="TAP" type="tap"></network> > > If you want to use pcap (i.e, bridged Ethernet), add: > <network index="0" name="XXXX" type="bridged"></network> > (Where XXXX is a substring of your network adapter's name) > > Optional attributes: mac="XX:XX:XX:XX:XX:XX" - specifies the MAC > address of the interface in the Linux side. Recommended on bridged > networking setups, where more than one Windows machine will be > running coLinux on the same subnet. > > I also prepared the ground for supporting more than one network > device (i.e, eth1, eth2, etc.), but it is not yet completed. > * linux: avoid more I/O in time.c. > > > A side note: > > For the non-developers and developers among you: would anyone like to > update the doc/running file, and whatever documentation files you see > fit? > > -- > Dan Aloni > da...@gm... > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Sugree P. <su...@hp...> - 2004-02-25 05:22:53
|
Furthermore, it's missing </block_device> for root_fs. Sugree Phatanapherom su...@hp... ----- Original Message ----- From: "Christophe Thibault" <ch...@ae...> To: "Cooperative Linux Development" <col...@li...> Sent: Wednesday, February 25, 2004 11:00 AM Subject: Re: [coLinux-devel] coLinux 0.5.4 > Noticed a typo in default.colinux.xml supplied in the binary zip: > > <network index="0" type="tap" name="TAP"</network> > > It's missing the closing > on the network tag. > > -Christophe > > ----- Original Message ----- > From: "Dan Aloni" <da...@gm...> > To: "Cooperative Linux Development" <col...@li...> > Sent: Tuesday, February 24, 2004 7:16 PM > Subject: [coLinux-devel] coLinux 0.5.4 > > > > This release brings the context switching code of coLinux much closer to > > completeness. It's the most sensitive code in this project but the most > > important one. > > > > I'd like to thank Alejandro R. Sedeno for the quick but excellent > > pcap-based Bridged Ethernet contribution, and also others who > > helped to debug other stuff that led to this release. > > > > * Version 0.5.4 AKA "Focal Segmental Glomerulosclerosis" (%gs/%fs) release > > * Fixed an issue with i686-optimized pthread and the preservation of > > %gs and %fs. The crashes that were caused by the i686 Gentoo image > > should now disappear. > > WINE would also work now ;) > > * cobd: Fixed accessing large block devices (1GB >). cobd0 was passing > > wrong information to userspace. > > * conet: Statistics are now gathered (patch by Pat Erley) > > * Tuned the time conversion between Windows and Linux. The machine is > > now initialized with the right date, not 4 days backwards. > > * Applied a configuration parsing fix (patch by Ballard Jonathan) > > * Some improvements of the switch code. We now preserve more > > registers, (MMX/SSE/SSE2/FP), and coLinux now has its own GDT. > > These changes should assure stability on more systems and processors. > > This fix also appears to solve the problem where processes were > > stuck on nanosleep() calls. > > * conet-pcap: pcap-based daemon (contributed by Alejandro R. Sedeno). > > * Network configuration is now handled in the coLinux configuration > > XML. > > For backward compatibility, add: > > <network index="0" name="TAP" type="tap"></network> > > > > If you want to use pcap (i.e, bridged Ethernet), add: > > <network index="0" name="XXXX" type="bridged"></network> > > (Where XXXX is a substring of your network adapter's name) > > > > Optional attributes: mac="XX:XX:XX:XX:XX:XX" - specifies the MAC > > address of the interface in the Linux side. Recommended on bridged > > networking setups, where more than one Windows machine will be > > running coLinux on the same subnet. > > > > I also prepared the ground for supporting more than one network > > device (i.e, eth1, eth2, etc.), but it is not yet completed. > > * linux: avoid more I/O in time.c. > > > > > > A side note: > > > > For the non-developers and developers among you: would anyone like to > > update the doc/running file, and whatever documentation files you see > > fit? > > > > -- > > Dan Aloni > > da...@gm... > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Bart K. <Bar...@su...> - 2004-02-25 10:13:17
|
Hi Dan, > This release brings the context switching code of coLinux much closer to > completeness. It's the most sensitive code in this project but the most > important one. The 0.5.4 release is not available (anymore) on the sourgeforce dl-sites?! Best regards, Bart |
From: Dan A. <da...@gm...> - 2004-02-25 10:27:11
|
On Wed, Feb 25, 2004 at 11:04:03AM +0100, Bart Kerver wrote: > Hi Dan, > > >This release brings the context switching code of coLinux much closer to > >completeness. It's the most sensitive code in this project but the most > >important one. > > The 0.5.4 release is not available (anymore) on the sourgeforce dl-sites?! Interesting. Must be an sf bug. I'll upload again. -- Dan Aloni da...@gm... |
From: Benoit M. <ben...@cg...> - 2004-02-25 10:52:39
|
Colinux doesn-t run on nt4, am I right??? Benoit |
From: Benoit M. <ben...@cg...> - 2004-02-25 13:18:01
|
Since Colinux doesn't support more than 4GB of RAM, couldn't it call the GlobalMemoryStatus instead of GlobalMemoryStatusEx depending on nt version... 4 (GlobalMemoryStatus) or >=5 (GlobalMemoryStatusEx) gonna try to modify it for that. Benoit ----- Original Message ----- From: "Benoit MICHEL" <ben...@cg...> To: "Cooperative Linux Development" <col...@li...> Sent: Wednesday, February 25, 2004 11:42 AM Subject: [coLinux-devel] coLinux 0.5.4 > Colinux doesn-t run on nt4, am I right??? > > Benoit > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Benoit M. <ben...@cg...> - 2004-03-01 11:14:50
Attachments:
misc.c
|
Hi all could someone compile recompile the daemon and console with his file plz? and then send back binaries to me (don't have net access, just mails.....) I can't do it myself, i'm on nt4 :( it goes in src/colinux/os/winnt/user/ based on 20040227 thanks Ben |
From: Benoit M. <ben...@cg...> - 2004-03-02 15:08:35
|
Compiled with GetGlobalStatus instead of GetGlobalStatusEx, no problem but I've another problem, it's about lynux.sys, the daemon can't find ExFreePoolWithTag entry point in ntoskrnl.exe when installing kernel driver. and the only doc I found about this api says nt4 supported. any Idea?? thx Ben ----- Original Message ----- From: "Benoit MICHEL" <ben...@cg...> To: "Cooperative Linux Development" <col...@li...> Sent: Monday, March 01, 2004 12:00 PM Subject: [coLinux-devel] coLinux on NT4? > Hi all > > could someone compile recompile the daemon and console with his file plz? > and then send back binaries to me (don't have net access, just mails.....) > I can't do it myself, i'm on nt4 :( > it goes in src/colinux/os/winnt/user/ > based on 20040227 > > thanks > > Ben > > |
From: Digital I. Inc. <ok...@di...> - 2004-03-02 15:20:17
|
Hello BTW, Why you have an interest about coLinux on NT4? Just your hobby? or you have real usage? but, at least, I welcome your effort very much. because, with your effort, we can collect more hints to stabilize coLinux. thanks Benoit!. and please give us your history of BSOD with a stack trace. --- Okajima. |
From: Benoit M. <ben...@cg...> - 2004-03-03 09:15:10
|
Hi I'd like to use it at work, where i'm still using nt4 (really heavy to use cL through vmware) It is for a real usage AND optionnaly ;) for my pleasure ;) but at home.... XP, colinux rulez what do you mean by BSOD?? and the daemon doesn't trapp, just show a messagebox with "device driver d:\col\linux.sys was unable to find entry point for ExFreePoolWithTag in ntoskrnl.exe driver" (litteral traduction, original was in french ;) ) then close the windows when I click on OK. It all began with the same symptoms complaining about GlobalMemoryStatusEx (not supported by NT4) I made these modifications in /src/colinux/os/winnt/user/misc.c diff says : 20,21c20,21 < MEMORYSTATUSEX m; < BOOL ret; --- > MEMORYSTATUS m; > //BOOL ret; 24,25c24,25 < ret = GlobalMemoryStatusEx(&m); < if (ret != TRUE) { --- > /*ret = */GlobalMemoryStatus(&m); > /*if (ret != TRUE) { 28c28 < } --- > }*/ 30c30 < if (m.ullTotalPhys > (DWORDLONG)0xFF000000) { --- > if (m.dwTotalPhys > (DWORDLONG)0xFF000000) { 36c36 < *mem_size = 0xFF000000 & (((unsigned long)m.ullTotalPhys) + 0xFFFFFF); --- > *mem_size = 0xFF000000 & (((unsigned long)m.dwTotalPhys) + 0xFFFFFF); just using GlobalMemoryStatus instead of GlobalMemoryStatusEx (my NT4 system is far below the 2GB limit ;) ) no pb anymore to compile it at home using cobuild.sh (edited to not averwrite my modifications) and when I tried it today here, the daemon complains about ExFreePoolWithTag When I look at my NTOSKRNL.EXE (v4.00) it exports ExFreePool but not ExFreePoolWithTag The doc I found say that nt4 SP4 workstation support this API, i'm in sp6a. Benoit ----- Original Message ----- From: "Digital Infra, Inc." <ok...@di...> To: "Benoit MICHEL" <bem...@ca...> Cc: "Cooperative Linux Development" <col...@li...> Sent: Tuesday, March 02, 2004 4:07 PM Subject: Re: [coLinux-devel] coLinux on NT4? > > Hello > > BTW, Why you have an interest about coLinux on NT4? > Just your hobby? or you have real usage? > but, at least, I welcome your effort very much. > because, with your effort, we can collect more hints to > stabilize coLinux. thanks Benoit!. > and please give us your history of BSOD with a stack trace. > > --- Okajima. |
From: Benoit M. <ben...@cg...> - 2004-03-03 15:51:57
|
memory allocated with ExAllocatePoolWithTag can also be freed with ExFreePool (wich is NT4 supported) in the file src/colinux/winnt/kernel/lowlevel/alloc.c I gonna try to compile tonight with the second in place of the first...... And this function is declared in win32api, include/ddk/winddk.h these functions are dependent of a flag : POOL_TAGGING, does someone know if this is set in colinux cross compilation tools? I don't think so. thx Ben ----- Original Message ----- From: "Benoit MICHEL" <ben...@cg...> To: "Digital Infra, Inc." <ok...@di...> Cc: "Cooperative Linux Development" <col...@li...> Sent: Wednesday, March 03, 2004 9:59 AM Subject: Re: [coLinux-devel] coLinux on NT4? > Hi > > I'd like to use it at work, where i'm still using nt4 (really heavy to use > cL through vmware) > It is for a real usage AND optionnaly ;) for my pleasure ;) > but at home.... XP, colinux rulez > what do you mean by BSOD?? > and the daemon doesn't trapp, just show a messagebox with "device driver > d:\col\linux.sys was unable to find entry point for ExFreePoolWithTag in > ntoskrnl.exe driver" (litteral traduction, original was in french ;) ) then > close the windows when I click on OK. > > It all began with the same symptoms complaining about GlobalMemoryStatusEx > (not supported by NT4) > I made these modifications in /src/colinux/os/winnt/user/misc.c > > diff says : > 20,21c20,21 > < MEMORYSTATUSEX m; > < BOOL ret; > --- > > MEMORYSTATUS m; > > //BOOL ret; > 24,25c24,25 > < ret = GlobalMemoryStatusEx(&m); > < if (ret != TRUE) { > --- > > /*ret = */GlobalMemoryStatus(&m); > > /*if (ret != TRUE) { > 28c28 > < } > --- > > }*/ > 30c30 > < if (m.ullTotalPhys > (DWORDLONG)0xFF000000) { > --- > > if (m.dwTotalPhys > (DWORDLONG)0xFF000000) { > 36c36 > < *mem_size = 0xFF000000 & (((unsigned long)m.ullTotalPhys) + 0xFFFFFF); > --- > > *mem_size = 0xFF000000 & (((unsigned long)m.dwTotalPhys) + 0xFFFFFF); > > > just using GlobalMemoryStatus instead of GlobalMemoryStatusEx (my NT4 system > is far below the 2GB limit ;) ) > > no pb anymore to compile it at home using cobuild.sh (edited to not > averwrite my modifications) > and when I tried it today here, the daemon complains about ExFreePoolWithTag > > When I look at my NTOSKRNL.EXE (v4.00) it exports ExFreePool but not > ExFreePoolWithTag > > The doc I found say that nt4 SP4 workstation support this API, i'm in sp6a. > > Benoit > > > ----- Original Message ----- > From: "Digital Infra, Inc." <ok...@di...> > To: "Benoit MICHEL" <bem...@ca...> > Cc: "Cooperative Linux Development" <col...@li...> > Sent: Tuesday, March 02, 2004 4:07 PM > Subject: Re: [coLinux-devel] coLinux on NT4? > > > > > > Hello > > > > BTW, Why you have an interest about coLinux on NT4? > > Just your hobby? or you have real usage? > > but, at least, I welcome your effort very much. > > because, with your effort, we can collect more hints to > > stabilize coLinux. thanks Benoit!. > > and please give us your history of BSOD with a stack trace. > > > > --- Okajima. > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Benoit M. <ben...@cg...> - 2004-03-04 10:15:31
|
Hi all I succeed in running colinux on nt4 sp6a after replacing ExFreePoolWithTag (in src/colinux/winnt/kernel/lowlevel/alloc.c) with ExFreePool. and GlobalMemoryStatusEx (in /src/colinux/os/winnt/user/misc.c) with GlobalMemoryStatus. I just still have pb compiling conet-bridged-daemon, ld can't find -lwpcap I downloaded libpcap-8.xxxx.tar.gz untared it, configure with --prefix= and --target feeded make then make install without any pb any idea??? thx Ben ----- Original Message ----- From: "Benoit MICHEL" <ben...@cg...> To: "Cooperative Linux Development" <col...@li...> Sent: Wednesday, March 03, 2004 4:37 PM Subject: Re: [coLinux-devel] coLinux on NT4? > memory allocated with ExAllocatePoolWithTag can also be freed with > ExFreePool (wich is NT4 supported) > in the file src/colinux/winnt/kernel/lowlevel/alloc.c > I gonna try to compile tonight with the second in place of the first...... > > And this function is declared in win32api, include/ddk/winddk.h > these functions are dependent of a flag : POOL_TAGGING, does someone know if > this is set in colinux cross compilation tools? I don't think so. > > thx > Ben > > > ----- Original Message ----- > From: "Benoit MICHEL" <ben...@cg...> > To: "Digital Infra, Inc." <ok...@di...> > Cc: "Cooperative Linux Development" <col...@li...> > Sent: Wednesday, March 03, 2004 9:59 AM > Subject: Re: [coLinux-devel] coLinux on NT4? > > > > Hi > > > > I'd like to use it at work, where i'm still using nt4 (really heavy to use > > cL through vmware) > > It is for a real usage AND optionnaly ;) for my pleasure ;) > > but at home.... XP, colinux rulez > > what do you mean by BSOD?? > > and the daemon doesn't trapp, just show a messagebox with "device driver > > d:\col\linux.sys was unable to find entry point for ExFreePoolWithTag in > > ntoskrnl.exe driver" (litteral traduction, original was in french ;) ) > then > > close the windows when I click on OK. > > > > It all began with the same symptoms complaining about GlobalMemoryStatusEx > > (not supported by NT4) > > I made these modifications in /src/colinux/os/winnt/user/misc.c > > > > diff says : > > 20,21c20,21 > > < MEMORYSTATUSEX m; > > < BOOL ret; > > --- > > > MEMORYSTATUS m; > > > //BOOL ret; > > 24,25c24,25 > > < ret = GlobalMemoryStatusEx(&m); > > < if (ret != TRUE) { > > --- > > > /*ret = */GlobalMemoryStatus(&m); > > > /*if (ret != TRUE) { > > 28c28 > > < } > > --- > > > }*/ > > 30c30 > > < if (m.ullTotalPhys > (DWORDLONG)0xFF000000) { > > --- > > > if (m.dwTotalPhys > (DWORDLONG)0xFF000000) { > > 36c36 > > < *mem_size = 0xFF000000 & (((unsigned long)m.ullTotalPhys) + 0xFFFFFF); > > --- > > > *mem_size = 0xFF000000 & (((unsigned long)m.dwTotalPhys) + 0xFFFFFF); > > > > > > just using GlobalMemoryStatus instead of GlobalMemoryStatusEx (my NT4 > system > > is far below the 2GB limit ;) ) > > > > no pb anymore to compile it at home using cobuild.sh (edited to not > > averwrite my modifications) > > and when I tried it today here, the daemon complains about > ExFreePoolWithTag > > > > When I look at my NTOSKRNL.EXE (v4.00) it exports ExFreePool but not > > ExFreePoolWithTag > > > > The doc I found say that nt4 SP4 workstation support this API, i'm in > sp6a. > > > > Benoit > > > > > > ----- Original Message ----- > > From: "Digital Infra, Inc." <ok...@di...> > > To: "Benoit MICHEL" <bem...@ca...> > > Cc: "Cooperative Linux Development" <col...@li...> > > Sent: Tuesday, March 02, 2004 4:07 PM > > Subject: Re: [coLinux-devel] coLinux on NT4? > > > > > > > > > > Hello > > > > > > BTW, Why you have an interest about coLinux on NT4? > > > Just your hobby? or you have real usage? > > > but, at least, I welcome your effort very much. > > > because, with your effort, we can collect more hints to > > > stabilize coLinux. thanks Benoit!. > > > and please give us your history of BSOD with a stack trace. > > > > > > --- Okajima. > > > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Sean B. <sea...@so...> - 2004-03-04 12:21:32
|
I think you are using the wrong library. I asked a similar question a few days ago. Here is part of the message: | Dan set the bridged daemon aside in the makefile. From the colinux/src | dir: | | make bridged_net_daemon | | You may also need the winpcap headers, those are available on the | winpcap site (google for link). I've been using the 3.0 Developer's | Pack. Careful how you integrate these with the existing includes, make a | backup of what's there since pcap includes some different versions of | what's already there. I cannot integrate the include files because I do not know how to do it properly. When you do integrate them please can you tell me what you did so I can compile the conet-bridged-daemon too :) ----- Original Message ----- From: "Benoit MICHEL" <ben...@cg...> To: "Cooperative Linux Development" <col...@li...> Sent: Thursday, March 04, 2004 9:59 AM Subject: Re: [coLinux-devel] coLinux on NT4? | Hi all | | I succeed in running colinux on nt4 sp6a after replacing ExFreePoolWithTag | (in src/colinux/winnt/kernel/lowlevel/alloc.c) with | ExFreePool. | and GlobalMemoryStatusEx (in /src/colinux/os/winnt/user/misc.c) with | GlobalMemoryStatus. | I just still have pb compiling conet-bridged-daemon, ld can't find -lwpcap | I downloaded libpcap-8.xxxx.tar.gz | untared it, configure with --prefix= and --target feeded | make then make install without any pb | | any idea??? | | thx | Ben | | ----- Original Message ----- | From: "Benoit MICHEL" <ben...@cg...> | To: "Cooperative Linux Development" <col...@li...> | Sent: Wednesday, March 03, 2004 4:37 PM | Subject: Re: [coLinux-devel] coLinux on NT4? | | | > memory allocated with ExAllocatePoolWithTag can also be freed with | > ExFreePool (wich is NT4 supported) | > in the file src/colinux/winnt/kernel/lowlevel/alloc.c | > I gonna try to compile tonight with the second in place of the first...... | > | > And this function is declared in win32api, include/ddk/winddk.h | > these functions are dependent of a flag : POOL_TAGGING, does someone know | if | > this is set in colinux cross compilation tools? I don't think so. | > | > thx | > Ben | > | > | > ----- Original Message ----- | > From: "Benoit MICHEL" <ben...@cg...> | > To: "Digital Infra, Inc." <ok...@di...> | > Cc: "Cooperative Linux Development" <col...@li...> | > Sent: Wednesday, March 03, 2004 9:59 AM | > Subject: Re: [coLinux-devel] coLinux on NT4? | > | > | > > Hi | > > | > > I'd like to use it at work, where i'm still using nt4 (really heavy to | use | > > cL through vmware) | > > It is for a real usage AND optionnaly ;) for my pleasure ;) | > > but at home.... XP, colinux rulez | > > what do you mean by BSOD?? | > > and the daemon doesn't trapp, just show a messagebox with "device driver | > > d:\col\linux.sys was unable to find entry point for ExFreePoolWithTag in | > > ntoskrnl.exe driver" (litteral traduction, original was in french ;) ) | > then | > > close the windows when I click on OK. | > > | > > It all began with the same symptoms complaining about | GlobalMemoryStatusEx | > > (not supported by NT4) | > > I made these modifications in /src/colinux/os/winnt/user/misc.c | > > | > > diff says : | > > 20,21c20,21 | > > < MEMORYSTATUSEX m; | > > < BOOL ret; | > > --- | > > > MEMORYSTATUS m; | > > > //BOOL ret; | > > 24,25c24,25 | > > < ret = GlobalMemoryStatusEx(&m); | > > < if (ret != TRUE) { | > > --- | > > > /*ret = */GlobalMemoryStatus(&m); | > > > /*if (ret != TRUE) { | > > 28c28 | > > < } | > > --- | > > > }*/ | > > 30c30 | > > < if (m.ullTotalPhys > (DWORDLONG)0xFF000000) { | > > --- | > > > if (m.dwTotalPhys > (DWORDLONG)0xFF000000) { | > > 36c36 | > > < *mem_size = 0xFF000000 & (((unsigned long)m.ullTotalPhys) + | 0xFFFFFF); | > > --- | > > > *mem_size = 0xFF000000 & (((unsigned long)m.dwTotalPhys) + 0xFFFFFF); | > > | > > | > > just using GlobalMemoryStatus instead of GlobalMemoryStatusEx (my NT4 | > system | > > is far below the 2GB limit ;) ) | > > | > > no pb anymore to compile it at home using cobuild.sh (edited to not | > > averwrite my modifications) | > > and when I tried it today here, the daemon complains about | > ExFreePoolWithTag | > > | > > When I look at my NTOSKRNL.EXE (v4.00) it exports ExFreePool but not | > > ExFreePoolWithTag | > > | > > The doc I found say that nt4 SP4 workstation support this API, i'm in | > sp6a. | > > | > > Benoit | > > | > > | > > ----- Original Message ----- | > > From: "Digital Infra, Inc." <ok...@di...> | > > To: "Benoit MICHEL" <bem...@ca...> | > > Cc: "Cooperative Linux Development" | <col...@li...> | > > Sent: Tuesday, March 02, 2004 4:07 PM | > > Subject: Re: [coLinux-devel] coLinux on NT4? | > > | > > | > > > | > > > Hello | > > > | > > > BTW, Why you have an interest about coLinux on NT4? | > > > Just your hobby? or you have real usage? | > > > but, at least, I welcome your effort very much. | > > > because, with your effort, we can collect more hints to | > > > stabilize coLinux. thanks Benoit!. | > > > and please give us your history of BSOD with a stack trace. | > > > | > > > --- Okajima. | > > | > > | > > | > > ------------------------------------------------------- | > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. | > > Build and deploy apps & Web services for Linux with | > > a free DVD software kit from IBM. Click Now! | > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click | > > _______________________________________________ | > > coLinux-devel mailing list | > > coL...@li... | > > https://lists.sourceforge.net/lists/listinfo/colinux-devel | > | > | > | > ------------------------------------------------------- | > SF.Net is sponsored by: Speed Start Your Linux Apps Now. | > Build and deploy apps & Web services for Linux with | > a free DVD software kit from IBM. Click Now! | > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click | > _______________________________________________ | > coLinux-devel mailing list | > coL...@li... | > https://lists.sourceforge.net/lists/listinfo/colinux-devel | | | | ------------------------------------------------------- | This SF.Net email is sponsored by: IBM Linux Tutorials | Free Linux tutorial presented by Daniel Robbins, President and CEO of | GenToo technologies. Learn everything from fundamentals to system | administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click | _______________________________________________ | coLinux-devel mailing list | coL...@li... | https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Dan A. <da...@co...> - 2004-04-14 05:22:48
|
On Thu, Mar 04, 2004 at 10:59:56AM +0100, Benoit MICHEL wrote: > Hi all > > I succeed in running colinux on nt4 sp6a after replacing ExFreePoolWithTag > (in src/colinux/winnt/kernel/lowlevel/alloc.c) with > ExFreePool. > and GlobalMemoryStatusEx (in /src/colinux/os/winnt/user/misc.c) with > GlobalMemoryStatus. Can you please send a unidiff patch for the tree, with all the changes you have made? -- Dan Aloni da...@co... |
From: Benoit M. <ben...@cg...> - 2004-04-14 12:19:22
|
Hi these two ones are the mod I made, but only running on "clean" nt4 (fresh install), wasn't running on my workstation (dev computer) making it to reboot, think about free mem, but hadn' time to investigate (since this, I migrate my computer to win2k....... sry) i'm sorry, but i don't have unidiff based on 20040227 : -src/colinux/os/winnt/kernel/lowlevel/alloc.c $ diff alloc.c alloc_mod.c 93c93 < ExFreePoolWithTag(ptr, CO_OS_POOL_TAG); --- > ExFreePool(ptr); -/src/colinux/os/winnt/user/misc.c $ diff misc.c misc_mod.c 20,21c20 < MEMORYSTATUSEX m; < BOOL ret; --- > MEMORYSTATUS m; 24,28c23 < ret = GlobalMemoryStatusEx(&m); < if (ret != TRUE) { < co_debug("Error, GlobalMemoryStatusEx returned: %x\n", GetLastError()); < return CO_RC(ERROR); < } --- > GlobalMemoryStatus(&m); 30c25 < if (m.ullTotalPhys > (DWORDLONG)0xFF000000) { --- > if (m.dwTotalPhys > (DWORDLONG)0xFF000000) { 36c31 < *mem_size = 0xFF000000 & (((unsigned long)m.ullTotalPhys) + 0xFFFFFF); --- > *mem_size = 0xFF000000 & (((unsigned long)m.dwTotalPhys) + 0xFFFFFF); ----- Original Message ----- From: "Dan Aloni" <da...@co...> To: "Benoit MICHEL" <ben...@cg...> Cc: "Cooperative Linux Development" <col...@li...> Sent: Wednesday, April 14, 2004 6:22 AM Subject: Re: [coLinux-devel] coLinux on NT4? > On Thu, Mar 04, 2004 at 10:59:56AM +0100, Benoit MICHEL wrote: > > Hi all > > > > I succeed in running colinux on nt4 sp6a after replacing ExFreePoolWithTag > > (in src/colinux/winnt/kernel/lowlevel/alloc.c) with > > ExFreePool. > > and GlobalMemoryStatusEx (in /src/colinux/os/winnt/user/misc.c) with > > GlobalMemoryStatus. > > Can you please send a unidiff patch for the tree, with all the > changes you have made? > > -- > Dan Aloni > da...@co... > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Evan D. <eda...@tj...> - 2004-02-25 15:37:07
|
I might be willing to help with documentation. I don't know all the details, but I could certainly write up my experience as a start to a comprehensive guide... On Wed, 25 Feb 2004, Dan Aloni wrote: > This release brings the context switching code of coLinux much closer to > completeness. It's the most sensitive code in this project but the most > important one. > > I'd like to thank Alejandro R. Sedeno for the quick but excellent > pcap-based Bridged Ethernet contribution, and also others who > helped to debug other stuff that led to this release. > > * Version 0.5.4 AKA "Focal Segmental Glomerulosclerosis" (%gs/%fs) release > * Fixed an issue with i686-optimized pthread and the preservation of > %gs and %fs. The crashes that were caused by the i686 Gentoo image > should now disappear. > WINE would also work now ;) > * cobd: Fixed accessing large block devices (1GB >). cobd0 was passing > wrong information to userspace. > * conet: Statistics are now gathered (patch by Pat Erley) > * Tuned the time conversion between Windows and Linux. The machine is > now initialized with the right date, not 4 days backwards. > * Applied a configuration parsing fix (patch by Ballard Jonathan) > * Some improvements of the switch code. We now preserve more > registers, (MMX/SSE/SSE2/FP), and coLinux now has its own GDT. > These changes should assure stability on more systems and processors. > This fix also appears to solve the problem where processes were > stuck on nanosleep() calls. > * conet-pcap: pcap-based daemon (contributed by Alejandro R. Sedeno). > * Network configuration is now handled in the coLinux configuration > XML. > For backward compatibility, add: > <network index="0" name="TAP" type="tap"></network> > > If you want to use pcap (i.e, bridged Ethernet), add: > <network index="0" name="XXXX" type="bridged"></network> > (Where XXXX is a substring of your network adapter's name) > > Optional attributes: mac="XX:XX:XX:XX:XX:XX" - specifies the MAC > address of the interface in the Linux side. Recommended on bridged > networking setups, where more than one Windows machine will be > running coLinux on the same subnet. > > I also prepared the ground for supporting more than one network > device (i.e, eth1, eth2, etc.), but it is not yet completed. > * linux: avoid more I/O in time.c. > > > A side note: > > For the non-developers and developers among you: would anyone like to > update the doc/running file, and whatever documentation files you see > fit? > > -- > Dan Aloni > da...@gm... > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |