Menu
▾
▴
colinux-users — coLinux users mailing list
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(100) |
Jun
(134) |
Jul
(149) |
Aug
(123) |
Sep
(185) |
Oct
(122) |
Nov
(59) |
Dec
(127) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(128) |
Feb
(233) |
Mar
(210) |
Apr
(196) |
May
(85) |
Jun
(96) |
Jul
(76) |
Aug
(149) |
Sep
(65) |
Oct
(78) |
Nov
(121) |
Dec
(82) |
| 2006 |
Jan
(249) |
Feb
(181) |
Mar
(176) |
Apr
(156) |
May
(128) |
Jun
(102) |
Jul
(157) |
Aug
(80) |
Sep
(42) |
Oct
(49) |
Nov
(36) |
Dec
(42) |
| 2007 |
Jan
(64) |
Feb
(38) |
Mar
(45) |
Apr
(74) |
May
(26) |
Jun
(20) |
Jul
(17) |
Aug
(12) |
Sep
(40) |
Oct
(7) |
Nov
(14) |
Dec
(16) |
| 2008 |
Jan
(52) |
Feb
(49) |
Mar
(90) |
Apr
(80) |
May
(78) |
Jun
(82) |
Jul
(25) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(3) |
Dec
(17) |
| 2009 |
Jan
(12) |
Feb
(16) |
Mar
(20) |
Apr
(14) |
May
(17) |
Jun
(10) |
Jul
(13) |
Aug
(12) |
Sep
(21) |
Oct
(10) |
Nov
(30) |
Dec
(1) |
| 2010 |
Jan
(2) |
Feb
(7) |
Mar
(22) |
Apr
(6) |
May
(33) |
Jun
(5) |
Jul
(4) |
Aug
(38) |
Sep
(46) |
Oct
(23) |
Nov
(9) |
Dec
(5) |
| 2011 |
Jan
(21) |
Feb
(27) |
Mar
(1) |
Apr
(18) |
May
(12) |
Jun
(12) |
Jul
(10) |
Aug
(30) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
(19) |
| 2012 |
Jan
(26) |
Feb
(6) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(10) |
Aug
(1) |
Sep
(18) |
Oct
(5) |
Nov
|
Dec
(1) |
| 2013 |
Jan
(27) |
Feb
|
Mar
(11) |
Apr
(14) |
May
|
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(25) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Robert P. <rob...@ho...> - 2004-06-06 04:49:16
|
Michael I encountered the same problem but on Windows 2000 as the host. Someone = else pointed out that I need to disable some kind of checksum = caching/software checksum on the network adaptor card. I am away from my = office machine and cannot find out what config it is. Go to the = "Properties" panel of your network card and see if there is something = like that and disable it. See if it works for you? Thanks. Rob ----- Original Message -----=20 From: Michael Laccetti=20 To: col...@li... ; = col...@li...=20 Sent: Saturday, June 05, 2004 6:36 AM Subject: [coLinux-devel] Unable to connect to coLinux from same box Hey guys, I've got a really weird issue. When I have coLinux running = on this machine (XP), I can't ping it from under XP, and I can't ping XP = from under coLinux. If I VNC to my dedicated Linux box, or my Win2k3 = server, I can SSH/VNC into the coLinux. From coLinux, I can see every = other machine out there, just not the XP that it's sitting on. This is = all sorts of frustrating. Anybody got any ideas as to how I can make = them see each other? Mike |
|
From: David K. <da...@gi...> - 2004-06-06 04:18:59
|
Dan Aloni <da...@co...> wrote: > On Fri, Jun 04, 2004 at 03:04:11PM +0100, Yonghao Wang wrote: > > > daemon: loading configuration from colinux.default.xml > > > > and it popup a windows error message: > > > > "The instruction at "0x0040af85" referenced memory at "0x00000000". The > > memory could not be "read". > > It appears the crash was inside mxml_string_getc. It is possible that > the mxml library crashed on an invalid XML. Please send it over. > > -- > Dan Aloni > da...@co... hi Dan, i ran into this bug too. the first text editor i tried to use to edit the coLinux config file was UltraEdit32. this particular program feels that it's necessary to prepend a BOM (or Byte Order Mark) to the beginning of the file, just because it's "Unicode". coLinux crashes if the xml file starts with a BOM - perhaps it should be renamed a BOMB :-) anyway i suppose colinux needs to be taught to tolerate this thing since other editors do that as well -- apparently Notepad BOMbs xml files, too (see http://koti.mbnet.fi/akini/java/unicodereader/, http://lists.xml.org/archives/xml-dev/200106/msg00389.html and http://blogs.msdn.com/oldnewthing/archive/2004/03/24/95235.aspx). it pisses me off that my editor did that, silently without telling me, as it made my very first experience with coLinux a very frustrating one! it was not until i opened the BOM-munged file in a real *text* editor (rather than a wannabe Unicode editor) that i was warned that this supposed text file now contained binary (high ASCII) characters, and helped me avoid these nasty crashes. and Yonghao, if you need a text editor that doesn't screw up the colinux config file, check out MetaPad: http://liquidninja.com/metapad hope this helps! -dave |
|
From: Terry J. <Ter...@co...> - 2004-06-06 02:07:52
|
I was wondering if anyone has set up apache on the NAT type configuration and if so how was this done?? Thanks in Advance! Terry Blinky |
|
From: Michael L. <mi...@s2...> - 2004-06-06 01:14:17
|
Not quite that big of a newbie. :) As I said before, no firewall is running on XP, there's a physically separate box doing all of that stuff between the net and the local network. Vince, do you perchance have a MSI motherboard? I have the same Broadcom NIC as you do. -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of John LeSueur Sent: June 5, 2004 9:09 PM To: Vince Hoffman Cc: Michael Laccetti; col...@li...; col...@li... Subject: Re: [coLinux-devel] Re: [coLinux-users] Unable to connect to coLinux from same box Try looking at your firewall settings, and remove any on your XP installation. John Vince Hoffman wrote: >On Sat, 5 Jun 2004, Michael Laccetti wrote: > > > >>Hey guys, I've got a really weird issue. When I have coLinux running >>on this machine (XP), I can't ping it from under XP, and I can't ping >>XP from under coLinux. If I VNC to my dedicated Linux box, or my >>Win2k3 server, I can SSH/VNC into the coLinux. From coLinux, I can >>see every other machine out there, just not the XP that it's sitting >>on. This is all sorts of frustrating. Anybody got any ideas as to >>how I can make them see each other? >> >> > >Wish I did :( >I have the dsame problem, I'm running the latest build from >sourceforge, on windows XP sp1. I've tried both the winpcap and the XP >native bridging with no luck. > >some relevent (maybe ? ) data >From daemon: > >Cooperative Linux Daemon, 0.6.1 >Compiled on Sat May 29 16:20:11 2004 > >From config file: > > <network index="0" name="Broadcom NetXtreme Gigabit Ethernet" >type="bridged"/> > >From startup: > >co_message_switch: setting callback rule for 6 >bridged-net-daemon: Checking adapter: Generic NdisWan adapter >bridged-net-daemon: Checking adapter: MS Tunnel Interface Driver >bridged-net-daemon: Checking adapter: Broadcom NetXtreme Gigabit >Ethernet Driver (Microsoft's Packet Scheduler) >bridged-net-daemon: Listening on: Broadcom NetXtreme Gigabit Ethernet >Driver (Mi crosoft's Packet Scheduler) ... >bridged-net-daemon: Listening for: (ether dst 00:43:4f:4e:45:30) or >(ether broad cast or multicast) or (ip broadcast or multicast) pipe >client 0/8: Connecting to daemon... >pipe client 0/8: Connection established >daemon: module connected: conet0 >co_message_switch: setting callback rule for 8 > >More disturbingly a tcpdump of a ping between them (colinux= 10.0.0.120 >windows= 10.0.0.10) ping gives: > >colinux root # ping 10.0.0.10 >PING 10.0.0.10 (10.0.0.10) 56(84) bytes of data. > >--- 10.0.0.10 ping statistics --- >2 packets transmitted, 0 received, 100% packet loss, time 1015ms > >while tcpdump shows: > >listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes >20:03:05.234086 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo request seq 1 >20:03:05.234811 IP 10.0.0.120.1034 > unsane.co.uk.domain: >46843+[|domain] >20:03:05.236848 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 1 >20:03:05.236878 IP unsane.co.uk.domain > 10.0.0.120.1034: 46843 >NXDomain*[|doma in] >20:03:05.237063 IP 10.0.0.120.1034 > unsane.co.uk.domain: >46844+[|domain] 20:03:05.238790 IP unsane.co.uk.domain > >10.0.0.120.1034: 46844 NXDomain*[|doma in] >20:03:05.238909 IP 10.0.0.120.1034 > unsane.co.uk.domain: >46845+[|domain] >20:03:05.240744 IP unsane.co.uk.domain > 10.0.0.120.1034: >46845*[|domain] >20:03:06.249358 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo request seq 2 >20:03:06.251320 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 2 >20:03:10.229086 arp who-has 10.0.0.10 tell 10.0.0.120 >20:03:10.229242 arp who-has unsane.co.uk tell 10.0.0.120 >20:03:10.231194 arp reply 10.0.0.10 is-at 00:0c:76:41:77:9f >20:03:10.231695 arp reply unsane.co.uk is-at 00:50:8b:03:6d:00 > >which if you cut out the DNS traffic, shoes ping request and replys. > >Any suggestions welcome, should i ask on the developers list ? > >Vince > > > > >>Mike >> >> >> > > >------------------------------------------------------- >This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one >installation-authoring solution that does it all. Learn more and >evaluate today! http://www.installshield.com/Dev2Dev/0504 >_______________________________________________ >coLinux-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ coLinux-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: John L. <jo...@su...> - 2004-06-06 01:07:19
|
Try looking at your firewall settings, and remove any on your XP installation. John Vince Hoffman wrote: >On Sat, 5 Jun 2004, Michael Laccetti wrote: > > > >>Hey guys, I've got a really weird issue. When I have coLinux running on >>this machine (XP), I can't ping it from under XP, and I can't ping XP from >>under coLinux. If I VNC to my dedicated Linux box, or my Win2k3 server, I >>can SSH/VNC into the coLinux. From coLinux, I can see every other machine >>out there, just not the XP that it's sitting on. This is all sorts of >>frustrating. Anybody got any ideas as to how I can make them see each >>other? >> >> > >Wish I did :( >I have the dsame problem, I'm running the latest build from sourceforge, >on windows XP sp1. I've tried both the winpcap and the XP native bridging >with no luck. > >some relevent (maybe ? ) data >From daemon: > >Cooperative Linux Daemon, 0.6.1 >Compiled on Sat May 29 16:20:11 2004 > >From config file: > > <network index="0" name="Broadcom NetXtreme Gigabit Ethernet" type="bridged"/> > >From startup: > >co_message_switch: setting callback rule for 6 >bridged-net-daemon: Checking adapter: Generic NdisWan adapter >bridged-net-daemon: Checking adapter: MS Tunnel Interface Driver >bridged-net-daemon: Checking adapter: Broadcom NetXtreme Gigabit Ethernet >Driver > (Microsoft's Packet Scheduler) >bridged-net-daemon: Listening on: Broadcom NetXtreme Gigabit Ethernet >Driver (Mi >crosoft's Packet Scheduler) ... >bridged-net-daemon: Listening for: (ether dst 00:43:4f:4e:45:30) or (ether >broad >cast or multicast) or (ip broadcast or multicast) >pipe client 0/8: Connecting to daemon... >pipe client 0/8: Connection established >daemon: module connected: conet0 >co_message_switch: setting callback rule for 8 > >More disturbingly a tcpdump of a ping between them (colinux= 10.0.0.120 >windows= 10.0.0.10) >ping gives: > >colinux root # ping 10.0.0.10 >PING 10.0.0.10 (10.0.0.10) 56(84) bytes of data. > >--- 10.0.0.10 ping statistics --- >2 packets transmitted, 0 received, 100% packet loss, time 1015ms > >while tcpdump shows: > >listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes >20:03:05.234086 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo request seq 1 >20:03:05.234811 IP 10.0.0.120.1034 > unsane.co.uk.domain: 46843+[|domain] >20:03:05.236848 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 1 >20:03:05.236878 IP unsane.co.uk.domain > 10.0.0.120.1034: 46843 >NXDomain*[|doma >in] >20:03:05.237063 IP 10.0.0.120.1034 > unsane.co.uk.domain: 46844+[|domain] >20:03:05.238790 IP unsane.co.uk.domain > 10.0.0.120.1034: 46844 >NXDomain*[|doma >in] >20:03:05.238909 IP 10.0.0.120.1034 > unsane.co.uk.domain: 46845+[|domain] >20:03:05.240744 IP unsane.co.uk.domain > 10.0.0.120.1034: 46845*[|domain] >20:03:06.249358 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo request seq 2 >20:03:06.251320 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 2 >20:03:10.229086 arp who-has 10.0.0.10 tell 10.0.0.120 >20:03:10.229242 arp who-has unsane.co.uk tell 10.0.0.120 >20:03:10.231194 arp reply 10.0.0.10 is-at 00:0c:76:41:77:9f >20:03:10.231695 arp reply unsane.co.uk is-at 00:50:8b:03:6d:00 > >which if you cut out the DNS traffic, shoes ping request and replys. > >Any suggestions welcome, should i ask on the developers list ? > >Vince > > > > >>Mike >> >> >> > > >------------------------------------------------------- >This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one >installation-authoring solution that does it all. Learn more and >evaluate today! http://www.installshield.com/Dev2Dev/0504 >_______________________________________________ >coLinux-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
|
From: Vince H. <jh...@un...> - 2004-06-05 20:05:27
|
On Sat, 5 Jun 2004, Michael Laccetti wrote: > Hey guys, I've got a really weird issue. When I have coLinux running on > this machine (XP), I can't ping it from under XP, and I can't ping XP from > under coLinux. If I VNC to my dedicated Linux box, or my Win2k3 server, I > can SSH/VNC into the coLinux. From coLinux, I can see every other machine > out there, just not the XP that it's sitting on. This is all sorts of > frustrating. Anybody got any ideas as to how I can make them see each > other? Wish I did :( I have the dsame problem, I'm running the latest build from sourceforge, on windows XP sp1. I've tried both the winpcap and the XP native bridging with no luck. some relevent (maybe ? ) data From daemon: Cooperative Linux Daemon, 0.6.1 Compiled on Sat May 29 16:20:11 2004 From config file: <network index="0" name="Broadcom NetXtreme Gigabit Ethernet" type="bridged"/> From startup: co_message_switch: setting callback rule for 6 bridged-net-daemon: Checking adapter: Generic NdisWan adapter bridged-net-daemon: Checking adapter: MS Tunnel Interface Driver bridged-net-daemon: Checking adapter: Broadcom NetXtreme Gigabit Ethernet Driver (Microsoft's Packet Scheduler) bridged-net-daemon: Listening on: Broadcom NetXtreme Gigabit Ethernet Driver (Mi crosoft's Packet Scheduler) ... bridged-net-daemon: Listening for: (ether dst 00:43:4f:4e:45:30) or (ether broad cast or multicast) or (ip broadcast or multicast) pipe client 0/8: Connecting to daemon... pipe client 0/8: Connection established daemon: module connected: conet0 co_message_switch: setting callback rule for 8 More disturbingly a tcpdump of a ping between them (colinux= 10.0.0.120 windows= 10.0.0.10) ping gives: colinux root # ping 10.0.0.10 PING 10.0.0.10 (10.0.0.10) 56(84) bytes of data. --- 10.0.0.10 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1015ms while tcpdump shows: listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes 20:03:05.234086 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo request seq 1 20:03:05.234811 IP 10.0.0.120.1034 > unsane.co.uk.domain: 46843+[|domain] 20:03:05.236848 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 1 20:03:05.236878 IP unsane.co.uk.domain > 10.0.0.120.1034: 46843 NXDomain*[|doma in] 20:03:05.237063 IP 10.0.0.120.1034 > unsane.co.uk.domain: 46844+[|domain] 20:03:05.238790 IP unsane.co.uk.domain > 10.0.0.120.1034: 46844 NXDomain*[|doma in] 20:03:05.238909 IP 10.0.0.120.1034 > unsane.co.uk.domain: 46845+[|domain] 20:03:05.240744 IP unsane.co.uk.domain > 10.0.0.120.1034: 46845*[|domain] 20:03:06.249358 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo request seq 2 20:03:06.251320 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 2 20:03:10.229086 arp who-has 10.0.0.10 tell 10.0.0.120 20:03:10.229242 arp who-has unsane.co.uk tell 10.0.0.120 20:03:10.231194 arp reply 10.0.0.10 is-at 00:0c:76:41:77:9f 20:03:10.231695 arp reply unsane.co.uk is-at 00:50:8b:03:6d:00 which if you cut out the DNS traffic, shoes ping request and replys. Any suggestions welcome, should i ask on the developers list ? Vince > > Mike > |
|
From: Vitaly B. <vi...@01...> - 2004-06-05 18:17:48
|
Hello David, True, your way worked better.. Though I still can't realize really what was wrong when I compiled it myself. My previous PostgreSQL (before I installed it your way) version() said "PostgreSQL 7.4.2 on i686-pc-linux-gnu, compiled by GCC 2.95.4". Anyway, while we're on the subject... I am making a <block_device> for CoLinux to serve as the database partition (PostgreSQL and its data will be there). Will it be better if I just create a blank file to use as the block_device (with fsutil) or should I actualy do a regular parition for it? Regards, Vitaly Belman ICQ: 1912453 AIM: VitalyB1984 MSN: tmd...@ho... Yahoo!: VitalyBe Saturday, June 5, 2004, 9:41:25 AM, you wrote: DK> Hi Vitaly, DK> Vitaly Belman <vi...@01...> wrote: >> >> [...] using CoLinux 0.6.1 with Debian distribution. >> [...] and I also installed PsgreSQL 7.4.2, >> [...] psql [...] hangs for a 10 seconds or so [and then] >> > >> > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) >> > VM: killing process psql >> >> The database itself seems to operate just fine... And I imported data >> to it and connected to it from another machine pgsql and another GUI >> clients. DK> i'm also runnning coLinux 0.6.1 using the debian distro and (select DK> version();) "PostgreSQL 7.4.2 on i386-pc-linux-gnu, compiled by GCC DK> 2.95.4" and am having *no* problems with it whatsoever. my psql works DK> great. DK> but pg 7.4.2 is not apt-"gettable" (for Woody) did you compile it DK> yourself? i got pg 7.4 from the unofficial apt-get repository at DK> http://backports.org and as i said, no problems so far ...and i've been DK> stressing it extensively for the last several days. DK> hth, DK> -dave DK> ------------------------------------------------------- DK> This SF.Net email is sponsored by the new InstallShield X. DK> From Windows to Linux, servers to mobile, InstallShield X is the one DK> installation-authoring solution that does it all. Learn more and DK> evaluate today! http://www.installshield.com/Dev2Dev/0504 DK> _______________________________________________ DK> coLinux-users mailing list DK> coL...@li... DK> https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Dan A. <da...@co...> - 2004-06-05 18:09:48
|
On Fri, Jun 04, 2004 at 03:04:11PM +0100, Yonghao Wang wrote: > daemon: loading configuration from colinux.default.xml > > and it popup a windows error message: > > "The instruction at "0x0040af85" referenced memory at "0x00000000". The > memory could not be "read". It appears the crash was inside mxml_string_getc. It is possible that the mxml library crashed on an invalid XML. Please send it over. -- Dan Aloni da...@co... |
|
From: Michael L. <mi...@s2...> - 2004-06-05 17:13:46
|
No, I have a proper firewall that sits between the internet connection and all of the machines here. -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of tei Sent: June 5, 2004 10:37 AM To: col...@li... Subject: Re: [coLinux-users] Unable to connect to coLinux from same box Michael Laccetti wrote: > > Hey guys, I've got a really weird issue. When I have coLinux running > on this machine (XP), I can't ping it from under XP, and I can't ping > XP from under coLinux. If I VNC to my dedicated Linux box, or my > Win2k3 server, I can SSH/VNC into the coLinux. From coLinux, I can > see every other machine out there, just not the XP that it's sitting > on. This is all sorts of frustrating. Anybody got any ideas as to > how I can make them see each other? > > Mike Its the XP "protected" with a firewall that block pings? ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: tei <42...@in...> - 2004-06-05 14:36:49
|
Michael Laccetti wrote: > > Hey guys, I've got a really weird issue. When I have coLinux running on > this machine (XP), I can't ping it from under XP, and I can't ping XP > from under coLinux. If I VNC to my dedicated Linux box, or my Win2k3 > server, I can SSH/VNC into the coLinux. From coLinux, I can see every > other machine out there, just not the XP that it's sitting on. This is > all sorts of frustrating. Anybody got any ideas as to how I can make > them see each other? > > Mike Its the XP "protected" with a firewall that block pings? |
|
From: Michael L. <mi...@s2...> - 2004-06-05 13:36:30
|
Hey guys, I've got a really weird issue. When I have coLinux running on this machine (XP), I can't ping it from under XP, and I can't ping XP from under coLinux. If I VNC to my dedicated Linux box, or my Win2k3 server, I can SSH/VNC into the coLinux. From coLinux, I can see every other machine out there, just not the XP that it's sitting on. This is all sorts of frustrating. Anybody got any ideas as to how I can make them see each other? Mike |
|
From: David K. <da...@gi...> - 2004-06-05 05:58:16
|
Hi Vitaly, Vitaly Belman <vi...@01...> wrote: > > [...] using CoLinux 0.6.1 with Debian distribution. > [...] and I also installed PsgreSQL 7.4.2, > [...] psql [...] hangs for a 10 seconds or so [and then] > > > > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) > > VM: killing process psql > > The database itself seems to operate just fine... And I imported data > to it and connected to it from another machine pgsql and another GUI > clients. i'm also runnning coLinux 0.6.1 using the debian distro and (select version();) "PostgreSQL 7.4.2 on i386-pc-linux-gnu, compiled by GCC 2.95.4" and am having *no* problems with it whatsoever. my psql works great. but pg 7.4.2 is not apt-"gettable" (for Woody) did you compile it yourself? i got pg 7.4 from the unofficial apt-get repository at http://backports.org and as i said, no problems so far ...and i've been stressing it extensively for the last several days. hth, -dave |
|
From: Robert C. <rw...@al...> - 2004-06-05 05:50:53
|
Hello Jon, On Friday, Jun 4, 2004, at 21:46 US/Central, Jon Marler wrote: > I thought that I would throw up a screen grab using colinux with > fedora core2 running xorg-x11 and gnome. I am using vnc to hit the > desktop. I also installed webmin with ssl. Just a thought: have you tried connecting via the Java interface (port 5800??). Apparently, this would allow you to access coLinux via IE's built-in Java support. > Here is the screen shot: > http://jonmarler.com/pics/colinux-FC2-gnome-webmin.png Oh, that is sweet. > Just playing at this stage. Nice job of playing. I'd be great if you could write up the steps you took to get this setup and post them on the wiki page. In particular, I'm curious to know what hardware, what host OS, which colinux binaries, which filesystem image (how you created FC2), and what some of your config files looked like (e.g. defaults.colinux.xml, /etc/hosts, /etc/resolv.conf, /etc/sysconfig/network*). This would be valuable information so that others can reproduce your results. Regards, - Robert |
|
From: Jon M. <jo...@we...> - 2004-06-05 02:46:35
|
I thought that I would throw up a screen grab using colinux with fedora core2 running xorg-x11 and gnome. I am using vnc to hit the desktop. I also installed webmin with ssl. Here is the screen shot: http://jonmarler.com/pics/colinux-FC2-gnome-webmin.png Just playing at this stage. -- Respectfully, Jon Marler |
|
From: <joe...@ce...> - 2004-06-04 22:02:57
|
When I started colinux without the -t nt, I noticed this message at the end
of the dos window:
bridged-net-daemon: Checking adapter: Generic NdisWan adapter
bridged-net-daemon: Checking adapter: NOC Extranet Access Adapter
bridged-net-daemon: Checking adapter: Broadcom NetXtreme Gigabit Ethernet
Driver
When I changed the _name_ colinux.xml bridged network node from:
"Broadcom 570x Gigabit Integrated Controller"
to be:
"Broadcom NetXtreme Gigabit Ethernet Driver"
it fired right up!
However, why would the name of the interface change between wincap, tap,
and/or colinux versions?
-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of
joe...@ce...
Sent: Friday, June 04, 2004 3:48 PM
To: col...@li...
Subject: [coLinux-users] Upgraded to 0.6.1, but networking stopped
Greetings.
I upgraded today from 0.6 to 0.6.1, and I'm having a little trouble.
I'm working on a W2K box connected to the company lan. My old
install was the debian 1g version, and I was very proud to have not only
changed my machine name, but also gotten the company dhcp to give me an IP
and the DNS to recognise the local name.
I uninstalled via add/remove programs as suggested, then installed
and let the installer install the tap driver and colinux. I renamed the tap
driver connection TAPConnection. I hadn't changed the default.colinux.xml
to a different name, so I was chagrined to see that it had been overwritten.
After the install, I read about it in the readme.
So, I rebooted and pointed the default.colinux.xml (now renamed) to
my old image and swap and gave it a try. It hung on the network
connections, but eventually got up to the login. I haven't installed it as
a service, because I wanted to make sure that it was working first.
However, when I log in my eth0 interface does not connect.
fermi_01:~# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
dmesg includes these lines:
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
In the dos window ipconfig reveals this:
Ethernet adapter TAPConnection:
Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.179.187
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
Trying to ping that IP address from the colinux side I get
fermi_01:~# ping 169.254.179.187
PING 169.254.179.187 (169.254.179.187): 56 data bytes
ping: sendto: Network is unreachable
ping: wrote 169.254.179.187 64 chars, ret=-1
ping: sendto: Network is unreachable
ping for 127.0.0.1 from colinux works OK
fermi_01:~# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.1 ms
Meanwhile, I'm looking at the TAPConnection Status, and every couple of
minutes or so the sent packets goes up by 2 or 3, but receieved remains at
zero. No pings that I'm doing seem to have any effect on these numbers.
The colinux.xml network node looks like this:
<network index="0" type="tap" />
What else am I missing?
Thanks,
Joe
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users
|
|
From: <joe...@ce...> - 2004-06-04 21:48:30
|
Greetings.
I upgraded today from 0.6 to 0.6.1, and I'm having a little trouble.
I'm working on a W2K box connected to the company lan. My old
install was the debian 1g version, and I was very proud to have not only
changed my machine name, but also gotten the company dhcp to give me an IP
and the DNS to recognise the local name.
I uninstalled via add/remove programs as suggested, then installed
and let the installer install the tap driver and colinux. I renamed the tap
driver connection TAPConnection. I hadn't changed the default.colinux.xml
to a different name, so I was chagrined to see that it had been overwritten.
After the install, I read about it in the readme.
So, I rebooted and pointed the default.colinux.xml (now renamed) to
my old image and swap and gave it a try. It hung on the network
connections, but eventually got up to the login. I haven't installed it as
a service, because I wanted to make sure that it was working first.
However, when I log in my eth0 interface does not connect.
fermi_01:~# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
dmesg includes these lines:
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
In the dos window ipconfig reveals this:
Ethernet adapter TAPConnection:
Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.179.187
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
Trying to ping that IP address from the colinux side I get
fermi_01:~# ping 169.254.179.187
PING 169.254.179.187 (169.254.179.187): 56 data bytes
ping: sendto: Network is unreachable
ping: wrote 169.254.179.187 64 chars, ret=-1
ping: sendto: Network is unreachable
ping for 127.0.0.1 from colinux works OK
fermi_01:~# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.0 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.1 ms
Meanwhile, I'm looking at the TAPConnection Status, and every couple of
minutes or so the sent packets goes up by 2 or 3, but receieved remains at
zero. No pings that I'm doing seem to have any effect on these numbers.
The colinux.xml network node looks like this:
<network index="0" type="tap" />
What else am I missing?
Thanks,
Joe
|
|
From: Guy G. - P. <gu...@wy...> - 2004-06-04 21:36:42
|
Sure, I use winpcap bridging on XP SP1 using colinux 0.6.1 and don't have this problem. I can ping the colinux host from the xp host, as well as shh into it. It doesn't show up inder ipconfig since there's no real adapter installed, but it is there and does seem to work exactly the same localy as it does remotely. I hostly don't know what might be wrong for you :( Guy Vince Hoffman wrote: >Hi all, > >I have colinux happily working (thanks to everyone who put time and effort >into this,) however I cannot get my host (windows XP sp1) to talk over the >network to the colinux install (0.6.1) my other machine can see both fine >so i know its working otherwise. Is it possible to make tem see each other >? Will switching to windows XP bridgig fmake it work ? (dont realy want to >have to, but will if its the only way.) >Thanks in advance > >Vince > > >------------------------------------------------------- >This SF.Net email is sponsored by the new InstallShield X. >>From Windows to Linux, servers to mobile, InstallShield X is the one >installation-authoring solution that does it all. Learn more and >evaluate today! http://www.installshield.com/Dev2Dev/0504 >_______________________________________________ >coLinux-users mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > > |
|
From: Vince H. <jh...@un...> - 2004-06-04 21:21:39
|
Hi all, I have colinux happily working (thanks to everyone who put time and effort into this,) however I cannot get my host (windows XP sp1) to talk over the network to the colinux install (0.6.1) my other machine can see both fine so i know its working otherwise. Is it possible to make tem see each other ? Will switching to windows XP bridgig fmake it work ? (dont realy want to have to, but will if its the only way.) Thanks in advance Vince |
|
From: Chuck A. <ch...@da...> - 2004-06-04 20:59:26
|
Robert Citek wrote: > I'm curious to know what in particular did you find difficult about > configuring networking? I'd like to know so that I can incorporate > those changes in the next bundle. Confusion of the concepts of "bridged networking", for starters -- coLinux uses it in the sense that VMware does, whereas it means something quite different in XP (in XP it's a sort of poor-man's VLAN). I never got bridged networking to work (not certain whether it was due to my struggles with ICS), so I ended up using the TAP driver and bridging it. The TAP driver took ages to install, during which it just hung for a while. I was certain it had locked up, so I had killed the process it a couple times in my initial attempts. Also the advice to ensure that it's "always connected" was something I found elsewhere. I wrestled with ICS for a while but it always wanted to change the IP of my network interface to a hardwired 192.168.0.1 ... I don't think my 10.0.0.0 LAN would care much for that. I was unfamiliar with XP's bridging, so it took me a little while to understand it. Install the TAP driver, set it to "always connected", bridge it, set it on the linux side to use DHCP, and it works splendidly (assuming you install dhcpcd or pump and have a DHCP server on the network). It was just the trial and error of discovering those steps that was tricky. chuck |
|
From: Robert C. <rw...@al...> - 2004-06-04 20:49:33
|
On Thursday, Jun 3, 2004, at 17:17 US/Central, Robert Citek wrote: > Here are the steps I took: > > from within Windows ... > * download or create a file with a bunch of zeros. I used one of > the swap files and uncompressed it with 7-zip: > o http://gniarf.nerim.net/colinux/swap/swap_64Mb.bz2 I repeated the process with the 1024 MB swap image: # df -H . Filesystem Size Used Avail Use% Mounted on /dev/cobd0 2.2G 156M 1.9G 8% / And it seemed to work since I was able to create a 1.5 GB file, which spanned the original 1 GB limit of the filesystem: # dd if=/dev/zero of=/tmp/zeros.big bs=10M count=150 150+0 records in 150+0 records out 1572864000 bytes transferred in 652.248297 seconds (2411450 bytes/sec) # df -H . Filesystem Size Used Avail Use% Mounted on /dev/cobd0 2.2G 1.8G 299M 86% / Regards, - Robert |
|
From: Vinson C. <vco...@gw...> - 2004-06-04 19:40:59
|
While attempting to run colinux-net-daemon.exe I get an error: "Device index
not specified."
What am I doing wrong? Thanks for any help.
Currently my default.colinux file reads:
<?xml version="1.0" encoding="UTF-8"?>
<colinux>
<!-- This line needs to point to your root file system.
For example change "root_fs" to the name of the Debian image.
Inside coLinux it will be /dev/cobd0 -->
<block_device index="0" path="\DosDevices\c:\Program
Files\coLinux\Debian-3.0r0.ext3.1gb"
enabled="true" />
<!-- This line can specify a swap file if you wish, or an additional
image file, it will /dev/cobd1. Additional block_devices can
be specified in the same manner by increasing the index -->
<block_device index="1" path="\DosDevices\c:\Program
Files\coLinux\swap_device"
enabled="true" />
<!-- bootparams allows you to pass kernel boot parameters -->
<bootparams>root=/dev/cobd0</bootparams>
<!-- image allows you to specify the kernel to boot -->
<image path="vmlinux" />
<!-- this line allows you to specify the amount of memory available
to coLinux -->
<memory size="64" />
<!-- This allows you to modify networking parameters, see the README
or website for more information -->
<network index="0" type="tap" />
</colinux>
|
|
From: Robert C. <rw...@al...> - 2004-06-04 16:47:46
|
On Friday, Jun 4, 2004, at 10:53 US/Central, Chuck Adams wrote: > Robert Citek wrote: >> I agree. Which is why I created a colinux bundle with the binaries, >> a filesytem, and some networking tweaks. Have a look on the wiki: >> colinux.org/wiki/index.php/PreBuiltBundles > > Being that the most difficult part of getting coLinux working is the > networking, I can imagine the prebuiltbundles are useful to a point > ... Yup, networking is the most difficult, with XP being a more difficult host than 2000, which is why I had to write the networking section as instructions on the wiki page. I wish I knew more on how to automate the configuration process. As for being useful to a point, absolutely correct. They are not meant to be a one-size-fits-all end-solution. I created them as starting points, so that people could get something working quickly and learn how the various pieces to colinux fit together. Hopefully, as users get more familiar with colinux, they will then tweak colinux to their heart's content, e.g changing filesystems, adding swap, adding/modifying installed applications, trying newer binaries, etc. I'm curious to know what in particular did you find difficult about configuring networking? I'd like to know so that I can incorporate those changes in the next bundle. Thanks in advance for any feedback. Regards, - Robert |
|
From: Chuck A. <ch...@da...> - 2004-06-04 15:53:46
|
Robert Citek wrote: > I agree. Which is why I created a colinux bundle with the binaries, a > filesytem, and some networking tweaks. Have a look on the wiki: > > colinux.org/wiki/index.php/PreBuiltBundles Being that the most difficult part of getting coLinux working is the networking, I can imagine the prebuiltbundles are useful to a point ... I use coLinux in a work environment on win XP, so I couldn't go reassigning my NIC interface the way the bloody stupid crippled ICS wants to, but I found that installing the TAP driver and using the network bridging in XP to bridge it to my real connection works like a charm. You'll want to set the TAP driver to "always on" tho, or it'll be kicked out of the bridge on reboot. Another thing to note for new users: the TAP driver can take a LONG time to install during which the add device control panel will just hang with no feedback. Be patient, it will eventually install. coLinux is definitely awesome. I can't wait for the patch to become accepted into the mainstream kernel, or failing that, at least as a USE flag in gentoo... chuck |
|
From: Robert C. <rw...@al...> - 2004-06-04 15:15:26
|
On Friday, Jun 4, 2004, at 09:56 US/Central, Crack, JC wrote: > However as a newcommer to the world of linux I'm finding it a little > hard to get things up and running. I've installed/downloaded all the > necessary bits but > double clicking on colinux-daemon.exe doesn't do anything. HELP!? > > Any chance of a tutorial or some form of step by step guide for new > commers? I agree. Which is why I created a colinux bundle with the binaries, a filesytem, and some networking tweaks. Have a look on the wiki: colinux.org/wiki/index.php/PreBuiltBundles They are not perfect and not the bleeding edge, but they do get you up to speed quickly. Once you are familiar with how colinux operates, then changing the pieces (e.g. the binaries, the filesystem, the networking) becomes much simpler. For more detailed notes, including how to get X11 w/VNC working, have a look here: http://cwelug.org/cgi-bin/wiki.cgi?CoLinux Give it a try and the let list know how it goes. Regards, - Robert |
|
From: Vitaly B. <vi...@01...> - 2004-06-04 15:05:04
|
Hello JC, I found this tutorial the most helpful: http://www.colinux.org/wiki/index.php/GettingStartedLong Regards, Vitaly Belman ICQ: 1912453 AIM: VitalyB1984 MSN: tmd...@ho... Yahoo!: VitalyBe Friday, June 4, 2004, 5:56:15 PM, you wrote: CJ> Hi, CJ> I think CoLinux is the best idea since sliced bread for those who want CJ> to use linux CJ> but don't want a dual boot or dedicated linux system. CJ> However as a newcommer to the world of linux I'm finding it a little CJ> hard to get things CJ> up and running. I've installed/downloaded all the necessary bits but CJ> double clicking on CJ> colinux-daemon.exe doesn't do anything. HELP!? CJ> Any chance of a tutorial or some form of step by step guide for new CJ> commers? CJ> Cheers, CJ> Jason CJ> ------------------------------------------------------- CJ> This SF.Net email is sponsored by the new InstallShield X. CJ> From Windows to Linux, servers to mobile, InstallShield X is the one CJ> installation-authoring solution that does it all. Learn more and CJ> evaluate today! http://www.installshield.com/Dev2Dev/0504 CJ> _______________________________________________ CJ> coLinux-users mailing list CJ> coL...@li... CJ> https://lists.sourceforge.net/lists/listinfo/colinux-users |
119 messages has been excluded from this view by a project administrator.
