Francois Tigeot wrote:
On Tue, Jun 07, 2005 at 10:20:03PM +0200, Torfinn Ingolfsen wrote:
On Tue, 07 Jun 2005 12:03:41 +0200
Francois Tigeot [EMAIL PROTECTED] wrote:
Stock X is sufficient.
Well, stock X will probably work. I have used that in the past on a
per-program basis. You know, the
On Tue, Jun 07, 2005 at 12:03:01AM +0200, Torfinn Ingolfsen wrote:
What are people using for remote X displays on amd64 machines?
Stock X is sufficient.
My users use ThinBSD based thin clients to connect to a
FreeBSD/amd64 server.
--
Francois Tigeot
On Tue, Jun 07, 2005 at 12:03:41PM +0200, Francois Tigeot wrote:
On Tue, Jun 07, 2005 at 12:03:01AM +0200, Torfinn Ingolfsen wrote:
What are people using for remote X displays on amd64 machines?
Stock X is sufficient.
That's really not a substitue for nxserver's performance... Assuming
On Tue, Jun 07, 2005 at 12:19:19PM +0200, Marc Olzheim wrote:
On Tue, Jun 07, 2005 at 12:03:41PM +0200, Francois Tigeot wrote:
Stock X is sufficient.
That's really not a substitue for nxserver's performance... Assuming
Torfinn is working over a high latency connection.
I assumed the
On Tue, 07 Jun 2005 12:03:41 +0200
Francois Tigeot [EMAIL PROTECTED] wrote:
Stock X is sufficient.
Well, stock X will probably work. I have used that in the past on a
per-program basis. You know, the 'DISPLAY=host:0.0 program ...' routine.
I'm sorry that my little question lacked enough detail
On Tue, Jun 07, 2005 at 10:20:03PM +0200, Torfinn Ingolfsen wrote:
On Tue, 07 Jun 2005 12:03:41 +0200
Francois Tigeot [EMAIL PROTECTED] wrote:
Stock X is sufficient.
Well, stock X will probably work. I have used that in the past on a
per-program basis. You know, the 'DISPLAY=host:0.0
Hello,
I'm riunning FreeBSD 5.4-stable (amd64) on this amd64 machine.
I would like to see the X display on this machine from another machine.
My first thought was VNC (tightVNC) as I'm using this on my other boxes
already. But alas, VNC isn't working on amd64.
I then saw FreeNX in the ports
What are people using for remote X displays on amd64 machines?
What about 'ssh -X remote-machine'?
Claus
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL
X is a fully network aware display method just set your display
to the remote machine. If you worried about security either VNP
it or tunnel over SSH.
Steve
- Original Message -
From: Torfinn Ingolfsen [EMAIL PROTECTED]
To: freebsd-stable@freebsd.org
Sent: Monday, June 06, 2005
Date: Tue, 7 Jun 2005 00:11:14 +0200
From: Claus Guttesen [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
What are people using for remote X displays on amd64 machines?
What about 'ssh -X remote-machine'?
'ssh -Y remote-machine' is more likely to be useful on more recent
versions of ssh.
--
* Kevin Oberman [EMAIL PROTECTED] [0616 23:16]:
Date: Tue, 7 Jun 2005 00:11:14 +0200
From: Claus Guttesen [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
What are people using for remote X displays on amd64 machines?
What about 'ssh -X remote-machine'?
'ssh -Y remote-machine' is
Date: Mon, 6 Jun 2005 23:20:41 +0100
From: Dick Davies [EMAIL PROTECTED]
* Kevin Oberman [EMAIL PROTECTED] [0616 23:16]:
Date: Tue, 7 Jun 2005 00:11:14 +0200
From: Claus Guttesen [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
What are people using for remote X displays on amd64
* Kevin Oberman [EMAIL PROTECTED] [0626 23:26]:
Date: Mon, 6 Jun 2005 23:20:41 +0100
From: Dick Davies [EMAIL PROTECTED]
* Kevin Oberman [EMAIL PROTECTED] [0616 23:16]:
Date: Tue, 7 Jun 2005 00:11:14 +0200
From: Claus Guttesen [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
there are several VNCs, buut either they are i386 or they are broken.
X forwarding is an option
If you using KDE, you can enable desktop sharing, it uses the vnc protocol,
you can connect using a standard vnc client. (this is reported to work on
AMD64)
This also will allow you to see the
On Tue, 7 Jun 2005 11:21, Axel Gonzalez wrote:
If you using KDE, you can enable desktop sharing, it uses the vnc protocol,
you can connect using a standard vnc client. (this is reported to work on
AMD64)
That works here.
I tried net/vnc but starting up give..
[foo64 2:25] /usr/ports/net/vnc
On 6/7/05, Daniel O'Connor [EMAIL PROTECTED] wrote:
That works here.
I tried net/vnc but starting up give..
[foo64 2:25] /usr/ports/net/vnc Xvnc :1
Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb'
Getting interface configuration (4): Device not configured
--SNIP--
failed to set default font
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jun 07, 2005 at 10:33:40AM +0800, Jiawei Ye wrote:
On 6/7/05, Daniel O'Connor [EMAIL PROTECTED] wrote:
That works here.
--SNIP--
failed to set default font path
On Monday 06 June 2005 21:33, Jiawei Ye wrote:
On 6/7/05, Daniel O'Connor [EMAIL PROTECTED] wrote:
That works here.
I tried net/vnc but starting up give..
[foo64 2:25] /usr/ports/net/vnc Xvnc :1
Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb'
Getting interface configuration (4): Device
On Monday 06 June 2005 21:26, Daniel O'Connor wrote:
On Tue, 7 Jun 2005 11:21, Axel Gonzalez wrote:
If you using KDE, you can enable desktop sharing, it uses the vnc
protocol, you can connect using a standard vnc client. (this is reported
to work on AMD64)
That works here.
I tried
19 matches
Mail list logo
