Why our Solaris fileservers still use the automounter
In theory, there's no need for your fileservers to use the automounter.Even if you make the filesystems visible under their normal names aswell as in /export , you could mount them explicitly in /etc/vfstab .However, doing so would significantly complicate our environment,because it turns out that the automounter worries about a number ofissues for us.
Of course, one big reason to use the automounter is administrativeconvenience; you can use the same set of automounter maps on yourfileservers as you do
Please test your error paths
One of my peculiar traits is that I test error paths, sometimesobsessively. If I write an error check into my code, I am not happyuntil I have induced the error and watched the error check firecorrectly. Judging from some of the code that I've seen this makes me ararity, but it shouldn't be this way.
In fact, I sometimes think that explicitly testing error paths is moreimportant than explicitly testing regular code paths. It is usuallypretty obvious when regular code paths don
今日我地學成語：光明磊落
還有為明光社打氣呢。明哥話齋，我地係咩人？我地就係做事光明
哈哈哈
A gotcha with the automounter and loopback mounts
On Solaris, there is a combination gotcha with the automounter and mountson the same host. It goes like this:
- your fileserver normally has /dev/whatever mounted on /export/foo.
- your generic automounter configuration mounts fileserver:/export/fooas /foo.
- you need to do some maintenance to the filesystem, so you unshareand unmount /export/foo.
- after you're done you try to remount it, but you get a message thatthe mount point is busy. The only mention of
On storing source code in some non-text format
Every so often these days there is some agitation that program sourcecode should not be stored as text but instead in some more intelligentand more abstract form, and just presented as text by editors.
This is the programming language version of the web's 'semantic markuponly' movement, and it fails for the exact same reason that only a smallfringe writes in purely semantic markup: the appearance of the text is important, it is not an afterthought. Programmers care not justabout the meaning of their code but
Why ZFS's data integrity is less important than Solaris's usability
The bottom line is that Solaris is hard to administer (yeah, it's afair cop), so server data is just going to have to suffer. Hopefullysome day Solaris will be as easy as redhat, or debian, or ubuntu, or
. Some day. Meanwhile, I'll choose dataintegrity over ease of administration. The problem with this is that quiet disk corruption is not currently abig issue for most people; it just don'
Menu