Re: remote X display
On Thu, Jan 22, 2004 at 04:12:17PM +0100, Cordula's Web wrote: : I have been looking all over for a concise howto for remote X on FreeBSD. I : see some that involve changing config files in the xdm directory, others use : xhost, and another uses xfig, which doesn't exist under FreeBSD AFAICT. : : Use ssh's -X flag: : : somehost ssh -X [EMAIL PROTECTED] : remotemachine echo $DISPLAY : somehost.example.com:10.0 : remotemachine xclock : : Don't forget to enable X forwarding in /etc/ssh/sshd_config: : X11Forwarding yes I had this working before, but I'm having problems. My main box is missing a monitor (on repair). Would that make a difference? Will X apps run on the main box without a monitor and forward X to the remote client? Right now, I get this: neptune:~ echo $DISPLAY neptune:~ : : All I want to do is use a laptop in a local network to be an X client : connected to a more powerful desktop machine. I'm not worried about : security. : : Is xhosts and the DISPLAY variable all I need? Or do I need to go through : all of the xdm configuration hoops? : : ssh X11 forwarding is much more secure than DISPLAY/xhosts/xdm etc..., : because: : 1. Your X11 server doesn't have to listen to port 6000 : (You don't have to add '-listen_tcp' to startx command) : 2. The communication between server and client is encrypted : : Of course, YMMV. : : NOTE: Please CC me, as I am not currently subscribed. Thanks. : : jm : -- : My other computer is your windows box. : : -- : Cordula's Web. http://www.cordula.ws/ jm -- My other computer is your Windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remote X display
: somehost ssh -X [EMAIL PROTECTED] : remotemachine echo $DISPLAY : somehost.example.com:10.0 : remotemachine xclock : : Don't forget to enable X forwarding in /etc/ssh/sshd_config: : X11Forwarding yes I had this working before, but I'm having problems. My main box is missing a monitor (on repair). Would that make a difference? Will X apps run on the main box without a monitor and forward X to the remote client? Right now, I get this: neptune:~ echo $DISPLAY neptune:~ If DISPLAY is not set, then ssh on your local machine and sshd on the remote box didn't establish an X11 forwarding channel. Are you sure that sshd_config is set up properly on the remote machine? Did you use -X (that's uppercase X) while invoking ssh locally? Perhaps your local ssh and remote sshd are not talking the same version of the SSH protocol? BTW, it is irrelevant if the remote box has a monitor or not. That box doesn't even need an X server (wether running or not). Only X clients and X libraries are needed on the remote machine. -- Cordula's Web. http://www.cordula.ws/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
remote X display
Hi all, I have been looking all over for a concise howto for remote X on FreeBSD. I see some that involve changing config files in the xdm directory, others use xhost, and another uses xfig, which doesn't exist under FreeBSD AFAICT. All I want to do is use a laptop in a local network to be an X client connected to a more powerful desktop machine. I'm not worried about security. Is xhosts and the DISPLAY variable all I need? Or do I need to go through all of the xdm configuration hoops? NOTE: Please CC me, as I am not currently subscribed. Thanks. jm -- My other computer is your windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remote X display
On 22/01/04 14:53 +, Jonathon McKitrick wrote: Hi all, I have been looking all over for a concise howto for remote X on FreeBSD. I see some that involve changing config files in the xdm directory, others use xhost, and another uses xfig, which doesn't exist under FreeBSD AFAICT. All I want to do is use a laptop in a local network to be an X client connected to a more powerful desktop machine. I'm not worried about security. Is xhosts and the DISPLAY variable all I need? Or do I need to go through all of the xdm configuration hoops? One idea is to use SSH. If you have sshd on the remote desktop you can use ssh -X to enable X11 forwarding. Just ssh into the remote box and run the X application and you're set to go, provided that X11 forwarding is enabled in the remote sshd_config. Good Luck, Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remote X display
On Thu, Jan 22, 2004 at 02:53:53PM +, Jonathon McKitrick wrote: All I want to do is use a laptop in a local network to be an X client connected to a more powerful desktop machine. I'm not worried about security. Is xhosts and the DISPLAY variable all I need? Or do I need to go through all of the xdm configuration hoops? you can do the following : run gdm on the server, start gdmconfig as root, enable XDMCP then on the client start X as following : X -query ipaddress_of_your_server ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remote X display
I have been looking all over for a concise howto for remote X on FreeBSD. I see some that involve changing config files in the xdm directory, others use xhost, and another uses xfig, which doesn't exist under FreeBSD AFAICT. Use ssh's -X flag: somehost ssh -X [EMAIL PROTECTED] remotemachine echo $DISPLAY somehost.example.com:10.0 remotemachine xclock Don't forget to enable X forwarding in /etc/ssh/sshd_config: X11Forwarding yes All I want to do is use a laptop in a local network to be an X client connected to a more powerful desktop machine. I'm not worried about security. Is xhosts and the DISPLAY variable all I need? Or do I need to go through all of the xdm configuration hoops? ssh X11 forwarding is much more secure than DISPLAY/xhosts/xdm etc..., because: 1. Your X11 server doesn't have to listen to port 6000 (You don't have to add '-listen_tcp' to startx command) 2. The communication between server and client is encrypted Of course, YMMV. NOTE: Please CC me, as I am not currently subscribed. Thanks. jm -- My other computer is your windows box. -- Cordula's Web. http://www.cordula.ws/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remote X display
On Thu, Jan 22, 2004 at 10:08:46AM -0500, Jason Stewart wrote: : On 22/01/04 14:53 +, Jonathon McKitrick wrote: : : Hi all, : : I have been looking all over for a concise howto for remote X on FreeBSD. I : see some that involve changing config files in the xdm directory, others use : xhost, and another uses xfig, which doesn't exist under FreeBSD AFAICT. : : All I want to do is use a laptop in a local network to be an X client : connected to a more powerful desktop machine. I'm not worried about : security. : : Is xhosts and the DISPLAY variable all I need? Or do I need to go through : all of the xdm configuration hoops? : : : One idea is to use SSH. : If you have sshd on the remote desktop you can use ssh -X to enable : X11 forwarding. Just ssh into the remote box and run the X : application and you're set to go, provided that X11 forwarding is : enabled in the remote sshd_config. Ah, I remember seeing this before, now that I think about it. Thanks for the reminder. Do I do this from the console or from an xterm? In other words, should X already be running? NOTE: Please CC me, as I am not currently subscribed. Thanks. jm -- My other computer is your windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remote X display
: One idea is to use SSH. : If you have sshd on the remote desktop you can use ssh -X to enable : X11 forwarding. Just ssh into the remote box and run the X : application and you're set to go, provided that X11 forwarding is : enabled in the remote sshd_config. Ah, I remember seeing this before, now that I think about it. Thanks for the reminder. Do I do this from the console or from an xterm? In other words, should X already be running? X should be already running. -- Cordula's Web. http://www.cordula.ws/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remote X display
On Fri, 23 Jan 2004 01:23, Jonathon McKitrick wrote: Hi all, I have been looking all over for a concise howto for remote X on FreeBSD. I see some that involve changing config files in the xdm directory, others use xhost, and another uses xfig, which doesn't exist under FreeBSD AFAICT. All I want to do is use a laptop in a local network to be an X client connected to a more powerful desktop machine. I'm not worried about security. Is xhosts and the DISPLAY variable all I need? Or do I need to go through all of the xdm configuration hoops? The machine you're actually sitting at needs to be running X-terminal software, that is X server and xdm or some equivalent. X applications can be run on either machine for control from there. In my opinion ssh is a much tidier way than rsh/xhost for running X applications remotely. Have a look at the special options in ssh for X transport in the man page, particularly -X and -f. xfig I only know as a (rather good) vector based drawing program but is just an ordinary X application without any special connection with operating across the network. Malcolm Kay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remote X display
what about setting the server with VNC? then the client connects with vnc client and you can run all the apps from the server from any machine. Unless I'm totally off. - Original Message - From: Malcolm Kay [EMAIL PROTECTED] To: Jonathon McKitrick [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, January 22, 2004 9:26 AM Subject: Re: remote X display On Fri, 23 Jan 2004 01:23, Jonathon McKitrick wrote: Hi all, I have been looking all over for a concise howto for remote X on FreeBSD. I see some that involve changing config files in the xdm directory, others use xhost, and another uses xfig, which doesn't exist under FreeBSD AFAICT. All I want to do is use a laptop in a local network to be an X client connected to a more powerful desktop machine. I'm not worried about security. Is xhosts and the DISPLAY variable all I need? Or do I need to go through all of the xdm configuration hoops? The machine you're actually sitting at needs to be running X-terminal software, that is X server and xdm or some equivalent. X applications can be run on either machine for control from there. In my opinion ssh is a much tidier way than rsh/xhost for running X applications remotely. Have a look at the special options in ssh for X transport in the man page, particularly -X and -f. xfig I only know as a (rather good) vector based drawing program but is just an ordinary X application without any special connection with operating across the network. Malcolm Kay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
got Cygwin/XFree86 installed.. next step to get a remote x display?
heh i actually started trying things out and i already can run apps from my fbsd box and get them displayed on cygwin/xf86 server.. but without the window manager :\ (did it with ssh -X) What should I do in order to view the remote display here on my win2k box properly, with KDE running, my background etc etc? help would be *much* appreciated ;) __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
