|
2010-03-11
, 18:06
|
Posts: 1,751 |
Thanked: 844 times |
Joined on Feb 2010
@ Sweden
|
#2
|
|
2010-03-11
, 18:29
|
Posts: 45 |
Thanked: 30 times |
Joined on Feb 2010
@ Germany
|
#3
|
For most of you this may be pretty obvious and you can stop reading at this point.
For the others, please read on. The Howto became quite long. Don't let this scare you away. I believe in some points I was a little too verbose. It is really all just unix textbook stuff. You may want to scroll down to "Conclusions" to see what you can expect.
I tested this stuff on my n810 handheld and a debian desktop machine.
Step 1: Install ssh
Make sure you have ssh installed on both machines (desktop and handheld). Ssh consists of a daemon and a client program. For our purposes it is sufficient to have the daemon on the desktop machine and only the client on the handheld, but I strongly recommend to have daemons on both machines, so you can log in to your handheld from the desktop. This simplifies many tasks (including this one) quite a lot, because you can use the desktop keyboard to control your handheld.
Here is what I have installed:
On the desktop (running debian):
After the installations the ssh daemons should be running on both machines. Verify this:
On the desktop:
On the desktop:
Then edit /etc/hosts on both machines and add entries like this:
On the desktop:
At this point you should be able to log in to your handheld from the desktop and vice versa.
You may get complaints about two unsupported options in /etc/ssh/ssh_config. If you comment out the two lines in that file, then ssh will no longer complain.
The next thing you want to do, it allowing ssh connections without having to answer the password prompt. A good howto can be found here. Here are the fundamentals
On the handheld:
You need to take the following steps as user "user" and not as root. When you start a terminal on the handheld you will be "user", but when you log in as root via ssh you are initially "root" and you need to "su - user". If you are uncertain who you are, run "id". Since we can already ssh to the handheld, we want to do everything from our desktop using a decent keyboard.
At this point you should be able to forward commands from your handheld (as "user") to your desktop without having to answer a password:
On the handheld:
Step 2: forward X11
So far we can only run remote console commands. But we really want to run X11 (graphical) applications remotely. For this to work you may have to enable X11 forwarding.
On the desktop:
Make sure your /etc/ssh/sshd_config file contains the following lines
On the handheld:
Again make sure you are "user" and not "root".
Step 3: Use personal menu
Install the personal menu package on the handheld (available on meamo.org). Then go to Control panel/Panels and replace one of the three existing panels with personal menu (I sacrificed "Contacts").
Next configure personal menu itself. There will be an entry in the Control panel under "Personalisation" called "Personal Menu". In the "Command to execute" field you can enter commands like one we used to invoke the xterm on the remote machine. Then you give the whole thing a name and chose an icon.
You can do this for a couple of applications, and in the end your personal menu may look like this:
Finally here is a screenshot showing Amarok being displayed on the handheld.
Conclusion: pros and cons
Those applications start and run pretty fast. They use the power of the desktop computer and only need the handheld for displaying things. They are still not as fast as when run natively on the desktop, because there they can make use of good graphics hardware. The epiphany web browser is amazingly snappy as long as you don't run flash movies.
In general any kind of animation will cause high CPU usage or worse. You better disable the visualization in Amarok.
The programs do not respond to the fullscreen button. However some applications have a builtin "fullscreen" option which is selectable via a menu entry. The epiphany web browser runs in fullscreen just fine.
The onscreen keyboard will not pop up, when you need to enter texts. For n810 users, this means you have to use the hardware keyboard.
Some applications heavily rely on right (or middle) mouse clicks. I have not found a way to fake right mouse clicks. This makes file managers pretty difficult to operate and you cannot use mouse gestures in epiphany.
When running Amarok, sound is still played by the desktop's sound card (which is what I want). The sound will not arrive at the handheld's speakers. What you get is a remote control for Amarok.
You can do similar things with VLC. Here you have to use VLC's web interface because you don't want the graphics forwarded to your handheld. This way you will get a remote control for VLC.
Hope some find this useful.
Last edited by drautzburg; 2010-03-11 at 18:42. Reason: Conusing linebraks