Menu
▾
▴
colinux-devel — Cooperative Linux development mailing list
You can subscribe to this list here.
| 2004 |
Jan
(64) |
Feb
(530) |
Mar
(266) |
Apr
(580) |
May
(360) |
Jun
(161) |
Jul
(185) |
Aug
(164) |
Sep
(123) |
Oct
(160) |
Nov
(59) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(156) |
Feb
(95) |
Mar
(124) |
Apr
(81) |
May
(79) |
Jun
(179) |
Jul
(35) |
Aug
(64) |
Sep
(56) |
Oct
(57) |
Nov
(18) |
Dec
(41) |
| 2006 |
Jan
(65) |
Feb
(37) |
Mar
(59) |
Apr
(73) |
May
(65) |
Jun
(27) |
Jul
(54) |
Aug
(76) |
Sep
(103) |
Oct
(23) |
Nov
(45) |
Dec
(29) |
| 2007 |
Jan
(41) |
Feb
(47) |
Mar
(61) |
Apr
(24) |
May
(14) |
Jun
(6) |
Jul
(23) |
Aug
(30) |
Sep
(16) |
Oct
(9) |
Nov
(53) |
Dec
(36) |
| 2008 |
Jan
(19) |
Feb
(49) |
Mar
(74) |
Apr
(21) |
May
(24) |
Jun
(5) |
Jul
(9) |
Aug
(53) |
Sep
(26) |
Oct
(23) |
Nov
(32) |
Dec
(19) |
| 2009 |
Jan
(47) |
Feb
(49) |
Mar
(39) |
Apr
(61) |
May
(28) |
Jun
(19) |
Jul
(12) |
Aug
(10) |
Sep
(31) |
Oct
(16) |
Nov
(60) |
Dec
(26) |
| 2010 |
Jan
(17) |
Feb
(9) |
Mar
(32) |
Apr
(11) |
May
(24) |
Jun
(33) |
Jul
(5) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(17) |
Dec
(7) |
| 2011 |
Jan
(12) |
Feb
(16) |
Mar
(2) |
Apr
(12) |
May
(5) |
Jun
(10) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(11) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2013 |
Jan
|
Feb
(7) |
Mar
(4) |
Apr
(10) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(3) |
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: gboutwel <gbo...@pr...> - 2004-04-05 20:32:54
|
Updated per comments to include the w32api.diff file in the patch itself. In addition I did some clean-up this time that I didn't do last time. Removing any commented out old stuff that might have been left in there, etc. See attached file. -------------------------------- Looking for that favorite verse? Search for it in Praize Bible http://www.praize.com/bible/ |
|
From: Alejandro R. S. <as...@MI...> - 2004-04-05 20:28:24
|
You shouldn't need to turn off the Rx checksum offloading, just Tx, but it probably won't hurt to have it off. I built a new 2.4.25 kernel using the 0.6.0 config file + socket filtering. If you want to try it and see if that fixes dhcp, it's available at: http://web.mit.edu/asedeno/www/coLinux/my_0.6.0_kernel Be sure to keep your old kernel around just in case. -Alejandro On Mon, 2004-04-05 at 15:11, Robert Pang wrote: > Alejandro > > Yes. That's it. My NIC have "Rx Checksum Offload" and "Tx Checksum Offload" > options. After disabling them, I am able to TCP to and from my W2k host with > coLinux. I still get dup ping replies though. Not sure if it matters or not. > > As for the kernel, I am just using the kernel that comes with 0.6.0 install. > Don't know if it is compiled with packet filtering or not. It looks like it > takes quite a bit of effort to setup the env to build coLinux and I doubt if > I have the bandwidth to try building the kernel myself. > > Thanks for your help in any case. > > Rob > > ----- Original Message ----- > From: "Alejandro R. Sedeno" <as...@MI...> > To: "Robert Pang" <rob...@ho...> > Cc: <col...@li...> > Sent: Monday, April 05, 2004 11:36 AM > Subject: Re: [coLinux-devel] Two networking issues > > > > With the caveat that I've not used your particular NIC, nor have I used > > Fedora: > > > > DHCP - Does your kernel have Socket Filtering? I'm not sure if this is > > compiled into the coLinux kernel yet, but it caused some issues with > > dhcp for me. > > > > As far as host<->coLinux communications, I recently had issues with an > > integrated network card that offloaded TCP and IP checksums to the NIC. > > Check the NIC's configuration from the device manager and look under > > advanced to see if there are any options resembling "Offload Transmit IP > > Checksum". Disable checksum offloading for transmit on both TCP and IP > > if the options are there. > > > > Good luck! > > > > -Alejandro > > > > > > On Mon, 2004-04-05 at 14:05, Robert Pang wrote: > > > Hi folks, > > > > > > coLinux is great. I am able to set up and run Fedora Core 1 with the > 0.6.0 > > > build on Windows 2000. However, I run into 2 issues. > > > > > > First, I cannot use DHCP with FC1. I get the same error as described in > > > http://www.colinux.org/wiki/index.php/coLinuxIAQ#A1. Since there is no > pump > > > binary package for FC1, I haven't tried pump to see if will resolve the > > > issue. FC1 uses dhclient for DHCP and I am not how to set it up to use > pump. > > > > > > Second, using static IP, I cannot make a TCP connection from the W2k > host to > > > coLinux or vice versa. ping works but I got duplicate replies if I ping > the > > > W2k host (rpang-pc2) from coLinux: > > > > > > [rpang@colinux rpang]$ ping rpang-pc2 > > > PING rpang-pc2 (130.35.168.159) 56(84) bytes of data. > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=4.96 > ms > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=6.25 > ms > > > (DUP!) > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.11 > ms > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.91 > ms > > > (DUP!) > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.13 > ms > > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.72 > ms > > > (DUP!) > > > .. > > > > > > ping from W2k to coLinux seems to be okay though: > > > > > > C:\Documents and Settings\rpang>ping lvbcheng-pc > > > > > > Pinging lvbcheng-pc.us.oracle.com [130.35.168.148] with 32 bytes of > data: > > > > > > Reply from 130.35.168.148: bytes=32 time=30ms TTL=64 > > > Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 > > > Reply from 130.35.168.148: bytes=32 time<10ms TTL=64 > > > Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 > > > > > > Ping statistics for 130.35.168.148: > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > > Approximate round trip times in milli-seconds: > > > Minimum = 0ms, Maximum = 30ms, Average = 12ms > > > > > > Because of this problem, I cannot make X connection from coLinux to my > > > cygwin/XFree86 running on my W2k host. Neither can I ssh from my W2k > host > > > back to coLinux. TCP connection to and from another machine on the > network > > > with coLinux is fine though. > > > > > > Here is my coLinux network setup: > > > > > > [rpang@colinux rpang]# ifconfig > > > eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30 > > > inet addr:130.35.168.148 Bcast:130.35.171.255 > Mask:255.255.252.0 > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:1523574 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:4726 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:104822082 (99.9 Mb) TX bytes:3234903 (3.0 Mb) > > > Interrupt:2 > > > > > > 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) > > > > > > My W2k network setup: > > > > > > Windows 2000 IP Configuration > > > > > > Host Name . . . . . . . . . . . . : rpang-pc2 > > > Node Type . . . . . . . . . . . . : Hybrid > > > IP Routing Enabled. . . . . . . . : No > > > WINS Proxy Enabled. . . . . . . . : No > > > > > > Ethernet adapter Local Area Connection: > > > > > > Description . . . . . . . . . . . : 3Com 3C918 Integrated Fast > > > Ethernet > > > Controller (3C905B-TX Compatible) > > > Physical Address. . . . . . . . . : 00-C0-4F-5E-C2-DA > > > DHCP Enabled. . . . . . . . . . . : No > > > IP Address. . . . . . . . . . . . : 130.35.168.159 > > > Subnet Mask . . . . . . . . . . . : 255.255.252.0 > > > Default Gateway . . . . . . . . . : 130.35.168.1 > > > DNS Servers . . . . . . . . . . . : 130.35.249.41 > > > 138.2.202.15 > > > Primary WINS Server . . . . . . . : 138.2.202.14 > > > Secondary WINS Server . . . . . . : 130.35.62.34 > > > > > > And my default.colinux.xml: > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > <colinux> > > > <block_device index="0" path="\DosDevices\e:\fedora_root" > > > enabled="true"> > > > </block_device> > > > <block_device index="1" path="\DosDevices\e:\colinux_swap" > > > enabled="true"> > > > </block_device> > > > <bootparams>ro root=/dev/cobd0</bootparams> > > > <image path="vmlinux"></image> > > > <memory size="64"></memory> > > > <network index="0" type="bridged" name="3Com 3C918 Integrated Fast > > > Ethernet Controller (3C905B-TX Compatible)"></network> > > > </colinux> > > > > > > BTW, I am using the bridged network. I failed to setup NAT with W2k ICS. > > > Enabling W2k ICS always results with an error. It turns out that ICS > uses > > > DHCP implicitly and there is another DHCP server running in my network > so > > > ICS cannot be used (see the first common problem under > > > http://is-it-true.org/nt/nt2000/utips/utips11.shtml). > > > > > > Any take on these two issues? > > > > > > Thanks. > > > > > > Rob > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: IBM Linux Tutorials > > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > > GenToo technologies. Learn everything from fundamentals to system > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > |
|
From: Eyal L. <gnu...@ya...> - 2004-04-05 20:11:47
|
Hey, I stumbled upon this when checking my mail :) I think the reason may be that Windows is using the disks better and making access faster. Perhaps DMA acceleration or some other feature is turned off on the Linux host side, making disk access slower on the Linux side. Then again, that could only explain the first run of the benchmark and not the cached runs. Maybe some bug in Linux's caching/buffering? --- Dan Aloni <da...@co...> wrote: > Hello, > > Today I ran some dbench2 benchmarks in order to test > coLinux's > (http://www.colinux.org) virtual disk I/O > performance. > > I'm cross-posting this message to the LKML, as I > know that on that > list there are some benchmarking experts or other > people who may > find this interesting. > > This is the output from a coLinux 2.4.25 guest VM > configured with > 128MB RAM running on a Linux 2.6.3 (BK) host that > has a total of > 256MB RAM. The host machine has a Mobile Intel > Celeron CPU (2.20GHz). > All filesystems used are ext3. > > colinux:/home/dax# dbench 5 -s -S > 5 clients started > 0 62477 10.01 MB/sec > Throughput 10.0026 MB/sec (sync open) (sync > dirs) 5 procs > > colinux:/home/dax# dbench 5 -s -S > 5 clients started > 0 62477 10.43 MB/sec > Throughput 10.4262 MB/sec (sync open) (sync > dirs) 5 procs > > colinux:/home/dax# dbench 5 -s -S > 5 clients started > 0 62477 10.90 MB/sec > Throughput 10.8926 MB/sec (sync open) (sync > dirs) 5 procs > > > I then ran the same thing on the host itself, > *without* the > coLinux VM running in the background: > > hostile17:~/colinux# dbench 5 -s -S > 5 clients started > 0 62477 5.08 MB/sec > Throughput 5.07573 MB/sec (sync open) (sync > dirs) 5 procs > > hostile17:~/colinux# dbench 5 -s -S > 5 clients started > 0 62477 5.13 MB/sec > Throughput 5.12705 MB/sec (sync open) (sync > dirs) 5 procs > > > The VM shows better results than the host. What > gives? Perhaps > it is because of the combination of the host and > guest's buffer > cache? I'd like to know about more percise > benchmarking methods > for VMs. > > -- > Dan Aloni > Cooperative Linux, lead developer > da...@co... > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux > Tutorials > Free Linux tutorial presented by Daniel Robbins, > President and CEO of > GenToo technologies. Learn everything from > fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ |
|
From: Robert P. <rob...@ho...> - 2004-04-05 19:11:21
|
Alejandro Yes. That's it. My NIC have "Rx Checksum Offload" and "Tx Checksum Offload" options. After disabling them, I am able to TCP to and from my W2k host with coLinux. I still get dup ping replies though. Not sure if it matters or not. As for the kernel, I am just using the kernel that comes with 0.6.0 install. Don't know if it is compiled with packet filtering or not. It looks like it takes quite a bit of effort to setup the env to build coLinux and I doubt if I have the bandwidth to try building the kernel myself. Thanks for your help in any case. Rob ----- Original Message ----- From: "Alejandro R. Sedeno" <as...@MI...> To: "Robert Pang" <rob...@ho...> Cc: <col...@li...> Sent: Monday, April 05, 2004 11:36 AM Subject: Re: [coLinux-devel] Two networking issues > With the caveat that I've not used your particular NIC, nor have I used > Fedora: > > DHCP - Does your kernel have Socket Filtering? I'm not sure if this is > compiled into the coLinux kernel yet, but it caused some issues with > dhcp for me. > > As far as host<->coLinux communications, I recently had issues with an > integrated network card that offloaded TCP and IP checksums to the NIC. > Check the NIC's configuration from the device manager and look under > advanced to see if there are any options resembling "Offload Transmit IP > Checksum". Disable checksum offloading for transmit on both TCP and IP > if the options are there. > > Good luck! > > -Alejandro > > > On Mon, 2004-04-05 at 14:05, Robert Pang wrote: > > Hi folks, > > > > coLinux is great. I am able to set up and run Fedora Core 1 with the 0.6.0 > > build on Windows 2000. However, I run into 2 issues. > > > > First, I cannot use DHCP with FC1. I get the same error as described in > > http://www.colinux.org/wiki/index.php/coLinuxIAQ#A1. Since there is no pump > > binary package for FC1, I haven't tried pump to see if will resolve the > > issue. FC1 uses dhclient for DHCP and I am not how to set it up to use pump. > > > > Second, using static IP, I cannot make a TCP connection from the W2k host to > > coLinux or vice versa. ping works but I got duplicate replies if I ping the > > W2k host (rpang-pc2) from coLinux: > > > > [rpang@colinux rpang]$ ping rpang-pc2 > > PING rpang-pc2 (130.35.168.159) 56(84) bytes of data. > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=4.96 ms > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=6.25 ms > > (DUP!) > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.11 ms > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.91 ms > > (DUP!) > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.13 ms > > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.72 ms > > (DUP!) > > .. > > > > ping from W2k to coLinux seems to be okay though: > > > > C:\Documents and Settings\rpang>ping lvbcheng-pc > > > > Pinging lvbcheng-pc.us.oracle.com [130.35.168.148] with 32 bytes of data: > > > > Reply from 130.35.168.148: bytes=32 time=30ms TTL=64 > > Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 > > Reply from 130.35.168.148: bytes=32 time<10ms TTL=64 > > Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 > > > > Ping statistics for 130.35.168.148: > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > Approximate round trip times in milli-seconds: > > Minimum = 0ms, Maximum = 30ms, Average = 12ms > > > > Because of this problem, I cannot make X connection from coLinux to my > > cygwin/XFree86 running on my W2k host. Neither can I ssh from my W2k host > > back to coLinux. TCP connection to and from another machine on the network > > with coLinux is fine though. > > > > Here is my coLinux network setup: > > > > [rpang@colinux rpang]# ifconfig > > eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30 > > inet addr:130.35.168.148 Bcast:130.35.171.255 Mask:255.255.252.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:1523574 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:4726 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:104822082 (99.9 Mb) TX bytes:3234903 (3.0 Mb) > > Interrupt:2 > > > > 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) > > > > My W2k network setup: > > > > Windows 2000 IP Configuration > > > > Host Name . . . . . . . . . . . . : rpang-pc2 > > Node Type . . . . . . . . . . . . : Hybrid > > IP Routing Enabled. . . . . . . . : No > > WINS Proxy Enabled. . . . . . . . : No > > > > Ethernet adapter Local Area Connection: > > > > Description . . . . . . . . . . . : 3Com 3C918 Integrated Fast > > Ethernet > > Controller (3C905B-TX Compatible) > > Physical Address. . . . . . . . . : 00-C0-4F-5E-C2-DA > > DHCP Enabled. . . . . . . . . . . : No > > IP Address. . . . . . . . . . . . : 130.35.168.159 > > Subnet Mask . . . . . . . . . . . : 255.255.252.0 > > Default Gateway . . . . . . . . . : 130.35.168.1 > > DNS Servers . . . . . . . . . . . : 130.35.249.41 > > 138.2.202.15 > > Primary WINS Server . . . . . . . : 138.2.202.14 > > Secondary WINS Server . . . . . . : 130.35.62.34 > > > > And my default.colinux.xml: > > > > <?xml version="1.0" encoding="UTF-8"?> > > <colinux> > > <block_device index="0" path="\DosDevices\e:\fedora_root" > > enabled="true"> > > </block_device> > > <block_device index="1" path="\DosDevices\e:\colinux_swap" > > enabled="true"> > > </block_device> > > <bootparams>ro root=/dev/cobd0</bootparams> > > <image path="vmlinux"></image> > > <memory size="64"></memory> > > <network index="0" type="bridged" name="3Com 3C918 Integrated Fast > > Ethernet Controller (3C905B-TX Compatible)"></network> > > </colinux> > > > > BTW, I am using the bridged network. I failed to setup NAT with W2k ICS. > > Enabling W2k ICS always results with an error. It turns out that ICS uses > > DHCP implicitly and there is another DHCP server running in my network so > > ICS cannot be used (see the first common problem under > > http://is-it-true.org/nt/nt2000/utips/utips11.shtml). > > > > Any take on these two issues? > > > > Thanks. > > > > Rob > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > |
|
From: Ballard J. <sac...@ho...> - 2004-04-05 18:48:35
|
You can add the patch inside of the script. For example: $ cat <<EOT This is text that gets sent to the "cat" program until it reaches a line that starts with EOT $ So you can replace "cat" with "patch" and the text with the body of the patch. Jonathan > ----- Original Message ----- > From: "gboutwel" <gbo...@pr...> > To: <col...@li...> > Sent: Monday, April 05, 2004 9:30 AM > Subject: [coLinux-devel] [PATCH] cobuild.sh-20040405.patch > > > > Hello, > > > > > > > > After some messing around, I was able to build using this modified > > cobuild.sh the latest colinux kernel and deamons. The patch > > refers to w32api.diff, this is the w32api.diff that was recently > > (March 14th 2004) posted to this mailing list. currently it's > > not availabel for d/l anywhere that I could tell, so the cobuild.sh > > script will have to be modified to point/d/l that file someplace > > or users will have to manually copy it there. > > > > > > > > Anyways, without futher ado, here's the patch (not this is > > my first public patch, so let me know if I've done something > > silly, stupid, or wrong): > > > > > > > > > > > > > > > > ------------------------------------------ > > > > Praize? Enter In... > > > > http://www.praize.com/ > > > |
|
From: Alejandro R. S. <as...@MI...> - 2004-04-05 18:36:51
|
With the caveat that I've not used your particular NIC, nor have I used Fedora: DHCP - Does your kernel have Socket Filtering? I'm not sure if this is compiled into the coLinux kernel yet, but it caused some issues with dhcp for me. As far as host<->coLinux communications, I recently had issues with an integrated network card that offloaded TCP and IP checksums to the NIC. Check the NIC's configuration from the device manager and look under advanced to see if there are any options resembling "Offload Transmit IP Checksum". Disable checksum offloading for transmit on both TCP and IP if the options are there. Good luck! -Alejandro On Mon, 2004-04-05 at 14:05, Robert Pang wrote: > Hi folks, > > coLinux is great. I am able to set up and run Fedora Core 1 with the 0.6.0 > build on Windows 2000. However, I run into 2 issues. > > First, I cannot use DHCP with FC1. I get the same error as described in > http://www.colinux.org/wiki/index.php/coLinuxIAQ#A1. Since there is no pump > binary package for FC1, I haven't tried pump to see if will resolve the > issue. FC1 uses dhclient for DHCP and I am not how to set it up to use pump. > > Second, using static IP, I cannot make a TCP connection from the W2k host to > coLinux or vice versa. ping works but I got duplicate replies if I ping the > W2k host (rpang-pc2) from coLinux: > > [rpang@colinux rpang]$ ping rpang-pc2 > PING rpang-pc2 (130.35.168.159) 56(84) bytes of data. > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=4.96 ms > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=6.25 ms > (DUP!) > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.11 ms > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.91 ms > (DUP!) > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.13 ms > 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.72 ms > (DUP!) > .. > > ping from W2k to coLinux seems to be okay though: > > C:\Documents and Settings\rpang>ping lvbcheng-pc > > Pinging lvbcheng-pc.us.oracle.com [130.35.168.148] with 32 bytes of data: > > Reply from 130.35.168.148: bytes=32 time=30ms TTL=64 > Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 > Reply from 130.35.168.148: bytes=32 time<10ms TTL=64 > Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 > > Ping statistics for 130.35.168.148: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 0ms, Maximum = 30ms, Average = 12ms > > Because of this problem, I cannot make X connection from coLinux to my > cygwin/XFree86 running on my W2k host. Neither can I ssh from my W2k host > back to coLinux. TCP connection to and from another machine on the network > with coLinux is fine though. > > Here is my coLinux network setup: > > [rpang@colinux rpang]# ifconfig > eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30 > inet addr:130.35.168.148 Bcast:130.35.171.255 Mask:255.255.252.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1523574 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4726 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:104822082 (99.9 Mb) TX bytes:3234903 (3.0 Mb) > Interrupt:2 > > 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) > > My W2k network setup: > > Windows 2000 IP Configuration > > Host Name . . . . . . . . . . . . : rpang-pc2 > Node Type . . . . . . . . . . . . : Hybrid > IP Routing Enabled. . . . . . . . : No > WINS Proxy Enabled. . . . . . . . : No > > Ethernet adapter Local Area Connection: > > Description . . . . . . . . . . . : 3Com 3C918 Integrated Fast > Ethernet > Controller (3C905B-TX Compatible) > Physical Address. . . . . . . . . : 00-C0-4F-5E-C2-DA > DHCP Enabled. . . . . . . . . . . : No > IP Address. . . . . . . . . . . . : 130.35.168.159 > Subnet Mask . . . . . . . . . . . : 255.255.252.0 > Default Gateway . . . . . . . . . : 130.35.168.1 > DNS Servers . . . . . . . . . . . : 130.35.249.41 > 138.2.202.15 > Primary WINS Server . . . . . . . : 138.2.202.14 > Secondary WINS Server . . . . . . : 130.35.62.34 > > And my default.colinux.xml: > > <?xml version="1.0" encoding="UTF-8"?> > <colinux> > <block_device index="0" path="\DosDevices\e:\fedora_root" > enabled="true"> > </block_device> > <block_device index="1" path="\DosDevices\e:\colinux_swap" > enabled="true"> > </block_device> > <bootparams>ro root=/dev/cobd0</bootparams> > <image path="vmlinux"></image> > <memory size="64"></memory> > <network index="0" type="bridged" name="3Com 3C918 Integrated Fast > Ethernet Controller (3C905B-TX Compatible)"></network> > </colinux> > > BTW, I am using the bridged network. I failed to setup NAT with W2k ICS. > Enabling W2k ICS always results with an error. It turns out that ICS uses > DHCP implicitly and there is another DHCP server running in my network so > ICS cannot be used (see the first common problem under > http://is-it-true.org/nt/nt2000/utips/utips11.shtml). > > Any take on these two issues? > > Thanks. > > Rob > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Robert P. <rob...@ho...> - 2004-04-05 18:05:05
|
Hi folks, coLinux is great. I am able to set up and run Fedora Core 1 with the 0.6.0 build on Windows 2000. However, I run into 2 issues. First, I cannot use DHCP with FC1. I get the same error as described in http://www.colinux.org/wiki/index.php/coLinuxIAQ#A1. Since there is no pump binary package for FC1, I haven't tried pump to see if will resolve the issue. FC1 uses dhclient for DHCP and I am not how to set it up to use pump. Second, using static IP, I cannot make a TCP connection from the W2k host to coLinux or vice versa. ping works but I got duplicate replies if I ping the W2k host (rpang-pc2) from coLinux: [rpang@colinux rpang]$ ping rpang-pc2 PING rpang-pc2 (130.35.168.159) 56(84) bytes of data. 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=4.96 ms 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=0 ttl=128 time=6.25 ms (DUP!) 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.11 ms 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=1 ttl=128 time=1.91 ms (DUP!) 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.13 ms 64 bytes from rpang-pc2 (130.35.168.159): icmp_seq=2 ttl=128 time=1.72 ms (DUP!) .. ping from W2k to coLinux seems to be okay though: C:\Documents and Settings\rpang>ping lvbcheng-pc Pinging lvbcheng-pc.us.oracle.com [130.35.168.148] with 32 bytes of data: Reply from 130.35.168.148: bytes=32 time=30ms TTL=64 Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 Reply from 130.35.168.148: bytes=32 time<10ms TTL=64 Reply from 130.35.168.148: bytes=32 time=10ms TTL=64 Ping statistics for 130.35.168.148: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 30ms, Average = 12ms Because of this problem, I cannot make X connection from coLinux to my cygwin/XFree86 running on my W2k host. Neither can I ssh from my W2k host back to coLinux. TCP connection to and from another machine on the network with coLinux is fine though. Here is my coLinux network setup: [rpang@colinux rpang]# ifconfig eth0 Link encap:Ethernet HWaddr 00:43:4F:4E:45:30 inet addr:130.35.168.148 Bcast:130.35.171.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1523574 errors:0 dropped:0 overruns:0 frame:0 TX packets:4726 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:104822082 (99.9 Mb) TX bytes:3234903 (3.0 Mb) Interrupt:2 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) My W2k network setup: Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : rpang-pc2 Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Description . . . . . . . . . . . : 3Com 3C918 Integrated Fast Ethernet Controller (3C905B-TX Compatible) Physical Address. . . . . . . . . : 00-C0-4F-5E-C2-DA DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 130.35.168.159 Subnet Mask . . . . . . . . . . . : 255.255.252.0 Default Gateway . . . . . . . . . : 130.35.168.1 DNS Servers . . . . . . . . . . . : 130.35.249.41 138.2.202.15 Primary WINS Server . . . . . . . : 138.2.202.14 Secondary WINS Server . . . . . . : 130.35.62.34 And my default.colinux.xml: <?xml version="1.0" encoding="UTF-8"?> <colinux> <block_device index="0" path="\DosDevices\e:\fedora_root" enabled="true"> </block_device> <block_device index="1" path="\DosDevices\e:\colinux_swap" enabled="true"> </block_device> <bootparams>ro root=/dev/cobd0</bootparams> <image path="vmlinux"></image> <memory size="64"></memory> <network index="0" type="bridged" name="3Com 3C918 Integrated Fast Ethernet Controller (3C905B-TX Compatible)"></network> </colinux> BTW, I am using the bridged network. I failed to setup NAT with W2k ICS. Enabling W2k ICS always results with an error. It turns out that ICS uses DHCP implicitly and there is another DHCP server running in my network so ICS cannot be used (see the first common problem under http://is-it-true.org/nt/nt2000/utips/utips11.shtml). Any take on these two issues? Thanks. Rob |
|
From: gboutwel <gbo...@pr...> - 2004-04-05 16:56:59
|
Hello, After some messing around, I was able to build using this modified cobuild.sh the latest colinux kernel and deamons. The patch refers to w32api.diff, this is the w32api.diff that was recently (March 14th 2004) posted to this mailing list. currently it's not availabel for d/l anywhere that I could tell, so the cobuild.sh script will have to be modified to point/d/l that file someplace or users will have to manually copy it there. Anyways, without futher ado, here's the patch (not this is my first public patch, so let me know if I've done something silly, stupid, or wrong): ------------------------------------------ Praize? Enter In... http://www.praize.com/ |
|
From: Dan A. <da...@co...> - 2004-04-05 14:05:13
|
On Mon, Apr 05, 2004 at 02:30:56PM +0100, Christoph Hellwig wrote: > > The VM shows better results than the host. What gives? Perhaps > > it is because of the combination of the host and guest's buffer > > cache? I'd like to know about more percise benchmarking methods > > for VMs. > > How are the virtual disks for the VM implemented? If you're doing > direct I/O these numbers are indeed strange. If not OTOH that's > expected because even synchronous I/O in the guest is actually > async which makes it a lot faster. The virtual block device driver in coLinux, named cobd, is synchronous with the host OS highest level read()/write() functions, which means e.g. for a READ block I/O request in the guest, filp->f_op->read() is called on an open 'struct file' in the host. If the call blocks, the entire guest VM blocks on it. So, according to this, any type of I/O in the guest means synchronous I/O in the host unless the data is already in the guest's buffer cache. It's not really the implementation I am planning to stick to, but it sure was very easy to implement. BTW, the block device on the host side can be a file or any device that exposes read()/write() interfaces to userspace. In this benchmarking case it is a 3GB file that hosts an image of an ext3 filesystem. -- Dan Aloni da...@co... |
|
From: Christoph H. <hc...@in...> - 2004-04-05 13:31:02
|
> The VM shows better results than the host. What gives? Perhaps > it is because of the combination of the host and guest's buffer > cache? I'd like to know about more percise benchmarking methods > for VMs. How are the virtual disks for the VM implemented? If you're doing direct I/O these numbers are indeed strange. If not OTOH that's expected because even synchronous I/O in the guest is actually async which makes it a lot faster. |
|
From: Dan A. <da...@co...> - 2004-04-05 13:14:55
|
Hello, Today I ran some dbench2 benchmarks in order to test coLinux's (http://www.colinux.org) virtual disk I/O performance. I'm cross-posting this message to the LKML, as I know that on that list there are some benchmarking experts or other people who may find this interesting. This is the output from a coLinux 2.4.25 guest VM configured with 128MB RAM running on a Linux 2.6.3 (BK) host that has a total of 256MB RAM. The host machine has a Mobile Intel Celeron CPU (2.20GHz). All filesystems used are ext3. colinux:/home/dax# dbench 5 -s -S 5 clients started 0 62477 10.01 MB/sec Throughput 10.0026 MB/sec (sync open) (sync dirs) 5 procs colinux:/home/dax# dbench 5 -s -S 5 clients started 0 62477 10.43 MB/sec Throughput 10.4262 MB/sec (sync open) (sync dirs) 5 procs colinux:/home/dax# dbench 5 -s -S 5 clients started 0 62477 10.90 MB/sec Throughput 10.8926 MB/sec (sync open) (sync dirs) 5 procs I then ran the same thing on the host itself, *without* the coLinux VM running in the background: hostile17:~/colinux# dbench 5 -s -S 5 clients started 0 62477 5.08 MB/sec Throughput 5.07573 MB/sec (sync open) (sync dirs) 5 procs hostile17:~/colinux# dbench 5 -s -S 5 clients started 0 62477 5.13 MB/sec Throughput 5.12705 MB/sec (sync open) (sync dirs) 5 procs The VM shows better results than the host. What gives? Perhaps it is because of the combination of the host and guest's buffer cache? I'd like to know about more percise benchmarking methods for VMs. -- Dan Aloni Cooperative Linux, lead developer da...@co... |
|
From: Dan A. <da...@co...> - 2004-04-05 10:58:21
|
Hello, For the ease of configuration, in Win32-TAP mode, I'd like coLinux to be able to set the host properties of the network interface: IP address netmask, MAC address, etc., according to configuration from the XML. Any patches are welcomed. -- Dan Aloni da...@co... |
|
From: Regis N. <re...@ho...> - 2004-04-05 09:56:26
|
I have to point out this:
http://www.nomachine.com/sources.php
and
http://www.nomachine.com/dev_build.php
So all the protocols are GPL'ed which is a very good start IMHO.
Now I have to try ...
Regis
----- Original Message -----
From: "Alejandro R. Sedeno" <as...@MI...>
To: <col...@li...>
Sent: Sunday, April 04, 2004 9:03 PM
Subject: Re: [coLinux-devel] NX + coLinux = Killer App
> That's all fine and good, but from a brief look at the website NX is not
> free. Don't get too excited unless you're willing to shell out for the
> server half of it. They do at least have a 30 day trial. (Apparently the
> software will not stop working after 30 days, but you won't be licensed
> to use it after that period without purchasing a license.)
>
> Server Personal Edition will run you $54.50 right now, normally 74.50.
>
> -Alejandro
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
|
|
From: Nathan C. <nat...@ya...> - 2004-04-05 07:04:31
|
Hi Dan, Ok, so you've got me on the multimedia side (no streaming audio via a VNC session), but I can always play mp3's on my local/host system (whether it's Windows or Linux). 1) Resumable sessions are a must for me. In fact, it is for this reason that I have always wondered why people run proprietary, commercial Xservers on their Windows box. The company I work for has thousands of licenses for such products when VNC is free. My primary system is a Windows laptop (I support Windows users). My laptop is in and out of standby mode and is frequently on and off of the network. Sometimes it is connected via ethernet, and sometimes wireless or dialup. I need to be able to reboot my laptop (another security patch) and come right back to the same session on my Linux box (I don't want to have to restart all of my apps). Some of my customers refuse to reboot their Windows machines because they have remote applications running simulations and they need to continue to run for hours to complete a simulation or something. If they were running VNC, they wouldn't have to worry about terminating their Xsession in order to reboot the client machine. 2) VNC is free! 3) Accessing Windows shares??? I do this all the time via either smbclient (console) or konqueror (GUI). So, I'm glad that NX meets some people's needs. I am a big fan of capitolism. But, I will be sticking with VNC, as it is free, meets my needs (resumable sessions, tunneled over VNC, and I can already access Windows shares), and NX doesn't seem to offer me anything worth paying for. I do appreciate your mention of this application. It isn't for me, but I'm sure that someone else will find this to be a killer app. Regards, :-) -Nathan Chilton --- Dan Milisic <dmi...@ca...> wrote: > Off the top of my head... > > - Multimedia Support (For example, streaming .mp3's > with xmms) > > - NX will let you access Windows share points on the > local machine > you're running NX Client on... whether it be the > VM's host or another > box on the 'net. > > VNC has its place but that's two very useful things > it can't do. > VNC has resumeable sessions, NX does not (yet). > Both are very much > cross-platform. > > D. > > Nathan Chilton wrote: > > >I always tunnel my VNC sessions through SSH... so, > why > >should I use NX instead? > > > >--Nathan > > > > > >--- Dan Milisic <dmi...@ca...> wrote: > > > > > >>Hi... > >> > >>Has anyone else tried NX under coLinux? It's > truly > >>amazing... I had > >>trouble getting NX to run on the coLinux > 'standard' > >>Debian image > >>yesterday, so I cooked up a Fedora Core 2 image > and > >>installed the NX > >>Server Personal Edition without any problems. > >> > >>NX Provides X11 while the coLinux VM hums along in > >>the background. > >>Here's a screenshot of NX running a Gnome 2.6 > >>session on my dual-head > >>WinXP notebook: > >> > >>http://66.207.121.60/harmony.jpg > >> > >>Set-up is very simple -- all that needs to be done > >>is install the NX > >>Server .rpm on the coLinux 'virtual' machine and > >>install the NX Client > >>exe on the Windows machine. In my situation I use > >>NAT to network > >>coLinux. Accessing the coLinux VM from anywhere > on > >>the 'Net (securely) > >>is as simple as forwarding port 22 in Windows ICS > >>(Internet Connection > >>Sharing) to the coLinux machine's private IP, and > >>hitting the external > >>IP of your Windows box with the NX Client. NX > will > >>tunnel X over SSH > >>so this is much more desirable than VNC. > >>Performance and stability have > >>been great thusfar. > >> > >>FYI, The FC2 Linux install is a 1GB compressed > image > >>(approximately > >>400MB compressed). If there's interest I can > upload > >>it to anyone who > >>wants to host and share. Gnome 2.6 is sweet! > >> > >>D. > >> > >> > >> > >> > >> > >> > >------------------------------------------------------- > > > > > >>This SF.Net email is sponsored by: IBM Linux > >>Tutorials > >>Free Linux tutorial presented by Daniel Robbins, > >>President and CEO of > >>GenToo technologies. Learn everything from > >>fundamentals to system > >> > >> > >> > >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > > > > >>_______________________________________________ > >>coLinux-devel mailing list > >>coL...@li... > >> > >> > >> > >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > >__________________________________ > >Do you Yahoo!? > >Yahoo! Small Business $15K Web Design Giveaway > >http://promotions.yahoo.com/design_giveaway/ > > > >. > > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux > Tutorials > Free Linux tutorial presented by Daniel Robbins, > President and CEO of > GenToo technologies. Learn everything from > fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ |
|
From: Bruno S. D. <bru...@ma...> - 2004-04-05 05:55:42
|
Hi, Dan Milisic wrote: > - Multimedia Support (For example, streaming .mp3's with xmms) I'd like better support for sound. It's a bit choppy for heavy use over network on solaris. > - NX will let you access Windows share points on the local machine > you're running NX Client on... whether it be the VM's host or another > box on the 'net. This is only if the NXServer is running on Linucks(TM). Nice to see this working on Solaris... :) NX is prolly one of the coolest apps I've used. Wanna see some solaris 10 with NXServer shots? http://www.mail.ac/users/kevin/nomachine/ -- Bruno Saverio Delbono Systems Engineer Open-Systems Group (not-profit) http://www.open-systems.org/ Email: Bruno.S.Delbono at {mail.ac,open-systems.org,wf0.com,lucifer.at} |
|
From: Alejandro R. S. <as...@MI...> - 2004-04-05 04:03:43
|
That's all fine and good, but from a brief look at the website NX is not free. Don't get too excited unless you're willing to shell out for the server half of it. They do at least have a 30 day trial. (Apparently the software will not stop working after 30 days, but you won't be licensed to use it after that period without purchasing a license.) Server Personal Edition will run you $54.50 right now, normally 74.50. -Alejandro |
|
From: Dan M. <dmi...@ca...> - 2004-04-05 03:31:44
|
Off the top of my head... - Multimedia Support (For example, streaming .mp3's with xmms) - NX will let you access Windows share points on the local machine you're running NX Client on... whether it be the VM's host or another box on the 'net. VNC has its place but that's two very useful things it can't do. VNC has resumeable sessions, NX does not (yet). Both are very much cross-platform. D. Nathan Chilton wrote: >I always tunnel my VNC sessions through SSH... so, why >should I use NX instead? > >--Nathan > > >--- Dan Milisic <dmi...@ca...> wrote: > > >>Hi... >> >>Has anyone else tried NX under coLinux? It's truly >>amazing... I had >>trouble getting NX to run on the coLinux 'standard' >>Debian image >>yesterday, so I cooked up a Fedora Core 2 image and >>installed the NX >>Server Personal Edition without any problems. >> >>NX Provides X11 while the coLinux VM hums along in >>the background. >>Here's a screenshot of NX running a Gnome 2.6 >>session on my dual-head >>WinXP notebook: >> >>http://66.207.121.60/harmony.jpg >> >>Set-up is very simple -- all that needs to be done >>is install the NX >>Server .rpm on the coLinux 'virtual' machine and >>install the NX Client >>exe on the Windows machine. In my situation I use >>NAT to network >>coLinux. Accessing the coLinux VM from anywhere on >>the 'Net (securely) >>is as simple as forwarding port 22 in Windows ICS >>(Internet Connection >>Sharing) to the coLinux machine's private IP, and >>hitting the external >>IP of your Windows box with the NX Client. NX will >>tunnel X over SSH >>so this is much more desirable than VNC. >>Performance and stability have >>been great thusfar. >> >>FYI, The FC2 Linux install is a 1GB compressed image >>(approximately >>400MB compressed). If there's interest I can upload >>it to anyone who >>wants to host and share. Gnome 2.6 is sweet! >> >>D. >> >> >> >> >> >> >------------------------------------------------------- > > >>This SF.Net email is sponsored by: IBM Linux >>Tutorials >>Free Linux tutorial presented by Daniel Robbins, >>President and CEO of >>GenToo technologies. Learn everything from >>fundamentals to system >> >> >> >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > >>_______________________________________________ >>coLinux-devel mailing list >>coL...@li... >> >> >> >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > >__________________________________ >Do you Yahoo!? >Yahoo! Small Business $15K Web Design Giveaway >http://promotions.yahoo.com/design_giveaway/ > >. > > > |
|
From: morfic <mo...@bb...> - 2004-04-05 03:23:38
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body> <5cents>i used to use vnc cause i didnt want to get CygwinX or buy Xwin32, but now having set up cygwin including xfree (for another project), i have to say, having X windows show up with a taskbar button per window, not one per desktop as i got it with vnc, i can see the benefits, im using flashdesktops ( <a class="moz-txt-link-abbreviated" href="http://www.flashdesktops.com">www.flashdesktops.com</a> ) on XP Pro, this way i could display windows on XP and move them to one of the 8 desktop im using as i am doing with any native win32 application, what im trying to say is, this is a matter of personal preference ( i defenitely switched teams and am loving cygwin X to display my X windows now), and vnc being easier than cygwin Xserver, honestly both is about as easy to setup, vnc probably has a size benefit on its side </5cents><br> <br> Jose Miguel Martinez wrote:<br> <blockquote cite="mid...@eu..." type="cite"> <pre wrap="">In case it is useful for somebody, I am using vnc for running graphic sessions in colinux. I think it is easier and simpler than all this X and cygwin stuff. You run vncserver in the colinux machine (it is already in debian and gentoo) and then use an vnc client in the windows machine. Vnc clients exists for a lot of architectures, win32 included. You can detach and reatach later to a graphic session, what you cannot do with an X session due to X clients deading when X connection lost. El Domingo, 4 de Abril de 2004 18:52, Digital Infra, Inc. escribió: </pre> <blockquote type="cite"> <pre wrap="">Hello Kerver. I am working on making an installer of Cygwin/X Japanese for coLinux. I tried your zip file and found that it requires basic cygwin system is installed. Do you have a way/plan to eliminate this feature? How to run your zip alone, without Cygwin itself? --- Okajima. </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">I used cygwin X. On coLinux (Debian), use dselect to find xterm and install it or do an "apt-get install xterm" instead. From cygwin, use "xhost +" to allow any connection, and that is okay behind a firewall. </pre> </blockquote> <pre wrap="">I copied all relevant files from cygwin for the XServer and deleted the rest of cygwin leaving me with only 6 Mb of DLL's to run the XWin server OUTSIDE cygwin (packed about 2.5 MB) ;) I zipped all of these and put them online, and put a bat file to startup the server. Tested with KDE and Enlightment, works fine a compact XServer for the till coLinux supports X native. <a class="moz-txt-link-freetext" href="http://speeldoos.showcase.surfnet.nl/startx.zip">http://speeldoos.showcase.surfnet.nl/startx.zip</a> regards, Bart ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! <a class="moz-txt-link-freetext" href="http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click">http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click</a> _______________________________________________ coLinux-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:coL...@li...">coL...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/colinux-devel">https://lists.sourceforge.net/lists/listinfo/colinux-devel</a> </pre> </blockquote> <pre wrap="">------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ coLinux-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:coL...@li...">coL...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/colinux-devel">https://lists.sourceforge.net/lists/listinfo/colinux-devel</a> </pre> </blockquote> <pre wrap=""><!----> </pre> </blockquote> </body> </html> |
|
From: Nathan C. <nat...@ya...> - 2004-04-05 03:12:05
|
I always tunnel my VNC sessions through SSH... so, why should I use NX instead? --Nathan --- Dan Milisic <dmi...@ca...> wrote: > Hi... > > Has anyone else tried NX under coLinux? It's truly > amazing... I had > trouble getting NX to run on the coLinux 'standard' > Debian image > yesterday, so I cooked up a Fedora Core 2 image and > installed the NX > Server Personal Edition without any problems. > > NX Provides X11 while the coLinux VM hums along in > the background. > Here's a screenshot of NX running a Gnome 2.6 > session on my dual-head > WinXP notebook: > > http://66.207.121.60/harmony.jpg > > Set-up is very simple -- all that needs to be done > is install the NX > Server .rpm on the coLinux 'virtual' machine and > install the NX Client > exe on the Windows machine. In my situation I use > NAT to network > coLinux. Accessing the coLinux VM from anywhere on > the 'Net (securely) > is as simple as forwarding port 22 in Windows ICS > (Internet Connection > Sharing) to the coLinux machine's private IP, and > hitting the external > IP of your Windows box with the NX Client. NX will > tunnel X over SSH > so this is much more desirable than VNC. > Performance and stability have > been great thusfar. > > FYI, The FC2 Linux install is a 1GB compressed image > (approximately > 400MB compressed). If there's interest I can upload > it to anyone who > wants to host and share. Gnome 2.6 is sweet! > > D. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux > Tutorials > Free Linux tutorial presented by Daniel Robbins, > President and CEO of > GenToo technologies. Learn everything from > fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ |
|
From: Dan M. <dmi...@ca...> - 2004-04-05 00:51:43
|
Hi... Has anyone else tried NX under coLinux? It's truly amazing... I had trouble getting NX to run on the coLinux 'standard' Debian image yesterday, so I cooked up a Fedora Core 2 image and installed the NX Server Personal Edition without any problems. NX Provides X11 while the coLinux VM hums along in the background. Here's a screenshot of NX running a Gnome 2.6 session on my dual-head WinXP notebook: http://66.207.121.60/harmony.jpg Set-up is very simple -- all that needs to be done is install the NX Server .rpm on the coLinux 'virtual' machine and install the NX Client exe on the Windows machine. In my situation I use NAT to network coLinux. Accessing the coLinux VM from anywhere on the 'Net (securely) is as simple as forwarding port 22 in Windows ICS (Internet Connection Sharing) to the coLinux machine's private IP, and hitting the external IP of your Windows box with the NX Client. NX will tunnel X over SSH so this is much more desirable than VNC. Performance and stability have been great thusfar. FYI, The FC2 Linux install is a 1GB compressed image (approximately 400MB compressed). If there's interest I can upload it to anyone who wants to host and share. Gnome 2.6 is sweet! D. |
|
From: Jose M. M. <tx...@eu...> - 2004-04-04 23:26:00
|
In case it is useful for somebody, I am using vnc for running graphic sessi= ons=20 in colinux. I think it is easier and simpler than all this X and cygwin=20 stuff. You run vncserver in the colinux machine (it is already in debian and gento= o)=20 and then use an vnc client in the windows machine. Vnc clients exists for a= =20 lot of architectures, win32 included. You can detach and reatach later to a= =20 graphic session, what you cannot do with an X session due to X clients=20 deading when X connection lost. El Domingo, 4 de Abril de 2004 18:52, Digital Infra, Inc. escribi=F3: > Hello Kerver. > > I am working on making an installer of Cygwin/X Japanese for coLinux. > I tried your zip file and found that it requires basic cygwin system is > installed. Do you have a way/plan to eliminate this feature? > How to run your zip alone, without Cygwin itself? > > --- Okajima. > > >> I used cygwin X. > >> > >> On coLinux (Debian), use dselect to find xterm and install it or do an > >> "apt-get install xterm" instead. > >> > >> From cygwin, use "xhost +" to allow any connection, and that is okay > >> behind a firewall. > > > >I copied all relevant files from cygwin for the XServer and deleted the > >rest of cygwin leaving me with only 6 Mb of DLL's to run the XWin server > >OUTSIDE cygwin (packed about 2.5 MB) ;) > > > >I zipped all of these and put them online, and put a bat file to startup > >the server. Tested with KDE and Enlightment, works fine a compact > >XServer for the till coLinux supports X native. > > > >http://speeldoos.showcase.surfnet.nl/startx.zip > > > >regards, > >Bart > > > > > >------------------------------------------------------- > >SF.Net is sponsored by: Speed Start Your Linux Apps Now. > >Build and deploy apps & Web services for Linux with > >a free DVD software kit from IBM. Click Now! > >http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick > >_______________________________________________ > >coLinux-devel mailing list > >coL...@li... > >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel =2D-=20 ______________________________ < hola, soy una firma horrible > ------------------------------ \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || txemi <tx...@eu...> web: http://txemi.webhop.org mirror: http://txemi2.webhop.org mirror2: http://txemi3.webhop.org=09 |
|
From: Digital I. Inc. <ok...@di...> - 2004-04-04 16:52:33
|
Hello Kerver.
I am working on making an installer of Cygwin/X Japanese for coLinux.
I tried your zip file and found that it requires basic cygwin system is installed.
Do you have a way/plan to eliminate this feature?
How to run your zip alone, without Cygwin itself?
--- Okajima.
>> I used cygwin X.
>>
>> On coLinux (Debian), use dselect to find xterm and install it or do an
>> "apt-get install xterm" instead.
>>
>> From cygwin, use "xhost +" to allow any connection, and that is okay behind
>> a firewall.
>
>I copied all relevant files from cygwin for the XServer and deleted the
>rest of cygwin leaving me with only 6 Mb of DLL's to run the XWin server
>OUTSIDE cygwin (packed about 2.5 MB) ;)
>
>I zipped all of these and put them online, and put a bat file to startup
>the server. Tested with KDE and Enlightment, works fine a compact
>XServer for the till coLinux supports X native.
>
>http://speeldoos.showcase.surfnet.nl/startx.zip
>
>regards,
>Bart
>
>
>-------------------------------------------------------
>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>Build and deploy apps & Web services for Linux with
>a free DVD software kit from IBM. Click Now!
>http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
>_______________________________________________
>coLinux-devel mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
|
|
From: Regis N. <re...@ho...> - 2004-04-03 13:51:47
|
Right, then you just have to replace the: NSISdl::download line 592 with an: Exec "$R2" Goto End and an external program will handle the download. You can also add a real link in iDl.ini: Text = To Sourceforge Download State = http://sourceforgeUrl Hope it works. It could be easy to add Var to decide either handle the download or spawn it :) Regis NEBOR ----- Original Message ----- From: "Dan Aloni" <da...@co...> To: "Regis NEBOR" <re...@ho...> Cc: <col...@li...> Sent: Saturday, April 03, 2004 5:10 AM Subject: [coLinux-devel] Re: lastest installer script > On Sat, Apr 03, 2004 at 02:38:49AM -0800, Regis NEBOR wrote: > > changes: > > > > - bugfix for gentoo image download > > - Made adding another image easier > > This is nice, but I think that downloading the image using the installation script > itself is not a good idea. I think it would be better to let the user use he/she's > own download manager. > > -- > Dan Aloni > da...@co... > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Dan A. <da...@co...> - 2004-04-03 13:09:58
|
On Sat, Apr 03, 2004 at 02:38:49AM -0800, Regis NEBOR wrote: > changes: > > - bugfix for gentoo image download > - Made adding another image easier This is nice, but I think that downloading the image using the installation script itself is not a good idea. I think it would be better to let the user use he/she's own download manager. -- Dan Aloni da...@co... |
|
From: Regis N. <re...@ho...> - 2004-04-03 10:38:58
|
changes: - bugfix for gentoo image download - Made adding another image easier Regis NEBOR |
81 messages has been excluded from this view by a project administrator.
