They've changed a few things. Quite a few things. And I was just starting to get seriously annoyed with them when I fixed the last difference and suddenly my code worked.

A bit more banging on various bits and I have a copy of my blog running on my home network.

Now I'm building a dev environment on my new notebook. I already have CentOS 4.4 on there (under VMWare), but when I'm developing I spend a pretty significant amount of time benchmarking code, so I need a reasonably precise timer, and running CentOS under VMWare does not give you that. At all. You can, with a little effort, set it up so that the clock doesn't run at either half or double speed, but accurate sub-second timing is not on the cards.

In testing previously I've found that Fedora is substantially better behaved in this respect, so that's what I'm installing right now.

VMWare has a helpful 25-page document explaining why the clock doesn't work when you're running Linux under VMWare, but personally I'd rather they just FIXED IT.

Well, okay, granted that I'm running a free operating system under a free virtualisation system under a rather clunky desktop operating system on cheap consumer hardware and have no right to expect the damn contraption to boot much less keep accurate time.

Nevertheless.

Update: Okay, so FC5 doesn't want to play nice either. Bah.

* Note to self: Check to see if that memory leak in Psyco has been fixed under 2.5. They did say that there had been a bug fixed relating to that.

Posted by: Pixy Misa at 07:42 AM | Comments (4) | Add Comment | Trackbacks (Suck)
Post contains 301 words, total size 2 kb.