From: Brendan S. <Br...@Br...> - 2007-04-24 05:37:45
|
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. >> > > |