From owner-freebsd-questions Tue Jun 6 7:56: 6 2000 Delivered-To: freebsd-questions@freebsd.org Received: from Samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (Postfix) with ESMTP id 7326937B91F for ; Tue, 6 Jun 2000 07:56:02 -0700 (PDT) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by Samizdat.uucom.com (8.9.3/8.9.3) id KAA00226; Tue, 6 Jun 2000 10:55:56 -0400 (EDT) To: support@tecpro.com Cc: questions@FreeBSD.ORG Subject: Re: VNC - Virtual Network Computing - Your Comments/Opions Please From: Chris Shenton Date: 06 Jun 2000 10:55:55 -0400 In-Reply-To: "Charles Peters - Tech Support"'s message of "Fri, 2 Jun 2000 23:55:15 -0400" Message-ID: Lines: 20 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Jun 2000 23:55:15 -0400, "Charles Peters - Tech Support" said: "Charles> Hello Everybody: I have been researching VNC, and would like "Charles> to try the port, but would like to have input from someone "Charles> how has used the product and has experience with it. VNC rocks. I use it whenever I have to do work on a WinDoze box. The idea of walking across the building -- or driving across town -- to diddle some damn GUI interface is insane. Install it on the Doze box as a service, otherwise it won't be there when you reboot it. And make sure you can reboot it via VNC and that it actually shuts down, then actually comes back up, before you walk away from it. I found this out the hard way on one Doze "server" installed in a lights-out data-center; had to visit it in person to fix the problem, but never again. I haven't yet researched the security risks of the protocol and haven't tried yet to run VNC over an SSH tunnel, so look into this if it's a concern. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message