On a similar topic, I was going about deleting some nodes from
one of our servers today, and I was struck by the inconsistency
of some command names. For example, one "DELETE"s filespaces, but
"REMOVE"s nodes. I'm always struck by the oddity of the
REMOVE command when it becomes shortened to "rem hostname". It
always feels like a comment.

 -- Tom

On Wed, 16 Dec 1998, Eric LEWIS wrote:

>     Someone said consistency is the hobgoblin of small minds . . . so call
>     me small minded.  There is a reserved word "inclexcl" that pertains to
>     UNIX clients and allows a path to an external file where an include
>     exclude list is stored (or so I was told by the UNIX gurus here).
>
>     Now, and in addition to not in replacement of (I think) there is an
>     entirely new use of the same reserved word.  (As explained below.)
>
>     Am I mistaken or is this an example of ADSM terminology becoming more
>     like English where the meaning of a word depends on what you mean not
>     what you say?
>
>     erl UW-Madison
>
>
>______________________________ Reply Separator 
>_________________________________
>Subject: Problem with Client Option Sets
>Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>  at IPNET
>Date:    12/16/98 4:49 AM
>
>
>The proper syntax is:
>DEFine CLIENT OPTION optsetname INCLEXCL "include d:\test1".
>In other words the include or exclude must be inside of the quotes. If your
>path name also has quotes, then use single quotes for the outer pair.
>INCLEXCL is the option name, the include or exclude is part of the option
>value. The B/A client will recongnize the need to parse for the include or
>exclude inside of the quotes.
>
>Tom Brooks
>ADSM Development
>