Running the Pi3 headless

I posted yesterday about the Dropbear SSH server:
http://bkhome.org/news/201612/dropbear-ssh-server-pets.html

Also about automatic activation of the ethernet connection at first bootup:
http://bkhome.org/news/201612/active-ethernet-at-first-boot.html

With the Pi3 running, and the dropbear server daemon running on it, waiting on port 22, and an active ethernet connection to my wireless router, I should be able to login from my laptop.

The wireless router I am using is a tiny one suitable for travellers, the TP-Link TL-WR802N (cost me AU$29 at a local store):
http://www.tp-link.com.au/products/details/cat-9_TL-WR802N.html


The TL-WR802N was recommended to me by Puppy Forum member jamesbond. Yeah, it is nice. I changed the configuration to "Access Point" mode.

On my baby laptop, running Windows 10, mobaXterm makes it easy. I had to do a scan to find what IP-address the dhcp server inside the router has assigned to the Pi3. Then started a terminal session.

Running Quirky linux on the same baby laptop, not quite so simple. I used a little commandline utility called 'multiscan', and it reported this IP address:

> multiscan -t 192.168.0.100 -s 22 -e 22
192.168.0.100:22 (ssh) is open

Then to run a session:

> ssh -X 192.168.0.100 -l root -p 22

It asks for the password, which is the default for most pups, "woofwoof", and I am in.

Unfortunately, there is a gotcha. If I type "leafpad", I get leafpad running, then if I choose "File -> Open...", I am able to open files in the Pi.

Fine, however, if I type "rox" in the terminal session, it opens the filesystem of my laptop. Wrong, wrong, wrong!

Over in Windows, running mobaXterm, "rox" behaves as expected, showing files in the Pi.

This is not a good situation, not for Linux on my laptop anyway.

---

Comments

Ah, yes, it had to be something simple. Regarding the "Wrong, wrong wrong" posted above, jamesbond has replied on the Puppy Forum:
http://murga-linux.com/puppy/viewtopic.php?p=936158#936158

Quoting:
BarryK wrote:
"Fine, however, if I type "rox" in the terminal session, it opens the filesystem of my laptop. Wrong, wrong, wrong!"

That's because 1, rox is already running in x86 Quirky, and 2, rox likes to re-use existing instance. This doesn't happen in MobaXterm because there is no Rox running there.
To "fix" this, when you're running Quirky, all you need to do is launch "rox -n" from your Pi3.

Tags: linux