DWiki has a pretty simple way of displaying comments; all comments ona single page, which also has the main entry. There's a lot of moresophisticated comment handling systems, like LiveJournal and Slashdot,and I won't deny that part of why DWiki is simple is that simple is less code . But part of it is deliberate,because it's all about the context.

Specifically, I want people who read comments to have as much contextas possible, which means that I want them to

Both SANs and cluster filesystems have multiple machines talking tomultiple shared disks that all of them can see. The difference is thatSANs are designed for a single machine to talk to a given disk at atime, while cluster filesystems allow multiple machines to talk to thedisk at once.

Which raises the big question: why do you need cluster filesystemsat all? Why can't multiple systems share a single disk without doinganything special?

There's two problems with shared disks: caches and coordinatingupdates. These

Since I just went digging for this the other day , here's what I know about what controlswhat Ethernet devices get named on Red Hat Enteprise (and probablyalso on Fedora, but I haven't looked at my Fedora systems in thislevel of detail).

• if kudzu is enabled, it uses /etc/sysconfig/hwconf to nameeverything. If there is no such file or the data in it doesn'tmatch current reality, various bad things happen.

  (You can probably hand-edit