Doing profiling and performance tuning on a web application is normallya big pain. It's hard to profile things when processes (or threads)are always coming and going, and the typical web environment has somany sources of random delays that it is difficult to do fine-grainedperformance comparisons between two bits of code.

With WSGI, you can get out of this. Your WSGI application doesn't dealwith the web directly, so you can write a WSGI frontend that is just atiming and profiling harness

One of the little divides in Unix is the one between people who set uptheir shell to have a per-shell command history (a local history) andthe people who set their shell up to use a global history.

While I know perfectly sane and sensible people who are in the globalhistory camp, I am firmly on the local history side, because to me myshell history is contextual. When I hit cursor up or tell a shell toredo the last command, I want it to do redo the

The link of the time interval comes from the online comic strip BonoboConspiracy , whichneatly summarizes the reality of XML on the web in today's strip .

The following is the ZFS-based design we would like to use for our newfileserver environment , presentedfor your entertainment and whatever use you can get from it.

The basic thing we give people are 'storage pools', which are made upfrom one or more standard sized 'bricks' of storage. Each storage poolcontains one or more filesystems, and is owned by a group (or a singleperson).

(Here I am using 'filesystem' to mean 'distinct mount point' or'different