Somehow, I just spent four hours playing Ikaruga.

They weren't kidding. This game is hard. Holy shit, this game is hard. I don't think I've ever played a game where it took me four hours to get to the THIRD STAGE before. This game rules.

I don't think I'll be sleeping this weekend.

(oh, and props to mpyne, who kicks *major* ass for dropping Ikaruga to me in the mail. The note he placed in the case reads "Let me know how Level 3 is. I only ever made it to the boss of Level 2." Holy shit this game is hard.)

wireless future

(responding to ChipX86)
Dude. One word.


Ok, to be slightly less cryptic: Wireless devices won't ever really replace their wired counterparts until they no longer require battery replacement to run. Batteries that recharge by gyroscopic motion? Ok, cool. Batteries that recharge by quantum phase induction? Hey, even if I just made it up, it sounds cool, and as long as it means that I don't have to put new batteries in when the current ones die, I'm all over it.

The main reason I don't have any wireless peripherals right now is the battery issue. I've almost talked myself into getting one of the Logitech mice that recharges on the base station - that's pretty close to my ideal scenario. It takes the whole "there's a battery inside" detail and makes it completely irrelevant.

build system notes

We had a discussion in #kde-devel earlier about what KDE's requirements for a build system are. What are the current problems we have with autoconf/automake/libtool? What features do they provide that we really care about? How hard would it be to replace any/all of them with things that suck less?

I took notes of the discussion. They're below; I'd like to get more feedback on this.

(One of the first points that I'm sure someone will make is "auto* is cross-platform! We need to support KDE on platforms that aren't Linux!" etc. Look, we realize this. However, auto* provides lots of problems for us on platforms we do care about, including MacOS X and Windows. (Ask RangerRick or js about them on IRC, or email them.)

Just because we're using auto* and friends doesn't mean that our code works; as a matter of fact, RangerRick noted that so far, all of his issues with the Mac port of the work-in-progress KDE4 have been build issues, and none of them have been code-related yet.

This is clearly a problem and since KDE4 is an aggressive new major release, we should solve it in the KDE4 timeframe. We don't want to have to wait until KDE5 for a build system that doesn't suck, do we?

Without further ado, the notes from the discussion.

Must support:

  • generating binaries (duh)
  • generating shared libs (on all ELF platforms + MacOS X; Windows?)
  • icon installation
  • uic, moc, KConfigXT, etc
  • GCC visibility
  • automatic dependency resolution
  • manual hints for dependency resolution
  • flex/bison
  • non-recursive (flat) builds
  • --enable-final
  • builddir != srcdir
  • simple to the point of being learnable within 5 minutes
  • kdeinit support (?)
  • multiple build targets (libfoo, libbar, libbaz) in one file
  • --compile-slots, like in unsermake
  • pkg-config support
  • support rpath sanely
  • ability to link & run uninstalled binaries
  • easily integrated into KDevelop
  • 'admin' needs to be shipped in KDE instead of in src of each app (if we keep the 'admin' dir, that is)

Would be nice, but not necessary:
  • having a standard and distributed build system and test suite
  • ability to build from svn:/trunk/KDE


cool interview

Matt Harrison sent me a link to a cool interview with Ivor Hewitt, one of the guys working on KHTML lately.

Looks like the interview has been taken down. Maybe it'll come back up soon.

Ivor, do you have a blog? Because you should. Planet KDE could use some KHTML blogging love...

wtf havoc

[@hp] clee: hold me like you did by the lakes of naboo!

I blame ajax

* clee kicks ajax
[clee] dammit, man. I really want a usable Expose feature. Like, yesterday would have been good.
[ajax] oh yeah, totally my fault
* clee blames you.
[ajax] why yesterday?
[clee] ajax: well, yesterday would have been good. today would have been acceptable. but if it gets here tomorrow, that's not soon enough.
* clee sighs
[ajax] i was thinking maybe there was some event yesterday
[clee] hahaha
[clee] no.
[ajax] like you were trying to show off X to some hottie in the coffee shop or something
[clee] hahahaha
[daniels] haha
[clee] and she whips out a Mac and she's like "Let's see your network-transparent windowing system do THIS!" and hits F9?
[ajax] but then she's all "shit boy, five year old acceleration architectures ain't gonna get you any poon"
[clee] yeah, happens to me all the time
[ajax] *smack*

vmware update

Just thought I'd post a quick update about my situation re: my computer at home, since I know you all care so much.

It turns out, after wiping my partition table and starting over from scratch and getting Linux back up (which took all of about ten minutes), Windows installed fine from the SATA DVD drive.

I have no idea how this is possible - this page says, and I quote:

> Out of the box, no current Windows version, including Windows Server > 2003, supports SATA drives.

My best guess is that the BIOS enables some sort of PATA emulation that Windows can use to find that drive. That's the only thing that makes sense.

And I was a little hard on VMware, to be honest. I mean, I was using a feature that they specifically warn against most people using, while running 32-bit VMware on a 64-bit (unsupported variant of a) host OS. I'm reminded of a quote here...

> People who do stupid things with hazardous materials often die.

Granted, I didn't exactly die, but I think it somewhat applies.

unexpected results

Red Hat, my employer, has a site license for VMware. (Well, either a site license, or an assload of Workstation licenses, I'm not really sure what the details are.)

I decided "Hey, why not play with the new release? You've got new hardware. Maybe VMware will run acceptably fast on it!"

Man, what a fucking brilliant idea that was.

Backstory: I haven't booted Windows in a few months, not since Doom3 came out and wasn't available initially on Linux. However, I have some shiny new devices in the new box, including a SATA DVD burner, which so far doesn't seem to work with Linux very well. Ubuntu's kernel enables SATA ATAPI support, which Jeff Garzik tells me is a bad naughty thing of them to do since it's not ready yet. Which results in my ability to *see* the drive on /dev/scd0, if the planets align properly, but I can't actually use it for much.

This machine doesn't have a floppy drive, since I'm a cheap bastard, and I happen to agree with Apple on this one. Fuck floppies. They should have died a long time ago. I also refuse to run Windows XP - I bought and paid for Windows 2000, a long time ago in a galaxy far far away, and it's the last release of Windows that I really plan on ever using. Windows 2000, being rather old, has some deficiencies, however. Like not having SATA support in the installer (unless you load a driver from a floppy, which I don't have).

I think to myself, "Hey! VMware! Raw disk support! It used to work pretty well, why not try doing an installation from a virtual machine into a physical disk? You can use the VM to download drivers, then create a new hardware profile, reboot into it, and maybe that'll work."


Let's just say that this was probably the worst idea I've had all night, even worse than eating that third slice of pizza. My partition table on /dev/hda now looks like this, thanks to VMware:

Disk /dev/hda: 41.1 GB, 41174138880 bytes16 heads, 63 sectors/track, 79780 cylindersUnits = cylinders of 1008 * 512 = 516096 bytesThis doesn't look like a partition tableProbably you selected the wrong device. Device Boot Start End Blocks Id System/dev/hda1 ? 216399 1904881 850995205 72 UnknownPartition 1 does not end on cylinder boundary./dev/hda2 ? 723265 1262922 271987362 74 UnknownPartition 2 does not end on cylinder boundary./dev/hda3 ? 167316 167316 0 65 Novell Netware 386Partition 3 does not end on cylinder boundary./dev/hda4 2671568 2671619 25817+ 0 EmptyPartition 4 does not end on cylinder boundary.Partition table entries are not in disk order

I'm not even sure what to say about that.

(For those of you wondering why I wanted to play with Windows in the first place - SATA DVD burner. I know that I can install Win2K drivers for the SATA chipset, and I know that the DVD burner will *probably* work there.)


My new toys arrived today.

That's one Lian-Li PC-60, one Chaintech VNF4/Ultra motherboard, and one Athlon64 3000+ CPU.

This machine is officially fast enough to scare me. I can play Doom3 at my monitor's native resolution (1680x1050) and the frame rate doesn't drop below 60fps even with baddies on the screen.

The only other goodies I need to complete this box are a couple of 400G SATA drives. The Hitachi model is only \$275 on NewEgg, which means that it's now possible to put over 1TB of storage into a box for under \$1000.

Holy shit life is good.