I have some wishes for docs.sun.com , Sun'stheoretically helpful collection of online documentation.

Sun has a lot of documentation about how to do things with Solaris.Well, how to do things with specific versions of Solaris, for exampleone for each specific release of Solaris 10. This level of archiveddocumentation for each specific release is commendable, but it leadsdirectly to my first wish:

I wish that Sun had permanent URLs that were always the current versionsof any particular document; I would

I've been talking about my wait for Solaris 10 update 6 for a while,because it promised improvements and bug fixes for various ZFS issuesthat had been giving me heartburn. Since it's been out for a while andwe've actually put it into production on one server, it's about time Idid a review on how its ZFS changes stack up.

• refquota doesn't actually solve our ZFS pool quota problem , but it was never going to; it turns out thatI failed

Given the recent commotion over some of LiveJournal's business decisionsand people's unhappyness with LiveJournal as a result, I've beenthinking about the various ways that LiveJournal makes itself sticky(and thus hard to leave, and so on). I think that there are threegeneral levels of LiveJournal stickyness, in ascending order:

• the simplicity and ease of use for individual users.

• the network effects: the more that people that you want to read useLiveJournal, the more attractive it is to be there and

In thinking more about undo issues , I think that thefundamental misconception of designing an undo system is to think of itas purely operation based, instead of something more complex (I don'tthink that it's purely time based either). Undo is only operation basedover the very short term, where you are undo-ing an immediate mistake.

I've been trying to think about what things you do with undo, ingeneral. So far, what I have come up with is:

• fix