New sharename functionality

For those who do not read the code all that often you might not be
aware of the changes to sharename functionality which have been
committed to the 1.3 branch over the last few months.  The goal of
all of this has been to simplify the notation needed to access AFS cells.

In the past, the OpenAFS Client Service has always published its
SMB name as the first ten letters of the %MACHINE% name
appended with "-AFS".  For example, my machine "CERBERUS"
is given an SMB name for the OpenAFS Client Service of "CERBERUS-AFS".
Now this is really ugly and also is somewhat hard to utilize in general 
purpose
scripts or roaming profiles.

Over the last several months there have been several submissions of how to
change this.  These have been merged together into the current set of rules.
If the selected Lan Adapter is a loopback, the SMB name will be either the
string specified by

     
HKLM\\SYSTEM\\CurrentControlSet\\Services\\TransarcAFSDaemon\\Parameters
          (REG_SZ) "NetbiosName"

or if not found, the name "AFS".  If the selected Lan Adapter is not a 
loopback,
then the traditional "%MACHINE%-AFS" is used.   When the loopback adapter
is not used it is not safe to publish a non-unique SMB name because it 
will cause
name space collisions with other clients on the same LAN or sharing the same
WINS.

This change provides for the ability to refer to the AFS root (not 
root.afs) as

    \\afs\all

and the athena.mit.edu cell as

    \\afs\all\athena.mit.edu

I still found this notion to be quite awkward.  Today I added the 
ability to skip
the use of the magic share "all".  Instead all valid cell names are now 
valid share
names as well.  This means that finally on Windows you can refer to the 
athena.mit.edu
cell as

    \\afs\athena.mit.edu

The "all" share is still available for those who have existing shortcuts 
they wish to
preserve.

Jeffrey Altman