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: Alejandro R. S. <as...@MI...> - 2004-02-26 00:38:36
|
On Wed, 2004-02-25 at 19:17, ch...@to... wrote: > Do I understand this correctly? > > bridged would be like a forewarding alias on the physical card of the > machine and on the same physical lan. And if using dhcp it would use the > networks real dhcp server. > > tap would be used if you wanted to have windows host to share it's network > connection and provide NAT and dhcp. > > chris The bridged connection essentially 'shares' the host's NIC, using winPCap to send out packets and listen for packets that it should receive. Your dhcp example is right on, it would use the real dhcp server. -Alejandro |
|
From: <ch...@to...> - 2004-02-26 00:26:41
|
Do I understand this correctly? bridged would be like a forewarding alias on the physical card of the machine and on the same physical lan. And if using dhcp it would use the networks real dhcp server. tap would be used if you wanted to have windows host to share it's network connection and provide NAT and dhcp. chris |
|
From: <ch...@to...> - 2004-02-26 00:07:29
|
I came up with a way to do topologilinux without initrd under coLinux after realizing that I was only using it to set sym links. I think I can put the links to /dev/cobd? in the /initrd folder and have fstab point to them for devices. When booting natively the initrd will be mounted here and will have it's own it's own links to /dev/loop? chris >> but as colinux is a very static architecture (because it does not deal >> with >> hardware) i don't really see the point > > example: Slackware > > Slackware CDs are essentially running off a initrd that is on the CD. that > initrd contains a mini-root, with all the scripts and the installer. This > boots, and then, after the setup starts, it mounts the CD. with initrd > support, installing slackware from CD would be as difficult as copying the > initrd, load colinux and install... and iso9660 support would be awesome > :o) (would make it easier to do, than to copy all that stuff to a ext2fs > filesystem...) > > Jok > --- > Nothing is foolproof to a sufficiently talented fool... > oo > ,(..)\ > ~~ > > > ------------------------------------------------------- > 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. <as...@MI...> - 2004-02-26 00:01:11
|
Since I've run into this problem with one user, I figure I'll mention it here for reference. A MAC address is not a set of random numbers. There is a ieee standard, and some of the bits actually mean something. The first two bits of the MAC address have very specific meanings. The first bit specifies if the MAC refers to an individual or a group; set it to 0. The second bit specifies if the MAC is globally administered or not; this bit should technically be a 1. so your MAC should technically start with one of: ?2, ?6, ?A, ?E and can start with: ?0, ?4, ?8, ?C though these would technically violate the ieee spec. If you want to learn more about the MAC address format, ask your favorite search engine. -Alejandro |
|
From: Dan A. <da...@gm...> - 2004-02-25 20:45:03
|
On Wed, Feb 25, 2004 at 07:06:14PM -0000, peter green wrote: > can you say what gcc version was used to compile the binary release [22:34 pts/81,callisto ~]% gcc -v Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.3/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux Thread model: posix gcc version 3.3.3 (Debian) [22:34 pts/81,callisto ~]% i686-pc-cygwin-gcc -v Reading specs from /usr/local/w32build/lib/gcc-lib/i686-pc-cygwin/3.3.2/specs Configured with: ./configure --target=i686-pc-cygwin --prefix=/usr/local/w32build --enable-languages=c,c++ Thread model: single gcc version 3.3.2 -- Dan Aloni da...@gm... |
|
From: peter g. <plu...@p1...> - 2004-02-25 20:14:07
|
i can't see any reason colinux wouldn't do iso9660 though i don't think that the current binary releases come with it -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of ePAc Sent: 25 February 2004 20:02 To: peter green Cc: col...@li... Subject: RE: [coLinux-devel] kernel patch > but as colinux is a very static architecture (because it does not deal with > hardware) i don't really see the point example: Slackware Slackware CDs are essentially running off a initrd that is on the CD. that initrd contains a mini-root, with all the scripts and the installer. This boots, and then, after the setup starts, it mounts the CD. with initrd support, installing slackware from CD would be as difficult as copying the initrd, load colinux and install... and iso9660 support would be awesome :o) (would make it easier to do, than to copy all that stuff to a ext2fs filesystem...) Jok --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ ------------------------------------------------------- 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 --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004 |
|
From: ePAc <ep...@ko...> - 2004-02-25 20:09:33
|
> but as colinux is a very static architecture (because it does not deal with > hardware) i don't really see the point example: Slackware Slackware CDs are essentially running off a initrd that is on the CD. that initrd contains a mini-root, with all the scripts and the installer. This boots, and then, after the setup starts, it mounts the CD. with initrd support, installing slackware from CD would be as difficult as copying the initrd, load colinux and install... and iso9660 support would be awesome :o) (would make it easier to do, than to copy all that stuff to a ext2fs filesystem...) Jok --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ |
|
From: ePAc <ep...@ko...> - 2004-02-25 20:02:38
|
> > Why do you need a kernel with an initrd support? > most distro boot off the CD with a InitRD. usign that initrd, and the colinux kernel, we should be able to use pretty much any CD to install a OS to a CODB file... :o) Jok --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ |
|
From: peter g. <plu...@p1...> - 2004-02-25 19:15:42
|
can you say what gcc version was used to compile the binary release
-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of Dan Aloni
Sent: 25 February 2004 03:16
To: Cooperative Linux Development
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
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004
|
|
From: peter g. <plu...@p1...> - 2004-02-25 18:34:37
|
tell me if i'm wrong here but i thought the whole point of an initrd was to avoid haveing too many drivers in the kernel but as colinux is a very static architecture (because it does not deal with hardware) i don't really see the point -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of ch...@to... Sent: 25 February 2004 16:53 To: col...@li... Subject: [coLinux-devel] kernel patch Just compiled a kernel for valentine version. can I just add the new patch or should I delete and start with fresh kernel source? I think I figured out how to use an initrd but need to build a kernel with support. <bootparams>initrd=cobd2 root=/dev/ram0 init=linuxrc rw</bootparams> and use the newer style of pivot root where it is explicitly done in linuxrc I tried faking it with the new standard kernel with <bootparams>root=cobd2 init=linuxrc rw</bootparams> but it dies when init (linuxrc) does thanks, chris ------------------------------------------------------- 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 --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004 |
|
From: Dan A. <da...@gm...> - 2004-02-25 17:35:24
|
On Wed, Feb 25, 2004 at 05:53:19PM +0100, ch...@to... wrote: > Just compiled a kernel for valentine version. > can I just add the new patch or should I delete and start with fresh > kernel source? To use the patch from the latest release, first remove the old patch using 'patch -R', and then apply the latest patch. > I think I figured out how to use an initrd but need to build a kernel with > support. > > <bootparams>initrd=cobd2 root=/dev/ram0 init=linuxrc rw</bootparams> > and use the newer style of pivot root where it is explicitly done in linuxrc > > I tried faking it with the new standard kernel with > <bootparams>root=cobd2 init=linuxrc rw</bootparams> > but it dies when init (linuxrc) does Why do you need a kernel with an initrd support? -- Dan Aloni da...@gm... |
|
From: <ch...@to...> - 2004-02-25 17:07:43
|
also are there any changes to .config ? or can I use the one I setup yesterday? > Just compiled a kernel for valentine version. > can I just add the new patch or should I delete and start with fresh > kernel source? > > I think I figured out how to use an initrd but need to build a kernel with > support. > > <bootparams>initrd=cobd2 root=/dev/ram0 init=linuxrc rw</bootparams> > and use the newer style of pivot root where it is explicitly done in > linuxrc > > > I tried faking it with the new standard kernel with > <bootparams>root=cobd2 init=linuxrc rw</bootparams> > but it dies when init (linuxrc) does > > thanks, > chris > > > ------------------------------------------------------- > 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: <ch...@to...> - 2004-02-25 17:02:40
|
Just compiled a kernel for valentine version. can I just add the new patch or should I delete and start with fresh kernel source? I think I figured out how to use an initrd but need to build a kernel with support. <bootparams>initrd=cobd2 root=/dev/ram0 init=linuxrc rw</bootparams> and use the newer style of pivot root where it is explicitly done in linuxrc I tried faking it with the new standard kernel with <bootparams>root=cobd2 init=linuxrc rw</bootparams> but it dies when init (linuxrc) does thanks, chris |
|
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 > |
|
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-02-25 10:52:39
|
Colinux doesn-t run on nt4, am I right??? Benoit |
|
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: 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: Ballard J. <sac...@ho...> - 2004-02-25 07:52:56
|
I compiled a few patches. 0.5.4 fixed implicit declarations=20 0.5.4 added co_os_realloc()=20 0.5.4 fixed overflow with the XML memory config=20 0.5.4 reimplemented os/winnt/user/daemon.c=20 Available at SourceForge.net: http://sourceforge.net/tracker/?atid=3D622065&group_id=3D98788&func=3Dbro= wse |
|
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 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" <as...@MI...> 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" <as...@MI...> > 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" <as...@MI...> > > > 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" <as...@MI...> > > > > > 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: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" <as...@MI...> 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" <as...@MI...> > > 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" <as...@MI...> > > > > 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. <as...@MI...> - 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" <as...@MI...> > 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" <as...@MI...> > > > 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" <as...@MI...>
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" <as...@MI...>
> > 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. <as...@MI...> - 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" <as...@MI...> > 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 > |
81 messages has been excluded from this view by a project administrator.
