David Nusinow: Random Bits
I've been extremely busy with labwork lately, trying to get a second paper ready for submission in the coming months. It's taken an obvious toll on my free software work, but that's life I guess. The upside is that the other night I realized why a year and half's worth of experiments kept turning up with negative results that seemed to contradict our other results. It turns out that this experiment was conceptually flawed, and even though I wasted a year and a half on this I did learn something even from those negative results that should go in to the final paper. I'm actually relieved, because even though I don't have all the data yet I can really see how the paper will end up, so I can start writing soon. Oftentimes knowing why something is wrong so you can fix it is even more important than being right.I set up an ikiwiki to help organize my lab data a few weeks ago, and it's been a huge win. Joey really did a fantastic job on the program and I can't imagine using a wiki that doesn't share a very similar design for any of my personal stuff. I showed my boss some of my data using it and now he wants me to set up a wiki for the lab. He actually wants me to show off my wiki to give my lab members a feel for the idea. Since ikiwiki doesn't seem to be appropriate for my lab members, I'm going to have to look in to the giant list of wikis to figure out the exact right one for my lab's requirements. This is something I never expected to be doing in grad school.
Because there's no way my brain can go without doing a little bit of programming, I finally sat down and wrote myself a small shell script that lets me grep through pdf's, which is something I couldn't find googling around. If you have a lot of pdf's like I do and don't something like beagle or tracker churning away in the background constantly just so you can search them, this is very helpful. It's obviously very crude, but it gets the job done nicely. It relies on the pdftotext program; hopefully it'll be of use to someone.
I've been digging in to my copy of UNIX Power Tools lately, trying to pick up new UNIX and vi arcana, which is something I haven't made a real serious effort to do in a long time. It's been surprisingly fun to try and replace old habits with things that I know are better but don't use. A good example is that I usually will fire off a new subshell in vim when I should really just suspend vim and use my original shell to save time. Re-examining the basics of how I use the system has been a lot of fun, and has made me a lot more comfortable with the simple day to day tasks.
keeps the release away.
That's why, following 

(To be fair: It is not theirs, Tolimar will be the godfather. But they do it with a perfection.)
No Tags
So, you know, SCO has been suing various people in the Linux community for the last few years, claiming that some code in Linux was stolen from them. So, I’m willing to bet that a lot of people were wondering: what exactly is SCO UnixWare? Well. Have I got a treat for you. Thanks to this wonderful thing called
Theorem: If aptitude is used, set to automatically
remove unneeded packages and every not willingly installed package is
marked auto, 
Intel is always seen as good guy, who is writing open source drivers,
releasing at least some specifications for hardware. Unfortunately it is
not always the case. If you want to use their new embedded solution -
Menlow CPU and Poulsbo chipset, they provide you lot of crap.
Basically what you get is a zip file containing several Microsoft Word
documents, badly formatted text files (end of lines at each 80 chars),
PDFs and some zip and tar archives. If you look to one of these
archives, you will get binary graphical installer, which will install
license, uninstallator and yet another set of tarballs. These tarballs
finally contain binary and source packages you need to make graphics
work on this platform. Maybe somebody did this to practise various ways
of compressing and distributing things, but it is really amazing how
many times you need to decompress several archives to actually get to
the things you want.
Unfortunately at the end you will find out that libgl1-mesa-dri-psb
binary (DRI driver for graphics) has no sources and Intel is not willing
to give them to you. Bad luck if you have slightly different
distribution than one of these which are supported (FC6, Midinux-build9,
ubuntu-gutsy, ubuntu-hardy) and the provided binary simply crashes.

Airports visited in the past week: 4 (rising to 6 in 12 hours or so)
Back in February, I worked on packages providing
Yesterday, I submitted my diploma thesis (one day before the deadline — yay!), so I will hopefully have much more time to work on my Debian packages again.