From owner-freebsd-questions Tue May 15 21:52:37 2001 Delivered-To: freebsd-questions@freebsd.org Received: from knight.exec.bsdi.com (knight.exec.ixsystems.net [206.40.55.67]) by hub.freebsd.org (Postfix) with ESMTP id 3603837B422 for ; Tue, 15 May 2001 21:52:34 -0700 (PDT) (envelope-from matt@ixsystems.net) Received: from thor.ixsystems.net (adsl-63-204-132-71.dsl.snfc21.pacbell.net [63.204.132.71]) by knight.exec.bsdi.com (8.11.0/8.11.0) with ESMTP id f4G4otw37588; Tue, 15 May 2001 21:50:55 -0700 (PDT) (envelope-from matt@ixsystems.net) Message-Id: <5.0.2.1.1.20010515214855.00ab5da8@mail.exec.bsdi.com> X-Sender: matto@mail.exec.bsdi.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 15 May 2001 21:52:19 -0700 To: , From: Matt Olander Subject: RE: Using PC's as X Terminals In-Reply-To: <001b01c0ddc0$7f133b40$1401a8c0@tedm.placo.com> References: <3B011EA3.5234DB81@imagination.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_132431276==_.ALT" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=====================_132431276==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed > >I'm trying to find a way to turn client machines (i386 machines running > >other operating systems that can't be replaced), into dumb X terminals > >on a part time basis. The people that will be using them are mainly > >going to be running windows the majority of the time, but will have the > >need to dip into an X environment on occasion. For various reasons, my > >superiors are unwilling to consider Win32 X servers, so this isn't an > >option for me. hi David, i had a similiar problem at work. people that used windows that occasionally needed access to freebsd. i ended up using vnc. the only problem i've noticed is that it generates a bit of network traffic while in use... www.uk.research.att.com/vnc/ matt --=====================_132431276==_.ALT Content-Type: text/html; charset="us-ascii"
>I'm trying to find a way to turn client machines (i386 machines running
>other operating systems that can't be replaced), into dumb X terminals
>on a part time basis. The people that will be using them are mainly
>going to be running windows the majority of the time, but will have the
>need to dip into an X environment on occasion. For various reasons, my
>superiors are unwilling to consider Win32 X servers, so this isn't an
>option for me.

hi David,
i had a similiar problem at work. people that used windows that
occasionally needed access to freebsd. i ended up using vnc.
the only problem i've noticed is that it generates a bit of network
traffic while in use...
www.uk.research.att.com/vnc/

matt
--=====================_132431276==_.ALT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message