3. You must know the client’s interface type, subnet
mask.
4. You must know the type of kernel build area.
5. You must know the swap device and partition on the
client.
6. You must know the client’s hardware Ethernet or FDDI
address.
7. If the client and the server reside on different subnets,
you will need the address of the gateway(s) that the
client can sue to communicate with the server.
Do you want to continue? (y/n) [y]:
4. Enter y to continue. You see the following prompt:
Enter the client processor’s hostname or press RETURN to quit:
5. Enter the host name for the DMS client.
If you enter a host name that is not in the server’s host database, you
see a message similar to the following:
arp failed on hostname "client1"
In the above message, arp is the Address Resolution Protocol. If you
receive this message, check the /etc/hosts file to determine the
correct host name. If the client was never registered with a network
naming service (such as BIND or NIS) or was never entered in the
/etc/hosts file, press
Ctrl/C to exit the dmu utility and manually add
the client to the /etc/hosts file before you restart the procedure.
____________________ Note _____________________
For the remaining examples, assume that the Return key is
pressed to accept the default response.
You see a prompt similar to the following:
Enter the path to contain the root file system. [/clients/client1]:
6. Enter a path, or press Return for the default, /clients/hostname.If
you specify a path other than the default , the directories in that path
already must exist. The path must begin with /clients, and can be no
longer than 25 characters.
For example, if you want to differentiate between client
systems in different departments at your site, you could specify
/clients/deptname/hostname as the root location. The deptname
directory must exist already under the /clients directory.
You see a prompt similar to the following:
Enter the swap device and partition on client1. [dsk0b]:
Managing DMS Clients and Environments 12–3