Suppose that you have a model formset and for some reason you want toadd an additional field to each individual form (or perhaps you want toreinterpret a model field into something that is more user-friendly),a field that is of course not in your model schema.

At one level, adding custom fields or custom field handling toa model formset is relatively simple once you know what to do . At another level, the question is howto get access to information about the field. The normal way of

Yesterday I said that XHTML was an obviouslyflawed standard right from the start. I should actually clarify that,and then explain it. First, XHTML is probably not flawed from a strictlytechnical perspective (I don't have the expertise to be sure). Instead,it has always been flawed on the larger, social level of how nominalstandards turn into real standards that people actually use.

(Ie, XHTML doesn't solve the real problem .)

The short version is that XHTML was doomed from the

The IE team famously doesn't pay too much attention to web standardslike, oh, XHTML (to give one famous example). As it happens, I thinkthat there's a decent devil's advocate argument for this position ( asI've mentioned in passing ).

(At this point, I would like to make it utterly plain that I don'tagree with what IE has done in terms of standards. That's why this is adevil's advocate position.)

(A quick disclaimer: this is how it works in Toronto. I think it's howit works pretty much anywhere where you have a choice of DSL providers,but I'm not sure.)

There are two parts of your DSL service: providing the basic DSL signaltone, what lights up the '(A)DSL' light on your DSL modem, and youractual PPPoE-based 'DSL ISP service' that connects you to the Internetthrough your ISP. What a lot of people don

The first and most important thing to know is that you should completelyignore what you'd think is the right way to do this. Trying to use whatyou find at System → Administration → Network for this(if there's anything there) is somewhere between useless and activelycounterproductive, even though it can be used for at least some othernetwork configuration things.

(This is system-config-network. If you installed Fedora 14 from scratchinstead of upgrading from a previous Fedora version you may not

Yesterday I wrote that even in twoor three years, building on btrfs would be risky because we'd probablybe one of the early people doing serious production deployments usingit. I want to note something related to that statement: what I said hasalmost nothing to do with how ready or not btrfs will be in two or threeyears, and everything to do with timing and release schedules.

Production deployments are almost invariably based on Linuxdistributions with long term support, the most prominent being UbuntuLTS and Red Hat

In light of yesterday's entry , the obviousquestion is what options we have for an alternative to Solaris in thenext generation of our fileserver infrastructure. I've been thinkingabout this for a while, and at the moment there are three mainalternatives.

The obvious option is OpenSolaris Illumos . However, there's a lot of question marksaround whether Illumos will really be able to deliver a viableopen source Solaris alternative. There's also even bigger questionmarks about whether it makes sense for us to

One of the things that I've been doing over the last while is thinkingabout what our long-term future with Solaris is; my best guess is that 'long term' herestarts somewhere around 2013. In theory the simple thing to do is tokeep running Solaris in basically the same setup as we have now, just onupdated hardware, but there are two potential problems with that idea.

The first is that it isn't at all clear if there will be affordableinexpensive 1

Recently at home, my testing Firefox started hanging when I tried to visit a particular website that Ibrowse every so often (experimentation eventually showed that it woulddisplay the site, but very very slowly). I could browse it from work, mysyndication feed reader at home was still talking to it, and in fact myregular Firefox instance could still see it. It was rather odd, or evenoutright mysterious.

My home machine has a native IPv6 address and connectivity (not justa 6to4 setup