Been helping my friend Bill build his garage, up in the mountains. I’m 63 years old and out of shape, so doing physical labor for even a few hours at nearly 9000 feet, has proven to be a challenge. But it is coming along. Bill has the whole thing designed in Autocad, and really knows what he is doing. His grandson Josh and I are the hired help. We don’t know much, but we do what we are told. It is coming along.
All posts by dee
Over the divide
Today was a little milestone for me. For the first time I took N8132Y over the divide, solo.
Of course I have been over many times, but always with somebody in the right seat. And Of course, what is the big deal anyway?
But when I learned to fly I was constantly admonished that flying in the mountains is tricky. I have known people who have died flying in the mountains. The winds can be difficult. I’ve had instruction from an accomplished mountain flyer, but still… every time I’ve gone up near the divide before there has been enough turbulence over the ridge that I’ve ended up turning back.
Today I went over. I was at 13,500ft, a comfortable margin over Rollins Pass. I flew on up to Granby, Colorado which is just over the ridge, landed, bought some expensive gas, and came back.
I’m very pleased.
Ubuntu 12.04 and luks encrypted root drive
I had trouble booting the last few kernels that came out in 11.10 (3.0.0-16 and 17), and alas the same trouble with booting 12.04 which I installed today.
My root filesystem is encrypted, and I expect during the boot process to get a prompt for the encryption password. This doesn’t happen, and instead the boot drops into busybox. I was able to just keep using 3.0.0-15 under 11.10 but now that 12.04 is installed I can’t do that anymore. Actually have to try to track this down. .
After a lot of digging around, I haven’t completely got it figured out, but I did find some hints in this tread: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/874774 which gave me a start, and at least enabled me to boot. The thread describes a mixup in matching device names from udev to names in /etc/crypttab. If a match isn’t found, you don’t get a prompt for a password, the device doesn’t get luksOpened, and the boot fails waiting for it. So, the trick is to ensure the matching logic finds a match between the udev devname and the entry in /etc/crypttab. I actually didn’t even have an entry in /etc/crypttab for the root device. Silly me. I had entries for a couple of other encrypted devices. I would love to report that all I had to do was put in an entry in /etc/crypttab and it all worked. I alas not – I haven’t yet managed to get the problem solved. But I now know where to look, and more importantly reading the thread mentioned did make clear the short term workaround, which may be clear to everyone but me: it didn’t occur to me that once I dropped into busybox, I could just do cryptsetup luksOpen /dev/sde3 sde3_crypt, type in the correct password, and then exit busybox. The boot process resumes and is successful.
Update: In the normal course of Ubuntu updates I got 3.2.24 and the problem spontaneously healied itself. Now upon boot, I get an early prompt for the root password. Bob’s your uncle.
Try out the flight planner
The new flight planner is available as of 4/25/12 on the FLYING page. I’m sure there are still plenty of bugs.
There is also a Metar Decoder and a Query Tool that retrieves airports, fixes and navaids from the FAA database.
There are plenty of tools for doing similar things. The Flight Planner is a little unique in that it is airplane sensitive, which makes it much more useful to me than other such tools, but equally makes it less useful for anyone else.