Network File System
(See NFS )
network hardware address
modifying for DMS client, 12–9
specifyingfor DMSclient, 12–5
network information
forDMS servers and clients, 10–2
Network Information Service
(See NIS )
network interface
for DMS clients, 10–8
network naming service
registering DMS client, 10–7
.new.. files,9–4
NFS
checking server status, 13–2
daemons required by, 10–3
installation, 10–3
used by DMS, 9–2
usinga remote RIS area, 4–10
using mount point to install
software, 4–2n, 10–2, 11–3n
NFS server
checking status, 13–2
nfsd daemon, 10–3
nfsiod daemon, 10–3
NIS, 6–2, 10–8
NIS utility, 10–8
no build support for DMS client,
10–6
O
operating system
installable by RIS, 2–4
installing on DMS server, 10–7
installing on RIS server, 3–3
tailored for DMS client, 9–5
overhead
disk space, 10–5
P
PAK
required for servers, 10–1
partial build support for DMS
client, 10–6
partitions
on DMS server, 10–2
planning
disk space for DMS, 10–4
planning disk space for RIS, 3–3
portmap daemon, 10–3
problems, 13–1
product
showing list of, 12–13
Product Authorization Key
(See PAK )
product environment, 2–3
deleting products in, 6–12
listing RIS products in, 6–11
multiple in single RIS area, 2–3
RIS products in listing, 6–11
profile set, 7–1
converting CDF to, 7–5
creating, 7–2
creating directories for, 7–2
definition, 7–1
deleting from RIS server, 7–6
populating, 7–2
registering for, 7–3
registering RIS client for, 7–3
protected system files, 9–4
R
registering a client, 6–1
for DMS, 10–8
information required for DMS
client, 10–8, 12–2
informationrequired for RIS clients,
6–1
problems in RIS, 8–3
with naming service, 6–2, 10–8
registration problems
cloned client, 8–4
remote boot
flow, 5–4
Index–6