Re: Machine naming convention

[Bob Van Cleef <vancleef@microunity.com>]

The most effective method I've used in the past is a simple, generic
name, based losely on the type of system; sunos, irix, win95, etc.
Such as wk001, wk002, wk003...  allowing the users of personal
workstations to select an "alias" -- in which case the alias became
the canonical name and the generic name became the CNAME.

This allowed administrators to easiely identfy all the SunOS systems
for running batch administrative functions, while allowing the users
to personalize their environment.  The generic name remained with 
the system, the personal name changed with the user.  

Basing the primary identification on a user or location will lead to
administrative head aches as people and systems move around.

Bob

On Wed, 5 Aug 1998, Jeffrey Roberts wrote:

> We are in the process of integrating several types of OS's, UNIX
> and NT, in our company and we would like to standardize on a machine
> naming convention.  Up until now we have used elements of the periodic
> table, car names, personal names, etc... for machine names.
> 
> One suggestion is to use "location" + "userid" as a machine name,
> eg: "torjdr", or "nyvito"
> 
> Does anyone have any good or bad experiences with this convention
> or can you suggest something else?
> 
> Thanks.
> 
> --
> -----------------------------------------------------------------------
> Jeffrey Roberts		jeffr@interlog.com
> Toronto, Canada
> 

><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>  ><>
Bob Van Cleef, Member of Technical Staff         (408) 734-8100
MicroUnity Systems Engineering, Inc.         FAX (408) 734-8136
475 Potrero Ave., Sunnyvale, CA 94086   vancleef@microunity.com