I'm evaluating ADSM for deployment in a large building here with many different
types of computing setups.  The only logical way I can see to keep track of
everything is to make sure everyone uses their machine's FQDN for their
nodename.

Now, this is no problem for Mac and DOS/Windows clients, we'll just have them
type their FQDN into their dsm.opt files.  The problem comes in with UNIX
machines.

It appears that the ADSM client does the equivelant of a 'uname -n' to pick the
nodename.  The problem is that for most machines here 'uname -n' only returns
the hostname portion of the FQDN.

I don't want to specify nodenames in all of the UNIX host's dsm.opt files for
two reasons; 1) I would like to take advantage of the "Passwordaccess Generate"
feature, and 2) I would like to allow groups of UNIX machines to run NFS
mounted ADSM binaries/config files.

Is there a painless (or mostly painless) way to get the UNIX ADSM clients to
pick the FQDN as their nodename?  I _really_ don't want to reconfigure 400 UNIX
machines here.

Thanks in advance,
--
# Baba Z Buehler - 'Hackito Ergo Sum'
# Baba Z Buehler - 'Hackito Ergo Sum'
# Beckman Institute Systems Services, Urbana Illinois
#
#  "I only use my gun when kindness fails"
#                                -- Robert Earl Keen, Jr.
#
# WWW: http://www.beckman.uiuc.edu/groups/biss/people/baba/
# PGP public key on WWW homepage and key servers (key id: C13D8EE1)