colinux-users — coLinux users mailing list

Re: [coLinux-users] performance

[Mitch B. <wm...@ag...>]

I was unable to find much documentation.  Through trial and error and 
source perusal, I came up with this recipe:

1) Open a Command Prompt or shell window and cd to the coLinux 
directory, e.g. "cd c:\colinux"

2) To see a list of options:

         colinux-debug-daemon -h

3) To see a list of "facility" names:

          colinux-debug-daemon -d
          (Type ^C to exit back to the cmd prompt.)

    * "facilities" are different types of messages that the daemon can
      capture.   The current list of facility names is:
    *            misc, network, messages, prints, blockdev, allocations,
      context_switch, pipe
    * Each facility has an associated level number - higher numbers
      capture more messages.
    * See below for how to set the facility level


4) To capture and display some messages:

            colinux-debug-daemon  -d  -p  -f mylogfile.xml  -s 
network=11,blockdev=9 

    * "-d" makes it get the raw debug messages in real time from a
      running colinux session.  Without "-d", it gets the raw debug
      messages from standard input, presumably from a
      previously-captured file.
    * "-p" makes it decode (parse) the raw debug messages and display
      them in human-readable form (encapsulated in XML markup).  Without
      "-p", I presume that it just sends the raw debug messages to the
      output, perhaps so you can capture them to a file in a compact
      form for later inspection.
    * "-f mylogfile.xml" makes it append the output to the file
      "mylogfile.xml".  Without "-f", it sends the output to standard
      output.  As far as I can tell, "-f filename" is equivalent to
      ">>filename".
    * "-s network=11,blockdev=9" sets the "network" facility level to
      11, thus capturing network messages sent at levels 0-11, and the
      "blockdev" facility level to 9.
    * To determine the desired facility level, either increase the
      number (trial and error) until you see the level of detail you
      need, or inspect the source code for the component you wish to
      debug to see the level at which the desired messages are sent.

5) There is also a "-n  ip-address" switch that will send the logs to 
UDP port 63000 at the indicated IP address, instead of to standard 
output or a file.  I suspect, but am not entirely sure, that you can use 
this feature either with or without the "-p" switch, thus sending either 
raw or preparsed messages to the remote machine.

6) There is a python program to listen on port 63000 and write the logs 
to a file.  The python program is in the source tarball, in 
src/colinux/user/debug/server.py

7) There is a python program to decode and display the XML-formatted 
(preparsed) messages.  It is in the source tarball, in 
src/colinux/user/debug/dump.py .  It is not strictly necessary to use 
this program; the XML-formatted messages are in ASCII and are easy 
enough to read directly.

8) The source code for colinux-debug-daemon is in the source tarball, in 
src/colinux/user/debug/main.c

9) The source code for various other colinux helper daemons (i.e. the 
things that ultimately send the debug messages) is in the source tarball 
in various places.  For example, the bridged network daemon source for 
Windows is in src/colinux/os/winnt/user/conet-bridged-daemon/

10) Debug messages are sent by calls like the following:

       co_debug_lvl(network, 13, "packet sent (0x%x written)\n", 
write_size);

Hope this helps,
Mitch Bradley

Holger Krull wrote:

>> Actually if you use recent snapshots, they include an 
>> colinux-debug-daemon,
>> which can be used to capture very detailed debug logs of things.
>
>
> Is there any description available on howto use the debug-daemon?
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out 
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] Invalid checksums

[Xavier B. <xav...@gm...>]

Hi,

I'm running CoLinux 0.6.2 on Windows 2000 SP4 to run a Debian image. 
I've got invalid checksums which makes impossible to run an ssh
session between the host and colinux.  I'm using a bridged ethernet
connection.

My configuration is :
<?xml version="1.0" encoding="UTF-8"?>
<colinux>
    <block_device index="0"
path="\DosDevices\e:\colinux\Debian-20040605-mit.ext3.1610mb"
enabled="true" />
    <block_device index="1" path="\DosDevices\e:\colinux\swap_512Mb"
enabled="true"></block_device>
    <bootparams>root=/dev/cobd0</bootparams>
    <image path="vmlinux" />
    <memory size="128" />
    <!--  <network index="0" type="tap" /> -->
    <network index="0" type="bridged" name="Marvell" />
</colinux>

A sample tethereal trace (host=192.168.1.100, colinux=192.168.1.102)
of a putty ssh connection:
No.     Time        Source                Destination           Protocol Info
      3 0.008588    192.168.1.100         192.168.1.102         TCP   
  1163 > 22 [SYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460
      4 0.008769    192.168.1.100         192.168.1.102         TCP   
  1163 > 22 [SYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460
      5 0.023884    192.168.1.102         192.168.1.100         TCP   
  22 > 1163 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460
      6 0.023902    192.168.1.100         192.168.1.102         TCP   
  1163 > 22 [ACK] Seq=1 Ack=1 Win=65535 [CHECKSUM INCORRECT] Len=0
      7 0.024081    192.168.1.100         192.168.1.102         TCP   
  [TCP Dup ACK 6#1] 1163 > 22 [ACK] Seq=1 Ack=1 Win=65535 Len=0
      8 0.024373    192.168.1.102         192.168.1.100         TCP   
  22 > 1163 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460
      9 0.024387    192.168.1.100         192.168.1.102         TCP   
  1163 > 22 [ACK] Seq=1 Ack=1 Win=65535 [CHECKSUM INCORRECT] Len=0
     10 0.024564    192.168.1.100         192.168.1.102         TCP   
  [TCP Dup ACK 9#1] 1163 > 22 [ACK] Seq=1 Ack=1 Win=65535 Len=0

As you can see, there are some packets with an invalid checksum and
others with a valid checksum.

The network card is a "Marvell Yukon Gigabit Ethernet
10/100/1000Base-T Adapter, Copper RJ-45" running at 100Mbps.

It only happens between the host and colinux.  On colinux, I can
flawlessly install packages and so on...

Any idea why it happens ?

Thank you,
Xavier Brouckaert

Re: [coLinux-users] performance

[Holger K. <hol...@gm...>]

> Actually if you use recent snapshots, they include an colinux-debug-daemon,
> which can be used to capture very detailed debug logs of things.

Is there any description available on howto use the debug-daemon?

[coLinux-users] Re: Up and running at last

[Martin K. <ka...@po...>]

Hi,

Simon Turvey wrote:
> Hi all,
> 
> Windows 2000 and CoLinux 6.2pre3; phew, what a nightmare.  I seem to 
> have got things running now.  My desire was for a bridged connection as 
> my company's VPN software plays silly beggars with ICS.  My problem 
> seemed to stem from the documentation on the wiki with respect to 
> setting up bridged connections.  Seems everyone else is using Windows XP 
> and the native bridging that it provides.
I do not. I use TAP and Loopback device for host<->colinux communication 
and bridging (PCAP!) ethernet card to the rest of (inter)net.

> Under Win2k, is the TAP-Win32 device required for a bridged connection? 
TAP  device doesn't need PCAP or XP-bridge. if you use TAP only for 
communication with host. if you need to go to internet, you can install 
sock server or other software to route the communication. most of users 
use ICS or XP-bridge. This doesn't work with WLAN (not really sure). You 
can't use PCAP for WLAN (quite sure).

> Which is the correct name to use for the connection.  Again, the 
> documentation (README) suggests getting the name from the 'Connect 
> Using' label in the connection properties.  This cannot be true as I 
> didn;t get this working until I specified 'Local Area Connection' i.e. 
> my default connection as the one to bridge using.
I think if you use snapshot than you have to use the obvious name - as 
you did. If you use 0.6.1 and older version there was indeed other way 
to discover the names, but it wasn't as easy as written in Wiki 
especialy on non-english versions of windows.

> Answer these and I'll update the docs so noone else has to go through 
> this trial-and-error situation :)
Great!

Regards,
Martin

RE: [coLinux-users] Up and running at last

[peter g. <plu...@bi...>]

basically there are two totally different ways of doing networking with
colinux

TAP gives you a fake network adaptor that you can do whatever you like with
(put it in the windows bridge use ICS with it etc)

WINPCAP attaches to an existing network adaptor and makes colinux appear to
be a seperate machine on the network that adaptor is connected too

as for the correct name it was originally the adaptor driver name however
this caused problems for people with two adaptors of the same brand in their
computer so it was changed to using the connection name. Im unsure exactly
when this change was made.



> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of Simon
> Turvey
> Sent: 06 October 2004 23:00
> To: col...@li...
> Subject: [coLinux-users] Up and running at last
>
>
> Hi all,
>
> Windows 2000 and CoLinux 6.2pre3; phew, what a nightmare.  I seem to
> have got things running now.  My desire was for a bridged connection as
> my company's VPN software plays silly beggars with ICS.  My problem
> seemed to stem from the documentation on the wiki with respect to
> setting up bridged connections.  Seems everyone else is using Windows XP
> and the native bridging that it provides.
>
> So, a few questions so I can update the documentation with some clearer
> instructions.
>
> Under Win2k, is the TAP-Win32 device required for a bridged connection?
>   The documentation seems to imply that it is not.
>
> Which is the correct name to use for the connection.  Again, the
> documentation (README) suggests getting the name from the 'Connect
> Using' label in the connection properties.  This cannot be true as I
> didn;t get this working until I specified 'Local Area Connection' i.e.
> my default connection as the one to bridge using.
>
> Answer these and I'll update the docs so noone else has to go through
> this trial-and-error situation :)
>
> All the best,
>
> si.
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] Up and running at last

[Simon T. <tur...@ca...>]

Hi all,

Windows 2000 and CoLinux 6.2pre3; phew, what a nightmare.  I seem to 
have got things running now.  My desire was for a bridged connection as 
my company's VPN software plays silly beggars with ICS.  My problem 
seemed to stem from the documentation on the wiki with respect to 
setting up bridged connections.  Seems everyone else is using Windows XP 
and the native bridging that it provides.

So, a few questions so I can update the documentation with some clearer 
instructions.

Under Win2k, is the TAP-Win32 device required for a bridged connection? 
  The documentation seems to imply that it is not.

Which is the correct name to use for the connection.  Again, the 
documentation (README) suggests getting the name from the 'Connect 
Using' label in the connection properties.  This cannot be true as I 
didn;t get this working until I specified 'Local Area Connection' i.e. 
my default connection as the one to bridge using.

Answer these and I'll update the docs so noone else has to go through 
this trial-and-error situation :)

All the best,

si.

Re: [coLinux-users] performance

[Mitch B. <wm...@ag...>]

I am using bridged networking with 20041002.  Network adapter matching 
is different between 20041002 and earlier snapshots.  The matched name 
used to be an internal name for the adapter, but now the name is the 
same one that is displayed underneath the connection icon in the Windows 
"Network Connections" window.  It is the name that Windows lets you 
change by right-clicking the connection icon and selecting "Rename".

  For example, for 20040910 my colinux.xml file used to say:

       <network index="0" type="bridged" name="Broadcom NetXtreme"/>

but now with 20041002 it says:

       <network index="0" type="bridged" name="Local Area Connection" />

The startup messages in the CMD window contain a list of the names that 
coLinux tries to match against.

Jaroslaw Fedevych (UALUG wrote:

>On Wed, Oct 06, 2004 at 04:49:28PM -0000, gboutwel wrote:
>  
>
>>Actually if you use recent snapshots, they include an colinux-debug-daemon,
>>which can be used to capture very detailed debug logs of things.
>> If users could use that daemon to produce logs of situations
>>where latency is a problem and (without inundating the developers)
>>provide them back to us, then we can anaylize them and find more
>>bottlenecks and fix them.
>>
>>    
>>
>
>Ack! Will need to get the time to hunt down what is wrong with it,
>if that recent snapshot will allow me to use bridged networking at all.
>(I'm on a LAN and TAP-Win32 with ICS is not for me)
>
>When I started 20041002 daemon, it was running nice except for the
>winPCAP initialization error (it had found matching network connection,
>but then, all of a sudden, it told ``no matching adapter'' and 
>``Error initializing winpcap''). However, I had no time to investigate
>any deeper, as $BOSSES demanded web server (running on coLinux) here and 
>now :).
>
>  
>

Re: [coLinux-users] performance

[Jaroslaw F. (U. <jar...@li...>]

On Wed, Oct 06, 2004 at 04:49:28PM -0000, gboutwel wrote:
> Actually if you use recent snapshots, they include an colinux-debug-daemon,
> which can be used to capture very detailed debug logs of things.
>  If users could use that daemon to produce logs of situations
> where latency is a problem and (without inundating the developers)
> provide them back to us, then we can anaylize them and find more
> bottlenecks and fix them.
> 

Ack! Will need to get the time to hunt down what is wrong with it,
if that recent snapshot will allow me to use bridged networking at all.
(I'm on a LAN and TAP-Win32 with ICS is not for me)

When I started 20041002 daemon, it was running nice except for the
winPCAP initialization error (it had found matching network connection,
but then, all of a sudden, it told ``no matching adapter'' and 
``Error initializing winpcap''). However, I had no time to investigate
any deeper, as $BOSSES demanded web server (running on coLinux) here and 
now :).

-- 
X Windows: If it's broke, don't fix it.

[coLinux-users] Sorry. Wrong mailing list

[Brendan S. <Bre...@fa...>]

It looks like I accidently CC'd the wrong mailing list regarding the 
gumstix.
Sorry <blush>

Brendan Simon.


col...@li... wrote:

>   4. Re: [Gumstix-users] USb net (Brendan Simon)
>  
>

[coLinux-users] Re: [Gumstix-users] USb net

[Brendan S. <Bre...@fa...>]

Hi Iain,

I got mine working fine with XP after using the linux.inf file.
Did using the linux.inf keep MSW happy regarding the Ethernet Gadget it 
detected?

Does the Ether Tap device say it has a connection when colinux is started?

Are you using XP?
Are you using XP in bridged mode?
If so, you DO NOT have to bridge from the linux side as it is done at 
the XP side.

How are you setting the IP address of the gumstix?
DHCP or static IP settings?  If DHCP, is your DHCP server confiured 
properly?

Is your linux IP address on the same subnet as the Windows IP address?

Cheers,
Brendan (from sometimes sunny Melbourne, Australia)


Iain Rankin wrote:

>Hi Brendan
>Thanks for the reply.
>I tried the Linux.inf and it didnt work either. Did you manage to get yours
>working ok.
>Cheers,
>Iain from Sunny Belfast
>  
>

[coLinux-users] Block device aliasing for dual-boot

[Shi, J. <Ju...@or...>]

I just upgraded to snapshot (20041006) and found a commend in the default
XML file the new block device alsasing stuff.
Is there more detail info about it, especially how to use it for dual-boot
system and how it works?

I have setup the colinux successfully to boot into my suse partion and got
it running. The problem is that the fstab and the network need to be changed
to get it work. Then these setting need to be changed back in order to boot
into suse (not through colinux). 

My question is: can the block device aliasing help in this situation?

Another question is regarding the initrd file. Is it possible to use it to
solve my problem above?

Thanks and best regards,
Jues

[coLinux-users] 0.6.2-pre4 - NX bit issue solved

[Dan A. <da...@co...>]

Hello,

Paradise (paradyse at gmail.com) has just confirmed that 
the latest snapshot (0.6.2-pre4) works with the NX bit 
enabled on an AMD64 box.

Enjoy this, and thanks for everyone who have helped.

-- 
Dan Aloni
da...@co...

Re: [coLinux-users] Re: performance

[sophana <sop...@ya...>]

I forgot to thank you all for your great job, and understand that 
profiling such a problem is not easy.
I would be glad to help, but unfortunately I actually don't have enough 
time to spend on the project.

Keep on the good work!

gboutwel wrote:

>>Is there a plan of getting rid of that network performance
>>    
>>
>problem?
>
>
>
>Obviously the answer is yes.  If the problem is in/with coLinux
>we hope to find it and fix it.  If it's in WinPCAP, TAP-Win32,
>PCAP (under linux), or TAP (under linux) then we probably won't
>be able to do much about it.
>
>
>
>  
>
>>Maybe it is because of winpcap?
>>    
>>
>
>
>
>The tests that we have done, show TAP being faster than WinPCAP.
> So there is some problem with WinPCAP, if you can switch to
>using TAP you MIGHT see performance improve.
>
>
>
>  
>
>>I would like to use windows machines to compute for our cluster,
>>    
>>
>that
>
>  
>
>>does lot of network activity fetching data to be processed
>>    
>>
>from nfs.
>
>  
>
>>(later AFS I hope) network performance is definitly a big problem...
>>    
>>
>
>
>
>Currently the problem is that resources are limited and we have
>other things that seem to be a higher priority.  Add to that
>we don't have an lot of networking gurus (programmers don't automatically
>= network gurus), and we need help from users getting the info
>we need to determine where bottlenecks are.
>
>
>
>We have found and remoed some bottle necks already.  If you are
>using the 0.6.1 release of coLinux you should see an significant
>improvement by moving to the recent coLinux snapshots, or moving
>to the next release of coLinux when it goes out.
>
>
>
>HTH,
>
>
>
>George
>
>
>
>------------------------------
>
>Love the funnies?
>
>Christian Cartoons at Praize
>
>http://www.praize.com/cartoons/
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>Use IT products in your business? Tell us what you think of them. Give us
>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>_______________________________________________
>coLinux-users mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>  
>

[coLinux-users] coLinux 0.6.2-pre3

[Dan A. <da...@co...>]

On Mon, Oct 04, 2004 at 06:12:00PM +0800, Paradise wrote:
> Yes, I did remove old driver by "colinux-daemon --remove-driver" and
> installing it again
> with "colinux-daemon --install-driver". 
> 
> The crashed blue screen code as below:
> 
> 0x000000FC (0xEC0C201C, 0x006A817B, 0xF3BF7A74, 0x00000001)
> NAVENG.SYS - Address F3BF7A74 base at F3BF7A74 Datestamp 00000000
> 
> It runs if I turn OFF NX, However It crashes when I turn on NX. About
> "naveng.sys"
>  it's something relate to Norton AntiVirus? I am running Norton System
> Work 2004 on my system.

I've uploaded a new snapshot (20041006) that specifically addresses the 
NX bit problem, by directly turning it off in the page tables. Can you 
please retry with this?

-- 
Dan Aloni
da...@co...

Re: [coLinux-users] CoLinux as a router

[A. K. <kli...@we...>]

tei wrote:

> A. Klingenstein wrote:
>
>> I want to set up the following: using CoLinux as a router for my host 
>
>
>
> Other option can be to run colinux has proxy. Because proxy work on 
> application layer, may be easyer than router.
>
That's not my problem. I can have NAT in 2 seconds: apt-get install 
ipmasq, but: as soon as I put in a second NIC in the colinux instance 
either it does not work at all or windows crashes. For a proxy I would 
need a working connection to the host OS too, which I currently lack
And if  I have a connection, I can just as well do proper NAT instead 
fudging around with proxies

Alex

Re: [coLinux-users] performance

[gboutwel <gbo...@pr...>]

> First someone had to track down which part of the system is
adding the

> latency to every packet.

> Winpcap, colinux driver or the colinux kernel itself.

> Can't be done without changeing the source and is therefore
a little

> complicated.



Actually if you use recent snapshots, they include an colinux-debug-daemon,
which can be used to capture very detailed debug logs of things.
 If users could use that daemon to produce logs of situations
where latency is a problem and (without inundating the developers)
provide them back to us, then we can anaylize them and find more
bottlenecks and fix them.



This method has already more or less been used to remove a couple
bottlenecks arleady.



HTH,



George



----------------------------------------------------

Need to store your files online? 

Upload them for free in Praize Briefcase

http://www.praize.com/cgi-bin/members/mybriefcase.cgi

Re: [coLinux-users] Re: performance

[gboutwel <gbo...@pr...>]

> Is there a plan of getting rid of that network performance
problem?



Obviously the answer is yes.  If the problem is in/with coLinux
we hope to find it and fix it.  If it's in WinPCAP, TAP-Win32,
PCAP (under linux), or TAP (under linux) then we probably won't
be able to do much about it.



> Maybe it is because of winpcap?



The tests that we have done, show TAP being faster than WinPCAP.
 So there is some problem with WinPCAP, if you can switch to
using TAP you MIGHT see performance improve.



> I would like to use windows machines to compute for our cluster,
that

> does lot of network activity fetching data to be processed
from nfs.

> (later AFS I hope) network performance is definitly a big problem...



Currently the problem is that resources are limited and we have
other things that seem to be a higher priority.  Add to that
we don't have an lot of networking gurus (programmers don't automatically
= network gurus), and we need help from users getting the info
we need to determine where bottlenecks are.



We have found and remoed some bottle necks already.  If you are
using the 0.6.1 release of coLinux you should see an significant
improvement by moving to the recent coLinux snapshots, or moving
to the next release of coLinux when it goes out.



HTH,



George



------------------------------

Love the funnies?

Christian Cartoons at Praize

http://www.praize.com/cartoons/

Re: [coLinux-users] CoLinux as a router

[tei <42...@in...>]

A. Klingenstein wrote:
> I want to set up the following: using CoLinux as a router for my host 


Other option can be to run colinux has proxy. Because proxy work on 
application layer, may be easyer than router.

Re[2]: [coLinux-users] Hi, new user and how install distros on colinux

[HUMA2000 <HUM...@te...>]

Oh, thanks! i haven't see the slackware section on wiki page, is also possible install the red hat distro using a similar way?

Tuesday, October 5, 2004, 6:38:06 PM, escribió:

MJAI> Check out the wiki @ http://www.colinux.org/wiki/
MJAI>  
MJAI> There is an article on the Wiki specifically for
MJAI> Slackware Here ->
MJAI> http://www.colinux.org/wiki/index.php/SlackwareHowTo
  
MJAI> ----- Original Message ----- 
  
MJAI> From:  HUMA2000
  
MJAI> To:coL...@li...  
  
MJAI> Sent: Tuesday, October 05, 2004 6:04   AM
  
MJAI> Subject: [coLinux-users] Hi, new user and   how install distros on colinux
  


  
MJAI> Hello, i'm a new user of colinux, is a great idea, but i
MJAI> have a little   trouble, i wanna use red hat or slackware over
MJAI> colinux, how can i install??   Thanks in advance.

  
MJAI> Excuse my bad english.

  



  
MJAI> ----------------------------------------------------

  
MJAI> HUMA2000

  
MJAI> HUM...@on...

  
MJAI> HUM...@te...

  
MJAI> hum...@gm...

  
MJAI> MSN: HUM...@ho...

  
MJAI> AIM; HUM...@ao...

  
MJAI> Yahoo!: HUM...@ya...

  
MJAI> ICQ: 50463695

  





MJAI> __________ NOD32 1.868 (20040910) Information   __________

MJAI> This message was checked by NOD32 antivirus system.
MJAI> http://www.nod32.com






----------------------------------------------------
HUMA2000
HUM...@on...
HUM...@te...
hum...@gm...
MSN: HUM...@ho...
AIM; HUM...@ao...
Yahoo!: HUM...@ya...
ICQ: 50463695

[coLinux-users] Easy install of a debian

[Pierre C. <pit...@gm...>]

Hi everybody
I have a few troubles installing my debian with colinux
Since it's only about copying files on my computer, I was wondering if
ti could be possible to have some kind of iso that would be installed
in one click
This iso would be hosted thanx to bittorent
I am a fan of linux live cds like damn small linux, dynebolic or slax
and love the easyness of them, I think colinux should become as easy
to use as them
I will work on this thing myself but do you, colinux users, think it
is a good idea ?
pi2

http://pit2PEER.org
--
A software is like a CD burner, sometimes it is open, sometimes it is closed.

[coLinux-users] CoLinux as a router

[A. K. <kli...@we...>]

I want to set up the following: using CoLinux as a router for my host 
(Windows XP). THe host will be nat'ed behind CoLinux which will use 
PPPoE DSL to connect to the internet.

I get a few problems however: I bridge one NIC and use it to connect to 
my DSL modem. This works fine: I can get a connection to my ISP. This is 
the config.xml line:
<network index="0" name="nforce2" type="bridged"></network>

Now I need to make a connection between CoLinux and the host. This is 
were problems start:

If I use a TAP adapter, I can't get a connection, at all,
If I put in a 2nd bridge, Windows always freezes sometime in the 
bootprocess of CoLinux. No BSOD; just a freeze, not even the mouse can 
be moved.

So what is the proper way to bridge one network interface and get a 
network connection to the host at the same time?

[coLinux-users] ifup: Cannot get driver information: Operation not supported

[Vincent M. <Vin...@un...>]

Hi,

I installed coLinux-0.6.1 on my windows XP, with=20
colinux_minimal_fedora_core_1
I can access to colinux console, but I haven't network access.

When I try a 'ifup eth0', I have this error :
ifup: Cannot get driver information: Operation not supported

Here's my configurations :

1) hardware
- an adsl router. Gateway =3D 10.0.0.138

- original ipconfig :
ipconfig :
Carte Ethernet Pont r=E9seau:

        Suffixe DNS propre =E0 la connexion : lan
        Adresse IP. . . . . . . . . . . . : 10.0.0.100
        Masque de sous-r=E9seau . . . . . . : 255.0.0.0
        Passerelle par d=E9faut . . . . . . : 10.0.0.138


- I put original lan connection and tap-win32 connection in a bridge


2) colinux

colinux.xml :
<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<colinux>
    <block_device index=3D"0"=20
path=3D"\DosDevices\c:\soft\colinux\fc1_2GB_root" enabled=3D"true">
    </block_device>
    <block_device index=3D"7"=20
path=3D"\DosDevices\c:\soft\colinux\swap_device" enabled=3D"true">
    </block_device>
    <bootparams>ro root=3D/dev/cobd0</bootparams>
    <image path=3D"vmlinux"></image>
    <memory size=3D"128"></memory>
    <network index=3D"0" type=3D"tap" name=3D"TAP" />
    </network>
</colinux>

[root@colinux root]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=3Deth0
BOOTPROTO=3Dstatic
BROADCAST=3D10.255.255.255
IPADDR=3D10.0.0.200
GATEWAY=3D10.0.0.100
NETMASK=3D255.0.0.0
NETWORK=3D10.0.0.0
ONBOOT=3Dyes

[root@colinux root]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:43:4F:4E:45:30
          inet addr:10.0.0.200  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:168 (168.0 b)
          Interrupt:2


[root@colinux root]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use=20
Iface
169.254.0.0     *               255.255.0.0     U     0      0        0 e=
th0
10.0.0.0        *               255.0.0.0       U     0      0        0 e=
th0
127.0.0.0       *               255.0.0.0       U     0      0        0 l=
o
default         10.0.0.100      0.0.0.0         UG    0      0        0 e=
th0


I can't ping 10.0.0.100, or 10.0.0.138


What can I do to treat this problem ?

Regards

Vincent

--=20
Vincent MATHIEU
Universit=E9 Nancy 2 - CRI
Equipe syst=E8me et r=E9seaux
tel : 03 83 39 64 04
coordonn=E9es : http://www.univ-nancy2.fr/ANNU/detail_pres.php?uid=3Dvmat=
hieu=09

Re: [coLinux-users] still cannot get 20040910 to work

[Eric S. J. <es...@ha...>]

Nuno Lucas wrote:
> Eric S. Johansson, dando pulos de alegria, escreveu :
> <...>
> 
>> now it's mostly working right.  upgraded gentoo and with over 120 
>> etc-update files, I just -5ed all the updates and have been cleaning 
>> them up slowly.  Unfortunately, something is wrong with the modules 
>> and since I have no back scroll (or cut and paste) with the console 
>> window (fltk) I can't figure out exactly what's happening since it 
>> isn't logged.
> 
> 
> "dmesg | less" ?

one would think.  Unfortunately, it is not.  So the only way to figure 
out what's wrong will come with a console window that has a few hundred 
lines of scroll back.

I know the developers have more important things on their minds so I can 
wait.  its working well enough for me now.

---eric

Re: [coLinux-users] performance

[Holger K. <hol...@gm...>]

Jaroslaw Fedevych (UALUG schrieb:

> On Fri, Oct 01, 2004 at 03:27:36PM +0200, Holger Krull wrote:
> 
>>No, colinux has its specific network problems. It has serious latency 
>>problems (if you don't use bridgeing just ping host and colinux to see 
>>the difference). Every packet gets a time penalty.

> Hmmm, and, well, where to hunt the problem down? I'm pretty tired
> of connection phases to Samba on coLinux, MySQL from coLinux to 
> host etc... BTW, I'm using bridged networking on Win2k, and 
> coLinux 0.6.1.

First someone had to track down which part of the system is adding the 
latency to every packet.
Winpcap, colinux driver or the colinux kernel itself.
Can't be done without changeing the source and is therefore a little 
complicated.

RE: [coLinux-users] coLinux 0.6.2-pre2

[peter g. <plu...@bi...>]

> The switch is cool. Also not networking but COW is also very usefull.
> Great for the budding admin -- screw up the system just start a new cow
> file ;) instant system restore. Also great for education use colinux to
> teach linux students can each have thier own cow file. And save space on a
> multi user machine. And as you probably know virtual server farmers can
> use cow with the switch to let clients have root. But this would be more
> for coLinux on Linux ;)
>
> chris
colinux was never really built to be a jail
if you can load code into the kernel (through modules for example but there
may be other ways) you have kernel mode access to the host system