On Sep 25, 2007, at 7:48 PM, Richard Elling wrote: > > The problem with this is that wrong information is much worse than no > information, there is no way to automatically validate the > information, > and therefore people are involved. If people were reliable, then even > a text file would work. If it can't be automatic and reliable, then > it isn't worth doing.
I dunno if I think we have to think this far into it. Consider the Clearview project and their implementation of vanity names for network interfaces. Conceivably, such a feature is useful to admins as they can set the name to be a particular vlan number, or the switch/blade/port where the other end of the ethernet line is terminated. Or their ex-girlfriend's name if it's a particular troublesome interface. The point is, it allows arbitrary naming of something so that the admin(s) can associate with it better as an object. Most importantly, there's a distinction here. Solaris provides the facility. It's up to the admin to maintain it. That's as far as it should go. I don't see this RFE proposal as anything different. To wit, a similar facility has existed for some time in the form of 8 character volume names one may set via format(1M). With that, the same predicament as the one you bring up can arise. However, there's that distinction again. The facility to do so is made available. It's on the onus of the admin to maintain its contents. /dale _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
