LornaJane Blog

Tied up with the various issues we’ve had recently with houses, I’ve got a new project. Its to turn my (mother’s) very old laptop into a dumb terminal we can have in the basement in the new house. The kitchen is in the basement and I’m keen not to bring any more hardware into that environment that we need to, just because kitchens are full of liquids and grease.

I’ve got a Toshiba Satellite 210CS, complete with its original “Optimized for Windows 95” sticker. It celebrated its twelfth birthday this year so its not doing too badly! Its had a couple of upgrades from its original configuration – it has a 1GB hard drive, a PCMCIA wirless card that will talk to our 802.11b router, and a memory expansion to take it to 24MB of RAM. The processor is a Pentium 120Hz and judging by the fact that it thinks its June 2nd 2005, its CMOS battery is flat.

On Sunday night (its a bank holiday here so we’ve had Monday off as well) we installed Damn Small Linux (DSL) onto it and hoped for the best. The most impressive thing about this is always trying to boot anything new. This machine predates real PCMCIA standards and predates USB; it has a CD drive but can’t boot from it and often won’t read written CDs. It does have wired network on PCMCIA but can’t boot from that either. And it has a floppy drive … somewhere. So we managed to find the floppy drive, and another machine with a floppy drive in it (we were quite surprised to realise the server has one), and even unearthed a floppy disk in the house. Which is more impressive than it sounds as all our stuff is in storage!

DSL went on like a dream but wrongly guessed the size of the screen on the laptop so on the first attempt when I thought it had stopped and I pressed return a few times to shift everything up the screen a bit, I discovered I had answered “no” to the question “would you like a boot loader?”! So we did that again and now its working fine.

Even more impressively, the DSL installation is happily driving the PCMCIA wireless card, out-of-the-box. Last time we re-installed this machine (we think 3 or 4 years ago) we gave up with getting a binary distro working and Kevin compiled some special Gentoo for it. I was impressed how painless this was, so a big thanks to the DSL people, I must send them some fanmail. Or money, maybe.

The plan is just to use the command line to ssh up to the main in-the-house server and use that for checking mail. We can use lynx and command-line chat equivalents if we get desperate too :)

¹ If you were hoping for an update, we’ve commissioned the searches but must complete by the end of May to avoid losing the mortgage. Watch this space.

This is the first in a mini-series of articles about using Linux/Unix to do things other than view logs and edit files. I’m 26 and find that many of my peers weren’t exposed to Unix servers at university, so they miss out on this. If you have any suggestions of things to include in the mini series, let me know please!

Write messages

So to pop up a message on another user’s PC, you’d usually use MSN, right? Well if you’re both logged into the same server there is another way. Just echo your message and then send the program write to get it to the person. Like this:

echo “Hello Kevin” | write kevin

Kevin will get a message on his screen which says:


Message from lorna@server on pts/1 at 22:14 ...
Hello Kevin
EOF


Silence please

To turn off receiving messages, you need to change your mesg setting, by setting it to n:

mesg n

Not surprisingly, you can turn it back on with:

mesg y

That’s today’s installment, have fun!

Not to be confused with houselessness which I have also been doing a lot of recently, today mouselessness is the name of the game. Inspired by this recent post on Coding Horror here are my thoughts on using a computer without a mouse.

RSI Risk

I posted a while back about last years brush with RSI and it really did seem to settle down for a while. I changed jobs and that also seemed to help for the first few weeks, then start to get worse again. I do concur that the mouse is the root of all hand-related evils at the desk, and use one as little as possible.

Working without the mouse

There are a lot of things you can do without a mouse. I use Opera as my main browser, it has keyboard navigation and I can surf for hours without touching the mouse at all.

There are lots of keyboard shortcuts for Windows (see Jon Galloway’s excellent mouseless computing article for ideas), which I started to get better with. These days however I’m using Linux at work and use a variety of quick shortcuts to help:

• I use all four desktops, with Ctrl+1, Ctrl+2, Ctrl+3 and Ctrl+4 to get me to where I want to do. Its really good and fast – especially when I remember to press control with my right hand and the number with my left!
• Opera, as mentioned above
• Katapult, which is a KDE application which allows you to type Alt+Space and type the program you want to run, it even autocompletes
• Vim. I do all my development over ssh and running vim. No dragging and dropping of files, no dragging to highlight to copy and paste, no icons to click on to format or open another file. Absolutely everything can be done without moving hands from keyboard and I have to say that spending the time with the cheat sheet and getting better with it was the best thing I’ve done since I taught myself to touch type in my teens. Not only does it save my hands, I’m also faster than my colleagues for most things. If you haven’t tried it for a few years and think is a basic text editor you might be stuck with on a server somewhere, then look again. GVim is available for most platforms with tabbed editing and its got code folding and autocompletion too.

Alternative input

At work I have a microsoft keyboard that I quite like but which has keys which go quite deep when you press them which isn’t ideal. I need to try changing hands with my mouse, but I also have a beautiful Kensington Pro trackball which is excellent. Its a bit strange with the main button in the bottom left below the ball but the ball is good and big and it is good. At home I rarely use a mouse and have a little external keyboard which has shallow button movement when it is pressed – which seems OK.

Mouseless computing

Its perfectly possible to do a lot of everyday actions without the use of a mouse. Getting up to speed with the shortcuts for the applications you use will take time – but I shall be taking the advice from the Coding Horror article and learning a new keyboard shortcut every day from now on. I am switching back to my trackball and will take time and effort to get my desk set up better – and I’ll let you know how I go. In the meantime, tell me whether you have had similar problems and what your favourite keyboard shortcut is. I think mine is Ctrl + G in Opera – to turn off stylesheets.

Here are a few notes I made when changing SSH acces for an ubuntu server over to using public/private key authentication. These instructions are for commands run on the server to generate keys which are then used to access that same server from elsewhere.

On the whole the process was exactly as straightforward as you’d think, which was nice. The users followed these steps:

1. Generate keys

The user access the server using SSH (still set up with passwords at this point) and runs the following command to generate keys:


ssh-keygen


We accepted the defaults for both the filename (id_rsa) and left the passphrase empty. Empty passphrases aren’t recommended but there will be automated processes using these keys.

2. Set up to accept

For an SSH server to authorise a user, it must havethe contents of that user’s public key in a file called authorized_keys. The user then comes along with their private key and can then gain access. We put the contents of the public key into the authorized_keys file (which doesn’t currently exist for these users).


cat id_rsa.pub > authorized_keys


3. Log in with public key

The users copied their private keys to their local machines and set up their various ssh clients to use these to gain access. For ssh-ing in from another server (and setting up with some of the clients), its the ssh command as usual but with the -i switch to denote the use of a specified identity file, e.g.:


ssh -i id_rsa user@host


4. Force this to be the only means of access

I had some trouble figuring out which line I needed to change in the openssh config file (at /etc/ssh/sshd_config for me running ubuntu edgy) but in the event, this did the trick:


PasswordAuthentication no


That’s it for today, hope this helps someone … including me next time I want to do something similar :)