Category: Technology


Focus, Damnit

OS X has a focus problem. It’s easier to explain with the following screen capture:

I’ve left out the menu bar and the Dock, just to emphasize the following point: which window is in focus? The terminal window or the finder dialogue? If you hit the “enter” key, do you get a newline in the Terminal, or do you acknowledge the “unsafe device removal” message?

Of course, you enter a newline in the terminal. This is but one example of the madness, and it seems to be worse in Lion than it was in previous releases of OS X.

Apple just announced something that has gotten my full attention, and my change my computer buying plans in the short and long term: the next release of OS X, dubbed Mountain Lion, allows a Mac to share it’s screen via an AppleTV at 720p, over the wireless network.

I know there’s lots of easy ways to hook a Mac up to your television, or cross-convert your media library to work on an AppleTV, but this setup allows for seamless access to any video content on your Mac in your living room. No more worries about using Handbrake to make a copy for your iPhone and then a second copy for your AppleTV – you just load the media into iTunes and it plays back over the AppleTV via screen sharing.

At the moment screen sharing appears limited to 720p, but I imagine that as 802.11ac is developed, and the next generation of the AppleTV is released, 1080p will be supported. It also means that I now want to keep my Mac Pro when I get the iMac, as I can easily hook the machine up to the TV in the living room without having to find space in the TV cabinet for the MacPro and all it’s bulk, heat and noise.

Keeps a man thinking, right?

I’ve noticed that each of the three iPhones I’ve owned over the last three years have a problem passing off to the 3G network when the WiFi signal is too weak to use. In other words, when the signal strength on the WiFi network is very low, the iPhone will still prefer WiFi to 3G, even if the WiFi connection is unusable. This happens every time I get to the far side of the house, but it also gets me when I’m on the bus and signal is coming and going, or when I’m walking around outside at work, and while I can still get a little of work’s network, I can’t use my phone without disabling WiFi.

I can’t fix the problem at work – I’m not in control of that – but I can fix things at home. Or so I had thought, with Apple’s mesh networking implementation in their Airport line of products. In previous iterations of my home networking setup, I’ve tried using an Airport Express to extend the network of an Airport Extreme. While it works, it’s not the most reliable thing, and as I have older Airport hardware, I can’t run simultaneous 802.11g and 802.11n networks while keeping things running at d decent speed. Finally, the cost to upgrade to the newest line of Apple networking products is substantial – the current generation Airport Express is $99, and the current generation Extreme is $179. Poking about online, I think I have the answer I need: Open Mesh

Specfically, the MR500 Mesh Router from Open Mesh. It’s $99 per unit, and cleverly runs 2 CPU’s – one for user traffic, and one for mesh traffic. It also uses both the 2.4 ghz band and the 5 ghz band – but the 5 ghz band is reserved for mesh traffic. This is all done in the name of enterprise grade reliability – the packets must keep flowing. The system also supports multiple gateway devices from the wired network to the wireless network, even ones on different ISPs, so failover between networks should be seamless. There is also the provision for per-user rate limiting, public and private networks, and self-restarting hardware if the software stack crashes. All for the $99 per-unit cost. It also has a built in 5 port 10/100 switch, so you can use it to bridge physical network segments.

The only downside to the system, as best I can tell, is that all the management and configuration of the devices is done on the Open Mesh website. They run a web app that you create an account on, and when the device powers it, it looks for it’s MAC address on the service, and configures itself accordingly. My concern comes in for times that my link to the internet is down, but I still want to stream movies and music inside the house. That is one example, and I’m sure others would have better ones, but it’s a concern. I need to do a little more digging and see if the device will just come back up under it’s old settings, assuming nothing should change if it can’t talk to it’s master. I’d feel a little more comfortable if I could run a local version of the cloud management application, but nonetheless, this is still worth looking at.

After doing a lot of reading online, I’ve finally built a new OpenAFS cell in my home network. This involved reading piles of terribly out-of-date documentation and HOWTO’s, and a lot of frustration on my part. I help administer OpenAFS at work, but I’d never set up a new cell before, and the process of working out the right Kerberos keys and setting up the servers with bos were throwing me for a loop.

Eventually, I found the guides hosted on spinlocksolutions.com, which have a very clear walkthrough, with up-to-date explanations on how to setup a Debian-based OpenAFS cell, as well as a Kerberos 5 domain and an OpenLDAP server. They can be used with Ubuntu Server almost without alteration. This is good, as I have a passing knowledge of Ubuntu from previous projects.

However, there were two gotchas I ran into when doing an install with Ubuntu Server:

  1. The Ubuntu installer had added my FQDN to /etc/hosts with an IP address of 127.0.2.1, which makes the afs-newcell script lose it’s mind when trying to create the CellServeDB entry it needs.
  2. The Ubuntu apt-get delivered copy of the afs-newcell perl script has an error in it, that it doesn’t add the -noauth flag when creating the dafs server. You will see errors about not having permissions to create the dafs server. Simply edit the script and add the ‘-noauth’ flag.

Once afs-newcell runs properly, everything else goes exactly according to the documentation – afs-rootcell creates things as it’s supposed to, and the various Debian/Ubuntu packages to configure PAM work as expected.

Google Ad Sense

I’ve decided to enable advertisements on this blog – primarily to offset the cost of hosting and running the thing. I’m going to use Google AdSense, as their ads aren’t really that irritating (no Flash), and hopefully they will be unobtrusive. If this turns out to be wrong, or they bother me, they will get shut down as fast as they were added.

Just letting everyone know.