One of the long-standing splits for dynamic websites is between dynamiccontent rendering and static content rendering (where you use trickslike 404 handlers to generate a page'scontent only once, write it to a static file, and then afterwards justserve the static file).

(This assumes that static rendering is viable; for heavilypersonalized sites it may be more trouble than it's worth,if you are already effectively never generating the samepage twice anyways.)

Fundamentally the choice is tradeoff of

I think I may have finally woken up to a (potential) cause for my random NumLock issues : the xine media player. Oneindicator, one that I really should have paid attention to earlier, isthat often starting xine will turn on NumLock (and sometimes turn itoff immediately afterwards). It is of course hard to be entirely suresince the problem is erratic, but I've been doing some testing sinceI noticed the correlation and I don't think I've ever had the problemwhen

We've recently been looking into using jumbo frames on gigabit Etherneton Solaris 10U4 x86 (aka Solaris 10 8/07); it turns out that thisis more work than you might expect, and information on it is somewhatscattered.

First, as of S10U4 only a few gigabit network drivers are documented assupporting jumbo frames:

In system design, we're periodically confronted with a choice betweenbuilding our environment out of a few big systems or a swarm of smallones. For example, consider storage; if you want 48 Tb of storage, youcould buy two Sun Thumpers or six or seven smaller 15-disk units. Bigsystems are often attractive; their very size gives them economies ofscale (and often means they cost less overall), and it's easier to dealwith only two boxes instead of six or