colinux-users — coLinux users mailing list

[coLinux-users] Reading ext3 drive in CoLinux on WinXP Pro

[David S. <Dav...@by...>]

I installed CoLinux 0.6.1 under WinXP Pro. Worked like a charm, and boots
extremely fast! Now I'm messing with my config.xml to try to get CoLinux
to mount my 120Gb IDE ext3-formatted drive. This is a separate drive than
the one Windows XP is installed on, and it has a single ext3 partition.
According to the CoLinux docs, CoLinux relies on the host OS to provide
logical access to block devices. But if my host OS (Windows) doesn't
understand ext3, how can it provide logical access? Here's what I've tried
to no avail in config.xml:

  <block_device index="1"
    path="\Device\HarddiskVolume1"
    enabled="true" />

  <block_device index="1"
    path="\Device\Harddisk1\Partition1"
    enabled="true" />

  <block_device index="1"
    path="\Device\Harddisk1"
    enabled="true" />

According to the Windows management console, my drive is "Disk 1", and it
appears as "Healthy (Unknown Partition)".

Can anyone shed any light on how I could get CoLinux to recognize my ext3
drive?

--Dave

Re: [coLinux-users] Networking/XP issues

[Jonathan P. <j-g...@jo...>]

From: "Brendan J Simon" <Bre...@fa...>
> I'm a first time user and have just installed the 0.6.1 release.  I can
> get it to run in the terminal mode but I haven't had any success with
> the networking :(
>
> I have XP and from the docs I've read it seems that Bridged networking
> is the best method as NAT has a few limitations.  Yes/No ???

As I see it, by avoiding NAT (as implemented under XP by
Internet Connection Sharing (ICS)) you give your Linux VM a
more 'first-class' status on your network, with its own IP
address etc. This can be either a good thing or a bad thing,
depending on your network.

> One of the problems I have is that my firewall (and DHCP server) is
> 192.168.0.1.  When I try to share the XP network conenction for other
> users it eventually gives me an error as it tries to assign 192.168.0.1
> for the shared address (or the attaching interface).  Does MS hardcode
> this value in????
> If so then this sucks.  What if one has more than one machine in this
> type of configuration on the local network ???  It doesn't scale.
> Maybe this is only intended for machines that connect direct to an ISP
> (eg. machine with modem, pstn or dsl, etc)???

Yes. ICS is not meant to scale, it's as you guessed a home user solution.
These users don't even want to know what an IP address is.
If you have a firewall and a DHCP server on your network, you want to
use bridged networking anyway, which has none of these limitations.

> Anyway, I can bridge the TAP interface and the 1GB Broadcomm interface
> but the TAP interface always has the red cross on it, even after I've
> started coLinux.

What does your <network> element look like ? Here's what I use for
XP-bridged
networking :

    <network index="0" type="tap" />

(do not use type='bridged' : it is supposed to make coLinux bridge itself
directly
to your real network card (so you don't have to use XP's bridge), but I
couldn't
get it to work)

> So, has anyone got coLinux working with networking on XP using bridged
mode?

Yes, it works fine for me.

> What about if another host has 192.168.0.1 on the network?

If you use XP's bridge and not ICS, there is no need to use 192.168.0.1.
Your
XP box keeps its IP address (actually, it's likely that the DHCP server will
give
it a new IP, since setting up the bridge makes it appear with a new MAC
address),
and the coLinux VM appears on the network with its own MAC address, which
allows the DHCP server to lease it an IP.

Hope this helps,
--Jonathan

RE: [coLinux-users] Networking/XP issues

[Ryan K. <rya...@co...>]

Brendan,

I had a similar problem (I have XP and a router).  Bridging the
connections work very well for me.  I bridged the TAP device and the
network card on my laptop that XP uses for its connection (I actually
have a built in wired Ethernet card and a PCMCIA wireless card - the
wireless card is the one that is actually used, so it is the one to
bridge).  My bridge is set up to be DHCP.  I left the gateway setting in
colinux as 192.168.0.1 so that it actually points to the router.
Internet connection sharing is not enabled.  Everything works well.
Bridging is slightly voodooish to me, so I was surprised at how well it
worked on the first try after I had failed at NAT for a while.

Let me know if you want me to look up any other settings or try to
remember any other details of how it works with my router and XP.

Ryan


-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of Brendan
J Simon
Sent: Wednesday, July 07, 2004 11:05 PM
To: col...@li...
Subject: [coLinux-users] Networking/XP issues

I'm a first time user and have just installed the 0.6.1 release.  I can 
get it to run in the terminal mode but I haven't had any success with 
the networking :(

I have XP and from the docs I've read it seems that Bridged networking 
is the best method as NAT has a few limitations.  Yes/No ???

One of the problems I have is that my firewall (and DHCP server) is 
192.168.0.1.  When I try to share the XP network conenction for other 
users it eventually gives me an error as it tries to assign 192.168.0.1 
for the shared address (or the attaching interface).  Does MS hardcode 
this value in????
If so then this sucks.  What if one has more than one machine in this 
type of configuration on the local network ???  It doesn't scale.
Maybe this is only intended for machines that connect direct to an ISP 
(eg. machine with modem, pstn or dsl, etc)???

Anyway, I can bridge the TAP interface and the 1GB Broadcomm interface 
but the TAP interface always has the red cross on it, even after I've 
started coLinux.

So, has anyone got coLinux working with networking on XP using bridged
mode?
What about if another host has 192.168.0.1 on the network?
Do I need to share my real interface?

Any ideas, suggestions or thoughts muchly appreciated.

Cheers,
Brendan Simon.



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] Networking/XP issues

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

I'm a first time user and have just installed the 0.6.1 release.  I can 
get it to run in the terminal mode but I haven't had any success with 
the networking :(

I have XP and from the docs I've read it seems that Bridged networking 
is the best method as NAT has a few limitations.  Yes/No ???

One of the problems I have is that my firewall (and DHCP server) is 
192.168.0.1.  When I try to share the XP network conenction for other 
users it eventually gives me an error as it tries to assign 192.168.0.1 
for the shared address (or the attaching interface).  Does MS hardcode 
this value in????
If so then this sucks.  What if one has more than one machine in this 
type of configuration on the local network ???  It doesn't scale.
Maybe this is only intended for machines that connect direct to an ISP 
(eg. machine with modem, pstn or dsl, etc)???

Anyway, I can bridge the TAP interface and the 1GB Broadcomm interface 
but the TAP interface always has the red cross on it, even after I've 
started coLinux.

So, has anyone got coLinux working with networking on XP using bridged mode?
What about if another host has 192.168.0.1 on the network?
Do I need to share my real interface?

Any ideas, suggestions or thoughts muchly appreciated.

Cheers,
Brendan Simon.

Re: [coLinux-users] Showstopper in starting colinux

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

You cannot have a .bz file for your root filesystem.  You must unpack it 
first.  Use WinZip or bzip2 in the cygwin insallation.

ie. change

path="\DosDevices\c:\coLinux\Debian-3.0r0.ext3.1gb.bz2"

to

path="\DosDevices\c:\coLinux\Debian-3.0r0.ext3.1gb"


Regards,
Brendan Simon.


col...@li... wrote:

>Message: 3
>Date: Thu, 8 Jul 2004 00:21:50 +0200
>From: Javier Candeira <can...@gm...>
>Reply-To: ja...@ca...
>To: coL...@li...
>Subject: [coLinux-users] Showstopper in starting colinux
>
>My colinux refuses to run, despite apparently doing everything in the
>wiki documentation. A DOS window appears, then goes away.
>
>I am including the trail of my showstopper. My colinux.xml is quite 
>stock, as you can see, and the colinux.bat is also straight out of the 
>howto, except for the ">log.txt" part.
>
>
>cheers,
>--javier.-
>
> >> Contents of colinux.bat:
>
>colinux-daemon.exe -t nt -c default.colinux.xml > log.txt
>
> >> Contents of default.colinux.xml:
>
><?xml version="1.0" encoding="UTF-8"?>
><colinux>
>     <!-- This line needs to point to your root file system.
>         For example change "root_fs" to the name of the Debian image.
>          Inside coLinux it will be /dev/cobd0 -->
>     <block_device index="0" 
>path="\DosDevices\c:\coLinux\Debian-3.0r0.ext3.1gb.bz2"
>     enabled="true" />
>
>     <!-- This line can specify a swap file if you wish, or an additional
>          image file, it will /dev/cobd1. Additional block_devices can
>         be specified in the same manner by increasing the index -->
>
>     <block_device index="1" path="\DosDevices\c:\coLinux\swap_256Mb"
>     enabled="true" />
>
>     <!-- bootparams allows you to pass kernel boot parameters -->
>     <bootparams>root=/dev/cobd0</bootparams>
>
>     <!-- image allows you to specify the kernel to boot -->
>     <image path="vmlinux" />
>
>     <!-- this line allows you to specify the amount of memory available
>          to coLinux -->
>     <memory size="96" />
>
>     <!-- This allows you to modify networking parameters, see the README
>          or website for more information -->
>     <network index="0" type="tap" name="TAP" />
></colinux>
>
>
> >> Contents of log.txt:
>
>conet-daemon: searching TAP device named "TAP"
>conet-daemon: TAP device not found
>Cooperative Linux Daemon, 0.6.2
>Compiled on Tue Jun 22 18:41:44 2004
>
>daemon: loading configuration from default.colinux.xml
>daemon: creating monitor
>colinux: allocated id 0
>co_message_switch: setting callback rule for 7
>co_message_switch: setting callback rule for 2
>co_message_switch: setting callback rule for 6
>co_message_switch: setting callback rule for 3
>co_message_switch: setting callback rule for 0
>co_message_switch: setting callback rule for 4
>colinux: launching net daemons
>daemon: launching daemon for conet0
>executing: colinux-net-daemon -c 0 -n "TAP" -i 0
>daemon: launching console
>executing: colinux-console-nt -a 0
>Linux version 2.6.7-co-0.6.2 (ka...@ca...) (gcc version 3.3.3 
>(Debian 20040422)) #243 Tue Jun 22 18:41:39 IDT 2004
>96MB LOWMEM available.
>On node 0 totalpages: 24576
>   DMA zone: 0 pages, LIFO batch:1
>   Normal zone: 24576 pages, LIFO batch:6
>   HighMem zone: 0 pages, LIFO batch:1
>Built 1 zonelists
>Kernel command line: root=/dev/cobd0
>Initializing CPU#0
>Setting proxy interrupt vectors
>PID hash table entries: 512 (order 9: 4096 bytes)
>Using pit for high-res timesource
>Console: colour CoCON 80x25
>Memory: 94176k/98304k available (1310k kernel code, 0k reserved, 561k 
>data, 88k init, 0k highmem)
>Calibrating delay loop... 244.94 BogoMIPS
>Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
>Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
>Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
>CPU:     After generic identify, caps: 0383f9ff 00000000 00000000 00000000
>CPU:     After vendor identify, caps: 0383f9ff 00000000 00000000 00000000
>CPU: L1 I cache: 16K, L1 D cache: 16K
>CPU: L2 cache: 512K
>CPU:     After all inits, caps: 0383f9ff 00000000 00000000 00000040
>CPU: Intel Mobile Intel(R) Pentium(R) III CPU - M  1333MHz stepping 04
>Enabling fast FPU save and restore... done.
>Enabling unmasked SIMD FPU exception support... done.
>Checking 'hlt' instruction... OK.
>NET: Registered protocol family 16
>devfs: 2004-01-31 Richard Gooch (rg...@at...)
>devfs: boot_options: 0x0
>Initializing Cryptographic API
>RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
>Using anticipatory io scheduler
>cobd: loaded (max 32 devices)
>loop: loaded (max 8 devices)
>conet: loaded (max 16 devices)
>conet0: initialized
>mice: PS/2 mouse device common for all mice
>input: AT Translated Set 2 keyboard on cokbd
>serio: cokbd at irq 1
>NET: Registered protocol family 2
>daemon: module connected: console
>co_message_switch: setting callback rule for 6
>IP: routing cache hash table of 512 buckets, 4Kbytes
>TCP: Hash tables configured (established 8192 bind 16384)
>NET: Registered protocol family 1
>NET: Registered protocol family 17
>VFS: Cannot open root device "cobd0" or cobd0
>Please append a correct "root=" boot option
>Kernel panic: VFS: Unable to mount root fs on cobd0
>  daemon: monitor terminated, reason 3
>switch_message: freed message 3d9a18 (2 to 4)
>daemon: module disconnected: console
>colinux: shutting down
>daemon: daemon cleanup
>SetConsoleWindowInfo() error code 6
>Console: Coopeartive Linux console started
>
>pipe client 0/6: Connecting to daemon...
>pipe client 0/6: Connection established
>Console: Monitor0: Attached
>
>Console: Monitor0: Broken pipe
>
>Console: Monitor0: Detached
>
>  
>

Re: [coLinux-users] Showstopper in starting colinux

[Olivier S. <co...@a-...>]

----- Original Message ----- 
From: "Javier Candeira" <can...@gm...>
To: <coL...@li...>
Sent: Wednesday, July 07, 2004 11:21 PM
Subject: [coLinux-users] Showstopper in starting colinux


> My colinux refuses to run, despite apparently doing everything in the
> wiki documentation. A DOS window appears, then goes away.

I see :

<block_device index="0" 
path="\DosDevices\c:\coLinux\Debian-3.0r0.ext3.1gb.bz2"
enabled="true" />     


uncompress (bunzip2) this Debian-3.0r0.ext3.1gb.bz2 file.


> cheers,
> --javier.-


Regards, O. Souiry

[coLinux-users] Showstopper in starting colinux

[Javier C. <can...@gm...>]

My colinux refuses to run, despite apparently doing everything in the
wiki documentation. A DOS window appears, then goes away.

I am including the trail of my showstopper. My colinux.xml is quite 
stock, as you can see, and the colinux.bat is also straight out of the 
howto, except for the ">log.txt" part.


cheers,
--javier.-

 >> Contents of colinux.bat:

colinux-daemon.exe -t nt -c default.colinux.xml > log.txt

 >> Contents of default.colinux.xml:

<?xml version="1.0" encoding="UTF-8"?>
<colinux>
     <!-- This line needs to point to your root file system.
         For example change "root_fs" to the name of the Debian image.
          Inside coLinux it will be /dev/cobd0 -->
     <block_device index="0" 
path="\DosDevices\c:\coLinux\Debian-3.0r0.ext3.1gb.bz2"
     enabled="true" />

     <!-- This line can specify a swap file if you wish, or an additional
          image file, it will /dev/cobd1. Additional block_devices can
         be specified in the same manner by increasing the index -->

     <block_device index="1" path="\DosDevices\c:\coLinux\swap_256Mb"
     enabled="true" />

     <!-- bootparams allows you to pass kernel boot parameters -->
     <bootparams>root=/dev/cobd0</bootparams>

     <!-- image allows you to specify the kernel to boot -->
     <image path="vmlinux" />

     <!-- this line allows you to specify the amount of memory available
          to coLinux -->
     <memory size="96" />

     <!-- This allows you to modify networking parameters, see the README
          or website for more information -->
     <network index="0" type="tap" name="TAP" />
</colinux>


 >> Contents of log.txt:

conet-daemon: searching TAP device named "TAP"
conet-daemon: TAP device not found
Cooperative Linux Daemon, 0.6.2
Compiled on Tue Jun 22 18:41:44 2004

daemon: loading configuration from default.colinux.xml
daemon: creating monitor
colinux: allocated id 0
co_message_switch: setting callback rule for 7
co_message_switch: setting callback rule for 2
co_message_switch: setting callback rule for 6
co_message_switch: setting callback rule for 3
co_message_switch: setting callback rule for 0
co_message_switch: setting callback rule for 4
colinux: launching net daemons
daemon: launching daemon for conet0
executing: colinux-net-daemon -c 0 -n "TAP" -i 0
daemon: launching console
executing: colinux-console-nt -a 0
Linux version 2.6.7-co-0.6.2 (ka...@ca...) (gcc version 3.3.3 
(Debian 20040422)) #243 Tue Jun 22 18:41:39 IDT 2004
96MB LOWMEM available.
On node 0 totalpages: 24576
   DMA zone: 0 pages, LIFO batch:1
   Normal zone: 24576 pages, LIFO batch:6
   HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: root=/dev/cobd0
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 512 (order 9: 4096 bytes)
Using pit for high-res timesource
Console: colour CoCON 80x25
Memory: 94176k/98304k available (1310k kernel code, 0k reserved, 561k 
data, 88k init, 0k highmem)
Calibrating delay loop... 244.94 BogoMIPS
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: 0383f9ff 00000000 00000000 00000000
CPU:     After vendor identify, caps: 0383f9ff 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU:     After all inits, caps: 0383f9ff 00000000 00000000 00000040
CPU: Intel Mobile Intel(R) Pentium(R) III CPU - M  1333MHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
devfs: 2004-01-31 Richard Gooch (rg...@at...)
devfs: boot_options: 0x0
Initializing Cryptographic API
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Using anticipatory io scheduler
cobd: loaded (max 32 devices)
loop: loaded (max 8 devices)
conet: loaded (max 16 devices)
conet0: initialized
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on cokbd
serio: cokbd at irq 1
NET: Registered protocol family 2
daemon: module connected: console
co_message_switch: setting callback rule for 6
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
VFS: Cannot open root device "cobd0" or cobd0
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on cobd0
  daemon: monitor terminated, reason 3
switch_message: freed message 3d9a18 (2 to 4)
daemon: module disconnected: console
colinux: shutting down
daemon: daemon cleanup
SetConsoleWindowInfo() error code 6
Console: Coopeartive Linux console started

pipe client 0/6: Connecting to daemon...
pipe client 0/6: Connection established
Console: Monitor0: Attached

Console: Monitor0: Broken pipe

Console: Monitor0: Detached

RE: [coLinux-users] Limited number of Linux can run coLinux

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

there should be no need of any modeules for networking in colinux

remember colinux does not directly access real hardware to put your system
on the network you need to look at
http://colinux.org/wiki/index.php/coLinuxNetworking

snapshots are at http://www.colinux.org/snapshots

the modules for use with colinux are supplied as a tarball which can be
transferred into the linux install and extracted once networking is up but
this is only needed for advanced stuff like iptables

there is nothing distro specific about colinux and there is info elsewhere
in the wiki about trying to make a linux install work nicely both natively
and in colinux

sadly linux has no real concept of hardware profiles which can make such
things a little awkward

the 2.6.x based colinux (current snapshots not yet any releases) should boot
any of the existing images. i belive there are some issues with distros that
use devfs though but this is all in the wiki

if you want modules support with a 2.6.x based colinux you will need
module-init-tools installed how easilly availible this will be depends on
the distro

-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of Sarah
Tanembaum
Sent: 07 July 2004 22:10
To: col...@li...
Cc: ope...@Op...
Subject: [coLinux-users] Limited number of Linux can run coLinux


It seems that only a few limited number of linux distribution can run
coLinux - those who came with the coLinux distribution. Although linux
kernel 2.4 are not supported now under coLinux(so they can concentrate for
2.6 kernel), there are a limited number of information on how to get it
working with the 2.6 kernel, e.g. Fedora 2.

Is there step by step to build coLinux VM on Windows, as well as how to
convert ANY linux distribution into coLinux compatible? Is there any latest
patch to apply to 2.6.7 kernel?

I somehow manage to convert my Linux partition into coLinux VM(I guess..)
but there are so many errors before it gives me the login promt. But
eventually, I get the login promt and able to log in.

At this point, since I do not have the 2.6.7-co-0.6.2, my network card is
not working, and some others modules as well. How do I compile those in
/lib/modules/2.6.7-co-0.6.2? Should I build it within coLinux or should I
build it in native?

Hellllllllllllllllpppp! Thanks

PS: Is there a site where I can download the snapshot of the latest coLinux
source/binaries? Thanks





-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004

[coLinux-users] Limited number of Linux can run coLinux

[Sarah T. <sar...@ya...>]

It seems that only a few limited number of linux distribution can run
coLinux - those who came with the coLinux distribution. Although linux
kernel 2.4 are not supported now under coLinux(so they can concentrate for
2.6 kernel), there are a limited number of information on how to get it
working with the 2.6 kernel, e.g. Fedora 2.

Is there step by step to build coLinux VM on Windows, as well as how to
convert ANY linux distribution into coLinux compatible? Is there any latest
patch to apply to 2.6.7 kernel?

I somehow manage to convert my Linux partition into coLinux VM(I guess..)
but there are so many errors before it gives me the login promt. But
eventually, I get the login promt and able to log in.

At this point, since I do not have the 2.6.7-co-0.6.2, my network card is
not working, and some others modules as well. How do I compile those in
/lib/modules/2.6.7-co-0.6.2? Should I build it within coLinux or should I
build it in native?

Hellllllllllllllllpppp! Thanks

PS: Is there a site where I can download the snapshot of the latest coLinux
source/binaries? Thanks

Re: [coLinux-users] Fw: From Argentina - Network problem.

[Robert C. <rw...@al...>]

Hola Javier,

On Sunday, Jul 4, 2004, at 20:58 US/Central, Javier Osvaldo Ch=E9rcoles=20=

wrote:
> Reason why I could read and understand if coLinux is connected with=20
> Windows 2000, when doing ping of anyone of the two sides are not=20
> tendrian that to lose the messages.=A0 I have all equal one to which=20=

> they enunciate notes, but nothing.=A0 That it can be, is algun example=20=

> of like connecting to me.

Which colinux binaries are you using?
Which Debian root filesystem are you using?

For my notes on a slightly older colinux version with a Debian root=20
filesystem on Windows 2000, see:

   http://cwelug.org/cgi-bin/wiki.cgi?CoLinux#v07

Buenos suerte,
- Robert

Re: [coLinux-users] Re: Recommended procedure for upgrading to latest snapshot

[Milind K. <mb...@ya...>]

Yeah, that's what I did and reused my (modified) xml
config file after editing the kernel information.
I also found that due to the reinstallation of the TAP
driver, WinXP reset the name of the Network interface,
so I had to rename that to match what I had in the
config file and add the TAP interface to the ICS list
of the WinXP LAN interface.

--- Sam Liddicott <sa...@li...> wrote:
> Milind Kamble wrote:
> > I too use debian (testing). So I guess I do not
> have
> > to be concerned with changing my fstab.
> > 
> > So can anyone using debian inform me how exactly
> they
> > upgraded to the 20040622 snapshot?
> 
> If you ont want to save any files on your FS image,
> just de-install, 
> install the update and then re-edit the xml config
> file.
> 
> Thats what I do
> 
> Sam
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings &
> Training.
> Attend Black Hat Briefings & Training, Las Vegas
> July 24-29 - 
> digital self defense, top technical experts, no
> vendor pitches, 
> unmatched networking opportunities. Visit
> www.blackhat.com
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
>
https://lists.sourceforge.net/lists/listinfo/colinux-users
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail

[coLinux-users] Slackware 10

[Adam R. <ada...@ax...>]

does anyone have installed slackware 10 (it's based on 2.4 kernel) ?

Adam

Re: [coLinux-users] Converting Fedora Distribution to coLinux

[A. A. A. <alp...@tt...>]

On Tue, Jul 06, 2004 at 01:50:19AM -0400, Sarah Tanembaum wrote:
> Is there a step-by-step guide in converting or building Redhat Fedora 2
> distribution to coLinux?
> 

Latest stable (0.6.1) coLinux is based on a 2.4 kernel (I think it will be 
2.6 based in the next release).
So, you first have to make sure FC2 supports 2.4 kernels before thinking 
about that (and a fedora group is the right place to ask for this). 
If FC2 is solely based on 2.6 kernels, then you have to wait for 0.6.2

I'm not sure if it would be possible to upgrade FC1 to FC2 by yum, or 
up2date, or checking individual rpms out of FC2 repository. You might get a 
partial upgrade as long as you stay away from kernel upgrade, but I'm not 
sure. A fedora group is also the right place to ask for it.


> Also, I'm looking for a way to make my linux installation(root- /dev/hda3
> swap-/dev/hda6) runs under coLinux?
> What need to be done first on the distribution and then on the coLinux part.


There's a lot of info about that on the wiki pages.

Re: [coLinux-users] I still need help, but please ignore my previous message.

[A. A. A. <alp...@tt...>]

Ryan,
Your situation has really not much to do with coLinux,
the issue has now reduced to that of accessing a vnc server running on a 
debian linux (you're using debian image, right?) from a windows machine.
You'd be much better off in a debian and/or a vnc related group, and you 
don't even have to tell them it's on coLinux ;-)


On Mon, Jul 05, 2004 at 04:31:41PM -0600, Ryan Krauss wrote:
> After starting the vncserver in coLinux, I also tried launching konsole
> and kcalc to see if my problem was that there aren't any gui
> applications running.  When I type konsole at the command prompt, I get
> the message: konsole: cannot connect to X server.
>  
> Ryan
>  

RE: [coLinux-users] I still need help, but please ignore my previous message.

[Leeuw v. d. T. <tim...@nl...>]

Hi Ryan,
=20
For that, you probably need to find out first on what 'DISPLAY', as it =
is called, the vncserver is running. This is something that I don't =
know, because I don't use it myself. It depends on how you start the =
vncserver as well; what is the command-line that you use for it?
=20
If you find out what is the proper value for DISPLAY, then you have to =
set the variable for all programs to use:
=20
export DISPLAY=3D...
=20
and then start konsole.
=20
From another user on the mailing-list, Robert Citek, I found the =
following URL:
 <http://cwelug.org/cgi-bin/wiki.cgi?CoLinux#v08> =
http://cwelug.org/cgi-bin/wiki.cgi?CoLinux#v08
Search for the topic 'problems with vncserver'.
Success,
--Tim van der Leeuw
=20
-----Original Message-----
From: col...@li... =
[mailto:col...@li...]On Behalf Of Ryan =
Krauss
Sent: dinsdag 6 juli 2004 0:32
To: col...@li...
Subject: RE: [coLinux-users] I still need help, but please ignore my =
previous message.


After starting the vncserver in coLinux, I also tried launching konsole =
and kcalc to see if my problem was that there aren't any gui =
applications running.  When I type konsole at the command prompt, I get =
the message: konsole: cannot connect to X server.
=20
Ryan
=20
-----Original Message-----
From: col...@li... =
[mailto:col...@li...] On Behalf Of Ryan =
Krauss
Sent: Monday, July 05, 2004 9:29 AM
To: col...@li...
Subject: [coLinux-users] I still need help, but please ignore my =
previous message.
=20
Thanks to many of you who responded to my last post.  It turns out that =
I searched the archives last night and stumbled onto my mistake.  I had =
forgotten to modify the .xml file when I reinstalled.  I tried to post a =
retraction and my new problem last night but accidentally sent it to the =
list admin instead of the list.  Setting up a network bridge was key and =
worked well.
=20
My new problem is that when I launch the vncserver, I only see a gray =
cross-hatched background in windows.  I am a linux newbie, so I don't =
know if there should be more, if I have launched anything that should =
show up on the graphical screen or what.  Can someone please help me or =
point me to a how-to page for my next steps.  I did try and create an =
xstartup script that is in the /root/.vnc directory that consists of two =
lines:
#!/bin/sh=20
startkde &
=20
Thanks for any help you can provide.
=20
Ryan
=20
-----Original Message-----
From: col...@li... [mailto: ] On Behalf Of =
Ryan Krauss
Sent: Sunday, July 04, 2004 11:22 PM
To: col...@li...
Subject: [coLinux-users] Help: colinux starts and immediately shuts down
=20
Please help me.
=20
I was trying to follow the instructions here: =
http://www.colinux.org/wiki/index.php/GettingStartedLong to get started. =
 I have been having problems getting the networking to work and had =
tried it a couple of times.  I decided to start over and uninstall =
everything.  Now when I double-click on the colinux.bat file, a command =
window pops up and seems to scroll through the usual stuff, but then it =
immediately shuts down.  Can you help me trouble shoot/solve this =
problem please.
=20
I am running Windows XP Pro.  My networking situation is slightly =
complicated.  We have a router that needs to be 192.168.0.1, so I don't =
think I can use that address for the colinux TAP connector.  I am trying =
to use the 1gb Debian file (I also tried the GenToo deluxe).
=20
I don't know what information to provide, so please feel free to send me =
additional questions.
=20
Ryan Krauss

RE: [coLinux-users] I still need help, but please ignore my previous message.

[Ryan K. <rya...@co...>]

After starting the vncserver in coLinux, I also tried launching konsole
and kcalc to see if my problem was that there aren't any gui
applications running.  When I type konsole at the command prompt, I get
the message: konsole: cannot connect to X server.
 
Ryan
 
-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of Ryan
Krauss
Sent: Monday, July 05, 2004 9:29 AM
To: col...@li...
Subject: [coLinux-users] I still need help, but please ignore my
previous message.
 
Thanks to many of you who responded to my last post.  It turns out that
I searched the archives last night and stumbled onto my mistake.  I had
forgotten to modify the .xml file when I reinstalled.  I tried to post a
retraction and my new problem last night but accidentally sent it to the
list admin instead of the list.  Setting up a network bridge was key and
worked well.
 
My new problem is that when I launch the vncserver, I only see a gray
cross-hatched background in windows.  I am a linux newbie, so I don't
know if there should be more, if I have launched anything that should
show up on the graphical screen or what.  Can someone please help me or
point me to a how-to page for my next steps.  I did try and create an
xstartup script that is in the /root/.vnc directory that consists of two
lines:
#!/bin/sh 
startkde &
 
Thanks for any help you can provide.
 
Ryan
 
-----Original Message-----
From: col...@li... [mailto: ] On Behalf Of
Ryan Krauss
Sent: Sunday, July 04, 2004 11:22 PM
To: col...@li...
Subject: [coLinux-users] Help: colinux starts and immediately shuts down
 
Please help me.
 
I was trying to follow the instructions here:
http://www.colinux.org/wiki/index.php/GettingStartedLong to get started.
I have been having problems getting the networking to work and had tried
it a couple of times.  I decided to start over and uninstall everything.
Now when I double-click on the colinux.bat file, a command window pops
up and seems to scroll through the usual stuff, but then it immediately
shuts down.  Can you help me trouble shoot/solve this problem please.
 
I am running Windows XP Pro.  My networking situation is slightly
complicated.  We have a router that needs to be 192.168.0.1, so I don't
think I can use that address for the colinux TAP connector.  I am trying
to use the 1gb Debian file (I also tried the GenToo deluxe).
 
I don't know what information to provide, so please feel free to send me
additional questions.
 
Ryan Krauss

[coLinux-users] I still need help, but please ignore my previous message.

[Ryan K. <rya...@co...>]

Thanks to many of you who responded to my last post.  It turns out that
I searched the archives last night and stumbled onto my mistake.  I had
forgotten to modify the .xml file when I reinstalled.  I tried to post a
retraction and my new problem last night but accidentally sent it to the
list admin instead of the list.  Setting up a network bridge was key and
worked well.
 
My new problem is that when I launch the vncserver, I only see a gray
cross-hatched background in windows.  I am a linux newbie, so I don't
know if there should be more, if I have launched anything that should
show up on the graphical screen or what.  Can someone please help me or
point me to a how-to page for my next steps.  I did try and create an
xstartup script that is in the /root/.vnc directory that consists of two
lines:
#!/bin/sh 
startkde &
 
Thanks for any help you can provide.
 
Ryan
 
-----Original Message-----
From: col...@li... [mailto: ] On Behalf Of
Ryan Krauss
Sent: Sunday, July 04, 2004 11:22 PM
To: col...@li...
Subject: [coLinux-users] Help: colinux starts and immediately shuts down
 
Please help me.
 
I was trying to follow the instructions here:
http://www.colinux.org/wiki/index.php/GettingStartedLong to get started.
I have been having problems getting the networking to work and had tried
it a couple of times.  I decided to start over and uninstall everything.
Now when I double-click on the colinux.bat file, a command window pops
up and seems to scroll through the usual stuff, but then it immediately
shuts down.  Can you help me trouble shoot/solve this problem please.
 
I am running Windows XP Pro.  My networking situation is slightly
complicated.  We have a router that needs to be 192.168.0.1, so I don't
think I can use that address for the colinux TAP connector.  I am trying
to use the 1gb Debian file (I also tried the GenToo deluxe).
 
I don't know what information to provide, so please feel free to send me
additional questions.
 
Ryan Krauss

RE: [coLinux-users] Help: colinux starts and immediately shuts down

[Leeuw v. d. T. <tim...@nl...>]

When 'debugging' a batchfile, or trouble-shootings programs started from =
a batch-file, always put a 'pause' command at the end of the batch-file. =
It helps to figure out what the error is that the program gives.

--Tim

-----Original Message-----
From: Tomas Fasth [mailto:to...@eu...]
Sent: maandag 5 juli 2004 13:56
To: Leeuw van der, Tim
Cc: Ryan Krauss; col...@li...
Subject: Re: [coLinux-users] Help: colinux starts and immediately shuts
down


Leeuw van der, Tim wrote:

>Hi,
>
>either bridged networking, or a local proxy. Look in the Wiki for =
instructions on how to setup a proxy such as FreeProxy. It's about the =
only way that I managed to get it working.
>
>But of course, that won't help you yet getting this running at all! So =
far, if it shuts down immediately, I'm afraid I can't really help you =
yet either :-(
> =20
>
They changed the behavior in colinux 0.6.1 regardning the configuration=20
file name.
I created a "colinux-daemon-rc" BAT file containing one line:
colinux-daemon -c default.colinux.xml

// Tomas

Re: [coLinux-users] Help: colinux starts and immediately shuts down

[Tomas F. <to...@eu...>]

Leeuw van der, Tim wrote:

>Hi,
>
>either bridged networking, or a local proxy. Look in the Wiki for instructions on how to setup a proxy such as FreeProxy. It's about the only way that I managed to get it working.
>
>But of course, that won't help you yet getting this running at all! So far, if it shuts down immediately, I'm afraid I can't really help you yet either :-(
>  
>
They changed the behavior in colinux 0.6.1 regardning the configuration 
file name.
I created a "colinux-daemon-rc" BAT file containing one line:
colinux-daemon -c default.colinux.xml

// Tomas

[coLinux-users] what about Fedora Core II ?

[Adam R. <ada...@ax...>]

hello,
how to setup FC2 on coLinux???
or where i can found an image for coLinux of FC2?
(or Slackware 10)?


regards,
Adam

Re: [coLinux-users] Re: Networking problems (0.6.1)

[Tomas F. <to...@eu...>]

Hello
I'm sorry for the double posting. I had a problem with my ISP blocking 
port 25 for outgoing smtp. In the process of finding a workaround I seem 
to have successfully posted the same reply twice. Again, my apologies.
// Tomas

RE: [coLinux-users] Help: colinux starts and immediately shuts down

[Leeuw v. d. T. <tim...@nl...>]

SGksDQoNCmVpdGhlciBicmlkZ2VkIG5ldHdvcmtpbmcsIG9yIGEgbG9jYWwgcHJveHkuIExvb2sg
aW4gdGhlIFdpa2kgZm9yIGluc3RydWN0aW9ucyBvbiBob3cgdG8gc2V0dXAgYSBwcm94eSBzdWNo
IGFzIEZyZWVQcm94eS4gSXQncyBhYm91dCB0aGUgb25seSB3YXkgdGhhdCBJIG1hbmFnZWQgdG8g
Z2V0IGl0IHdvcmtpbmcuDQoNCkJ1dCBvZiBjb3Vyc2UsIHRoYXQgd29uJ3QgaGVscCB5b3UgeWV0
IGdldHRpbmcgdGhpcyBydW5uaW5nIGF0IGFsbCEgU28gZmFyLCBpZiBpdCBzaHV0cyBkb3duIGlt
bWVkaWF0ZWx5LCBJJ20gYWZyYWlkIEkgY2FuJ3QgcmVhbGx5IGhlbHAgeW91IHlldCBlaXRoZXIg
Oi0oDQoNCi0tVGltDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBjb2xpbnV4
LXVzZXJzLWFkbWluQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KW21haWx0bzpjb2xpbnV4LXVzZXJz
LWFkbWluQGxpc3RzLnNvdXJjZWZvcmdlLm5ldF1PbiBCZWhhbGYgT2YgTWFyaXVzeg0KTWFzbG93
c2tpDQpTZW50OiBtYWFuZGFnIDUganVsaSAyMDA0IDEwOjAzDQpUbzogUnlhbiBLcmF1c3MNCkNj
OiBjb2xpbnV4LXVzZXJzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KU3ViamVjdDogUmU6IFtjb0xp
bnV4LXVzZXJzXSBIZWxwOiBjb2xpbnV4IHN0YXJ0cyBhbmQgaW1tZWRpYXRlbHkgc2h1dHMNCmRv
d24NCg0KDQpSeWFuIEtyYXVzcyB3cm90ZToNCg0KPiBQbGVhc2UgaGVscCBtZS4NCj4NCj4gIA0K
Pg0KWy4uLl0NCg0KPiBJIGFtIHJ1bm5pbmcgV2luZG93cyBYUCBQcm8uICBNeSBuZXR3b3JraW5n
IHNpdHVhdGlvbiBpcyBzbGlnaHRseSANCj4gY29tcGxpY2F0ZWQuICBXZSBoYXZlIGEgcm91dGVy
IHRoYXQgbmVlZHMgdG8gYmUgMTkyLjE2OC4wLjEsIHNvIEkgDQo+IGRvbuKAmXQgdGhpbmsgSSBj
YW4gdXNlIHRoYXQgYWRkcmVzcyBmb3IgdGhlIGNvbGludXggVEFQIGNvbm5lY3Rvci4gIEkgDQo+
IGFtIHRyeWluZyB0byB1c2UgdGhlIDFnYiBEZWJpYW4gZmlsZSAoSSBhbHNvIHRyaWVkIHRoZSBH
ZW5Ub28gZGVsdXhlKS4NCj4NCkluIHRoaXMgY2FzZSB5b3Ugc2hvdWxkIHVzZSB0aGUgYnJpZ2Vk
IG5ldHdvcmtpbmcuDQpJIGhhZCBzaW1pbGFyIHNpdHVhdGlvbiAoYnV0IHdpdGggV2luZG93cyAy
MDAwKSAtLSBhIHByaXZhdGUgbmV0d29yayBvZiANCjE5Mi4xNjguMC54Lg0KDQoNCg0KLS0gDQpQ
b3pkcm9ma2EsDQpNYXJpdXN6IE1hc2xvd3NraQ0KDQoiSGUgdXNlZCB0byBoYXZlIGhvYmJpZXMs
IGJ1dCBoZSBpcyBub3cgYSBwcm91ZCBmYXRoZXIgaW5zdGVhZC4iICAtLSBPcmVuIEV0emlvbmkN
Cg0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0NClRoaXMgU0YuTmV0IGVtYWlsIHNwb25zb3JlZCBieSBCbGFjayBIYXQgQnJpZWZpbmdz
ICYgVHJhaW5pbmcuDQpBdHRlbmQgQmxhY2sgSGF0IEJyaWVmaW5ncyAmIFRyYWluaW5nLCBMYXMg
VmVnYXMgSnVseSAyNC0yOSAtIA0KZGlnaXRhbCBzZWxmIGRlZmVuc2UsIHRvcCB0ZWNobmljYWwg
ZXhwZXJ0cywgbm8gdmVuZG9yIHBpdGNoZXMsIA0KdW5tYXRjaGVkIG5ldHdvcmtpbmcgb3Bwb3J0
dW5pdGllcy4gVmlzaXQgd3d3LmJsYWNraGF0LmNvbQ0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCmNvTGludXgtdXNlcnMgbWFpbGluZyBsaXN0DQpjb0xp
bnV4LXVzZXJzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KaHR0cHM6Ly9saXN0cy5zb3VyY2Vmb3Jn
ZS5uZXQvbGlzdHMvbGlzdGluZm8vY29saW51eC11c2Vycw0K

Re: [coLinux-users] Re: Networking problems (0.6.1)

[Tomas F. <to...@eu...>]

Ah, almost forgot, I also had to disable hardware checksumming for the 
physical network interface to get everything to work in harmony. I think 
that is something that will be fixed in the next release. // Tomas

Tomas Fasth wrote:

> Andrew Lawson wrote:
>
>> Hello I've been giving colinux 0.6.1 a try but am having no luck with
>>  the networking. I'll explain the setup;
>
>
> Hello
> This is what I did; Host system is XP Professional with SP 1 and latest
> patches installed.
>
> - Create a network bridge between the local network adapter and the
> virtual TAP-Win32 adapter. You can do this by selecting both adapters in
> the "network connections" window, and choose "create bridge" in the
> right click menu.
> - Change the network definition in the default.colinux.xml file:
> <network index="0" type="bridged" name="Microsoft MAC Bridge Virtual 
> NIC" />
>
> -- Tomas
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital 
> self defense, top technical experts, no vendor pitches, unmatched 
> networking opportunities. Visit www.blackhat.com
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] Help: colinux starts and immediately shuts down

[A. A. A. <alp...@tt...>]

On Sun, Jul 04, 2004 at 11:22:13PM -0600, Ryan Krauss wrote:
> Please help me.
>  
> I was trying to follow the instructions here:
> http://www.colinux.org/wiki/index.php/GettingStartedLong to get started.
> I have been having problems getting the networking to work and had tried
> it a couple of times.  I decided to start over and uninstall everything.
> Now when I double-click on the colinux.bat file, a command window pops
> up and seems to scroll through the usual stuff, but then it immediately
> shuts down.  Can you help me trouble shoot/solve this problem please.
>  

Forget the .bat file at this moment.
Now, open a command prompt (y'know how to do that, right?), cd to where 
colinux is installed (y'know where it's installed, right?), and enter
the following command:
colinux-daemon -c default.colinux.xml

tell us what you've seen.


> I am running Windows XP Pro.  My networking situation is slightly
> complicated.  We have a router that needs to be 192.168.0.1, so I don't
> think I can use that address for the colinux TAP connector.  I am trying
> to use the 1gb Debian file (I also tried the GenToo deluxe).
>  

You can utilize another private address range, say, 10.x.x.x or you can
create subnets with different netmasks. Alternatives are ample, and these
are all elementary TCP/IP stuff, has nothing to do with being specific to
coLinux.

Re: [coLinux-users] Networking problems (0.6.1)

[A. A. A. <alp...@tt...>]

On Fri, Jul 02, 2004 at 04:19:04PM +0200, Andrew Lawson wrote:
> Hello
>     I've been giving colinux 0.6.1 a try but am having no luck with
> the networking. I'll explain the setup;
> 
> Colinux installed the tap driver automatically, it's address is
> 192.168.0.1 as expected. The only changes I've made to this setup on
> this interface is to insert the same router and dns addresses as per my
> normal nic.
> 

And, why did you do that? Is that how ICS is described in windows help?
Or, did the wiki misguide you?