colinux-users — coLinux users mailing list

Re: [coLinux-users] Is there a way to set the nt console to a different size at start up?

[Paolo M. <pao...@gm...>]

Frank Church wrote:
> Is there a way to set the nt console to a different size at start up?
>
> The default size is small when you have to view start up problems,
>
>   
you can use cocon=100x40

to set 100x40 console.

Obviously you can choose values you think are the better for your use.

Bye,
Paolo

[coLinux-users] Help need with udev: renamed network interface eth0 to eth2

[Frank C. <vfc...@go...>]

I installed an ubuntu Gutsy and later upgraded them to Hardy Heron,
but it seems that some of the networking settings carried over, and as
I have to run them all at the same time I just want to make sure the
problems don't happen again. I am afraid to reboot them in case they
lose their settings.

I have used the info in this link
http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2
to fix the problem temporarily, but I am not sure what mac addresses
they will be given if I reboot them. I just want to have a way of
ensuring that the interfaces are given unique mac address when they
restart.

These are the current ifconfig settings and the contents of the
/etc/udev/rules.d/70-persistent-net.rules, they are all derived from
the same image.


gutsy 7.1 - current configuration of ifconfig
==============================
eth0      Link encap:Ethernet  HWaddr 00:FF:41:48:88:00
eth1      Link encap:Ethernet  HWaddr 00:FF:37:1B:2C:00

<pre>
# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:55:1d:81:00",
NAME="eth0"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:9c:6d:40:00",
NAME="eth1"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:23:78:05:00",
NAME="eth2"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:3f:c7:4b:c0",
NAME="eth3"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:37:1b:2c:00",
NAME="eth4"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:41:48:88:00",
NAME="eth5"
</pre>


heron 1 - current configuration from ifconfig
=================================
eth0      Link encap:Ethernet  HWaddr 00:ff:41:48:88:00
eth1      Link encap:Ethernet  HWaddr 00:ff:37:1b:2c:00

<pre>
  GNU nano 2.0.7                      File:
/etc/udev/rules.d/70-persistent-net.rules
          View

# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:41:48:88:00",
ATTR{type}=="1", NAME="eth0"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:37:1b:2c:00",
ATTR{type}=="1", NAME="eth1"


# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:ff:3f:c7:4b:c0", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth0"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:ff:23:78:05:00", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth1"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:ff:41:48:88:00", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth2"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:ff:37:1b:2c:00", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth3"
</pre>

heron 2 - working configuration from ifconfig
=================================
eth0      Link encap:Ethernet  HWaddr 00:ff:55:1d:81:00
eth1      Link encap:Ethernet  HWaddr 00:ff:9c:6d:40:00
<pre>
# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:41:48:88:00",
ATTR{type}=="1", NAME="eth0"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:37:1b:2c:00",
ATTR{type}=="1", NAME="eth1"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:ff:55:1d:81:00", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth2"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:ff:9c:6d:40:00", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth3"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:ff:3f:c7:4b:c0", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth4"

# PCI device 0x1a55:0x0005 (conet)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:ff:23:78:05:00", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth5"

</pre>




-- 
Frank Church

============================
http://devblog.brahmancreations.com

[coLinux-users] Is there a way to set the nt console to a different size at start up?

[Frank C. <vfc...@go...>]

Is there a way to set the nt console to a different size at start up?

The default size is small when you have to view start up problems,

-- 
Frank Church

=======================
<a href="http://devblog.brahmancreations.com">devblog.brahmancreations.com</a>

Re: [coLinux-users] Iso?

[Henry N. <hen...@ar...>]

mattias wrote:
> Can i install a colinux dist via  a standard iso?
> E.g
> cobd0="c:\test.iso"
>    

No, mostly distributions have special initrd, that would not run under 
coLinux.
The second problem is, that the distributions needs full partion table 
informations.

You have some alternates:
* Install WUBI and follow steps from Wiki. That is very easy.
See http://colinux.wikia.com/wiki/Wubi

* The (new) scsi drivers are usable to install in such way, for example

   scsi0=disk,C:\colinux\harddisk.img,4000
   scsi1=cdrom,c:\test.iso

But, you need to modify the initrd and add the modules into. Bill has 
posted the commands for Fedora:
>     gunzip -c initrd.img > initrd.cpio
>     tar xfz vmlinux-modules.tar.gz
>     find lib/modules |cpio -o -H newc -A -F initrd.cpio
>     gzip -c initrd.cpio > initrd.img
This way is mostly difficould. For example you needs a distribition that 
can install without graphic. coLinux have text mode only.

-- 
Henry N.

[coLinux-users] Iso?

[mattias <mj...@mj...>]

Can i install a colinux dist via  a standard iso?
E.g
cobd0="c:\test.iso"

Re: [coLinux-users] 2 instances

[Henry N. <hen...@ar...>]

mattias wrote:
> Can i run 2 instances of colinux on the same time? Or only one
>    

You can.

You needs completely all in a copy. You needs two config files, two 
rootimage files, two swap files, and if you use TAP, than you also needs 
to add a second of this.

Some words are written in this wiki page:
http://colinux.wikia.com/wiki/Running_as_a_Service

Here you can see 4 instances running:
http://home.arcor.de/henryn/colinux/screenshoots/colinux-4runs.png

-- 
Henry N.

[coLinux-users] pppoe [was: ip]

[Henry N. <hen...@ar...>]

mattias wrote:
> Have anyone be able to use an ip from your isp with colinux
> If so
> Do you use winpcap or windows own bridge
>    

You need "pcap-bridge" or "ndis-bridge" in the coLinux config.
Than install pppoe inside Linux and configure your provider.

Be sure, that you can not use Internet on Windows side at same time.

-- 
Henry N.

[coLinux-users] ip

[mattias <mj...@mj...>]

Have anyone be able to use an ip from your isp with colinux
If so
Do you use winpcap or windows own bridge
Sorry my english

[coLinux-users] 2 instances

[mattias <mj...@mj...>]

Can i run 2 instances of colinux on the same time? Or only one

Re: [coLinux-users] coLinux inside VirtualBox on Linux ?

[Frédéric L. W. M. <lis...@pe...>]

On Fri, 4 Sep 2009, Henry Nestler wrote:

> Am 04.09.2009 03:16, schrieb Henry Nestler:
>
> PCI was completely disable from an older Kconfig.
> Network works now.
>
> For quick update on your sources follow these steps:
> - Go into directory of coLinux kernel sources (linux-2.6.25-source) and run 
> "quilt pop -a"
> - Replace "patch/pci-2.6.25.diff" in coLinux Source tree from this tar.
> - Run "quilt push -a" in kernel source tree.
> - Replace .config in "linux-2.6.25-build" with the newer one 
> "linux-2.6.25-config" from this tar.
> - Rebuild Kernel by running "make kernel" in coLinux source tree.
>
> I will upload my build next minutes.

Thanks. It worked fine, also compiling with MK8. So, I guess 
it was a GCC 4.3.3 x 2.6.22.18 issue.

Re: [coLinux-users] coLinux inside VirtualBox on Linux ?

[Frédéric L. W. M. <lis...@pe...>]

On Thu, 3 Sep 2009, Henry Nestler wrote:

> Frédéric L. W. Meunier wrote:
>> Henry, it worked fine with a 2.6.22.18 kernel compiled using GCC
>> 4.3.3.
>> 
>> But running a 2.6.25 kernel compiled using your patches, I got
>> 
>> colinux: error, expected kernel API version 13, got 11
>> error initializing
>> daemon: exit code 82c6fc03
>> daemon: error driver version, please reinstall driver!
>> 
>> Is it because the 4.1.2 x 4.3.3 ?
>> 
>> But why 2.6.22.8 is accepted by the daemons and not 2.6.25 ?
> The patch series was to old. We have changed a lot on the passage page, 
> that's why we have increased the API to 13 now. This avoids a crash of your 
> host system. ;-)
>
> Patches have updated now on:
> http://www.henrynestler.com/colinux/testing/kernel-2.6.25
>
> Please run a "make clean" after adding the new patches for kernel 2.6.25.
>
> Please remember to enable the patch gcc412fix.diff in the file 
> patch/series-2.6.25, if gcc 4.1.2 is your local compiler for kernel builds.

Thanks. It compiled and worked fine. I'm using GCC 4.3.3. I had 
patched the 2.6.22.18 sources with http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git;a=blob;f=queue-2.6.24/time-prevent-the-loop-in-timespec_add_ns-from-being-optimised-away.patch;h=489cbdaa36a065ee536b73f53b7cba8a8e8635bc;hb=cf3242783319c215e3d2e59e293e9c307724cea5

Henry, do you get networking support with the 2.6.25 kernel ? 
Here, lo comes up, but not eth0.

In VirtualBox I'm using the Debian 5.0r2 image with slirp. I 
also tried pcap and tuntap, but eth0 doesn't come up.

If I boot with the 2.6.22.18 vmlinux, it comes up.

Re: [coLinux-users] coLinux inside VirtualBox on Linux ?

[Henry N. <hen...@ar...>]

Frédéric L. W. Meunier wrote:
> Henry, it worked fine with a 2.6.22.18 kernel compiled using GCC
> 4.3.3.
>
> But running a 2.6.25 kernel compiled using your patches, I got
>
> colinux: error, expected kernel API version 13, got 11
> error initializing
> daemon: exit code 82c6fc03
> daemon: error driver version, please reinstall driver!
>
> Is it because the 4.1.2 x 4.3.3 ?
>
> But why 2.6.22.8 is accepted by the daemons and not 2.6.25 ?
The patch series was to old. We have changed a lot on the passage page, 
that's why we have increased the API to 13 now. This avoids a crash of 
your host system. ;-)

Patches have updated now on:
http://www.henrynestler.com/colinux/testing/kernel-2.6.25

Please run a "make clean" after adding the new patches for kernel 2.6.25.

Please remember to enable the patch gcc412fix.diff in the file 
patch/series-2.6.25, if gcc 4.1.2 is your local compiler for kernel builds.

-- 
Henry N.

Re: [coLinux-users] coLinux inside VirtualBox on Linux ?

[Frédéric L. W. M. <lis...@pe...>]

On Thu, 3 Sep 2009, Henry Nestler wrote:

> Frédéric L. W. Meunier wrote:
>> Is that combination supposed to run ?
>> 
>> I ask because I want to do some tests with coLinux, but not like
>> on Windows, where I use the stable coLinux snapshots with my
>> Linux partition and don't run into a problem for a long time.
>> 
>> I customized the 2.6.22.8 kernel, removing options I don't need,
>> adding others (not drivers and such), am also willing to try out
>> the 2.6.25 patches, but don't want get lots of BSOD's if things
>> go wrong.
>> 
>> What if I run coLinux inside VirtualBox's VM, that has Windows
>> XP SP3 ? Is it supposed to work ? But if it does, can it hide
>> problems that may arise when I use the same kernel on plain
>> Windows ?
>> 
> Of curse you can run coLinux inside a VirtualBox machine.
>
> You should run XP (not Linux) inside VirtualBox to have the same host OS for 
> coLinux:
> Any OS (Windows or Linux) --> VirtualBox --> Windows XP --> coLinux
>
> Please enable Physical Address Extension ("/PAE" in boot.ini file), if your 
> "stable" Windows also use it. You can see "Physical Address Extension" after 
> pressing Windows+Pause.
> http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx
>
> There are no hiding problems from inside VirtualBox.

Henry, it worked fine with a 2.6.22.18 kernel compiled using GCC 
4.3.3.

But running a 2.6.25 kernel compiled using your patches, I got

colinux: error, expected kernel API version 13, got 11
error initializing
daemon: exit code 82c6fc03
daemon: error driver version, please reinstall driver!

Is it because the 4.1.2 x 4.3.3 ?

But why 2.6.22.8 is accepted by the daemons and not 2.6.25 ?

Re: [coLinux-users] coLinux inside VirtualBox on Linux ?

[Henry N. <hen...@ar...>]

Frédéric L. W. Meunier wrote:
> Is that combination supposed to run ?
>
> I ask because I want to do some tests with coLinux, but not like
> on Windows, where I use the stable coLinux snapshots with my
> Linux partition and don't run into a problem for a long time.
>
> I customized the 2.6.22.8 kernel, removing options I don't need,
> adding others (not drivers and such), am also willing to try out
> the 2.6.25 patches, but don't want get lots of BSOD's if things
> go wrong.
>
> What if I run coLinux inside VirtualBox's VM, that has Windows
> XP SP3 ? Is it supposed to work ? But if it does, can it hide
> problems that may arise when I use the same kernel on plain
> Windows ?
>    
Of curse you can run coLinux inside a VirtualBox machine.

You should run XP (not Linux) inside VirtualBox to have the same host OS 
for coLinux:
Any OS (Windows or Linux) --> VirtualBox --> Windows XP --> coLinux

Please enable Physical Address Extension ("/PAE" in boot.ini file), if 
your "stable" Windows also use it. You can see "Physical Address 
Extension" after pressing Windows+Pause.
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx

There are no hiding problems from inside VirtualBox.

-- 
Henry N.

[coLinux-users] coLinux inside VirtualBox on Linux ?

[Frédéric L. W. M. <lis...@pe...>]

Is that combination supposed to run ?

I ask because I want to do some tests with coLinux, but not like 
on Windows, where I use the stable coLinux snapshots with my 
Linux partition and don't run into a problem for a long time.

I customized the 2.6.22.8 kernel, removing options I don't need, 
adding others (not drivers and such), am also willing to try out 
the 2.6.25 patches, but don't want get lots of BSOD's if things 
go wrong.

What if I run coLinux inside VirtualBox's VM, that has Windows 
XP SP3 ? Is it supposed to work ? But if it does, can it hide 
problems that may arise when I use the same kernel on plain 
Windows ?

Re: [coLinux-users] [Solved] If I run coLinux as different admin on windows xp, i get eth0 and eth1 coundn't be found error!

[Henry N. <hen...@ar...>]

>
> I always thought in was a problem outside coLinux, in Windows. but when I digged in the mailing list, i found something similar:
>
> Networking and run-as-service user account issues
> http://sourceforge.net/mailarchive/forum.php?thread_name=48406129.4070804%40henry.ne.arcor.de&forum_name=colinux-users
>
> so cleaning the /etc/udevd/rules.d/70-persistent-net.rules worked.
>    

yes, different users on Windows have different MAC numbers, and udev 
will rename it into some others as eth0 and eth1. To fix this in future, 
please add a "bypass" for conet in the rule file.

see wiki:
http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2

Or set a fixed MAC number for your interface, for example:
eth0=slirp,02:00:00:00:00:01
eth1=tuntap,,02:00:00:00:00:02

-- 
Henry N.

[coLinux-users] [Solved] If I run coLinux as different admin on windows xp, i get eth0 and eth1 coundn't be found error!

[First N. <bak...@ya...>]

I always thought in was a problem outside coLinux, in Windows. but when I digged in the mailing list, i found something similar:

Networking and run-as-service user account issues
http://sourceforge.net/mailarchive/forum.php?thread_name=48406129.4070804%40henry.ne.arcor.de&forum_name=colinux-users

so cleaning the /etc/udevd/rules.d/70-persistent-net.rules worked.

Thanks again, sorry for the trouble.



      

[coLinux-users] Please help: If I run coLinux as different admin on windows xp, i get eth0 and eth1 coundn't be found error!

[First N. <bak...@ya...>]

Hi,

I have two administrator accounts on a xp machine (let's call them ALPHA and BRAVO).

I installed coLinux 0.7.4 as first admin ALPHA, (and Gentoo in coLinux) result: everything works!

But if i run as admin BRAVO; in boot sequence, i get an error about eth0 and eth1 couldn't be found! (check kernel module etc.)
                               
i uninstalled as admin ALPHA and installed as admin BRAVO. But result was same. eth0 and eth1 was NOT working as admin BRAVO, but was working as admin ALPHA AGAIN !!

In fact i really need to run coLinux as admin BRAVO, but coLinux only runs properly as admin ALPHA.

Please help

Thanks in advance



      

Re: [coLinux-users] vnc step by step needed

[baldyeti <e_...@ho...>]

If you set the same address both for tun and eth0,
how do you know the answer you're getting from ping
is from the other operating system ? Please try what
has been suggested, then assess connectivity through
some simple protocol (putty/a browser, if you've got
sshd/apache started on the linux side), then proceed
to X or vnc.

On 25/08/2009 22:12, Ben Brannen wrote:
> OK.  I can now ping from one machine to another and vice-versa (I 
> think). I set my TAP-Win32 to the same address as my colinux which 
> happened to be 10.0.2.15 mask 255.255.255.0 and left default gateway blank.
> 
> here is a snapshot of the related section of my processes. Elipses ..... 
> means it was truncated by the console window
> 
> root      2263  0.0  0.1   2060   372 ?        S<s  15:40   0:00 
> dhclient3 -pf /var/run/dhclient.eth0.pid -lf 
> /var/lib/dhcp3/dhclient.eth0.leases eth0
> root      2286  0.0  0.3   5276   980 ?        S<s  15:40   0:00 
> /usr/sbin/sshd
> root      2287  0.0  0.6   4120  1676 tty1     S    15:40   0:00 -bash
> root      2305  0.2  2.4   8520  6264 tty1     S    15:45   0:00 
> Xtightvnc :1 -desktop X -auth /root/.Xauthority -geometry 1024x768 
> -depth 24 -rfbwait 120000......
> root      2312  0.3  4.6  22516 12000 tty1     S    15:45   0:00 
> xfce4-terminal --geometry=80x24+10+10 --title X Desktop
> root      2313  0.1  3.2  16688  8364 tty1     S    15:45   0:00 
> x-window-manager
> root      2318  0.0  0.2   2964   696 tty1     S    15:45   0:00 
> dbus-launch --autolaunch e169c71230fc8d642638262f4a899d73 
> --binary-syntax --close-stderr
> root      2319  0.0  0.3   2480   844 ?        Ss   15:45   0:00 
> /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
> root      2320  0.0  1.5  18472  3932 ?        Ss   15:45   0:00 
> xfce-mcs-manager
> root      2321  0.0  0.2   2748   760 tty1     S    15:45   0:00 
> gnome-pty-helper
> root      2322  0.0  0.6   4104  1636 pts/0    Ss+  15:45   0:00 bash
> root      2327  0.0  0.3   3580  1016 tty1     R+   15:49   0:00 ps aux
> 
> 
> Restating the objective: is to run VNC in windows to display a desktop 
> or some such from co-linux.  I can start vncserver in colinux and set a 
> password.  I also tried
> export DISPLAY=10.0.2.15:1 <http://10.0.2.15:1>
> xclock &
> [1] 2334
> COLINUX:~/.VNC# Client is not authorized to connect to ServerError: 
> Can't open display 10.0.2.15:1 <http://10.0.2.15:1>
> [1]+  Exit 1                  xclock
> colinux:~/.vnc#
> tried switching to non-root user and get the same error
> 
> (I'm assuming with that error I can't go further however I tried anyway 
> thinking I might get a blank screen and this is what I got)
> 
> Whenever I try to connect from windows using RealVNC or TightVNC i get 
> the same errors:
> Failed to connect to server(10.0.2.15)
> 
> I've tried connecting to:
> 10.0.2.15
> 10.0.2.15:1 <http://10.0.2.15:1>
> 10.0.2.15:5900 <http://10.0.2.15:5900>
> 10.0.2.15:5901 <http://10.0.2.15:5901>
> 
> -ben
> 
> 
> ------------------------------
> 
> On Sat, Aug 22, 2009 at 2:08 AM, baldyeti 
> <e_...@ho... 
> <mailto:e_...@ho...>> wrote:
> 
>     I know there are several ways to setup networking for
>     colinux and the instructions on the wiki can be confusing.
>     As I said, I think your windows tun/tap address should be
>     on the same IP subnetwork as your virtual linux.
> 
>     In my case I have
> 
>     C:\temp>ipconfig /all
>     ...
>     Ethernet adapter tuntap:
>             Description . . . . . . . . . . . : TAP-Win32 Adapter V8
>     (coLinux)
>             Physical Address. . . . . . . . . : 00-FF-77-A4-F2-4C
>             Dhcp Enabled. . . . . . . . . . . : No
>             IP Address. . . . . . . . . . . . : 192.168.0.1
>             Subnet Mask . . . . . . . . . . . : 255.255.255.0
>             Default Gateway . . . . . . . . . :
> 
>     shoebox:~# ifconfig
>     eth0      Link encap:Ethernet  HWaddr 00:ff:39:6d:48:00
>               inet addr:192.168.0.106  Bcast:192.168.0.255
>     ...
> 
>     So: for me 192.168.0.x is the virtual IP network through
>     which host and guest communicate. In your case, either change
>            the tun/tap address to 10.0.2.xxx
>            or the linux addresss to 192.168.37.yyy
> 
>     On the windows side you also need to enable connection sharing of
>     your main (physical) connection (10.252.248.152)
> 
>     On 21/08/2009 22:50, Ben Brannen wrote:
>      > Looks like we are getting closer.  I can't ping colinux from windows.
>      >
>      > colinux:~# ping 10.252.248.152
>      > PING 10.252.248.152 (10.252.248.152) 56(84) bytes of data.
>      > 64 bytes from 10.252.248.152 <http://10.252.248.152>: icmp_seq=1
>     ttl=255 time=30.0 ms
>      >
>      > C:\>ping 10.0.2.15
>      > Pinging 10.0.2.15 with 32 bytes of data:
>      > Request timed out.
>      > ...
>      > Ping statistics for 10.0.2.15 <http://10.0.2.15>:
>      >     Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>      >
>      > -ben
>      >
> 
> 
>     ------------------------------------------------------------------------------
>     Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>     30-Day
>     trial. Simplify your report design, integration and deployment - and
>     focus on
>     what you do best, core application coding. Discover what's new with
>     Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>     _______________________________________________
>     coLinux-users mailing list
>     coL...@li...
>     <mailto:coL...@li...>
>     https://lists.sourceforge.net/lists/listinfo/colinux-users
> 
> 
> 
> ------------------------------------------------------------------------
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] vnc step by step needed

[Ben B. <ben...@gm...>]

OK.  I can now ping from one machine to another and vice-versa (I think). I
set my TAP-Win32 to the same address as my colinux which happened to be
10.0.2.15 mask 255.255.255.0 and left default gateway blank.

here is a snapshot of the related section of my processes. Elipses .....
means it was truncated by the console window

root      2263  0.0  0.1   2060   372 ?        S<s  15:40   0:00 dhclient3
-pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0
root      2286  0.0  0.3   5276   980 ?        S<s  15:40   0:00
/usr/sbin/sshd
root      2287  0.0  0.6   4120  1676 tty1     S    15:40   0:00 -bash
root      2305  0.2  2.4   8520  6264 tty1     S    15:45   0:00 Xtightvnc
:1 -desktop X -auth /root/.Xauthority -geometry 1024x768 -depth 24 -rfbwait
120000......
root      2312  0.3  4.6  22516 12000 tty1     S    15:45   0:00
xfce4-terminal --geometry=80x24+10+10 --title X Desktop
root      2313  0.1  3.2  16688  8364 tty1     S    15:45   0:00
x-window-manager
root      2318  0.0  0.2   2964   696 tty1     S    15:45   0:00 dbus-launch
--autolaunch e169c71230fc8d642638262f4a899d73 --binary-syntax --close-stderr
root      2319  0.0  0.3   2480   844 ?        Ss   15:45   0:00
/usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
root      2320  0.0  1.5  18472  3932 ?        Ss   15:45   0:00
xfce-mcs-manager
root      2321  0.0  0.2   2748   760 tty1     S    15:45   0:00
gnome-pty-helper
root      2322  0.0  0.6   4104  1636 pts/0    Ss+  15:45   0:00 bash
root      2327  0.0  0.3   3580  1016 tty1     R+   15:49   0:00 ps aux


Restating the objective: is to run VNC in windows to display a desktop or
some such from co-linux.  I can start vncserver in colinux and set a
password.  I also tried
export DISPLAY=10.0.2.15:1
xclock &
[1] 2334
COLINUX:~/.VNC# Client is not authorized to connect to ServerError: Can't
open display 10.0.2.15:1
[1]+  Exit 1                  xclock
colinux:~/.vnc#
tried switching to non-root user and get the same error

(I'm assuming with that error I can't go further however I tried anyway
thinking I might get a blank screen and this is what I got)

Whenever I try to connect from windows using RealVNC or TightVNC i get the
same errors:
Failed to connect to server(10.0.2.15)

I've tried connecting to:
10.0.2.15
10.0.2.15:1
10.0.2.15:5900
10.0.2.15:5901

-ben


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

On Sat, Aug 22, 2009 at 2:08 AM, baldyeti <e_...@ho...> wrote:

> I know there are several ways to setup networking for
> colinux and the instructions on the wiki can be confusing.
> As I said, I think your windows tun/tap address should be
> on the same IP subnetwork as your virtual linux.
>
> In my case I have
>
> C:\temp>ipconfig /all
> ...
> Ethernet adapter tuntap:
>         Description . . . . . . . . . . . : TAP-Win32 Adapter V8 (coLinux)
>         Physical Address. . . . . . . . . : 00-FF-77-A4-F2-4C
>         Dhcp Enabled. . . . . . . . . . . : No
>         IP Address. . . . . . . . . . . . : 192.168.0.1
>          Subnet Mask . . . . . . . . . . . : 255.255.255.0
>         Default Gateway . . . . . . . . . :
>
> shoebox:~# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:ff:39:6d:48:00
>           inet addr:192.168.0.106  Bcast:192.168.0.255
> ...
>
> So: for me 192.168.0.x is the virtual IP network through
> which host and guest communicate. In your case, either change
>        the tun/tap address to 10.0.2.xxx
>        or the linux addresss to 192.168.37.yyy
>
> On the windows side you also need to enable connection sharing of
> your main (physical) connection (10.252.248.152)
>
> On 21/08/2009 22:50, Ben Brannen wrote:
> > Looks like we are getting closer.  I can't ping colinux from windows.
> >
> > colinux:~# ping 10.252.248.152
> > PING 10.252.248.152 (10.252.248.152) 56(84) bytes of data.
> > 64 bytes from 10.252.248.152: icmp_seq=1 ttl=255 time=30.0 ms
> >
> > C:\>ping 10.0.2.15
> > Pinging 10.0.2.15 with 32 bytes of data:
> > Request timed out.
> > ...
> > Ping statistics for 10.0.2.15:
> >     Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> >
> > -ben
> >
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] vnc step by step needed

[baldyeti <e_...@ho...>]

I know there are several ways to setup networking for
colinux and the instructions on the wiki can be confusing.
As I said, I think your windows tun/tap address should be
on the same IP subnetwork as your virtual linux.

In my case I have

C:\temp>ipconfig /all
...
Ethernet adapter tuntap:
         Description . . . . . . . . . . . : TAP-Win32 Adapter V8 (coLinux)
         Physical Address. . . . . . . . . : 00-FF-77-A4-F2-4C
         Dhcp Enabled. . . . . . . . . . . : No
         IP Address. . . . . . . . . . . . : 192.168.0.1
         Subnet Mask . . . . . . . . . . . : 255.255.255.0
         Default Gateway . . . . . . . . . :

shoebox:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:ff:39:6d:48:00
           inet addr:192.168.0.106  Bcast:192.168.0.255
...

So: for me 192.168.0.x is the virtual IP network through
which host and guest communicate. In your case, either change
	the tun/tap address to 10.0.2.xxx
	or the linux addresss to 192.168.37.yyy

On the windows side you also need to enable connection sharing of
your main (physical) connection (10.252.248.152)

On 21/08/2009 22:50, Ben Brannen wrote:
> Looks like we are getting closer.  I can't ping colinux from windows.
> 
> colinux:~# ping 10.252.248.152
> PING 10.252.248.152 (10.252.248.152) 56(84) bytes of data.
> 64 bytes from 10.252.248.152: icmp_seq=1 ttl=255 time=30.0 ms
> 
> C:\>ping 10.0.2.15
> Pinging 10.0.2.15 with 32 bytes of data:
> Request timed out.
> ...
> Ping statistics for 10.0.2.15:
>     Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> 
> -ben
> 

Re: [coLinux-users] vnc step by step needed

[Ben B. <ben...@gm...>]

Looks like we are getting closer.  I can't ping colinux from windows.

colinux:~# ping 10.252.248.152
PING 10.252.248.152 (10.252.248.152) 56(84) bytes of data.
64 bytes from 10.252.248.152: icmp_seq=1 ttl=255 time=30.0 ms

C:\>ping 10.0.2.15
Pinging 10.0.2.15 with 32 bytes of data:
Request timed out.
...
Ping statistics for 10.0.2.15:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

-ben




On Fri, Aug 21, 2009 at 2:27 AM, e_fax_t<e_...@ho...> wrote:
> Hi,
>
> please reply on the list in the future so others can contribute.
>
> colinux.org may not reply (it does for me), but at least it seems
> the address is being resolved so there's hope.
> OTOH your TAP address (192.168.37.10)) is not on the same
> subnetwork as your linux (virtual) one, which is different
> from my setup. Let's try & establish if connectivity is alright
> before thinking of a graphical session.
>
> Can you try pinging windows from colinux/debian
>   $ ping 10.252.248.152
>
> then colinux/debian from windows
>   c:> ping 10.0.2.15
>
> if that is working, then try installing vncserver (as root)
> # apt-get install vncserver
>
> then start it as suggested in my list reply, and try
> connecting from a windows vnc client to 10.0.2.15:1
>
> ----- Original Message ----- From: "Ben Brannen" <ben...@gm...>
> To: "baldyeti" <e_...@ho...>
> Sent: Thursday, August 20, 2009 9:18 PM
> Subject: Re: [coLinux-users] vnc step by step needed
>
>
> Thank you for responding:
>
> * apt-get-update = yes
>
> * ping colinux.org = no replies with
> PING colinux.org (216.34.181.97) 56(84) bytes of data....and hangs (I
> suppose it would eventually time-out)
>
> * start sshd? - I don't know how to do this.
>
> logged in as root:
> colinux:~# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:ff:11:17:a6:00
>         inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
>         inet6 addr: fe80::2ff:11ff:fe17:a600/64 Scope:Link
>         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>         RX packets:4605 errors:0 dropped:0 overruns:0 frame:0
>         TX packets:1900 errors:0 dropped:0 overruns:0 carrier:0
>         collisions:0 txqueuelen:1000
>         RX bytes:6551008 (6.2 MiB)  TX bytes:118882 (116.0 KiB)
>         Interrupt:10
>
> lo        Link encap:Local Loopback
>         inet addr:127.0.0.1  Mask:255.0.0.0
>         inet6 addr: ::1/128 Scope:Host
>         UP LOOPBACK RUNNING  MTU:16436  Metric:1
>         RX packets:34 errors:0 dropped:0 overruns:0 frame:0
>         TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
>         collisions:0 txqueuelen:0
>         RX bytes:2384 (2.3 KiB)  TX bytes:2384 (2.3 KiB)
>
> colinux:~#
>
> from windows host:
> private info is x'd  out
> C:\>ipconfig
>
> Windows IP Configuration
>
>
> Ethernet adapter Intel PRO1000 MT Network Connection:
>
>       Connection-specific DNS Suffix  . : xxxxxxxx.xxx
>       IP Address. . . . . . . . . . . . : 10.252.248.152
>       Subnet Mask . . . . . . . . . . . : 255.255.255.0
>       Default Gateway . . . . . . . . . : 10.252.248.1
>
> Ethernet adapter TAP-Win32 Adapter V8 (coLinux):
>
>       Connection-specific DNS Suffix  . :
>       IP Address. . . . . . . . . . . . : 192.168.37.10
>       Subnet Mask . . . . . . . . . . . : 255.255.255.0
>       Default Gateway . . . . . . . . . :
>
> C:\>
>
> -ben
>
>
>
> On Thu, Aug 20, 2009 at 1:14 PM, baldyeti<e_...@ho...> wrote:
>>
>> I think we need a bit more information, Ben:
>>
>> have you got the network connectivity working at all, eg running
>> "apt-get update" from colinux (or simply "ping colinux.org",
>> for that matter), and conversely connecting from the windows side
>> to your colinux instance (typically using putty after having started
>> sshd on the colinux side) ?
>>
>> I have occasionally run vnc myself (tightvncserver debian package)
>> I start it from the colinux console typing
>> "vncserver -geometry 1024x768 -depth 24"
>>
>> Then I use tightvnc (vnc viewer) on the windows side (colinux-ip:1),
>> and am presented with a KDE desktop.
>>
>>
>> On 19/08/2009 21:44, Ben Brannen wrote:
>>>
>>> I need step by step instructions to setup - use a remote i.e. vnc or
>>> like connection to present a desktop - I'm trying jwm - but would be
>>> happy with even a blank gray screen for starters.
>>>
>>> I've tried for several days using several different methods and have
>>> had no luck.
>>> I think the problem might be in the way the IP's are configured but
>>> I'm not sure.
>>>
>>> What I need is this format:
>>> 1 key this in
>>> 2 set this value... located here.... to ....
>>> 3 key that in....
>>> etc....
>>>
>>> Several blogs, webpages etc have some of it and each web page assumes
>>> we know too much and is written as more of a refresher than a true
>>> step by step. I'm unable to reconcile it all.
>>>
>>> I've loaded co-linux with no problems. That was the easy part. Using
>>> a debian distro (default download) and it works great! I've started
>>> (or tried to start) the vnc / X servers / etc... But when I try to
>>> remote I get ..Connection refused.... I've tried RealVNC, TightVNC, IP
>>> from ifconfig, IP from Windows co-linux network connection,
>>> with/without :1, or :2 appended to the IP and several other
>>> combination's.
>>>
>>> Any help is greatly appreciated.
>>>
>>> -ben
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>>> 30-Day
>>> trial. Simplify your report design, integration and deployment - and
>>> focus on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and focus
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>
>

Re: [coLinux-users] vnc step by step needed

[baldyeti <e_...@ho...>]

I think we need a bit more information, Ben:

have you got the network connectivity working at all, eg running
"apt-get update" from colinux (or simply "ping colinux.org",
for that matter), and conversely connecting from the windows side
to your colinux instance (typically using putty after having started
sshd on the colinux side) ?

I have occasionally run vnc myself (tightvncserver debian package)
I start it from the colinux console typing
	"vncserver -geometry 1024x768 -depth 24"

Then I use tightvnc (vnc viewer) on the windows side (colinux-ip:1),
and am presented with a KDE desktop.


On 19/08/2009 21:44, Ben Brannen wrote:
> I need step by step instructions to setup - use a remote i.e. vnc or
> like connection to present a desktop - I'm trying jwm - but would be
> happy with even a blank gray screen for starters.
> 
> I've tried for several days using several different methods and have
> had no luck.
> I think the problem might be in the way the IP's are configured but
> I'm not sure.
> 
> What I need is this format:
> 1 key this in
> 2 set this value... located here.... to ....
> 3 key that in....
> etc....
> 
> Several blogs, webpages etc have some of it and each web page assumes
> we know too much and is written as more of a refresher than a true
> step by step.  I'm unable to reconcile it all.
> 
> I've loaded co-linux with no problems.  That was the easy part.  Using
> a debian distro (default download) and it works great!  I've started
> (or tried to start) the vnc / X servers / etc... But when I try to
> remote I get ..Connection refused.... I've tried RealVNC, TightVNC, IP
> from ifconfig, IP from Windows co-linux network connection,
> with/without :1, or :2 appended to the IP and several other
> combination's.
> 
> Any help is greatly appreciated.
> 
> -ben
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july

[coLinux-users] vnc step by step needed

[Ben B. <ben...@gm...>]

I need step by step instructions to setup - use a remote i.e. vnc or
like connection to present a desktop - I'm trying jwm - but would be
happy with even a blank gray screen for starters.

I've tried for several days using several different methods and have
had no luck.
I think the problem might be in the way the IP's are configured but
I'm not sure.

What I need is this format:
1 key this in
2 set this value... located here.... to ....
3 key that in....
etc....

Several blogs, webpages etc have some of it and each web page assumes
we know too much and is written as more of a refresher than a true
step by step.  I'm unable to reconcile it all.

I've loaded co-linux with no problems.  That was the easy part.  Using
a debian distro (default download) and it works great!  I've started
(or tried to start) the vnc / X servers / etc... But when I try to
remote I get ..Connection refused.... I've tried RealVNC, TightVNC, IP
from ifconfig, IP from Windows co-linux network connection,
with/without :1, or :2 appended to the IP and several other
combination's.

Any help is greatly appreciated.

-ben

Re: [coLinux-users] install colinux-driver without administrator privileges

[Henry N. <hen...@ar...>]

Hello Peter

At 13.08.2009 11:50, Bojtos I. Péter wote:
> I have a problem, which I can't solve. My idea was put everything 
> belongs to Colinux to a pendrive and run it everywhere i go. But when 
> I runned coLinux on windows as a normal user, it failed to start (with 
> no driver installed), I tried to install it with 'colinux-daemon 
> --install-driver' but it also failed as a normal user. (not enough 
> privileges to do that)
> Is there a solution to install driver without administrator privileges?

No, you can't. Only administrators or users of this group can install 
drivers.

-- 
Henry N.