On 6/22/06, Greg Lane <[EMAIL PROTECTED]> wrote:
On Thu, Jun 22, 2006 at 04:04:34PM +0300, Alex Savovski <[EMAIL PROTECTED]> wro
> I have the same ,problem,But I have never run on other version,I use
> RELENG_6_1, AMD64
On Thu, Jun 22, 2006 at 11:29:15AM -0500, Jonathan Fosburgh <[EMAIL PROTECTED]>
wrote:
> VNC (tightvnc included) as well as NXWindows (IMHO, much better than VNC) are
> based on old versions of XFree86 that don't support AMD64. I have had some
> success running the i386 package of tightvnc and starting only twm from the
> xstartup script. Some applications (just about anything using gtk) crash the
> VNC server, and some (KDE) work all right. YMMV.
>
> I have tried to make NXWindows work on amd64 but there is just too much
> patching that needs to be done for my meager skills.
Thanks for the info. I had figured something like this. I installed
the 64-bit system anticipating a future memory upgrade from the current
4GB to 8GB. However, VNC is essential for various members of my group,
as is ports/devel/root (which doesn't compile on amd64) and there is
some of our own (also essential) custom software which is not 64-bit
clean. Since this holds up a number of people from their work
and my patching skills are VERY meager, I will have to roll back to
the 32-bit OS.
Did you try to build/install a 32bit version of VNC? Also, if you are
running a Unix like OS why use VNC? You can achive %90 of the same
features (with less of a memory/cpu impact) by running X apps
remotely.
-pete
--
~~o0OO0o~~
Pete Wright
www.nycbug.org
NYC's *BSD User Group
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
