As time goes by, there's an increasing amount of stuff I want to writedown. One of the things that stalls me out on this (apart from the sheereffort of writing) is the question of where and how I should put them;in particular, should I make a wiki page or write a blog entry?

In theory this shouldn't come up; WanderingThoughts is part ofa hybrid wiki-blog, which I've extolled the virtues of before . In practice this is an illusion

We just got the following message today from a well regarded commercialbackup system that costs a lot of money:

* host:/filesystem save: path length of 1025 too long, directorynot saved: /filesystem/long/dir/path/...

Path name length limitations; just what I like to find out about inmy backup software. (I suspect that the limit is 1024 characters andthat the path is not exactly 1025 characters, it's

A lot of hardware RAID systems (whether controller based or SANs) liketo present a multi-disk RAID array to the host operating system as asingle device. While attractive, this can lead to hard to diagnoseperformance issues under load (well, a random IO load).

The basic problem is that you get the best performance by keeping allof your disks busy. But when you aggregate multiple disks into what theoperating system sees as one disk, the operating system is going toschedule IO for one disk

Classic Mistakes Enumerated is an exerpt from the book Rapid Development by Steve McConnell; itruns through 36 familiar classic development mistakes that people makeover and over again. Brooks's Law makes an appearance, of course.

(From Bill de hÓra .)