colinux-users — coLinux users mailing list

Re: [coLinux-users] Can anybody read me??

[Tim H. <ti...@br...>]

steelgunner wrote:
> Hello,
>
> How to start many co-linux  instances in the same computer??
>

In short, just read the instructions, but try looking at the output from
"colinux-daemon.exe -h"
and notice the way you can use different config files


>
>

Re: [coLinux-users] Many Colinux instances

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

On Tue, May 18, 2004 at 03:59:35PM -0400, Carlos Paz wrote:
> 
> I need to setup many Linux instances, but I can't, the next errors happens:
> 
>  
> 
> C:\coLinux2>colinux-daemon2.exe
> 

Changing the executables's name is futile.

You have to specify different config files with -c option for each instance.

You also need to create a TAP device for each by following
Settings->Control Panel->Add Hardware->Blah blah...
and configure them accordingly. Note that, you must consider MAC address 
variability if you bridge them all.

Is not there a wiki page about these already?

Re: [coLinux-users] coLinux + Knoppix

[Aaron S. <as...@in...>]

I got knoppix to run on top of Win2K using coLinux (mentioned in an
earlier thread).  It took a little work.
Currently it requires 2.5 GB of disk space on windows, and a spare
partition on a second computer to get it running

Here is a rough sketch of how to do it for those interested:
1) On a second computer, boot knoppix off of the cd
2) create a 2.5 GB partition, and mkfs it (I chose ext3) and mount it up
as /mnt/newdisk
3) 'cp -a /KOPPIX/* /mnt/newdisk'
3.1) replace /mnt/newdisk/etc/init.d/xsession with

#!/bin/sh

. /etc/sysconfig/knoppix

if [ ! -d /home/knoppix ]; then
  mkdir /home/knoppix
  chown knoppix:knoppix /home/knoppix
fi

    echo "startdke" > /home/knoppix/.xinitrc

# clean up any old lock files
rm -f /home/knoppix/.vnc/*.pid
rm -f /tmp/.X0-lock
rm -fr /tmp/.X11-unix

# start up kde
su - -c "vncserver -geometry 1024x768 -depth 16 :0" knoppix

3.2) create an /mnt/newdisk/etc/fstab

/dev/cobd0 / ext3 defaults 1 1
none /proc proc defaults 0 0

3.3) create some missing devices

mknod /mnt/newdisk/dev/cobd0 b 117 0
mknod /mnt/newdisk/dev/cobd1 b 117 1
mknod /mnt/newdisk/dev/cobd2 b 117 2
mknod /mnt/newdisk/dev/cobd3 b 117 3
mknod /mnt/newdisk/dev/cobd4 b 117 4
mknod /mnt/newdisk/dev/cobd5 b 117 5
mknod /mnt/newdisk/dev/cobd6 b 117 6
mknod /mnt/newdisk/dev/cobd7 b 117 7


3.4) and then unmount /mnt/newdisk
4) On the target computer, install coLinux 0.6.0 and netcat and vncviewer
5) using netcat (nc) on knoppix and netcat on the target computer (win2k),
copy the raw filesystem over as a single 2.5 GB file.

6) modify your default.colinux.xml to look like this, adjusting your path
& ethernet card name as necessary

<?xml version="1.0" encoding="UTF-8"?>
<colinux>
    <block_device index="0" path="\DosDevices\c:\colinux\knoppix_ext3"
enabled="true"></block_device>
    <bootparams>root=/dev/cobd0 lang=us BOOT_IMAGE=knoppix</bootparams>
    <image path="vmlinux"></image>
    <memory size="128"></memory>
    <network index="0" type="bridged" name="3Com 10/100 Mini PCI Ethernet
Adapter"></network>
</colinux>

7) start up colinux-daemon.exe

8) knoppix will come up and start.  It mounts up the root filesystem and
also DHCP's an IP address (make sure you have a DHCP server nearby)

9) After a minute or two, fire up 'vncviewer' with the IP address of
knoppix.  (you might have to do an 'ifconfig -a' on the console to
determine the ip).  It runs really nice in full screen mode

Notes:
*) If you don't want to use the 'bridged' network, you can make knoppix
only talk with windows, the network line should read as below.  Also then
hard code your IP address in windows on the 'tap' ethernet as 192.168.0.1
and hardcode knoppix as 192.168.0.40.  Make sure you kill or disable
'pump' in knoppix so that it does not keep trying to dhcp.

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

*) If we rebuild the coLinux kernel and include the 'cloop.o' driver then
in theory you can point your first block device to a modified ramdisk
(like the boot.img that comes on knoppix) and then point your second block
device to \DosDevices\D:\knoppix\KNOPPIX.  This allows you to save 2.5GB
of disk space.  Then you can use the knoppix method of persistant home
directories and configuration files.  (I have not tried this, please let
me know your experience if you do)  Also, once a modified kernel has been
built, the first several steps including the second computer are skipped.

Re: [coLinux-users] Is USB supported?

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

Sean Covel wrote:

> Robert,
> 
> I finally had a chance to look at this again.  The line you added to 
> your xml file seems to be missing the beginning.
> 
> dmdiage.exe reported my usb device as K:\Device\HardDisk1\DP(1)0-0+3
> 
> I added:
> 
> <block_device index="2" enabled="true" />
> 

where is the path?

you need the "windows-ish" name, and the result like will be something 
like this (not exactly this, I suspect):

<block_device index="2" path="\Device\Harddisk1\DP(1)0-0+3" enabled="true" />


> I then started coLinux and did the following:
> 
> mkdir /mnt/usb
> mount -t vfat /dev/cobd2 /mnt/usb
> 
> I got the following error:
> 
> mount: /dev/cobd2:  Can't read Superblock
> 
> Its formatted Fat32.
> 
> Any thoughts?
> 
> Thanks,
> 
> Sean
> 
> Robert Citek wrote:
> 
>>
>> Hello Sean,
>>
>> On Monday, May 17, 2004, at 19:00 US/Central, Sean Covel wrote:
>>
>>> I'd appreciate any information you have.  I'm on Win2k, coLinux 
>>> 20040509, and the Gentoo "delux" image.
>>
>>
>>
>> I can't find my notes anywhere.  Off the top of my head, you need to 
>> get the tool called dmdiag.exe.  IIRC, you get this from Microsoft but 
>> google to be sure.  Install it and run it.  Then insert your USB stick 
>> and run it again.
>>
>> Here's an example when I use my USB stick.  Here's a very abbreviated 
>> portions of dmdiag.exe output before:
>>
>> ---------- Drive letter to device name, QueryDosDevice() ----------
>>
>>            D: \Device\CdRom0
>>            A: \Device\Floppy0
>>            C: \Device\HarddiskVolume1
>>
>> Here's a very abbreviated portions of dmdiag.exe output after:
>>
>> ---------- Drive letter to device name, QueryDosDevice() ----------
>>
>>            D: \Device\CdRom0
>>            E: \Device\Harddisk1\DP(1)0-0+3
>>            A: \Device\Floppy0
>>            C: \Device\HarddiskVolume1
>>
>> Notice the new device E:\.  That's my USB stick.  I then add this line 
>> to my defaults.colinux.xml:
>>
>> enabled="true" />
>>
>> The index number will change depending on how many devices you already 
>> have defined and will be accessible within colinux as /dev/cobd2  (as 
>> in _co_linux _b_lock _d_evice 2.  After I start colinux, I can mount 
>> the usb stick like so:
>>
>> # mkdir /mnt/usb
>> # mount /dev/cobd2 /mnt/usb
>> UMSDOS 0.86k (compatibility level 0.4, fast msdos)
>> # dir /mnt/usb/
>> total 2620
>> drwxr--r--    3 root     root        16896 Jan  1  1970 .
>> drwxr-xr-x    5 root     root         4096 May 18 00:32 ..
>>  ...
>> # umount /mnt/usb
>>
>> This is a simple way for Windows to communicate with coLinux.  
>> However, only one system can be accessing the device at a time.  So, 
>> you will need to unmount before Windows can see it and all Windows or 
>> files that are accessing the device must be closed on the Windows side 
>> before you can mount it again.
>>
>> Hope this helps.  The above is tested on a Win2K machine running 
>> coLinux 20040509 with the Debian image.  If you get USB to work for 
>> you, I'd like to encourage you to write up your experiences and post 
>> them on the wiki, especially if you are using a different host OS, 
>> snapshot, or image.
>>
>> Regards,
>> - Robert
>>
>>
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 

[coLinux-users] Can anybody read me??

[steelgunner <ste...@in...>]

Hello,

How to start many co-linux  instances in the same computer??

Re: [coLinux-users] Is USB supported?

[Sean C. <sea...@co...>]

Robert,

I finally had a chance to look at this again.  The line you added to 
your xml file seems to be missing the beginning.

dmdiage.exe reported my usb device as K:\Device\HardDisk1\DP(1)0-0+3

I added:

<block_device index="2" enabled="true" />

I then started coLinux and did the following:

mkdir /mnt/usb
mount -t vfat /dev/cobd2 /mnt/usb

I got the following error:

mount: /dev/cobd2:  Can't read Superblock

Its formatted Fat32.

Any thoughts?

Thanks,

Sean

Robert Citek wrote:
> 
> Hello Sean,
> 
> On Monday, May 17, 2004, at 19:00 US/Central, Sean Covel wrote:
> 
>> I'd appreciate any information you have.  I'm on Win2k, coLinux 
>> 20040509, and the Gentoo "delux" image.
> 
> 
> I can't find my notes anywhere.  Off the top of my head, you need to get 
> the tool called dmdiag.exe.  IIRC, you get this from Microsoft but 
> google to be sure.  Install it and run it.  Then insert your USB stick 
> and run it again.
> 
> Here's an example when I use my USB stick.  Here's a very abbreviated 
> portions of dmdiag.exe output before:
> 
> ---------- Drive letter to device name, QueryDosDevice() ----------
> 
>            D: \Device\CdRom0
>            A: \Device\Floppy0
>            C: \Device\HarddiskVolume1
> 
> Here's a very abbreviated portions of dmdiag.exe output after:
> 
> ---------- Drive letter to device name, QueryDosDevice() ----------
> 
>            D: \Device\CdRom0
>            E: \Device\Harddisk1\DP(1)0-0+3
>            A: \Device\Floppy0
>            C: \Device\HarddiskVolume1
> 
> Notice the new device E:\.  That's my USB stick.  I then add this line 
> to my defaults.colinux.xml:
> 
> enabled="true" />
> 
> The index number will change depending on how many devices you already 
> have defined and will be accessible within colinux as /dev/cobd2  (as in 
> _co_linux _b_lock _d_evice 2.  After I start colinux, I can mount the 
> usb stick like so:
> 
> # mkdir /mnt/usb
> # mount /dev/cobd2 /mnt/usb
> UMSDOS 0.86k (compatibility level 0.4, fast msdos)
> # dir /mnt/usb/
> total 2620
> drwxr--r--    3 root     root        16896 Jan  1  1970 .
> drwxr-xr-x    5 root     root         4096 May 18 00:32 ..
>  ...
> # umount /mnt/usb
> 
> This is a simple way for Windows to communicate with coLinux.  However, 
> only one system can be accessing the device at a time.  So, you will 
> need to unmount before Windows can see it and all Windows or files that 
> are accessing the device must be closed on the Windows side before you 
> can mount it again.
> 
> Hope this helps.  The above is tested on a Win2K machine running coLinux 
> 20040509 with the Debian image.  If you get USB to work for you, I'd 
> like to encourage you to write up your experiences and post them on the 
> wiki, especially if you are using a different host OS, snapshot, or image.
> 
> Regards,
> - Robert
> 
> 

Re: [coLinux-users] coLinux + Knoppix

[wind li <wi...@su...>]

<!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 bgcolor="#ffffff" text="#000000">
Aaron Spangler wrote:
<blockquote cite="mid001001c43d4c$22a787f0$6501a8c0@w2000" type="cite">
  <meta content="text/html; charset=iso-8859-1"
 http-equiv="Content-Type">
  <meta content="MSHTML 5.00.3813.800" name="GENERATOR">
  <style></style>
  <div><font face="Arial" size="2">I got knoppix 3.3 to work with
coLinux.&nbsp; I had to make a few changes, most notably:</font></div>
  <div>&nbsp;</div>
  <div><font face="Arial" size="2">3) Created a modified xinit so that
it would bring up vncserver.&nbsp; I also then created an icon on my windows
desktop that starts up TightVNC's vncviewer to connect to the knoppix
virtual machine.</font></div>
</blockquote>
<div>I have much interesting&nbsp; in this. How can we do it ?<br>
<br>
Thanks<br>
Wind<br>
</div>
<br>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>

Re: [coLinux-users] coLinux + Knoppix

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

On Tuesday, May 18, 2004, at 21:51 US/Central, Aaron Spangler wrote:
> I got knoppix 3.3 to work with coLinux.=A0 I had to make a few =
changes,=20
> most notably:
>  ...=A0
> There was a few other changes.=A0 I'll post the full details later =
when=20
> I get time.

This is fantastic.  Yes, please post the full details for others to=20
reproduce.

Regards,
- Robert

[coLinux-users] coLinux + Knoppix

[Aaron S. <as...@in...>]

I got knoppix 3.3 to work with coLinux.  I had to make a few changes, =
most notably:

1) The kernel supplied with coLinux does not include the 'cloop.o' =
driver necessary to mount the knoppix filesystem.  Similarly, the stock =
knoppix kernel does not support any of the coLinux drivers.  So we must =
then use an uncompressed filesystem.  In this case, I created a 3GB ext3 =
filesystem and then performed a 'cp -a' from the /KNOPPIX filesystem to =
the new filesystem while knoppix was running.  If we rebuild the kernel =
to include both the coLinux patches and include the cloop.o kernel =
driver, then modifing the initrd that comes with knoppix is sufficient.

2) Created a link to /dev/hda1 to /dev/cobd0 so the knoppix discover =
stuff would stumble on the correct root filesystem.  I of course created =
a real cobd0.

3) Created a modified xinit so that it would bring up vncserver.  I also =
then created an icon on my windows desktop that starts up TightVNC's =
vncviewer to connect to the knoppix virtual machine.

Notes:

Keyboard, Video, mouse work awesome.  (Full screen VNC works just as =
good as standalone knoppix)
The image works great in both 'bridged' and 'tap' network modes.  The =
only problem I found is that if you are running 'bridged' mode and a =
DHCP server is not running, then knoppix does not get an IP address.  =
Because of this you cannot then VNC to vncserver if you are running in =
bridged and there is no DHCP server. (In this case, it is better to run =
in bridged mode).

There was a few other changes.  I'll post the full details later when I =
get time.

[coLinux-users] CoLinux Interrupt Timer runs way too high??

[Aaron S. <as...@in...>]

I got coLinux to run great on one of my Win2k Boxes.

I have another Win2k box that seems to peg the CPU when I start coLinux =
with the same image.

I tried several different root images.  All of my tests have been with =
coLinux 0.6.0 using the provided kernel.

When I run top, it seems to update way too quickly.  If I type 'date', =
wait 10 seconds and type 'date' again, the system clock gains several =
hours!.  Also if I do a 'vmstat', I get huge interrupt counts.   If I =
keep doing 'cat /proc/interrupts', it shows the timer is sending tens of =
thousans of interrupts per second.  If I peg the cpu with a linux =
program and wait a few minutes, the problem seems to go away.  Similarly =
if I peg the cpu with a windows program, the problem seems to go away.  =
About 15 seconds after the cpu becomes idle, the timer interrupts go =
through the roof again.

I'm not sure what to do.

Suggestions?

 -Aaron

[coLinux-users] Many Colinux instances

[Carlos P. <dir...@bo...>]

Hi,

 

I need to setup many Linux instances, but I can't, the next errors happens:

 

C:\coLinux2>colinux-daemon2.exe

Cooperative Linux daemon

daemon: manager is already running

daemon: monitors running: 1

daemon: driver cannot be removed, aborting

 

Any solution??

 

Thanks in advance

 

Re: [coLinux-users] Never heard back from anybody regarding Kismet...

[<ch...@to...>]

Check the windows XP native bridging thread. There is a posting by Sam
Liddicott saying that he was able to disable the adapter in windows an
load a linux driver. (colinux can directly access hardware if windows is
not using it) This method would probably work for what you want to do. Yo=
u
will not have direct access to this through windows but could probably
setup a tap and route the windows traffic through linux and then back out
the wifi card. You will probably have to compile your wifi card module
seperatly for a non coLinux enabled kernel of the same patch level.

chris


> Hi all.  I never heard back from anybody regarding my message below.  I=
s
> Kismet going to work under CoLinux?  In other words, does CoLinux give
> direct access to hardware?  If not, can someone recommend a Linux
> distribution which will allow me to run Windows XP and Linux side-by-si=
de,
> where Kismet can have direct access to WLAN cards so they can be put in=
to
> promiscuous mode?
>
> - Phil
>
>
> --__--__--
>
> Message: 1
> Date: Sat, 15 May 2004 22:14:07 -0700
> From: Philip Schlesinger <psc...@ic...>
> To: col...@li...
> Subject: [coLinux-users] Will Kismet / AirSnort work under CoLinux?
>
> Hi all.  Please see subject.  The Windows version of AirSnort isn't
> great yet.  Kismet won't work under Cygwin b/c Windows doesn't allow th=
e
> WLAN card to be put into promiscuous mode.  Does CoLinux have the power
> to use a WLAN card in promiscuous mode?
>
> - Phil
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=3D2562&alloc_id=3D6184&op=3Dclick
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] Never heard back from anybody regarding Kismet...

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

On Monday, May 17, 2004, at 23:32 US/Central, Philip Schlesinger wrote:
> Hi all.  I never heard back from anybody regarding my message below.   
> Is Kismet going to work under CoLinux?  In other words, does CoLinux  
> give direct access to hardware?

You may be able to pull the same trick I did with USB for the wifi or  
other hardware.  Basically, use dmdiag.exe to figure out the device  
name under Windows, "bind" it to a block device in the .xml file, and  
then access it within colinux as /dev/cobd[0-9].

   
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/ 
dmdiag-o.asp

Let us know how it goes.

> If not, can someone recommend a Linux distribution which will allow me  
> to run Windows XP and Linux side-by-side, where Kismet can have direct  
> access to WLAN cards so they can be put into promiscuous mode?

You could run Linux with Windows under VMWare or maybe Bochs.  Not  
quite side-by-side, but close.

Go Zot!

Regards,
- Robert

[coLinux-users] Never heard back from anybody regarding Kismet...

[Philip S. <psc...@ic...>]

Hi all.  I never heard back from anybody regarding my message below.  Is Kismet going to work under CoLinux?  In other words, does CoLinux give direct access to hardware?  If not, can someone recommend a Linux distribution which will allow me to run Windows XP and Linux side-by-side, where Kismet can have direct access to WLAN cards so they can be put into promiscuous mode?

- Phil


--__--__--

Message: 1
Date: Sat, 15 May 2004 22:14:07 -0700
From: Philip Schlesinger <psc...@ic...>
To: col...@li...
Subject: [coLinux-users] Will Kismet / AirSnort work under CoLinux?

Hi all.  Please see subject.  The Windows version of AirSnort isn't 
great yet.  Kismet won't work under Cygwin b/c Windows doesn't allow the 
WLAN card to be put into promiscuous mode.  Does CoLinux have the power 
to use a WLAN card in promiscuous mode? 

- Phil

Re: [coLinux-users] Re: Re: Easy way SSH into colinux w/o checking ip?

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

Hello James,

On Monday, May 17, 2004, at 11:41 US/Central, James E. LaBarre wrote:
> It worked great in the Gentoo image (the only coLinux image I've ever 
> gotten to even boot successfully).

That's strage.   What other images have you tried?  Can you post your 
defaults.colinux.xml file?

Regards,
- Robert

Re: [coLinux-users] Is USB supported?

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

On Monday, May 17, 2004, at 19:46 US/Central, Robert Citek wrote:
> # mount /dev/cobd2 /mnt/usb
> UMSDOS 0.86k (compatibility level 0.4, fast msdos)
> # dir /mnt/usb/
> total 2620
> drwxr--r--    3 root     root        16896 Jan  1  1970 .
> drwxr-xr-x    5 root     root         4096 May 18 00:32 ..=00
>  ...

Chances are your USB stick has a fat32 and not a DOS filesystem.  If=20
so, you probably want to specify the filesystem type:

  # mount -t vfat /dev/cobd2 /mnt/usb

Regards,
- Robert

Re: [coLinux-users] Is USB supported?

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

Hello Sean,

On Monday, May 17, 2004, at 19:00 US/Central, Sean Covel wrote:
> I'd appreciate any information you have.  I'm on Win2k, coLinux=20
> 20040509, and the Gentoo "delux" image.

I can't find my notes anywhere.  Off the top of my head, you need to=20
get the tool called dmdiag.exe.  IIRC, you get this from Microsoft but=20=

google to be sure.  Install it and run it.  Then insert your USB stick=20=

and run it again.

Here's an example when I use my USB stick.  Here's a very abbreviated=20
portions of dmdiag.exe output before:

---------- Drive letter to device name, QueryDosDevice() ----------

            D: \Device\CdRom0
            A: \Device\Floppy0
            C: \Device\HarddiskVolume1

Here's a very abbreviated portions of dmdiag.exe output after:

---------- Drive letter to device name, QueryDosDevice() ----------

            D: \Device\CdRom0
            E: \Device\Harddisk1\DP(1)0-0+3
            A: \Device\Floppy0
            C: \Device\HarddiskVolume1
=00
Notice the new device E:\.  That's my USB stick.  I then add this line=20=

to my defaults.colinux.xml:

=00    <block_device index=3D"2" path=3D"\Device\Harddisk1\DP(1)0-0+3"=20=

enabled=3D"true" />=00

The index number will change depending on how many devices you already=20=

have defined and will be accessible within colinux as /dev/cobd2  (as=20
in _co_linux _b_lock _d_evice 2.  After I start colinux, I can mount=20
the usb stick like so:

# mkdir /mnt/usb
# mount /dev/cobd2 /mnt/usb
UMSDOS 0.86k (compatibility level 0.4, fast msdos)
# dir /mnt/usb/
total 2620
drwxr--r--    3 root     root        16896 Jan  1  1970 .
drwxr-xr-x    5 root     root         4096 May 18 00:32 ..=00
  ...
# umount /mnt/usb

This is a simple way for Windows to communicate with coLinux.  However,=20=

only one system can be accessing the device at a time.  So, you will=20
need to unmount before Windows can see it and all Windows or files that=20=

are accessing the device must be closed on the Windows side before you=20=

can mount it again.

Hope this helps.  The above is tested on a Win2K machine running=20
coLinux 20040509 with the Debian image.  If you get USB to work for=20
you, I'd like to encourage you to write up your experiences and post=20
them on the wiki, especially if you are using a different host OS,=20
snapshot, or image.

Regards,
- Robert

Re: [coLinux-users] How to compile and install newer kernels?

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

On Monday, May 17, 2004, at 09:19 US/Central, ib...@ge... 
wrote:
> does anyone know/have pointers to more information about  how to 
> compile
> and install a newer kernel for colinux?

I have a bunch of notes on various installs I've tried.  See the 
section " Building coLinux on coLinux with Debian root filesystem" at 
the bottom of this page:

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

Is this what you had in mind?

Regards,
- Robert

Re: [coLinux-users] How to compile and install newer kernels?

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

On Mon, May 17, 2004 at 10:19:46AM -0400, ib...@ge... wrote:
> 
> 
> 
> 
> Hello folks,
> 
> does anyone know/have pointers to more information about  how to compile
> and install a newer kernel for colinux?
> 

If you want newer in terms of 2.4.x series, 0509 snapshot already has it.

If you're asking for 2.6.x, I think it requires more than just giving a 
pointer, on which some folks from devel team should be working.

Re: [coLinux-users] Is USB supported?

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

On Monday, May 17, 2004, at 14:49 US/Central, Sean Covel wrote:
> I'm using the 2.4.26-co kernel and I don't see any modules for USB.  
> Is USB supported yet?

Hmm, worked for me.  I had to use a windows tool to figure out the 
device name (dmiag or something close to that name) and modify the .xml 
file.  When I get home, I'll dig out the details, write up a wiki page, 
and post the url.  BTW, I was using Win2K, colinux 20040509, and the 
Debian image.

Regards,
- Robert

[coLinux-users] Is USB supported?

[Sean C. <sea...@co...>]

I'm using the 2.4.26-co kernel and I don't see any modules for USB.  Is 
USB supported yet?

Thanks,

Sean

Re: [coLinux-users] Re: Re: Easy way SSH into colinux w/o checking ip?

[James E. L. <ja...@be...>]

>>>   Usually, I'll move around constantly between campus
>>>and my house. Campus is 192.168.0.x and House is
>>>10.1.1.x, so what ip address(n subnet) should i use
>>>for the NAT? I'll have vnc working tomorrow with
>>>XDMCP. Should I set static IPs in NAT and have TAP a
>>>static Ip and then i vnc into it everytime?

Do you have DHCP at home and at school?  I ended up installing WinPcap 
on mine and let the client grab an address from my router (using 
connection sharing wouldn't work here).  It worked great in the Gentoo 
image (the only coLinux image I've ever gotten to even boot successfully).

RE: [coLinux-users] Re: [coLinux-devel] Windows XP native bridging

[Daniel S. <dan...@ya...>]

Will this really work? It looks to me like the colinux patch prevents you
from building network drivers and the supporting PCI drivers you need. If
this does work, then maybe the colinux patch shouldn't prevent building
hardware drivers when you're configuring your kernel, Seems that this could
actually be quite useful on a multi-homed machine.

Dan

-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of Samuel
Liddicott
Sent: Monday, May 17, 2004 11:17 AM
To: col...@li...
Cc: col...@li...
Subject: [coLinux-users] Re: [coLinux-devel] Windows XP native bridging



"John Nelson" <jo...@mo...> wrote in
message news:40A...@mo......
> I have been using XP's native bridging without a hitch for quite some
> time now.    If you want *all* of your traffic to go to colinux, just
> disable your network adapter in windows, and find and load an
> appropriate driver module for the adapter under colinux.  As long as
> Windows know not to touch the adapter, colinux is free to sieze it for
> itself.
<...snip...>





-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] Re: [coLinux-devel] Windows XP native bridging

[Samuel L. <sa...@li...>]

"John Nelson" <jo...@mo...> wrote in
message news:40A...@mo......
> I have been using XP's native bridging without a hitch for quite some
> time now.    If you want *all* of your traffic to go to colinux, just
> disable your network adapter in windows, and find and load an
> appropriate driver module for the adapter under colinux.  As long as
> Windows know not to touch the adapter, colinux is free to sieze it for
> itself.
>
> More likely, however, you'll probably want some level of access for both
> Windows and colinux.  That usually means bridgng.  The knowledge-base
> entry at microsoft indicates a few things that /shouldn't/ be relevant
> to your situation... if they are, we'll need to fix things.  First of
> all, make sure you only have your wireless and TAP-Win32 adapter
> present.  Second, make sure you have ICS disabled (the adapter statuses
> should NOT say 'shared' -- this is the part that shouldn't be relevant
> for that MS-kb entry).  Third, select both adapters, right-click and
> select 'bridge' -- this should work with ICS disabled.  Lastely, make
> sure your colinux configuration file has a 'network' element in it with
> the type argument set to 'tap'.

Do I also need to right-click the bridge interface and select which adaptor
is to be used to make the internet connections?
What settings should I have on my windows TAP adaptor? DHCP? Or hard wired
to some local networks settings?
Can I put my coLinux eth0 adaptor on dhcp (I have installed dhcp-client) or
should it be hard-wired?

> At this point, the rest of the world will see two computers behind your
> network interface once colinux starts up.... it will see /both/ your
> Windows machine and your colinux "machine".  As such, colinux will get
> its own IP address independent of your Windows machine.  Since it will
> have its own IP, sending your http/smtp/whatever-else to it is trivial.
> As for setting that IP, your linux system needs to be internally
> configured to use either static or DHCP-provided addresses, depending on
> which your Windows machine is getting.

My windows is DHCP on its true interface but what about the TAP windows
interface? Surely that should NOT be DHCP or it will be asking coLinux what
address to use?

Sam

Re: [coLinux-users] Windows 2000 - Connection Sharing

[Sean C. <sea...@co...>]

Robert,

Robert Citek wrote:
> 
> (I've moved this thread back to the list.)
> 
> On Monday, May 17, 2004, at 03:32 US/Central, Sean Covel wrote:
> 
>> The main networking page in the WIKI is missing the "always on" setting.
> 
> 
> Which page is that?  Can you post a URL?
> 

http://www.colinux.org/wiki/index.php/coLinuxNetworking

>> I'm glad you started the user list because your documentation on the 
>> WIKI is difficult to navigate.
> 
> 
> Just to clarify, I didn't start the user list nor the wiki.  I just 
> send/reply to e-mails, write/modify wiki pages, and dabble with the code 
> occasionally.  Dan deserves the credit for starting the project and the 
> lists.  http://www.colinux.org/?section=devteam
> 

Ok, Thanks DAN!!!

>> I just did an "emerge sync" on coLinux and it worked!
> 
> 
> This seems to be Gentoo's equivalent to Debian's apt-get update ... sort 
> of.
> 

Only much worse, since it compiles everything from scratch.  Its still 
running...

>> The two pieces I was missing was the "always on" and the static IP for 
>> the TAP NIC.
> 
> 
> Interesting.  Although 'ipconfig /all' says 'no' for 'DHCP enabled', I 
> have never set the IP address on the TAP adapter.  TAP has always been 
> DHCP for me.  Strange that the TAP adapter doesn't list a gateway, 
> either, yet it works.
> 
>> Having the link to the "ipconfig /all" really helped.
> 
> 
> That's good to know.  Thanks for the feedback.
> 

I thought the blank gateway was odd too.  I manually set my connection 
up for static IP, no gateway (like yours ;-)) and it seems to work too.

>> I'm running coLinux 20040509.  My root fs is the Gentoo fs.
>>
>> I was SOOOO close to re-partitioning my laptop's HD so I could dual 
>> boot Linux.  I'm sure my work's tech support would have frowned on 
>> that. coLinux solves that problem for me!
>>
>> Thanks for your hard work and a really cool project!!!
> 
> 
> For the pieces I've done, you're welcome.  But thanks really go to Dan 
> for getting the ball rolling and everyone else for pushing it along.
> 
>> P.S.  Now to try to get coLinux to use my wireless NIC.  Am I too 
>> greedy?  Maybe, but my home network is wireless.
> 
> 
> I say go for it.  But if you run into issues, you may want to check the 
> mailing list archives and the wiki page for hints on wireless.  I've 
> heard people having mixed results.  I'm doing wireless, but in a very 
> strange way:
> 



>   http://cwelug.org/cgi-bin/wiki.cgi?X11_Colinux_Win2k_Osx

Ouch!  That makes my head hurt!!!  I saw a howto that uses a socks proxy 
to get the connection to go over wireless.  Long about step 5 you need 
to apt-get something.  Since I didn't have the regular networking going 
I couldn't exactly install anything...  Now that my networking is going, 
I can re-start working on the wireless connection.

> 
> Regards,
> - Robert
> 
> 
> 

Again, thanks, and you too Dan!

Sean

> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>