colinux-users — coLinux users mailing list

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

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

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" />

I hope it helps.

-- Tomas

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

[<mas...@wp...>]

Ryan Krauss wrote:

> Please help me.
>
>  
>
[...]

> 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).
>
In this case you should use the briged networking.
I had similar situation (but with Windows 2000) -- a private network of 
192.168.0.x.



-- 
Pozdrofka,
Mariusz Maslowski

"He used to have hobbies, but he is now a proud father instead."  -- Oren Etzioni

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

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

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] Fw: From Argentina - Network problem.

[<joc...@ho...>]

Pardon, but my ingles is pesimo, in the first place I want to =
congratulate to or to the creators of this product, who to where I could =
see works of 10, excellent.  My consultation goes directed by the part =
of network or network, since profit not to make the update of the Debian =
to be able to see the KDE.  Reason why I could read and understand if =
coLinux is connected with Windows 2000, when doing ping of anyone of the =
two sides are not tendrian that to lose the messages.  I have all equal =
one to which they enunciate notes, but nothing.  That it can be, is =
algun example of like connecting to me.

thanks.

Javier Osvaldo Ch=E9rcoles




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

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

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

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

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

[Jeff W. <Kaz...@ce...>]

At 7/4/2004 04:53 PM -0300, Javier Osvaldo Ch=E9rcoles wrote:
>Perdonen, pero mi ingles es pesimo, en primer lugar quiero felicitar al o=
=20
>a los creadores de este producto, que hasta donde pude ver funciona de 10,=
=20
>excelente.
>Mi consulta va dirigida por la parte de red o network, ya que no logro=20
>hacer la actualizaci=F3n del Debian para poder ver el KDE. Por lo que pude=
=20
>leer y entender si coLinux se conecta con Windows 2000, al hacer un ping=20
>de cualquiera de los dos lados no se tendrian que perder los mensajes.
>Tengo todo igual a lo que enuncian las notas, pero nada. Que puede ser,=20
>hay algun ejemplo de como conectarme.
>
>Saludos.

Which http://www.google.com/language_tools translates [with trivial=20
editing] to:

>Pardon, but my English is poor, in the first place I want to congratulate=
=20
>to or to the creators of this product, who to where I could see works of=20
>10, excellent.
>
>My consultation goes directed by the part of network or network, since=20
>profit not to make the update of the Debian to be able to see the=20
>KDE.  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 tendrian=
=20
>that to lose the messages.
>
>I have all equal one to which they enunciate notes, but nothing.  That it=
=20
>can be, is again example of like connecting to me.
>
>Greetings.
>
>Javier Osvaldo Consulting
>Ch=E9rcoles Ulises

I don't know if that made it much clearer or not.

--
Jeff Woods <kaz...@ce...>=20

RE: [coLinux-users] From Argentina - Network problem.

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

if you want to get help wending your message in english is adviseable
  -----Original Message-----
  From: col...@li...
[mailto:col...@li...]On Behalf Of Javier
Osvaldo Ch=E9rcoles
  Sent: 04 July 2004 20:54
  To: col...@li...
  Subject: [coLinux-users] From Argentina - Network problem.


  Perdonen, pero mi ingles es pesimo, en primer lugar quiero felicitar al=
 o
a los creadores de este producto, que hasta donde pude ver funciona de 10=
,
excelente.
  Mi consulta va dirigida por la parte de red o network, ya que no logro
hacer la actualizaci=F3n del Debian para poder ver el KDE. Por lo que pud=
e
leer y entender si coLinux se conecta con Windows 2000, al hacer un ping =
de
cualquiera de los dos lados no se tendrian que perder los mensajes.
  Tengo todo igual a lo que enuncian las notas, pero nada. Que puede ser,
hay algun ejemplo de como conectarme.

  Saludos.

  Javier Osvaldo Ch=E9rcoles
  Consultora Ulises
  02323437354 - 0232315530879
  www.chercoles.com.ar
  jav...@mu...


  ---
  Outgoing mail is certified Virus Free.
  Checked by AVG anti-virus system (http://www.grisoft.com).
  Version: 6.0.713 / Virus Database: 469 - Release Date: 30/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] From Argentina - Network problem.

[<joc...@ho...>]

Perdonen, pero mi ingles es pesimo, en primer lugar quiero felicitar al =
o a los creadores de este producto, que hasta donde pude ver funciona de =
10, excelente.
Mi consulta va dirigida por la parte de red o network, ya que no logro =
hacer la actualizaci=F3n del Debian para poder ver el KDE. Por lo que =
pude leer y entender si coLinux se conecta con Windows 2000, al hacer un =
ping de cualquiera de los dos lados no se tendrian que perder los =
mensajes.
Tengo todo igual a lo que enuncian las notas, pero nada. Que puede ser, =
hay algun ejemplo de como conectarme.

Saludos.

Javier Osvaldo Ch=E9rcoles
Consultora Ulises
02323437354 - 0232315530879
www.chercoles.com.ar
jav...@mu...


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

Re: [coLinux-users] problems getting linux.sys to load

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

On Sun, Jul 04, 2004 at 03:23:06AM +0100, peter green wrote:
> on win2k advanced server accessing via terminal services
> this is the second person i have had report this to me
> 
> does anyone know what causes this and if anything can be done about it
> 

This could be a namespace issue. 
On a terminal server, services use the global namespace by default, whereas
clients have a session namespace. There is a "Global\" prefix to be used by
client processes to manipulate the global namespace, which colinux-daemon
seems to lack in this case.

Anyway, devel-list is a much beter place to discuss this.

Re: [coLinux-users] help setting up a dual boot system

[Dwight C. <da...@po...>]

I've had no real issues with upgrading colinux in-place, your mileage may vary.

d.c.

On Sun, 4 Jul 2004, Samir Kuthiala wrote:

>thx. i'll definitely try this.
>
>on a side note, can i just install a new version of colinux over my
>existing ver or do I need to uninstall and then install?
>
>~Samir
>


| dwight a. campbell : da...@po...  : http://rats.darktech.org/ |
| linux guru in training : reality avoidance therapist for hire : KD7KJG |
| when you live in a sick society, just about everything you do is wrong |

Re: [coLinux-users] help setting up a dual boot system

[Samir K. <sam...@gm...>]

thx. i'll definitely try this. 

on a side note, can i just install a new version of colinux over my
existing ver or do I need to uninstall and then install?

~Samir


On Fri, 2 Jul 2004 11:45:30 -0700 (PDT), Dwight Campbell
<da...@po...> wrote:
> 
> Eh, here's the cheap-n-nasty solution I'm using for that....
> 
> (colinux 20040622, slackware 10.0)
> 
> First thing in /etc/rc.d/rc.S is add at the top
> 
> /sbin/mount -o remount,rw /
> /etc/rc.d/rc.VerHack
> /sbin/mount -o remount,ro /
> 
> the contents of rc.VerHack are
> 
> #!/bin/sh
> # version workarounds.  Bah!
> 
> echo "Applying ugly kernel version hacks (colinux vs. real linux)"
> /bin/rm /etc/fstab
> /bin/rm /etc/lilo.conf
> /bin/rm /opt/kde/share/config/kdm/Xservers
> /bin/rm /usr/src/linux
> 
> if uname -r | grep "co-" ; then
>  ln -s /etc/fstab.colinux /etc/fstab
>  ln -s /etc/lilo.conf.colinux /etc/lilo.conf
>  ln -s /opt/kde/share/config/kdm/Xservers.colinux /opt/kde/share/config/kdm/Xservers
>  ln -s /usr/src/linux-2.6.7-co-0.6.2 /usr/src/linux
> else
>  ln -s /etc/fstab.reallinux /etc/fstab
>  ln -s /etc/lilo.conf.reallinux /etc/lilo.conf
>  ln -s /opt/kde/share/config/kdm/Xservers.reallinux /opt/kde/share/config/kdm/Xservers
>  ln -s /usr/src/linux-2.6.7 /usr/src/linux
> fi
> 
> Substitute config files as needed for differrences between real hardware and
> colinux boot.  This approach has a few downsides, such as possibly borking
> system sanity checks at boot time.  Wouldn't want to use anything even vaguely
> resembling in a production environment, etc etc.
> 
> Hope this helps,
> d.c.
> 
> On Thu, 1 Jul 2004, Samir Kuthiala wrote:
> 
> >Hi
> >
> >I have been trying to get the colinux to work on my dual boot system
> >(win2k pro + RH9) for the last few days but with no success. heres a
> >summary of what I have done so far
> >
> >1. create /dev/cobd0 to /dev/cobd7 using mknod
> >2. installed colinux 0.6.1without downloading the Debian/Gentoo image.
> >modified the config file to this...
> >===============================================
> ><colinux>
> >       <block_device index="0" path="\Device\HarddiskVolume2" enabled="true" />
> >        <block_device index="1" path="\Device\HarddiskVolume3" enabled="true" />
> >    <bootparams>root=/dev/cobd0</bootparams>
> >    <image path="vmlinux" />
> >    <memory size="64" />
> >    <network index="0" type="tap" name="tap" />
> ></colinux>
> >===============================================
> >3. copied the kernel modules packaged along with colinux into the
> >/lib/modules dir
> >
> >I then tried to boot the colinux. failed with some error about unable
> >to locate /dev/hda3 (thats my root partition). I assumed this was due
> >to me not having modified fstab. I then modified fstab to remove all
> >references to /dev/hd* and added in /dev/cobd0 (as root) and
> >/dev/cobd1 as swap. However the bootup sequence still fails with some
> >error message about invalid superblock.
> >
> >I have gone through the website/forums/wiki and am just about to give
> >up. Can somebody help me figure out whats going wrong?
> >
> >Thanks
> >Samir
> >
> >
> >-------------------------------------------------------
> >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
> >
> 
> | dwight a. campbell : da...@po...  : http://rats.darktech.org/ |
> | linux guru in training : reality avoidance therapist for hire : KD7KJG |
> | when you live in a sick society, just about everything you do is wrong |
> 
> 
> 
> 
> -------------------------------------------------------
> 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] tap driver very slow

[Peng <rin...@gm...>]

The tricky thing is that, each time you do "ping google.com", you are
pinging a different
IP address....

-- Peng

On Fri, 2 Jul 2004 09:31:42 +0800, Samir Kuthiala
<sam...@gm...> wrote:
> Hello
> 
> My tap driver is really slow. eg: it take 200+ ms to ping google from
> linux while it takes only 30+ ms from windows. has anyone experienced
> this before?
> 
> Also the tap driver seems to connect to internet whether I turn on the
> internet sharing or not. I was quite surprised by this as the wiki
> explains in great detail how to setup the virtual network.
> 
> -Samir
> 
> -------------------------------------------------------
> 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] About the colinux homepage...

[Peng <rin...@gm...>]

I have been talking about colinux with many of my friends ... I found
some common misunderstanding from these people because they just saw
these from www.colinux.org:

"In its current condition, it allows us to run the KNOPPIX Japanese
Edition on Windows (see Screenshots). "

And they don't even want to give a try ...  just because they don't
want to run the KNOPPIX Japanese Edition!  I think that description is
kind of confusing and it should be changed ... at least say that

1) It can run almost any existing distribution including debian &
gentoo & redhat & whatever.
2) It can boot your existing linux partitions on the harddrive

Best Regards,

Peng

[coLinux-users] problems getting linux.sys to load

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

on win2k advanced server accessing via terminal services
this is the second person i have had report this to me

does anyone know what causes this and if anything can be done about it

C:\Program Files\coLinux>colinux-daemon --remove-driver
Cooperative Linux Daemon, 0.6.1
Compiled on Sat May 29 16:20:11 2004

colinux: manager open: last error: The system cannot find the file
specified.
daemon: couldn't get driver handle, removing anyway
driver: stopping driver service
driver: removing driver service

C:\Program Files\coLinux>colinux-daemon --install-driver
Cooperative Linux Daemon, 0.6.1
Compiled on Sat May 29 16:20:11 2004

daemon: loading C:\Program Files\coLinux\linux.sys
colinux: manager open: last error: The system cannot find the file
specified.
daemon: error opening kernel driver

C:\Program Files\coLinux>

please use reply all as the person who reported this to me is not on the
mailing list
---
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

---
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

Re: [coLinux-users] help setting up a dual boot system

[Dwight C. <da...@po...>]

Eh, here's the cheap-n-nasty solution I'm using for that....

(colinux 20040622, slackware 10.0)

First thing in /etc/rc.d/rc.S is add at the top

/sbin/mount -o remount,rw /
/etc/rc.d/rc.VerHack
/sbin/mount -o remount,ro /

the contents of rc.VerHack are

#!/bin/sh
# version workarounds.  Bah!

echo "Applying ugly kernel version hacks (colinux vs. real linux)"
/bin/rm /etc/fstab
/bin/rm /etc/lilo.conf
/bin/rm /opt/kde/share/config/kdm/Xservers
/bin/rm /usr/src/linux

if uname -r | grep "co-" ; then
  ln -s /etc/fstab.colinux /etc/fstab
  ln -s /etc/lilo.conf.colinux /etc/lilo.conf
  ln -s /opt/kde/share/config/kdm/Xservers.colinux /opt/kde/share/config/kdm/Xservers
  ln -s /usr/src/linux-2.6.7-co-0.6.2 /usr/src/linux
else
  ln -s /etc/fstab.reallinux /etc/fstab
  ln -s /etc/lilo.conf.reallinux /etc/lilo.conf
  ln -s /opt/kde/share/config/kdm/Xservers.reallinux /opt/kde/share/config/kdm/Xservers
  ln -s /usr/src/linux-2.6.7 /usr/src/linux
fi


Substitute config files as needed for differrences between real hardware and
colinux boot.  This approach has a few downsides, such as possibly borking
system sanity checks at boot time.  Wouldn't want to use anything even vaguely
resembling in a production environment, etc etc.


Hope this helps,
d.c.

On Thu, 1 Jul 2004, Samir Kuthiala wrote:

>Hi
>
>I have been trying to get the colinux to work on my dual boot system
>(win2k pro + RH9) for the last few days but with no success. heres a
>summary of what I have done so far
>
>1. create /dev/cobd0 to /dev/cobd7 using mknod
>2. installed colinux 0.6.1without downloading the Debian/Gentoo image.
>modified the config file to this...
>===============================================
><colinux>
>	<block_device index="0" path="\Device\HarddiskVolume2" enabled="true" />
>	 <block_device index="1" path="\Device\HarddiskVolume3" enabled="true" />
>    <bootparams>root=/dev/cobd0</bootparams>
>    <image path="vmlinux" />
>    <memory size="64" />
>    <network index="0" type="tap" name="tap" />
></colinux>
>===============================================
>3. copied the kernel modules packaged along with colinux into the
>/lib/modules dir
>
>I then tried to boot the colinux. failed with some error about unable
>to locate /dev/hda3 (thats my root partition). I assumed this was due
>to me not having modified fstab. I then modified fstab to remove all
>references to /dev/hd* and added in /dev/cobd0 (as root) and
>/dev/cobd1 as swap. However the bootup sequence still fails with some
>error message about invalid superblock.
>
>I have gone through the website/forums/wiki and am just about to give
>up. Can somebody help me figure out whats going wrong?
>
>Thanks
>Samir
>
>
>-------------------------------------------------------
>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
>

| dwight a. campbell : da...@po...  : http://rats.darktech.org/ |
| linux guru in training : reality avoidance therapist for hire : KD7KJG |
| when you live in a sick society, just about everything you do is wrong |

[coLinux-users] Networking problems (0.6.1)

[Andrew L. <ad...@ke...>]

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.

No changes to my normal nic config except to active the connection
sharing. I notice that there is a 'configuration' button which brings
up a menu of the services allowed, I've activated them all for the
moment.

The linux setup has had it's dns setup changed to the same servers as
the tap and normal interfaces. the address remains 192.168.0.40 with
192.168.0.1 as the router.

With this setup I can't ping/ftp/telnet anywhere, dns does not
function, however, from the windows command line I can ping the linux
vm.

As far as I can see I've done everything, can anyone spot a mistake or
a step missed? Blow is the nic part of the console startup message.

pipe client 0/6: Connecting to daemon...
pipe client 0/6: Connection established
conet-daemon: searching TAP device named "TAP Adapter"
conet-daemon: found TAP device named "TAP Adapter"
conet-daemon: opening TAP: "TAP Adapter"
conet-daemon: driver version 7.1
conet-daemon: enabling TAP...
pipe client 0/8: Connecting to daemon...
pipe client 0/8: Connection established
Cooperative Linux Daemon, 0.6.1
Compiled on Sat May 29 16:20:11 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 Adapter" -i 0
daemon: launching console
executing: colinux-console-fltk -a 0
Linux version 2.4.26-co-0.6.1 (ka...@ca...) (gcc version 3.3.3
(Debian 20040429)) #1 Sat May 29 15:30:37 IDT 2004
64MB LOWMEM available.


       thanks

                Andrew

Andrew Lawson
Kerridge Computer Company
Automotive Technical Dept
Tres Cantos, Espa=F1a

RE: [coLinux-users] Problems with vncserver

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

If you prefer not to edit it on the console... using nano or vim or what =
other editor your linux install has... you can copy it to a windows =
share using smb.

mount -t smbfs //<winsysname>/<sharename> /mnt/net -o =
uid=3D<youruserid>,gid=3Dusers,user=3D<windowsusercode>,password=3D<windo=
wspassword>

Something like that! Perhaps the order of options is wrong. Perhaps it's =
passwd instead of password, or another option is misspelled.... but =
hopefully you'll get the idea and hopefully the manuals will guide you =
further.

greetings,

--Tim

-----Original Message-----
From: lor...@in... [mailto:lor...@in...]
Sent: vrijdag 2 juli 2004 15:18
To: Leeuw van der, Tim
Subject: RE: [coLinux-users] Problems with vncserver


I can try all on monday morning, after I'll tell you.
How can I export a text file like Xsession from the Colinux console to a =
windows
system?

Thanks.
Lorenzo


---------- Initial Header -----------

From      : "Leeuw van der, Tim" tim...@nl...
To          : lor...@in...,"colinux-users"
col...@li...

Cc          :=20
Date      : Fri, 2 Jul 2004 13:42:56 +0200
Subject : RE: [coLinux-users] Problems with vncserver

> Hi,
>=20
> Which applications are started exactly in /etc/X11/XSession? Are any
applications started at all? What if you launch an xterm on display =
colinux:1
after starting the vncserver?
>=20
> greetings,
>=20
> --Tim
>=20
> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of
> lor...@in...
> Sent: vrijdag 2 juli 2004 13:36
> To: colinux-users
> Subject: [coLinux-users] Problems with vncserver
>=20
>=20
> I'm trying to use Colinux with VNC in windows 2000.  I've done all the =
things
are described in "Getting started long" and in "XCo Linux" for use "VNC =
without
XDMCP".
> When I launch the command:
>=20
> vncserver :1 -geometry 1024x768 -depth 16
>=20
> the output is:
>=20
> xauth: (argv):1: bad display name "colinux:1" in "add" command
> New 'X' desktop is colinux:1
> Starting applications specified in /etc/X11/Xsession
> Log file is /root/.vnc/colinux:1.log
> colinux:/#
>=20
> When I use VNC VIEWER to connect to 192.168.0.40:1 I can loogin but =
then I can
only view a gray screen with mouse and nothing else happens.
> Thanks for help.
> Lorenzo
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20
> digital self defense, top technical experts, no vendor pitches,=20
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> coLinux-users mailing list
> coL...@li...

> https://lists.sourceforge.net/lists/listinfo/colinux-users
>=20

Re: [coLinux-users] Problems with vncserver

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

Hello Lorenzo,

On Friday, Jul 2, 2004, at 06:36 US/Central, lor...@in... 
wrote:
> When I use VNC VIEWER to connect to 192.168.0.40:1 I can loogin but 
> then I can only view a gray screen with mouse and nothing else > 
> happens.

These are my notes on getting VNC to work on win2k using a slightly 
older version of the colinux binaries and the debian root filesystem:

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

The key commands are that one needs to install a window manager (I 
happen to have used fluxbox, but kde, gnome, tab, etc. should world 
similarly):

   apt-get install x-window-system-core vncserver fluxbox xterm

and one needs to modify the ~/.vnc.startupx to point to that window 
manager:

   mkdir ~/.vnc && echo -e '#!/bin/bash\nfluxbox &' > ~/.vnc/startupx

Hope this helps and let us know how things go.

Regards,
- Robert

RE: [coLinux-users] Problems with vncserver

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

Hi,

Which applications are started exactly in /etc/X11/XSession? Are any =
applications started at all? What if you launch an xterm on display =
colinux:1 after starting the vncserver?

greetings,

--Tim

-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of
lor...@in...
Sent: vrijdag 2 juli 2004 13:36
To: colinux-users
Subject: [coLinux-users] Problems with vncserver


I'm trying to use Colinux with VNC in windows 2000.  I've done all the =
things are described in "Getting started long" and in "XCo Linux" for =
use "VNC without XDMCP".
When I launch the command:

vncserver :1 -geometry 1024x768 -depth 16

the output is:

xauth: (argv):1: bad display name "colinux:1" in "add" command
New 'X' desktop is colinux:1
Starting applications specified in /etc/X11/Xsession
Log file is /root/.vnc/colinux:1.log
colinux:/#

When I use VNC VIEWER to connect to 192.168.0.40:1 I can loogin but then =
I can only view a gray screen with mouse and nothing else happens.
Thanks for help.
Lorenzo



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

[coLinux-users] Problems with vncserver

[lorenzo\.perone\@inwind\.it <lor...@in...>]

I'm trying to use Colinux with VNC in windows 2000.  I've done all the th=
ings are described in "Getting started long" and in "XCo Linux" for use "=
VNC without XDMCP".
When I launch the command:

vncserver :1 -geometry=
 1024x768 -depth 16

the output is:

xauth: (argv):1: bad display nam=
e "colinux:1" in "add" command
New 'X' desktop is colinux:1
Starting ap=
plications specified in /etc/X11/Xsession
Log file is /root/.vnc/colinux=
:1.log
colinux:/#

When I use VNC VIEWER to connect to 192.168.0.40:1 =
I can loogin but then I can only view a gray screen with mouse and nothin=
g else happens.
Thanks for help.
Lorenzo

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

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

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

[coLinux-users] tap driver very slow

[Samir K. <sam...@gm...>]

Hello

My tap driver is really slow. eg: it take 200+ ms to ping google from
linux while it takes only 30+ ms from windows. has anyone experienced
this before?

Also the tap driver seems to connect to internet whether I turn on the
internet sharing or not. I was quite surprised by this as the wiki
explains in great detail how to setup the virtual network.

-Samir

Re: [coLinux-users] help setting up a dual boot system

[Samir K. <sam...@gm...>]

hmmm sounds like a good idea. it should be quite straight forward.
i'll try it :)


On Thu, 1 Jul 2004 17:30:21 -0400, Peng <rin...@gm...> wrote:
> 
> I once attempted to do some hack with the "init=" boot option to make
> colinux boot with a different init script. But it turns out that
> colinux is running so well that I never needed to boot my "real" linux
> again... so I haven't actually tried it yet :P
> 
> On Fri, 2 Jul 2004 01:03:59 +0800, Samir Kuthiala
> 
> <sam...@gm...> wrote:
> >
> > Hi
> >
> > Thanks for all the suggestions. I finally got it to work... sort of.
> > basically in short I had to remove allr eferences in /etc/fstab to
> > /dev/*.  Also I had to enable fastboot in /etc/rc.d/rc/sysinit
> >
> > There are still some errors regarding some fonts, inability to load
> > usb drivers and at every bootup my system keeps prompting me to change
> > hardware config etc. but the system as such is working fine. I am able
> > to connect to an external Xserver and run my programs.
> >
> > However I had to modify my fstab quite a bit to make my dual boot
> > work. (to a point where I am unable to load linux normally :(
> >
> > Does anyone know of a way to switch fstabs depending on which kernel
> > is loaded? or maybe another mechanism to handle device differences
> > between different bootup sequences.
> >
> > Thanks
> > Samir
> >
> >
> >
> >
> > On Thu, 1 Jul 2004 06:41:59 -0400, Peng <rin...@gm...> wrote:
> > >
> > > I am pretty sure that the problem is caused by fsck attempting to
> > > access /dev/hda3.  Try to find out where this hda3 comes from, and
> > > change it to /dev/cobd0.
> > >
> > > On Thu, 1 Jul 2004 18:33:15 +0800, Samir Kuthiala
> > >
> > > <sam...@gm...> wrote:
> > > >
> > > > tried both /dev/cobd0 and /dev/cobd/0. no change. in the repair fs i
> > > > tried doing cat /etc/mtab and the partition which is mounted is
> > > > /dev/hda3
> > > >
> > > >
> > > >
> > > > On Thu, 1 Jul 2004 05:55:36 -0400, Peng <rin...@gm...> wrote:
> > > > >
> > > > > Oops.  Try the following:
> > > > >
> > > > > give root password and enter the "repair fs" shell
> > > > >
> > > > > ls -l /dev/cobd0
> > > > >
> > > > > see if that device exists....  sometime devfs put that device into /dev/cobd/0
> > > > > if that's the case, you can either modify fstab or create a symbolic link from
> > > > > /dev/cobd0 --> /dev/cobd/0
> > > > >
> > > > > let me know if it works...
> > > > >
> > > > > -- Peng
> > > > >
> > > > > On Thu, 1 Jul 2004 17:51:19 +0800, Samir Kuthiala
> > > > >
> > > > > <sam...@gm...> wrote:
> > > > > >
> > > > > > I have already tried that. no difference. It stops at loading the root
> > > > > > partition which is pretty funny considering that afterwards it throws
> > > > > > me into the "Repair Filesystem" shell. And I can see the entire linux
> > > > > > partition and browse through it from within co-linux.
> > > > > >
> > > > > >
> > > > > > On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote:
> > > > > > >
> > > > > > > Try:
> > > > > > >
> > > > > > > <block_device index="0" path="\Device\HarddiskVolume3" enabled="true"
> > > > > > > />
> > > > > > >
> > > > > > > And disable your swap partition.  Once the basic system works you can keep going
> > > > > > > and add the swap thing...
> > > > > > >
> > > > > > > Good luck,
> > > > > > >
> > > > > > > Peng
> > > > > > >
> > > > > > >
> > > > > > > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala
> > > > > > > <sam...@gm...> wrote:
> > > > > > > >
> > > > > > > > Hi
> > > > > > > >
> > > > > > > > I have been trying to get the colinux to work on my dual boot system
> > > > > > > > (win2k pro + RH9) for the last few days but with no success. heres a
> > > > > > > > summary of what I have done so far
> > > > > > > >
> > > > > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod
> > > > > > > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo image.
> > > > > > > > modified the config file to this...
> > > > > > > > ===============================================
> > > > > > > > <colinux>
> > > > > > > >        <block_device index="0" path="\Device\HarddiskVolume2" enabled="true" />
> > > > > > > >         <block_device index="1" path="\Device\HarddiskVolume3" enabled="true" />
> > > > > > > >    <bootparams>root=/dev/cobd0</bootparams>
> > > > > > > >    <image path="vmlinux" />
> > > > > > > >    <memory size="64" />
> > > > > > > >    <network index="0" type="tap" name="tap" />
> > > > > > > > </colinux>
> > > > > > > > ===============================================
> > > > > > > > 3. copied the kernel modules packaged along with colinux into the
> > > > > > > > /lib/modules dir
> > > > > > > >
> > > > > > > > I then tried to boot the colinux. failed with some error about unable
> > > > > > > > to locate /dev/hda3 (thats my root partition). I assumed this was due
> > > > > > > > to me not having modified fstab. I then modified fstab to remove all
> > > > > > > > references to /dev/hd* and added in /dev/cobd0 (as root) and
> > > > > > > > /dev/cobd1 as swap. However the bootup sequence still fails with some
> > > > > > > > error message about invalid superblock.
> > > > > > > >
> > > > > > > > I have gone through the website/forums/wiki and am just about to give
> > > > > > > > up. Can somebody help me figure out whats going wrong?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > > Samir
> > > > > > > >
> > > > > > > > -------------------------------------------------------
> > > > > > > > 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 setting up a dual boot system

[Samir K. <sam...@gm...>]

hmmm I am using 0.6.1 Isnt that the latest version?

On Thu, 1 Jul 2004 17:40:30 +0000, Patrick White <pa...@im...> wrote:
> 
> 
>        I ran into similar probelms with Win2000, colinux 0.6.0 and RH EL3.. tracked
> it down to the size of the physical partition being reported to colinux as 0.
> The zero size causes fsck of root to fail (even through the blocks can
> actually be accessed), which causes the boot to fail.  I think the physical
> partition size reporting problem has been fixed in later versions.  Fastboot
> skips the fsck on root, so that's probably why it makes things work.
>        This solution would worry me because if the root partition ever gets
> corrupted, you'll never be able to fix it without booting natively.  Might be
> worthwhile upgrading to a version with the physical partition size reporting
> fix.
> 
> later,
> patbob
> 
> 
> On Thursday 01 July 2004 5:03 pm, Samir Kuthiala wrote:
> > Hi
> >
> > Thanks for all the suggestions. I finally got it to work... sort of.
> > basically in short I had to remove allr eferences in /etc/fstab to
> > /dev/*.  Also I had to enable fastboot in /etc/rc.d/rc/sysinit
> >
> > There are still some errors regarding some fonts, inability to load
> > usb drivers and at every bootup my system keeps prompting me to change
> > hardware config etc. but the system as such is working fine. I am able
> > to connect to an external Xserver and run my programs.
> >
> > However I had to modify my fstab quite a bit to make my dual boot
> > work. (to a point where I am unable to load linux normally :(
> >
> > Does anyone know of a way to switch fstabs depending on which kernel
> > is loaded? or maybe another mechanism to handle device differences
> > between different bootup sequences.
> >
> > Thanks
> > Samir
> >
> > On Thu, 1 Jul 2004 06:41:59 -0400, Peng <rin...@gm...> wrote:
> > > I am pretty sure that the problem is caused by fsck attempting to
> > > access /dev/hda3.  Try to find out where this hda3 comes from, and
> > > change it to /dev/cobd0.
> > >
> > > On Thu, 1 Jul 2004 18:33:15 +0800, Samir Kuthiala
> > >
> > > <sam...@gm...> wrote:
> > > > tried both /dev/cobd0 and /dev/cobd/0. no change. in the repair fs i
> > > > tried doing cat /etc/mtab and the partition which is mounted is
> > > > /dev/hda3
> > > >
> > > > On Thu, 1 Jul 2004 05:55:36 -0400, Peng <rin...@gm...> wrote:
> > > > > Oops.  Try the following:
> > > > >
> > > > > give root password and enter the "repair fs" shell
> > > > >
> > > > > ls -l /dev/cobd0
> > > > >
> > > > > see if that device exists....  sometime devfs put that device into
> > > > > /dev/cobd/0 if that's the case, you can either modify fstab or create
> > > > > a symbolic link from /dev/cobd0 --> /dev/cobd/0
> > > > >
> > > > > let me know if it works...
> > > > >
> > > > > -- Peng
> > > > >
> > > > > On Thu, 1 Jul 2004 17:51:19 +0800, Samir Kuthiala
> > > > >
> > > > > <sam...@gm...> wrote:
> > > > > > I have already tried that. no difference. It stops at loading the
> > > > > > root partition which is pretty funny considering that afterwards it
> > > > > > throws me into the "Repair Filesystem" shell. And I can see the
> > > > > > entire linux partition and browse through it from within co-linux.
> > > > > >
> > > > > > On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote:
> > > > > > > Try:
> > > > > > >
> > > > > > > <block_device index="0" path="\Device\HarddiskVolume3"
> > > > > > > enabled="true" />
> > > > > > >
> > > > > > > And disable your swap partition.  Once the basic system works you
> > > > > > > can keep going and add the swap thing...
> > > > > > >
> > > > > > > Good luck,
> > > > > > >
> > > > > > > Peng
> > > > > > >
> > > > > > >
> > > > > > > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala
> > > > > > >
> > > > > > > <sam...@gm...> wrote:
> > > > > > > > Hi
> > > > > > > >
> > > > > > > > I have been trying to get the colinux to work on my dual boot
> > > > > > > > system (win2k pro + RH9) for the last few days but with no
> > > > > > > > success. heres a summary of what I have done so far
> > > > > > > >
> > > > > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod
> > > > > > > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo
> > > > > > > > image. modified the config file to this...
> > > > > > > > ===============================================
> > > > > > > > <colinux>
> > > > > > > >        <block_device index="0" path="\Device\HarddiskVolume2"
> > > > > > > > enabled="true" /> <block_device index="1"
> > > > > > > > path="\Device\HarddiskVolume3" enabled="true" />
> > > > > > > > <bootparams>root=/dev/cobd0</bootparams>
> > > > > > > >    <image path="vmlinux" />
> > > > > > > >    <memory size="64" />
> > > > > > > >    <network index="0" type="tap" name="tap" />
> > > > > > > > </colinux>
> > > > > > > > ===============================================
> > > > > > > > 3. copied the kernel modules packaged along with colinux into
> > > > > > > > the /lib/modules dir
> > > > > > > >
> > > > > > > > I then tried to boot the colinux. failed with some error about
> > > > > > > > unable to locate /dev/hda3 (thats my root partition). I assumed
> > > > > > > > this was due to me not having modified fstab. I then modified
> > > > > > > > fstab to remove all references to /dev/hd* and added in
> > > > > > > > /dev/cobd0 (as root) and /dev/cobd1 as swap. However the bootup
> > > > > > > > sequence still fails with some error message about invalid
> > > > > > > > superblock.
> > > > > > > >
> > > > > > > > I have gone through the website/forums/wiki and am just about
> > > > > > > > to give up. Can somebody help me figure out whats going wrong?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > > Samir
> > > > > > > >
> > > > > > > > -------------------------------------------------------
> > > > > > > > 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
> >
> > -------------------------------------------------------
> > 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
> 
> -------------------------------------------------------
> 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 setting up a dual boot system

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

On Fri, Jul 02, 2004 at 01:03:59AM +0800, Samir Kuthiala wrote:
> 
> There are still some errors regarding some fonts, 

that must be console fonts, I guess it's related to the way colinux kernel 
is configured

> inability to load usb drivers 

colinux kernel does not have usb drivers, but your /etc/modules.conf has 
references to it, so you get errors


> and at every bootup my system keeps prompting me to change
> hardware config etc. 

turn off kudzu, your hardware config is not the same anymore


> 
> Does anyone know of a way to switch fstabs depending on which kernel
> is loaded? or maybe another mechanism to handle device differences
> between different bootup sequences.
> 

AFAIK, some work has been started on it, you'll be able to specify a mapping 
between /dev/hdX and /dev/cobdX in config.xml. Note that version of colinux 
will be based on 2.6.x kernel.