Digital PDFs

AA-MFO1A-TE

1988

90 pages

Original

3.8MB

view download

OCR Version

3.1MB

view download

Document:	ULTRIX-32 Guide to Diskless Management Services
Order Number:	AA-MFO1A-TE
Revision:	0
Pages:	90
Original Filename:

OCR Text

ULTRIX-32

Guide to Diskless
Management Services

Order No. AA-MFO1A-TE

ULTRIX-32 Operating System, Version 3.0

Digital Equipment Corporation

The information in this document is subject to change without notice and should not be
construed as a commitment by Digital Equipment Corporation.
Digital Equipment Corporation
assumes no responsibility for any errors that may appear in this document.

The software described in this document is furnished under a license and may be used or
copied only in accordance with the terms of such license.

No responsibility is assumed for the use or reliability of software on equipment that is not
supplied by DIGITAL or its affiliated companies.

The following are trademarks of Digital Equipment Corporation:

DEC

Q-bus

VAX

DECnet

VAXstation

DECUS

ULTRIX

VMS

MASSBUS

ULTRIX-11

MicroVAX

ULTRIX-32

PDP

UNIBUS

ULTRIX Worksystem Software
dlila]ital1]

UNIX is a registered trademark of AT&T in the USA and other countries.

IBM is a registered trademark of International Business Machines Corporation.
MICOM is a registered trademark of Micom System, Inc.
This manual was written and produced by the ULTRIX Documentation Group in Nashua, New
Hampshire.

Contents

About This Manual
AUAIEIICE oeiiiiniieiiiee ettt et tieer e ta e er e e as e sansease st esteettasatssensanaseranrannees

vii

OrganizZatiOn .......coveeiiiiiiiiiriireiiie
eer e e eeeeeiiee e e s tettrni s e eentara e e s eetrrana e

vii

Related Documentation .......cocoeveiieiiiiviiieiiieeiriieerieieeeneeerenreetneasssnasereaseessiessnnes

viii

CONVENLIONS tevniiiniiiiiiiiiiiiieiieeeiirerierrte
et eetneerteestersteresnerstessesrsserrnsstsesansesrnssnnnns -

viid

1 Overview
1.1 The Diskless Server’s Environment ..........ccccccooiiiiiiiiiiiiiiiniiiin

1-1

1.2 Diskless Management Services Utility .....ccccccoeviiiiiiiiiiiiiiiiiiiin.

1-2

1.3 Order of OPerations

1-2

.......cccccceeerieiiiiiirieeeereeeiiiiiie
e eeeesiee e erreresseesnees

1.4 Diskless Server Area File Systems

......cccooceoiiiiiiiiiiiiiniieiiiiiereninnneennn.

1.4.1 Directories ......cccevieiiiiiiiiiiiiiiiiiiiiniieeiiii
e
1.4.2 Diskless Server Area from the Client’s View ........c.ccccoonnis

1-5
1-6

1.5 Disk Space Required on the Server ...,

1-8

1.5.1 Disk Space Required for the dlenv File System ...................
1.5.2 Disk Space Required for the dlclient File System ................

1-8
1-9

1.6 Default Configuration Files ........ccccccciiiiiiiiiiiiiiiiiiii 1-10
1.7 Diskless Clients With DisKS

.iivieiiiiiiiiiiii

eeanens

1-10

2 Diskless Management Services Setup Preparation
2.1 Gathering Prerequisite Information

...........occoovevovevooieeeeesooooeoeeoe,

2.2 Setting Up ULTRIX Network Services on the Server

2-1

......o.......

2-1

2.2.1 Installing an ULTRIX Operating System on the Server ......
2.2.2 Setting Up a Local Area Network .......ccccooooeveevieeveevoenvoinn,

2-2

.....ccccocvveevvevvvmeeeeoeneiinnnn,

2-2

............cccoceeooeooiooieoooooooieieeoin,

2-2

2.3.1 Formatting the DiSK .....ccccoooeeeeeoieieeoieeeeeeee oo,
2.3.2 Planning the Disk All0Cation ........oceceeevooeeeeeieeeeeeeeeeeeeee,

2-3

2.3.2.1 Partitioning a Disk with DMS ..oooovieeeeeeeeeeeeeeeeee
2.3.2.2 Manually Partitioning a DisK ...ccoovvvveveeeeeeeeeieeoeeeoi

2-3

2.2.3 Setting Up a Network File System
2.3 Planning the Server Configuration

2.3.3 Planning Diskless Server Area Software Installation ............
2.3.4 Planning the Clients’ Defaults .........cocccoovvvveeiveeeveeeeeeoeeeienn,
2.3.5 Identifying the Distribution Media ......ccccoovevvvvveevereervoenriennnn,

2.3.6 Obtaining the Device Special File Name or Mount Point ...
2.4 Planning Client RegiStrations

2-1

2-3

24
24
24

2-4

..........coeeeeveemoeireeeeieeeeeeee oo,

2-5

2.4.1 Obtaining Information About Each Client .......cocvooovvvovevvinn,
2.4.2 Placing Clients’ Host Names and IP Addresses in
JBECTRNOSES ..ottt
e,
2.4.3 Referring to the DMS Clients’ Defaults Setup Checklist .....

2-5

2.4.4 Filling Out the DMS Client Setup Worksheet .......oocovevvin...

2-6
2-7

2-9

3 Diskless Server Setup
3.1 Partitioning & DISK

...occceeoiiiiiiiiiii

3-1

3.1.1 Partitioning a Disk Using dms ......ccooevvmvveeeeeeeereeoeeoeosee
3.1.2 Partitioning a Disk Manually ........cccoooveeerveeeeeeeeeeeeeoeeo

3-5

3.2 Installing Software Subsets into a Diskless Server Area ................

3-6

3.2.1 Installing ULTRIX-32 Supported Software Subsets .............
3.2.2 Installing Additional Software Products ........ooovvoeoovvommeeoin.,

3-10

3-1

3-7

3.3 Setting Up Clients’ Defaults

......cccocoeviiereiiiiiiiiiiiiiiiiceceieee
e eeeeeevvveeenn

3.3.1 Setting Up a Default Client fstab File

3-12

........ccccccovvvvvivnirnnnnnnn..

3-12

.......cccccccvvvvverviiiiiiiiiiiiiiiiiinnninnnn..

3-13

4.1 Adding a CHent ..ot

4-1

4.2 Booting a ClHent .......cooiiiiiiiiiiiccccee

4-6

4.2.1 Changing a Client’s Boot Server ..........cccccoovocviiiviiiinniiinnninnnnn.

4-6

3.4 Rebuilding Diskless Default Kernels

4 Management and Maintenance

4.3 Modifying a CLENnt

.......coooviiiiiiiiiiiiiiiiiee

et eeseereenaneenen

4.4 Removing a CLent

.......cccccvviiiiiiiiiiiiiiiiiiiiccee

4-7

4-8

4.5 Listing Configurations ..........ccccoooviiiviviiiiieiiieieieeiereeereeeeeeeeeeeseeeseree
e,

4-10

4.6 Reading Mail on a Client

4-11

........coooviiiiiiiiiiiiiiiicccceeee

4.6.1 Reading Mail from a Diskless Client with Multiple
e

4-11

4.6.2 Reading Mail from a Diskless Client with a Single User ....

USEIS woiiiiiiiiiiiiiiiiiieie

4-12

4.7 Customizing a Client’s Setup ......coeeeeiiiiiiiiiiiiiiiieieeeeeeeeeeeeeee
e

4-13

4.7.1 Customizing Kernels

.........ccocooveiiiiiiiiiiiiiiiiiiiieeeee
e

4-13

4.7.1.1 Customizing a Client’s Kernel on the Server Processor

4-13

4.7.1.2 Customizing a Client’s Kernel on the Client Processor

4-16

4.7.2 Sharing a Customized Kernel ........ccccccccvvviiiiiiviiiiiiiiiiieeeeeeeeeen,

4-17

4.7.3 Setting Up Clients’ Remote Home Directories

...........ccou.......

4-18

........ccccoooviiiiiiiiiiiiiiiiiiiinvenennnn.

4-19

4.8 Maintaining the Diskless Environment

4.8.1 Controlling Root File System Growth

.....cccccoooviiiiiiiiiienieinnn,

4-19

.........ccccoovvvrvviiviiiiireeerenn.

4-20

.....ooooviiiiiiiiiiiiiiiiii
e

4-20

4.8.2 Listing Installed Software Subsets

4.8.3 Removing SuUbSets

5 Troubleshooting
5.1 Server Areas to Check for Client Booting Problems

........cccoouur.n....

5-1

5.2 Client Crash Description ........cccccoocoveeiiiiieeeeieeeeeeeeeereeeeeeeeeeeee
e e,

5-2

Figures
1-1:

Diskless Server Area Directory Structure

...........cccccoveveovoiirveeevviinn,

1-6

1-2:

Client Views of the Diskless Server Area .........coccooovveevvveveeeinins

1-7

2-1:

DMS Clients’ Defaults Setup Checklist

......ccccceevvvveeveereeeeieeeeineninn,

2-8

2-2:

DMS Client Setup Worksheet

........cccooooeeeivooeeeeeeeeeieeeeeeeieeeeesieeniin,

2-9

Tables
1-1:

Sequence of Operations Performed on the Server

.....oooovvvoenn..n.

1-3

1-2:

Swubdirectories Installed into the var Area on the Server .............

1-5

1-3:

Approximate Disk Space Required

..........cccccoeoveemvoveeevieeeeieeeiiinenans

1-9

2-1:

Device Special File NAmMeS

......ccoccviviveiiiiiiieeeeeeeeceeeeeeeeeeeeeeiree
e eeis

2-5

2-2:

Processor and Graphics Device Combinations .........ccceeeevvevevvennnnnn.

2-6

About This Manual

This manual describes how to install and maintain your diskless server area
using the diskless management services utility, dms.

Audience
The audience for this manual is anyone installing and maintaining the
diskless server area.

The manual assumes that:

You, or a DIGITAL Field Service representative, have checked the
hardware to ensure that it is working properly.

You have read the Owner’s Manuals supplied with your hardware.

You know the location and function of the controls and indicators on
your hardware.

You understand how to load and unload the installation media and

any disks needed during the installation.
®

You know how to use ULTRIX software.

Organization
Chapter 1

Overview of the Diskless Management Services
Describes the diskless server area and introduces the dms
utility.

Chapter 2

Diskless Management Services Setup Preparation
Describes the knowledge, information, and tasks required
before you set up the diskless server area.

Chapter 3

Diskless Server Setup
Describes how to partition a disk, install software into a
diskless environment, and set up a default configuration for
that server’s clients.

Chapter 4

Management and Maintenance
Describes how to add, modify, and delete diskless clients,
and how to customize clients’ setups.

diskless clients.

Tells how to manage

Chapter 5

Troubleshooting
Describes how to perform troubleshooting operations in the
diskless server area.

Related Documentation
The following suggests the order in which you should read the
related
documentation:
1.

Hardware documentation
You should have on hand the hardware documentation associate
d with

your processor,

particularly the

Owner’s

Manual.

These

manuals

show you how to set up the processor and its additional devices.
These manuals also supply valuable troubleshooting guidelines.

Release Notes
Before beginning the installation, you should read the current
version
of the Release Notes.

System and network management guides
Read the appropriate system and network management guides
to help

you prepare to

install the diskless

server area.

Conventions
The following conventions are used in this manual:

special

In text, each mention of a specific command, option,

partition, pathname, directory, or file is presented in this
type.
command(x)

In text, cross-references to the programmer’s manuals

include the section number in the manual where the

command is documented.

command in the

For example, see the cat(1)

ULTRIX Reference Pages.

example

In examples, computer output text is printed in this
type.

example

In examples, user input is printed in this bold type.

This is the default superuser prompt.

>>>

This is the console subsystem prompt.

In examples, a vertical ellipsis indicates that not all of the

lines of the example are shown.

<KEYNAME
> In examples, a word or abbreviation in angle brackets
indicates that you must press the named key on the

terminal keyboard.
Mbyte

Throughout the text, the abbreviation Mbyte is used for
megabyte.

One megabyte equals

1,048,576 bytes.

Overview 1

A server processor provides diskless management services to client
processors from a diskless server area.

The diskless server area contains
software that is available to registered client processors that are licensed to
access that software.

Each client registered for a diskless server area is booted from the server
and uses the software in the diskless server area as if that software were
located on the client’s processor.
The diskless client has no system
management responsibilities because the software remains located on the
server, and system management operations are all performed on the server.

This chapter presents an overview of the diskless management services and
introduces the diskless management services utility, dms, for setting up and
managing the diskless server area.

1.1

The Diskiess Server’s Environment

The environment for a diskless server area consists of the following
components:

A server

The server can be any DIGITAL supported processor except the
MicroVAX 2000 and the VAXstation 2000, which are not supported
servers.
The software subset containing support for the maintenance
operations protocol, MOP, must be installed in order for your system
See the ULTRIX-32 Advanced Installation

to be used as a server.

Guide for software subset descriptions and dependencies.
°

A distribution device on the server

The distribution device could be a tape drive, an RA60 disk drive, a

TK50 tape cartridge drive, or a TK70 tape cartridge drive.
You use
the distribution device to transfer the software subsets for a specific
product to the server’s disk, where registered clients can access the
software.
e

The Ethernet

You must set up the server and all client processors as hosts on the
Ethernet. Clients use the Ethernet to access the diskless server area.

Clients

Each diskless client must have at least 6 Mbytes of memory.
Diskless clients are members of the MicroVAX and VAXstation
series of processors.

The supported processors in these series are:
MicroVAX 1I

MicroVAX 2000

MicroVAX 3300
MicroVAX 3400
MicroVAX 3500

MicroVAX 3600
VAXstation II
VAXstation II/GPX
VAXstation 2000

VAXstation 3100
VAXstation 3200

VAXstation 3500

1.2

Diskless Management Services Utility

The tool to set up the diskless server area and to register diskless clients
is the Diskless Management Services utility, dms. You also use the dms

utility to manage your client processors.

See dms(8) in the
Reference Pages for a summary of the dms functionality.

ULTRIX

The dms utility supports default configurations for graphics devices and

Ethernet hardware. Support for other devices requires customization.

Chapter 3 and Chapter 4 include descriptions of procedures performed
Chapter 4 also contains descriptions of customizing a client’s

using dms.
setup.

1.3

‘

Order of Operations

The system manager on the server processor performs a series of
procedures to configure the server for diskless management services.
The
procedures to set up a diskless server area follow, listed in the order in
which they are performed:

Allocate disk partitions and create the file systems required for
diskless management services

Install software

Optionally, set up a default configuration to assign to each client

registered for the diskless server area
o

Boot clients from the server

Table 1-1 lists each operation required to set up a diskless server area in
sequence and the name of the applicable dms utility option and manual

method for each.

It also lists the section of this guide that describes each

procedure.

Table

1-1: Sequence of Operations Performed on the Server

Operation

DMS

Manual

Menu Option

Method

Partition disk & create

Configure Server

chpt & newfs

file systems

Set up Disk Partitions

commands

Section 3.1.1

Section 3.1.2

Install ULTRIX-32

Configure Server/Install Software

N/A

supported software

into an Environment

Section 3.2.1
Install additional

Configure Server/Install Software

software, for example,

into an Environment

the ULTRIX Worksystem

Section 3.2.2

N/A

Software Server Kit
Set up default client

Configure Server/Set up Clients’

configuration

Defaults

N/A

Section 3.3
Register Clients

Add Client Processor

N/A

Section 4.1
Boot clients

N/A

boot commands
Section 4.2

1.4

Diskless Server Area

File Systems

File systems and administrative files for diskless clients are located on the
server.
Each diskless server area contains two types of file systems:
o

One or more dlenv file systems that contain the diskless environment.
The components of a diskless environment are one or more common
root directories, a portion of which is copied to each diskless client’s
area in the second type of file system, the diclient file system.
The
dlenv file system also holds a shared software area within each
common root area that contains the usr area, where read-only data

files and executable files are located.
When the client is booted from
the server, this shared usr area is automatically mounted by each
client registered to access that common root directory.

One or more diclient file systems, each of which contains machinespecific areas where a copy of each registered diskless client’s portion
of the common root directory, and, in some cases, the client’s swap

file are located.
Throughout this guide, the diskless server area file systems are designated
dienv?
and diclient?.
The common root directories are designated
root?.vax.
The question mark (?) represents the number assigned to the
specific file system or common root directory when it is installed.
The
portion of the common root directory that is copied to each registered
client is designated Cliname.root.

A server processor may have several diskless server areas. Each common
root?.vax directory of each dlenv file system may contain a different set of

software products to provide a distinct software environment for a group of
licensed diskless clients to share.
The files in the usr area of a particular
root?.vax directory are shared by all the clients registered for that
environment.

Creating separate file systems for each dlenv?
and diclient?
component in
your diskless server areas provides security by giving the server control
over the degree of access to each diskless environment.
This limits each
registered client’s access to its own Cliname.root directory and to the
shared usr area of its root?.vax directory, which is designated read only.

The components of each diskless server area may be on separate partitions
of one disk or distributed on separate partitions of multiple disks.
For
example, a dlenv file system may be on a separate partition of one disk,

and a diclient file system on a separate partition of a second disk.

1.4.1

Directories

When you use the basic installation procedure to install an ULTRIX
operating system on the server, or perform an advanced installation and

choose the default file system allocation, the installation software creates
the /usr/var directory.

If you perform an advanced installation and do not

choose the default file system allocation, you can allocate the var area as a

separate file system.
You can install a diskless server area whether the var area is a directory

under /usr or a separate file system.

Throughout this guide, /var is

assumed to be a separate file system.

After the software subset containing the maintenance operations protocol,
MOP, has been installed, and you have created a dlenv file system and a
diclient file system, several subdirectories exist in the var area that make
up the diskless server area directory structure.

These subdirectories are

shown in Table 1-2.

Table

1-2: Subdirectories Installed

Subdirectory

into the var Area

on the Server

Contents

/var/diskless/dms

client default parameter files

/var/diskless/defs

client system and configuration files

/var/diskless/clients

MOP registration packets (network
downline load files)

/var/diskless/bin

dms executable files

/var/diskless/diclient0

individual client root directories and
swap files, for example, ClientA.root,

ClientA.swap, ClientB.root, and
ClientB.swap.
/var/diskless/dlenv0

common root areas, like root0.vax and
root1.vax that contain shared usr areas

that are mounted by each client and

root directories propagated to clients.

Figure 1-1 illustrates the diskless server area setup.

In this figure, solid

boxes represent file systems, ellipses represent directories, and dashed
boxes represent files.

/var/diskless

dlelientQ-N

dlenv0-N

root0.vax
-

Figure

1-1: Diskless Server Area

Directory Structure

1.4.2

Diskless Server Area from the Client’'s View

Only the diskless server has access to the entire /var/diskiess directory
structure.
The diskless client has access only to the shared usr area that
exists in the root?.vax for which it is registered in the dlenv?

file system
file

and to its own Cliname.root directory and swap file in the diclient?

system.
Figure 1-2 shows each client’s view of the diskless server area
and of its own root and usr area.

Diskless Server

/var/diskless

F—-—m - '1/

]

iClientA.swap

diclient0

dienv(

]

b---mmmm r

root0.vax

1ClientB.swap

[

ClientB.root

i
Diskless

Client
.

View

)

Diskless |
Client B

View

shared usr

root

’d

Vs
/

/
/

usr

r—m"====

swap

usr

F-m

- e|

swap

:
J

Figure

1-2: Client Views of the

Diskless Server Area

The dashed lines indicate those areas that each client mounts when it is
booted from the server. The two areas are the root?.vax directory in the

The solid lines around each client processor’s view box indicate that from a

client’s view both root and usr seem to be located on the local machine.
Users on the client processor access the software on the server just as
they would if the software were actually located on the local processor.

1.5

Disk Space

Required on the Server

Disk space is required on the server for each diskless server area file
You can automate disk partitioning by using the dms utility to

system.

partition a disk that will be dedicated to a diskless server area.

Do not under estimate the disk space you need.
If you under estimate the
disk space required for the file systems, you must repartition your disk to
provide the necessary space.
Repartitioning a disk is a complex procedure

and it overwrites existing software.

1.5.1

Disk Space

Required for the dlenv File System

The recommended size range of the dlenv file system of each diskless

environment is 35 to 100 Mbytes. Each common root?.vax area contains at

least the ULTRIX-32 mandatory software subsets, plus whatever other
supported subsets and additional software products are desired for clients
who are registered to access that area.

The table that follows shows the approximate sizes of the software subsets
for some ULTRIX products that you might want to install in one or more
root?.vax areas.

Table

1-3: Approximate Disk Space Required
Approximate

Software Subsets

Size in Mbytes

ULTRIX mandatory

All ULTRIX supported

All ULTRIX Worksystem

All ULTRIX unsupported

100

In addition, be sure to allow space for any other software products you
plan to install.
Most users load all of the ULTRIX-32 supported software subsets, plus

the ULTRIX Worksystem Software subsets.

Those two products require

about 60 Mbytes of disk space.
Throughout this guide, space recommendations are based on a diskless
server area with one dienv file system with one root?.vax directory
containing all the ULTRIX-32 supported software subsets and all the
ULTRIX Worksystem Software subsets.

1.5.2

Disk Space Required for the diclient File System

You must allow disk space on the server for each client’s Cliname.root

directory and, in some cases, swap file in the diclient file system.
Consider these factors when you plan the space requirements of your
diskless clients:
o

The clients’ volatile files, like those in the tmp directory, and volatile
directories like var/spool and var/adm/crash are located in dlclient

Customized clients require more space than clients linked to a default

kernel
o

Clients that add files to their Cliname.root areas use space

The recommended size for each client’s root directory is 10 Mbytes. Add
an amount equal to the client’s memory size if the client will do a full

crash dump over the network to the server.
The swap file should be 20 Mbytes or two times the client’s memory size,
whichever is greater.

You can estimate the space that different clients in a group require and
spread that amount of space over the whole group when determining your
diclient?
disk space requirements.
For example, you might allocate 5
Mbytes for each client’s root file system and 12 Mbytes for each client’s
swap file. Those allocations would require 85 Mbytes in the dlclient file

system to support five diskless clients.

1.6

Default Configuration Files

The diskless software includes several default configuration files for building
clients’ kernels. When a client is registered, the correct kernel is assigned
to it according to the client’s processor and graphics device types.
You can create customized configuration files for clients, build kernels, and
provide a copy of the customized kernel to the client.
See the Guide to

System Configuration File Maintenance for information about configuration
files and Section 4.7.1 for information about customized kernels.

1.7

Diskless Clients with Disks

A client processor with a disk can act as a diskless client.
For example,
clients may locate swap files and data files on their local disks.
Such a
client requires a kernel built from a configuration file that is customized

with the appropriate entries to access its local disk.

See the Guide to System Configuration File Maintenance for information
about editing configuration files.
Refer to Section 4.7 for an example of

customizing a kernel.

Diskless Management Services Setup Preparation 2

This chapter describes how to prepare to set up your diskless server area.
The chapter describes how to:

Gather prerequisite information

Set up ULTRIX network services on the server

Plan the server configuration

Plan client registrations.

2.1

Gathering Prerequisite Information

As the system manager at the server, you should:
®

Know your superuser password. The setup procedure requires you to
type this password.

2.2

Make sure that your clients are licensed for all the software that
they access in the diskless server area.

Setting Up ULTRIX Network Services on the Server

Perform the following tasks before you start the dms setup preparation:

Install an ULTRIX operating system on the server

Set up a local area network

Set up a network file system

2.2.1

Installing an ULTRIX Operating System on the Server

The Basic Installation Guide for your processor explains how to install an
ULTRIX operating system. The ULTRIX-32 Advanced Installation Guide

tells you how to perform an advanced installation.
that lists supported software subset sizes.

It also provides a table

The subset containing the maintenance operations protocol, MOP, must be
mstalled if your system is to be a server.

To load the subset containing MOP, either perform an advanced installation
or use the setld command after the basic installation is complete.
For

example:
#

setld

-a

/dev/rmtOh

ULTMOPO30

For more information, refer to setld(8)

2.2.2

Setting Up a

Local Area

in the

ULTRIX Reference Pages.

Network

You must connect the dms server and all of your client processors to the
Ethernet. See the Guide to Networking for instructions on how to set up a
local area network (LAN).

If you run the network data base Yellow Pages (YP) service on the server,
the dms utility sets up each diskless client to run YP. See the Guide to
the Yellow Pages Service for information about YP.
Do not run the ypsetup utility on diskless client processors.
If your diskless server is also any type of Berkeley Internet Name Domain
(BIND) server, the dms utility sets up each diskless client to run BIND
using the diskless server as the client’s BIND server also. See the Guide

to the BIND Service for information about BIND.

Do not run the bindsetup utility on diskless client processors.

If you are running both the YP and the BIND services on the diskless
server, the diskless client’s /etc/svcorder file contains yp, bind, and local, in
that order, by default.

2.2.3

Setting Up a

Network File System

The network file system (NFS) must be set up before you install a
diskless server area.
See the Guide to the Network File System for
mstructions on how to set up NFS.

Do not run the nfssetup utility on diskless client processors.
utility sets up diskless clients for NFS.

2.3

The dms

Planning the Server Configuration

Perform the following tasks to prepare to configure a diskless server:
o

Make sure your disk is already formatted if you plan to use dms to
allocate disk partitions

Plan the disk allocation

Plan your diskless server area software installation

Plan the clients’ defaults

Identify the distribution media

Obtain the full pathname of the device special file name or mount

Refer to the DMS

point for the distribution media
Clients’ Defaults Setup Checklist, located at the

end of this chapter

2.3.1

Formatting the

Disk

If you plan to use the dms utility to allocate disk partitions, your disk
must be formatted.
DIGITAL formats disk packs for most processors
before they are shipped.

See your Owner’s Manual for information about

your disk.

2.3.2

Planning the

Disk Allocation

You can install both the shared and client-specific portions of each diskless
server area on one disk. Or, you can spread a diskless server area over
multiple disks. For example, one disk can contain the dlenv file system.
Another disk can contain the diclient file system.

Spreading diskless server areas over multiple disks may improve system
performance because client access is not concentrated on one disk.

2.3.2.1
Partitioning a Disk with DMS - You can use the dms utility to
partition your disk and set up the file systems necessary for a diskless
server area.
The utility sets up dlenv and diclient file systems in
consecutive order, starting with dlenv0 and diclient0.

These file systems
must be in place before you can install software subsets into a diskless
server area using dms.

If the disk is already in use, remember to back up any data you want to
restore before you partition the disk using dms because the whole disk will
be overwritten.
A description of partitioning disks with dms is included in Chapter 3.
2.3.2.2
Manually Partitioning a Disk - You can use the chpt utility to
find available disk space and to rearrange partitions on a disk you are
using for both the diskless server area and other processing.
See the

Guide to System Disk Maintenance for information about estimating size

and changing disk partitions.
You can create the /var/diskless/dlenv?
systems using newfs.

and /var/diskless/diclient?

The question mark (?)

file

represents the number you

assign to each file system for each diskless server area. See the Guide to
e DY

TTM °*

h W

A description of partitioning disks manually is included in Chapter 3.

2.3.3

Planning Diskless Server Area Software

Installation

When you install software into a diskless server area, you install software
products in the dlenv file system and select kernels to be built.

Software

is installed into one or more common root?.vax areas.
It is recommended that you install all the software you want in each
diskless environment at one session.

Start with your ULTRIX-32

supported software subsets, then install any additional software products
that clients will share.

This avoids having to update clients registered for

that diskless environment.

See the ULTRIX-32 Advanced Installation Guide for a description of
ULTRIX-32 software subsets and their sizes.
In additon, see the
documentation provided with your other software products to decide which
subsets to install.
If all the software you want will not fit into the dlenv
file system, consider mounting another disk.

Make sure that you allow enough space for all the software you plan to
install in all the common root?.vax areas when you allocate disk space for

the dlenv file system.

2.3.4

Planning the Clients’ Defauits

Plan the default setup for the diskless clients that will use this server.
Refer to the DMS Clients’ Defaults Setup Checklist at the end of this
chapter for a list of the defaults you can specify.

2.3.5

Identifying the

Distribution Media

See the bill of materials for the distribution media types and associated

labels for your products.

2.3.6

Obtaining the

Device Special File

Name or Mount Point

Obtain the full path for the device special file name or mount point
associated with your software distribution media.
The device special file
name points to the device on which you mount the media containing the
software subsets. = The mount point is the file system on which you
mount the software when the distribution media is an RA60 disk.

Table 2-1 lists possible distribution media and, where applicable, the device
special file name for each. The first column lists the distribution media
type, the second column lists the full pathname for the device special file
or mount point, and the last column contains the DIGITAL name for the
P LY SLL

The question mark (?)

in the device special file name represents the unit

number of the distribution device. For example, if the distribution device is
a TU81 unit 0, then the device special file name is dev/rmtOh.

Table 2-1: Device Special File
Media Type
RA60 disk

Names

Device Special File Name

DIGITAL Name

Full pathname of mount

RA60

point
TK50 tape cartridge

/devirmt?h

TK50,

9-track magnetic

/devirmt?h

TS05, TUSO

tape

TK70

TU45, TE16

TU77
/devirmt?|

TUS81.

TUS1E

TU78, TU79

2.4

Planning Client Registrations

Perform the following tasks to prepare to register diskless clients:
°

Obtain information about each client.

Place each client’s host name and IP address in /etc/hosts

Fill out the DMS Client Setup Worksheet, located at the end of this

chapter

2.4.1

Obtaining Information About Each Client

You need the following information about each processor you plan to
register as a client:
o

Host name, which can contain up to 32 characters.

Superuser password.

Processor and graphics device type.

The possible processors and graphics device combinations are listed in
Table 2-2.

Table 2-2: Processor and Graphics Device Combinations

Processor

Possible Graphics Device

VAXstation II

monochrome

VAXstation 1I/GPX

color

VAXstation II/GPX
( multi-station)

color

VAXstation 2000

monochrome

VAXstation 2000

color

VAXstation 3000 series

monochrome

VAXstation 3000 series

color

VAXstation 60

color

MicroVAX 11

no graphics

MicroVAX 2000

no graphics

MicroVAX 3000 series

no graphics

Hardware Ethernet address

See the Guide to Ethernet Communications Servers for
information about hardware Ethernet addresses.

2.4.2

Placing Clients’ Host Names and IP Addresses in /etc/hosts

You automatically place each client processor’s host name and Internet
address in the /etc/hosts file when you initially set up your
LAN using the netsetup utility. The netsetup utility is described in the

Protocol (IP)

Guide to Networking.

You can also place the host name and IP address in the /etc/hosts file by
using a text editor, such as vi. The host name and IP address for each

client processor must be unique.

Note

If the host system is being served by the Yellow Pages (YP)
service, see the Guide to the Yellow Pages Service for
information about modifying and propagating a host file.

If the host system is a Berkeley Internet Name Domain (BIND)
server, see the Guide to the BIND Service for information about

modifying and propagating a host file.

2.4.3

Referring to the

DMS Clients’ Defaults Setup Checklist

The DMS Clients’ Defaults Setup Checklist is a checklist of the
information you need to set up diskless clients’ defaults on the server.
Refer to this worksheet when you choose the option, Set up Clients’
Defaults, from the dms utility Configure Server Menu, which is described

in Chapter 3.

The defaults you set up are used as default choices when

you add a diskless client using dms.

DMS Clients’ Defaults Setup Checklist
This information is used as default choices when registering diskless
clients.

You will be asked to choose the following during the

client registration procedure:

Common root directory to be copied for clients
File system to contain clients’ root directories

Swap file location (on clients’ disks or on the server)
File system to contain clients’ swap files and swap file size in 1/2Mbyte increments

Full, partial, or no memory dump across the network for clients
For a partial dump, Mbytes to dump in 1/2-Mbyte increments
Default client processor type

Whether default is to link clients to a default kernel, or to copy the
kernel

Figure 2-1: DMS Clients’ Defaults Setup Checklist

2.4.4

Filling Out the

DMS Client Setup Worksheet

Use the DMS Client Setup Worksheet to record the information you need
to set up a client processor using the dms utility option, Add Client

Processor, which is described in Chapter 4. Fill out a worksheet for each
diskless client processor you plan to add.

DMS Client Setup Worksheet
If you used the dms utility Configure Server Menu option, Setup
|
Clients’ Defaults, you can use some or all of the default values when you
register diskless clients.

1. Enter the client’s host name as it appears in the
/etc/hosts file:
2. Enter the client’s hardware Ethernet address:

3. Other information you need about each client:
o

Common root directory to be copied

File system to contain client’s root directory

Root password

Swap file location {(on server or local)

Swap file directory name, if located on the server

Swap file size, if swap file is located on the server

Full, partial, or no memory dump across network for client

Processor type

Link to a default kernel, or get a copy of the default kernel

Figure 2-2: DMS Client Setup Worksheet

Diskless Server Setup 3

This chapter describes how to use the dms Configure Server Menu options
to configure a diskless server.

The instructions tell you how to perform

the following tasks:
e

Partition a disk

Install software into a diskless server area

Set up clients’ defaults

Rebuild diskless default kernels

3.1

Partitioning a

Disk

You can use the dms utility to partition your disk for a diskless server
area.

The utility creates the file system, dlenv?, for the diskless clients’

root?.vax and sharable usr area, and the file system, diclient?, for each
diskless client’s root and swap areas. The question mark (?)

represents the

number corresponding to the file systems for each diskless server area.
You can also allocate disk space and create the file systems necessary for

a diskless server area manually, using the chpt and newfs commands.
This section includes instructions for each method of allocating disk space
and creating the necessary file systems.

3.1.1

Partitioning a

Disk Using dms

This section describes how to use the dms utility Configure Server Menu
option, Set up Disk Partitions, to partition your disk and set up the file
systems necessary for a diskless server area.

data on your disk before using dms.
the disk.

Be sure to back up any

The program overwrites all data on

Your disk must be formatted before you partition the disk.
DIGITAL
formats disk packs for most processors before they are shipped.
See your

Owner’s Manual for information about your disk.

In the sample session that follows, a new, formatted disk is used.
1.

manager

password:

Enter your root password, which does not appear on the screen.

Type the following at the system prompt:
#

/etc/dms

A message appears reminding you that all users who are going to
access the diskless server area must be licensed to use that software.
It then asks you to type your superuser password:
Licensing

Message

continue

please

enter

the

superuser

password:

If you type an invalid superuser password, the dms utility returns
If you type a valid superuser password,

you to the system prompt.

a message appears that explains what documentation you should read.

A diskless management services menu appears.
Server Menu by typing c:
DISKLESS

MANAGEMENT

Configure
Add

SERVICES

Server

Client

(DMS)

Processor

¢C

Remove

Client

Processor

Client

Parameters

List

Enter

UTILITY

Modify

Configurations

Exit
your

choice:

Invoke the Configure

A menu like this appears:
Set

Install
Set

Rebuild
Enter

your

Disk

Partitions

Software
Clients’”

into

=>
an

Environment

Defaults

Kernels

choice:

Enter d to invoke the disk partitioning utility.

A message appears saying that the utility will partition a disk and
create the file systems necessarv for a diskless environment
The

A prompt asks if you want to continue.

Enter y to continue, and

the prompt for the device special file name appears.
Enter the device special file name.
Enter
the

the

device

desired

special

disk,

for

file

For example:

name

example

the

wc+

/dev/rra2c:

partition

/dev/rra3c

A message like this appears:
Press

RETURN

when

/dev/rra3c

ready.

Confirm that the device is ready, then press the RETURN key.
A display appears, ending with a message and prompt like the
following:
Please
1)

select

one

dlenv

and

diclient

Both
on

this

Only

dlenv

Only

dlclient

your

following
areas

uses

are

for

this

disk:

reside

disk.

Enter

the

area

reside

area

reside

this
on

disk.

this

disk.

selection:

Enter the number corresponding to your selection.

In this example,

the system manager chooses to have both areas on this disk:
Enter

your

selection:

A message appears saying that each client requires a swap file and a
root area.

The message also says that distributing swap files and

root areas over multiple disks increases performance and may allow
more space for additional diskless clients.
10.

The next message says that each diskless client is allocated a swap
file. The message is followed by a prompt for you to type the swap
file size.

Enter the swap file size you want.

The recommended swap file size

is 20 Mbytes or two times the client’s memory size, whichever is
greater.
11.

A message appears saying that a root directory is propagated to each
diskless client. The recommended root size is 10 Mbytes.

The

message is followed by a prompt for you to type the propagated root
area size.

Enter the root area size.
12.

A message appears saying how much space is available on the disk
you selected. This message is followed by a message giving the
I
I

. S

R
I

LY
o

T
T

usr portion of the dlenv file system.

A prompt asks you to type the

sharable usr area size.

Enter the size of the shared usr area, which must be large enough to
include all of the root?.vax directories you plan to install. For

example:
Enter

the

sharable

usr

area

size

The dms utility creates the dlenv?
files are checked.
13.

Mbytes:

file system. Messages appear as

A prompt asks you to type the number of clients you want to
support on this disk.
A message gives the range available.
Enter the maximum number of diskless clients you plan to serve. If
you choose too small a number, you may not be able to add all the
diskless clients you want.

14.

A message appears saying how many clients will be supported.
The dms utility creates the diclient?
as files are checked.

15.

Messages appear

When partitioning is complete, a display similar to this appears:
This

your

new

disk

configuration:

Partition

contains

the

dienv

Partition

contains

the

diclient

Partition

contains

the

available

Disk

16.

file system.

than

Mbytes

partitioning

area.
area.

space,

remain.

completed.

If you chose to have only a part of the diskless environment, for
file system, on the first disk you
partitioned with dms, run the program again and designate another
example, only the dlenv?

disk to partition. Choose the next area you want when the prompt

appears requiring you to select the area to reside on the current disk.

You can use this procedure to partition as many disks and create as many
dlenv and diclient file systems as you need.
Then you can install the
software subsets your diskless clients will use in the diskless server area.

3.1.2

Partitioning a Disk Manually

This section includes instructions for allocating disk space and creating the
necessary file systems for a diskless server area manually.
Partition your disk and create the file systems for diskless management
services manually only if you cannot dedicate a disk to the diskless area.

If you must partition your disk manually, be sure to read the Guide to
System Disk Maintenance and refer to the chpt(8,) newfs(8,) fsck(8, and
mount(8) commands in the ULTRIX Reference Pages before you begin.

Follow this procedure to set up a diskless server area manually:
1.

Decide how much space you need for the file systems.
Allow
adequate space for the dlenv?
file system, depending on the number
of root?.vax areas you plan to have and on the software products
each root?.vax area will contain.
Allow adequate space in the

Use the df command to list the current mounted file systems and to
see the amount of free space available on each file system.
For

diclient?

file system for each client you plan to register.

example:
%

The command produces a display similar to this:
total

kbytes

node

kbytes

used

free

used

/dev/ra2a

7415

5711

963

86%

/dev/ra2h

194550

89368

85727

51%

/usr

/dev/ra2g

38175

11852

22506

34%

/usr/users

percent
Mounted

Become the superuser and use the chpt command with the -q option
to see the current size of disk partitions.
For example:
#

chpt

-q

/dev/rra2c

The display depends on the type of disk, but it is similar to this:
/dev/rra2c
partition

table:
top

size

15883

15884

0
0

891071

891072

T O

bottom

partition

128255

128256

577151

448896

577152

891071

313920

OO0
LMY OO0

Current

Filesystem

If there are partitions free which meet your size requirements, go to

step 7.

Unmount all file sytems on the disk you are going to partition.
For safety, back up the file systems on the disk before continuing.

Use chpt to partition the disk, following the procedure described in
the Guide to System Disk Maintenance.

Be sure to allow enough

space for the areas that must be restored, if any. Make sure the
partitions you are going to use do not overlap.

Use the newfs command to create the file systems. You must run
newfs on any partition that has been changed in size or offset.
Use the fsck command to check the newly created file systems.

Refer to the Guide to System Crash Recovery for information about
the fsck command.
Edit your /etc/fstab file to mount the new file systems on their
specified mount points. The fstab entries are similar to the following:
/dev/ra3d:/var/disklessdlenvO:rw:1:4:ufs::

/dev/ra3g:/var/disklessdlclientO:rw:1:5:ufs::

If you relocated or repartitioned any file systems, update those
entries in fstab to specify the new locations.
10.

Create the directories that will be used as mount points for the new
diskless file systems.

11.
12.

For example:

mkdir

/var/diskless/dienv0

mkdir

/var/diskless/dlclientO

Make sure all your file systems are mounted.
Edit the /etc/exports file to include the exported diskless file systems.
The entries are similar to these:
/var/diskless/dlenv0

nobody

/var/diskless/dlclient0

-n

-0

-r=0

nobody

-n

-r=0

Specifying nobody means that no one can mount the exported
diskless file systems manually.

The -n option prevents a client from

accessing the next higher level in the directory structure, relative to
its root directory.
The -0 option makes the file systems read only,

and -r=0 maps the client’s root access to the server’s root user

identification.

3.2

Installing Software Subsets into a
Area

Diskless Server

After you complete the disk partitioning procedure and create the dlskless
PR

4.4 [P I

Y ID N
Y. 1

-y

software into the dlenv file system and build the kernels necessary for
clients who will be registered to access this diskless server area.

Install all

the software you plan to use in this diskless server area before you begin
registering clients.
Each time you install the ULTRIX-32 mandatory software subsets, a new
common root?.vax area is created.

Perform the installation procedures

described in the next two sections to set up root?.vax areas with different
products. Then, licensed clients may access those areas suited to their
needs.
You can install the ULTRIX Worksystem Software Server Kit, ULTRIX

unsupported software subsets, and DIGITAL layered products that are
compatible with the ULTRIX-32 V3.0 setld utility into the diskless server
area.

These additional software products can only be installed to existing

root?.vax areas.

See the documentation provided with your additional

software products.
Note

Use only the ULTRIX Worksystem Software Server Kit to install
ULTRIX Worksystem Software into a diskless server area.

server with either ULTRIX-32 Version 2.2 or ULTRIX
Worksystem Software Version 1.1 software cannot serve clients
with ULTRIX-32 Version 3.0 or ULTRIX Worksystem Software

Version 2.0 software.

3.2.1

Installing ULTRIX-32 Supported Software Subsets

In the sample session that follows, the system manager installs all the

ULTRIX-32 supported software subsets into one common root?.vax area,
/var/diskless/dlenv0/root0.vax, of a diskless server area.

You would perform

this procedure again to set up multiple common root?.vax areas that
contain different software subsets.

The second set of ULTRIX-32

supported software subsets would be installed in
/var/diskless/dlenvO/root1.vax.
1.

Invoke dms and select the Configure Server Menu option from the

DMS menu.
2.

When the Configure Server Menu appears, type i to select the Install

Software into an Environment option.
3.

A prompt asks if you are installing ULTRIX-32 supported software.

In the following example, the system manager is installing the
ULTRIX-32 supported software:
Are

you

installing

ULTRIX-32

supported

software?

(y/n)

[n]:

A message appears saying that you have chosen to install a new
diskless environment.
If there is more than one dlenv?
file system available, a menu
appears listing the possible file systems.
For example:
These

are

the

possible

file

/var/diskless/dlenv0

/var/diskless/dlenvl

Enter

your

choice

[]:

systems

contain

the

environment:

A message like the following appears automatically if there is only
one file system available, or after you enter the number corresponding
to your choice of file system if there is more than one available:
The

environment

/var/diskless/dlenv0/root0.vax.

A prompt asks for the full pathname of the device special file name
or mount point for the distribution media.

Enter the device special file name or mount point of your distribution
media.
In the following example, the system manager plans to mount the 9track magnetic tape labeled ULTRIX- 32 V3 0 SUPPORTED MT9 on
a TU81 tape drive, unit O:
Enter

the

full

device

mount

path

associated

point

[no

with

default]:

the

software

distribution

kit

dev/rmtOh

A message tells you to press the RETURN key after you mount the
software distribution media.
Make sure the device is on-line and
ready.
After you press the RETURN key, another message appears to make
sure that you have loaded the media.
The message asks you to type
y when you are ready:
Press

RETURN

software

after

you

distribution

software

Please

make

sure

Ready

(y/n)?

mount

subsets
your

the

media

the

device.

the

var

installation

directory.
tape

mounted

and

on-!ine

A message appears listing the software subsets that are mandatory
and will be installed automatically, followed by a list of optional
software subsets for the product you are installing.

Select the optional software subsets that you want from the list.
you want all of the optional software subsets, enter the number

corresponding to the selection, All of the Above.

A message appears listing the subsets that you have chosen to install
and asking you to confirm your choice.
If the software subsets listed are the ones that you want, type y. If
you type n, the list of optional software subsets is displayed again,

and you can select the subsets that you want.
Messages appear as each software subset that you selected is
installed and verified. This may take an hour if you select all of the
software subsets.
9.

When the subset installation is complete, a message appears asking
you to select the kernels you want to build as default kernels for the

different types of client processors supported.
If you have clients whose kernels were built using ULTRIX
Worksystem Software Version 1.1 software, do not build kernels for
them during this part of the installation.

Install the ULTRIX

Worksystem Software Server Kit as additional software, and build
kernels for those clients during that installation procedure.

Answer y or n to build kernels corresponding to the types of client
processors you plan to register. For example:
Which

kernels

SETEVAX

applies
MicroVAX

Build

SETEVAX

you
to

want

the

build?

following

2000

kernel?

processor

types:

non-graphics
(y/n)

[n]:

A message appears saying that kernel building is occurring and that
it may take several hours.

Messages appear as the kernels are built.
Note

The ULTRIX File System (UFS) is not needed for diskless
workstations. Ignore the message warning that UFS is not
configured.
10.
*

As each kernel is configured, a message similar to this appears:
*

The

new

configured

kerne!l

/var/diskless/dlenv0/root0.vax/sys/SETEVAX.dlconf/vmunix

Each kernel you build can be either linked or copied to applicable
processors which you register as diskless clients.

3.2.2

Installing Additional Software

Products

You can install the ULTRIX Worksystem Software Server Kit, ULTRIX
unsupported software subsets, and DIGITAL layered products that are
compatible with the ULTRIX-32 V3.0 setld utility into the diskless server
area.

Note

Use only the ULTRIX Worksystem Software Server Kit to install
ULTRIX Worksystem Software into a diskless server area.
A
server with either ULTRIX-32 Version 2.2 or ULTRIX
Worksystem Software Version 1.1 software cannot serve clients
with ULTRIX-32 Version 3.0 or ULTRIX Worksystem Software
Version 2.0 software.

To install additional software products, invoke the dms utility again and
select the Configure Server Menu option, Install Software into a Diskless
Environment. For example, you might install a different set of optional
software subsets to /var/diskless/dlenv0/root0.vax.

Make sure no diskless clients which mount the usr area of this common
root?.vax area are running when you install an additional software product,

or their usr area may change.

In the sample session that follows, the system manager installs ULTRIX
Worksystem Software into /var/diskless/dlenvO/root0.vax.
1.

When the prompt asking if you are installing ULTRIX-32 supported
software appears, type n.

A message like this appears:
You

have

chosen

existing

install

software

into

environment.

If there is more than one installed root?.vax directory in the diskless
server area, choose the appropriate directory from the menu that lists
existing root?.vax directories.
For example:
These
1.
2.

Enter

diskless

are

the

possible

installation

directories:

/var/diskless/dlenv0/root0.vax
/var/diskless/dlenv0/rootl.vax

your

choice

[

A prompt asks for the full pathname of the device special file name
or mount point for the distribution media.

Enter the device special file name or mount point of your distribution
maedia

If your distribution media is tape, a message appears asking you to
confirm that the tape is mounted and on line.

If your distribution media is tape, confirm that the tape is mounted
and on line, then type y.
A message appears listing the software subsets that are mandatory
and will be installed automatically, followed by a list of optional

software subsets for the product you are installing.
Select the optional software subsets that you want from the list.

you want all of the optional software subsets, enter the number

corresponding to the selection, All of the Above.
A message appears listing the subsets you have chosen to install and

asking you to confirm your choice.
If the software subsets listed are the ones you want, type y.

If you

type n, the list of optional software subsets is displayed again, and

you can select the subsets you want.
Messages appear as each software subset you selected is installed and

verified.
If a kernel must be built for the software product you just installed,
you are asked which kernels you want updated with this product. For
exmple,
Which

build

the

following

with

the

kernels

product

just

you

want

installed?:

You should build all the default kernels so that all types of clients
can use the installed software.

In this example, the system manager

chooses to build a kernel for the VAXstation 2000 color monitor:
SESGVAX

applies

VAXstation
Build

SESGVAX

the

following

2000

kernel?

processor

types:

color

(y/n)

[y]:

Be sure to build kernels for any client processors whose existing

kernels were built using ULTRIX Worksystem Software Version 1.1
software.

A message like the following appears when the kernel has been built:

9.
*

The

new

configured

kernel

/var/diskless/dlenv0/root0.vax/sys/SESGVAX.dlconf/vmunix
If

any

they

clients

will

now

had
be

links

linked

to
to

kernels
the

that

updated

were

kernel.

just

updated,

If you had clients registered for this root?.vax directory and they
were not linked to a default kernel, you will now be asked whether
to copy the corresponding updated default kernel to those clients.

10.

If diskless clients are registered to share this area, a prompt asks if
you want to update the Cliname.root directories of those clients.

Enter yes to keep the diskless clients in a consistent state.
Repeat these installation procedures for each root?.vax area you plan to set
up.

3.3

Setting Up Clients’ Defaults

After you complete the disk partitioning procedure and have installed all
the software products desired into a diskless environment, use the dms
utility Configure Server Menu option, Set up Clients’ Defaults, to set up

the default configuration for diskless clients who will be registered for this
diskless server area.
The default values you set during this procedure are
the default values that appear in square brackets, [ ], when you register
diskless clients using the dms option, Add a Client, or if you choose the
Set up Clients’ Defaults option again to change the defaults.
3.3.1

Setting Up a Default Client fstab File

You can create a default fstab file that can be copied each time a client is
added. Use this default fstab file to let clients mount other file systems,
like user areas, from the server. Place your default fstab file in

Ivar/diskless/defs/fstab.

and to fstab(8)

fstab files.

Refer to the Guide to System Environment Setup
in the ULTRIX Reference Pages for information about
‘

The dms utility checks each client’s root directory and corresponding usr
area against each mount point listed in the default fstab file. If any mount

points do not exist, the dms utility creates the necessary directories.
When the client is next booted, all the file systems listed in its fstab file
are mounted.

In the following example, the system manager on tigris creates a one-line,
default fstab file to let clients mount the users directory from that server:
/usr/users@tigris:/usr/users:rw:O:O:nfs:soft,bg,nosuid:

Entries in the fstab file must be exported from the server.
This requires
an entry in the server’s /etc/exports file.
Refer to the Guide to the
Network File System and to exports(8) in the ULTRIX Reference Pages for
more information.

In the following example, the system manager has added the line /usr/users
to the existing /etc/exports file on tigris to ensure that the fstab file is
exported properly to all clients:
/usr/users
/var/diskless/diclient0

-n

-r=0

nobody

/var/diskless/dlenv0

-0

-r=0

nobody

-n

Specifying nobody means that no one can mount the exported diskless
The -n option prevents a client from accessing
the next higher level in the directory structure, relative to its root
file systems manually.

directory.
The -0 option makes the file systems read only, and -r=0
maps the client’s root access to the server’s root user identification.

3.4

Rebuilding Diskless Default Kernels

You can use the dms utility Configure Server Menu option, Rebuild
Kernels, to build kernels that were not built during installation of a
root?.vax area.
This option lets you build default kernels for diskless
clients that are to be added, but whose processor types do not match any
of the default kernels built previously.
Only the default kernel
configurations provided with the diskless software can be built with this
option.

The example that follows describes the steps required to build the default
kernel for a multi-station VAXstation II/GPX:
1.

Invoke dms and select the Configure Server Menu option.

When the Configure Server Menu appears, type k to select the
Rebuild Kernels option.

A message like this appears:
You

have

chosen

build

kernels

only.

If there is more than one root?.vax directory available, a menu
appears listing the possible directories.

A message like the following appears automatically if there is only
one directory available, or after you enter the number corresponding
to your choice of directory if there is more than one available:
Which

kernels

you

want

build?

Type y at the prompt to build each kernel you want. For example:
QEQD2VAX

applies

VAXstation

the

following

multi-station

Build

QEQD2VAX

processor

types:

II/GPX

kernel?

color

(y/n)

[n]:

A message appears saying that kernel building is occurring and that
it may take several hours.

Messages appear as the kernels are built.
Note

The ULTRIX File System (UFS)
workstations.

is not needed for diskless

Ignore the message warning that UFS is not

configured.
6.
*

As each kernel is configured, a message similar to this appears:
*

The

new

configured

kernel

/var/diskless/dlenv0/root0.vax/sys/QEQD2VAX.dIlconf/vmunix

Each kernel you build can be either linked or copied to applicable
processors which you register as diskless clients.

If you already added clients and tried to link or copy a default kernel that
had not been built to those clients, a message like this appeared:
WARNING:

will

not

default

able

kernel

boot

exists.

diskless

The

without

client

one.

Invoke the dms utility again and use the Modify Client Parameters option

to link the appropriate clients to the kernels you rebuilt.

Management and Maintenance 4

This chapter describes how to manage and maintain the diskless
environment and how to manage diskless clients. The instructions tell you
how to perform the following tasks:
°

Add a client.

Boot a client.

Modify a client.

Remove a client.

List a configuration.

Read mail on a client.

Customize a client’s setup.

Maintain the diskless server area.

4.1

Adding a

Client

To add a client processor:
1.

manager

password:

Enter your root password, which does not appear on the screen.
2.

Type the following at the system prompt:
#

/etc/dms

A message appears reminding you that all users who are going to
access the diskless server area must be licensed to use that software.
It then asks you to type your superuser password:
Licensing

Message

continue

please

enter

the

superuser

password:

If you type an invalid superuser password, the dms utility returns
you to the system prompt.

If you type a valid superuser password,

a message appears that explains what documentation you should read.

Select the Add Client Processor option by typing a:

Client

Processor

Client

Parameters

List

Configurations

Enter

your

choice

Exit

[

0
=0

Remove
Modify

—3

Processor

UTILITY

Server

Client

(DMS)

TR |

Configure
Add

SERVICES

Y PR

MANAGEMENT

VVVVVYV

DISKLESS

A message appears indicating that you have chosen to add a client
processor.

The message also supplies some additional information.

A prompt asks if you want to continue with the add client processor
procedure.
After you confirm that you want to continue, a prompt asks you to
enter the client’s host name.
Enter the host name from the DMS

Client Setup Worksheet.

For

example:
Enter

the

client

processor’s

host

name:

bergalt

If you did not enter the client processor’s host name in the
/etc/hosts file, the dms utility displays an appropriate error message

and repeats the prompt.

If the server is also a BIND server the name you enter must include
the BIND server’s domain name, for example:
tigris.dec.com

If the BIND server’s domain name is not included, a message
appears telling you how to specify the client’s host name for BIND.

The next prompt asks you to type the hardware Ethernet address for
the client. See the worksheet you filled out in Chapter 2 for the
correct entry.

In this example, the system manager specifies the hardware Ethernet
address for the client bergalt:
Enter

the

example,

client

processor’s

00-AE-F2-00-38-05

[

hardware Ethernet address,
]: 08-00-2B-03-05-8B

for

If more than one root?.vax directory has been installed in this
diskless server area, a prompt appears asking you to select the name
of the root?.vax directory to copy for this client’s Cliname.root

directory.

Each of these root?.vax directories may contain different

software subsets.

If only one root?.vax area has been installed, the
prompt does not appear and the existing root?.vax directory is
assigned automatically.
If the prompt appears, enter the number corresponding to the
root?.vax directory that you want.
In this example, the system
manager selects
Select

the

root