colinux-users — coLinux users mailing list

Re: [coLinux-users] unable to install package

[floratush <flo...@ya...>]

am sorry for being so naive, but please help me out. i also have the proble=
m
of failing to connect to the debian image . it complains that connection to
backports.org couldnt be made and that hence the package is not found. then
goes ahead and says out of mmap space etc..please help me and elaborate how
exactly i should solve this problem.
I have just downloaded colinux today and hence find it illogical that the
image package its using is out of date (i could be wrong - but even then
dont know where and how to point to the current version)

NB i just want to run gcc in windows. thats how i landed on colinux

florence



Sam Moffatt wrote:
>=20
> There are a few issues here
> 1) Stable has updated twice since 3.0 (first Sarge [3.1] and now Etch
> [4.0]) so it is unlikely that the APT locations are still valid.
> 2) You're running out of allocated space for packages, this is a known
> fault when updating to Etch. See the release notes for a solution.
>=20
> I would suggest using a more recent image. I would also suggest
> acquainting yourself with the target operating system in a full
> virtual machine (e.g. one of VMWare's products) or a fully fledged
> box.
>=20
> Sam
>=20
> On 13/04/07, Wolfram Wadepohl <Wol...@ek...> wrote:
>> paulo donizete gardinalli filho schrieb:
>>
>> >     Hi, when you use debian for the first time on colinux, before any
>> > installation, you need to execute de following command:
>> > apt-get update
>> > this command will update the apt database..
>>
>> No, did not help:
>>
>> Hit http://security.debian.org stable/updates/main Packages
>> Hit http://security.debian.org stable/updates/main Release
>> Err http://www.backports.org stable/kernel-image-2.6.6-i386 Packages
>>    404 Not Found
>> Ign http://www.backports.org stable/kernel-image-2.6.6-i386 Release
>> Hit http://ftp.us.debian.org stable/main Packages
>> Hit http://ftp.us.debian.org stable/main Release
>> Hit http://ftp.us.debian.org stable/main Sources
>> Hit http://ftp.us.debian.org stable/main Release
>> Reading Package Lists...
>> Failed to fetch
>> http://www.backports.org/debian/dists/stable/kernel-image-2.6.6-i386/bin=
ary-i386/Packages
>>   404 Not Found
>> E: Dynamic MMap ran out of room
>> E: Error occured while processing wzdftpd-dev (NewPackage)
>> E: Problem with MergeList
>> /var/lib/apt/lists/ftp.us.debian.org_debian_dists_stable_main_binary-i38=
6_Packages
>> E: The package lists or status file could not be parsed or opened.
>>
>> i think the URL to the backports is no longer valid.
>> > -----Mensagem original-----
>> > De: Wolfram Wadepohl <Wol...@ek...>
>> > Para: col...@li...
>> > Data: Quinta, 12 de Abril de 2007 16:04
>> > Assunto: [coLinux-users] unable to install package
>> >
>> > Hello,
>> >
>> > i tried to install a new package into the
>> > Debian-3.0r2.ext3-mit-backports.1gb.bz2 root image.
>> >
>> > result:
>> > # apt-get install make
>> > Reading Package Lists...
>> > Building Dependency Tree...
>> > The following NEW packages will be installed:
>> >    make
>> > 0 packages upgraded, 1 newly installed, 0 to remove and 0  not
>> upgraded.
>> > Need to get 386kB of archives. After unpacking 799kB will be used.
>> > Err http://ftp.us.debian.org stable/main make 3.79.1-14
>> >    404 Not Found [IP: 35.9.37.225 80]
>> >
>> > how can i install new packages?
>>
>>
>> --
>> Sch=C3=B6ne Gr=C3=BC=C3=9Fe aus Reutlingen
>>
>> Wolfram Wadepohl
>> Forschung & Entwicklung
>>
>> E&K AUTOMATION
>> Indumat GmbH & Co. KG
>> Siemensstra=C3=9Fe 3
>> 72766 Reutlingen
>> Deutschland
>>
>> Tel.  +49 7121 514-289
>> Fax   +49 7121 514-299
>> eMail Wol...@ek...
>>        W.W...@in...
>>        W.W...@ie...
>> WWW   http://www.ek-automation.com
>>        http://www.indumat.de
>>
>> Diese Nachricht ist keine gesch=C3=A4ftliche Mitteilung i. S. des EHUG.
>>
>> Bitte senden Sie mir keine Word- oder PowerPoint- (tm Microsoft) Anh=C3=
=A4nge.
>> Senden Sie mir einfachen Text, HTML oder PDF.
>> Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html
>>
>>
>> ------------------------------------------------------------------------=
-
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your
>> opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>>
>>
>=20
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>=20
>=20

--=20
View this message in context: http://www.nabble.com/unable-to-install-packa=
ge-tf3565761.html#a10246025
Sent from the colinux-users mailing list archive at Nabble.com.

[coLinux-users] BSOD on Intel Core 2 Duo, Windows Vista

[BS R. <bsr...@gm...>]

Hi all

(I posted this to the help forum, but did not receive any response, so
trying out here)

coLinux 0.7.1 RC3 crashed with a BSOD when I tried to run it on Windows
Vista, Intel Core 2 Duo (2GB RAM). I am aware of the coLinux problem on new
CPUs and operating systems that support "noexecute" as documented here:
http://colinux.wikia.com/wiki/NoExecuteDEP

I have read people managing to run coLinux on Windows Vista on the web. So,
I just wanted to know:

a. Can coLinux 0.7.1 or 0.8.0 run on Windows Vista, Intel Core 2 Duo with
DEP setting set to default "OptIn"?

b. Does the "noexecute" problem in coLinux need to be fixed on a
per-processor basis? (as it has been done for Intel P4 and Xeon)

c. Does the fix for Intel P4 and Xeon processors allow coLinux to run on
Windows Vista (or Windows XP SP2) on those processors with DEP setting set
to default "OptIn"?

d. I am no OS expert, can someone explain (or point to an existing thread)
as to why this "noexecute" setting causes the coLinux to crash, where as
essential Windows programs and services keep running?

Answers to above questions, will rule out the doubt that I may have made an
error during my installation.

Thanks
Reddy

[coLinux-users] Vista service installation

[Francois L. <fl...@ky...>]

Hello,

I can not install "colinux-daemon @xxx --install-service xx"

I get an answer in the command line output (coming from Vista, or from
colinux ???) : "cannot open service control manager. Install failed"

Does somebody know a workaround to install it as a service (without
waiting for a colinux version) ?

Thanks by advance to all,

Regards,

Francois Liot

[coLinux-users] Vista service installation

[Francois L. <fl...@ky...>]

Hello,

I can not install "colinux-daemon @xxx --install-service xx"

I get an answer in the command line output (coming from Vista, or from
colinux ???) : "cannot open service control manager. Install failed"

Does somebody know a workaround to install it as a service (without
waiting for a colinux version) ?

Thanks by advance to all,

Regards,

Francois Liot

Re: [coLinux-users] How to speed up coLinux

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

Joaquín Seijó schrieb:
> En 24/04/2007 17:58:11, Holger Krull <hol...@gm...> escribió:
> 
>>> It's easier to set MTUs and other custom parameters for each app when  
>>> they
>>> have a dedicated tap, plus (don't know this is true however, if tap
>>> behaves exactly like a 10Mbps ethernet then it is) it avoids the
>> That 10Mps is just a label. In reality the interface is faster.
> 
> I still had better results with this setup, but as i said i'm just  
> starting to research and test, i even don't know of the internals of the  
> tap interface so i can't argue here on which choice is better.
> 
> How much faster is the interface in reality?

I assume the speed of the virtual network only depends on the speed of
the cpu. I never tested pure virtual speed, only when bridged with a
ethernet card. On a Gigabit card from realtek the transfer speed to
another computer was about 20 MByte per second (measured with netio,
both cpus 2 GHz Athlon XP).
I expect the speed to the windows host without bridging to be higher.

Re: [coLinux-users] How to speed up coLinux

[<ka...@gm...>]

En 24/04/2007 17:58:11, Holger Krull <hol...@gm...> escribió:

>> It's easier to set MTUs and other custom parameters for each app when  
>> they
>> have a dedicated tap, plus (don't know this is true however, if tap
>> behaves exactly like a 10Mbps ethernet then it is) it avoids the
>
> That 10Mps is just a label. In reality the interface is faster.

I still had better results with this setup, but as i said i'm just  
starting to research and test, i even don't know of the internals of the  
tap interface so i can't argue here on which choice is better.

How much faster is the interface in reality?

Re: [coLinux-users] How to speed up coLinux

[<ka...@gm...>]

The machine is a Pentium 4 2.66. The host is XP SP2 and i use  
Topologilinux in colinux mode (i think it's colinux 6, i don't remember  
exactly). Topologilinux 6 is based on Slackware 10.1 so it uses x.org and  
kde from that release.

Windows setup:

The real ethernet is 192.168.1.1 - it is bridged wih pcap
The taps are on different subnets, as follows:
#1 -	"SMB"	- 192.168.2.1
#2 -	"X"	- 192.168.3.1
#3 -	"ESD"	- 192.168.4.1

they are passed to colinux in the same order

Their counterparts in colinux are:
eth0: 192.168.1.2
eth1: 192.168.2.2
eth2: 192.168.3.2
eth3: 192.168.4.2

X server is Hummingbird Exceed (last version with GLX extensions so you  
can do OpenGL, it looks quite good), and i have Cygwin ESD, but i don't  
use it for now as this machine hasn't got its sound output connected. So i  
use another machine (192.168.2.3) as the esd output. For some reason i  
couldn't get Cygwin ESD to work over the ethernet so i had to use JEsd  
(http://www.jcraft.com/jesd/) there.

Linux setup:

SAMBA shares a 300G, XFS formatted hdd as the data store (this is why i  
started using colinux - i couldn't access my data from windows before  
that). One share for the TAP #1 with rw perms, and one share for the LAN  
(192.168.1.xxx) with ro perms.

As for X and esd, the variables DISPLAY and ESPEAKER are set accordingly.

Default runlevel is 4. I use KDM for login.

For playback: xmms / Xine.

The end result is each application having its own adapter for  
communication. To switch the linux esd output between the host and the  
remote machine i export ESPEAKER=espeaker and have a sed-based script  
changing the IP in /etc/hosts. This is better than changing an exported  
variable as you don't need to relogin for it to have effect.

I'm playing with different MTUs and other network parameters now to see  
what is best for each application, but this is a slow job and still don't  
have definitive results. But for the daily work it's all good! I can use  
all the adapters at once and AFAICT it haves very decent performance (yes  
with video, sound and file transfers).

Hope it helps, if you need more details ask me. I'm at work now and this  
is all i can remember from here, for more i'll have to check my system up,  
and tell you what switches i use for each app exactly.

Joaquín


En 25/04/2007 05:18:06, Julien Langlois <jul...@gm...>  
escribió:

> Hi
>
> 2007/4/24, Joaquín Seijó <ka...@gm...>:
>> With this setup i can have (after KDM login) the KDE kicker on one side  
>> of
>> the screen and the windows taskbar on the other, watch videos w/o  
>> glitches
>> and redirect the sound to the windows host or to another machine that  
>> has
>> its sound output to an amplifier to have the movies with surround sound.
>
> Could you detail your configuration please ? I've latency sound
> problem .... I can't listen sound without 2 seconds latency ... And
> the video render don't allow me to watch video correctly :(
>
> Thanks
>
>    Julien Langlois

Re: [coLinux-users] "Authentic" Linux experience

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

,
> 	I am not blessed with a computer that has working CDrom=20
> hardware
If you have a working floppy drive and network adaptor and a suitable =
internet connection you could do a floppys+network install of debian
No virus found in this outgoing message.
Checked by AVG Free Edition.=20
Version: 7.5.463 / Virus Database: 269.5.10/774 - Release Date: =
23/04/2007 17:26

Re: [coLinux-users] "Authentic" Linux experience

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

zk...@zk... schrieb:
>  Also, the idea that 
> I wouldn't really be required to do any of the bits that go along with 
> real Linux systems--compiling new kernels, etc. is a bit strange to me.  

Why would you need to compile a new kernel in a standard linux
distribution? There is really nothing strange about not doing so.

> 	I was wondering if anybody had any thoughts on how the CoLinux 
> experience might be made as authentic as possible? I'd ideally like to 
> use real Linux accessibility technology, Speakup and friends in 
> particular.  Any ideas here, or is VMWare the best option for now?

A real linux installation would be the best option if you don't need
windows.
If the speakup you mean is the project mentioned here:
http://www.linux-speakup.org/speakup.html
then you will need to compile your own colinux with the necessary
speakup patches. I assume that can be done, but as sound transfer is
still problematic in colinux, i recommend to stick with vmware server.

[coLinux-users] "Authentic" Linux experience

[<zk...@zk...>]

Hello,
	I am not blessed with a computer that has working CDrom 
hardware--at least, the hardware doesn't seem to read Gentoo or any 
other Linux distro CD very well, at least when booting.
So, I've decided to use VMWare, because that's as close to an authentic 
Linux experience as I can get--complete with the kernel and all.
CoLinux is great, but I just feel a little odd about having to use a 
Windows screen reader to read CoLinux's NT console.  Also, the idea that 
I wouldn't really be required to do any of the bits that go along with 
real Linux systems--compiling new kernels, etc. is a bit strange to me.  
So...VmWare has its problems, but...
	I was wondering if anybody had any thoughts on how the CoLinux 
experience might be made as authentic as possible? I'd ideally like to 
use real Linux accessibility technology, Speakup and friends in 
particular.  Any ideas here, or is VMWare the best option for now?
Thanks,
Zack.

Re: [coLinux-users] How to speed up coLinux

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

Joaquín Seijó schrieb:
> It's easier to set MTUs and other custom parameters for each app when they  
> have a dedicated tap, plus (don't know this is true however, if tap  
> behaves exactly like a 10Mbps ethernet then it is) it avoids the  

That 10Mps is just a label. In reality the interface is faster.

Re: [coLinux-users] How to speed up coLinux

[<ka...@gm...>]

It's easier to set MTUs and other custom parameters for each app when they  
have a dedicated tap, plus (don't know this is true however, if tap  
behaves exactly like a 10Mbps ethernet then it is) it avoids the  
possibility of running out of bandwith. I think the downside is that it  
takes a few more cpu cycles though

Finally, it's a clearer setup for me, and i just like it :D, but i have to  
make better tests yet

J

On 24/04/2007 11:11:44, Michael Livshin <gm...@cm...> wrote:
>> i use three taps: one for SAMBA, one for X and one for
>> ESD.
>
> what does this buy you compared to running all those over one TAP
> device?
>
> just curious,
> --m

Re: [coLinux-users] How to speed up coLinux

[Michael L. <gm...@cm...>]

Joaquín Seijó <ka...@gm...>
writes:

> i use three taps: one for SAMBA, one for X and one for  
> ESD.

what does this buy you compared to running all those over one TAP
device?

just curious,
--m

Re: [coLinux-users] How to speed up coLinux

[<ka...@gm...>]

Another vote here! i use three taps: one for SAMBA, one for X and one for  
ESD (will try later with its sucessor, pulseaudio) and it works perfectly,  
have tried once with VNC over tap but it didn't compared IMO with X. Also  
is worth to mention again the NX platform, which i haven't tried but  
should make things even faster.
With this setup i can have (after KDM login) the KDE kicker on one side of  
the screen and the windows taskbar on the other, watch videos w/o glitches  
and redirect the sound to the windows host or to another machine that has  
its sound output to an amplifier to have the movies with surround sound.
Try giving all colinux/X/ESD daemons ABOVE NORMAL priority! that helps too

Joaquín

En 24/04/2007 10:37:41, Mark Woodruff <mar...@gm...> escribió:

> Another vote for Tap. I've never used Slirp; perhaps that's why I
> didn't have the problems with Cygwin/X and Xming.
>
> On 4/24/07, Brendan Simon <Br...@br...> wrote:
>> I will have a go at the dual slirp/tap solution.
>>
>> I tried Xming with slirp and things like xeyes and xcalc seem to work
>> very well indeed, however, my GNOME session took forever to fire up.  I
>> mean a very very long time.  I couldn't believe it to tell you the
>> truth.  VNC was much faster.  All I can think of is that the X protocol
>> is not very efficient for things like GNOME and it ends up being better
>> to use VNC (over slow network connections such as SLIRP).
>>
>> I suspect TAP will be much better and hopefully that will make GNOME
>> more usable :)
>>
>> Cheers, Brendan.
>>
>>
>> George P Boutwell wrote:
>> > Brendan Simon wrote:
>> >
>> >> But I still don't understand why coLinux or VNC is sooooo slow.
>> > Having said this, the easiest & fastest mechanism that we (several
>> > core developers & core community members) have found to work for both
>> > Internet & network-based X/VNC display is to use eth0=SliRP for  
>> Internet
>> > and eth1=tap for X/VNC.  That is to say that SLiRP is used to allow an
>> > virtually 0 configuration internet connection, even when switching
>> > interfaces, moving around as is common with laptops.  While having a
>> > static configuration with the TAP device for X/VNC.
>> >
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] How to speed up coLinux

[Mark W. <mar...@gm...>]

Another vote for Tap. I've never used Slirp; perhaps that's why I
didn't have the problems with Cygwin/X and Xming.

On 4/24/07, Brendan Simon <Br...@br...> wrote:
> I will have a go at the dual slirp/tap solution.
>
> I tried Xming with slirp and things like xeyes and xcalc seem to work
> very well indeed, however, my GNOME session took forever to fire up.  I
> mean a very very long time.  I couldn't believe it to tell you the
> truth.  VNC was much faster.  All I can think of is that the X protocol
> is not very efficient for things like GNOME and it ends up being better
> to use VNC (over slow network connections such as SLIRP).
>
> I suspect TAP will be much better and hopefully that will make GNOME
> more usable :)
>
> Cheers, Brendan.
>
>
> George P Boutwell wrote:
> > Brendan Simon wrote:
> >
> >> But I still don't understand why coLinux or VNC is sooooo slow.
> > Having said this, the easiest & fastest mechanism that we (several
> > core developers & core community members) have found to work for both
> > Internet & network-based X/VNC display is to use eth0=SliRP for Internet
> > and eth1=tap for X/VNC.  That is to say that SLiRP is used to allow an
> > virtually 0 configuration internet connection, even when switching
> > interfaces, moving around as is common with laptops.  While having a
> > static configuration with the TAP device for X/VNC.
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] How to speed up coLinux

[Brendan S. <Br...@Br...>]

Found the setup on the wiki :)
    
http://colinux.wikia.com/wiki/UserConfigs#Networking_with_SLIRP_.28for_Internet.29_and_TAP_.28for_X_server.29

I can confirm that this works a million times (approximately) better 
than slirp.  This was with Xming/XDMCP.  I suspect VNC over TAP will be 
pretty good too.

My next step was to try out K/QEMU but now I can put that on hold unless 
something else comes up ;-)  USB ???

Thanks, Brendan.


Brendan Simon wrote:
> I will have a go at the dual slirp/tap solution.
>
> I tried Xming with slirp and things like xeyes and xcalc seem to work 
> very well indeed, however, my GNOME session took forever to fire up.  
> I mean a very very long time.  I couldn't believe it to tell you the 
> truth.  VNC was much faster.  All I can think of is that the X 
> protocol is not very efficient for things like GNOME and it ends up 
> being better to use VNC (over slow network connections such as SLIRP).
>
> I suspect TAP will be much better and hopefully that will make GNOME 
> more usable :)
>
> Cheers, Brendan.
>
>
> George P Boutwell wrote:
>> Brendan Simon wrote:
>>  
>>> But I still don't understand why coLinux or VNC is sooooo slow.
>> Having said this, the easiest & fastest mechanism that we (several
>> core developers & core community members) have found to work for both
>> Internet & network-based X/VNC display is to use eth0=SliRP for Internet
>> and eth1=tap for X/VNC.  That is to say that SLiRP is used to allow an
>> virtually 0 configuration internet connection, even when switching
>> interfaces, moving around as is common with laptops.  While having a
>> static configuration with the TAP device for X/VNC.
>>   
>
>

Re: [coLinux-users] How to speed up coLinux

[Brendan S. <Br...@Br...>]

I will have a go at the dual slirp/tap solution.

I tried Xming with slirp and things like xeyes and xcalc seem to work 
very well indeed, however, my GNOME session took forever to fire up.  I 
mean a very very long time.  I couldn't believe it to tell you the 
truth.  VNC was much faster.  All I can think of is that the X protocol 
is not very efficient for things like GNOME and it ends up being better 
to use VNC (over slow network connections such as SLIRP).

I suspect TAP will be much better and hopefully that will make GNOME 
more usable :)

Cheers, Brendan.


George P Boutwell wrote:
> Brendan Simon wrote:
>   
>> But I still don't understand why coLinux or VNC is sooooo slow.
> Having said this, the easiest & fastest mechanism that we (several
> core developers & core community members) have found to work for both
> Internet & network-based X/VNC display is to use eth0=SliRP for Internet
> and eth1=tap for X/VNC.  That is to say that SLiRP is used to allow an
> virtually 0 configuration internet connection, even when switching
> interfaces, moving around as is common with laptops.  While having a
> static configuration with the TAP device for X/VNC.
>   

Re: [coLinux-users] How to speed up coLinux

[Brendan S. <Br...@Br...>]

Thanks for the help George.  This sounds like the best solution 
currently available for X/VNC with laptops :)
Is there a wiki/faq entry on how to setup this scenario?

The virtual video device sounds very interesting and would bring coLinux 
up to par with K/QEMU with respect to GUI performance.  I've seen a 
colleague use QEMU and it looked great with the X display.  AFAICT, 
K/QEMU does not require a special kernel where as coLinux requires a 
special coLinux built kernel, so I presume coLinux is slightly faster 
than K/QEMU otherwise there would be no point, right ????

Cheers, Brendan.


George P Boutwell wrote:
> Brendan Simon wrote:
>   
>   There are some scenarios, such as VNC and X usage where the throughput
> of SLiRP and coLinux's Networking in general just aren't up to it.  This
> is a known issue and believe it or not this has been improving.  The
> speed of coLinux networking in 0.7.1 is way, way, way better than it was
> in 0.6.x
>
>   coLinux project is attacking the network performance issue as best we
> can, with the tools and resources that we have.  As someone else pointed
> out there have been some really good discussions in the past about
> changes/tweaks, etc to default networking settings that done
> carefully/correctly can drastically improve the performance (see the
> archives for details)
>
>   In addition to that we are addressing the VNC/X issue by working on an
> experimental (at this time) virtual video device driver that would (in
> theory) allow QEMU & VMWare like video for coLinux and which would
> provide better performance than the current solutions which all involve
> using the network to get video.
>
>   Having said this, the easiest & fastest mechanism that we (several
> core developers & core community members) have found to work for both
> Internet & network-based X/VNC display is to use eth0=SliRP for Internet
> and eth1=tap for X/VNC.  That is to say that SLiRP is used to allow an
> virtually 0 configuration internet connection, even when switching
> interfaces, moving around as is common with laptops.  While having a
> static configuration with the TAP device for X/VNC.
>   

Re: [coLinux-users] CoLinux logo

[Adam A. <ad...@au...>]

Henry Nestler wrote:
>>     I am completing an article on coLinux for embedded developers.
>>
>>     I would like to include the coLinux Ying/Yang image in the article.
>>     Where would I find a reasonable resolution version of the image
>>     as well as some notice a publish would consider sufficient as 
>> permission to use ?
>>     
>
> On SourgeForge under Patches you will find an SVG version of the Logo
> http://sourceforge.net/tracker/index.php?func=detail&aid=1235876&group_id=98788&atid=622065
>
> I see no problem to publish it in conjuntion with coLinux.
>   
I am certainly not a lawyer, but isn't the Microsoft logo a trademark? 
Can it be used the way the coLinux logo uses it without infringing 
Microsoft's trademark?

Adam Augustine

Re: [coLinux-users] How to speed up coLinux

[George P B. <geo...@gm...>]

Brendan Simon wrote:
> But I still don't understand why coLinux or VNC is sooooo slow.  My 
> understanding may be flawed?  Here is my thinking:
>
>     If I have a second PC running Linux and a VNC server, and connect
>     from a MSW box using a VNC server over a 100Mbps network, I get much
>     much better performance than if I use MSW/Colinux.  I'd expect
>     coLinux to get similar performance (or at least close).
>
>     Assumption: given the two OSes are on the same machine I would
>     expect network throughput would be better than two separate
>     machines.  However, I think the using the network support
>     (particulary slirp) in coLinux is as slow, if not slower, than a
>     real network
>
>     Maybe because both host OS and guess OS are so resource intensive
>     that the performance hit is extremely noticeable.  If that is the
>     case, then using any virtual OS would seem to useful only for
>     playing and doing basic things.
>
>   
  There are some scenarios, such as VNC and X usage where the throughput
of SLiRP and coLinux's Networking in general just aren't up to it.  This
is a known issue and believe it or not this has been improving.  The
speed of coLinux networking in 0.7.1 is way, way, way better than it was
in 0.6.x

  coLinux project is attacking the network performance issue as best we
can, with the tools and resources that we have.  As someone else pointed
out there have been some really good discussions in the past about
changes/tweaks, etc to default networking settings that done
carefully/correctly can drastically improve the performance (see the
archives for details)

  In addition to that we are addressing the VNC/X issue by working on an
experimental (at this time) virtual video device driver that would (in
theory) allow QEMU & VMWare like video for coLinux and which would
provide better performance than the current solutions which all involve
using the network to get video.

  Having said this, the easiest & fastest mechanism that we (several
core developers & core community members) have found to work for both
Internet & network-based X/VNC display is to use eth0=SliRP for Internet
and eth1=tap for X/VNC.  That is to say that SLiRP is used to allow an
virtually 0 configuration internet connection, even when switching
interfaces, moving around as is common with laptops.  While having a
static configuration with the TAP device for X/VNC.

HTH,

George

Re: [coLinux-users] Where is Debian Etch Root Image?

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

Henry Nestler schrieb:

> I have cleaned and trimmed it down to smaller size (39MB):
> http://www.henrynestler.com/colinux/images/Debian-4.0r0-etch.ext3.1gb.bz2
> 
> If this is OK, I upload it to SourceForge.  Please give an feedback!

> Slirp is the first network eth0, users of tap-win32 should edit
> /etc/network/interfaces.

Yes, and nano is the existing editor.

> Users should run
>    apt-get install console-tools
>    apt-get install dselect  and/or   apt-get install aptitude
> to get a fontend for installing packages.

tzconfig would be the next.
I just upgraded the image to use kdm and icewm, everything works fine.
I haven't figured out yet why the console isn't using my german keyboard
but a ssh session is.

Re: [coLinux-users] [Colinux-Users] Making image from Virtual Box

[Andrew C. <an...@ri...>]

Incidentally if anyone has one I would LOVE either a suse 10.2 or Fedora
core 6 image as a starting point since I don't have qemu setup to install my
own. 

-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of
fr...@gi...
Sent: Monday, April 23, 2007 9:48 AM
To: Cooperative Linux Users
Subject: [coLinux-users] [Colinux-Users] Making image from Virtual Box


I understand that you can change a Qemu (vcow) image into a Colinux
compatible drive image by stripping off some bytes. Has anyone been able to
due the same for a Virtual Box image?

I was able to easily install SuSe on VBox, but couldn't quite get Qemu to
properly load it...probably just me. :P

Fred

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express Download DB2 Express C - the
FREE version of DB2 express and take control of your XML. No limits. Just
data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] [Colinux-Users] Making image from Virtual Box

[<fr...@gi...>]

I understand that you can change a Qemu (vcow) image into a Colinux  
compatible drive image by stripping off some bytes. Has anyone been  
able to due the same for a Virtual Box image?

I was able to easily install SuSe on VBox, but couldn't quite get Qemu  
to properly load it...probably just me. :P

Fred

Re: [coLinux-users] Xming/XDMPC with SLIRP

[Henry N. <Hen...@Ar...>]

Brendan Simon wrote:
> Can I use Xming to connect to gdm on colinux via xdmcp ???
> 
> If so, how?  I can't ping 10.0.2.15 from my DOS prompt.  I don't think 
> the 10.0.2.15 address is visible to Windows is it?
> 
> Do I have to modify my eth0 setting in the colinux.conf file?
> eg. change:
>     eth0=slirp,00:D0:1F:99:88:99,tcp:22:22/tcp:5901:5901
> to:
>     eth0=slirp,00:D0:1F:99:88:99,tcp:22:22/tcp:5901:5901/tcp:177:177

The address 10.0.2.15 is not visable from host side.  Slirp is the 
"localhost" or your real network address.

Remember: Slirp has no ping supoort.

You can see the "open ports" directly on your Windows command prompt 
with "netstat.exe -an" as "LISTENING", or with the tool TCPview from 
Sysinternals.
Also remember, that you must open your Firewall for slirp redirections.

To connect from your Host to coLinux via slirp-redirections you should 
use localhost or 127.0.0.1.  With the example above you can connect SSH 
as localhost:22 from your Windows.  Use your IP:22 from outside of your PC.

­--
Henry

Re: [coLinux-users] CoLinux logo

[Henry N. <Hen...@Ar...>]

Hello David,

>     I am completing an article on coLinux for embedded developers.
> 
>     I would like to include the coLinux Ying/Yang image in the article.
>     Where would I find a reasonable resolution version of the image
>     as well as some notice a publish would consider sufficient as 
> permission to use ?

On SourgeForge under Patches you will find an SVG version of the Logo
http://sourceforge.net/tracker/index.php?func=detail&aid=1235876&group_id=98788&atid=622065

I see no problem to publish it in conjuntion with coLinux.

-- 
Henry