bjoernvold.com

You will need a ssh server like openssh server. I am going to assume that you know how to set up SSH. (If you don't, ask in the help section and you will be guided)
Normally you ssh into your box with:
and provide a password and start using the CLI (Command Line Interface).
You can backup and sync your data and move and copy files - well what you can do in a CLI.
You can also start the GUI programs from the server on your clients
Simply use this code:

So if your name is Barak and your server is called "washington" and you want to start netbeans, it would look like this:



So it is possible not only to centralize your files but also your programs.

good tip
thank you

Glad you liked it! I find it practical.

Just a quick suggestion here. If you like ssh and use it regularly, you might want to take a look at setting up passwordless ssh. There are a number of good tutorials out there. I just linked to the first one in my wiki.

I use ssh on my home lan and accessing that lan from work (shhh! Don't let IT know). Passwordless login is more secure than sending an unencrypted password across a net, it's faster, and it's more convenient than waiting on a prompt and fumble-fingering an actual password.

I should also say that I'm doing this from work with portable apps (PuTTY and KiTTY) and you have to use a key generator to get it to work, but it's still nearly hassle free.

Try it!

Mark

I'll give it a go - Thanks!
Yup that works fine! Here is what I did:


Hmm I think I will write this up in a tip of its own. Or maybe you could?
How do you reach your home lan - fixed IP? Dyndns?

ssh -f -Y you@yourserver <program_you want_to _start>

I get this when trying to start the Puppy package manager.

Grr yes there must have been an update to openSSH. I have trouble here to getting anything to run now.
You could activate/add X11Forwarding yes in/etc/ssh/sshd_config on your puppy box. But I doubt it will help. It is supposed to be activated by default.

Tax times, busy times... Anywho


I've had a glance at the sshd manual and am uncertain about how to configure for X. ISTR something about the wildcard * host being a little non-secure but not sure who everybody goes by on this mini-lan.
Off to the job, now. Thanks for looking in on me!

Could *possibly* be of some help.

Could *possibly* be of some help as well?

*shrug

On the thin client, where sshd is running, I changed two lines in /etc/sshd_config (I believe the commented lines are default configuration; I uncommented, switched no to yes, yes to no, following what the sshd_config manual said):


Then `kill -1 <pid of sshd>` sends SIGHUP to sshd, causing it to restart and read the configuration anew. Now, time to rock and roll!


Off to google on that authentication error, which gave me, among other things, this:

If you encounter X11 connection rejected because of wrong authentication error after logging to an UNIX/Linux host through ssh with X11 forwarding option, -X, check your /etc/inet/hosts file for multiple localhost entries; and remove the unnecessary ones.

For example, my /etc/inet/hosts has the following entries when the xclock failed with an X11 connection rejected .. error.

remotehost% cat /etc/inet/hosts

127.0.0.1 localhost
::1 localhost
10.2.211.150 sunfiret2000 loghost


Removing the 2nd line, ::1 localhost, fixed the issue.

In Puppy, Mandriva, too, I think there is /etc/hosts, which looked like this:



On a hunch, I removed the 'puppyrc' entry and





Thanks for the tips and tricks!

Thank you !
And yes I belive the /ect/hosts is universal.

Ah this has been annoying me for some time now. And FINALLY I found the reason.
On the server side (the remote box):
In /etc/ssh/sshd_config I needed to forward X11.
Like this:

Bloody updates But now life is good again
restart X with (You might need to replace rc.d with init.d - or simply reboot).
....
Everything stars fine except netbeans where I have to use --jdkhome <path_to JDK>to locate jdk.
This is getting complicated to remember so I just tried a:

and entered netbeans in the terminal. That worked, in fact every GUI started fine like that.
Actually it works just fine without the -X too, so the setting in the sshd_config file did it all.