Skip to Content

Posts Tagged ‘linux.conf.au’

LCA Day #1

Permalink

I had been meaning to post daily updates from LCA but the conference is just too awesome to get a chance to blog- ROCK!

Debian Miniconf #6
As a Debian groupie I started the conference off with a brief by the Debian project leader (DPL) Anthony Towns. The first minute of the talk was really strong. Then his phone rang and he took the call! It was the first time I had ever seen this at a conference.

After a good minute of “uh huh *pause* yes, yes, ok ok” he got off the phone and asked one of the audience members to call his mum. Naturally, everyone was very confused. It turned out he was moving today and his mom was the only person in the area to look after the movers.

With that brief interruption the Debian miniconf was off!

A few of the highlights:

  • Funny: m68k buildd is keeping up properly thanks to an emulated build box running on amd64
  • Hopeful: the rework of the GNU Free Documentation License to fit into the DFSG
  • Sad: There were updates on IceWeasel. Why is Sun better at working with Debian than the much more open Mozilla Corp?

bluetooth cameras

The next talk was interesting because of the problem domain: honey bees. Jamie Honan, the presenter, was trying to find a way to keep an eye on his remote bee hives to prevent them from swarming. The problem with a swarming hive is that his next door neighbor is allergic to bees. The best detection method of a swarming hive is smacking the hive and listening to the frequency of the reaction. He didn’t have a mechanical process for smacking the hive yet but a device like the Fascinating Electronics USB servo controller that I brought along for show and tell would work great.

The last session I went to before the embedded show and tell was a talk by Keith Packard on the direction that X.org is heading. If all goes according to plan it shouldn’t be necessary to have much of an xorg.conf in a few more versions as most everything will be hot-pluggable. w00t!

It was a great day. Thanks to the Seven who are putting this week together.

The Story So Far

Permalink

This is assignment zero, a brief biography, written for Dr. Budd’s CS419 and CS480. Enjoy!

Part of my decision for coming to Oregon State was that my Debian install had automatically chosen ftp.oregonstate.edu as the fastest mirror available. The message this sent me as a high school student was that OSU, our at least a few people on campus, cared about Free Open Source Software. It didn’t hurt that OSU had an engineering program that is well known for creating quality graduates either.

During the fall term of my freshman year I meet up with the ftp.oregonstate.edu admin, Scott Kveton. At the time he was forming the Open Source Lab and was looking to hire students to write open source software. I had been using Linux for a couple of years and could hardly contain my excitement; I was going to be paid to write open source software as a freshman! And at the time I had no idea that this job was going to open up crazy amazing opportunities for me and all of the other students at the Open Source Lab.

Every successful project I have ever worked on has had a few components: an interesting problem, an experienced mentor and hands off management. At the Open Source Lab I had all of these components for three years and I grew a lot as a developer and person. The OSL and FOSS are great opportunities for students to work on interesting and large projects even as they are still developing their skills in the classroom.

The software I find the most interesting is behind the scenes: the system software. Kernels, device drivers and networking protocols are all things that most users don’t have to think about but are nonetheless very important. There are a few interesting properties about this level of software. First, it must be extremely well thought out and written; if this software goes bad then the user is going to have a very bad day. Second, the code is usually rich with interesting data structures and programming tricks to squeeze out as much performance from the hardware as possible. And finally a lot of smart and interesting people work in system software and I like working with those types of people.

I decided I wanted to be a computer scientist after working for two high school robotics project. The patience and guidance of my mentor, Ron Jackson, helped improve my programming abilities a great deal. Despite the tight deadlines involved in creating full scale humanoid robots in under 6 months during both years the software was written and working before the competition. It was a huge confidence boost to have that responsibility and trust invested in me and in the end come through with a working solution. I had found something I was good at and had a really fun time doing. Perfect.

After college I would like to work as a Linux Kernel developer. This decision is partly influenced by the great experience I had working on a genetic algorithm for the CPU scheduler while working at IBM in Austin. It is also a result of the number of great interactions I have had with members of Kernel community including: Val Henson, Greg KH, Jake Moilanen, the entire OzLabs crew and many others that I have probably forgotten. Plus, I like penguins- that helps.

/me runs off to Australia for a bit.