[opensuse-packaging] Installation: lightweight VNC server
[ This mail has been originally sent to opensuse-FACTORY] Hi, I just went through the new installation images searching for any huge binaries or libraries (or any other big files). I've found that we use Xvnc server (for remote installation). Only the binary takes 3.8 MB (of course, installation image is compressed). I'm asking here because FACTORY users have often broad knowledge of several alternatives [package maintainers too ;), of course]. Don't you know any 'better' and smaller (binary size, memory consumptions, less libraries) than the current Xvnc? Ideally we have it in build service... Of course, it has to cover the same range of features we currently use. Some hints: * FreeNX http://freenx.berlios.de/ * TightVNC http://myprogs.net/program/44ec3a0569499cc480f1fafabb8aebbb/TightVNC * any other? http://nixbit.com/search/vnc-server/ Any ideas, opinions, experience? Thanks and Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.
Lukas Ocilka wrote:
I just went through the new installation images searching for any huge binaries or libraries (or any other big files). I've found that we use Xvnc server (for remote installation). Only the binary takes 3.8 MB (of course, installation image is compressed).
I'm just thinking out loud - the vnc server is only needed if you pass vnc=1 to linuxrc, right? Now the instsys was split up into multiple images in Factory. So... is it possible / does it make sense to put the vnc part into a separate image and mount that image only when vnc is used? Of course it doesn't save space on the CD, but it might save some memory in the instsys (or not?). Just an idea :) Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Michal Marek napsal(a):
Lukas Ocilka wrote:
I just went through the new installation images searching for any huge binaries or libraries (or any other big files). I've found that we use Xvnc server (for remote installation). Only the binary takes 3.8 MB (of course, installation image is compressed).
I'm just thinking out loud - the vnc server is only needed if you pass vnc=1 to linuxrc, right? Now the instsys was split up into multiple images in Factory. So... is it possible / does it make sense to put the vnc part into a separate image and mount that image only when vnc is used? Of course it doesn't save space on the CD, but it might save some memory in the instsys (or not?).
Yes, good idea :) and already filed... ;) FATE #303513: Move parts of installation to separate image L.
On Fri, Mar 07, 2008 at 10:39:22AM +0100, Lukas Ocilka wrote:
Don't you know any 'better' and smaller (binary size, memory consumptions, less libraries) than the current Xvnc? Ideally we have it in build service... Of course, it has to cover the same range of features we currently use.
Some hints: * FreeNX http://freenx.berlios.de/ * TightVNC http://myprogs.net/program/44ec3a0569499cc480f1fafabb8aebbb/TightVNC * any other? http://nixbit.com/search/vnc-server/
I don't know, but Wikipedia has a link to a list: http://gentoo-wiki.com/VNC -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, On Fri, 7 Mar 2008 at 10:39, Lukas Ocilka wrote:
Don't you know any 'better' and smaller (binary size, memory consumptions, less libraries) than the current Xvnc?
maybe we could run a local X server with dummy drivers and use libvnc.so to export it via VNC. libvnc.so is part of the Xvnc package and has only about a tenth of the size of Xvnc binary. Another option might be to modularize Xvnc, so that it becomes a set of "hardware" driver modules for the modular X server. That way we'd save duplicating all the X server code in the Xvnc binary.
* TightVNC
We're already using the vncviewer from TightVNC, but the server is unusable for us, because it is based on a very old version of XFree86, which is not 64bit clean. Also, the "Tight" in the name refers to it's bandwith requirements rather than the size of the binaries, so we might not gain much by using the cu Reinhard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, Mar 07, 2008 at 11:58:31AM +0100, Reinhard Max wrote:
Hi,
On Fri, 7 Mar 2008 at 10:39, Lukas Ocilka wrote:
Don't you know any 'better' and smaller (binary size, memory consumptions, less libraries) than the current Xvnc?
maybe we could run a local X server with dummy drivers and use libvnc.so to export it via VNC. libvnc.so is part of the Xvnc package and has only about a tenth of the size of Xvnc binary.
There are so many issues with this module. Please use the statically built Xvnc server. It's hard enough to keep Xvnc building and working (somewhat).
Another option might be to modularize Xvnc, so that it becomes a set of "hardware" driver modules for the modular X server. That way we'd save duplicating all the X server code in the Xvnc binary.
Isn't this the same as you suggested above? Use the dummy module as video driver + libvnc.so? Plus option -sharevts as it's also required for a multiseat environment? How reliable is multiseat at the moment? What you always can do is download the Xvnc sources (xf4vnc.sf.net) and strip it down to your needs. But we have way too many X11 sources, for which we need to make security updates, so it's not an option for us to maintain a second Xvnc. Best regards, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, 7 Mar 2008 at 13:15, Stefan Dirsch wrote:
Isn't this the same as you suggested above? Use the dummy module as video driver + libvnc.so?
It's similar, but not exactly the same. In the first case the dummy driver and libvnc would be used, in the second case, the relevant parts of Xvnc would become hardware driver modules for video and input devices, so that the dummy driver is not needed. I am not sure if that'd be worth the effort, though. cu Reinhard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (5)
-
Lukas Ocilka -
Martin Vidner -
Michal Marek -
Reinhard Max -
Stefan Dirsch