gillhaa@ghost.whirlpool.com (Andrew Gillham) writes:

> So can somebody with xsrc installed build a NetBSD/i386 package
> for us?  :-)

After incorporating the FreeBSD patches available from the website
(http://www.orl.co.uk/vnc, in case anyone's forgotten), copying
FreeBSD.cf to NetBSD.cf, and adding an include of unistd.h in one file,
I was able to get a clean build.

I don't know anything about making an offical entry in the ports stuff,
but I did tar up the modified sources (if someone wants to make a
patchfile, go ahead. I plan to make one and send it to orl when I get a
chance) as well as NetBSD binaries. You can find them here:


	http://www.morningstar.com/~laine/vnc

   vnc-3.3.1.x86.netbsd.tar.gz

	VNC server and viewer, and Java classes, compiled for
	NetBSD-i386 1.3. To install, just cd to /usr/local and
	untar this file.

   vnc-3.3.1.unixsrc-plus-BSD-patches.tar.gz

	Source patched to build properly on NetBSD and FreeBSD.
	To build and install:

	    tar xzvf vnc-3.3.1.unixsrc.tar.gz
	    cd vnc-3.3.1
	    xmkmf
	    make world
	    (become root)
	    ./vncinstall

   vnc-3.3.1.x86.win32.exe*

	self extracting Installshield executable for MS Windows
	(95 and NT) (From ORL you can only get it in a zip file
	or tar.gz. I used PackageForTheWeb (comes with InstallShield)
	to make the .exe (yes, I shamefacedly admit that I develop
	MS Windows software :-O)

   vnc-3.3.1.doc.tar.gz

	documentation - I haven't even looked at it. Too easy.

Some quickstart instructions
----------------------------

To start up a virtual X server on your Unix box:

1) create a directory in your home directory called ".vnc"

2) create a shell script called "xstartup" in that directory which runs
   some X things. Either you can create a new script, or just have it
   call "~/.xsession &" (if you have one). It's probably useful to at
   least run a window manager (tvtwm, fvwm, twm, etc).

3) from your home directory, run "vncserver". Pay attention to which
   display it tells you you've gotten "it will say something like
   "machine:1"). The first time you run it, it will ask you for a
   password.

4) Run one of the clients (the PC one, or "vncviewer" on Unix and tell
   it the screen you were given (if you're using NetScape, add 5800 to
   the number, eg "machine:5801) type in your password, and you're off
   and running.

5) The X server doesn't exist when you exit the client. It sticks around
   until you kill the Xvnc process. You can connect and reconnect
   multiple times from multiple places, and your window state is saved.

Note that each virtual X server uses about 16 MB on the Unix box (at
least my 1600x1200 truecolor virtual X server does ;-). I haven't tried
it over a modem, but performance is "acceptable" on a 64/128 (bandwidth
on demand) ISDN line (just don't run xearth!)