Digital PDFs

AA-NE12A-TE

May 1989

93 pages

Original

4.0MB

view download

OCR Version

3.8MB

view download

Document:	ULTRIX Release Notes for RISC Processors
Order Number:	AA-NE12A-TE
Revision:	0
Pages:	93
Original Filename:

OCR Text

ULTRIX

Release Notes
for RISC Processors

Order No. AA-NE12A-TE

ULTRIX-32 Operating System, Version 3.0
ULTRIX Worksystem Software, Version 2.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

ULTRIX

VMS

DECnet

ULTRIX-11

DECUS

ULTRIX-32

XUI

DECwindows

VAX

ULTRIX Worksystem Software

MicroVAX

VAXstation

ila] i 1]al1]

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

PostScript is a registered trademark of Adobe Systems, Inc.
X Window System is a trademark of MIT.

This manual was written and produced by the ULTRIX Documentation Group in Nashua, New
Hampshire.

Contents

About This Manual

ATAICIICE ooeeeeeeeeeeeeeeeeeee e ettt eeeeeeseabaaesassaaaaaeseeesnaseasttnsssstaratbaaeesrarissaeneanassanaes

OFANIZALION ..vevivveeereeiiieeiiiiiie ettt

CONVENTIOIIS oovueeeveneeeieneeetrtiseerrsaeeesnnasesasssserssesseeesestomsseesrisssssinmeesraesasnsssesssses

1 System Setup Notes

ie
s e e raesssaeeaeeraassaass
et eieiieeri
1.1 Installation INOLES .ceuviieeiiiiiiiii

1-1

1.1.1 Changes to the Advanced Installation ...

1-1

1.1.1.1 Selecting Swap Partitions ...,
1.1.1.2 Unsupported Subsets ........ccccovviiiiiiiiiiiiiiiii
1.1.1.3 System Disk Partition Tables ..........ccccccviimiiiiiiiiinnnn

1-2
1-2
1-2

1.1.2 Structure of Distribution Media .....ccc.ooooviiiiiininiiiiiiiiininen.
1.1.3 Making Special Files After an Installation .....................
1.1.4 ULTRIX Boot Path Restriction .....c....cccooviiiiiiiiiiniiinin.
1.1.5 Failure During Tape Installation ...
1.1.6 Correcting Nonexistent Symbolic Links .......ccccccoviiiiiiiniiiis
1.1.7 Formatting Disks .....ccoooviiiiiiiiiiiiiiir
1.1.8 Identifying DeviCes .......ccccccirirriimiimiiimimimiiiiiiiiiiiiinas

1-3
1-3
1-3
1-3
14
1-4
1-4

1.2 Remote Installation Service NOtES ...ccoooeviiiiiiiiiiiiiiiiiiiiiiiiineeen
1.2.1 Changes to the Network Installation ...
1.2.2 Duplicate Copies of /etc/mop_mom on Startup ................

1.2.3

Registering Clients with BIND Hostnames ...............ccccoeiiee.

1-4
1-5
1-5

1.3 Diskless Management Services NOteS .......ccccccvviiiiiieieiiiieiiiinnieiiinnninnnnns

1-5

1.3.1 Diskless Management Services Installation Notes .................

1-6

1.3.2 Different DMS Commands

.........cccooeviiieiiiiiiiiiiiiireeiiieeeeriineeennns

1-6

1.3.3 The /etc/exports File ......ccoccooiiiiiiiiiiiiiiiiiiiiiiinriie
e

1-7

1.3.4 DMS Mount Point Change ..........cccooeoiiiiiiiiiiiiiiiiiiiiieenreeeneniennn.
1.3.5 Creating Links for the /usr/hosts Directory .........cc....cccoocceeiis

1-7
1-7

1.3.6 Changes in Setting Up Disk Environments ...............ccc.........

1-7

1.3.7 Timezone Setting for Diskless Clients
1.3.8 Diskless Client Directory

........c.cc.ccoieiiiiiiiniannnnn.

1-8

.......c..cccocvvviiriiiiiimiiieniieeiiiireeeeeeeeeeeaens

1-8

1.3.9 Sufficient Disk Space

......cccoooviiiiiiiiiiiiiiiiiiiiiien

1-8

1.3.10 VAX Diskless Clients

..........cooviiiiiiiiiiiiiiii

1-8

1.3.10.1 Changing the swap Area ........cccccooeiiiiiiiiiiiiiiiiiiieieeeeerriieeen,

1-8

1.3.10.2 Loading the MOP Subset

........ccccoeviiiiiiiiiiiiiiiiiiiiieiiieeeennnn,

1-9

1.3.11 Adding and Modifying Clients

........cccccooiiiiiiiiiiiiiiiniiiiiiiieeee,

1-9

...........cccooooiiiiiiiiiiiiiiiiiiie
e,

1-9

1.3.12 Kernel Build Failure

1.4 System Configuration Notes ..........cccooiiiiiiiiiiiiiiiiiiiiin
1.4.1 Increasing Your Swap SpPace
1.4.2 Printer SetuP

1-9

........cccccriiiiiiiiiiiiiiiennnnneeeeeeeenenenee

1-10

..ccccocoeiiiiiiiiiiiieeiiiieeeiiiee
et eette e et ee ittt e esaraeeaeananns

1-10

1.4.3 Spool Directories for Remote Printers ........ccc.ccccovieiviiiiiinninnn.

1-11

1.4.4 Shared Modem Lines

.........cccoooiiiiiiiiiiiiiiiiiiieeiiieeeeiiie
e

1.4.5 Reactivating Hardwire Terminals

................c..coeeiiiiiiiiiiininn.

1-11
1-11

1.4.6 Unterminated Terminal Lines ..........ccccoooiiiiiiiiiiiiiiiiniiiiieenn,

1-12

1.4.7 System EXEerCiSers .......c.ccocccciiiiiiiiiiiiiiiieeiiiiieeeeeeirieeeeeeeiniaeeeeanas

1-12

1.4.8 Eight-Bit Terminal Driver Support .......cccccoooiiiiiiiiiiiiiiiinieennnn.

1-12

1.4.9 PostScript Support Requires Adobe Font Metrics Files

1-13

1.4.10 Relocating awk and sed Binaries

.......

..........ccccccoviiiiiiiiiiiiiiinnnnnnn.

1-13

1.4.11 The /etc/svcorder File for YP and BIND ........cccccoeevvrrinnnnin.

1-14

1.4.12 Configuring Your Network with YP or BIND

......................

1-14

2-1

..........ccccceeeiiiiiiieiiiiiiiieeeeeeiiiieeeeerevee

2-2

2 ULTRIX Worksystem Software Notes
2.1 Known Server Problems

2.2 DECwindows AppPLCations

..........cooooiiiiiiiiiiiiiii

.............ccccooomiiiiiiiiiiiiiiiiieiiceeeeees

2-3

2.2.2 The dxterm Terminal Emulator ............ccooooviiiiiiiiiiiiiiiiiiinennnnn.

2.2.1 The dxmail Mail Handler

2-3

iv Contents

2.2.3 The dxcalendar Program

............ccccccooviiiiiiiiiiiiieiiiiiniiiiiieeeieennnn.

2-6

2.2.4 The dxcalc Calculator ..........cccoovvveiiiiiiiiiiiiiiiiecceeeee
e

2-6

2.2.5 The dxdb Debugger

2-6

...
e

2.2.6 The dxsession Session Manager
2.2.7 The dxvdoc Program

...........ccccoccocovveiviiiveriiieerennneenns

2-7

...........ccccocoiiiiiiiiiiiiiiiiiiiieiiiiee
e,

2-9

2.2.8 The dxdiff Visual Differences Program ............cccccovvivniennnn...

2-9

2.2.9 The dxue User EXeECULIVE

.....cooovviiimiiiiiiiiiiiiiieiiieeiieevieeveeeins

2-10

2.2.10 The dxnotepad Program

..........cccccccooviiiriiiiiiiniiiiriieerrninierieennnn.

2-11

2.2.11 The dxpaint Program

.........ccccoooiiiiiiiiiiiiiiiiiiiieeeeeeeeveeeevri
e,

2.2.12 The dxpsview PostScript Previewer

2-12

.........ccccccoovvviivriiirnnnnnne.

2-12

2.2.12.1 Known Problems ........ccccevvviiiiiiiiiiiiiiieeeeeeeeeeeeeeeeeeseeeeasaeans

2-12

2.2.12.2 Application Resource Names

2-14

.......ccccooovvuuvvviiiieeeeeeeneeeaannne.,

2.2.12.3 Differences Between the Previewer and an LPS40

Printer

..o

2-14

2.2.13 The dxwm Window Manager ..........cooccccoeeieivniviiriieiernnrerenneennn.

2-14

2.2.13.1 Naming Windows and Icons

.......cccccccovviriiiiiiiiiiiiieriinnnnnnnn.

2-15

2.2.13.2 Handling Mapping Requests

.......cccooeviiiiiiiiiiininirnniirnnennnn.

2-16

2.3 Demonstration Programs

2-17

........cccoiiiiiiiiiiiiiiiieiiiiee
e ceeerr e eeeertee e e e raaseee

2-17

2.4.1 The uwm Window Manager ..........ccccooeeviivirrieiiiiiiiiinieeiiiiienneennns

2-18

2.4 X11 R3 Applications

.........cccciiiiiiiiiiiiiiiiiii

2.4.2 The xbiff Command ............cccoeiiiiiiiiiiiiiieiiiiiiiecreeeeeeeeeeeenaes

2-18

2.4.3 The xterm Terminal Emulator ...........cccccooiviiiiiiiiiiiniriiiineninnnn.

2-18

.......cccoovvviiiiiiiiniiiinnnnnnns

2-20

2.4.5 Command Line Syntax Changes ........ccccccccvviiiiieereeeriiiiinieinnennn.

2.4.4 Changes to .Xdefaults from MIT X10

2-21

2.4.6 Unsupported R3 CHents

2-21

.......cccccoiviiiiiiiiiiiiiiiiiiiieeceeeeeeveceveeens

2.5 DECWINAOWS FONtS ..oovuiiiiiiiiiiiiiceee
2.5.1 Font File NAmMeS

2-21

.....ccoovuiiiiiiiiiiiiiieieee
et
e e nas

2-22

2.5.2 Access to Font Names

.......ccccoooevmriiiiiiiiiiiiiiiieicriiieeeeeeeeee
e,

2.5.3 Understanding Font Names

2-22

........cc.ccccoeeeieiiiviiiiiiiviiiineeieiee
s

2-23

2.5.4 Font Properti€s ....ccccocioiiiiiiiiiiiiiiiieeeeiieeeeeeviieeeeerie
e eraae e eanaes

2-24

2.5.5 Font Problems

...

2-25

2.6 The XIib Library

...t
e s e e aees

2-25

2.7 The XUI TOOIKIL

.coovviiiiiiieiiiiiieeeiiie
ettt eeis e e rtreeeeateesren e esatnessanneenns

2-27

Contents v

3 ULTRIX-32 Operating System Notes

3.1 Differences Between RISC-Based and VAX-Based Systems ............. 3-1
3.1.1 Components Not in RISC-Based Systems ...........ccceeiieinnn 3-1
3.1.2 Components that Differ ..., 3-3
3.1.3 Components on RISC-Based Systems Only .........c.cccceiinins 3-9
3.1.4 Unsupported Components on RISC-Based Systems ............... 3-10

3.2 Hints for Porting Software to RISC-Based Systems .................. 3-10
3.3 Compliance with Operating System Standards ................... 3-12
3.4 Network File System ....ccccccooeeiiiiiiiiiiiiiiiiiiiiiriinienreeceee 3-12
3.4.1 NFS File and Record Locking .....c...ccccoviiiimiiirmiiiniiiiinncnnn. 3-12
3.4.2 NFS Server Security Changes .........ccccocvviiiiiiiiiiiiieinieniininnnn. 3-12
niii 3-13
s
3.5 Programming NOtES .....cccccoviiiimiiimiiiiinien
3.6 LIDIATIES cevveeeneeeniiineiriiiierneerneerarsasreesenssssresserneensessnsersesssssnnsssesserssssssseniones 3-13
es 3-13
iases
iiniinrerrss
s sieerrecessssaa
3.6.1 C LIDIary ...oeceeeveeieieviiiiiieiiieieiiiiii
3.6.2 Math Library ........ccccooviicoimiiiiiiiiiniiiinieiniinnssscnee 3-14

3.7 Compiler NOLES .cccceeriiiiiiiiiiiiiiiiii

et 3-14

3.8 Commands and Utilities ......ccoceoeiieiriiiiiiiiiiiiie

et 3-16

nri
e e e eeaaeeess
3.8.1 The ar Command ........cccooeeriiiiiiiiierreeiiitii
e
3.8.2 The lint Command .......c..ceovviieriririmiiiiiiiier
3.8.3 The Iprsetup Command ..........ccoceiiiiiimiiiiiinniiiis
iiiee
e
3.8.4 The Ipr Command ........ccoccviriiiiiniiiiiiiiini
3.8.5 The cp Command ......cccccccviiiiiiiiimmmmiiiirrrrrinirr e
3.8.6 The showmount Command ........ccccoceeriiiimmmiiiiirmiiiiiinninennen.
3.8.7 Regular Expression Handling ...,
et
3.8.8 The mail Command .......cccceeemreeiimiiiiiiiiniiiiir

3-17
3-17
3-18
3-18
3-18
3-19
3-19
3-19

3.8.8.1 Alternate Forwarding File ...........cccomiiiinniiin.
3.8.8.2 Daemon Start Order .......cccocooeevieiieeiiriiiiiiiiiiiiiiiniers
3.8.8.3 Delimiters for ANASINg ....cc.c.cccoeeiiimiiirmmiiiiriiiennnneereen
3.8.8.4 Invoking mail More Than Once ........ccccooeiiiiiiiiiiiienccnnnnnn,

3-19
3-20
3-20
3-20

vi Contents

3.8.9 The sh Command ....c.coooeeiniiiiiniiiiiiiiiitierreirterearenestrseresasasasenss
e
3.8.10 The newcsh Command ........cccccoviiiiiiiirriimiiineeiiiereeer
eaaes
et
3.8.11 The chfn Command .......cccocieiiiiiiiiiiiiiiiiiicr
3.8.12 The cpio Command ............cccocviiiiiiiiiiiiiiiiiiiin
e,
et eeaaaes
3.8.13 The csh Command ........ccccoiriiiiiiiiieieiereeieiiee

3-20
3-21
3-21
3-21
3-21

3.8.14 The dc Command .......ccooueeiiiiiiiiiiiiiiiiieeeiieree
s e e eeaasaas
e e naes
e
3.8.15 The Itf Command .......ccoouvvmiiiiiiiiiiiiiiieeirer
3.8.16 The make Command ..........occeiiuiiiirimiriiririini
i aans
3.8.17 The pstat Command .......cccccccerrrrimmmmmimmmiiiniiiiiens
e,
3.8.18 The rdump Command .........ccccceerriiimiiiiiiiniiiiiiiiiiiine
3.8.19 The script Command .........cccccccvveieiriiiiiiiiiiminin
e
3.8.20 The setld Command ........cccceiiiiiiiiiiiiiiiiiiiiieii

3-21
3-22
3-22
3-23
3-23
3-23
3-23

3.8.20.1 Removing Subsets ........ccceeeiieiieiieniiiiiiiiiiiiiiiiinnii
e,
3.8.20.2 Installing Subsets from Two Installation Devices ..........
3.8.20.3 Installing Subsets .....cccccccvvuierrememiiiiiiiiiiireet
s

3-23
3-23
3-24

3.8.21 The size Command .......ccccooiiiiiiiieiiiiiereiiiererirrinicee
st ceraseeenes
3.8.22 The talk Command ........cccoeeiiiiimiieiriereiiieriereeeereeeenserneseeeesens

3-24
3-24

3.8.22.1 The talk Command Is Not 8-bit Clean .........cccccceeerreennn.
3.8.22.2 Changes in the talk Program ...........cccccccoooviiiiiiiiiiinnnnn...

3-24
3-25

e
The uucp Command ..........ccccrrrmminiiiiiiiiiiiiiiiiiiee
The uucpsetup Command ...........ccceeeviiirimiiiiiiiiiiiiiiiiiii.
s eraaees
The vi Command ......cccccceeiiiiiiiiiiiniriiiriieiic
The yppasswd Command ......c...ccccceeeiiiiiiiiiiiiiniiniiniiniiin.

3-25
3-25
3-25
3-26

3.9 System Facilities ........cceevviiiiiiiiiiiiiiiiiiiiii
e

3-26

3.8.23
3.8.24
3.8.25
3.8.26

3.9.1
3.9.2
3.9.3
3.9.4

Errors in the /etc/passwd File .....cooooeiiiiiiiiiiiiiiiiiiniiiiiinninn
The ptrace System Call .......cccoooeiiiiiiiniiiiiiiiiii,
The sendmail Program ........ccccccoeereimmmiriiiiiiniiiriiieiiniiiiiceeennnn,
Writing into a Remote a.out File .......cccooooiiiiiiiiiiiiinn
.

3-26
3-27
3-27
3-27

3.10 Networking and Communications ......cc....ccccovviiiiiiiiiiiiiiiiiiiienninniinnnnnn

3-28

DLI/802 Passes Up Packets That Should Be Dropped ......
DLI/Ethernet DIIVErs ....ccccccciiiiiiiiiiiieierrenereennsesuseressssnseenes
Incorrect UUCP Checksum Calculation with F Protocol ....
Performance Improvement for YP and BIND ......................
Manual Update of BIND server’s Serial Number ................

3-28

3.10.1
3.10.2
3.10.3
3.10.4
3.10.5

3-28
3-28
3-29
3-29

Contents vii

3.10.6 Use of Full Host Names When Running BIND ................. 3-29
3.10.7 NFS Server Security Changes .......cccccccoviiriiiiimiiiiiiiiiinininiennnn, 3-30
3.10.8 Blank Lines in Yellow Pages Map Files ....ccccoocoeiiiiiiininnnnnn. 3-30

3.11 Standards and External Specifications .......c.ccccoomiiiiiiiiiii. 3-30
3.11.1 POSIX Interface Support .....cc.cccccooiiiiiiiiiimiiiiimmiinreeniiineeeeaeenn.
3.11.2 System Calls in the POSIX Environment ........................

3-30
3-31

3.12 Miscellaneous Known Problems ...........ccooooiiiiiiiiiiiiiiiiiininiiiiinnnniennn 3-31
4 ULTRIX Documentation Notes

......cccocceveeireiiiiiiiiiiniiiiiiieenerieenecenanns

4-1

4-2

4.3 Undocumented Library Functions .......cc....ccoeoiiiiiiiimiiiiiniiiinnnennnee.

4-3

4.1 Revised and New Documents

4.2 Reference Pages ......ococoviiviiiiiiimiiiiiiniiiiii

viii Contents

About This Manual

These notes apply to the ULTRIX Worksystem Software, Version 2.C
(RISC) and ULTRIX-32 Operating System, Version 3.0 (RISC) software
kits. The ULTRIX Worksystem Software, Version 2.0 (RISC) kit is
intended for RISC-based workstations and contains two components:
.

Graphics windowing software

Base operating system software

The ULTRIX-32 Operating System, Version 3.0 (RISC) kit is intended for
RISC-based server systems and contains only the base operating system
software.

Audience

This manual should be read by all customers who have a purchased an
ULTRIX Worksystem Software, Version 2.0 (RISC) or ULTRIX-32
Operating System, Version 3.0 (RISC) system.
Organization
Chapter 1

System Setup Notes

Contains the notes that you should read before installing

your system, setting it up as a remote installation ( ris) or
a diskless management services (dms) server, or configuring
(building) your system kernel.

Chapter 2

ULTRIX Worksystem Software Notes
Contains the notes that pertain to ULTRIX Worksystem
Software, which provides the graphics windowing software.
If you have an ULTRIX Worksystem Software, Version 2.0
(RISC) system, you should read the notes in this chapter.

Chapter 3

ULTRIX-32 Operating System Notes
Contains the notes that pertain to the ULTRIX-32

Operating System, which provides the base operating system
software.

If you have an ULTRIX Worksystem Software,

Version 2.0 (RISC)
Version 3.0 (RISC)

or ULTRIX-32 Operating System,
system, you should read the notes in

this chapter.
Chapter 4

ULTRIX Documentation Notes
Contains the notes that pertain to the ULTRIX

documentation that shipped with your ULTRIX Worksystem
Software, Version 2.0

(RISC)

System, Version 3.0 (RISC)

or ULTRIX-32 Operating

system.

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.

name(n)

References to ULTRIX commands, system calls, or

subroutines include the section numbers in the ULTRIX
Reference Pages or ULTRIX Worksystem Software

Reference Pages where they are documented.
italics

In syntax and function definition descriptions, this type

indicates terms that are variable.
UPPERCASE

The ULTRIX system differentiates between lowercase and
uppercase characters.

In examples, enter uppercase

characters only where they are specifically indicated by an
example or a syntax line.
example

In examples, system output is printed in this type.

example

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

x About This Manual

System Setup Notes 1

The notes in this chapter provide information about installing and setting
up your ULTRIX Worksystem Software, Version 2.0 (RISC) or

ULTRIX-32, Version 3.0 (RISC) system. You should read this chapter in
its entirety before you install your software distribution Kkit. Then,
depending on your system, you should read the relevant notes in the

remaining chapters.

This chapter discusses:
.

Installation notes

Remote installation service notes

Diskless management services notes

System configuration notes

1.1

Installation Notes

The notes in this section pertain to the installation procedure.

This

section discusses:

Changes to the advanced installation
Structure of the distribution media

Making special files after the installation

ULTRIX boot path restriction

Failure during tape installation

Correcting nonexistent symbolic links

Formatting disks

Identifying devices

1.1.1

Changes to the Advanced Installation

The next three notes are specific to the advanced installation procedure:

Selecting swap partitions

Unsupported software subsets

System disk partition tables

1.1.1.1
Selecting Swap Partitions - Avoid selecting the a partition of
any disk for use as a swap partition. If a customized partition table has
previously been defined for a disk and swapping occurs to the a partitions,
the disk partition table, which resides on the a partition, will be destroyed.
For information about increasing swap space, see Section 4.1.
1.1.1.2 Unsupported Subsets - To install desired unsupported subsets
from tape or CDROM distribution after you have completed the installation,
use the /etc/setld command. For further information, see setld(8) in the
ULTRIX Reference Pages.

To install subsets from tape, load the tape labeled UNSUPPORTED. To
install subsets from your CDROM distribution, mount the ¢ partition of the
CDROM and load subsets from /mnt/RISC_UNSUPPORTED or
/mnt/VAX_UNSUPPORTED, as is appropriate.
1.1.1.3 System Disk Partition Tables - If you have modified the
partition table of the system disk, the advanced installation issues a
prompt asking if you want to use the default partition structuring or the
customized partitioning. The basic criteria for allowing a customized
partition structure are that the root or a partition must be at least 32768
blocks and that the swap or b partition must be at least 12288 blocks.
(This assumes that you plan to add a second paging device.)
The
installation does not check to guarantee the size of any other partitions on
this disk. Therefore, you are responsible for selecting a suitable location
and size for the /usr file system.

During the advanced installation, no other disks on the system are

modified.

Whatever partition tables might exist are used; otherwise, default

partition structuring is assumed.

During a basic installation, however, target system disks are set to have
default partitions. No other disks on the system are modified during a
basic installation.

1-2 System Setup Notes

1.1.2

Structure of Distribution Media

The subsets on the distribution media are an ordered set of tar images

starting at the fifth file on tape. These images are compressed (with the
compress(1) utility). One benefit of doing this is that less space will be
required to hold the subsets when you set up a RIS area for network
installations.

Note that the setld product environments on the CDROM distribution are
structured hierarchically.

1.1.3

Making Special Files After an Installation

During an installation to disk, only the special files for the disk and tape
devices actually used are created. To make special files for other devices,
follow this procedure once the installation procedure has completed.
%

Password:
# cd /dev
# MAKEDEV device. . .

The device name specified should be the name of the peripheral as it is
displayed during auto-configuration when your system boots.
1.1.4

ULTRIX Boot Path Restriction

If an attempt to boot a kernel image from disk fails because the image
does not exist, the ultrixboot program prompts for the kernel image name
as follows:
Enter

image

name:

With this release, you must enter the following path using the same syntax
used at the console prompt:
rz(0,0,0)vmunix.new

The ultrixboot program is currently unable to load a kernel image from a
disk other than the actual booted device.
1.1.5

Failure During Tape Installation

During a TK50 tape installation, you must wait until the tape completely
rewinds before answering any questions presented by the Standalone
ULTRIX Environment.

This is necessary to prevent the installation

software from accessing the tape device while it is still rewinding after the

bootstrap operation.

System Setup Notes 1-3

1.1.6

Correcting Nonexistent Symbolic Links

After performing an installation, some symbolic links point to nonexistent
files.
%

To correct this, issue the following commands:

Password:
#

/etc/rdump

-s

/etc/rrestore

-s

../bin/rrestore

-s

sbmake

../bin/rdump

/usr/bin/make

/etc/rdump
/etc/rrestore

/usr/bin/make

Note that correcting this situation is not essential to normal operation.

1.1.7

Formatting Disks

The Basic Installation Guide for the DECstation 3100 states that you

must format and prepare your disks.

Because your disks are preformatted

and ready for use, you should ignore this step.

1.1.8

Identifying Devices

During an installation, you are instructed to use the test command to

identify the devices that are connect to your system.

To ensure that your

system will boot successfully, you should use the following commands to

identify your devices:
%

test

init

1.2

-c

Remote

Installation Service

Notes

The notes in this section pertain to a Remote Installation Service (RIS)

installation.

This section discusses:

Changes to the network installation

Duplicate copies of /etc/mop_mom on startup

Registering clients with BIND hostnames

1.2.1

Changes to the Network Installation

The ULTRIX Worksystem Software, Version 2.0 (RISC)

kit installation

offers the option of doing an advanced installation procedure from the

network.

Only those subsets beginning with UDT and UDW in a client’s

model file will be installed during the system installation.

You can install

other subsets from the network at a later time by using the /etc/setld
command.

1-4 System Setup Notes

The basic installation procedure from the network only installs the
mandatory UDT and UDW subsets.

1.2.2

Duplicate Copies of /etc/mop_mom on Startup

The ris utility attempts to modify the /etc/rc.local file to start the

mop_mom daemon on system startup. It does this by searching for a line
in /etc/rc.local that begins with /etc/mop_mom. If no such line is found,
one is created. This can cause duplicate invocations of the daemon if the

Jetc/rc.local has been modified to start the mop_mom daemon in a way
that is not recognized by ris.

If the /etc/rc.local file must be modified to start mop_mom in a way not

understood by this utility, you must add the following string to the
Jetc/rc.local file to prevent duplicate invocations:
/etc/mop_mom_risfix

This has no effect on system startup and effectively indicates to ris that
the mop_mom daemon has already been set up correctly.
1.2.3

Registering Clients with BIND Hostnames

The ris utility does not correctly register clients with full BIND specified
hostnames in the mop databases. This will cause a boot failure for these
clients when attempting to perform the network installation. If you
encounter this problem, make the following change:
%

Password:

# cd /usr/var/dnet/clients
# mv fullhostname.sys full hostname

The fullhostname is the fully specified hostname for the client that is to
be booted.

Diskless Management Services Notes
1.3
The notes in this section pertain to a diskless environment.

This section

discusses:

Diskless management services installation notes

Different DMS commands

The /etc/exports file

DMS mount point change

Creating links for the /usr/hosts directory

System Setup Notes 1-5

Changes in setting up disk environments

Timezone setting for diskless clients

Diskless client directory

Sufficient disk space

VAX diskless clients

Adding and modifying clients

Kernel build failure

1.3.1

Diskless Management Services Installation Notes

Diskless management services (DMS) has undergone a number of changes
that affect the way clients are added.

For example, only one GENERIC

kernel is distributed for use in running clients added to the environment.

Kernels are no longer built on the server system.

This means that at

least one client in the environment must be registered to build a
customized kernel.

Regardless of the client’s swap requirements, a

temporary (in the case of choosing a local swap device)
is created to support this activity.

network swap file

After adding this client, you should

boot the RISC-based diskless system using the following command:
>>

setenv

auto

bootpath

mop()

When the client system boots, it will automatically build the kernel as
described on the server system.

When the build completes, you are

instructed to set the boot environment at the console and to reboot using
commands displayed.

After the first client has built a customized environment, you can add
other systems that are to be considered clones of the first by using the

“duplicate sub-option”.

For now, only the /dev directory and the /vmunix

and /etc/hosts file and /sys hierarchy are duplicated from the first
environment.

The rest of the client’s root environment is installed as in

the past from the selected ‘“dlenv?/root?.mips” environment.

1.3.2

Different DMS Commands

For ULTRIX Worksystem Software, Version 2.0 (RISC)

and ULTRIX-32,

Version 3.0 (RISC), DMS has been significantly changed to support a nonVAX architecture.

As a consequence, the /etc/dms.new command has been

provided with the RISC-based server kit to serve other RISC-based clients.
You should use the appropriate DMS command when managing your RISCbased and VAX-based clients:

/etc/dms.new for RISC-based system and

letc/dms for existing VAX-based system.

1-6 System Setup Notes

1.3.3

The /etc/exports File

Do not change the entries in the /etc/exports file by replacing blanks with
tabs or breaking up long lines with a return. The dms utility places its
entries in the /etc/exports file in a format that it can recognize when it
reaccesses the file. Failure to follow these guidelines can cause problems
with the mount daemon and with the dms utility’s ability to read the file
properly.

1.3.4

DMS Mount Point Change

The mount point for dlenv? and diclient? have changed. The new mount
point are /dlenv? and /diclient?, not /var/diskless/dlenv? and

Ivar/diskless/diclient?.

The /etc/fstab and /etc/exports files reflect this

change.

This note pertains to /etc/dms.new only.

1.3.5

Creating Links for the /usr/hosts Directory

On the diskless client, the /usr/hosts directory does not contain any links
that will allow you to log in to another system by entering that system’s
name as a command.

To create the links, type the following command:
% /usr/hosts/MAKEHOSTS /dlenv?/root? .mips/usr/hosts

1.3.6

Changes in Setting Up Disk Environments

The DMS utility no longer requires dedicated disks for the software or

client environments when setting up a diskless area.
to use individual partitions for diskless areas.

You are now allowed

You must take care to set

up the partitions of the disk they will be using. That is, you must take
care that the partitions chosen are large enough to complete the procedure
successfully when installing software or to hold the total number of clients
that will be registered. Repartitioning of the disk is no longer performed
through the dms utility.

You must set up the disk partitions before using

them.

These changes offer more installation flexibility by not requiring an entire
disk for diskless environments and allow multiple environments on different
partitions within the same disk. The new changes also allow you to add
additional diskless environments at any time.

Before invoking the dms utility, you should read the Guide to Diskless

Management Services.

In particular, you should read Chapter 3, which

discusses the new procedure for selecting disks and partitions.

System Setup Notes 1-7

1.3.7

Timezone Setting for Diskless Clients

When you add a diskless client, its timezone setting is extracted from the
server’s config file. The dms utility depends on the presence of a properly
constructed configuration file on the server system as was created during
the installation acting of the server.
1.3.8

Diskless Client Directory

A diskless client directory ( /diclient?) must exist before you install any
software subsets. You must use the appropriate dms option to configure a
client partition on your server system; otherwise, when you install the
second set of subsets, dms will fail.
1.3.9

Sufficient Disk Space

It is important that you carefully calculate disk requirements for diskless
client areas by using the documentation provided with your server kit. If
you do not have enough disk space and you attempt to add a diskless
client, the dms.new utility will fail to register the client. In addition, the
remove client function also will not work. In this case, you will have to
remove the /diclient?/client_name.root directory manually.
VAX Diskless Clients

1.3.10

The next two notes are specific to serving VAX diskless clients:
o

Changing the swap area

Loading the subset

1.3.10.1
Changing the swap Area - If you execute the dms Modify
Client Parameters option to change the swap area from SERVER to
LOCAL or LOCAL to SERVER, the system will display warning messages.
On rebooting VAX diskless clients, you should ignore any of the following
messages that may appear:
mkdir

mv:
mv:

/sys/SYSTEMNAME

cannot
cannot

dev/X0

access
access

File

dev/ttypf
dev/ptypf

Exists

1-8 System Setup Notes

Exists

1.3.10.2 Loading the MOP Subset — When a RISC machine serves VAX
diskless clients, the MOP subset should be loaded on the server and
installed into all VAX client areas. Otherwise, the diskless client cannot
build a netblk executable file that contains the required network
information, and the following message will be displayed:

Cannot

find

SAS/mop.h

In addition, if the diskless client swaps on local disk, the kernel will not
boot.

1.3.11

Adding and Modifying Clients

When adding clients by using the dms duplicate suboption, you should
follow the instructions to boot the client before attempting to modify the
same client.

1.3.12

Kernel Build Failure

A difference in the time of day between the server and a client system

(more specifically, when the server’s date and time lags the client’s) can
cause the kernel build to fail This discrepancy causes an obscure problem
with makefile dependencies to appear in the form of a “syntax error’ when
diskless client systems attemp to build their kernel

A workaround for this problem is as follows:

Either temporarily adjust the time on the server so that it is ahead
of the client system, or set the date and time on the client system
so that it lags the server’s date and time.

Reboot the client system and allow it to complete the kernel build.

System Configuration Notes
1.4
The notes in this section pertain to your system configuration.

This

section discusses:
°

Increasing your swap space

Printer setup

Spool directories for remote printers

Shared modem lines

Reactivating hardwire terminals

Unterminated terminal lines

System exercisers

System Setup Notes 1-9

Eight-bit terminal driver support

PostScript printer support

Relocating awk and sed binaries

The /etc/svcorder file for YP and BIND

Configuring your network with YP or BIND

1.4.1

Increasing Your Swap Space

If you increase your swap space beyond the default 60 Mbytes by adding
swap partitions or using a larger swap partition and you plan to run
processes with very large data segments (that is, greater than 85 Mbytes),
you must edit your system configuration file and increase the system
dmmax parameter accordingly. The syntax of the dmmax parameter is:
dmmax n

Specifies the number of 512-byte disk blocks in a swap fragment.
(The default is 4096.)

The following table provides guidelines for making the appropriate change:
Configured Swap

60 Mbytes (default)
0 — 85 Mbytes
86 — 170 Mbytes
171 - 340 Mbytes

Recommended Value

4096 (default)
4096

8192
16384

For further information, see the Guide to System Configuration File
Maintenance for RISC Processors.
1.4.2

Printer Setup

The default size limit of a file to be printed is 1025024 bytes (local or
remote).
As superuser, you can modify this default by editing the
/etc/printcap file on the local system where you issue the Ipr command and
inserting the mx#0 or mx#nn parameter.
If mx#0 is specified, the default
file size is unlimited.
If mx#nn is specified, the default file size is the
specified number of 1024-byte blocks.

Once set, this new limit applies both to local print jobs and to those print
jobs sent to remote systems. Note that this limit on the local system does
not affect print requests sent from remote systems.

1-10 System Setup Notes

As a nonprivileged user, you can workaround the file size limit by dividing
the file into sections less than 1025024 bytes before printing (assuming
that the file data format allows for this). Or, you can use the rcp
command to copy the file to a system with a printer that has a
sufficiently large file size limit. Log in on that system and then request
local printing.

Spool Directories for Remote Printers

1.4.3

If you specify a printcap entry for a remote printer, you must also create
a spool directory for that printer, just as you would for a local printer.
For example, if you have an LA100 printer with a printcap entry of
:sd =/usr/spool/la100, then you should type the following commands to
create its spool directory with the proper owner:
%

Password:

# mkdir

chown

1.4.4

/usr/spool/1al00

daemon

/usr/spool/1al00

Shared Modem Lines

The use of shared lines requires modem control. Carrier detection must be
raised on receipt of an incoming connection and must be dropped when the
remote party hangs up. Direct connects that use modem eliminators do
not obey this protocol and cannot be used for shared lines. If you try to
use shared lines on a direct connect line that has Carrier Detect strapped
high, you will disable the line.

1.4.5

Reactivating Hardwire Terminals

Hardwired terminal ports other than the console port may hang as a result
of electrical noise appearing on the line when the terminal is turned off
and then turned back on. When the port is hung, the terminal does not
respond to keyboard input. To temporarily reactivate the terminal line,
follow these steps:

Determine the process identification (PID) of the getty process
associated with the terminal line with the ps command.

Use the kill command to kill that process. If you do not know the
number of the hung terminal line, use the last(1) command with the
user’s login name.

The following example shows how to temporarily reactivate a hung terminal
line.

Assume that the login name of the user is anders:

System Setup Notes 1-11

Password:

anders

last

anders
anders

ttyOl
ttyOl

Mon
Mon

Nov
Nov

18
18

10:00
08:35

still
09:08

logged in
(00:33)

anders

ttyOl

Mon

Nov

00:26

02:00

(01:33)

-ax

PID

STAT

TIME

COMMAND

0?”