In a moment of boredom, I tried to bring up an X session on my Raspberry Pi from my laptop in the hotel, via the machine in the DMZ on my home network. It worked! It’s not very fast, but proves it can be done. The command I used was:
ssh -X home_dmz_machine 'ssh -X raspberrypi "exec startlxde"'
My home server went phut last week. There was a brief power outage, and everything else came back on — except the server. It was a three year old Mini-ITX box, and I’m casting about for ways to replace it.
To serve my immediate music serving and podcasting needs, I have pressed The Only Computer That Runs Windows into service, running Ubuntu using Wubi. Unfortunately, I do still occasionally need to run Garmin Mapsource, which only runs on Windows, and also The Only Computer That Runs Windows is also rather too nice a laptop to be sat doing server duty.
I have some options:
- Get a new motherboard for the mini-itx box. Via still has some crazy ideas about pricing (over $200 for a fanless C7?) but maybe I’ll go for Intel’s snappily-named D945GCLF, which looks okay for what I need and is only $80.
- I could resurrect the old Athlon box I got in 2002, but it’s big, loud, and its components are probably near end of life. Also, why disturb a mature spider habitat?
What I was really looking for was one of those tiny fanless internet appliance boxes that were so 2007 (like the Koolu and the Zonbu, both of which have moved on to other things), but such units, without the tied storage service contract, are upwards of $500.
My needs are simple:
- run Firefly to feed the Soundbridges;
- generate the automatic podcast every day, which realistically means a linux box with Perl, sqlite and the like;
- have something to ssh into when boredom strikes the need arises. Perhaps unwise having an open machine sitting directly on the internet, but only the ssh port will be open.
I really also need to get rid of all the computer junk in the basement. It now includes two fritzed mini-ITX systems and the world’s slowest PostScript laser printer. Such fun.
MidpSSH on my Blackberry talking to a screen session on my home server running a bittorrent client (and no, this doesn’t mean that I was torrenting over a mobile network).
How did I manage to go for so long without knowing about screen? screen allows you to create several connection sessions to a terminal, switch between them, detach from them, then reconnect from anywhere. I’d previously had to to set up long-running remote jobs as background jobs, relying on nohup and various methods to prevent terminal output. But no more!
This page taught me all I know about screen: screen: Keep Your Processes Running Despite A Dropped Connection
I know the technology is not that nifty, but I amused and amazed myself by sshing into the home server whilst on the Via train somewhere between Smith’s Falls and Ottawa.
Finally got something useful done with the Thinkpad with the broken backlight. Thanks to lots of help from Paul, and a critical bit of advice from Stephen, it’s now living on my network and visible to the outside world.
What had me initially confused was that both my modem (a SpeedTouch 546) and my Netgear router have NAT firewalls. I had to declare the router as a DMZ on my modem, and the Thinkpad a DMZ on my router. Also, the router’s DynDNS support was only reporting its IP address as seen behind the modem, so I had to turn that off and use dynDNS from the modem.
Security hole? Perhaps; but it’s not as if OpenBSD is the least secure or most widely-used OS. I’ve really only got sshd and thttpd running, so there’s not much to chew on …
Blue skies, crops growing, grasshoppers hopping, wind turbines turbing, blue-winged swallows over my head.
In short, it’s a beautiful day in Kingsbridge.
Kelly wanted the tetris shelves, but the cost was a bit steep. Her brother made these for her birthday.
The image links to a gallery of three views of the shelves.