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: peter g. <plu...@p1...> - 2004-08-26 19:20:41
|
> As a newbie I have some questions: > > Is coLinux in userspace? the daemon is but the driver and linux kernel are not > Does it run on any OS? any that the daemon and driver can be ported to (currently windows and linux afaict) > Is it an NT subsystem? no > Can it be used as a ReactOS subsystem? the answer to the last question kinda makes this one irrelevent the daemon gets given cpu use by windows like any other process this calls into the driver which in turn calls into linux messages are passed between the kernel and the daemon via the driver --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.737 / Virus Database: 491 - Release Date: 11/08/2004 |
|
From: Peter W. <pet...@ep...> - 2004-08-26 13:18:24
|
As a newbie I have some questions: Is coLinux in userspace? Does it run on any OS? Is it an NT subsystem? Can it be used as a ReactOS subsystem? Greetings Peter |
|
From: Rene T. <mei...@gm...> - 2004-08-26 08:43:08
|
hi, it's described in the colinux wiki: http://www.colinux.org/wiki/index.php/XCoLinux regards, rene On Thu, 26 Aug 2004 15:42:05 +0800, mohan <mo...@va...> wrote: > Hi Bothari, > > Do you any documentation on how to go about getting the x-server > working with the co-linux. ? Appreciate your feedback on this. > > Regards, > > Mohan > > > > > -----Original Message----- > From: col...@li... > [mailto:col...@li...] On Behalf Of Bothari > Sent: Wednesday, August 25, 2004 11:33 PM > To: col...@li... > Subject: Re: [coLinux-users] windows x-server > > Group, > I tried it on Win2K, 1.7G processor, 1G memory, 1024x768. It came > up fine and I was able to run it, but it was very slow. I could type > in a whole sentace in firefox before the text started showing up. > Neither the xload on colinux or the task manager in W2K seemed to > indicate what the hold up was. I'm using bridged networking, but > that's what I use with cygwin, and it's lots faster. > Does anyone have a tip for speeding things up? > Joe > > On Tue, 24 Aug 2004 23:37:35 +0200, Rene Tegel <mei...@gm...> > wrote: > > Hi list, > > > > maybe somewhat off-topic, but recently i found a nice x-server that > > does a fine job connecting to colinux. it may be a convenient > > replacement for cygwin. > > > > The server was a commercial product that only very recently (august > > 1.) has been released as freeware. 'managed' window integration is > > supported. > > > > you can download it from http://www.pexus.com/ > > > > hope this is of help for someone, > > > > regards, > > > > rene > > > > ------------------------------------------------------- > > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > -- > "Do what you must do." Kathy Ferguson > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: <ti...@fu...> - 2004-08-26 08:16:39
|
This is general what I do to get X and colinux working.
- Install cygwin with X (or full cygwin, takes a bit longer)
- Open cygwin shell and start the X server with 'X <options>'
I use the following options
-ac No authentication required
-multiwindow Use windows desktop as window manager, works fine
and faster than using extra X window manager
-clipboard Clipboard is not enabled by default
-nodecoration I'm not sure if this makes any sense with -multiwindow
-xkblayout fi I'm from Finland..
-xkblayout pc105 Supposedly helps to get some keys working
-xkbvariant nodeadkeys
-xkbrules xfree86
If you google "cygwin X" then you can find better description of some of
these parameters. However, not for -ac, because it is 'standard' X server
parameter, for that, and another option -query, you need to consult "man
X" perhaps, on system that has that man page. Or google.
I also add & to the end so that I can use the cygwin shell for other
things.
In the colinux side, you just install the X programs and run them
with DISPLAY=192.168.1.1:0.0, for example:
DISPLAY=192.168.1.1:0.0 xterm &
You will need -ac, or -query. With -query 192.168.1.1 you will probably
need to install gdm or similar display manager to colinux system. That
IMHO is quite waste while -ac -multiwindow works just fine and you don't
have to install lots of packages just to get X working.
> Is there any documentation guide on 2.6.7 kernel (debian/fedora) using
> colinux 2.6.7 with x-server. Appreciate if someone in this group can
> assist me in getting it to work for me.
--
timo
|
|
From: mohan <Mo...@va...> - 2004-08-26 07:51:39
|
Dear all, Is there any documentation guide on 2.6.7 kernel (debian/fedora) using = colinux 2.6.7 with x-server. Appreciate if someone in this group can = assist me in getting it to work for me.=20 Appreciate you help. Mohan -----Original Message----- From: col...@li... = [mailto:col...@li...] On Behalf Of Claude = LeFrancois (QB/EMC) Sent: Tuesday, August 24, 2004 1:38 AM To: 'col...@li...' Subject: FW: [coLinux-users] NFS performance and colinux Hi George, I have tested successfully option 1 from the list provided in my = previous message. So, I have been able to make a Solaris jumpstart from = a Windows 2000 based system using coLinux 0.6.2 (snapshot-20040710) ! I = have recompiled the 2.6.7 colinux kernel with the "NFS over TCP" feature = enabled. It works like a charm. The installation speed is very good. It's quite = the same speed than a native Linux system. Of course, the IP = fragmentation/reassembly problem I have observed using the bridged = network configuration under win2k is not solved but at least there is a = workaround. As far as I can see, there is no more = fragmentation/reassembly problem using the new NFS feature because I = think each NFS packet subject to fragmentation is replaced by a "RPC = continuation" packet. If a part of a packet is missing, I guess only the = missing element will re-transmit instead of the whole NFS stream in a = normal world. This is due to the TCP nature and design. So, the "NFS = over TCP" feature improves NFS reliability for connections under "bad" = networking conditions. Thanks, Claude. Claude LeFran=E7ois=20 cla...@er... -----Original Message----- From: Claude LeFrancois (QB/EMC)=20 Sent: Wednesday, August 18, 2004 5:46 PM To: 'gboutwel' Cc: col...@li... Subject: RE: [coLinux-users] NFS performance and colinux Hi George, I have installed snapshot-20040710. I have made the modification to the = xml file to attach to my Broadcom interface. I have booted my Fedora = Core 1 distribution with the 2.6.7 kernel without a problem. This = snapshot does not contain the nfsd support. So, I have recompiled the = colinux kernel with the appropriate settings. I have also learned that = the NFS daemon service has changed in the 2.6 kernels. So, I had to make = a little adaptation (mount -t nfsd nfsd /proc/fs/nfs). Finally, I got my = colinux working fine. :) However, my Solaris jumpstart does not work yet. I hit the same problem. = It seems the IP fragmentation problem is still there but I have noticed = an good improvement. It looks like the jumpstart client (the Solaris = box) sends a bunch of large NFS read packets at the same time. Colinux = is not able to reply to all of them in time and the jumpstart client = sends ICMP packets with TTL exceeded to colinux. At this moment the = jumpstart client gives "NFS server not responding". The only way I have = to improve this situation is to set the block size to 1024 which avoids = the fragmentation. The bad stuff is that only the root fs benefits from = this settings all the other NFS mounts from the client are 4K blocks. The jumpstart client is point-to-point connected with my laptop using a = cross-over cable. To solve this situation, I see two options: 1. Hard code the NFS packet size to 1024 in the kernel 2. Try the new feature: NFS over TCP But, the fragmentation problem in colinux is not solved... I am a bit = confused now. I don't know what to do at this point. I am using the = bridged networking configuration. I guess it has nothing to do with the = TAP drivers, isn't it ? I am using win2k so there is no way to enable = bridging through the TAP interface because it appears this is only = supported in XP. I absolutely need to use bridging because the jumpstart = client initiates the jumpstart process by a RARP request. Then, I cannot = use NAT because these packets won't be redirected to my colinux = distribution unless a port forwarding mechanism exists. My system is a HP NC8000 laptop. It has 512 MB RAM and 1.5 GHz Pentium M = CPU. The network interface is a Broadcom NetXtreme Gigabit adapter. I = have already disabled TCP checksums and flow control on this interface. Any suggestions are really welcome ! Here is the output of my latest ping test: PING 192.168.0.101 (192.168.0.101) 4096(4124) bytes of data. 4104 bytes from 192.168.0.101: icmp_seq=3D1 ttl=3D255 time=3D2.24 ms 4104 bytes from 192.168.0.101: icmp_seq=3D2 ttl=3D255 time=3D2.10 ms 4104 bytes from 192.168.0.101: icmp_seq=3D3 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D7 ttl=3D255 time=3D2.09 ms 4104 bytes from 192.168.0.101: icmp_seq=3D8 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D10 ttl=3D255 time=3D2.10 ms 4104 bytes from 192.168.0.101: icmp_seq=3D12 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D13 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D15 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D17 ttl=3D255 time=3D2.06 ms 4104 bytes from 192.168.0.101: icmp_seq=3D20 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D23 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D24 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D26 ttl=3D255 time=3D2.09 ms 4104 bytes from 192.168.0.101: icmp_seq=3D27 ttl=3D255 time=3D2.11 ms 4104 bytes from 192.168.0.101: icmp_seq=3D30 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D32 ttl=3D255 time=3D1.97 ms 4104 bytes from 192.168.0.101: icmp_seq=3D33 ttl=3D255 time=3D2.09 ms 4104 bytes from 192.168.0.101: icmp_seq=3D34 ttl=3D255 time=3D2.07 ms --- 192.168.0.101 ping statistics --- 35 packets transmitted, 19 received, 45% packet loss, time 34196ms rtt min/avg/max/mdev =3D 1.974/2.158/2.242/0.087 ms, pipe 2 Thanks, Claude. Claude LeFran=E7ois=20 cla...@er... -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of gboutwel Sent: Wednesday, August 18, 2004 9:32 AM To: col...@li... Cc: Claude LeFrancois (QB/EMC) Subject: Re: [coLinux-users] NFS performance and colinux > > One question: are you using bridged networking ? > > I'm using the tap adapter, bridged by WinXP with my network card. I use both. On the PCAP bridging there is, also, 0% loss of packets using latest sources. > Not sure about that (I made no tests), but it seems the tap-win32 > adapter is somewhat faster and reliable than the bridged adapter. Also, > the code was revised lately to accomodate larger packets transfers. Yeah, most the tests that Dan has done shows TAP to be the faster interface. George ------------------------------------------ Praize? Enter In... http://www.praize.com/ ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: mohan <Mo...@va...> - 2004-08-26 07:41:46
|
Hi Bothari,
Do you any documentation on how to go about getting the x-server
working with the co-linux. ? Appreciate your feedback on this.
Regards,
Mohan
-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of Bothari
Sent: Wednesday, August 25, 2004 11:33 PM
To: col...@li...
Subject: Re: [coLinux-users] windows x-server
Group,
I tried it on Win2K, 1.7G processor, 1G memory, 1024x768. It came
up fine and I was able to run it, but it was very slow. I could type
in a whole sentace in firefox before the text started showing up.=20
Neither the xload on colinux or the task manager in W2K seemed to
indicate what the hold up was. I'm using bridged networking, but
that's what I use with cygwin, and it's lots faster.
Does anyone have a tip for speeding things up? =20
Joe
On Tue, 24 Aug 2004 23:37:35 +0200, Rene Tegel <mei...@gm...>
wrote:
> Hi list,
>=20
> maybe somewhat off-topic, but recently i found a nice x-server that
> does a fine job connecting to colinux. it may be a convenient
> replacement for cygwin.
>=20
> The server was a commercial product that only very recently (august
> 1.) has been released as freeware. 'managed' window integration is
> supported.
>=20
> you can download it from http://www.pexus.com/
>=20
> hope this is of help for someone,
>=20
> regards,
>=20
> rene
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>=20
--=20
"Do what you must do." Kathy Ferguson
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users
|
|
From: Bothari <bo...@gm...> - 2004-08-25 15:33:14
|
Group,
I tried it on Win2K, 1.7G processor, 1G memory, 1024x768. It came
up fine and I was able to run it, but it was very slow. I could type
in a whole sentace in firefox before the text started showing up.
Neither the xload on colinux or the task manager in W2K seemed to
indicate what the hold up was. I'm using bridged networking, but
that's what I use with cygwin, and it's lots faster.
Does anyone have a tip for speeding things up?
Joe
On Tue, 24 Aug 2004 23:37:35 +0200, Rene Tegel <mei...@gm...> wrote:
> Hi list,
>
> maybe somewhat off-topic, but recently i found a nice x-server that
> does a fine job connecting to colinux. it may be a convenient
> replacement for cygwin.
>
> The server was a commercial product that only very recently (august
> 1.) has been released as freeware. 'managed' window integration is
> supported.
>
> you can download it from http://www.pexus.com/
>
> hope this is of help for someone,
>
> regards,
>
> rene
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
--
"Do what you must do." Kathy Ferguson
|
|
From: Kuniyasu S. <k.s...@ai...> - 2004-08-25 06:22:14
|
Dear,
We released new Japanese KNOPPIX which includes coLinux+cygwin/X installer
and batch-file to boot with KNOPPIX-CD.
It enables us to use KNOPPIX on coLinux with cygwin/X.
The detail is described in the following URL.
http://unit.aist.go.jp/it/knoppix/colinux/index-en.html
Iso image is downloadable from following URL.
ftp://ring.aist.go.jp/pub/linux/knoppix/iso/knoppix_v3.4_20040517-20040820.iso
http://ring.aist.go.jp/pub/linux/knoppix/iso/knoppix_v3.4_20040517-20040820.iso
Bittorrent is also available.
http://http://unit.aist.go.jp/it/knoppix/knoppix_v3.4_20040517-20040820.iso.torrent
MD5: d872effcc85721e663b7afd0d0076a17
Have fun. :-)
------
suzaki
|
|
From: Rene T. <mei...@gm...> - 2004-08-24 21:37:38
|
Hi list, maybe somewhat off-topic, but recently i found a nice x-server that does a fine job connecting to colinux. it may be a convenient replacement for cygwin. The server was a commercial product that only very recently (august 1.) has been released as freeware. 'managed' window integration is supported. you can download it from http://www.pexus.com/ hope this is of help for someone, regards, rene |
|
From: <st...@t2...> - 2004-08-24 20:47:41
|
Hey, i also tried that, it gives me the same silent errors. It is a binary copy of the cygwin esound so i theres no reason to give me different results, anyway i retried it. Still doesn't work, another idea? (sorry samir, you probably are getting this twice... i forgot the first t= ime to send to the list) Quoting Samir Kuthiala <sam...@gm...>: > use this >=20 > http://www.liquid-reality.de/main/projects/esound |
|
From: Samir K. <sam...@gm...> - 2004-08-24 18:27:51
|
use this http://www.liquid-reality.de/main/projects/esound On Tue, 24 Aug 2004 20:54:55 +0300, st...@t2... <st...@t2...> wrote: > Hi, people... > I wrote a few days ago, i was the one that made problems with fsck and lost his > Feodora partition :-(, i could never get it back to work. > Anyway, i keeped on trying with coLinux, downloaded the minimal feodora core 1 > image and installed it. Then started downloading new packages untill i had a > nice configuration. > Now i am writing from Mozilla in gnome... everything running in colinux except > of course the X server which is cygwin. > I have been working all the day long trying to make enlighted sound daemon to > work. I have installed the esound of cygwin (binaries, version 0.2.35). I run > the server like this: > $ esd -tcp -bind 192.168.1.1 -public -promiscuous > 192.168.1.1 is the TAP interface in the windows side, as you know networking > works all right because the X server works nice!. > i try from the same cygwin console to play a sound, the one that comes with > esound to test: > $ esdplay --server=192.168.1.1:16001 test.wav > and i hear the beautifull "Hasta la vista, baby" from terminator. > But anyway i try to do the same from coLinux: > $ esdplay --server=192.168.1.1:16001 test.wav > and i get nothing, not even an error message, esdplay executes with no problem. > I also tried executing xmms with the esound plugin and instead of just failing > silently it shows me a very helpfull error message which says in other words: > "something doesn't work, try to change this situation" > I also tried to run esdplay installing three versions of esound in colinux, > none > of them gave me a different result. The last version i tried was exactly the > same one which runs in cygwin, that not only is good because it matches the > server but also because it was the version that worked ok in cygwin. Of course > no positive results. > > I tried to see if esd is accepting the connections from colinux > $ telnet 192.168.1.1 16001 > Trying 192.168.1.1... > Connected to 192.168.1.1. > > As you see there is no problem with the connection. > I have no idea if the problem is from CoLinux, esound or the network > configuration itself, or if its only destinity :( > > Any ideas? > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: <st...@t2...> - 2004-08-24 17:55:15
|
Hi, people... I wrote a few days ago, i was the one that made problems with fsck and lo= st his Feodora partition :-(, i could never get it back to work. Anyway, i keeped on trying with coLinux, downloaded the minimal feodora c= ore 1 image and installed it. Then started downloading new packages untill i ha= d a nice configuration. Now i am writing from Mozilla in gnome... everything running in colinux e= xcept of course the X server which is cygwin. I have been working all the day long trying to make enlighted sound daemo= n to work. I have installed the esound of cygwin (binaries, version 0.2.35). I= run the server like this: $ esd -tcp -bind 192.168.1.1 -public -promiscuous=20 192.168.1.1 is the TAP interface in the windows side, as you know network= ing works all right because the X server works nice!. i try from the same cygwin console to play a sound, the one that comes wi= th esound to test: $ esdplay --server=3D192.168.1.1:16001 test.wav and i hear the beautifull "Hasta la vista, baby" from terminator. But anyway i try to do the same from coLinux: $ esdplay --server=3D192.168.1.1:16001 test.wav and i get nothing, not even an error message, esdplay executes with no pr= oblem. I also tried executing xmms with the esound plugin and instead of just fa= iling silently it shows me a very helpfull error message which says in other w= ords: "something doesn't work, try to change this situation" I also tried to run esdplay installing three versions of esound in colinu= x, none of them gave me a different result. The last version i tried was exactly = the same one which runs in cygwin, that not only is good because it matches t= he server but also because it was the version that worked ok in cygwin. Of c= ourse no positive results. I tried to see if esd is accepting the connections from colinux $ telnet 192.168.1.1 16001 Trying 192.168.1.1... Connected to 192.168.1.1. As you see there is no problem with the connection. I have no idea if the problem is from CoLinux, esound or the network configuration itself, or if its only destinity :( Any ideas? |
|
From: colinux <co...@ge...> - 2004-08-24 16:27:46
|
Here is my configuration:
Windows 2000 Pro Box
ipconfig /all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : windowsbox
Primary DNS Suffix . . . . . . . : here.there.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : here.there.com
there.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : there.com
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-08-74-AA-9C-9C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.5.42.141
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.5.42.1
DHCP Server . . . . . . . . . . . : 10.5.10.13
DNS Servers . . . . . . . . . . . : 10.5.10.10
10.10.10.10
Primary WINS Server . . . . . . . : 10.5.10.13
Secondary WINS Server . . . . . . : 10.10.9.13
Lease Obtained. . . . . . . . . . : Monday, August 23, 2004
12:48:34 PM
Lease Expires . . . . . . . . . . : Friday, August 27, 2004
12:48:34 PM
coLinux Instance on Windows 2000 Pro Box
colinux root # ifconfig
eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30
inet addr:10.5.42.127 Bcast:10.5.42.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11034 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1121883 (1.0 Mb) TX bytes:2707 (2.6 Kb)
Interrupt:2
colinux root # netstat -rv
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
10.5.42.0 * 255.255.255.0 U 0 0 0
eth0
loopback localhost.local 255.0.0.0 UG 0 0 0 lo
default 10.5.42.1 0.0.0.0 UG 0 0 0
eth0
Second Linux (Gentoo) Box
linuxbox root # ifconfig
eth0 Link encap:Ethernet HWaddr 00:B0:D0:92:FB:E9
inet addr:10.5.41.175 Bcast:10.5.41.255 Mask:255.255.255.0
inet6 addr: fe80::2b0:d0ff:fe92:fbe9/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21602929 errors:0 dropped:0 overruns:84 frame:0
TX packets:3426069 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4068341560 (3879.8 Mb) TX bytes:953483174 (909.3 Mb)
Interrupt:5 Base address:0xec80
linuxbox root # netstat -rv
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
10.5.41.0 * 255.255.255.0 U 0 0 0
eth0
loopback localhost 255.0.0.0 UG 0 0 0 lo
default 10.5.41.1 0.0.0.0 UG 0 0 0
eth0
All boxes/Instances can ping each other. However, when I attempt to
connect to coLinux from the hosting W2K box via ssh using Putty, I
cannot connect. The last log entry for /var/log/ssh/current shows the
ssh server starting:
Aug 24 09:29:10 [sshd] Server listening on 0.0.0.0 port 22.
whereas /var/log/everything/current shows nothing. I can connect to the
coLinux instance from a second Linux box as shown in /var/log/ssh/current:
Aug 24 09:50:17 [sshd] Accepted keyboard-interactive/pam for root from
10.5.41.175 port 34394 ssh2
Aug 24 09:50:17 [sshd(pam_unix)] session opened for user root by root(uid=0)
The only thing that's obviously different is that the second Linux box
uses a different gateway.
What would prevent the hosting W2K box from connecting to the coLinux
instance via ssh using Putty?
Many thanks,
Greg
|
|
From: Didier C. <Did...@un...> - 2004-08-24 13:14:56
|
Hello, I've installed Colinux on a XP SP1 machine. I've set it to use a virtual=20 ethernet interface (TAP-Win32 Adapter) to go on the network. That works fine when I'm logged with "Administrator" account on XP. If I=20 use a ordinary user account I can't netheir reach Colinux machine from XP= =20 nor XP machine from Colinux. Is there anybody who has met the problem and solved it ? Thanks, Regards, Didier CROUTZ Universit=E9 Nancy 2 - Centre de Ressources Informatiques UFR Maths-Info 13 rue Michel NEY 54037 NANCY CEDEX tel.: 03 83 39 64 38 fax: 03 83 39 64 39 Email: did...@un... ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Claude L. (QB/EMC) <cla...@er...> - 2004-08-23 17:38:35
|
Hi George, I have tested successfully option 1 from the list provided in my = previous message. So, I have been able to make a Solaris jumpstart from = a Windows 2000 based system using coLinux 0.6.2 (snapshot-20040710) ! I = have recompiled the 2.6.7 colinux kernel with the "NFS over TCP" = feature enabled. It works like a charm. The installation speed is very good. It's quite = the same speed than a native Linux system. Of course, the IP = fragmentation/reassembly problem I have observed using the bridged = network configuration under win2k is not solved but at least there is a = workaround. As far as I can see, there is no more = fragmentation/reassembly problem using the new NFS feature because I = think each NFS packet subject to fragmentation is replaced by a "RPC = continuation" packet. If a part of a packet is missing, I guess only = the missing element will re-transmit instead of the whole NFS stream in = a normal world. This is due to the TCP nature and design. So, the "NFS = over TCP" feature improves NFS reliability for connections under "bad" = networking conditions. Thanks, Claude. Claude LeFran=E7ois=20 cla...@er... -----Original Message----- From: Claude LeFrancois (QB/EMC)=20 Sent: Wednesday, August 18, 2004 5:46 PM To: 'gboutwel' Cc: col...@li... Subject: RE: [coLinux-users] NFS performance and colinux Hi George, I have installed snapshot-20040710. I have made the modification to the = xml file to attach to my Broadcom interface. I have booted my Fedora = Core 1 distribution with the 2.6.7 kernel without a problem. This = snapshot does not contain the nfsd support. So, I have recompiled the = colinux kernel with the appropriate settings. I have also learned that = the NFS daemon service has changed in the 2.6 kernels. So, I had to = make a little adaptation (mount -t nfsd nfsd /proc/fs/nfs). Finally, I = got my colinux working fine. :) However, my Solaris jumpstart does not work yet. I hit the same = problem. It seems the IP fragmentation problem is still there but I = have noticed an good improvement. It looks like the jumpstart client = (the Solaris box) sends a bunch of large NFS read packets at the same = time. Colinux is not able to reply to all of them in time and the = jumpstart client sends ICMP packets with TTL exceeded to colinux. At = this moment the jumpstart client gives "NFS server not responding". The = only way I have to improve this situation is to set the block size to = 1024 which avoids the fragmentation. The bad stuff is that only the = root fs benefits from this settings all the other NFS mounts from the = client are 4K blocks. The jumpstart client is point-to-point connected with my laptop using a = cross-over cable. To solve this situation, I see two options: 1. Hard code the NFS packet size to 1024 in the kernel 2. Try the new feature: NFS over TCP But, the fragmentation problem in colinux is not solved... I am a bit = confused now. I don't know what to do at this point. I am using the = bridged networking configuration. I guess it has nothing to do with the = TAP drivers, isn't it ? I am using win2k so there is no way to enable = bridging through the TAP interface because it appears this is only = supported in XP. I absolutely need to use bridging because the = jumpstart client initiates the jumpstart process by a RARP request. = Then, I cannot use NAT because these packets won't be redirected to my = colinux distribution unless a port forwarding mechanism exists. My system is a HP NC8000 laptop. It has 512 MB RAM and 1.5 GHz Pentium = M CPU. The network interface is a Broadcom NetXtreme Gigabit adapter. I = have already disabled TCP checksums and flow control on this interface. Any suggestions are really welcome ! Here is the output of my latest ping test: PING 192.168.0.101 (192.168.0.101) 4096(4124) bytes of data. 4104 bytes from 192.168.0.101: icmp_seq=3D1 ttl=3D255 time=3D2.24 ms 4104 bytes from 192.168.0.101: icmp_seq=3D2 ttl=3D255 time=3D2.10 ms 4104 bytes from 192.168.0.101: icmp_seq=3D3 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D7 ttl=3D255 time=3D2.09 ms 4104 bytes from 192.168.0.101: icmp_seq=3D8 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D10 ttl=3D255 time=3D2.10 ms 4104 bytes from 192.168.0.101: icmp_seq=3D12 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D13 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D15 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D17 ttl=3D255 time=3D2.06 ms 4104 bytes from 192.168.0.101: icmp_seq=3D20 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D23 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D24 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D26 ttl=3D255 time=3D2.09 ms 4104 bytes from 192.168.0.101: icmp_seq=3D27 ttl=3D255 time=3D2.11 ms 4104 bytes from 192.168.0.101: icmp_seq=3D30 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D32 ttl=3D255 time=3D1.97 ms 4104 bytes from 192.168.0.101: icmp_seq=3D33 ttl=3D255 time=3D2.09 ms 4104 bytes from 192.168.0.101: icmp_seq=3D34 ttl=3D255 time=3D2.07 ms --- 192.168.0.101 ping statistics --- 35 packets transmitted, 19 received, 45% packet loss, time 34196ms rtt min/avg/max/mdev =3D 1.974/2.158/2.242/0.087 ms, pipe 2 Thanks, Claude. Claude LeFran=E7ois=20 cla...@er... -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of gboutwel Sent: Wednesday, August 18, 2004 9:32 AM To: col...@li... Cc: Claude LeFrancois (QB/EMC) Subject: Re: [coLinux-users] NFS performance and colinux > > One question: are you using bridged networking ? > > I'm using the tap adapter, bridged by WinXP with my network card. I use both. On the PCAP bridging there is, also, 0% loss of packets using latest sources. > Not sure about that (I made no tests), but it seems the tap-win32 > adapter is somewhat faster and reliable than the bridged adapter. Also, > the code was revised lately to accomodate larger packets transfers. Yeah, most the tests that Dan has done shows TAP to be the faster interface. George ------------------------------------------ Praize? Enter In... http://www.praize.com/ ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Didier C. <Did...@un...> - 2004-08-23 15:41:09
|
Hello, I've installed Colinux on a XP SP1 machine. I've set it to use the networ= k=20 a virtual ethernet interface (TAP-Win32 Adapter) to go on the network. That works fine when I'm logged with "Administrator" account on XP. If I=20 use a ordinary user account I can't netheir reach Colinux machine from XP= =20 nor XP machine from Colinux. Is there anybody who has met the problem and solved it ? Thanks, Regards, Didier CROUTZ Universit=E9 Nancy 2 - Centre de Ressources Informatiques UFR Maths-Info 13 rue Michel NEY 54037 NANCY CEDEX tel.: 03 83 39 64 38 fax: 03 83 39 64 39 Email: did...@un... |
|
From: Kirk B. <ki...@vi...> - 2004-08-23 15:19:57
|
Hi, have been through the many scraps of info on getting networking to work, but can't find anything that I can cannibalise for my setup. Am trying coLinux with the Woody image. My setup is: - Compaq Presario R3000 laptop running Win XP Home - USB 802.11b wireless card - Linksys WAG54G wireless router / ADSL gateway - Static IPs based on 192.168.1.x (Linksys gateway is 192.168.1.1, the Win XP IP is .103) Woody boots and runs fine from the colinux shell -- but I've tried many combinations of setting up ICS / the TAP driver / Bridges / IP settings but to no avail. If anyone has a similar hardware setup to me and would be kind enough to post what steps they took to get networking up, I would be most grateful! Many thanks Kirk. |
|
From: BrokenClock <bro...@fr...> - 2004-08-23 08:31:40
|
Hello everybody, I'm a new user to coLinux, and I think it is very great! Go on, guys! Now, my question : is there a way to make an image from an existing system, use it on a windows station with coLinux, and put back the image on the original system? My goal is to make some change on a RedHat server, test them before put them on the real system. It should very easier for me to make things this way instead of make the changes on the living system.* I tried to make an image using SystemRescueCS (http://www.sysresccd.org/), and with the dd command to a file on a ftp server, but I missed something to make a bootable image for coLinux. Best regards, Stephane Mourey |
|
From: gboutwel <gbo...@pr...> - 2004-08-22 00:17:10
|
> However, I suspect the interface selection code has some problems. By = > example, on my system, I have multiple "Local Area Connection" entries. = > Something like this: > > Local Area Connection > Local Area Connection 2 > Local Area Connection 3 > > I needed my system to bridge on "Local Area Connection". I have = > modified my xml file accordingly but coLinux never got attached to the = > proper interface. If I recall well, it has attached to the "Local Area = > Connection 3" instead. > > So, to work around this problem, I have renamed the "Local Area = > Connection" to "Local Area Connection Broadcom" and after the proper = > modification has been done to the xml file, coLinux has attached to the = > correct interface. The code itterates through the Network Interfaces in the order they occur in the Windows Registry. Matching the first one that it finds that partially matches. The only improvement to this code would be to: 1) Read all the interfaces of the registry, order them, then do the partial match. 2) Store all partial matches, instead of going with the first one, then iterate all partial matches for an exact match, if not exact match can be found, then go with the first one. George ----------------------------------------- Love to Chat? Start talking in the Christian Chat Rooms http://www.praize.com/chat/ |
|
From: Henry N. <Hen...@ar...> - 2004-08-21 22:55:16
|
Joe Wells (reverse mailbox letters to reply) wrote: > Peng <rin...@gm...> writes: > > >>The floating point error is probably caused by the CFLAGS. I solved >>it by recompiling the system (at least, xfree) with "-march=i686". > > > By the way, this is equivalent to -march=pentiumpro. Inside GCC, > using -march=pentiumpro instead of -march=pentium4 uses the > PROCESSOR_PENTIUMPRO flag instead of PROCESSOR_PENTIUM4, and turns off > PTA_SSE, PTA_SSE2, PTA_MMX, PTA_PREFETCH_SSE. (Both -march=pentium2 > and -march=pentium3 also use PROCESSOR_PENTIUMPRO.) > > I am making a wild guess that it will be enough to turn off PTA_MMX. > I want to try some recompiling with "-march=pentium4 -mno-mmx" to see > if that is enough to fix things. > I'm view into compile scripts. Kernel was compiled for i586. Show into conf/linux-config: CONFIG_M586=y # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set ... But the colinux libraries and daemons will compile for 686. See into build-common.sh: TARGET=i686-pc-mingw32 This compile the cross compiler for i686 and all targets was compile for i686, also if the build do no set any CFLAGS. Is this your problem? If yes, should we compile all for i586 only? I'm using Pentuim4 and do not get any errors. Henry |
|
From: <sl...@bl...> - 2004-08-21 20:34:36
|
Peng <rin...@gm...> writes: > The floating point error is probably caused by the CFLAGS. I solved > it by recompiling the system (at least, xfree) with "-march=i686". By the way, this is equivalent to -march=pentiumpro. Inside GCC, using -march=pentiumpro instead of -march=pentium4 uses the PROCESSOR_PENTIUMPRO flag instead of PROCESSOR_PENTIUM4, and turns off PTA_SSE, PTA_SSE2, PTA_MMX, PTA_PREFETCH_SSE. (Both -march=pentium2 and -march=pentium3 also use PROCESSOR_PENTIUMPRO.) I am making a wild guess that it will be enough to turn off PTA_MMX. I want to try some recompiling with "-march=pentium4 -mno-mmx" to see if that is enough to fix things. -- Joe > Good luck, > > Peng > > On Sat, 21 Aug 2004 13:49:20 +0200, Ronald Pijnacker <pij...@ds...> wrote: > > On Thu, Aug 19, 2004 at 04:10:37PM -0400, Peng wrote: > > > Which distribution are you using? > > > > I am using the same Gentoo linux that I also use natively. > > I do compile with optimization flags for the Pentium4 that I have, but > > that's never given any problems before. > > > > Regards, > > > > Ronald. > > > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Peng <rin...@gm...> - 2004-08-21 19:53:44
|
The floating point error is probably caused by the CFLAGS. I solved it by recompiling the system (at least, xfree) with "-march=i686". Good luck, Peng On Sat, 21 Aug 2004 13:49:20 +0200, Ronald Pijnacker <pij...@ds...> wrote: > On Thu, Aug 19, 2004 at 04:10:37PM -0400, Peng wrote: > > Which distribution are you using? > > I am using the same Gentoo linux that I also use natively. > I do compile with optimization flags for the Pentium4 that I have, but > that's never given any problems before. > > Regards, > > Ronald. > |
|
From: Henry N. <Hen...@ar...> - 2004-08-21 12:42:13
|
Ronald Pijnacker wrote: > Hi all, > > This week I installed snapshot 20040710. I ran into a couple of problems: > > - When logging in (vnc + XDMCP) WindowMaker now gets a floating point > exception. This doesn't happen with the previous snapshots or in > native linux. > > - /dev/cobd1 is mapped to the first partition, which holds a ext3 fs. > Until now I could mount it with no problems. However, in this snapshot > I cannot anymore: "no such device". > > Just my two cents... > > Oh, by the way, I saw some announcements of "other" snapshots in the mailing > list. What is the status of these snapshots compared with the ones on the > official site (colinux.org/snapshots) ? The latest snapshot seems quite old. > > Regards, > > Ronald. The official snapshot is completly. Some newer version works, but they have no installer. You must install the last snapshoot, than download the executables, kernel, Modules, extract this into your favorite directory and call a simply colinux-deamon.exe --remove-driver colinux-deamon.exe --install-driver After this you can test some of the non official versions. http://home.arcor.de/henryn/colinux/colinux-0.6.2-20040817.zip http://home.arcor.de/henryn/colinux/modules-0.6.2-20040817.tar.gz Please try this, think works better. If you interrest the difference of this version, you should install monotone and get the log of the source. Henry |
|
From: Ronald P. <pij...@ds...> - 2004-08-21 11:49:27
|
On Thu, Aug 19, 2004 at 04:10:37PM -0400, Peng wrote: > Which distribution are you using? I am using the same Gentoo linux that I also use natively. I do compile with optimization flags for the Pentium4 that I have, but that's never given any problems before. Regards, Ronald. |
|
From: Claude L. (QB/EMC) <cla...@er...> - 2004-08-20 13:36:48
|
Hi George, I have tested successfully option 1 from the list provided in my = previous message. So, I have been able to make a Solaris jumpstart from = a Windows 2000 based system using coLinux 0.6.2 (snapshot-20040710) ! I = have recompiled the 2.6.7 colinux kernel with the "NFS over TCP" = feature enabled. It works like a charm. The installation speed is very good. It's quite = the same speed than a native Linux system. Of course, the IP = fragmentation/reassembly problem I have observed using the bridged = network configuration under win2k is not solved but at least there is a = workaround. As far as I can see, there is no more = fragmentation/reassembly problem using the new NFS feature because I = think each NFS packet subject to fragmentation is replaced by a "RPC = continuation" packet. If a part of a packet is missing, I guess only = the missing element will re-transmit instead of the whole NFS stream in = a normal world. This is due to the TCP nature and design. So, the "NFS = over TCP" feature improves NFS reliability for connections under "bad" = networking conditions. Thanks, Claude. Claude LeFran=E7ois=20 cla...@er... -----Original Message----- From: Claude LeFrancois (QB/EMC)=20 Sent: Wednesday, August 18, 2004 5:46 PM To: 'gboutwel' Cc: col...@li... Subject: RE: [coLinux-users] NFS performance and colinux Hi George, I have installed snapshot-20040710. I have made the modification to the = xml file to attach to my Broadcom interface. I have booted my Fedora = Core 1 distribution with the 2.6.7 kernel without a problem. This = snapshot does not contain the nfsd support. So, I have recompiled the = colinux kernel with the appropriate settings. I have also learned that = the NFS daemon service has changed in the 2.6 kernels. So, I had to = make a little adaptation (mount -t nfsd nfsd /proc/fs/nfs). Finally, I = got my colinux working fine. :) However, my Solaris jumpstart does not work yet. I hit the same = problem. It seems the IP fragmentation problem is still there but I = have noticed an good improvement. It looks like the jumpstart client = (the Solaris box) sends a bunch of large NFS read packets at the same = time. Colinux is not able to reply to all of them in time and the = jumpstart client sends ICMP packets with TTL exceeded to colinux. At = this moment the jumpstart client gives "NFS server not responding". The = only way I have to improve this situation is to set the block size to = 1024 which avoids the fragmentation. The bad stuff is that only the = root fs benefits from this settings all the other NFS mounts from the = client are 4K blocks. The jumpstart client is point-to-point connected with my laptop using a = cross-over cable. To solve this situation, I see two options: 1. Hard code the NFS packet size to 1024 in the kernel 2. Try the new feature: NFS over TCP But, the fragmentation problem in colinux is not solved... I am a bit = confused now. I don't know what to do at this point. I am using the = bridged networking configuration. I guess it has nothing to do with the = TAP drivers, isn't it ? I am using win2k so there is no way to enable = bridging through the TAP interface because it appears this is only = supported in XP. I absolutely need to use bridging because the = jumpstart client initiates the jumpstart process by a RARP request. = Then, I cannot use NAT because these packets won't be redirected to my = colinux distribution unless a port forwarding mechanism exists. My system is a HP NC8000 laptop. It has 512 MB RAM and 1.5 GHz Pentium = M CPU. The network interface is a Broadcom NetXtreme Gigabit adapter. I = have already disabled TCP checksums and flow control on this interface. Any suggestions are really welcome ! Here is the output of my latest ping test: PING 192.168.0.101 (192.168.0.101) 4096(4124) bytes of data. 4104 bytes from 192.168.0.101: icmp_seq=3D1 ttl=3D255 time=3D2.24 ms 4104 bytes from 192.168.0.101: icmp_seq=3D2 ttl=3D255 time=3D2.10 ms 4104 bytes from 192.168.0.101: icmp_seq=3D3 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D7 ttl=3D255 time=3D2.09 ms 4104 bytes from 192.168.0.101: icmp_seq=3D8 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D10 ttl=3D255 time=3D2.10 ms 4104 bytes from 192.168.0.101: icmp_seq=3D12 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D13 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D15 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D17 ttl=3D255 time=3D2.06 ms 4104 bytes from 192.168.0.101: icmp_seq=3D20 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D23 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D24 ttl=3D255 time=3D2.23 ms 4104 bytes from 192.168.0.101: icmp_seq=3D26 ttl=3D255 time=3D2.09 ms 4104 bytes from 192.168.0.101: icmp_seq=3D27 ttl=3D255 time=3D2.11 ms 4104 bytes from 192.168.0.101: icmp_seq=3D30 ttl=3D255 time=3D2.22 ms 4104 bytes from 192.168.0.101: icmp_seq=3D32 ttl=3D255 time=3D1.97 ms 4104 bytes from 192.168.0.101: icmp_seq=3D33 ttl=3D255 time=3D2.09 ms 4104 bytes from 192.168.0.101: icmp_seq=3D34 ttl=3D255 time=3D2.07 ms --- 192.168.0.101 ping statistics --- 35 packets transmitted, 19 received, 45% packet loss, time 34196ms rtt min/avg/max/mdev =3D 1.974/2.158/2.242/0.087 ms, pipe 2 Thanks, Claude. Claude LeFran=E7ois=20 cla...@er... -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of gboutwel Sent: Wednesday, August 18, 2004 9:32 AM To: col...@li... Cc: Claude LeFrancois (QB/EMC) Subject: Re: [coLinux-users] NFS performance and colinux > > One question: are you using bridged networking ? > > I'm using the tap adapter, bridged by WinXP with my network card. I use both. On the PCAP bridging there is, also, 0% loss of packets using latest sources. > Not sure about that (I made no tests), but it seems the tap-win32 > adapter is somewhat faster and reliable than the bridged adapter. Also, > the code was revised lately to accomodate larger packets transfers. Yeah, most the tests that Dan has done shows TAP to be the faster interface. George ------------------------------------------ Praize? Enter In... http://www.praize.com/ ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
119 messages has been excluded from this view by a project administrator.
