matsu

Two improvements for the Mac OS X finder

• When a file is being copied or moved, if it’s replacing another with the same name, the info on both files (such as size, last modification date, etc.) should be shown (Thanks to Bruno Rodrigues for pointing this to me, even Windows does this!);
• When ejecting a volume, if the command is refused because files on that volume are being used, the list of applications using the files in question should be shown, so we don’t have to hunt down every single one to safely eject a volume.

Howto: mounting your Mac filesystem through the internet using SSH

This brief tutorial will teach how to mount the entire filesystem of a fixed Mac computer connected to the internet through encrypted SSH so it shows up just like a network drive on any Mac you want, through any internet connection.

I’ll be talking about the host Mac (the one where the original filesystem resides) as host, and the moving Mac as the client, where the remote volumes will be read/written from.

Requirements:

1. Make sure you have admin privileges on both the host and client computers (although running your main account with admin privileges is not advised);
2. Make sure that on the host machine that you’re either connected directly to the internet and have TCP port 22 not firewalled or you have privileges to reconfigure your internet router to re-route port 22 requests from the internet to the host computer;
3. Make sure that you can access the host computer from the internet, either by having a fixed IP address (not normal on domestic aDSL or Cable connections), or by using a free service such as DynDns.org (this explanation goes beyond the scope of this howto – search for the solution for your own router or Mac on the internet);

Procedures on the host machine:

1. On System Preferences, under “Internet and Network” you’ll find the “Sharing” icon, click it;
2. Under “Services”, turn “Remote Login” on – authenticate yourself as necessary beforehand if needed;
3. Open a terminal window on the same machine, and type ssh yourusername@127.0.0.1 to test if in fact the SSH service has become activated – follow the instructions;
4. If the computer is connected directly to the internet, also under “Sharing”, you’ll find the firewall tab, click on the allow column for “Remote Login – SSH”;
5. Or if you’re connected to the internet through a router, you’ll have to look for port mappings or something equivalent on the router, to relay all internet requests for port 22 from the internet to the host computer (this explanation goes beyond the scope of this howto – search for the solution for your own router on the internet).

Procedures on the client machine:

You will need three pieces of software:

• MacFUSE – obtainable here;
• sshfs – also obtainable here;
• MacFusion – a wrapper to make everything more user friendly, obtainable here, make sure the version you’re downloading is compatible with the core version of MacFUSE you obtained (as I’m writing this, everything is a bit under development, so there are incompatible beta versions floating around)

1. Install MacFUSE and reboot, followed by installing sshfs and MacFusion (which in theory don’t need a system restart to work);
2. On a terminal window on the client, outside from the host’s LAN (i.e., connected through the internet) test first if you can SSH to the host machine, by typing ssh username@completedomain.com
3. If you can login into your account, the next step is to fire up MacFusion (which should be located in your Applications folder of your client machine
4. MacFusion is really simple – preferences are resumed to setting MacFusion to startup itself at boot, to check for updates to itself on Startup, and what to do when the client Mac goes to sleep and resumes.
5. The only thing missing now is to add, if you wish, the host computer to MacFusion’s favorites list – you’ll have to supply the name (whatever you wish), the server (without any “http” or similar prefixes), the Port can be left at 22, you can change the Server Path to / if you want for instance to access the “Volumes” directory to access any external disks that specific user has access to, and the most likely authentication method you’ll be using is “Password”.
6. The first time you try to mount (connect to) to the host’s filesystem from the client machine, MacFusion will even be nice enough to give you the option to store the password in the Keychain – this is up to you, if you trust you computing space enough to store passwords or not.

This is it! If everything worked, you’ll have a brand new volume on your desktop, that works exactly like a local LAN drive, with the permissions of the user you logged yourself as. Now you can do backups remotely through the internet, do anything you could do with a local LAN drive, but through a fully encrypted tunnel, and just limited by both the upstream and downstream speeds of both the host’s and client’s machine internet connections.

If you’re reading this…

…it means that the latest matsu home move has been successful.  Matsu is running in the original XP install, but now running under VMWare Fusion on my Mac Mini, meaning that I’ve shutdown my last Windows non-virtual machine.  I’ve been meaning to do this since the first of Fusion’s beta releases, but it was impossible (or very difficult) to do it, as the first release didn’t support ethernet bridging of the Airport (wireless) connection.  This latest version seems a little faster, and it also adds support for DirectX, and even Vista will run on it.

VACUUMing your mail.app with SQLite

Via BoingBoing and Cory Doctorow (who switched to Ubuntu from Mac OS X), a speedup tip for mail.app – pretty easy and fast.

1. Close mail.app
2. Backup your mail
3. Open a terminal window
4. Go to your mail directory with cd ~/Library/Mail
5. Start SQLite (which is installed by default) with sqlite3 Envelope\ Index
6. Clean up your mail DB with vacuum subjects;
7. Wait for the sqlite prompt to reappear
8. Exit SQLite with ctrl-D
9. Open mail.app again and enjoy the improved speed!

Computing space

While working today, I noticed that my computing space has become increasingly more “onion like”, with layers upon layers of systems.  Here’s a screen capture of my personal daily workspace.

The primary display is the MacBook’s LCD (1440×900) and the secondary display is an external LCD (1680×1050).  I’ve resized them to the same size for clarity.

The main display is the normal desktop, with Firefox, iCal, Adium, a terminal window, etc.  Things get a bit more layered on the second display.  On the foreground you can see a Windows install running on VMWare Fusion locally, running Mapsource.  Behind that on the left, it’s a Remote Desktop connection to my home Windows server, with another Windows install running on it (it’s the WAMP where matsu is served from).  And finally, behind all windows, on the right, is a Citrix connection to a Reuters hosted platform.  It’s amazing what I’ve seen in the evolution of computing since 1983, from my first computer until today…