The other day I came across a post from someone saying how they were using a PC to run the their Zaurus Xwindows. I think I know what they are doing, becasue I think I have done it a few times in the past when playing around. But I was wondering if someone could post a short tutorial.
Is it as simple as starting X windows on a PC and point it to the Zaurus IP address?
I hope I'm making sense. Kinda tired right now.

Zaurus:
-set a password for root

- Edit /etc/ssh/sshd_config:
X11Forwarding: yes

on the pc running X:
- ssh -X root@zaurusip

then launch xterm dillo or whatever

The above assumes you are using Linux/Solaris/BSD on your PC
If you are running Windoze, then you would need to install an X server such as Reflection X first.

Alternatively, you can install x11vnc on the Zaurus and use any vnc client such as tightvnc and access the X desktop from the PC

you' are right on windows, free there is xdeep32 tutorial here:
http://www.it.uu.se/datordrift/faq/hemarbete/xdeep32

and cygwin xserver, note that with cygwin ssh -X is broken, but you can use ssh -Y

-Y enables Trusted forwarding and more control over specific X server features. You may find in any case that certain applications require -Y to run remote due to the features that they try to use of the X server unless you can specifically allow the X SECURITY extension of your X server to provide those features over ssh.

-Andy

Good tutorial. So I now have my putty term open, but do I get an app to show up on my windows desktop? Do I need to set the DISPLAY to something other than 0:0? thks

normally you just have to launch it

With cygwin, you can have a Linux Enviroment on Windows with Xfree, SSH, KDE and more more more.... GCC

Awesome, this is a nice little X server.. I have been looking for a free one for Windows for a while.... have even got my Zaurus providing xdmcp login now

And now I have putty and X/Deep-32 available on my moinmoin personal wiki that I run on my Zaurus... convinent way of carrying it around to install on Windows machines

That's exactly what I was looking for. Thanks pgas!
The Windows info is good too. Thanks everyone.

Answered my own question. For me I had to set my DISPLAY to point to the the host machine. So if I'm logging in via usb from my 'doze box, that would be 192.168.129.1:0.

btw, xdeep32 is a really nice, simple to use X server & a great newbie setup page. Thanks for those

For this works you go need xdm running on Z, and configured to accepts conections... but dont have xdm for ARM, and dont needs!

I was actually saying that I have already got it going... since OpenBSD on the Zaurus is the same as the other architectures I just disabled the local server, enabled xdmcp client support and start xdm with -udpPort 177 and hey presto I can login using xdmcp from X/deep-32

-Andy

Excellent!

I don't suppose I could get a volunteer to summarize this information for the wiki?

Armagon

At one time, I think on RC11, I was able to run, I THINK, openbox, remotely. I'm not sure what I ran, but the result was that I got the entire window manager onto my local machine from the Z. Looked similar to VNC, but worked a lot better. However, on beta2, I just get a lot of errors when I try to run openbox redirected to another machine.

Am I crazy? I know I did it, but I'm not really sure how. It wasn't VNC, it was x.

you probably had to remove the "-nolisten tcp" argument from startx or it wasnt there in the rc before.

I just tried Xdeep. Wow. Sure works well, thanks. Using SSH gives me piece of mind over VNC and RD. Took 5 Min to get up and running (that's the way it should be).
I used ReflectionX back in the Redhat 7 or 8 erra, and it worked well but I couldn't afford to buy it.

Now I can use KO/Pi (installed on my Zaurus) on my Windows Laptop. Nice!
It's a nice answer to the sync problem, in case anyone is looking for a solution still.

hmmm... from playing around with it a bit more there seems to be a problem with KOrganizer. The first time I create a calendar entry or ToDo it works fine, but everytime after that (untill I restart the xdeep server) I can't type any text. I can paste into the filed, but typing a key doens't seem to register. I can go back to the main KO window and the keyboard works there. Strange. GPE-Calendar, and other applicaitons don't seem to suffer the same problems so maybe the issue is with the microkde libs.
Ideas, anyone?

All I can confirm is that I haven't experienced any problems with gpe-calendar, gpe-contacts, sylpheed, dillo or gpe-gallery (the apps I've actually tried so far). Unfortunately we don't have the pi-sync apps available in OZ/GPE yet.

Are you using the ssh -Y option? I found that a lot of things didn't work until I enabled that. The gpe apps were about the only things that did work to start with, so I think maybe they're a little more forgiving...

Thanks for the tip, but I'm using putty to do ssh in Windows. I've enabled X11 forwarding in PuTTY, so I think I've done what you're suggesting. The mystery continues.

Just started trying out OZ/GPE.
There's no /etc/ssh/sshd_config in OZ/GPE.
Any ideas?

Oz uses dropbear and not openssh (pdaxrom will also come with dropbear with the next release)
I think ssh -X is suppose to work out of the box.

(search for dropbear in the OZ forums)

Or you could install openssh if you'd prefer (it's in the feeds).

I have followed ur instructions, I could ssh into Z, but when I tried to run dillo I got the following error:



I am running this on X11 on my mac
any ideas what cause this?

thx~

It's the same thing I noticed. You have to set your DISPLAY variable to point to your pc, as in 'export DISPLAY=192.168.129.1:0' (if that's your pc's ip) before running the command.

I wrote myself a script to set it when I needed it. Put it in your path & just use it to run your program 'xpc dillo'. HTH

NB: this works with openssh installed. I'm not sure if it works with dropbear (as is default in the OZ images, don't know about what you use in pdaxrom).

You are correct. It does work out of the box in OZ.
Thanks.

anyone have xdm running on beta1? I'm having no luck, just err 97