x11vnc is a VNC server for real X displays. VNC (Virtual Network Computing) is a very useful network graphics protocol which allows multiple simple remote viewers to watch and control a single desktop. x11vnc differs from traditional UNIX VNC servers in that it is accessing a real X displays that may already be in progress rather than creating it's own X server for clients to connect to.
On Tue, 7 Jun 2005 06:51:03 -0700 (PDT) "Loren M. Lang" <lorenl@alzatex.com> wrote: > > >Number: 81995 > >Category: ports > >Synopsis: New port: net/x11vnc VNC Server for real X servers [ ... ] > >Description: > x11vnc is a VNC server for real X displays. VNC (Virtual Network > Computing) is a very useful network graphics protocol which allows > multiple simple remote viewers to watch and control a single > desktop. x11vnc differs from traditional UNIX VNC servers in that it > is accessing a real X displays that may already be in progress rather > than creating it's own X server for clients to connect to. So one could attach and interact with a running kde or gnome session ? > echo x - net/x11vnc/Makefile > sed 's/^X//' >net/x11vnc/Makefile << 'END-of-net/x11vnc/Makefile' > X# New ports collection makefile for: mozplugger ^^^^^^^^^^^ I believe you want x11vnc here -- IOnut Unregistered ;) FreeBSD "user"
Fixes the comments in the Makefile -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2
On Tue, 7 Jun 2005 06:51:03 -0700 (PDT) "Loren M. Lang" <lorenl@alzatex.com> wrote: > echo x - net/x11vnc/pkg-plist > sed 's/^X//' >net/x11vnc/pkg-plist << 'END-of-net/x11vnc/pkg-plist' > Xbin/x11vnc >>>>>>>>>>> > Xshare/x11vnc/classes/VncViewer.jar > Xshare/x11vnc/classes/index.vnc >>>>>>>>>>>>>>>>>> Ideally you should OPTIONnally depend on java and install this two files or don't depend and don't install them. > END-of-net/x11vnc/pkg-plist -- IOnut Unregistered ;) FreeBSD "user"
On Tue, Jun 07, 2005 at 07:22:28PM +0300, Ion-Mihai Tetcu wrote: > On Tue, 7 Jun 2005 06:51:03 -0700 (PDT) > "Loren M. Lang" <lorenl@alzatex.com> wrote: > > > echo x - net/x11vnc/pkg-plist > > sed 's/^X//' >net/x11vnc/pkg-plist << 'END-of-net/x11vnc/pkg-plist' > > Xbin/x11vnc > > >>>>>>>>>>> > > Xshare/x11vnc/classes/VncViewer.jar > > Xshare/x11vnc/classes/index.vnc > >>>>>>>>>>>>>>>>>> > > Ideally you should OPTIONnally depend on java and install this two files > or don't depend and don't install them. The port itself does not depend or require java. The jar file comes pre-compiled and bundled with x11vnc. The vnc server also has a mini webserver which runs on port 5800+n where n is the display number and the webserver serves the java applet to be run by an external client so they don't need a vnc viewer installed to access the server. As the jar file does not need to be compiled or even run on the server, I see no problem with including it unconditionally. The only benefit to not including it is save 35k of disk space. > > > END-of-net/x11vnc/pkg-plist > > > > > -- > IOnut > Unregistered ;) FreeBSD "user" > -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2
Responsible Changed From-To: freebsd-ports-bugs->mezz I'll take this.
State Changed From-To: open->feedback I have made some changes, please review this shar file. http://people.freebsd.org/~mezz/shar/x11vnc.shar Here's what I have done: - Add USE_GNOME=gnometarget, keep in mine it doesn't mean it adds GNOME dependency. It's just easier to remember for have configure target. A lazy way to remember. :-) - Add CONFIGURE_ENV= [...] - Add a missing dependency, jpeg. - Respect the PTHREAD_LIBS, don't be hardcore on -lpthread. Three above have clean up and make configure looks nicer. See the before and after diff of 'make configure' http://people.freebsd.org/~mezz/x11vnc-configure.txt - Remove 'USE_XLIB=yes', USE_X_PREFIX takes care of it. - Fix the plist, you have missed directories. - Added DOCS, there have a lot of good informations in those files. Therefore, they are very useful to be part of the installation. - Change spacebar to tab. I think, that's all for now. Look forward to add this port in ports tree, I think it might be useful for jail that I am planning to setup for GNOME 2.12. BTW: I haven't test it in the runtime, so be sure to re-check on it too. Cheers, Mezz
On Tue, 7 Jun 2005 09:58:35 -0700 "Loren M. Lang" <lorenl@alzatex.com> wrote: > On Tue, Jun 07, 2005 at 07:22:28PM +0300, Ion-Mihai Tetcu wrote: > > On Tue, 7 Jun 2005 06:51:03 -0700 (PDT) > > "Loren M. Lang" <lorenl@alzatex.com> wrote: > > > > > echo x - net/x11vnc/pkg-plist > > > sed 's/^X//' >net/x11vnc/pkg-plist << 'END-of-net/x11vnc/pkg- > > > plist' Xbin/x11vnc > > > > >>>>>>>>>>> > > > Xshare/x11vnc/classes/VncViewer.jar > > > Xshare/x11vnc/classes/index.vnc > > >>>>>>>>>>>>>>>>>> > > > > Ideally you should OPTIONnally depend on java and install this two > > files or don't depend and don't install them. > > The port itself does not depend or require java. The jar file comes > pre-compiled and bundled with x11vnc. The vnc server also has a mini > webserver which runs on port 5800+n where n is the display number and > the webserver serves the java applet to be run by an external client > so they don't need a vnc viewer installed to access the server. As > the jar file does not need to be compiled or even run on the server, > I see no problem with including it unconditionally. The only benefit > to not including it is save 35k of disk space. Hmm, makes sense. I use it today, and it works with tridiavnc, tightvnc and KDE's krdc, including compressing. With ssh tunneling like suggested on the site, either direct or with tightvnc "-via", I get: channel 3: open failed: connect failed: Connection refused Thanks again for this port. -- IOnut Unregistered ;) FreeBSD "user"
Looks goods. No problems with portlint or the standard port test cycle. I also tested it in runtime and it seems to run well as well as the built-in web server and java applet. -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2
State Changed From-To: feedback->closed Committed, thanks!