SCO_XENIX_System_V_Run_Time_Environment_2.2A_Apr87 SCO XENIX System V Run Time Environment 2.2A Apr87

SCO_XENIX_System_V_Run_Time_Environment_2.2A_Apr87 SCO_XENIX_System_V_Run_Time_Environment_2.2A_Apr87

User Manual: SCO_XENIX_System_V_Run_Time_Environment_2.2A_Apr87

Open the PDF directly: View PDF .
Page Count: 488

Download
Open PDF In Browser	View PDF

• •
• •
•

•

seQ

THE SANTA CRUZ OPERATION

SCOXENIX·
System V
Operating
System

•

~--------------------~

S CO XENIX® System V
Operating System

Run Time Environment

Release Notes
Installation Guide
Introduction to XENIX
Operations Guide
Hardware Dependent (HW) Commands

The Santa Cruz Operation, Inc.

START HERE

,•

This binder contains everything you need to know about installing XENIX
and runningXENIX programs.
•

Before You Begin:
1

Check the Compatible Hardware section of the
Release Notes in this binder before making any
hardware modifications to your system.

Read the "Installation Notes" in the Release
Notes.

3 -

Glance through Chapter 2, "Installation Procedure,"
in the Installation Guide, also in this binder. Then,
use that chapter to help you install XENIX.

• If you've never used XENIX, refer to the Introduction To XENIX in this
binder. It shows you how to use some of the basic XENIX commands.

• The Release Notes contain important information about your system.
Refer to them if you have any questions.
• For information on operating your system, including how to add
terminals, line printers and other devices, and perform system backups,
see the Operations Guide.

The XENIX® System V
Operating Systelll

Release Notes.
Version 2.2.1

The Santa Cruz Operation, Inc.

Information in this document is subject to change without notice and does
not represent a commitment on the part of The Santa Cruz Operation, Inc.
nor Microsoft Corporation. The software descn'bed in this document is
furnished under a license agreement or nondisclosure agreement. The
software may be used or copied only in accordance with the terms of the
agreement. It is against the law to copy this software on magnetic tape, disk,
or any other medium for any purpose other than the purchaser's personal
use.
ALL USE, DUPLICA nON, OR DISCLOSURE WHATSOEVER BY
THE GOVERNMENT SHALL BE EXPRESSLY SUBJECT TO
RESTRICTIONS AS SET FORTH IN SUBDIVISION (b) (3) (ii) FOR
RESTRICTED RIGHTS IN COMPUTER SOFfWARE AND
SUBDIVISION (b) (2) FOR LIMITED RIGHTS IN TECHNICAL
DATA, BOTHAS SET FORTH IN FAR 52.227-7013.

PortionsC 1983,1984,1985,1986, 1987 The Santa Cruz Operation, Inc.
All righ ts reserved.

ni, dOO\lIDRt:wa. ')'P•••~whllan IMACJSN_

1/300 L•••r Prin'.r.

The Bernoulli Box is a registered trademark of IOmega Corporation.
Compaq Deskpro and Plus are trademarks of Compaq COPlputer
Corporation.
COREtape is a trademark of CORE International.
mM PC XT and PC AT are registered trademarks of International Business
Corporation.
lMA GEN is a registered trademark ofIMA GEN Corporation.
MS-DOS is a registered trademark of Microsoft
QuadPort is a trademark of Quadram.
PC'; LIMITED AT is a trademark of PC LI~TED.
UNISYS is a registered trademark of the UNISYS Corporation.
TecJl1aris a trademark ofTecm3j, Inc.
UNISYS is a trademark of UNISYS Corporation. XENIX is a registered
trademark of Microsoft Corporation.
Document Number: XG-03-23-87 -3.0/2.2.1
Part Number: 018-030-016
ProcessedDate: MonApr 613:21:35PDT1987

XENIX System V 2.2.1
Operating System Release Notes

1. Preface

1.1 Contents of the Distribution
1.2 Packages In This Set

1.3 SVID Confonnance Notes

2. Important Notes About Installation

2.1 Memory Requirements 8
2.1.1 vi(C) and vsh(C) 8
2.1.2 Display Adapters 8
2.2 Adding a 2.1 Hard Disk to 2.2

2.3 Installing tenninfo( C) 10
2.4 New Id(CP) Program 10
2.5 Installing on a Serial Console 10
2.6 Include Files and Utilities 11
2.7 Games Support 11
2.8 Restoring Lost Files 11
3. Software Notes 12
3.1 shl(C) Notes 12
3.2 Slow Printing 12

-i -

3.3 Keyboard Lock -up 13
3.4 Large Model restor 15
3.5 Software Reboot 15
3.6 Dos/XENIXCoexistence 16
3.7 dtype(C) 16
3.8 UsingXENIX-NET 16
3.9 mapchan(M) and mapscrn(M)

3.10 ULIMIT 17
3.11 NOFILE - Number of Open Files 17
3.12 setkey(C) 18
3.13 shutdown(C) and Shell Layers 18
3.14 Irwin Tape Drive Notes 18
3.15 Tape Support For 8086 Machines 19
3.16 sysadmin(C)

3.17 Buffer Overflow 19
3.18 Display Adapter Note 20
3.19 Creating Boot and Root Floppies 20
3.20 crypt(C) 20
3.21 csh(C) - sh(C) Conflicts 20

3.22/dev/tty[II,12,13,14] 20
3.23 Additional Multiscreens - ttyll, tty12 21

- ii -

3.24 screen(HW) - Control Modes 21
3.25 !etc!init 22
3.26 fonnat(C) and DOS 22
3.27 Using Raw Devices 22
3.28 uname(S) 23
3.29 uucp(C) and cu(C) Notes 23
3.29.1 Autodialing' 24
3.29.2 Communications with 3.0 XENIX Systems 24
3.29.3 L-devicesandL.sys 24
3.29.4 Modem Usage under XENIX 24
3.29.5 Restriction in the USERFILE 25
3.29.6 uuinstall(C) 25
3.30 vsh( C) 25
3.31 ClockrateAdjustment 25
3.32 IMAGEN printers - ips(M) 26
4. Documentation Notes 26
4.1 Updated Documentation 26
4.2 Operations Guide - Chapter 6 27
4.2.1 Creating Backups 27
4.2.2 Getting a Backup Listing 28
4.2.3 Restoring Backup Files 28
4.2.4 Restoring an Entire Filesystem 30
4.2.5 Editing!etc!default/filesys and!etc!default!archive 31
4.3 Operations Guide- Chapter 7 32
4.3.1 Section 7.3- Using a Cartridge Tape Drive 32
4.3.2 Installation and Configuration 33
4.3.3 AccessingtheDrive 33
4.3.4 The tar Command 33
4.3.5 letc!defaultEntries 34

-ili-

4.3.6 The Irwin Tape Drive 34
4.3.7 Section 7.12.1-lpinit 36
4.4 User's Guide - Chapter 6 36
4.4.1 Section6.5.3-"CreatetheL.sysFile" 36
4.5 tennio(M) and stty(C) 37
4.6 fsname(M) 37
4.7 Shell Enhancements 37
4.7.1 DefiningFunctions 38
4.8 dos(C) - dosformat 38
4.9 enable(C) and disable(C) 39
4.10 format(C)

4.11 fsck(C) 39
4.12 haltsys(C) 39
4.13 mkuser(C) 40
4.14 mount(C) and mnt 40
4.15 default(M) -/etc/default/archive 40
4.16Iogin(M) 40
4.17 tenncap(M) 40
- 5. Compatible Hardware 41
5.1 General Compatibility Guidelines 41
5.1.1 Machines 42
5.1.2 MathChips 43
5.1.3 Memory Cards 43
5.1.4 Multi-Function Cards 43
5.1.5 Serial 110 Boards 44

- iv -

8250a Serial JJO Chip Notes 44
Serial Card Addresses and Notes 45
5.1.6 Tape Drive/Controller Combinations 50
5.1. 7 Video Adapters and Monitors 50
5.1.8 Add-On Hard Disks 51
5.1.9 Compatible Hard Disk Controllers 52
5.1.10 Modems and Autodialing 52
5.2 XENIX-86XT 53
5.2.1 Machines 53'
5.2.2 Math Chips 53
5.2.3 MemoryCards 54
5.2.4 Accelerator Boards 54
5.2.5 Add-OnHardDisks 54
5.2.6 Compatible Hard Disk Controllers 56
5.3 XENIX -6300+ 56
5.3.1 Memory Cards 56
5.3.2 Hard Disks 57
5.4 XENIX-286AT 58
5.4.1 Machines 58
5.4.2 MathChips 59
5.4.3 Memory Cards 60
5.4.4 Add-OnHardDisks 60
5.4.5 Compatible Hard Disk Controllers 61
5.5 XENIX-286HP 61
5.5.1 Machines 61
5.5.2 MemoryCards 62
5.5.3 Serial JJOboards 62
5.5.4 VideoCardsandMonitors 62
5.5.5 OtherHPHardware 62
5.5.6 Compatible Hard Disk Controllers 63
5.5.7 Add-OnHardDisks 64
5.6 XENIX-386AT 67
5.6.1 Machines 67
5.6.2 MemoryCards 67
5.6.3 Add-OnHardDisks 67
5.6.4 Serial Cards 67

-v-

5.6.5 Compatible Hard Disk Controllers 67
6. Common Installation/Configuration Questions and Answers 68

- vi -

Release Notes
Release 2.2.1
XENIX System V for Personal Computers
Operating System
March 23, 1987

1. Preface
This document contains important information about System V
Release 2.2 Operating System for Personal Computers:
•

Installation Notes

•

Software Notes

•

Documentation Notes

•

Compatible Hardware

•

Common Questions and Answers

Note
Please read through this entire document before installing
the XENIX operating system.

We are always pleased to hear of users' experiences with our product,
and recommendations of how it can be made even more useful. All
written suggestions are given serious consideration.

XG-03-23-87 -3.0/2.2.1

- 1 - The Santa Cruz Operation

XENIX

for Personal Computers

1.1 Contents of the Distribution
The XENIX System V 2.2 Operating System is distributed on the
following 96tpi floppies:
Volumes Nl-N2
Volumes Bl
Volumes XI-X3
Games (Optional) - Volume 1
A 3.5" distribution will also be available. Contact your sales! support
center.
The XENIX System V 2.2 Operating System is also available on the
following 48tpi floppies for 8086XT and 286AT machines:
Volumes NI-N7
Volumes BI-B3
Volumes XI-XIO
Games (Optional) - Volume 1
The software is grouped into packages that are listed in the next
section, "Packages In This Set" .

1.2 Packages In This Set
The XENIX software is grouped into packages. This makes
customizing your system easier, since you can use the custom(C)
utility to add or delete groups of programs that have related
functions.
For example, if you do not want to use your system for
communications, you would not install the UUCP package. If you
install a package, then change your mind later, use custom to remove
that package. custom can locate all the files that belong in a certain
package and delete them, thus removing the package.
These are the packages in the Operating System:
Operating System Packages
ALL
LINK

Entire operating system set
The Link Kit

XG-03-23-87-3.0!2.2.1

- 2 - The Santa Cruz Operation

Operating System Release Notes

PERM
RTS
BASE
BACKUP
SYSADM
FILE
LPR
IM:AGEN
MAIL
CSH
DOS
VSH

EX
UUCP
INITTAB
MAPCHAN
TERMINF

XENIX contents and permissions lists
XENIX run time system
Basic extended utility set
System backup and recovery tools
System administration tools
File manipulation tools
Multiple line printer spoo ler
IM:AGEN laser printer support
Electronic mail and local area networking
TheC-shell
DOS utilities
The visual shell
The ex and vi editors
uucp and cu communications utilities
Terminal initialization
International character set mapping
Terminfo database

1.3 SVID Conformance Notes
XENIXmeets the System V Interface Definition (SVID) published in
1985 by AT&T (Select Code 307-127). XENIX System V has been
subjected to a stringent set of tests for the purpose of verifying
conformance to SVID. seo XENIX System V conforms to SVID
functionality with the following exceptions:

XG-03-23-87-3.0/2.2.1

- 3 - The Santa Cruz Operation

XENIX for Personal Computers

SVID
Specification

SCQXENIX
Implementation

shmat

Allows non-zero
arguments.

shmaddr argument must be zero.
The SVID states that shmatO
should allow a non-zero
shmaddrargument. llle
segmented architecture of the 86
family precludes allowing
attachment of shared memory at
specific physical addresses.
Because of this, SCQ XENIX
requires that the shmaddr
argument be zero to allow the
system to choose the first
available address.

shmop
shmctl
shmget

Shared memory
operations.
Return "char
*shmaddr"

Because of the architecture of
the 86 family of chips, SCQ
XENIX chose to implement
shared memory by using far
pointers. The SVID "char
*shmaddr" is replaced with
"char far *shmaddr." lllis is for
the same reason as listed for
shnult above.

ptrace

Address
specified as
(int*).

Address specified as structure.
The SVID states that ptraceO
calls should fail if the 'addr'
argwnent is not the start address
of a word. Because of word
alignment conventions in the 86
family of chips this failure will
not occur.

Function

XG-03-23-87-3.0/2.2.1

- 4 - The Santa Cruz Operation

Operating System Release Notes
These exceptions are found on the tennio manual pages
(termio( dev) for SVID and termio(M) for XENIX):
Termio
Characters/values
QUIT
ERASE
KILL
38400 baud
initial
default
baud rate

SVID
Soecification
Ctrl-I
#
@

B38400
B300

SCOXENIXV
Implementation
Ctrl-\
Ctrl-H
Ctrl-U
not included
B9600

2. Important Notes About Installation
Please refer to the Installation Guide in the binder marked "XENIX
Operating System Run Time Environment" to install the XENIX
Operating System. Chapter 2, "Installation Procedure," describes
the actual installation steps.
This installation is not an upgrade, and it will overwrite the present
contents of the hard disk in drive O. If you have an earlier version of
XENIX, contact your sales/support center for infonnation on
obtaining and upgrade.
You can continue to use a pre-2.2 XENIX file system on another hard
disk by following the instructions in the section "Adding a 2.1 Hard
Disk to 2.2" later in these Release Notes.
If you have all three systems, (the XENIX Operating System,

Development System and Text Processing System) you can use the
XENIX Installation Guide to install them all at once. If you wish to
install the Development System and/or the Text Processing System
at a later time, refer to the Release Notes at the beginning of the
appropriate guide (XENIX Programmer's Guide Volume lor XENIX
Text ProceSsing Guide). See also the manual page for custom(C).
With custom you can install all or portions of the XENIX System.
Read the Release Notes and Installation Guide in their entirety and
make sure you completely understand the installation process before
installing the product.

XG-03-23-87-3.0/2.2.1

- 5 - The Santa Cruz Operation

XENIX for Personal Computers
There are some specific points to be aware of before you start:
•

Do not abort the installation process, for example, by using
the DEL or Ctrl-\ keys. H you need to stop because you
enter incorrect information or for some other reason, start
the process again from the beginning rather than trying to
proceed from the stopping point.

•

Users upgrading their XENIX 3.0 system to XENIX System V
should refer to Appendix A "Upgrading Your System" in
the XENIX Installation Guide. Users installing XENIX for
the first time can ignore that appendix.

•

XENIX must boot from the physical drive 0 (hard disk or
diskette). Keep this in mind when planning for extra
hardware.

•

XENIX installs with a minimum of screen prompts and
typing, and is set up with ample defaults for most uses and
sites. However, you can customize the operating system
during installation to meet a wide variety of needs.
If you know that you need to customize your installation, go
over this next list and decide if any of the items apply to you.
If they do, read any suggested sections and make sure you
understand the procedures involved before installing
XENIX:

Install all or only parts of the operating system.
This is described during the installation process,
but the section of these Notes "Packages In The
Distribution" can help you decide what software
you need, and what software you may not need.
Create additional filesystems, besides the root.
This is also described in Chapter 2 of the
Installation Guide "Installation Procedure."
Add a second hard disk which came from a 2.1
system.

){(J-03-23-87-3.0/2.2.1

- 6 - The Santa Cruz Operation

Operating System Release Notes

You can continue to use the filesystems on a
second hard disk that you created in XENIX 2.1 or
later.
Do not install XENIX 2.2 right away. Instead, you
should read the subsequent section of these
Release Notes "Adding a 2.1 Hard Disk to 2.2"
before installing XENIX.
If you intend to use 2.1 filesystems on drive 0 after
installing 2.2, you must obtain the 2.1 to 2.2
upgrade from your sales/support center. The
XENIX 2.2 installation will replace a 2.1
installation on drive o.

Set up your hard disk to accommodate other
operating systems, such as DOS.
This is discussed in Chapter 2 and Chapter 3 of the
Installation Guide, "Installation Procedure" and
"Using DOS and XENIX on the Same Disk."
As before, most users and sites do not need to extensively
customize their installations since the "defaults satisfY most
requirements. If you need to customize your installation,
though, make sure you have a clear idea of what you want
before you start the actual installation process.
•

If you plan to use DOS and XENIX on the same hard disk,
install DOS first, then install XENIX. This is not required by
XENIX but by some versions of DOS.

XG-03-23-87-3.0/2.2.1

- 7 - The Santa Cruz Operation

XENIX for Personal Computers

2.1 Memory Requirements
Please use the following table to determine the amount of memory
you need to run XENIX:
System
Ope,rating System

Development System

Requirements
minimum: 512K
recommended: 640K
or more
multiuser: 1MB2MB, or more for
optimum performance
minimum: 640K
recommended: 1MB

When you invoke a utility that needs more memory than is available,
the message "Killed" or "too big" displays on your screen.
2.1.1 vl(C) and vsh(C)

vi(C) and vsh(C) are not supported for machines with only 512
Kilobytes(K) of main memory. H you have only 512K of main
memory installed, use of any medium model program may severely
impair system performance.
2.1.2 Display Adapters

H you have two display adapters on a machine running with less than
640K of RAM, you see the following message at boot time:
Insufficient memory for second display adapter
The second adapter is not used by XENIX.

2.2 Adding a 2.1 Hard Disk to 2.2
Follow these steps to add an existing 2.1 hard disk to your 2.2 system:

XG-03-23-87-3.0/2.2.1

- 8 - The Santa Cruz Operation

Operating System Release Notes

•

Enter single user mode.

•

Use the fixpenn utility to create the necessary device nodes:

cd I
fixperm -c -dHDl letc/inst.perms
If you do not know what fdlsk partitions you have your
XENIX file systems in, run fdisk:

fdisk - f I devIrhdlO
Enter "1" at the main fdisk menu to display the partition
table. Write down the numbers of the partitions that
contain XENIX, then exit from fdisk.
•

Invoke divvy with the following command line:
divvy -b 1 -c 1 -p 1 '-v partition-number
In the above command line, substitute the actual partition
numbers that you copied from the fdisk table. Follow this
divvy procedure for all of the possible fdisk partitions.
Examine your divvy table. You should see a list of divvy
divisions, which may contain valid filesystems, that do not
have names. Only the divvy division number and sizes are
displayed.,
Next, create names for all the divisions you want to
preserve. You can call them anything you want, such as u,
user2, etc.
When you have named all of the potential divvy divisions,
enter "q" to quit from divvy, thenUi" to install the partition
table.

•

When you have named all of the likely candidates in all the
possible fdisk partitions, mount each of the file systems in
tum. For example, to mount a filesystem named lu, enter:
mount Idev/u Imnt
If the divvy partition was not valid, the mount command
should refuse to mount the filesystem. If the file system
mounts, change directories to it and examine it.

XG-03-23-87-3.0/2.2.1

- 9 _I The Santa Cruz Operation

XENIX for Personal Computers
If it is not the filesystem you want to preserve, unmount it,
remove it from Idev, and try another filesystem.

Do this until you find the file system you want to preserve.
Use this command for each filesystem you want to preserve:
mkdev fs I devldevicename Idirectory
In the above command, substitute the name of the actual
device and the mount directory. For example:

mkdev fs I devlu lu

2.3 Installing terminro (C)
If you choose to install tenninfo, which is in the TERMINF package,
you see some messages that describe the installation process. These
messages are normal and can be ignored.

2.4 New Id (CP) Program
If you intend to use the XENIX 2.1 Development System with the
XENIX 2.2 Operating System, you should install the new version of
Id(CP) that is shipped with the 2.2 Operating System. Install the new
Id program after you reinstall the 2.1 Development System.

Id is in the Link Kit package LINK, so you can use custom(C) to
extract just that file from the package. See custom(C) for
information on installing a single file from a package.

2.5 Installing on a Serial Console
If you are installing XENIX on a system that does not have a video
display adapter, and you are using a serial console, you will see this
message:

No display adapter present
This is a normal part of the installation.

}{(}-03-23-87-3.0/2.2.1

- 10 - The Santa Cruz Operation

Operating System Release Notes

2.6 Include Files and Utilities
Machine dependent Development System include files and utilities
are included on the 2.2 Operating System N Volumes. If you do not
install the Link Kit and the Development System set, you may not be
prompted to extract any files off some of the N volumes.

2.7 Games Support
Games are supplied, as is, for your pleasure and enjoyment. They
are not supported. On line documentation is supplied for some of
the games in the directory /usr/games/doc. Use custom(C) to install
the Games floppy:
1.

Enter custom.

Select the option to "Add a Supported Product."

Insert Games Volume 1 when prompted, then follow the
screen prompts as they appear.

Refer to the custom(C) manual page in the XENIX Reference for
more information on installing all or parts of a package.

2.8 Restoring Lost Files
If you accidentally erase one or more of the files included with the
distribution after you have installed XENIX, you can use custom(C)
to restore the file, or files. The custom(C) utility can list, install, or
remove individual files, sets within the XENIX System packages, or
entire packages of the XENIX System.

Refer to custom(C) in the XENIX Reference for information on using
custom. You cannot use custom to restore any special modifications
you made to a file between the time when you first installed it and the
time when the file is lost.

XG-03-23-87-3.0/2.2.1

- 11 - The Santa Cruz Operation

XENIX for Personal Computers

3. Software Notes
This section discusses special notes about the XENIX software.

3.1 shl(C) Notes
H you have problems with shell layers, sbl(C), on some terminals,
but not on others, or sbl works on yout console, but not on another
terminal, you may have to set istrip for that terminal line:
stty istrip
XENIX 2.2 is initially configured for one shell layer session at a time.
You can use mkdev sbl to change this single session limit. The script
will prompt for the number of sessions desired and will relink the
kernel. The new limits will become effective after rebooting, as the
script will instruct.

3.2 Slow Prin ting
If you have a parallel printer that is printing abnormally slowly, the
parallel port hardware may be missing interrupts. A solution is to
alter the way that the hardware and the printer driver communicate.
The parallel printer driver can be made to "poll" a parallel port,
which does not rely on interrupts from the parallel port, but may
cause an increased drain on system resources.

To set up polling for a parallel port/parallel printer, you must create
what is known as a "special device node." Login as root (super-user)
and enter one of the following sets of commands.
ForlpO:
mknod / dev/lpOp c 6 64
chown bin /dev/lpOp
chgrp bin / dev/lpOp
chmod 222 / dev/lpOp
Forlp1:

}{(J-03-23-87-3.0/2.2.1

- 12 - The Santa Cruz Operation

Operating System Release Notes

mknod Idev/lplp c 665
chown bin Idev/lp1p
chgrp bin Idev/lp1p
chmod 222/dev/lp1p
Forlp2:
mknod Idev/lp2p c 666
chown bin Idev/lp2p
chgrp bin Idev/lp2p
chmod 222 I deyIlp2p

H you are using the print spooler you should now run mkdev Ip to
inform the spooler ofthe new parallel poll device. You can choose to
add a new printer or re-configure an existing printer. When you are
asked to choose a device for the printer, do not use the standard
parallel devices that are displayed. Instead, use: "/dev/lpOp",
"/dev/lp1p", or "/dev/lp2p".

3.3 Keyboard Lock- up
A small number of systems experience a problem known as
"keyboard lockup," where the system does not respond to keyboard
input from the console keyboard. This particular condition only
affects keyboards that are attached to the video display adapter, not
standard terminals that are attached to serial lines.
Your keyboard may be "locked up" if:
•

The system console keyboard cannot be used to enter data
or perform any tasks

•

You cannot flip Multiscreens and the CAPS LOCK key
does not tum the caps lock light on or off

•

Other terminals on the system continue to work

•

Printers or other devices continue to work

•

The system is still running.

Keyboard lockup is similar to other circumstances, so before trying
to fix a "locked" keyboard, make sure that:

){(J-03-23-87-3.0/2.2.1

- 13 - The Santa Cruz Operation

XENIX for Personal Computers

•

You did not accidentally enter Ctrl-S

•

The "Keyboard Lock" key is not in the lock position

•

The keyboard is still plugged in

•

The system itself is still running.

First, make sure you did not enter Ctrl-S accidentally. Press Ctrl-Q
several times and check to see if you can enter characters on the
screen. Press RETURN a few times, or enter DEL.
Next, check the Keyboard Lock key, if your computer has one. It
should be turned to the "unlocked" position. Also, make sure the
keyboard is still plugged in to the correct socket.
Make sure the system is still running. Check another terminal to see
if it is still working and that you can perform system tasks, such as
logging in and checking the date. If you do not have another
terminal, watch the hard disk access light, if your computer has one.
If it flashes periodically, at least once every thirty seconds or so, the
system is still running and is using the hard disk. Note that you
cannot use other terminals and that the hard disk access light may not
flash if you are in single user mode.
If you check all of the suggestions, but you still cannot use your
console keyboard, try unplugging the console keyboard then
plugging it in again. If this fixes the problem, it is definitely a case of
keyboard lockup. If this last step does not fix the problem, you may
still have keyboard lockup.

You can prevent keyboard lockup with the following fix. Note that it
disables the keyboard lights (LEDs), so you should do this only if you
have tried all other approaches:
1.

Get the system console working, if it is not. Reboot the
system if you have to, and bring it up to single-user mode.

If you didn't reboot, log in as root on the system console and
sh~t the system down to single user mode with shutdown (C):

# I etcl shutdown su
See shutdown(C) in the XENIX "Reference" for more
information.

XG-03-23-87 -3.0/2.2.1

- 14 - The Santa Cruz Operation

Operating System Release Notes
3.

Once the system is in single user mode, back up the kernel:
#cd/
# mv xenix xenix.OO
# cp xenix.OO xenix

Enter this command:

# adbL -w /xenix
ledspresent/w 0
$q

This patches your kernel with the necessary fix. Again, note
that it permanently disables the console keyboard lights
(LEDs).

Shut the system down:
# / etc/ shutdown 0

When you see the "Normal System Shutdown" message,
press any key to reboot the system. You have now fixed the
keyboard lockup problem.

3.4 Large Model restor
A large model version of restor(C), restorL, is now included as part
of the BACKUP package. This allows the use of the X key option of
the restor command, which enables operations on large directory
trees without running out of memory. This utility is not supported on
8086 machines.

3.5 Software Reboot
XENIX System V 2.2 allows software rebooting, so you do not need
to power off to reboot. The following message is displayed after a
system shutdown:
** SafetoPowerOff**
-or** Hit Any Key to Reboot **

}(J-03-23-87-3.0/2.2.1

- 15 - The Santa Cruz Operation

XENIX for Personal Computers

FIXed disk heads are "parked" (locked) when this message is
displayed.
A new command, reboot, causes the system to automatically reboot
after shutting down, without waiting for any keyboard input.

Note
When the floppy drive door is closed, the computer
attempts to boot from a floppy. The floppy drive door
must be open to boot off the hard disk.

3.6 DOS/XENIX Coexistence
XENIX supports the coexistence of MSTM-DOS and XENIX on the
same hard disk. Some versions of DOS have restrictions, for
example, ITT DOS releases previous to 3.10 cannot share the disk
with XENIX or MS-DOS. For these releases, XENIX, or a
combination of XENIX and MS-DOS must occupy the whole disk.

In addition, an ITT MS-DOS+ release 3.20 hard disk partition that is

32 Mbytes or larger should not be made active. Activating this
partition will corrupt the MS-DOS+ ending cylinder. XENIX dos(C)
commands may not work when accessing an ITT MS-DO S+ release
3.20 hard disk partition that is 32 Mbytes or larger.
Whenever you use DOS and XENIX on the same disk, if in doubt,
install DOS first, then install XENIX.

3.7 dtype (C)
The dtype(C) utility reports incorrect file system versions (e.g.,
System3.xversus System V).

3.8 Using XENIX-NET
You cannot use versions of XENIX-NET previous to 1.1.1 with the

){(7-03-23-87-3.0/2.2.1

- 16 - The Santa Cruz Operation

Operating System Release Notes
XENIX 2.2 Operating System.

3.9 mapchan(M) and mapscm(M)
Using 7-bit terminals with mapchan mapping, where the '[' (left
bracket) character is mapped to some other character, can cause
escape sequence processing by tenncap, and other applications to
fail. H you must map the '[' character, termcap entries (and
applications programs) can be modified to look for the mapped value
instead of '[' .
The function of the mapscm(M) utility has been superceded in
XENIX 2.2 by mapchan, and we do not recommend using mapscm.
Use mapcban instead, since it performs the same functions as
mapscm, plus several additional functions. mapscm is included for
backwards compatibility, but is implemented through the mapchan
scheme.
All mapping is now done through the tty disciplines. With mapchan
you can map tty input, output, and use dead and compose keys.
Formerly, under mapscm, you could only map tty output for the
computer display attached to the video display adapter.
The mapscm utility now constructs a mapchan table for tty output
mapping only, and creates defaults for the input, compose and dead
key tables. Thus, if you create mapping tables with mapchan, then
modify tty output with mapscm, mapscm overwrites the mapchan
tables with new ones, using system defaults for tty input, and dead
and compose key mapping.
See mapcban(C) in the XENIX Reference for more information on
channel mapping.

3.10 ULIMIT
The default ULIMIT has been raised for XENIX 2.2. It is now
2,097,152 blocks (1 gigabyte).

3.11 NOFILE - Number of Open Files
The 2.2 kernel allows up to 60 open files per user, rather than the

XG-03-23-87-3.0/2.2.1

- 17 - The Santa Cruz Operation

XENIX for Personal Computers
previous limit of 20 open files. Note that this increase is in the kernel
limit only, and that standard I/O routines other than those in the
XENIX 2.2 Development System have the previous limit. The
open(S) system call does not have this limit, since it depends only on
the kernel.
You may have to reconfigure your kernel to increase certain
parameters if you use programs that take advantage of this increased
limit. For example, you may have to increase NINODES to raise the
limit to the number of inodes open on the system at one time. See
configure (C).
Use the Link Kit to raise any required limits. See Chapter 4 of the
Installation Guide, "Using The Link Kit."

3.12 setkey(C)
Assigning more than 512 characters to function keys fills the allotted
string key buffer. The sequences sent by the arrow keys are
overwritten, and the arrow keys do not work, most recognizably in
vi(C).

3.13 shutdown (C) and Shell Layers
shutdown(C) does not work if ps and who am I do not report the
same tty name, for example from within sheUlayers (shl(C». Do
not run shutdown(C) from within shell layers.

3.14 Irwin Tape Drive Notes
tape (C) utility does not yet work with the Irwin (ctmini) device.
Refer to Section 4.3.6 for instructions on how to use the Irwin tape
cartridge drive.
When using an Irwin mini-cartridge tape drive to write large amounts
of data, you may see this error message after the last file has been
written on the tape:
Tape uncorrectable ECC error
If this occurs after the last file has been written, the message is

XG-03-23-87-3.0/2.2.1

- 18 - The Santa Cruz Operation

Operating System Release Notes

erroneous and can be ignored. You can check to make sure the last
file was successfully written to tape.
If you see this message in the middle of writing, it is probable a valid
error message. Try to read the data off of the tape to make sure the
error is valid, and if it is, you should reformat the tape with the
fonnat(C) command. Specify the -e option. See fonnat(C) for
information on formatting tapes.

3.1S Tape Support For 8086 Machines
In this release of XENIX there is no tape support for 8086 machines.

3.16 sysadmin (C)
sysadmin(C) now has a selection for 3 1/2 inch floppies. However,
only drives 0 and 1 are supported in this release. Note that some 3112
inch drives are configured as drive 2.

3.17 Buffer Overflow
The XENIX kernel read buffers hold up to 256 characters. Overflow
of a buffer causes it to be flushed and the 257th character is not
echoed. If this 257th character is dropped during the output of an
escape sequence, the output of that sequence is other than expected.
For example, if a function key is programmed to send ""[154g" and
the function key is held down so that the output of this string on the
screen repeats, the 257th string character, "4", is dropped and the
string interpreted would instead be ""[15g" that one time.
If setkey(C) is used to assign more than 512 characters to function
key strings, the character buffer limit in the function key buffer is
overflowed. The arrow keys are the first to stop working. To reduce
unnecessary character assignments, remove the characters within
quotes in the file /usrllib/keyboard/strings. Use the mapstr utility
(see mapkey(M» to make the string changes.

}{(J-03-23-87-3.0/2.2.1

- 19 - The Santa Cruz Operation

XENIX

for Personal Computers

3.18 Display Adapter Note
CMOS location Ox2d is read at boot time to initialize the display
adapter. H that register is non zero, the adapter may be initialized
differently than would normally be expected.

3.19 Creating Boot and Root Floppies
You can now create boot and root floppies with the mkdev(C) utility.
To do this, use the following command:
mkdev fd
You can create bootable or root file system floppies with 48tpi drives.
With 96tpi drives, you can create combined boot/root floppies.

3.20 crypt(C)
The crypt(C) command has been removed from XENIX System V. H
you want the crypt(C) utility and associated crypt(S) libraries, and
you live in the United States, contact the support center listed on the
support information card included with the software.

3.21 csh (C) - sh (C) Conflicts
The C-shell, csh(C), has many built-in commands with the same
name and functionality, but different syntax, than those used by the
sh(C) shell. The sh(C) commands are those documented in the
XENIX Reference. An example of two commands that exhibit this
behavior are echo and nice. Refer to the manual page csh(C) for
information on built-in C-shell commands.

An letclcshrc file is included with this release. You can customize the
C-shell environment for all csh(C) users by using this file, which is
similar to letclprojilefor sh(C) users.

3.22 Idev/tty[11,12,13,14]
Serial lines Idevltty11, Idevltty12, Idevltty13, and Idevltty14 are no

){Ci-03-23-87-3.0/2.2.1

- 20 - The Santa Cruz Operation

Operating System Release Notes
longer linked to the serial IJO devices IdevlttyJa, IdevlttylA,
Idevllty2a and Idevltty2A , respectively. These links were maintained
for backwards compatibility with uucp(C) and shell scripts. Please
note that if you use older versions of UlICp(C), you may have to alter
certain files because of this change.
Idevllty11 and IdevlttyJ2 are now multiscreens. The next section
describes these new multiscreens.

3.23 Additional Multiscreens - ttytt, ttyt2
The maximum number of multiscreens has been increased to twelve.
If your system has enough memory, it is automatically configured for
up to twelve multiscreens. You can also reconfigure the system with
the Link Kit as described in Chapter 4 of the XENIX Installation
Guide, "Using The Link Kit."
You can use these new multiscreens just like the other ten if your
keyboard has the additional function keys Fll and F12, and they are
compatible with the standard enhanced keyboard Fll and F12. If
you have fewer function keys than the number of multiscreens
enabled, or a "non-compatible" keyboard, you can access the other
screens by stepping past the last multi screen with Ctrl-PrtScr.
For example, if your keyboard has ten function keys, but you have
twelve multiscreens enabled, you can access the eleventh and twelfth
screens by first going to the tenth screen, by pressing AIt-FI0, then
pressing Ctrl-PrtScr to step to the eleventh screen. H you press CtrlPrtScr again, you can access the twelfth screen, and if you press it
once more, you are back to the first screen.
~~re~~~~

m~sc~min~~

muItiscreen(M) in the XENIXRejerence .

3.24 screen(HW) - Control Modes
This note is primarily for software developers.
The screen(HW) manual page for XENIX 2.2 lists the following
commands under "Control Modes":

XG-03-23-87 -3.0/2.2.1

- 21- The Santa Cruz Operation

XENIX for Personal Computers

SWAPMONO
SWAPCGA
SWAPPGA
SWAPEGA
In the current release, these ioctl commands behave just as if a
"change multiscreen" sequence were issued. For compatibility, we
recommend that you do not use the commands listed above and that
programs should swap to other adapter types by opening the devices
associated with the desired adapter.

For example, if a program, that is started on a multiscreen associated
with a monochrome adapter, is to display output on an installed
CGA, the program should open Idevlcolor and use the mode
changing and selector mapping ioctl s on the resulting file descriptor.
This maintains greater compatibility.

3.25 letclinit
1etclini! can only be executed by the kernel as process 1. It cannot be
run from the shell prompt.
For information on changing init states, see the new manual page
teUnit(C). This page is distributed in the set of updated
documentation, and should be placed in the XENIXReference.

3.26 fonnat(C) and DOS
The fonnat(C) command is a low-level formatter for XENIX, and
does not format floppies for use under DOS. To format DOS
floppies, use the dosfonnat command. See dos(C) in the XENIX
Reference.
Error-free floppies are required for XENIX.

3.27 Using Raw Devices
When using dd(C) or tar(C) with a raw device, specify the block size
as a multiple of 1K, which is equivalent to 2 "b." This is
recommended because dd (C) and tar(C) use 512 byte blocks. The
XENIX filesystem uses 1024 byte blocks. For example, for dd (C)

XG-03-23-87 -3.0/2.2.1

- 22 - The Santa Cruz Operation

Operating System Release Notes
using a 9K (system) block size use:
dd if=file of=/dev/rfdO bs==18b
Specify an even blocking factor with tar(C):
tar cvfb Idev/rfdO 18 file
or use the default tar settings (see tar( C».

3.28 uname(S)
No XENIX utilities currently use the node name in the uname
structure. XENIX utilities use the entry in letclsystemid. However,
some sites may want to set the node name in the uname structure.
The node name can be up to 9 characters long. You can set the node
name by using the Link Kit to relink a new XENIX kernel. Refer to
Chapter 4 of the XENIX Installation Guide "Using the Link Kit" .
To create the node entry in the uname structure, first install the Link
Kit with custom(C), then:

# cd lusrlsys/conf
# .1configure

select "System Name"
enter name
# ./linlLxenix
# mv xenix Ixenix.new
reboot specifying xenix .new
# uname-a
verify node name appears as desired
# mv Ixenix.new Ixenix
reboot as usual

3.29 uucp(C) and cu(C) Notes
This section answers questions you may have about uucp(C) and
cu(C). The installation of the uucp programs and utilities is
optional. Refer to the chapter "Building a Micnet Network" in the
XENIX Operations Guide and the chapter on "Building a
Communications System" in the XENIX User's Guide. Also refer to
custom(C) to install (or remove) communications files.

XG-03-23-87-3.0/2.2.1

- 23 - The Santa Cruz Operation

XENlX for Personal Computers

3.29.1 AutodlaUnll

In addition to the program on the dial(M) manual page,
/usr/lib/uucp/dial.c, the C language program for the distributed
/usr/lib/uucp/dial is included in this release. You can copy and
modify dial.c or you can use this as an example to write programs to
use other kinds of modems. The makefile distributed in
/usr/lib/uucp should be modified to reflect your own dialer program.
You must have the XENIX Development System in order to compile
C programs. dial programs cannot be shell scripts.

If you create a dial program for another modem, please send us the
source. User-written dial programs will be considered for inclusion
in future releases.
3.29.2 Communlcadons with 3.0 XENIX Systems

If you have trouble connecting to a computer running XENIX System
3.0 with uucp(C), try making that system "active" and the computer
running XENIX System V the "slave" .
3.29.3 L-devlces and L.sys

We recommend running uucp(C) direct connections at 2400 or 4800
baud so that the system's performance is not impaired. These baud
rates are specified in the files lusrllib/uucp/L-devices and
/usr/lib/uucp/L.sys. This can be done by specifying the dialer
program instead of the call unit device features.
Do not use tabs as field separators in the L.sys file.
3.29.4 Modem Usalle under XENIX

Refer to the XENIX Operations Guide chapter "Using Peripheral
Devices" for information on modem settings, modem control,
aliasing alphabetic characters and dialing with your computer.

XG-03-23-87-3.0/2.2.1

- 24 - The Santa Cruz Operation

Operating System Release Notes

3.29.5 Restrldlon in the USER FILE

USERFll..ES used in this release must start with the line:
uucp, /
followed by at least one other line.
Because the uucp login can be accessed by many users, some of
whom may be undesirable, you should not use "uucp " as the uucp
account. To ensure proper security, create a different account with
uucico as its login shell. Many systems use the uumachineJtame
convention as the user login, where machineJtame represents the
system's machine name.
3.29.6 uuinstaU(C)

uuinstaU(C) may not allow certain features such as variable baud rate
to be configured. Note that the L.sys and L- devices files may have to
be edited with a text editor to use new features.

3.30 vsh(C)
The visual shell, vsb(C), does not currently support the use of special
characters when specifying file names. The use of these special
characters (* , [, ], and ?) is explained in the chapter "Basic
Concepts" in the Introduction to XENIX •
vsb(C) resets the swtcb character. It is not possible to switch from
the session manager, sbl(C) , while runningvsb. However, switching
from vi(C) or sysadmsb(C) works.

3.31 Clockrate Adjustment
If you have an AT&T 6300 or an Olivetti M24 you may need to reset

your clockrate, since these computers operate at a different
frequency than the default setting.
You can check the accuracy of your clock rate using the date(C)
command over a period of days. If the system clock gains or loses
time excessively, refer to the manual page clockrate(HW) for

XG-03-23-87-3.0/2.2.1

- 25 - The Santa Cruz Operation

XENIX for Personal Computers
information on setting the clock rate.
The correct clock rate for an AT&T 6300 or an Olivetti M24 is
1.22878.

3.32 IMAGEN printers - ips (M)
When .using an IMAGEN printer in parallel printer mode (using
Ipbs, see ips(M» you must specify the quote character as hex 2 (Ox02
or control-b) and the EOF character as hex 4 (Ox04 or control-d).
Control characters must be "taken as is". Refer to the IMAGEN
system manuals provided with the printer, for information on
specifying these characters in the printer configuration.

4. Documentation Notes
In order to make the documentation as complete as possible, this
section describes errors in the documentation as well as some new
features ofXENIX2.2 that are not documented elsewhere.

4.1 Updated Documentation
This release contains a package of updated documentation labeled
"Change Pages." This packet contains:
•

New and updated documentation

•

Instructions for incorporating this documentation into your
manuals

Note that for some of the longer chapters, only the pages that
changed are included. You might, for example, replace only pages 5
through 10.
Follow the instructions in the packet.

}(G-03-23-87-3.0/2.2.1

- 26 - The Santa Cruz Operation

Operating System Release Notes

4.2 Operations Guide - Chapter 6
The following sections should have been in Chapter 6 of the
Operations Guide, "Backing Up File Systems. "
4.2.1 Creating Backu ps

To create backups with sysadmin, log in as the super-user, then:
1.

Enter:
sysadmin
and press RETURN. You see a file system maintenance
menu.
Filesystem Maintenance Options
1. Do a daily backup (level 9)

2.
3.
4.
5.

Do a periodic backup (level 0)
Get a backup listing
Restore backed-up file(s)
Restore an entire file system

Enter an option or enter q to quit:
2.

Enter "1" for a daily backup or "2" for a periodic backup
and press RETURN. H the system has never had a periodic
backup, it automatically performs one, even if you have
chosen adailybackup.

You see two menus in sequence. The first is a selection of
filesystems to back up, and the second is a selection of
backup, or archival media.
Each menu also presents the option "Other:". The "Other"
option appears in many of the sysadmin menus. Using this·
option, you can backup or restore filesystems that are not
described in /etc/deJault/jilesys and use backup devices that
are not described in /etc/default/archive. These two files are
discussed later.

XG-03-23-87 -3.0/2.2.1

- 27 - The Santa Cruz Operation

XENIX for Personal Computers

Load a volume, tape or disk, into the selected drive, and
press RETURN. The system displays the current date and the
date of the last backup ( "the epoch" if there has been no
backup), then begins to copy files to the drive. H a volume
runs out of space, the program displays the message:
Change volumes

Remove the first volume, insert a new volume, then press
RETURN. The program continues to copy files to the new
volume. Repeat this step until the program displays the
message:
DONE

When doing a periodic backup, you may need to repeat the last step
several times before the backup is complete.
4.2.2 Getting a Backup Listing

To get a backup listing, log in as root, then:
1.

Enter "3" at the main sysadmin menu. You are prompted
for the name of the file in which to place the listing. Enter
RETURN if you wish to use the default Itmplbackup.list.
The program prompts you to insert the first backup volume.

Load the first volume, then press RETURN. The program
automatically reads the filenames off the backup volume and
places them in the list file.

4.2.3 Restoring Backup Flies

You can restore files from the backup volumes by invoking the
sysadmin program and selecting the fourth item in the menu. You
will need the complete set of backup volumes containing the latest
version of the file or files you wish to restore, and you need the "full
pathname" of the file or files you wish to restore. This pathname is
given in the backup listing.
To restore a file, follow these steps:

XG-03-23-87-3.0/2.2.1

- 28 - The Santa Cruz Operation

Operating System Release Notes
1.

From the main sysadmin menu, enter "4" and press
RETURN. You see:
1. Restore file(s) to their originallocation(s)

2. Restore file( s) to another location
Enter an option, or enter q to quit:
2.

When you select option 1, be aware that files with the same
names as files currently on your disk will overwrite the disk
files. Always restore files in a temporary directory, then
compare them, if necessary.

If you select option 2, you are prompted for a directory
name. Your restored files are placed in that directory, and
are named by the numbers (inode numbers) displayed by the
restore program.

The program prompts you to enter the full pathname of a file
you wish to restore, and continues prompting for filenames
until you just press RETURN. If you press RETURN, the
program prompts you to insert the first volume in the backup
set.

Next you are prompted for the archive device. Select the
same drive and medium on which your backup was created,
for example, tape or floppy disk.

Load volume 1 of the backup set into the drive, then press
RETURN. The program displays the inode numbers of the

files you have given, then prompts for a volume number.
7.

Remove the first volume and replace it with the last volume
made of the backup set into the drive, enter its number and
press RETURN. The program searches the volume for the
specified files and places copies into the specified locations
on your hard disk.

The program prompts for volume numbers until all of the
files have been found. Continue to read volumes in reverse
order until the first volume made has been loaded and you
have returned to the main menu.

){(J-03-23-87-3.0/2.2.1

- 29 - The Santa Cruz Operation

XENIX for Personal Computers

H you select another directory as the destination for the
restored files, the files are placed in that directory and named
by their inode numbers.

4.2.4 Restoring an Entire FUesystem

To restore an entire filesystem, select option "5" in the main
sysadmin menu. Do not use this option carelessly; all information
currently in the target file system will be overwritten. Restore an
entire file system only onto a clear or newly-made filesystem, or onto
a file system that is completely corrupted or inaccessible. See
divvy( C), mkfs( C) and other documentation on making filesystems.
You can use this option to restore any filesystem, including the root
filesystem. However, there are special considerations; if you need to
restore your root filesystem, you must have a boot/root floppy. H the
root file system is only partially damaged, use option 4 to recover the
necessary files. If you need to restore the entire root filesystem, you
can do this by:
•

Using a boot/root floppy that has the restore command on
it; or

•

Reinstalling the XENIX system, then using option 4 to
recover the files that are unique to your system.

To restore an entire filesystem:
1.

Select option 5. You are warned that this is a serious task
and are given a choice as to whether you wish to continue.

At the next menu, select the file system that you wish to
restore, or the "Other" option to enter the name of another
filesystem. H you select the root filesystem, you see a
shortened version of the previous warning, and you are
asked if you wish to continue. If you select "Other", you are
prompted for the device name of the filesystem that you wish
to back up or restore.

Next you see the archive menu. Select the medium on which
your filesystem is backed up, for example, tape or floppy.

}(J-03-23-87-3.0/2.2.1

- 30 - The Santa Cruz Operation

Operating System Release Notes

You are prompted to load the first volume of the backup into
the selected drive. The restore program prompts you to
change volumes if necessary.

4.2.5 Editing /etc/default/fllesys and /etc/default/archlve

The files /etc/default/filesys and fete/default/archive are used by
sysadmin to create the filesystem and archive device menus. Even
though each menu provides the option "Other" so that you can use
filesystems and devices not described, you should keep these default
files up to date as your system changes. These files are also used by
other programs, and should be maintained as specified for these
programs.
Each device, file system or drive, in these files is represented by a one
line entry which consists of "name=value" pairs, separated by spaces
or tabs. For example, the following is a possible entry in
/ etc/default/archive:
cdev=/dev/rfd048ds9 desc="Floppy Drive 0 (48dsdd)"\
blocking=18 size=360 format="format -f /dev/rfd048ds9

The value part of "name=value" pairs "desc="Floppy Drive 0
(48dsdd)"" and "format="fonnat -f /dev/rfd048ds9"" contain
spaces, therefore they must be surrounded by quotes in order to be
interpreted correctly.
Note that the newline is preceded by a backslash (\), which causes
the two lines to be interpreted as one line. This convention makes
the files easier to read.
The minimum necessary information about an archive device is:

A character device name (cdev=) or
a block device name (bdev=), and
a size, (size=).
Without these, sysadmin will not use the entry.
A description, (desc=), can be added that appears in the archive
device menu. H a format command is included, then you mayfonnat

XG-03-23-87 -3.0/2.2.1

- 31 - The Santa Cruz Operation

XENIX

for Personal Computers

media from the sysadmin program.
A blocking factor for the medium, (blocking=), is included in the
above example for possible use by other programs. It is not used by
sysadmin.
The size (size=) , in the above example, is considered to be a number
of K, or kilobytes. H an entry is included for density, (density=), as in
the following example, then the size is taken to mean a number of
feet, which is more appropriate for tape than for Hoppy disks:
cdev=/dev/rmtO desc="Cartridge Drive (600 ft tape)'"
blocking=20 size=600 density=20000

The minimum necessary information about a filesystem is:
a character device name, (cdev=), or a block device name,
(bdev=).
Additionally, you may include a description, (desc=),
which appears in the sysadmin filesystem menu,
and the mount directory, (mountdir=), which is also used
by letelmnt, in addition to sysadmin. The name remount,
in the example below is used exclusively by /ete/mnt to
indicate whether a file system should be mounted when the
system goes multiuser (when / ete/rc is run).
bdev=/dev/root cdev=/dev/rroot mountdir=/\
desc='The root file system" rcmount=no
Backslashes escape the value of newlines, and the comment
character is a number sign (#).

4.3 Operations Guide - Chapter 7

4.3.1 Section 7.3 - Using a Cartridge Tape Drive

The following sections should have appeared in Chapter 7 of the
Operations Guide.

XG-03-23-87 -3.0/2.2.1

- 32 - The Santa Cruz Operation

Operating System Release Notes
A tape cartridge drive is a mass storage device that uses 114 inch tape
cartridges to store data. It is also referred to as a QIC (quarter inch
cartridge) tape drive. A tape cartridge can hold many times the data
that can be stored on floppies, making it much more useful for large
backup operations.
The drives that are supported under XENIX. are listed in the
Operating System Release Notes. For hardware-specific
information, refer to the manual for your drive and tape(HW) in the
XENIXReference.
4.3.1 Installation and Configuration

Refer to the your tape drive hardware manual for physical
installation instructions. Once it is connected to your computer,
enter this command to configure the drive:
mkdev tape
mkdev runs an interactive program called tapeinit which explains the
configuration process and prompts you for necessary input.
See mkdev( C) for more information.
4.3.3 Accessing the Drive

You use a QIC tape drive much like a floppy. You can use the
standard commands such as tar(C), dd(C), cpio(C), backup(C),
dump(C), and re store (C) commands are used to access a cartridge
tape drive. This section summarizes tape operations and how to
perform simple backups and restores. For instructions on how to
perform system backups and related file system maintenance, see the
chapter on "Backing Up File Systems" in this guide.
4.3.4 The tar Command

The tar command is useful for making a backup copy of entire
directorie.s. The command has the syntax:
tar cvf devicefile files
The devicefile is the file name that corresponds to the cartridge drive.

){(J-03-23-87-3.0/Z.2.1

- 33 - The Santa Cruz Operation

XENIX

for Personal Computers

files are the names of the files or directories to be copied. For
example, to copy all the files in the directory lulbogart to the
cartridge drive Idev/rctO, enter:

tar cvf Idev/rctO /u/bogart
To restore files stored on tape, insert the cartridge containing the files
or directories you wish to restore and enter the following command:
tar xvf devicefile
tar restores all the files on the tape to the present directory.
For detailed information on backup operations and other methods
of copying files, refer to tar(C), cpio( C), backup(C), and restore(C)
in theXENIXReference.
4.3.5 fetcfdefault Entries

Depending on the utilities used, you will need to create entries in
certain files in the / etc/default directory. These entries are the
default information that utilities such as tar use when accessing the
given device. Using tar and a Qle tape drive (configured as / devlrctO).
as an example, the device would require the following entry in
/etc/defa u It/tar:
archiveO=/dev/rctO 20 300 Y
In this case,ldevlrctO is the default device (archiveO), with a blocking

factor of 20, and a volume size of 300 feet. y indicates that (yes) the
device is a tape drive. If /dev/rctO is a ctmini drive, the entry would
be:
archiveO=/dev/rctO 18 0 Y
The utilities backup and restore have similar files and entries. For
more information on default files, see default(M) in the
XENIX Reference and the manual entry for the particular command.
4.3.6 The irwin Tape Drive

XENIX 2.2 supports two kinds of Irwin mini-cartridge tape drives:

•

the Model 110 (10 megabyte) and

XG-03-23-87-3.0/2.2.1

- 34 - The Santa Cruz Operation

Operating System Release Notes
•

the Model 145 (40 megabyte).

Memory and Irwin Usage. Irwin use is directly related to the amount
of physical memory installed on your computer. The more memory
you have, the better the driver performs. This is because of normal
memory fragmentation occurring in multiuser operating systems.
The Model 110 works with a minimum of 1 megabyte of physical
memory or 530K of user memory. The Model 145 works with 1
megabyte of physical memory or 390K of user memory. Look for the
"user =XXX kIt message during boot -up. The value of "XXX' must be
530 or greater for the Model 110 and at least 390 for the Model 145 .
We recommend that you always use the Irwin tape drive in singleuser mode because there is more memory available and less memory
fragmentation. Also, system activity is typically quiet when running
in single user mode; Irwin format and 110 operations are faster and
there are fewer bad blocks on tapes formatted when running on a
quiet system.
When excess memory fragmentation occurs, you see this error
message on the console:
: Not enough memory for mini-cartridge; retrying ...
The driver tries to access the tape drive for one minute. During this
time you can either wait for processes to exit or kill processes that are
using up memory. If memory fragmentation still exists after one
minute, the tape command fails and you see,
: Not enough memory for mini-cartridge; open failed.
Fonnatting the Irwin Tape Media. You must format blank, unused,
Irwin mini-cartridge tapes with the fonnat(C) utility before YOll can
llse them. Use this command on blank, unformatted tapes:
format Idevlrctminiv
The rctminiv device verifies the format on the tape. You should also
use the verification device when making backups tapes.
YOll cannot reformat 10-megabyte tapes. You can only reformat
4O-megabyte tapes. Generally, once the format is written, it is good
for the life of the media. The fonnat only needs to be re-written if a
failure occurs while formatting is in progress.

XG-03-23-87 -3.0/2.2.1

- 35 - The Santa Cruz Operation

XENIX for Personal Computers

To reformat a 40-megabyte tape use the format command with the - e
option:
format -e /dev/rctminiv
This erases the tape completely, including all previous format
information, then reformats the tape. Note that this is a lengthy
process and it cannot be interrupted once it has been started.
4.3.7 SecdoD 7.12.1 - Iplnlt

Before you give the Ipinit command, you must make sure that the line
to the printer is working correctly. To check this, you should connect
the printer to your system, tum it on, and send text from the system
to the port that is connected to the printer. For example, the
command:
cat /etc/motd > /dev/ttyla
should cause a copy of the /etc/motd file to print on your printer. H
this test fails, you should check and make sure that:
•

The printer is correctly connected to the computer.

•

The connecting cable is in good condition.

•

Your printer is powered on.

•

The port is recognized by XENIX.

4.4 User's Guide - Chapter 6

4.4.1 SecdoD 6.5.3 - "Create the L.sys FIle"

In the section "Create the L.sys File," the line that reads:

--ogio -EOT -ogin -uuccg ssword: market
should read:

XG-03-23-87-3.0/2.2.1

- 36 - The Santa Cruz Operation

Operating System Release Notes

--ogin -@ -ogin -uuccg ssword: market

4.5 termio(M) and stty(C)
There are two new extensions to the c-flag field which is documented
on the tennio{M) manual page:
CTSFLOW
RTSFLOW

0020000
0040000

CTSFLOW and RTSFLOW enable CTs/RTS ftow control. You
should also set - ixon and - aaoy so that these two types of ftow
control do not interfere with each other.

On the stty(C) manual page, the following two stty settings should
have been included in the list of "Common Control Modes":
ctsftow (-ctsftow)
Enables CTS protocol for a modem line.
rtsftow (-rtsftow)
Enables RTS signaling for a modem line.

4.6 fsname(M)
The "Syntax" line of the fsoame(M) utility is incomplete. It should
read:
fsname [- p] [. s name] 1devIdevice

4.7 Shell Enhancements
There are several enhancements to the shell (Bourne shell) in XENIX
2.2:
•

You can now define functions within the shell.

•

You can now redirect the output of built in shell commands
just as you would for other commands.

XG-03-23-87 -3.0/2.2.1

- 37 - The Santa Cruz Operation

XENIX for Personal Computers

4.7.1 DeftnlDa Functions

Functions are like shell scripts or procedures except that they reside
in memory and so are executed by the shell process, not by a separate
process. The basic form is:

name ( ) {list;}
list can include any of the commands previously discussed.
Functions can be defined in one section of a shell script to be called
as many times as needed, making them easier to write and maintain.
Here is an example of a function called "getyn":
# Prompt for yes or no answer - returns non -zero for no
getyn()
{
while
echo "\0$* (yIn)? c">&2
do
read yo rest
case $yo in
[yY]) return 0 "
[nN]) return 1 ;;
*) echo "Please answer y or nIt >&2 ;;
esac
done
}

In this example, the function appends a "(yIn)?" to the output and
accepts "r' , "y" , "n" or "N" as input, returning a 0 or 1. If the input
is anything else, the function prompts the user for the correct input.
The echo should never fail, so the while-loop is infinite.
Functions are used just like other commands; an invocation of getyn
might be:
getyn "Do you wish to continue"

II exit

However, unlike other commands, the shell positional parameters
$1, $2, ... , are set to the arguments of the function. Since an exit in a
function will terminate the shell procedure, the return command
should be used to return a value back to the procedure.

4.8 dos (C) - dosformat
There is a new command, dosformat, that creates DOS 2.0 formatted
disks. The drive may be specified in either DOS drive convention,

XG-03-23-87-3.0/2.2.1

- 38 - The Santa Cruz Operation

Operating System Release Notes
using the default file /etc/default/msdos or using the XENIX special
filename.
dosfonnat has three options, -f, -q, and -v. The -f option
suppresses the interactive feature. The -q (quiet) option is used to
suppress information normally displayed during dosfonnat. The-q
option does not suppress the interactive feature. The -v option
prompts the user for a volume label after the diskette has been
formatted. The maximum size of the volume label is 11 characters.
The dos(C) manual page in the XENIX Reference contains an error.
The example display on "Page 2" that looks like this is incorrect:
A=/dev/fdO C=/dev/hdOd D=/dev/hdld
It should look like this:

A=/dev/fdO
C=/dev/hdOd
D=/dev/hdld

4.9 enable(C) and disable(C)
You no longer need to wait a full minute between running the
enable(C) and disable(C) commands.

4.10 fonnat(C)
The fonnat( C) utility now has a -e option that completely erases and
reformats a mini -cartridge.

4.11 fsck(C)
fsck(C) now uses the file /etc/default/boot for automatic boot
control.

4.12 baltsys (C)
haltsys(C) no longer uses the shutdn(S) system call. Instead, it now
uses uadmin(S).

XG-03-23-87 -3.0/2.2.1

- 39 - The Santa Cruz Operation

XENIX for Personal Computers

4.13 mkuser(C)
There are two new possible parameters in the letcldefaultlmkuser
default file. HOMEMODE sets the permissions in the new user's
home directory and PROFMODE sets pennissions for the new user's
.login and .cshrc , or .profile files. They are set as follows:

HOMEMODE=0755
PROFMODE=064O

4.14 mount(C) and mnt
There is a new command, mnt, that mounts filesystems based on
information in letcldefault/filesys. mnt runs from /etc/rc with the
-rc flag to mount filesystems when the system comes up multiuser.

4.15 default(M) - /etc/defau It/archive
There is a new default file, letc/defaultlarchive. It describes which
backup, or archive, devices correspond to which devices on· the
system.

4.16 login (M)
There are three new types of entries in letc/defaultllogin:
IDLEWEEKS,CONSOLEandPASSREQ.
IDLEWEEKS=n, where n is a number of weeks, works in conjunction
with pwadmin{C). H a password has expired, you are prompted to
choose a new one. H it has expired beyond IDLEWEEKS, the user is
not allowed to log in and must consult the system administrator. The
CONSOLE=/dev/??? entry means that root can only log in on the
/dev device listed. PASSREQ-YES, if set, forces you to select a
password if you do not have one.

4.17 term cap (M)
The manual page tenncap{M) in the XENIX Reference mentions
console{M) in the "See Also" section. This is incorrect. It should

XG-03-23-87 -3.0/2.2.1

- 40 - The Santa Cruz Operation

Operating System Release Notes

reference screen(HW).
Refer to screen(HW) for a description of the character sequences
used by the display device attached to your video display adapter.

Compatible Hardware

XENIX runs on most PC hardware. In general, your hardware·
configuration must have the original settings and boards before you
boot XENIX. H you have added any boards, make sure that all
switches are set as recommended in the manufacturer's hardware
manual for that board.
These Notes contain general guidelines for hardware compatibility,
followed by a section of exceptions and special notes for each
machine type. These guidelines must be followed to ensure proper
system performance.

Note
The specific hardware that is listed in these Notes has been
used with XENIX. However, because compatible machine
or add-on peripheral manufacturers may change
configuration, functionality, or firmware at any time, no
guarantee is implied. Please write us with accurate
hardware information for possible inclusion on our lists.

5.1 General Compatibility Guidelines
This section describes what hardware can be used with the standard
XENIX distribution. There are many other devices that you can use,
which require additional vendor supplied software, that are available
from independent hardware vendors. Call your dealer for the
availability of an mv/ISV catalogue.

XG-03-23-87-3.0/2.2.1

- 41 - The Santa Cruz Operation

XENIX for Personal Computers

5.1.1 Machine.

XENIX System V 2.2 is available for several machine configurations.
Your version is for one of the following machines:
XENIX version
86XT

Hardware Configuration
Standard PC/XT compatible with an 86 family
CPU, running in real or unprotected mode.

6300+

AT &T 6300+ with a 286 CPU running in
protected mode.

286AT

Standard PC/AT compatible with a 286 or 386
CPU running in protected mode.

286HP

HP Vectra with a 286 CPU running in protected
mode.

386AT

Compaq Deskpro 386 compatible with a 386 CPU
running in demand paged virtual memory 32 bit
mode.

Note

For machines with bus or processor speeds greater than 6
MHz, check with your peripheral vendor to verify that
their hardware will run under your configuration.
Malfunctions with slow hardware are especially noticeable
in a 386 environment.

Some computers arrive with the hard disk only partially formatted. If
you have such a machine, use the DOS hard disk format command or
Diagnostics diskette to format the entire disk before installing the
XENIX Operating System.

){(J-03-23-87-3.0/2.2.1

- 42 - The Santa Cruz Operation

Operating System Release Notes

Some computers require specific switch settings to run XENIX. If
your computer does not run XENIX with the settings as shipped,
contact your computer hardware representative for the proper
settings.
5.1.2 Math Chips

Your personal computer may include the 8087 or 80287 math coprocessor, which is automatically detected and supported by
XENIX-86, XENIX-286, and XENIX-386. These co-processors will
im prove floating point efficiency.
Intel 8087 and 80287 math co-processors matching your machine's
CPU speed should work with XENIX. Follow the manufacturer's
recommendations.
At boot time, XENIX announces the presence of a math coprocessor with the message "math coprocessor present" if an 8087 or
80287 is detected. Please note that switches on the main system
board must be set properly to enable 8087 or 80287 interrupts. Check
your hardware manual for the proper switch settings.
Some 8087 and 80287 exceptions have been masked. Refer to the
manual page for 8087(M).
5.1.3 Memory Cards

In general, most memory cards work with XENIX. If you experience
"panic: parity" errors it is often because of low quality memory chips
or cards.
With memory cards, check the switch settings on both the card and
motherboard. Refer to the hardware manuals for your computer and
for the memory card to find the correct switch settings. XENIX-86
supports up to 640K of main memory. XENIX-286 and XENIX-386
support up to 16MB of main memory.
5.1.4 Multi-Function Cards

The serial ports on many multi -function cards function as expected
if COM1 and COM2 are fully compatible with the mM specifications

XG-03-23-87 -3.0/2.2.1

- 43 - The Santa Cruz Operation

XENIX for Personal Computers
for these serial ports. These parameters are explained in the "Serial

110 Boards" section of these Notes.
Memory, parallel ports or other hardware will also function as
expected.
5.1.5 Serial 110 Boards

This section describes the conditions under which various serial 110
boards work with XENIX, and the results of using them. Standard
single port serial 110 boards function as expected if COM! and COM2
are fully compatibIe with the IBM specifications for these serial ports.
Each multiport serial 110 board is unique; XENIXhas driver code for
each card listed. Only those with status poll registers may work on
XENIX, and new boards require additional driver support. The
following serial 110 boards are supported with XENIX:
AMI lamb 4 and 8 port
Arnet Controls 2, 4 and 8 port
(clock option not supported)
Arnet Twin port
AST FourPORT/XN
Control Systems Hostess 4 and 8 port versions
CTC Versanet 4AT (4 port) and 8AT (8 port)
Digiboard 4 and 8 port
mM standard COM1 and COM2
Kimtron Quartet 4 port
Quadram QuadPort™ 1 and 5 port
Stargate Technologies OC4400 (4 port) and
OC8000 (8 port) versions
Tandon Quad SeripSard
Refer to the serial(~ and mkdev(C) manual pages for more
information on compatible serial 110 cards and on adding and
enabling serial lines.
82508 Serial 110 Chip Note.

Some computers or add-on serial 110 cards use the 8250a serial 110
chip. Some revisions of this chip do not handle interrupts properly.
DOS does not use interrupts, so the use of this chip with DOS causes
no problems. XENIX does make use of interrupts, as it is a multi-

XG-03-23-87-3.0/2.2.1

- 44 - The Santa Cruz Operation

Operating System Release Notes

tasking operating system.
The problem with the serial I/O chip shows up when using uucp(C)
or cu( C). Indications that your computer contains a bad revision
8250a chip are that uucp(C) may lose characters constantly and
generate unkillable uucico processes, and that cu(C) at high baud
rates stops executing and does not exit.
The problem rarely shows up when using the serial port with a
terminal. It is associated with high-speed serial input. !fyou want to
use uucp(C) or cu(C) and your computer has one of these chips, we
recommend you replace the 8250a chip with an 8250b serial I/O chip
or use a multi-function card containing a serial port and configure it
as COM! or COM2. Configure the built-in serial port as COM3 or
COM4, which are not often used by XENIX, or avoid high-speed
input on that port.
All COMl boards should be strapped at interrupt vector 4. All
COM2 boards should be strapped at interrupt vector 3. Check your
serial card hardware manual or call the hardware manufacturer for
the switch settings that implement these addresses.

Note
SCO uniPATH SNA-3270 uses interrupt vector 3, which can
interfere with the use of a serial card on COM2.

Serial Card Addresses and Notes

The following table lists supported serial cards and their addresses.
Note that if you install two serial cards on COMl and COM2 that are
incompatible, you may see this message at boot time:
WARNING: Serial boards are installed at conflicting addresses

The message indicates the boards do not have the correct switch
settings. This check does not occur for cards installed on additional
COM ports and you may not see this message even if the boards are
actually incompatible.

}{(J-03-23-87-3.0/2.2.l

- 45 - The Santa Cruz Operation

XENIX for Personal Computers

Refer to the following serial address table to resolve conflicts and
check the "Notes" following the table for more information.

Serial Card Addresses
Primary Primary Alternate Alternate
UO
Status
110
Status
Address Address Address Address

Physical
Port

Board
Type

COM1

AMI lamb··
Arnet
AST·
CTCt
Digiboardtt
Hostess
Kimtron
Quadram···
Stargate
Tandon···

OXS40
OxlOO
OX2AO
Oxl60
Ox 110
OXSOO
Oxl20
Ox280
Ox290
OX2AO

Ox210
Ox 142
Ox2BF
n/a
OxlS1
OxS07
Ox8120
Ox2D3
0x2D0
nfa

none
Ox280
none
none
none
Ox680
none
none
none
none

n/a
OX2C2
n/a
nJa
n/a
Ox687
n/a
nfa
nfa
nfa

COM2

AMI lamb··
Arnet
AST·
CTCt
Hostess
Digiboardtt
Kimtron
Quadram···
Stargate
Tandon···

Ox2CO
Oxl80
OxlAO
Ox2l8
OXS80
Ox210
Ox2EO

Ox2l2
OxlC2
OxlBF
nfa
OxS87
Ox2S0
Ox82EO
Ox2DB
OxlDO
nfa

none
Ox300
none
none
Ox700
none
none
none
none
none

nfa
Ox342
nfa
nfa
Ox7fJ7
nfa
nfa
nfa
nfa
nfa

•
Ox400
OTHERl UNISYS····

nfa

none

nfa

OTHER2

nfa

none

nfa

•
UNISYS···*

XG-03-23-87-3.0/2.2.1

Ox288

Oxl90
Ox280
Ox408

- 46 - The Santa Cruz Operation

Operating System Release Notes

* Only enhanced mode is supported. Do not use the AST
driver.

** Only continuous mode is supported.
*** Tandon is the only card whose I/O addresses are
potentially identical with other supported cards, such as the
AST and Quadram serial cards.
Since card addresses must not overlap in the same systems, if
you have both a Tandon and a Quadram, the Tandon must
be on COMl and the Quadram must be on COM2.
You can use the following Quadram serial expansion cards in
these configurations under the standard XENIX Operating
System:
COMl

COM2

5-port
I-port
5-port

5-port
1-port
I-port

H you need to use any other configuration of Quadram cards,
you must relink the kernel using the Link Kit. Edit sioconf.c
as follows:
1.

This file contains several groupings of serial card
descriptions. Each group is identified by the first
number on the description line.
Find the descriptions for the Quadram cards in each
group and move that descriptor line to the front of
the group.

Remake and boot the new kernel.

*.** These senal cards only work on the UNI SYS PC/IT.

Notes for the CTC Versanet serial cards:

XG-03-23-87-3.0/2.2.I

- 47 - The Santa Cruz Operation

XENIX for Personal Computers

The correct switch settings for the SAT and 4AT
are:
As a COMI (strapped at addrOxI60, using irq4 ) the
SAT has:
switches 33, 35, 36, 38, 39 & 40 OFF
switches 34, 37 ON (ie: shunted)
on the DIPSWITCH selection:
5,6 & S should be OFF
all the others should be ON
As a COM2 ( strapped at addr OX21S, using irq3 ) the
8AThas:
switches 33, 35-40 OFF
switch 34 ON (ie: shunted)
on the DIPSWITCH selection:
1, 2 & 7 should be OFF
all the others should be ON.
The 4AT is the same as the 8AT in both the above
cases, with the following common exception:
switches 39 & 40 MUST BE ON (shunted)

These boards come in both 8250 and 16450 versions,
you must have the 16450 version if you intend to run
on 386. The 8250 should run on the 286.

The original CTC Versanet boards used different
addresses. Please ask your hardware vendor for
versanet boards strapping at the above addresses
(160 and 21S).

The CTC "Maomao-4" serial board is not
supported.

XG-03-23-S7 -3.0/2.2.1

- 48 - The Santa Cruz Operation

Operating System Release Notes

tt Notes on the Digiboard serial card:
1.

Ports for switches DS2 to DS5 (DS9 for 8 port
version) must be strapped starting at the boards base
address as given in the table and incrementing by 8
for each port.
The following example is for COM1 at 110:
DS2
DS3
DS4
DS5
DS6
DS7
DS8
DS9
DS1

110
118
120
128
130
138
140
148
150

H COM1 is used then aU the ports must be strapped
as "EVEN" to interrupt request line 4 (see Digiboard
documentation). H COM2 is used then all the ports
must be strapped as "ODD" to interrupt request line
3 (same notation).

Only rev. 3 and later boards are supported.

XG-03-23-87 -3.0/2.2.1

- 49 - The Santa Cruz Operation

XENIX

for Personal Computers

5.1.6 Tape Drive/Controller Combinations

The tape drivers, included in this release, work with the following
drive/ controller combinations.
Manufacturer
Archive
Computone ATvantage-SX
Tape backup
COREtape
Emerald
Irwin· (mini-cartridge)
TIT

TecmaiIM(IBM®}
TI
Wangtek

Controller
SC400
SC400

Drive
Scorpion 5945
Scorpion 5945

PC36
PS60-9000
floppy
floppy
PC36
QIC60
SC400
PC-36

5000(E}
(Combo)
145 (40 megabyte drive)
110 (10 megabyte drive)
5000(E}
(Combo)
Scorpion 5945
5000(E}

• The Irwin 40 megabyte drive uses a DC2000 tape cartridge, and
the 10 megabyte drive uses a DC1000 tape cartridge.
Note that these drives are sometimes sold under other brand names.
Only one cartridge tape subsystem is supported per computer.
QIC24 format is supported on the full size cartridges. Tape support is
raw (character) only, no block device. A tape utility, tape(C), is
provided for rewinding, erasing, retensioning, etc.
Tape drivers are included with XENIX-286 and XENIX-386, but not
withXENIX-86.
5.1.7 Video Adapters and Monitors

Any video adapter/monitor combination which runs with an adapter
that is a true equivalent of a standard adapter should run under
XENIX.
XENIX supports the use of two video adapters and two monitors, one
of type mono and the other of type color.
Adapters which come as the default adapter in supported computers
(monochrome or color monitor) will work with XENIX.

XG-03-23-87 -3.0/2.2.1

- 50 - The Santa Cruz Operation

Operating System Release Notes

We have used the following video adapters and monitors under
XENIX. Although many standard emulating cards work with XENIX,
these are some specific examples.

Video Cards and Monitors
Monitor

Card

standard monochrome

IBM Mono Card
Hercules mono
ASTCGA
Paradise Modular Graphics Card
Everex Graphics Edge
IBMCGA
Plantronics Color-Plus
Wyse WY -430 (cga, mono,
color, hercules)

IBM EGA

Wyse WY -440 (EGA card)
WyseWY-700
NEC APC-H431
IBMPGA

standard RGB (red green
blue) or com posite color
WY-530 (green or amber
monochrome)
WY-630 (color)
WY-640 (color EGA)
standard monochrome
standard RGB color
IBM EGA
WY-640 (color EGA)
WY-700

IBMPGA

5.1.8 Add- On Hard Disks

The "Enhanced Hard Disk Support" feature is described earlier in
these Notes.
Many hard disks, both standard and nonstandard, can be used by
XENIX as long as the disk controller supports the drive. The disk
must interface electrically with the disk controller (usually "ST506").

XG-03-23-87 -3.0/2.2.1

- 51- The Santa Cruz Operation

XENIX

for Personal Computers

Compatible hard disk controllers are discussed in the next section.
For a standard disk: the motherboard ROM must have an entry for
the disk (type) determined by the number of heads, cylinders, tracks
per cylinder (heads), sectors per track, and other characteristic
information.
Follow the manufacturer's instructions to set switches or
configuration.
For nonstandard disks: The user may type in information that
overrides the ROM during installation.
5.1.9 Compatible Hard Disk Controllers

Many hard disks will work with XENIX. Whether or not a disk works
depends upon the controller board. Here are two tests the controller
must meet:
1.

The disk controller is fully compatible with the standard
controller for that configuration, for example, XEBEC
compatible for XT configurations, WDI0I0, WD2010, or
WD2020 compatible for AT.

No special vendor software is needed to make the controller
work under DOS.

If a controller meets these tests, it might work, but if it fails these
tests, it will not work.
5.1.10 Modems and Autodiallng

Any standard RS-232 modem works with XENIX using uucp(C) and
cu(C). The default autodialer is for the Hayes Smartmodem 1200.
An auto dial program is also supplied for the Racal Vadic 3451, and
the 212, and the Hayes Smartmodem 2400. Other autodialing
modems can be supported by writing a dialer program, or modifying
the existing one in /usrllib/uucp/dial .
The "uucp(C) Notes"section Note" and the dial(M) manual page in
the XENIX Reference Manual contain more information on writing
other dialer programs.

XG-03-23-87 -3.0/2.2.1

- 52 - The Santa Cruz Operation

Operating System Release Notes

5.2 XENIX-86XT

5.2.1 Machines

We have used the following machines under XENIX -86XT:
AT &T 6300 (Olivetti M24 in Europe)
Compaq Portable, DeskProTM * and PlusTM
Eagle Turbo ®
ffiMPC XT
ITfXP
ITfXTRA
Mitsubishi
NCR™ PC-6**
Tandy 1200

UNiSYS®

Wavemate Bullet-286 XT
WYSEpc WY-1100
WYSEpc+ WY-1400

*
**

Internal cartridge tape not supported.
For the NCR machine, configure the switches on the
motherboard for a color monitor, regardless of the type of
monitor used.

These machines have been reported to run XENIX -86, but we have
not tested them:
Compuserve/Canada Arthur in Canada
Ericsson PC
Leading Edge
Victor VPC 30 and VPC 15
5.2.2 Math Chips

We have used the following math co-processor chips under XENIX86XT:
8087

For8088CPUs.

XG-03-23-87-3.0/2.2.1

- 53 - The Santa Cruz Operation

XENIX for Personal Computers

8087-2
8087-3

For 8086 CPUs.
For fast 8086 CPUs.

5.2.3 Memory Cards

We have used the following memory cards under XENIX -86XT:
AST 6pack+
Tandon
Quadram quadboard
Sigma Maximizer
Microsoft RAM card
Tecmar Captain or First-Mate
AT&T for the 6300
5.2.4 Accelerator Boards

Accelerator boards are special cards that plug in to an 8088 machine
(not an 8086). They replace the 8088 CPU with a 286 CPU and
perhaps replace some memory as well. XENIX runs on accelerator
boards in 8086 unmapped mode.
The following accelerator board is supported in the XENIX-86XT
standard distribution:
Seattle Telecom and Data (SID) PC286
5.2.5 Add- On Hard Disks

We have used the following hard disks under the standard disk
XENIX-86XT configuration.

XG-03-23-87 -3.0/2.2.1

- 54 - The Santa Cruz Operation

Operating System Release Notes

CMI15
Plus HardCard 10
Miniscribe 20
Seagate 20
CDC 30
Rhodime 30
Mountain 20, 30
Syquest SQ306 standard
CDC Wren
Seagate ST-225
Miniscribe 3425
The following disks have been reported to work under the standard
disk XENIX -86XT configuration, but we have not tested them:
Peachtree 10, 20, 30
Maynard Apollo 30
Franklin Telecom 10, 20, 33
Rhodime 10
Tandon 10
Alpha Omega 10, 20, 30
Mountain Hard File
The following tables list the controllers most commonly used with
8086/8088 machines, and the type of hard disks they can support:
XEBEC Controller
(standard mM PC/XT compatible)

Type

Cyls

Hds

Size

Example

0
1
2
3

306
375
306

2
8
6
4

5MB
24MB
15MB
10MB

standard

306

}(J-03-23-87-3.0/2.2.1

- 55 - The Santa Cruz Operation

XENIX for Personal Computers

DTC Controller
(standard on AT+T 6300 - fully supported)

Type

Cyls

Hds

Size

Example

306
375
306
306
306
644

2
8
6
4
2
5

5MB
24MB
15MB
10MB
5MB
30MB
20MB
20MB

Syquest SQ306 standard
CDC Wren
Seagate ST -225
Miniscribe 3425

1
2
·3
4

6
7

Drive types 8 - 15 reserved

5.2.6 Compatible Hard Disk Controllers

The following table lists the hard disk controllers that we have used
under the XENIX-86XT configuration:
XEBEC 1210A
DTC 5150
WD lOO2/WX-2
Adaptec 2002
12 interface
ADES
CDC

5.3 XENIX- 6300+
XENIX-6300+ runs standard AT&T hardware with original switch

settings.
5.3.1 Memory Cards

Use AT&T memory cards, since the 6300+ has its own 16 bit bus and
is not AT memory card compatible.

XG-03-23-87 -3.0/2.2.1

- 56 - The Santa Cruz Operation

Operating System Release Notes

5.3.2 Hard Disks

The latest BIOS, version 2.01, contains a table of 8 supported disks
and their characteristics:
Type
0
1
2
3
4
5
6
7

Size
10MB
30MB
20MB
40MB
40MB
80MB
67MB
20MB

Exam~le

CDC Wren
CMICM6426
Tandon
Seagate ST4051
Miniscribe 8086
Micropolos 1325
Seagate ST225
or Miniscribe 3425

Cyls
306 cylinders
697 cylinders
640 cylinders
981 cylinders
977 cylinders
1024 cylinders
1024 cylinders
612 cylinders

Hds
4 heads
5 heads
4 heads
5 heads
5 heads
8 heads
8 heads
4 heads

Item 7 is the "standard" 20 MB disk currently in use in the PC 6300
PLUS. This table is the same as the one contained in versions 1.04
and 1.06 of the BIOS. The "other parameters" in the table affect
performance rather than capacity, so are not listed here. Item 5
should say 67MB instead of BOMB.
Hard disk drives C (and, optionally, D) are identified as entries 0-7 in
the table by setting one DIP switch on the motherboard and two
jumpers on the Western Digital controller board. On the
motherboard, there is a package of eight switches labelled "DSW-1."
Switch 3 is the most significant bit for drive D, and switch 4 is the
most significant bit for drive C. On the HDU controller board, there
is a package of eight jumper positions labelled "SW1."
The next two significant bits are jumper positions 4 and 3 for drive C
and 2 and 1 for drive D.
In all cases, "OFF" or "Open" is binary "1," and "ON" or "Closed" is
binary "0." So, the eight possible settings are:

XG-03-23-87-3.0/2.2.1

- 57 - The Santa Cruz Operation

XENIX for Personal Computers

Motherboard
DSW-1 switch

Disk Controller Board
SW1jumpers

Setting

3(D)_or_4(C)

4(C)_or-2 (D)

3(C)_or_1 (D)

On
On
On
On
Off
Off
Off
Off

Closed
Closed
Open
Open
Closed
Closed
Open
Open

Closed
Open
Closed
Open
Closed
Open
Closed
Open

1
·2

3
4
5

6
7

5.4 XENIX-286AT

5.4.1 Machines

We have used the following machines under the XENIX-286
configuration:

}(J-03-23-87-3.0/2.2.1

- 58 - The Santa Cruz Operation

Operating System Release Notes

American Research Corporation
Basic Time BT/ AT
Compaq Portable and DeskPro 286, 386*
ContellCADO AT/4
Epson Equity m
mM PC AT (6 or 8 meg version)
mM286/XT
ITTXTRAXL
Mitsubishi -286
MAD 286 AT
NCR PC-8 **
NEC APC IV
PC's LIMITED A TrM
Shaq> PC 7511
UNi SYS PC/IT

Tandy 3000
Texas Instruments Business Pro
Tomcat 3200-AT
WYSEpc 286 WY-2200
Victor V286
Zenith Z200 series
* Run in 286 Mode.
** Configure the CMOS database for
color monitor, regardless of the type of monitor used.
These machines have been reported to run XENIX-286, but we have
not tested them:
AST Premium 286
Corona ATP
Kaypro 286i
Olivetti M28
5.4.2 Math Chips

The 80287 math co-processor chip works in theXENIX-286AT. The
chip must be the correct speed for the 286, and it must be installed
correctly.

)(J-03-23-87-3.0/2.2.1

- 59 - The Santa Cruz Operation

XENIX for Personal Computers

5.4.3 Memory Cards

We have used the following memory cards under the XENIX-286
configuration:
AMI SMART PACK 2
AST
Quadram
Tecmar
Talltree Systems
Silicon Valley Systems
STB Rio Grande
5.4.4 Add- On Hard Disks

As noted earlier, many hard disks can be used by XENIX as long as
the motherboard supports the drive. ROM entries for the ffiM
PC AT are listed here. Refer to your computer hardware manual for
the disk types supported by other 286AT computers.
PC AT Disk Types Entries on Motherboard ROM
Type

Cyls.

Hds.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

306
615
615
940
940
615
462
733
900
820
855
855
306
733
0

4
4
6
8
6
4
8
5
15
3
5
7
8
7
0

XG-03-23-87 -3.0/2.2.1

Size

10MB
20MB
30MB
60MB
45MB
20MB no precompensation
30MB
30MB
110MB
20MB
35MB
50MB
20MB
40MB
Reserved, do not use.

- 60 - The Santa Cruz Operation

Operating System Release Notes

Note that other compatible machines may have different ROM
tables. Check your computer hardware reference manual for the
,appropriate ROM table entries for your computer.
We have used the following hard disks under the standard disk
286AT configuration:
Emerald 50, 70, 140
Maxtor 140
CDC 20, 30, 40, 70
Core
The Bernoulli Box® runs on standard AT compatibles with the
device driver from SCO, purchased separately. XENIX- 286 is
available on Bernoulli cartridges.
5.4.5 Compatible Hard Disk Controllers

We have used the following controllers under the XENIX-286
configuration:
WD 1010
WD 2010
DTC WD1010 compatible

5.5 XENIX- 286HP
For XENIX-286HP configuration infonnation,
documentation included with your machine.

consult

the

5.5.1 Machines

The minimum machine configuration that can run XENIX -286-HP
System Vis:
Hewlett-Packard Vectra model 45945A

XG-03-23-87 -3.0/2.2.1

- 61 - The Santa Cruz .Operation

XENIX for Personal Computers

5.5.2 Memory Cards

In addition to standard PC/AT memory, the following HP memory
cards work:
Hewlett-Packard 1/2 MB (45973A)
Hewlett-Packard 1 MB (45974A)
5.5.3 Serial 110 boards

In addition to the previously mentioned serial cards, the following
HP cards work:
Hewlett-Packard Serial Card (24540A)
Hewlett-Packard Dual Serial/Parallel Card (24541A)
5.5.4 Video Cards and Monitors

In addition to the previously mentioned video cards and monitors,
the following HP video cards and monitors work:
Hewlett-Packard Multimode Video Adaptor Card (45981A)
Hewlett-Packard Monochrome Monitor (35731A)
Hewlett-Packard Color Video Adaptor Card (45984A)
Hewlett-Packard Color Monitor (35741A)
Hewlett-Packard EGA Video Adaptor Card (45983A)
Hewlett-Packard EGA Monitor (35743A)
5.5.5 Other HP Hardware

The following terminals have been verified with XENIX - 286-HP:
Hewlett -Packard 2392
Hewlett -Packard 2393
A termcap entry has been included to support the HP 2392 and 2393
terminals with the following termcap name~:
- Standard HP mode: 2392
- HP mode without standout and underline: 2392ne
- ANSI mode: 2392an (supported by most applications)

XG-03-23-87 -3.0/2.2.1

- 62 - The Santa Cruz Operation

Operating System Release Notes

Set the TERM environment variable to the appropriate name.
The following printers are supported as standard print devices with
XENIX-286-HP:
Hewlett-Packard LaserJefIM Serial/Parallel (2686A)
Hewlett-Packard ThinkJetTM SeriaVParallel (2225D/2225C)
Hewlett-Packard QuietJetThf Serial/Parallel (2227A)
5.5.6 Compatible Hard Disk Controllers

The following table lists the hard disk controllers that have been
verified with XENIX-286-HP:

Manufacturer

Model#

Comments

Hewlett-Packard

45815A

supports 45817M 40MB
disk and some third party
ST-506 hard disk drives
(refer to sectionA.1.10)

Hewlett-Packard

45816A

supports 45816M 3 1/2"
ruggedized disk

45895A

Western
Digital
compauole hard
controller

XG-03-23-87 -3.0/2.2.1

2010
disk

- 63 - The Santa Cruz Operation

XENIX for Personal Computers

5.5.7 Add- On Hard Disks

The following hard disks have been verified with XENIX-286-HP
using the HP 45815A controller:

Description

Jumper
Setting

Priam®60

60Mb full height

DBC

Priam®40

40Mb full height

AEF

ST-4051

40Mb full heigh t

AEF

ST-225

20Mb half height

DEF

Maxtor® XTl085

68Mb full heigh t

AEC

Drive

Notes

Seagate

XG-03-23-87-3.0/2.2.1

Mounting b racket may
have to be slightly bent

- 64 - The Santa Cruz Operation

Operating System Release Notes

The following hard disks have been verified with XENIX-286-HP
using the HP 45895A controller:

Drive

Description

Disk
Type

Seagate

20Mb

Seagate

40Mb

Priam

60Mb

Maxtor

68Mb

Maxtor

140Mb

CMI

20Mb

CMI

30Mb

CDC

20Mb

){(J-03-23-87-3.0/2.2.1

- 65 - The Santa Cruz Operation

XENIX for Personal Computers

The following hard disks types have not been verified but may work
with XENIX -286-HPwith the HP 45895A controller:
Type
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

Cyls.
306

615
615
940
940
615
462
733
900
820
855
855
306

733
0
612
977
977
1,024
733
733
733
306

Hds.

Size

Precompensation

4
4
6
8
6
4
8
5
15
3
5
7
8
7
0
4
5
7
7
5
7
5
4

10Mb
21Mb
32Mb
65Mb
49Mb
21Mb
32Mb
32Mb
117Mb
21Mb
37Mb
52'Mb
21Mb
44Mb
Reserved, do not use.
21Mb
42Mb
59Mb
62Mb
32Mb
44Mb
32Mb
10Mb

128
300
300
512
512
none
256
none
none
none
none
none
128
none

XG-03-23-87-3.0/2.2.1

0
300
none
512
300
300
300
0

- 66 - The Santa Cruz Operation

Operating System Release Notes

5.6 XENIX-386AT

5.6.1 Machines

We have used the following machines under XENIX- 386:
Corvus 331
Compaq 386
Wyse 386
Systems using the Intel-386 motherboard will probably work.
5.6.2 Memory Cards

In general, 386 machines can use special 32 bit memory as well as

standard AT 16 bit memory. The 32 bit memory is definitely faster.
Follow manufacturers' guidelines to install both kinds of memory.
XENIX will use all of the memory properly installed in a machine.
5.6.3 Add· On Hard Disks

In general, 286AT disk configurations work on the 386AT.
5.6.4 Serial Cards

For serial cards, you must use only the fastest serial I/O chips. The
16450 generally works , whereas the 8250 usually does not.
5.6.5 Compatible Hard Disk Controllers

We have used the following controllers under the XENIX-386
configuration:
WD 1010
WD 2010
DTC WD1010 compatible

XG-03-23-87 -3.0/2.2.1

- 67 - The Santa Cruz Operation

XENIX for Personal Computers

6. Common Installation/Configuration Questions and
Answers
This section is our support department's combined effort to present
answers to the most common installationlconfiguration questions.
1.

PROBLEM: When I try to read one of the distribution
floppies I get the error message:
Error on dev floppy (2/52) block=xxx cmd=OOO3 status=OOO2
tar: tape read error
REMEDY: First try it on another machine. If it is a Boot or
Filesystem floppy, try booting it on a similar machine (your
dealer may be able to assist you). If it is not a Boot or
Filesystem diskette, try reading it using DISKCOPY under
DOS, or use the following command on a XENIX system:
dd if=/dev/install of=/dev/null

If any of these yields a message similar to the one above on
your own system, you are entitled to a free replacement
floppy.

PROBLEM: When booting from the Nl floppy,
"EEEEEE"s print on the console and the system refuses to
respond.
REMEDY: Try booting a DOS floppy, or other bootable
diskette. If the machine can boot a diskette, then your N1
floppy is corrupted. You are entitled to a free replacement
floppy.

PROBLEM: When booting up, the console screen blanks,
the cursor is gone, or the display is garb led.
REMEDY: You may have an incompatible monitor card.
Check Appendix A of these Notes for a list of supported
video cards and monitors. If yours is not listed but
compatible with one on the list, it should work. If not, check
your card's hardware manual to see if there are ways to
configure the switch settings so the card is in a IBM-

XG-03-23-87 -3.0/2.2.1

- 68 - The Santa Cruz Operation

Operating System Release Notes

compatible emulation mode and that it is addressing the
kind of monitor attached. If changing the switch settings
fails, then your monitor card is incompatible, and should be
replaced with a compatible card.
4.

PROBLEM: I see the error message:

Panic: memory failure -- parity error
REMEDY: Some part of your hardware is sending a "nonmaskable memory error interrupt" (a signal sent by the
hardware that halts the operating system). Run your
system's hardware diagnostics tests if available. Physically
re-seat your memory cards, and check for bent pins, etc. If
these measures fail to correct the problem, or you don't feel
comfortable in checking your hardware yourself, seek
assistance from professional hardware experts. One
frequent cause is memory chips that are slower than factoryrecommended chips.
5.

PROBLEM: I am trying to add a terminal to a serial port, but
do not get a login.

REMEDY: Follow these procedures to locate the cause of
the problem.
A.

If you are using a 4 or 8-port serial expansion board,

check to see if your board is recognized at bootup by
checking the bootup message. If not, the switches
on your card are not set properly., Check your
board's hardware documentation for the proper
switch settings and the "Compatible Hardware"
section of these Notes for the correct addresses. Be
sure it doesn't conflict with the interrupts for the
standard COM ports. COMl should be configured
as interrupt 4 and COM2 as interrupt 3. When the
card is correctly configured and recognized in the
boot up message, run "/etc/mkdev serial" which
creates device files for your extra serial ports.

XG-03-23-87-3.0/2.2.l

- 69 - The Santa Cruz Operation

XENIX for Personal Computers

Make sure you are in multi-user mode, your
terminal is plugged in and turned on and set for 9600
baud, 8 data bits, 1 stop bit, no parity. (If your
terminal doesn't send these, then see the section
titled "Changing the gettydefs File" in Chapter 7 of
the Operations Guide for ways to configure your
terminal.) The terminal should be connected with a
cable so that Transmit Data on the serial port is
connected to Read Data on the terminal, and
Transmit Data on the terminal is connected to Read
Data on the serial port (see the serial(HW) manual
page in the XENIX Reference Manual or your
terminal manual for more information.)

If the port is enabled, hit the RETURN key a few
times to see if a 'login:' prompt appears. If so, you
are ready to login. If not, disable the port by typing:

disable Idevlttyname

where ttyname is the device special filename of the
port in question. (For more information on the
naming convention for serial ports, see serial(HW)
in the Run Time Environment.) Make 'sure you're
using the non-modem control device.
D.

Check the / etc/ttys file so the entry for this serial port
looks like this:
Omttyname
If it does not look like the example above, then edit
/ etc/ttys with a text editor to correct it.

From the console, as root, see if you can redirect
output to your terminal by typing:
date> Idev/ttyname

If you do not see the date printed on your terminal
and you are not sure of the correct ttyname, try other
ttynames on that serial port. If you still do not see
the date printed, a hardware problem is possible, so
verify the following:

XG-03-23-87 -3.0/2.2.1

- 70 - The Santa Cruz Operation

Operating System Release Notes
Your cable is configured correctly (see B.
above). Also, try using only pins 2, 3 and 7.
Re-check
your
terminal
configuration (see #2 above).

setup

Re-check your switches on your serial
port. Hyouare using a multi-port card, try
other lines on that card.
Try attaching the terminal to a standard
serial port, COM1 or COM2, to see if the
terminal and cabling is correct.
If you have SCOXENIXV, Release 2.1 and
also have the SNA product, you cannot use
COM2, as SNA uses COM2, interrupt
vector 3.

Once you get the date printed on your terminal, then
enable the port and look for the 'login:' promp-t.
enable Idevlttyname

If you do not see the 'login' prompt, then verify that
getty is actually running on that port and that the
software is configured properly by typing:

ps -t ttyname
The output should look similar to the following
where "login" or "getty" is listed in the "CMD"
column.
F S UID PIO PPID C PRJ NI AOOR SZ WCHAN TrY TIME CMD

1 S 214 9210 1

0 30 20

344

6994

2a 0:06 getty

If you have typed the disable and enable commands
many times·, it is possible that a new getty cannot be
spawned on that port. H so, then shutdown the
system, re-boot, enter multi-user mode, and try
again.

XG-03-23-87-3.0/2.2.1

- 71- The Santa Cruz Operation

XENIX for Personal Computers

PROBLEM: I can't get a printout on my serial printer.
REMEDY: Make sure your serial printer is configured
properly under XENIX:

Be sure your printer is both capable of supporting
XON/XOFF protocols or DTR and is configured

for those protocols. Verify that it is turned on and
the cable is properly attached to the computer and
printer.
B.

If the port is enabled, disable it by typing: .

disable Idevlltyname

where ttyname is the device special filename of the
port in question. (For more information on the
naming convention for serial ports, see serial (HW)
in the Run Time Environment.) Make sure you're
using the non -modem control device.
C.

From the console, as root, see if you can redirect
output to your printer by typing:
date> Idevlltyname

If you do not see the date printed on your printer and
you are not sure of the correct ttyname, try other
ttynames on that serial port. If you still do not see the
date printed, hardware is suspect so verify the
following:

Your cable is configured correctly. If using
XON/XOFF protocol, see Question 5 step
B above. Also, try using only pins 2, 3 and

7.
Re-check your printer configuration by
verifying its switches in your printer
hardware manual. (See item A above.)
Re-check your switches on your serial
port. If you are using a mUlti-port card, try
other lines on that card and be sure it does

XG-03-23-87 -3.0/2.2.1

- 72 - The Santa Cruz Operation

Operating System Release Notes
not conflict with the standard COM ports.
Try attaching the printer to a standard
serial port, COMl or COM2, to see if the
printer and cabling is correct.

When you get the date printed on your printer, you
should run letclZpinit to configure the spooler to
support this printer. (See Chapter 7 of the XENIX
Operations Guide for more information on
letcIZpinit.) Then be sure to enter the correct stty(C)
options in the spooler's interface script
(IusrlspooZIZplinterjacelprintername) to control the
baud rate, XON/XOFF protocol, and other options
as necessary. The baud rate and XON/XOFF
protocol should match the baud rate set on your
printer.

PROBLEM: How can I get my terminal type set
automatically when I login?
REMEDY: XENIX can be easily configured to automatically
set the terminal type upon login by following these
procedures:

Login as root and edit the file letclttytype with a text
editor. Change the terminal type field for the line
associated with the tenninal in question to the
terminal type you desire to use. Follow the model
for the console. If you want your terminal type to be
set to 'wy50' for Idevlttyla, edit letclttytype as
follows:
wy50 ttyla

Then the user's start up file must be edited with the
appropriate tset(C) command line to automatically

XG-03-23-87-3.0/2.2.l

- 73 - The Santa Cruz Operation

XENIX for Personal Computers
set the terminal type. In each C-shell user's .login
file, add the following line:
tset -s -0 > Itmp/tsetS$; source Itmp/tset$$; Ibin/rm Itmp/tsetS$

Be sure the remove the default setenv(C) command

line involving TERM and TERMCAP from the
. login file.
In each Bourne Shell user's .profile, add the

following line:
eval 'tset -s'
Be sure to remove the existing tset command line
from the .profile file.
D.

Have each user logout, then login again to test the
new terminal type change. After login, have them
verify the new termtype by typing:
env

){(J-03-23-87-3.0/2.2.1

- 74- The Santa Cruz Operation

3-3-87
018-030-016

The XENIX® System V
Operating System

Installation Notes
Version 2.2 Update A

The Santa Cruz Operation, Inc.

Information in this document is subject to change without notice and does
not represent a commitment on the part of The Santa Cruz Operation, Inc.
nor Microsoft Corporation. The software described in this document is
furnished under a license agreement or nondisclosure agreement. The
software may be used or copied only in accordance with the terms of the
agreement. It is against the law to copy this software on magnetic tape, disk,
or any other medium for any purpose other than the purchaser's personal
use.
ALL USE, DUPLICATION, OR DISCLOSURE WHATSOEVER BY
THE GOVERNMENT SHALL BE EXPRESSLY SUBJECf TO
RESTRICTIONS AS SET FORTH IN SUBDIVISION (b) (3) (ii) FOR
RESTRICTED RIGHTS IN COMPUTER SOFTWARE AND
SUBDIVISION (b) (2) FOR LIMITED RIGHTS IN TECHNICAL
DATA, BOTHAS SET FORTH IN FAR 52.227-7013.

Portions @ 1983, 1984,1985, 1986, 1987 The Santa Cruz Operation, Inc.
All rights reserved.

This documentwastypesetwith an lMAGEN® 8/300 Laser Printer.
The Bernoulli Box is a registered trademark of IOmega Corporation.
Compaq Deskpro and Plus are trademarks of Compaq Computer
Corporation.
COREtape is a trademark of CORE International.
FoxBA SE is a trademark of Fox Software, Inc.
mM PC XT and PC AT are registered trademarks oflnternational Business
Corporation.
IMAGEN is a registered trademark ofIMAGEN Corporation.
Lyrix is a registered trademark of The Santa Cruz Operation, Inc. MS-DOS
is a registered trademark of Microsoft
QuadPort is a trademark of Quadram.
PC's LIMITED AT is a trademark of PC LIMITED.
Tecmaris a trademark of Tecmar, Inc.
un ifA TH is a trademark ofPathl"ayDesigns, Inc.
UNISYS is a trademark of the UNI SYS Corporation.
XENIX is a registered trademark of Microsoft Corporation.
DocumentNumber: XG-4-3-87-3.0.2/2.2

Processed Date: Mon Apr 610:26:59PDT 1987

Update A Operating System
Installation Notes

1. Preface

1.1 What You Need
1.2 Your Options

1
3

1.3 Deciding to Update or Re-install
1.4 Option 1: The Update

1.5 Options 2 and 3: Re-installation 5
1.5.1 About fdisk Partitions 5
1.5.2 Complete Re-installation 6
1.5.3 Partial Re-installation 7
1.6 Clearing Disk Space for the Update

8·

1.7 User-ConfigurableFiles and the "Update" Option
2. Update Procedure

3. Preserving Existing Filesystems 27
4. User-Configurable System Files 29

Installation Notes
Update A
XENIX System V for Personal Computers
Operating System
April 3, 1987

1. Preface
You should have Release 2.1 or later of the SCO XENIX System V
Operating System installed on your computer to use this update.
Update A allows you to upgrade your system to match SCO XENIX
System V Release 2.2 functionality. These notes contain installation
instructions for your update procedure and are organized as follows:
•

Update Procedure

•

Preserving Existing Filesystems

•

User-configurable System Files

1.1 What You Need
We recommend that the person who installed your system also
perform this update because they will be the most familiar with
XENIX and your filesystems. For instance, The update requires 1300
blocks of free space on your hard disk. This implies that you must
know how to free up space if your disk is full. Although these
Installation Notes instruct you on how to do this, you should already
be familiar with basic aspects of system maintenance.
In particular, you need to have a good working knowledge of the
following:

•

tar( C) . You will be asked to back up certain files on your
system. Although the update disk provides a utility to do
most of this for you, you must know how to use tar (or your
usual backup utility) to back up your non-root filesystems

XG-04-03-87 -3.0.2/2.2

- 1 - The Santa Cruz Operation

(such as/u).
•

custom(C). During the update process you may be directed
to use custom to install various packages of the Operating
System set. custom is an interactive installation utility that
is used to install selected sets of the Operating System,
other XENIX sets and various products. H you are not
familiar with custom, please read the manual page and
familiarize yourself by removing unused Operating System
Packages from your system.

•

vi(C) or other file editor. You may be asked to merge certain
files that contain information used by the system. Some of
these files are different under 2.2 and you will need to
combine your existing information with the new files.

Read the entire procedure and make certain you understand each
step before performing the update.
In addition, do not abort the installation process, for example, by
using the DEL or Ctrl-\ keys. H you must stop because you enter
incorrect information or for some other reason, start the process
again rather than trying to proceed from the stopping point.

Do not change any files or directories created by the update.

Note
If you have SCO XENIX-NETTM and/or SCO uniPATHTM
SNA-3270 installed on your system, you must have XENIXNET release 1.1.1 or later and SNA-3270 release 1.2.0 or
later to use them with this update. H you have an earlier
revision of these products, please contact your supplier and
obtain a new release. If you perform this update with
obsolete revisions, they will not function ~operly.
Applications such as SCQ LyrixR, SCQ FoxBASE ,etc.,
are completely compatible with XENIX System V Operating
System Release 2.2.

XG-04-03-87-3.0.2/2.2

- 2 - The Santa Cruz Operation

Update A Operating System

1.2 Your Options
There are three ways to install the update. Regardless of which you
choose, you must perform these tasks first:
•

Clear space for the update if necessary. (1.6)

•

Reboot and run backup portion of Update procedure.
(Steps 1-9 of Update procedure.)

The numbers refer to sections of these notes concerned with each
task.
Here is a summary of each of the three options, including the
additional steps to be performed (each is explained in the sections
that follow):
Update. Run the update as described in the Update procedure. This
updates all Operating System files with 2.2 versions without affecting
user-created files or2.1 filesystems.
•

Follow Update procedure (2.0)

•

Perform any necessary file merges (4.0)

•

Re-install applications or device drivers using custom

Partial Re- installation. Back up all files on the fdisk partition that
contains the root filesystem, perform a standard 2.2 installation and
preserve any 2.1 file systems on independent (non-root) fdisk
partitions.
•

Back upnon-rootfilesystems (1.5)

•

Preserve your existing file systems (3.0)

•

Perform normal installation (Chapter 2 of Installation
Guide)

•

Re-install applications

XG-04-03-87 -3.0.2/2.2

- 3 - The Santa Cruz Operation

XENIX

for Personal Computers

Complete Re-installation. Back up all filesystems and perform a
standard 2.2 installation (as if installing for the first time).
•

Back up non-root filesystems (1.5)

•

Perform normal installation (Chapter 2 of Installation
Guide)

•

Re-install applications

1.3 Deciding to Update or Re- install
There are basically two considerations to weigh when deciding
whether to re-install or update your system: The update option has
been designed to save you the effort of re-installation by performing
all necessary backups, preserving all user-configurable files, and
replacing only those elements of your 2.1 Operating System that have
changed. However, two 2.2 enhancements will not be available on a
system which has been updated. These are:
•

Extended Badtracking

•

Non-standard Disk Support

These may not present a problem; if the number of bad tracks on
your hard disk is not high and you have no need for non-standard
disk support, the update is probably the best option for you. The
third option has been made available for those who have certain
filesystems to preserve, but still must perfonn a re-installation. For
all three options, the update disk includes a utility to perform a
backup of your user-configurable files and all files in in the root
filesystem that are unique to your system. It is absolutely essential
that you perform this backup if you are re-installing, whether partial
or complete. In either case, it is also necessary to back up all nonroot filesystems that are on the same fdisk partition as the root
filesystem. You should do this with your accustomed backup
method; the update script will not back up these files for you.

XG-04-03-87 -3.0.2/2.2

- 4 - The Santa Cruz Operation

Update A Operating System

1.4 Option 1: The Update
If you choose to perfonn the update, you can ignore section 3 of
these notes.

The "Update" is divided into two stages. The first begins when you
enter "update" at the Boot: prompt (Step 2), while the second begins
with entering "install" at the Boot: prompt (Step II). If you have not
completed the first half, (Le. reached St,ep II) you must start again at
Step 2 of the Update procedure. If you pass Step 11 successfully,
from then on you should restart from that point. If you start over,
note that operations which previously completed successfully are not
repeated.}

1.5 Options 2 and 3: Re- installation
These two options have several elements in common. It is important
to have a complete backup of all the files that are unique to your
system (files that are not part of a product or other standard
distribution). The update script will back up most of these for you.
The script does not back up non-root filesystems. (/u is an example
of a non-root filesystem.) These filesystems should be backed up
using your usual method, regardless of whether you are performing a
partial or complete re-installation.
The complete re-installation option is for those who have no
filesystems on separate fdisk partitions. The partial option is for
those who do have file systems on separate fdisk partitions (or a
second hard disk). The section that follows explains this distinction.
1.5.1 About fdlsk Partitions

fdisk(C} is a utility used to partition the hard disk so that different
operating systems occupy distinct sections of the hard disk, just as
DOS and XENIX might on your system. Only one partition may be
active at at time. Your system probably has a single partition for
XENIX.

If you have more than one XENIX partition that is capable of
booting, each partition must be activated in turn and updated.

XG-04-03-87 -3.0.2/2.2

- 5 - The Santa Cruz Operation

XENIX for Personal Computers

To check the number of partitions on your hard disk, log in and enter
the following command:
fdisk
This menu is displayed:
1.
2.
3.
4.
5.

Display Partition Table
Use Entire Disk for XENIX
Create XENIX Partition
Activate Partition
Delete Partition

Enter your choice or 'q' to quit:
Select "I" and you see a table similar to this:
Current Hard Disk Drive: Idev/rhdOO

Total disk size: 1220 tracks (5 tracks reserved for
masterboot and diagnostics)
Press to continue

1.5.2 Complete Re-lnstallatlon

You probably have a single XENIX partition. If so, any filesystems
you have are located on the same partition as your root filesystem,
and it is necessary to account for them when you re-install. Before
you begin the installation, write down the names and sizes of the
filesystems in question. Use the diny(C) utility to obtain this
information:
divvy -c 1 -b 1
divvy(C) displays a table similar to this one:

XG-04-03-87 -3.0.2/2.2

-6-

The Santa Cruz Operation

Update A Operating System

Name

New File System?

First Block

Last Block

root
swap

no, exists
no, exists
no, exists
no
no
no
no, exists
no

0
1
2
3
4
5
6
7

0
13755
15136

13754
15135
25135

recover
d1057all

25136
0

25145
25546

You need to duplicate the entries for your filesystems when you reinstall.
During the actual installation procedure, you will be prompted for
the following:
Do you require block by block control over the layout
of the XENIX division?
You must respond "y" and re-create file systems at least as large as
your original ones, so that your backups will fit within the space
allocated.
First, back up your system files by following steps 1-9 of the
procedure described in section 2 of this document. Next, back up
your non-root filesystems. Finally, you should perform a normal
installation as described in Chapter 2 of the Installation Guide.
1.5.3 Partial Re-lnstallatlon

If you have other filesystems on separate fdisk partitions or a second
hard disk, then you should perform a partial re-installation, follow
the instructions above, but refer to Section 3: "Preserving Existing
Filesystems" after performing your backups and prior to the reinstallation. This will allow you to retain your filesystems that are on a
different fdisk partition from the root filesystem. When you see the
fdisk menu mentioned earlier, you must enter "q" if you wish to
preserve the current partition table. You must NOT select option
"2" , or you will wipe out all of the data on your hard disk. If you enter
"2", a message will warn you and ask if you wish to continue.

XG-04-03-87 -3.0.2/2.2

- 7-

The Santa Cruz Operation

XENIX for Personal Computers

Note
Concerning applications:
You should re-install certain applications following the
update. Do this in single user mode. Some products, such
as SCQ XENIX-NET, SCQ uniPATH SNA-3270, and
Installable Device Drivers (IDDs) , include device drivers
which are added to the XENIX kernel during installation.
Despite the fact that these files will remain on the system
after the update, the 2.2 kernel will not contain the
infonnation required to use these products. Re-installation
will ensure that your products will function properly.
Some products may be installed using custom(C) (i.e.
SCQ XENIX-NET, SCQ uniPATH SNA-3270 and any
IDDs). Please refer to the installation instructions for
each product.
A new feature of SeQ XENIX System V Release 2.2 is
standard support for cartridge tape drivers; third party
drivers for these devices are no longer necessary. Use
mkdev tape to install a cartridge tape driver, mini cartridge
tape driver or other supported tape driver.
Some products must be at a specific release level to
function properly with SeQ XENIX System V Release 2.2.
Check with your supplier if you are unsure as to whether
you have the correct release. Remember, releases of
XENIX-NET and uniPATH SNA-3270 prior to 1.1.1 and
1.2.0, respectively, will not function with 2.2 and you must
obtain a new release before installing this update.

1.6 Clearing Disk Space for the Update
It is very important to remove any unnecessary files from your system
before beginning the update. Some files might be removed
altogether, while others, such as those kept as records only, and
those which are referenced only occasionally might be archived,

XG-04-03-87-3.0.2/2.2

- 8-

The Santa Cruz Qperation

Update A Operating System

(backed up and stored on tape or disk) and then removed. Some
examples might be: outdated mail, LOG files generated by programs
such as uucp or micnet, directories of users that no longer use your
system, files in Itmp, etc. (The directories of former users may be
deleted by using nnuser after they are emptied.) If you have
Operating System packages installed which are no longer used or
needed, you should remove them with the custom(C) utility prior to
performing the update.
The update requires a minimum of 1300 free blocks to work
correctly. If this space is not available, the update will terminate and
you will be instructed to create free space by removing files. Most of
the packages in the Operating System have increased in size from
release 2.1 to 2.2. The amount of space you will need depends on
what you install. If you install only the Run Time System, most of the
space used by the update will be available again after completion of
the update. Therefore, you may want to back up selected files,
remove them from the system and restore them when the update is
complete. To see how much disk space is available on your system,
use the following command:
df -v /dev/root
Since packages of the Operating System have increased in size in
XENIX 2.2, the update will first attempt to re-install the packages
that were previously installed on your system. If there is insufficient
space, the update will give priority to packages that include userconfigurable files in order to preserve any changes you may have
made. If the disk space is still insufficient, or if no packages
containing user-configurable files were installed on your system,
then you will be given the option to use the custom( C) program to
indicate which packages are most important to re-install
immediately. You will find list of packages containing userconfigurable files at the end of Section 4. Following the update, you
can remove more unnecessary files and re-install more packages
using custom.

1.7 User- Configurable Files and the "Update" Option
User-configurable files are those files of the XENIX Operating
System set that are routinely modified by users or by programs run by
users. Some of these user-configurable files have not changed in 2.2,

XG-04-03-87-3.0.2/2.2

- 9 - The Santa Cruz Operation

XENIX

for Personal Computers

and these files are preserved in their original locations by the update.
Others have changed either in format or default content. Your 2.1
versions of these files will be saved so that any changes made on your
system can be incorporated into the 2.2 versions of these files.
Where possible, these changes will be made automatically for you
during the update. Refer to Section 4 for more information on user
configurablefiles in the Operating System.

2. Update Procedure

Note
Certain steps of this procedure are alternative events that
apply only when two or more different messages may be
displayed. These "sub - steps" are clearly labeled with a, b,
or c. You must select the step to be followed by matching
the message displayed on your system. After following the
instructions for the sub-step selected, proceed to the next
regular step.

To install Update A, follow these steps:
1.

Login as root (super-user) and shut down the system. Be sure
and inform all users that the system will be unavailable for
sometime.

Insert volume N1, reboot the system and type "update" at
the Boot: prompt.

XG-04-03-87 -3.0.2/2.2

- 10 - The Santa Cruz Operation

Update A Operating System

Note
If you see this message at any point during the update process:

During installation you may choose to overwrite all
or part of the present contents of your hard disk.
Do you wish to continue? (yIn)
You have made a mistake; you hit RETURN at the boot
prompt rather than entering "update" or "install". Respond
"n" to the above query and reboot your system. Make certain
that you enter "update" or "install" at the Boot: prompt as
appropriate.

The following message is displayed:
Insert Update volume 1 and press

Press RETURN as directed. The following message is
displayed, along with pertinent fsck messages about your
filesystem:
Checking root filesystem ...

The program first checks for free space. You must have at
least 1300 blocks (650 Kbytes) free in order to perform the
update. If you see a message indicating that you have
insufficient space, you must stop, reboot the system
normally and back up or remove some files. This free space
is needed only for the update process and will be available
again after the update is complete. The total amount of
space needed to update your system depends on what you
have installed. Any user files can be stored on removable
media (floppy), removed from the hard disk for the duration
of the update, then restored afterward.

XG-04-03-87 -3.0.2/2.2

- 11 - The Santa Cruz Operation

XENIX for Personal Computers

The update script now checks your system for data files that
contain lists of constituent files from the previous release. If
any of the necessary files is missing, you will see an
appropriate "Warning:" message, the system will halt, and
you must boot normally in order to install the necessary files.

5a.

If you have an updated XENIX 2.0 system, and the file
fetc/base.perms is missing, you see the message:
Warning: certain files needed for the update are not installed.
If you are running an updated 2.0 system, extract the file
Jetclbase.perms from your 2.0 distribution media. If you are
running a 2.1 system, extract the files Jete/in st. perms,
Jetc/rts.perms, and /etc/ext.perms from your 2.1 distribution
media. Refer to your Update documentation for your instructions.

Extract the file /etc/base.perms by inserting 2.0 Floppy
Number 1 from your 2.0 distribution, and entering the
following commands:
cd /
tar xv ./etc/base.penns
Shut down your system, insert 2.2 volume Nl and reboot,
resuming the update from the beginning (Step 2). Then
proceed to Step 6.

5b.

If you have a 2.1 system and any of the files /etc/inst.perms,
/etc/ext.perms, and /etc/rts.perms are missing, then you see
the message:

){(}-04-03-87-3.0.2/2.2

- 12 - The Santa Cruz Operation

Update A Operating System

Warning: The files fetclinst.perms, fetc/ext.perms,
fetcfrts.perms are not all installed. Reboot your system
and invoke:
custom

-0

Use your previous XENIX OS floppies for this step. custom
will prompt for the required volumes. When the main custom
menu appears (with options to install or remove packages),
select quit. Then resume the update procedure.

If they are all missing, then you see:
Warning: certain files needed .for the update are not installed.
If you are running an updated 2.0 system, extract the file
fetcfbase.perms from your 2.0 distribution media. If you are

running a 2.1 system, extract the files fetc/inst.perms,
fetc/rts.perms, and fetc/ext.perms from your 2.1 distribution
media. Refer to your Update documentation. for your instru~tions.

If /etc/inst.penns is missing, then it must be extracted first.
You cannot use custom -0; instead you must insert volume
N1 of your XENIX 2.1 distribution and enter the following
commands: (If you have a 96 tpi distribution, replace fdO
withfd096)

mount -r /dev/fdO Imnt
cp Imnt/etc/inst.perms letc
umount fdev/fdO
When /etc/inst.perms is in place, letclrts.perms and
fetc/ext.perms maybe extracted using custom -0, which will
restore the data files automatically. Select "q" at the
installation menu as instructed above. Shut down the
system, insert 2.2 volume N1 and reboot, resuming the
update from the beginning (Step 2). at the Boot: prompt.
~.

You see the following:

XG-04-03-87 -3.0.2/2.2

- 13 - The Santa Cruz Operation

XENL~

for Personal Computers

You will now have the opportunity to backup any files on your
system that are not on the XENIX distribution. This option is
precautionary if you are updating, essential if you are re-installing.
Please refer to your Update documentation for a description of your op

The following menu is displayed:
1. Backup con.figurable system files and user files
011 the root filesystem.
2. Continue update.
Enter an option:

Enter "1" and press RETURN. A list of all files on the root
filesystem which will not be updated by the 2.2 distribution is
then created. This is a time-consuming process; the system
displays a message to that effect. When it is complete you see
the message:
A script has been created in /etc/update.backup to
backup your important system files. After the system has
been shut down, reboot your standard 2.1 environment in
system maintenance (single user) mode and run the script:
I etc/update.b ackup
AFTER you see the message: ••• Normal System Shutdown
reb oot the system by opening the floppy door and pressing
any key. The screen will clear and you will see the boot
message:
Boot

Press to boot otT the hard disk.

XG-04-03-87-3.0.Z/Z.2

- 14 - The Santa Cnlz Operation

Update A Operating System

Reboot as instructed and enter single user mode. Run the
backup script by entering:
I etc/update. backup

You see the following message:
Enter full name of raw media device
you would like to use (or q to quit):

Respond with the appropriate device, for example
/dev/rfd096dsI5 for the high density floppy drive. If the
information on the device selected does not appear in
/etc/default/tar, you are prompted for the volume size and
the blocking factor. The next prompt is:
You will be expected to insert formatted media.
Do you wish to continue? (yIn)

If you enter "n", the script will exit. Restart the script after
you have a supply of formatted media.
If you enter "y" you see:
You will be prompted for new media as needed.
Insert the first volume and hit any key to continue:

When complete, you see:
The safety backup of your system is complete.
Shutdown the system, and restart the update process.

You can use tar(C) to restore any files from the backup. If

XG-04-03-87 -3.0.2/2.2

- 15 - The' Santa Cruz Operation

XENL,,{ for Personal Computers

you use a cartridge tape as your backup medium, you will
need to re-install your cartridge tape driver prior to restoring
from the backup.
9.

You now have three options:
a) Hyou are perfonning the "Update," shutdown the system
and boot offN1, typing "update" at the Boot: prompt.
b) H you are performing a "Partial Re-installation," (you
wish to save 2.1.3 partitions) back up all non-rootfilesystems
and proceed to Section 3 and follow the instructions.
c) H you are perfonning a "Complete R~,..instaIlation," (not
saving partitions) back up all non-root filesystems and
proceed to the standard 2.2 Installation Procedure in
Chapter 2 of the Installation Guide.

10.

The update menu is displayed again:
1.

Backup configurab Ie files and user files
on the root filesystem.
Continue update

Enter an option:

Enter "2" and press RETURN. You see the messages:
Assessing currently installed system ...
Saving user configurable files ...
You will not be able to boot your old version of XENIX after this
stage of the update without re-installing.
Preparing root filesystem for update installation ...
Checking root filesystem and re-ordering free list ...

XG-04-03-87 -3.0.2/2.2

- 16 - The Santa Cruz Operation

Update A Operating System

Certain fsck messages are displayed, such as "FILE SYSTEM
WA S MODIFIED." This is nonnal. Next, you see:
AFTER you see the message: ' •• Normal System Shutdown •• '
reboot the system by removing volume UAl, inserting volume Nl,
and pressing any key.
The screen will clear and you will see the boot message:
Boot
Type 'install' after the colon and press

11.

The system will now shut down; insert N1, press any key and
type 'install' at the Boot: prompt as instructed.

Note
If you stop the update at any subsequent point, restart from
step 11.

12.

The following message is displayed:
Installing Run Time System ...

You will first be asked for N1, B1 and Xl in order to install
the necessary data files. Next, you will be asked for all the B
volumes and some of the N volumes. Follow onscreen
instructions. You will see the following message, which can
be ignored:
fixperm: bad format executable file: .Jete/getty

XG-04-03-87 -3.0.2/2.2

- 17 - The Santa Cruz Operation

XENIX for Personal Computers

13.

The following message is displayed:
Operating system serialization.

You are then prom pted for your serial number and activation
key. Enter them as instructed.
14.

The next display is:
The XENIX 2.2 Run Time System has been installed.

14a.

If there is enough space on your system to restore all
packages that were previously installed, you see:
You may now choose to install those packages that were
previously installed on your system. It is b est to
re-install these packages now, because the update will
correctly restore the user configurable files. The
following packages appear to have been installed on
your XENIX system prior to this update:

You see a list of Operating System packages previously
installed on your system.

Do you wish to install these packages now? (yIn)

Respond "y" and press RETURN. If you do not choose to
install the packages at this time, the user-configurable files
from these packages that have been preserved by the updat~
will be overwritten by 2.2 versions, unless you take the
precaution of backing up these files ahead of time. Proceed
to step 15.
14b.

If you do not have sufficient disk space to restore all of the
previously installed packages, you see:

XG-04-03-87 -3.0.2/2.2

- 18 - The Santa Cruz Operation

Update A Operating System

Due to the increased size of the Run Time System, and
other packages, it is not possible to re-install all
of the packages that were previously installed on your
system during this update. When the update is complete,
you may choose to remove more unnecessary files, and
install additional packages.

If there is sufficient disk space to restore those packages
which contain user-configurable files, then you see:
There is enough space available on your system to
install those packages that contain user-configurable
files. It is best to re-install these packages now,
because the update will correctly restore the user
configurable files.

Two lists are displayed: the first contains the packages that
cannot be re-installed at this time, the second contains
packages which include user configurable files that can be
re-installed.
Do you wish to install these packages now? (yin)

It is recommended that you re-install the packages with
user-configurable files now. Respond "y" and proceed to
step 15.

14c.

If there is insufficient disk space for all of the packages
containing user-configurable files or if none were originally
installed, you see:

XG-04-03-87-3.0.2/2.2

- 19 - The Santa Cruz Operation

XENIX for Personal Computers

If there were packages with user-configurable files installed,
they will be listed separately from the other packages, and
you will be advised to install them first. If packages with no
user-configurable files were previously installed, only one list
will be printed. Next, you will be asked:
Do you wish to install any packages now? (yIn)

If you select "n", the update will continue. If you select "y",
custom will be invoked. It is advisable to try and install the
packages one at a time in order of importance until custom
reports that there is no disk space available. At that point you
should respond "n" to the prompt:
Do you wish to continue? (yIn)

Note
If csh(C) or vsh(C) were installed, it is important to re-install
them so that users. who have one of these shells as their login
shell will be able to log in.

At the time you re-install all remaining packages, (after the
update) be sure to back up any user-configurable files from

XG-04-03-87 -3.0.2/2.2

- 20 - The Santa Cruz Operation

Update A Operating System

packages that you were unable to install during the update.
Lists of these files are in the directory Itmp/update and
discussed further in Section 4 of these notes.
15.

The system prompts for the insertion of necessary volumes.
You see messages indicating the installation of the packages
indicated. The next message displayed is:
The following user-configurable files from your XENIX
system have not changed in format in XENIX 2.2. Your local
modifications, if any, have been preserved, and these
files are in their correct locations.
This list of files will also be in /tmp/update/config.list.
(press each time you hear a bell)

A list of your user-configurable files is displayed. Next, the
message "Re-checking file permissions ... " is displayed.
You may also see messages about "not empty" files. Do not
be alarmed; this indicates that your old files were preserved
correctly.
16.

After the first list of files has been restored and checked, a
similar message is disp layed:

XG-04-03-87 -3.0.2/2.2

- 21 - The Santa Cruz Operation

XENIX for Personal Computers

The following user-configurable files from your XENIX
system require minor changes in either content or format
for use with XENIX 2.2. You will want to incorporate
your local modifications, if any, into the new files.
Some files will be modified automatically, if possible.
Refer to your Update documentation for more information
on the merge process.
Your original files have been saved for reference. They are
each located in the appropriate directory, but their names
have been appended with "2.1". For example, letc/termcap
from your system will be in letcltermcap2.1, and the new
version in letc/termcap.
This list of files will also be in Itmp/update/merge.list.
(press each time you hear a bell)

A list of files to be merged is displayed. Then the message:
Merging selected user configurable files ...

The system then automatically merges some of the files
listed, combining your existing data with the fonnat changes
made to 2.2. Some of the files listed will have to be merged
manually. As each file is updated, a corresponding message
appears. Should an error message appear, such as
"/etc/default/boot not merged", continue with the update,
but you will have to merge any files that appear in error
messages as well. Messages beginning with "Warning:" may
not require any action, unless accompanied by messages
beginning with "Error:". When you complete the update
process as outlined in this section, proceed to Section 4 of
these Installation Notes for instructions on how to perfonn
any necessary merges manually.
17.

The system will now set timezone variables just as in anonnal
installation. You see:

XG-04-03-87 -3.0.2/2.2

- 22 - The Santa Cruz Operation

Update A Operating System

Time zone initialization
Are you in North America? (yIn)

If you enter 'y' , you see this menu:
1.
2.
3.
4.
5.
6.
7.
8.

AST
EST
CST
MST
PST
YST
HST
NST

Atlantic Standard Time
Eastern Standard Time
Central Standard Time
Mountain Standard Time
Pacific Standard Time
Yukon Standard Time
Hawaiianl Alaskan Standard Time
Nome Standard Time

Enter the number that represents your time zone or enter q to quit:

Enter the appropriate number and press RETURN. If you
are in North America, you are asked:
Does daylight saving time (summer time) apply at your location? (yIn)

If you are not in the United States (or one of the time zones
represented above), and entered "n", the following is
displayed:
What is the abbreviation of your standard time zone? Enter
1-9 characters or enter 'q' to quit

Enter the abbreviation for your time zone and press
RETURN. Next you see this message:

XG-04-03-87 -3.0.212.2

- 23 - The Santa Cruz Operation

XENIX for Personal Computers

How many hours west of Greenwich Mean Time are you?
Enter hh[:mm:ss] (eg 10:30:00 or 10:30, use negative
numbers for locations east of GMT) or enter 'q' to quit.

Answer with a number between -24 an 24, then press
RETURN.
Next you see:
Does summer time (daylight saving time) apply at your location? (yIn)

If daylight saving/standard time changes occur in your area,
enter 'y'. If not, enter 'n'. If you answered yes, after you
press RETURN, you see:
What is the summer abbreviation of your time zone?
Enter 1-9 characters or enter 'q' to quit

You now specify the use of daylight saving time in your area.
You select the dating method used in your area to switch
between standard and daylight time. You see the following
menu:
1. Week of the year (1-52).
2. Week of a specific month (eg. 1st week of April).
3. Day of year, ie. Julian date (1-365).

Select the method your time zone uses to convert
from standard time to summer time (daylight saving time)
or enter 'q' to quit.

If your time zone changes on a specific week, choose option
1. If it switches on a specific week of a specific month,
choose option 2. If it switches on a specific day of the year,
choose option 3. Enter the appropriate response as
prompted and press RETURN. Next you see:

XG -04 -03 -87 -3.0.2/2.2

- 24 - The Santa Cruz Operation

Update A Operating System

At what time of day is the conversion made (use 24 hour clock)?
'Enter hh[:mm:ss] or press RETURN for default value of 2 am.
or enter 'q' to quit

You then see a similar menu asking when your time zone
reverts back to standard time:
1. Week of the year (1-52).
2. Week of a specific month (eg. 1st week of April).
3. Day of the year, ie. Julian date (1-365).
Select the method your time zone uses to convert from
summer time (daylight saving time) to standard time
or enter 'q' to quit.

Enter the appropriate number and respond to the prompts as
directed. You then see:
At what time of day is the conversion made (use 24 hour clock)?
Enter hh[:mm:ss] or press RETURN for default value of 2 am.
or enter 'q' to quit.

Enter the appropriate date when your area shifts back to
standard time. Next you are prompted for the number of
hours to shift for daylight time:
How many hours does your timezone adjust for summer time
(daylight saving time)?
Enter hh:mm:ss or press RETURN for the default value of 1 hour
or enter 'q' to quit.

Most time zones ad just one full hour for daylight saving time.
The time zone variable, TZ, in the file letclde!aultllogin is
changed accordingly. Your time zone is now set. There is no
need to change the .profile unless you want to override the
local standard.

XG-04-03-87 -3.0.2/2.2

- 25 - The Santa Cruz Operation

XENIX for Personal Computers

18.

The following message is displayed:
All of the applications and other XENIX sets that were
installed on your system are still installed under
XENIX 2.2. However, some applications and devices must
be reinitialized, or re-installed using releases that are
compatible with 2.2. These applications and devices
should be re-installed while in single user mode following
the completion of the update. Reboot your system as
instructed below, enter system maintenance (single user)
mode, and follow the instructions included with your
applications.
Further explanation is available in the Update documentation.
If you have not already carefully read the section
of your Update documentation pertaining to re-installation
requirements, please do so before continuing.
Press when you are ready to continue:

Press RETURN after you have read the messages. Next, the
following messages are displayed:
AFTER you see the message: '** Normal System Shutdown **'
reboot the system by opening the floppy door and pressing any key.
The screen will clear and you will see the boot message:
Boot

Press to boot off the hard disk

The system will then shut down. Follow the reboot
instructions in the" AFTER" message above.
19.

Go into single user mode (your root password has been
preserved) and perform the required file merges as described
in Section 4. Ensure that all your files are intact and in their
proper locations. If necessary, you can use your backup

XG-04-03-87 -3.0.2/2.2

- 26 - The Santa Cruz Operation

Update A Operating System

floppies to restore user files. Refer to tar(C) for instructions
on restoring from your archive media. If you use a cartridge
tape as your backup medium, you will need to re-install your
cartridge tape driver prior to restoring from the backup.
20.

Finally, while still in single user mode, install any
applications or device drivers using custom (see the note that
follows Section 1.5.3).

Note
When you enter custom following the update, any packages
that were not re-installed may appear to be partially installed
(labeled "Part" in the menu). This is due to the preserved
user configurable files and directory structures.

3. Preserving Existing Filesystems
The following procedure is used to preserve existing XENIX 2.1
filesystems. This is to be performed in conjunction with a partial reinstallation. These steps are applicable to one or more filesystems on
your primary disk" or on an additional hard disk.
Note that the filesystems cannot be in the fdisk partition in which you
are going to install XENIX. You can only preserve a filesystem that is
in a different fdisk partition. Filesystems in the same partition as the
root filesystem must be backed -up, re-created and restored.
1.

Use the Is -I command to find the pertinent information
about the filesystem you want to preserve, such as
permissions, links, owner and group, major and minor
device numbers, and the name of the file system .
For example, if you want to preserve a filesystem named /u,
enter:

XG-04-03-87-3.0.2/2.2

- 27 - The Santa Cruz Operation

XENIX for Personal Computers

Is -I Idev/u Idev/ru
You see something like this:
brw-r----- 1 sysinfo
crw-r----- 1 sysinfo

sysinfo
sysinfo

1, 104 Dec 1904:17 Idev/u
1, 104 Dec 15 17:34/dev/ru

In this example, the filesystem on the first line is described in
the following manner: "b" is the device type (block or
character), "sysinfo" is the owner, "I" is the major device
number, "104" is the minor device number, and" I devlu" is
the name of the device.

Repeat the Is -I step for every
preserve.

file~ystem

that you want to

Write down all of the information that you see. Remember,
you cannot preserve any filesystems that are in the fdisk
partition containing the root file system (location of OS
installation).
2.

Finish reading the Release Notes for other information
pertinent to installing your operating system. Then, install
XENIX 2.2. Follow the instructions in Chapter 2
"Installation Procedure," of the Installation Guide.

After you have installed XENIX 2.2, enter single user mode.
If the file systems you want to preserve are on the same hard
disk as the one on which you installed XENIX, skip to the
next step.
If the filesystems you want to preserve are on a second hard
disk, enter this command:

cd I
letc/fixperm -dHDl -s letc/inst.perms
4.

While still in single user mode, use mknod to create device
nodes for the filesystem(s) you want to preserve. For
example, use these commands to create device nodes for the
lu directory described in the example above:

XG-04-03-87-3.0.2/2.2

- 28 - The Santa Cruz Operation

Update A Operating System

mknod b
mknod c
Example:
letc/mknod Idev/u b 1 104
letc/mknod Idev/ru c 1 104
5.

Then, make sure these device nodes have the correct
permissions, owner and group. For example, for the lu
filesystem previously described:
chmod 640 Idev/u Idev/ru
chown sysinfo Idev/u Idev/ru
chgrp sysinfo Idev/u Idev/ru

You have now preserved your existing filesystems. Use the
mkdev command to ensure that the filesystems you
preserved are correctly set up.
letc/mkdev fs Idev/u lu
In this example, the lu directory will be created at the mount
point for Idev/u, along with a lost+found directory to
facilitate cleaning the filesystem. You will also be asked if
you wish to have this file system mounted automatically when
the system starts up multiuser.

To mount and unmount the file system , enter these
commands, respectively:
mount Idev/u lu
umount Idev/u

4. User- Configurable System Files
This section contains instructions for merging 2.2 distribution files
with their 2.1 counterparts. Listed below are files which have
bhanged for 2.2 but may contain system-specific information you
wish to preserve. Copies ofyouT 2.1 versions of these files have been
left in their corresponding directories, under the name: ftlenanle2.1.

XG-04-03-87 -3.0.2/2.2

- 29 - The Santa Cruz Operation

XENIX for Personal Computers

If you have not made any modifications to a particular file, you need
not make any changes to the new/version.

Online copies of the list of files specific to your system can be found
in Itmp/update in merge .list and config. list .
You will need to use a text editor, such as vi(C) or SCO Lyrix, in
order to make the described changes. In order to determine which
lines have changed in a file, the utilitydiff(C) is useful. Please be sure
to review the following guidelines before making any changes. Some
changes are necessary to ensure correct functionality with the 2.2 OS.
If any of the 2.2 distribution files are incorrectly modified, unedited
versions can be retrieved from the distribution media using custom.
•

/etc/default/mkuser
New options are available. If you previously modified the
HOME setting, make the same modification to the new file.

•

/etc/default/tar
New devices have been added to the possible defaults and a
third column has been added (which indicates whether the
choice is a tape device). The 2.1 file format is supported,
but you should be sure your modified defaults are still valid
device names. For example, the standard, supported
cartridge tape device is called IdevlrctO. New features of
applications which use information in the third column may
not be available if you install your2.1 version in place of the
2.2 version.

•

/ etc/gettydefs
Since XENIX OS 2.2 supports 8-bit data paths, all settings
in this file include the stty flag CS8 in order to support 8-bit
terminals. Your 2.1 letc/gettydefs file can be used with 2.2 if
you add CS8 to all stty settings for any lines which will be
used by 8-bit tenninals. If you do not use 8-bit terminals
(those which use the 8th bit in order to display foreign
character sets, for example), then you do not need to
modify your 2.1 version of this file and it can replace the 2.2

XG-04-03-87-3.0.2/2.2

- 30 - The Santa Cruz Operation

Update A Operating System

version installed.

•

letc/rc
Several changes in standard system settings have been made
to this file. Only additions made below the comment:
# Add local commands here.
should be needed in the 2.2 version. Copy all lines below
the comment from your 2.1 version into the 2.2 version of
letclrc. If you have included commands to mount
filesystems when the system comes up multi-user, this is no
longer necessary. 2.2 includes a mechanism to use
information in the file letcldefaultlfilesys to mount
filesystems as specified. (See filesys(F) for more
information.) If you are using process accounting, be sure
to make the same modifications to the new 2.2 version
(uncomment the appropriate lines) as you did for the 2.1
version. If you have been using SCO XENIX-NET or SCQ
uniPATH SNA-3270, then some modifications may have
been made to this file during the installation of those
programs. Be sure you have the correct association
between this file and the installed status of those programs.

•

I etc/termcap
If you have added any terminal definition sections to your
2.1 file, be sure to merge these definitions into the new 2.2
version. Many new entries have been added to the 2.2
version, and several descriptions have been fixed, so you
may want to try the new version before making any
modifications.

•

lusrllib/uucp/dial
If you compiled a new version of this program, you will want
to replace the 2.2 version with your custom 2.1 version.

•

/usr/lib/uucp/dial.c
If you made any special modifications to this program, you
will probably want to merge them into the new 2.2 version

XG-04-03-87-3.0.2/2.2

- 31- The Santa Cruz Operation

XENIX for Personal Computers

(which also has several useful changes made since the 2.1
version).
•

/usr/lib/uucp/makefile
If you have modified any of the source in the directory
/usr/lib/uucp, and made corresponding changes in this file,
you will want to preserve those changes.

A few files will be modified for use with 2.2 automatically. Required
changes will be made; however, access to new features may not occur
automatically. Be sure to read the Release Notes and new
Documentation for information on new features. If any of the
automatic merges fail, you will need to ensure your installed file is
appropriate foruse with 2.2.
•

/ etc/ default/boot
More explicit control over various stages of autoboot is
achievable through mUltiple entries in this file. 2.1
functionality is maintained in the automatic modification of
this file during the update process. See autoboot(M) for
more information.

•

/usr/lib/uucp/L-devices
/etc/ttys
/ etc/ttytype
A total of twelve (12) multiscreens are now supported,
therefore the devices ttyll and tty12 now refer to the
eleventh and twelve multiscreens. Ports formerly
associated with devices ttyll , ttyl2, tty13, and tty14 are now
called ttyla, tty2a, ttylA, tty2A, respectively. Since serial
consoles are supported in 2.2, the first multi screen is called
/ dev Itt yO 1. The changes will be made automatically during
the update process for these three files.

•

/usr/spooVcron/crontabs/root
A line to automatically keep the hardware and software

XG-04-03-87-3.0.2/2.2

- 32 - The Santa Cruz Operation

Update A Operating System

clocks in synch will be added toyour2.1 file.
•

/etc/passwd
Your2.1 version of this file will work fine with 2.2. One new
administrative user (dos) has been added in order to
support setuid dos utilities. This will be done automatically,
as long as no dos user already exists on your system.

Files to be Merged

*=Automatic merge will be attempted for these files.
*/ etc/ defaul t/boot
/etc/default/mkuser
/ etc/default/tar
/etc/gettydefs
*/etc/passwd
/etc/rc
/ etc/tenncap
*/ etc/ttytype
*/etc/ttys
*/usr/spool/cron/crontabs/root
*/usr/lib/uucp/L_devices
/usr/lib/uucp/ dial
/usr/lib/uucp/dial.c
/usr/lib/uucp/makefile
Files Which Will be Preserved

.profile
/ etc/checklist
/etc/cshrc
/etc/ddate
/ etc/ default/backup
/ etc/default/ cron
/ etc/default/ dum pdir
/ etc/ default/login
/etc/default/lpd
/ etc/defaul t/ micnet
/ etc/ defaul t/ msdos

XG-04-03-87-3.0.2/2.2

- 33 - The Santa Cruz Operation

XENIX for Personal Computers

/ etc/defaul t/passwd
I etc/default/restor
letc/group
/etc/motd
/ etc/ systenlid
/etc/wtmp
lusr/ adm/pacct
/usr/lib/mail/aliases.hash
/usr/lib/maiValiashash
/usr/lib/mail/faliases
/usrllib/ maillmaliases
/usr /lib/maiV mailre
/usr/lib/mkuser/mkuser.eshre
/usr/lib/mkuser/mkuser.login
/usr/lib/mkuser/mkuser.vsh
/usr/lib/mkuser/mkuser. prof
lusr/lib/mkuser/mkuser .mail
lusr/lib/uuep/L.emds
/usr/lib/uuep/L.sys
/usr /lib/uuep/L_dialcodes
/usr/lib/uuep/L_stat
lusr/lib/uuep/L_sub
/usr/lib/uuep/R_stat
lusr/lib/uuep/R_sub
/usr/ spoolllp/pstatus
/usr/ spoolllp/ qstatus
Packages Containing User- Configurable Files

BACKUP
CSH
LPR
MAIL
SYSADM
UUCP
VSH

XG-04-03-87 -3.0.2/2.2

- 34 - The Santa Cruz Operation

4-3-87

011-03B-035

XENIX® System V
Operating SysteIn

Installation Guide

Portions © 1980, 1981, 1982, 1983, 1984, 1985, 1986, 1987 Microsoft Corporation.
All righ ts reserved.
Portions © 1983,1984,1985,1986, 1987 The Santa Cruz Operation, Inc.
All rights reserved.

ALL USE, DUPLICATION, OR DISCLOSURE WHATSOEVER BY THE
GOVERNMENT SHALL BE EXPRESSLY SUBJECT TO RESTRICTIONS AS SET
FORTH IN SUBDIVISION (b) (3) (ii) FOR RESTRICTED RIGHTS IN COMPUTER
SOFTWARE AND SUBDIVISION (b) (2) FOR LIMITED RIGHTS IN TECHNICAL
DATA, BOTH AS SET FORTH IN FAR 52.227-7013.

This document was typeset with an IMAGEN® 8/300 Laser Printer.
Microsoft, MS-DOS, and XENIX are trademarks of Microsoft Corporation.
lMA GEN is a registered trademark ofIMA GEN Corporation.

SCO Document Number: XG-12-19-86-3.0

Part Number: 512-210-041

Contents
1
1.1
1.2
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
3
3.1
3.2
3.3
3.4
3.5
3.6
3.7
4
4.1
4.2
4.3
4.4
A
A.1
A.2
A.3
A.4
A.5
A.6
A.7

Introduction
Overview 1-1
UsingThisGuidc

1-1

Installation Procedure
Overview 2-1
XENIX System Distribution 2-1
HowToUseThisGuide 2-2
Before You Start 2-3
Installation Procedure 2-4
TheNextStep 2-30
Troubleshooting 2-31
Using DOS and XENIX On the Same Disk
Introduction 3-1
Partitioning the Hard Disk Usingfdisk 3-1
InstallingXENIX on aDOS System 3-4
UsingXENIX and DOS With Two Hard Disks 3-5
Removing An Operating System From the Hard Disk
DOS Accessing Utilities 3-6
XENIX and DOS On Non-Standard Disks 3-7
U sing the Link Kit
Introduction 4-1
Device Drivers 4-1
Allocating and Deallocating Kernel Resources
Testing and Installing the New Kernel 4-14
Upgrading Your System
Shut Down the System A - 2
BackuptheSystem A-2
Save Special Files A-3
Install the New Operating System
Relink the Kernel A - 7
Reinstall Applications A-7
Merge Saved Files A-8

A -6

4-8

3-6

Chapter!
Introduction
1.1

Overview 1-1

1.2

UsingThis Guide

1-1

Introduction

1.1 Overview
This is a guide to installing XENIX on your personal computer. Setting up
user accounts and peripheral devices is also discussed.
Topics covered in this guide include:
-

How the system is distributed in three packages and what each contains.

Responding to system prompts in the installation procedure.

What you need to get started.
Starting the system for the first time.

Preparing the hard diskforXENIX.

Starting the system from the hard disk.

Setting up user accounts.

Using a second operating system (DOS) with XENIX.
Adding device drivers to your system.

1.2 Using This Guide
This guide contains the following sections:
Chapter 1: futroduction
An introduction and overview of topics covered in this guide.
Chapter2: Installation Procedure
A step by step guide to installing XENIX on your computer.
Starting XENIX for the first time, initializing the hard disk, and
setting up user accounts are among the topics discussed.
Chapter3: UsingDOS andXENIX on the Same Disk
.
Installing both DOS and XENIX, accessing DOS files from
XENIX , and related issues. Includes a description of the
fdisk(C) utility, which partitions the hard disk for both systems.
Chapter4: Using the Link Kit
Using the Link Kit to install device drivers for additional peripheral devices is described.
A ppendix A : Upgrading Your System
Guidelines and instructions for upgrading from System III to SystemV.

1-1

Chapter2
Installation Procedure
2.1

Overview

2-1

2.2

XENIX System Distribution 2-1
2.2.1 48tpiVersus96tpiDistributions 2-1

2.3

HowTo Use This Guide

2.4

Before You Start 2-3
2.4.1 Choosing Swap Area 2-4

2.5

Installation Procedure 2-4
2.5.1 Overview 2-4
2.5.2 WhatYouNeed 2-5
2.5.3 Initializing The Hard Disk 2-7
2.5.4 StartingXENIX On the Hard Disk 2-19
2.5.5 Installing the XENIX Distribution 2-25
2.5.6 Sysinfo Account 2-27
2.5.7 Creating the FirstUserAccount 2-27
2.5.8 Using a Second Filesystem 2-30

2.6

TheNextStep

2.7

Troubleshooting 2-31

2-30

2-2

Installation Procedure

2.1 Overview
This guide explains how to install the XENIX system on a personal computer. The XENIX Operating System is a powerful system of programs
that gives your computer the same multi-user, multi-tasking capabilities
as many large and expensive computers.
When you install the system, you:
•

Initialize the hard disk, then;

•

Copy the XENIX utilities from the XENIX distribution media to the
initialized hard disk.

2.2 XENIX System Distribution
The complete XENIX System consists of the following three distribution
sets:
•

The Operating System

•

The Development System

•

The Text Processing System

The Operating System contains the XENIX programs you need to create
multiple user accounts, manage file systems, create and manage files and
perform system maintenance tasks.
The Development System contains the XENIX programs you need to
create, compile, and debug assembly and high-level language programs.
The Text Processing System contains the XENIX programs you need to
create, edit, and typeset documents.
2.2.1 48tpi Versus 96tpi Distributions
The installation instructions in this chapter are for both 48tpi and 96tpi distributions. Most of the steps are exactly the same regardless of the distribution you have.
However, there are some differences. These are marked with headings
(48tpi or 96 tpi) that indicate special steps for each distribution. Read the
installation instructions carefully.

2-1

XENIX Installation Guide

2.3 How To Use This Guide
Read through this guide thoroughly before beginning the installation procedure so that you become familiar with the various steps and terminology
used in each section. If you run into difficulties duringthc installation, call
the Support Center listed on the support information card included with
the software.
Always follow these rules:

During the installation you use the keyboard to enter information. Always:
•

Begin each command after a prompt (often a $, % or #
symbol). During the installation process, the prompt can
be" < Installation> ," under certain conditions.

•

Enter all requested names and numbers exactly as shown.

•

Complete a line by pressing the RETURN key.
NOTE: The RETURN key is sometimes denoted on the
keyboard by a "down-left" arrow, or referred to as the
ENTER key.

If you make an entering error, you can erase the character:

•

By using the backspace key,
OR

•

By pressing Ctrl-h.

•

To delete everything you have entered on a line,
press Ctrl-u.

Some additional items to be aware of:

•

(yIn)? is asking ."yes or no?", and always requires a
response from you (enter "y" or "n" and press the
RETURN key).

•

The control symbol ( " ) refers to the Ctrl key, and is followed by another key which, used in combination with the
Ctrl key, has a special meaning.
Example: "h means backspace
Press the Ctrl key and the other key at the same time. This
is the same action as using the Shift key.

2-2

Installation Procedure

•

The RETURN key on your keyboard may have a large single arrow pointing down and left (or the word ENTER) on
it rather than the word "return." In this guide, however, it
is written this way:
RETURN

•

Commands referred to in text arc shown in boldface with
the reference manual section next to the command in
parentheses (for example cat(C». Refer to the preface of
the XENIX User's Reference for a guide to the various reference sections.

2.4 Before You Start

Before you begin the installation procedure, make sure your computer is
fully assembled (and operational) and you are familiar with its operation.
In particular you should know:
•

How to tum the computer off and on.

•

Howto insert fioppies into thefioppydrive.

•

Howto reset the computer.

If you have just assembled your computer for the first time or are unsure
about the items listed above, briefiyreview the hardware manuals provided
with your computer and hard disk, The hard disk must be connected to
your computer according to manufacturer's specifications. Also, we suggest you run a system self-test as described in the computer's Operator's
Guide in order to detect possible hardware problems.
Other items to be aware of:
•

If you are upgrading or reinstallaing from an earlier release of
XENIX, be sure to follow the upgrade procedure as outlined in

Appendix A of this guide. This appendix includes valuable information on performing backups of selected filesystems and ensuring
compatibility of your binaries.
•

If you already have a valid separate (non-root) lu filesystem, it may
be possible to preserve it across the reinstallation. This is onlypossible if you do not increase the maximum number of bad tracks on
your hard disk or shrink the size of the XENIX partition using fdisk.
If these conditions are not met, you will not be prompted for the
option to preserve your filesystem.

2-3

XENIX Installation Guide

•

If you plan to partition the hard disk for use with DOS in addition to
XENIX, you must install DOS first. Refer to Chapter 3 of this guide
for details.

•

If you are using a 48tpi floppy set, you have two floppies labeled
BOOT and FILESYSTEM (Nl and N2). If you are using a 96tpi
floppy set, you have only one BOOT/FILESYSTEM floppy.

•

Copy the BOOT and FILESYSTEM floppy or floppies as soon as you
can, then put the originals in a safe place and use the copies. These
floppies are write protected, but any floppy can fail with frequent
use, so it is a good idea to back-up all your volumes, but especially
these first, crucial floppies.
Use the MS-DOSTM floppy copy routine diskcopy to make backups,
before installing XENIX. If you cannot use the DOS routine, you
can copy the floppie's with the XENIX diskcp(C) command once
you have installed the XENIX System. For more information on
diskcp, seetheXENIX User'sReference.

2.4.1 Choosing Swap Area
While installingXENIX System V you are prompted to allocate the amount
of swap area you want. If you do not specify the number of blocks of swap
area you want, you are automatically given a default amount. This default
is minimal. Due to the difficulty in increasing your swap area, it is recommended that you ask for the upper limit amount shown by the divvy(C)
program, if you are planning to use large applications (like databases or
spreadsheet programs), use the software development set extensively, or
make many programs "sticky" for performance reasons. For more information see "Using Peripheral Devices", of the Operations Guide.
2.5 InstallationProcedure

2.5.1 Ovenriew
The installation procedurehas six steps:

1. Start XENIX from the BOOT Floppy (volume Nl).
2.

2-4

Initialize the hard disk with the hdinit(C) program and, if desired,
modify the hard disk partition table to share space with the
DOS operating system.

Installation Procedure

3. Re-start the system from the newly initialized hard disk.
4.

Copy the XENIX utilities onto the hard disk.

Create the super-user password.

Create the first user account.

The following sections describe each step. After you complete the installation, be sure to store this guide and the distribution floppies in a safe place.
You will need them again if you wish to reinstall the system for anyreas011.
2.5.2 WhatYou Need
To install the XENIX System you need:
-

A personal computer with at least 512K bytes of memory, with 640K
recommended.
One hard disk with at least 10 megabytes of storage.
One double-sided floppy drive.
The XENIX System distribution floppy disks.
A Serial Number (an alphanumeric code printed on the Serialization Card).

An activation key (an alphabetic code printed on the Serialization
Card).

The XENIX System distribution set contains these floppies:
-

The XENIX Operating System floppies. The Release Notes
delivered with this guide contain a list of the number of floppies in
each set and the software packages contained in the Operating System.

Optional: Development ·System floppie~. The Release Notes
delivered with the Programmer's Guide contain a list of the software
packages contained in the Development System.

Optional: Text Processing System floppies. The Release Notes
delivered with the Text Processing Guide contain a list of the
software packages contained in the Text Processing System.
primary drive (sometimes called the boot drive). Check your computer
hardware manual if you are not sure which drive is the primary drive.

2-5

XENIX Installation Guide

Tum on your computer and the hard disk.

The computer loads the XENIX bootstrap program from the floppy disk
and begins to execute it. In the upper left corner of the screen, the computer may display the total amount of memory installed. Next, you see:
XENIX System V
Boot

Press RETURN to boot from the floppy drive. You see the default
floppy boot.
IfYOll are using 48tpi floppies, you see this message:
fd( 4) xenix root=fd(4) swap=ram(16) pipe=ram(17) swaplo=O nswap=l000 ronly

IfYOll are using 96tpifloppies, you see this message:
fd(S2) xenix root=fd(S2) swap=ram(16) pipe=ram(17) swaplo=O nswap=1000 ronly

If you are using 48tpifloppies. you seethe prompt:

Insert Filesystem volume and press
Remove the BOOT floppy (Nl) and insert the FILESYSTEM floppy (N2).
If you are using 96tpi floppies, leave the BOOT/FILESYSTEM floppy in
the drive.

After XENIX is loaded in memory, the system displays information about
how memory is allocated and some other system information.
Then the system performs a self-check to determine if there are any problemswith. the hardware. The letters A - Z appear in sl1:ccession.
-

After the letter Z is displayed, the following message appears:
No single-user login present
Entering System Maintenance Mode

If the letters stop displaying before the letter "Z" is reached, run hardware
diagnostics as explained in your computer manual, correct any identified
problems and start the installation procedure again from the beginning. If
the letters stop again, call the Support Center listed on the support information card and be prepared to tell them at what letter the display ended.

2-6

Installation Procedure

The self-check using letters A-Z occurs every time you bring up your
XENIX system.
Once the system begins to run, the following message is displayed:
XENIX System V I-lard Disk Initialization

When you see this message, you are ready to proceed with Initializing The
Hard Disk.

2.5.3 Initializing The Hard Disk
The following steps describe how to initialize the hard disk.
1.

You see the message:
During installation you may choose to overwrite all
orpart of the present contents of your hard disk.
Do you wish to continue? (yIn)

Note
If you have any files on the hard disk that you wish to save before
in stalling XENIX follow this procedure. Enter:
n

and press RETURN.
The following message appears:
Aborting initialization proced ure
At this point, the system shuts down automatically, as the following
message is displayed on the screen:

** Normal System" Shutdown **
**

Safe to Power Off
**
- or Hit Any Key to Reboot **

2-7

XENIX Ins ta lla tion Guide

Remove the floppy, and reboot your existing operating system. After
you have backed up the files you want to save, restart the XENIX
installation procedure from the beginning.
Back up files that reside on partitions that you are going to overwrite.
Creating a new partition on an unused portion of the hard disk will
not overwrite files on another partition. It is not necessary to back up
files that reside on an existing partition you are not changing.

If you do not have any files you want to save, enter:
y

and press RETURN.
The hdinit program now invokes dkinit, which sets the parameters
for the hard disk. You see information about your hard disk and
this menu:
Hard Disk Drive 0 Configuration

1. Display current disk parameters
2. Modify current disk parameters
3. Select default disk parameters
Enter an option or 'q' to quit:
dkinit is primarily for unusual or non -standard disks. If you have a
standard hard disk, one that is supported by your computer
hardware or special mother board ROM, enter "q" followed by
RETURN to continue the installation. Entering "q" at this point
selects the default parameters for your hard disk. Unless you know
that your disk is non -standard, assume that it is standard and enter
"q", to continue your installation with fdisk(C). Skip to step 3.
If your disk is non .:.standard, dkinit operates as follows:
If you enter" 1" or "2", you see the following display:

Disk Parameters
1. Cylinders
2. Heads
3. Write Reduce
4. Write Precomp
5. Ecc
6. Control
7. Landing Zone

2-8

Values
value
value
value
value
value
value
value

Installation Procedure

8. Sectorsltrack

value

When you see the display, "mIlle" is replaced with the default value
for that variab Ie.
If you entered a "I", you now see the first menu again. If you
entered a "2", you are now prompted:

Enter a parameter to modify or 'q' to return to the main menu:
Enter any of "I" - "8" to change the disk parameters, or "q" to
return to the previous men u.
Enterthe new value or to use the existing value:
If you wish to change the value, enter a new value now or press
RETURN to use the existing value.

After you finish changing the disk parameters, enter "q" to return
to the main menu. Next, enter "q" again to save the changes you
made. Exiting from dkinit by entering "q" overwrites any parameters you have changed with the new values. If you wish to restore the
default parameters after making modifications, enter "3" from the
first menu.
As part of the initialization process, you may partition the hard
disk, using the fdisk(C) utility, to support both DOS and XENIX on
the same hard disk, or you can allow XENIX to use the whole disk.

Note
If you wish to partition the disk so that you can use another operating
system in addition to XENIX , do not follow the fdisk steps shown
here. Instead, see Chapter 3 of this Installation Guide and the
.fdisk(C) manual page in the XENIX User's Reference ..

Install DOS on the· hard disk before installingXENIX. Installing DOS
after XENIX , in some circumstances, changes the fdisk table and
makes the XENIX partition unbootable. If this happens, you must
recreate the fdisk table. Note that DOS fdisk reports disk size in
cylinders, XENIXfdiskreports disk size in tracks.
After you set up the desired partitions with fdisk, return to the next
part of this installation procedure.
If you are only using XENIX on your hard disk, continue with the following steps.

2-9

XENIX Installation Guide

3. After a moment, an fdisk menu appears on the screen. You see this
option list:
1. Display Partition Table
2. Use Entire Disk for XENIX
3. Create XENIX Partition
4. Activate Partition
5. Delete Partition
Enter your choice or 'q' to quit:
En ter option" 1" and press RETURN.
If you have never installed an operating system on your disk, you see
a tab Ie similar to this:

Current Hard Disk Drive: I dev/rhdOO

I Partition

Status

Type

Start

End

Size

Total disk size: 1220 tracks (5 tracks reserved for masterboot and
diagnostics)
Press to continue

Note
If you have previously installed an operating system on your disk, you
see a table that might look something like this:

Current Hard Disk Drive: Idev/rhdOO

Total disk size: 1220 tracks (5 tracks reserved for masterboot and
diagnostics)
Press to continue

2-10

Installation Procedure

If you would like XENIX to occupy the whole disk, enter option "2".
If any other operating systems were previously installed on your disk,
you will see the following warning message:

Warning! All data on your disk will be lost!
Do you wish to continue? (yIn)
Enter "y" and press RETURN. Even if you have already installed
XENIX , and are just reinstalling the system, you should enter "y"
and press RETURN at this point only if you want XENIX to occupy
the whole disk. This ensures that fdisk partitions the whole disk for
XENIX.
Note that the track numbers and size of your disk may vary from this
example.

Press RETURN, and you see the main fdisk menu. You have now
set up the partition(s) to use XENIX on your hard disk. To continue
with the next step in the installation procedure, enter:

q
and press RETURN.
4. Now you see a menu from the program badtrk(M). With the badtrk
program, you can scan your hard disk for defective tracks. The program maps any flawed locations to good tracks elsewhere on the
disk. It also creates a bad track table, which is a list of all the bad
tracks on your hard disk.
The main program menu looks like this:

1. Print Current Bad Track Table

2.
3.
4.
5.
6.

Scan Disk (You may choose Read -Only or Destructive later)
Add Entries to Current Bad Track Table by Cylinder/Head Number
Add Entries to Current Bad Track Table by Sector Number
Delete Entries Individually from Current Bad Track Table
Delete All Entries from Bad Track Table

Please enter your choice or 'q' to quit:
Enter "2", then press RETURN. If badtrk thinks that the table may
have been changed, you are asked if you want to update this device
with anew table. You should answer "y".

2-11

XENIX Installation Guide

NeJl.-t, you are asked if you want to salvage any data on the bad
tracks, and warned that this may take a long time. If you have data
that you want to salvage, and you do not have another way to
recover it (fpr example, from backups), then only enter "y". If you
do not have data you want to recover, or the data can be recovered
from backups, enter "n".
You see the following submenu:
1.
2.
3.

Scan entire XENIX partition
Scan a specified range of tracks
Scan a specified filesystem

Enter the number corresponding to the type of scan you wish to perform. If you are installing XENIX for the first time or performing a
complete reinstallation, select option" 1".
If you choose option "2" or "3", you are prompted to specify the

area you wantbadtrkto scan.
After you select the area you want scanned, you are given the
choice:
1.
2.

Quick scan (approximately 7 megabytes/min)
Thorough scan (approximately 1 megabyte/min)

If you are installing XENIX for the first time, or are performing a

complete reinstallation, select option "2".
You are prompted:
Do you want this to be a destructive scan? (y/n)
If you respond "n", anon-destructive scan begins.

This scan reads but does not write to the disk. For a new installation
or reinstallation, enter "y". You are warned:
This will destroy the present contents of the region you are scanning.
Do you wish to continue? (yIn)

2-12

Installation Procedure

Enter "y" and press RETURN . You see the following message:
Scanning in progress, press 'q' to interrupt at anytime.
After you have responded to the above prompts, the program scans
the active partition of the new disk for flaws. The larger your disk,
the longer the scanning process takes, so a very large disk may take a
while.
As badtrk scans the disk, it displays the number of each track it
examines, and the percentage of the disk already scanned. Pressing
the "q" key at anytime interrupts the scan. If you press "q" to interrupt the scan you do not need to press RETURN. You are then be
prompted to continue scanning or to return to the main menu.
Whenever badtrk finds a defective track, it lists the location of that
track using both the sector number and cylinder/head conventions.
Defective track information is entered into the table and displayed
on the screen. An example bad track might be:
error on devFixed Disk (0/47), block=12954 cmd=0003 status=0018
sector = 12971, cylinder/head = 190/3

When the scan is complete, the menu reappears. Enter option "I"
to see the results of the scan. Your bad track table might look like
this:
Defective Tracks

Cylinder

Head

190

Sector Number(s)
12971-12987

Press to continue

Note
If there is a flaw in the first few tracks of the XENIX partition, you are
returned to the fdisk utility (see the previous installation step).
Repartition the disk with fdisk so that the XENIX partition no longer
includes the defective tracks. You will have to experiment to determine how many tracks to exclude. Leave these defective tracks unassigned to any operating system. When you leave fdisk, badtrk runs
again. Scan the disk for flaws.

2-13

XENIX Installation Guide

This process continues until badtrk finds no flaws in the first few
tracks.

Press RETURN to return to the main menu.
If your disk comes with a flaw map, you should enter any flaws

from it into the bad track table.
Because most disk flaws are marginal or intermittent, your disk's
flaw map will probably list more bad tracks than the scanningprocess reveals. If so, you should now add these defective tracks to
the bad track table.
Select either option "3" or option "4" depending upon the format
of the flaw map furnished with your disk. Enter the defective
tracks, one per line. If you make a mistake, enter:
q

and press RETURN. When you see the main badtrk menu, enter
option "5" to delete a track.
If your disk is not furnished with a flaw map, or you are finished

making changes to the bad track table, enter:
q

and press RETURN to return to the main menu.
Atthemain badtrkmenu, enter:
q

again and press RETURN.
You now choose the number of tracks to allocate as replacements
for those tracks that are flawed. You should allocate at least as
many as the recommended number, although you can choose to
allocate less. Please make this choice carefully, because if you
need to allocate more space later, you will have to reinstall
XENIX.
The program now displays the number of identified bad tracks
and you are prompted to enter the number of bad tracks to allocate space for. Enter the number or just press RETURN to use the
recommended number that is displayed. For example, you might
see:

2-14

Installation Procedure

Enter the number of bad tracks to allocate space for
(or press return to use the recommended value of 20):
If you press RETURN and do not enter an alternate value, badtrk

allocates the recommended number of tracks as replacements.
This number is based on the number of bad tracks currently in the
table, plus an allowance for tracks that may go bad in the future.
Ne>..1, badtrk prompts:
Do you want to update this device with the new table?
Enter:

y
and press RETURN to save the changes. To correct any mistakes
or otherwise alter the bad track table, enter "n". Modify the bad
track table to contain the desired entries, enter "q" at the main
menu to return to the prompt displayed above, then enter "y" to
update the device with the new table.
Now you are prompted:
Do you want to attempt to salvage any valid data
on the bad tracks? [may take a longtime] (yIn)
Generally you should respond "n" to this prompt. However, if
you have not made a backup of needed data on the bad tracks and
there is no other way of recovering this information, you may
want to respond "y". Keep in mind that this process may take a
longtime.
5. You now see several prompts from the divvy(C) utility. This program allocates portions of your partitioned disk for the root and
swap areas. It also allocates a small portion of the disk for a
recover area that is used during autoboot by the fsck(C) program.
autoboot uses Idevlscratch, the file system created by divvy, when
it runs fsck on the root filesystem. You also use Idevlscratch as a
scratch filename at other times when fsck prompts for one, provided that the filesystem being checked is not larger than the root
filesystem.

Note
If you are performing a reinstallation and you have a valid existing /u
filesystem, divvy will prompt for the option to preserve it across the
reinstallation. You will be prompted only if the filesystem is valid,
and you did not increase the maximum number of bad tracks on your
2-15

XENIX Installation Guide

hard disk or shrink the size of the XENIX partition using fdisk. The
prompt appears as follows:
This device contains a valid disk division table.
Your additional (non -root) filesystems
can be preserved across the reinstallation.
Do you want to preserve your additional filesystems? (yIn)
If you enter "y", divvy prompts:
If you choose block-by-block control, do not change the
bounds of any file system you wish to retain.
Without block-by-block control, your original disk layout
cannot and will not be modified.
Do you require block byblock control over the layout
of the XENIX division? (yIn)
If you respond "y", divvy will then proceed with the block-by-block
procedure as described in step 6. If you choose not to preserve any
filesystems, divvy immediately prompts for swap space allocation,
and the installation proceeds normally, as in the steps that follow.

You are prompted to choose the amount of space to allocate for the
swap area. If you do not specify the number of blocks of swap area
you want, you are automatically given a default amount. This
default is minimal.
Due to the difficulty in increasing your swap area, it is recommended that you ask for the upper limit amount shown by the
divvy(C) program. This is especially important if you are planning
to use large applications like databases or spreadsheet programs,
use the Development System extensively, or make many programs
"sticky" (memory resident) for performance reasons.

2-16

Installation Procedure

If you plan to install the Development System, enter a swap-area

allocation that is at least 500 blocks larger than the default.
divvy prompts you:
There are 10098 blocks in the XENIX area.
Between 1000 and 2000 blocks should be reserved for the swap area.
Please enter the swap-space allocation, or press
to get the default allocation of 1250 blocks:

The actual numbers in this prompt vary depending upon the size of
your disk. Enter your swap space allocation now or press:
RETURN

to choose the default values.
If your disk is larger than 20M bytes, you see the prom pt:

Do you want a separate lu filesystem? (yIn)
We recommend that you have a separate file system with disks larger
than 20M bytes, especially if you anticipate having many, active
users. You should leave at least 15M bytes for the root filesystem.
You can call this separate file system anything you want, and, if
desired, you can change the name later. The name should be
different from any other directory or filesystem. We recommend
that you use the name lu. For more information on using a lu
filesystem, see Chapter 7 of the XENIX Operations Guide, "Using
Peripheral Devices." That chapter describes adding a second hard
disk (and filesystem), but the discussion of a second filesystem
applies here.
If you have enough storage for a separate user filesystem, and want
to create one, enter:

y
and press RETURN.
Next, you see:
Enterblock allocation forthe lu file system.
(min to max)

2-17

XENIX Installation Guide

In the display, min and max are replaced with the minimum and
maximum number of blocks that can be allocated for the filesystem.

You are now promptedforblock-by-block control of the partition:
Do you require block-by-block control over
the layout of the XENIX partition? (yIn)
If you are installing XENIX for the first time, enter:
n

and press RETURN. Block-by-block control means you can
choose the exact size of filesystems and the swap area to fit your
needs. Most users do not need this kind of precise control, so
answering 'n' at this prompt causes divvy to use default settings
based on the size of your hard disk.
If you answer "y" you see a table from the divvy program. Refer to
divvy( C) in the User's Reference for more infonnation.
If you create a very large root filesystem you may be asked if you
want to allocate an additional, small portion of the disk as scratch
space for fsck. fsck needs the scratch space for temporary storage
when checking very large filesystems. You should make a scratch
filesystem if you have a very large root filesystem, since this makes
bootingXENIXand runningfsckmuch easier.
7. The system now loads a rudimentary XENIX file system onto your
hard disk. This takes several minutes. You see the messages:
Making file systems
Hard disk initialization proced ure completed.
If you are using a 96tpiftoppyset, this is followed by the message:

Operating System Serialization
Enter your serial number
and press :
Enter your serial number exactly as it is shown on your Serialization
Card and press RETURN. Then you see the message:
Enter your activation key and press :
Enter your activation key exactly as it is shown on your Serialization
Card and press RETURN.

2-18

Installation Procedure

When the hdinit program is finished, the system shuts down and
displays instructions on booting the newly initialized hard disk.
Make note of these instructions. You then see:

** Normal System Shutdown **
Safe to Power Off
**
- or ** Hit Any Key to Reboot **

If you want to add a second hard disk, finish the installation procedure. Then refer to Chapter 7 of the XENIX Operations Guide,
"U sin g Peri pheral Devices."

2.5.4 Starting XENIX On the Hard Disk
This section explains how to start theXENIX system using the hard disk.

1. If you are using 48tpi floppies, you will see instructions to remove
the filesystem floppy and insert the BOOT floppy (Nl) into the
drive.
If you are using 96tpi floppies, open the floppy door, but leave the

BOOTIFILESYSTEM floppy in the drive.
Now press any key to reboot the system.
After you see the boot prompt
Boot
If you are using 96tpifloppies, enter:

and you see:
hd(40)xenix
If you are using 48tpi floppies, enter:

install
and you see:
fd (4) xenix root=hd( 40) swap=hd( 41) pipe=hd(40) swap}o=O nswap=O

2-19

XENIX Installation Guide

Press RETURN.
Next, regardless of your floppy type, you see some copyright information, and information about the memory configuration of your
system.

Note
Note that this startup procedure applies only to the first time you
install XENIX on your hard disk. Hereafter you need only press
RETURN when you see the Boot prompt, no matter what type of
floppies you use for your installation.

As before, the system performs a self-check to determine where
any problems exist with the hardware. The letters A-Z appear successively on screen. If the letters displaying stop before the letter
"Z" is reached, run hardware diagnostics as explained in your computer manual. Correct any identified problems and start the XENIX
installation procedure again.
If the letters stop at this point, call the Support Center listed on the

support information card and be prepared to tell them the last letter
displayed.
2.

Now the program fsck(C) is run. fsck checks the filesystem(s) on
your hard disk. In this case, it will check only the root filesystem.
If you have a very large root filesystem, but did not respond "y" to
the divvy prompt for creating a scratch filesystem, then fsck

prompts for the name of a scratch file. fsck requires a scratch file
that is not on the filesystem being checked. See fsck(C) for more
information.
An example scratch file in this case is a blank formatted floppy. In
response to the prompt from fsck, enter the name of the drive containingthefloppy, such as:
Idev/rfdO

2-20

Installation Procedure

Note
If you responded "y" to the prompt from divvy regarding a scratch
filesystem, then you will not see the prompt from fsck for a scratch
file name during installation. You will, however, see this prompt any
other time that fsck is run on a filesystem large enough to need a
scratch file. You can en ter:

Idev/scratch
for the root filesystem, or for any filesystem that is not larger than the
root file system .

3. If you have 48tpi floppies, when fsck finishes, you are prompted to
make sure the BOOT (Nl) floppy is in the drive. You see the following:
Verify Operating System (Installation )volume N1 is inserted
and press
If you have 96tpi floppies, you are prompted to insert floppy Bl at

this point.
4.

After this, follow any additional screen prompts for floppies. Note
that you maynotbe prompted to insert all the volumes in your distribution at this time.
For example, the Link Kit is on one of your volumes and it is not
installed at this time. You can install the Link Kit later in this procedure.

If you insert a floppy in the wrong order, you see this prompt:
Error: incorrect volume in drive!
Remove the floppy from the drive, insert the correct volume, and
press RETURN.

2-21

XENIX Installation Guide

If there is an error with the extraction procedure, such as a floppy

error, the door of the floppy drive is not completely closed, or there
is some other problem you may see the message:
Extraction error: try again? (yin)
Enter:
y

and press RETURN.
5. If you have 48tpi floppies, when the last of the "N" volumes you are
prompted for is read, you see the message:
Operating system serialization.
Enter your serial number
and press
Enter the serial number exactly as it is shown on your Serialization
Card and press RETURN. Then you see the message:
Enter your activation key
and press
Enter the activation key exactly as it is shown on your Serialization
Card and press RETURN.
6.

Ne>..i you are prompted to enter the "B" series of floppies. You see
screen prompts like those for the "N" floppies.
When the last of the "B" floppies is installed, you see:
Please assign a password for the super-user account, "root".
Enter new password (minimum of 5 characters)
Please use a combination of upper and lowercase letters and numbers.
New password:

The new password can be any combination of letters, numbers, and
punctuation marks, but should be at least 5 characters long. Enter
the new password and press RETURN.

2-22

Installation Procedure

The system does not display the password as you enter it, so type
carefully. After you press RETURN the system displays the message:
Re-en ter new password:
Enter the new password once more and press RETURN. Make sure
you type it correctly, otherwise the program prompts you to enter
the password again. When you have entered the password correctly,
you see some information about XENIX passwords and how to
change your super-user password in the future.
The super-user password is now in place. From now on, the password is required whenever you attempt to access the system as
super-user. The super-user password keeps the system safe from
unauthorized use. It is important that you create a super-user password during system installation to ensure maximum protection of
the system and prevent unnecessary use of the super-user (also
known as "root") account.
It is very easy to make errors when logged in as super-user that
could destroy files. Login as super-user only to install programs
and to do system maintenance tasks. For a complete description of
the super-user, see the XENIX Operations Guide.

Do not forget the super-user password. To restore a forgotten
super-user password you must reinstall the XENIX system. If
necessary, keep a copy of the super-user password in a safe place.
Next you see:
Does daylight savings time apply at your location? (yIn)
()

If daylight savingslstandard time changes occur in your area, enter
"y." If not, enter "n." After you press RETURN, you see:

Are you in North America? (yIn)

2-23

XENIX Installation Guide

If you enter "y", you see:

1. AST 2. EST 3. CST 4. MST 5. PST 6. YST 7. HST 8. NST -

Atlantic Standard Time
Eastern Standard Time
Central Standard Time
Mountain Standard Time
Pacific Standard Time
Yukon Standard Time
Hawaiian/Alaskan Standard Time
Nome Standard Time

Enter the number that represents yourtimezone:
If, for example, your timezone is Nome Standard time, you would
enter the number "8" and press RETURN.
If you are not in the United States (or one of the time zones
represented above), and entered "n", the following is displayed:
What is the standard abbreviation of your timezone? (3 capital letters )

Enter three upper case letters which represent your time zone and
press RETURN. Next you will see this message:
How many hours west of Greenwich Mean Time
are you (partial hours are valid - e.g. 12.5)1
Answerwithanumberbetween -24 and 24, then press RETURN.
You now specify the use of daylight savings time in your area. You
select the dating method used in your area to switch between standard and daylight time. You see the following prompt:

1. Week ofthe year (1-52)
2. Day of the year (i.e. Julian date 1-366)
Select the method your time zone uses to convert
between standard and daylight time.
If your time zone switches on a specific week, choose option 1, if it

switches on a specific day of the year, choose option 2. Then press
RETURN.

2-24

Installation Procedure

The next prompt asks for the Week or the Day of the year when your
area switches to daylight time, depending on which method you
specified above. You see:
Enter the [Week or Julian Date] when your time zone converts
to daylight savings time:
Enter the appropriate week orday now. Next you see:
Enter the [Week or Julian Date] when your time zone converts
back to standard time:
Now enter the appropriate date when your area shifts back to standard time. Next you are prompted for the number of hours to shift
for daylight time. You see:
How many hours does your time zone adjust for
daylight savings time (partial hours are valid - e.g.. 5)?
Most time zones adjust one full hour for daylight savings time.
The time zone variable, TZ, in the file /etc/deJaultllogin is changed
accordingly . Your time zone is now set. There is no need to change
the .profile for a user. unless they call in from a different time zone,
and want to override the local standard.
You have now installed the minimal XENIX system, or run time system.
You can use many of the standard XENIX utilities, or install other applications packages.
You see another menu which gives you the option of stopping or continuingwith the installation. You can, atthis point, stop the installation, oryou
can continue to install the XENIX Operating System in the ne}..1: section,
Installing the XENIX Distribution.
2.5.5 Installing the XENIX Distribution

You can now install more of the XENIX Operating System. With the
custom(C) program you can selectively e}..1:ract files from the distribution
set to create your own custom XENIX system. You see information about
your filesystem(s), including the number of blocks currently used. You
also see this menu:

1. Stop installation
2. Continue installation
If you want to install all or part of the Operating System, enter option "2"
and press RETURN.

2-25

XENIX Installation Guide

Note that the entire XENIX distribution, including the Development System and Tex1: Processing System requires more than 10M bytes of disk
space.
If you choose option '2,' you are prompted for a set to install (customize).
Choose from Operating System, Development System, and Text Processing System. If you do not select a system to "customize", by choosing the
'q' option, you stop installation procedure. You will need to use
custom( C) to add more of XENIX.

The custom program prompts for the necessary volume numbers. Insert
the appropriate floppies and follow the screen prompts. For information
on installing portions of the Operating System, see the XENIX Reference
section on custom(C).
You can install the Link Kit at this time with custom. Note that you are
prompted for your serial number and activation key again. Enter them as
you did earlier in the installation.
When you are finished installing XENIX , you see a message about booting
the system. You then see:

** Normal System Shutdown **
**

Safe to Power Off
**
- or Hit Any Key to Reboot **

The system shuts down. Remove any floppy that is in the drive.
Press any key to reboot the system and press RETURN when the boot
prompt appears:
Boot
You see:
hd(40)xenix
The screen clears and you see some self check diagnostics. You then see:
Enter CONTROL-d to proceed with normal startup
(or give root password for system maintenance)
Since there are some system administration steps you should take now,
enter the root oassword and Dress RETURN . You soon see the root
prompt, also us~d in system maintenance mode, which is a number sign: #.
You are ready to perform the system administration tasks covered in the
2-26

Installation Procedure

section that follows.
2.5.6 Sysinfo Account
There is a special account used to perform system backups. The "sysinfo"
account is set up with permissions and privileges similar to the super-user
aecount, but only for performing system backups. See the chapter "Backing Up File Systems" in the XENIX Operations Guide for more on this procedure.
You will need a password on the sysinfo account just as you do for the
super-user (also known as "root") account.
To create the sysinfo password, follow these steps:

1. Enter:
passwd sysinfo
and press RETURN.
The system displays the message:
New password:
The new password can be any sequence of letters, numbers, andlor
punctuation marks, but should be at least 5 characters long.
2.

Enter the new password and press RETURN.
The system does not display the password as you enter so enter carefully. After you press RETURN the system displays the message:
Retype new password:

Enter the new password once more and press RETURN. Make sure
you enter it correctly, otherwise the program will ignore the change.

2.5.7 Creating the First User Account
NeA1, create the first user account, "guest". This guest account is a temporary workspace on the system that you may use to practice with the
XENIX system. Later, after installation is complete and you are familiar
with the XENIX commands, you can remove the guest account and create
private accounts for all the system users.

2-27

XENIX Installation Guide

To create the first user account, follow these steps:

1. Enter:
mkuser
and press RETURN. The system displays the message:
Mkuser
Add a userto the system
Do you require detailed instructions? (yIn):
Enter:
n

and press RETURN (you can examine the instructions at some other
time). You can quit from the program at any "(yIn)" prompt by
entering the letter 'q' and pressing RETURN.
2. The system prompts for more information:
Enter new user's login name:
Enter:
guest
and press RETURN. The name "guest" is now the login name for
the new user account.
3.

Next you are asked:
Do you wish to use the next available userid? (y/n/q):
Answer "y" .

Next, the program prompts for a group name:
Do you wanttousethe default group? (yIn)?
Enter:
y

This sets the group to "group".
5.

2-28

Next, the program prompts for the new user's password.

Installation Procedure

En ter password:
Press RETURN. This allows you to use the guest account without
giving a password.
6.

Next, the program prompts for the shell type. The following
displays:
Please specify the type of shell (command interpreter)
this user requires. You can enter 1, 2, 3, 4, or S as follows:
1
2
3
4
S

Standard (Bourne) Shell.
Visual Shell.
C Shell.
Restricted Shell.
Uucp.

Enter" I" and press ENTER. The guest account has an sh(C) shell.
7.

Finally, the program prompts you for comments:
Please Enter Comment

> ......................... .
>

Enter:
guest account
and press RETURN.
8. The system then prompts if you want to change anything. Enter:
n

and press RETURN.
9.

Finally, you see the prompt:
Do you want to add another user? (yIn)
Enter:
n

and press RETURN.

2-29

XENIX Installation Guide

The new guest account is ready. Later, when you tum to the XENIX User's
Guide, you may use this account to, for instance, practice logging in, make
directories and run programs.
2.5.8 Using a Second Filesystem

If you created a lu filesystem earlier in the installation, enter the following
command after you finish installing the XENIX system and are in System
Maintenance Mode:
mkdev fs Idev/u lu
In addition, you may wish to edit the letcldefaultlmkuser file. Change the
entry which reads "HOME=/usr" to "HOME=/u". This establishes lu as
the location for user accounts.
2.6 The NextStep

If you are familiar with the XENIX Operating System, you may continue
with normal startup and begin working. Just press the CONTROL key and
enter 'd'. Refer to the explanation of normal startup in the XENIX Operations Guide if you have problems.
If you are not familiar with the XENIX Operating System, we recommend
that you halt the system and turn to the XENIX User's Guide and the XENIX
Operations Guide to learn howto start the system, how to login, and how to
run programs.
To halt the system, follow these steps:

1. Enter:
/etc/shutdown 0
and press RETURN.

2. Wait forthe following message:

**
**
**

Normal System Shutdown
Safe to Power Off
- or Hit Any Key to Reboot

**
**

3. ''X/hen you see tIle Sllutdo\'1Jn message, it is safe to tum off tile power
to the computer.

2-30

Installation Procedure

2.7 Troubleshooting
Sometimes things can go wrong in the installation procedure. Most often,
there is no problem with the software or the procedure itself. Occasionally
there is a problem with the hardware, but most are minor, such as improperly connected cables.
You can avoid most simple errors by reading the Release Notes delivered
with this product, and this Installation Guide completely before you try to
install the software.
During the installation procedure, don't assume you know what is about to
happen, even if you have installed the XENIX system before. Use the
documentation wisely.

If you have difficulty installing the software, here is a list of some of the
most common problems, how to avoid them, and how to fix them if they
happen:

•

Some hardware (for example, a disk drive) doesn't seem to work,
although it works fine under another operating system.
Certain hardware configurations do not work with XENIX. Refer to
the "Compatible Hardware" section in the Release Notes for information on what hardware you can use with XENIX .

•

XENIX is installed after DOS, now both operating systems do not

work.
You may want to back up your DOS files, install DOS and install
XENIX . For details on this, see Chapter 3 in this Installation Guide,
"Using DOS And XENIX On The Same Disk."

•

Error reading a floppy.
Make sure the correct floppy is in the drive and it is inserted
correctly (see your owner's manual if you do not know how insert
the floppy correctly).
Make sure the floppy drive door is closed after you insert a floppy.

If you are sure the proper floppy is inserted correctly, and you still
have a read error, try tapping the floppy lightly against a hard surface, such as a table top. Be careful not to damage the media,
though!

•

The system does notbootfrom the BOOTfloppy.
Make sure you insert the BOOT floppy. If you insert another floppy
instead, you do not see an error message, but the system still does

2-31

XENIX Installation Guide

not boot.
The nOOT floppy is shipped with a write protect tab so that you do
not accidentally erasc it during the installation process. If you erase
or damage the BOOT floppy, and you have not made a backup copy,
call the SoftCare Support Center number to arrange for a new
BOOT floppy.

•

The system won 't boot from the hard disk
You may see a message such as:
panic: iinit
or another kind of error message. Sometimes this happens because
you did not run a bad track scan during installation, and the boot
block was written on a bad track.
Whatever the reason, you must reinstall the XENIX system. If you
didn't enter all the flaws furnished on a flaw map, do so this time.
If XENIX still won't boot, run your system's and disk's hardware
diagnostics.

•

You forget to enter more bad tracks from a manufacturer furnished
Jlawmap.
You can add more flaw locations to the bad track map any time you
are in System Maintenance mode. Follow these steps if you are still
in the installation procedure:
Finish installing the run time system.
When you are prompted to continue installing, or stop the
installation process, stop the installation process.
Enter system maintenance mode.
-

Run badtrkto add the new flaws.
Salvage any data (when prompted under badtrk).
Run the eus tom utility to finish installing your system.

2-32

Chapter3
Using DOS and XENIX
On the Same Disk
3.1

Introduction

3-1

3.2

PartitioningtheHardDiskUsingfdisk 3-1

3.3

InstallingXENIX on aDOS System

3.4

UsingXENIX and DOS With Two Hard Disks

3.5

Removing An Operating System From the Hard Disk

3.6 DOS Accessing Utilities

3-4
3-5

3-6

3.7 XENIX and DOS On Non-Standard Disks

3-7

3-6

Using DOS and XENIX On the Same Disk

3.1 Introduction
Many users received the MS-DOS, or other closely compatible DOS,
operating system with their computer. This chapter explains how you can
still use DOS utilities, files, and applications after you install the XENIX
operating system. You can even access DOS files and directories from
XENIX. You do not need to throw awayyourinvestmcnt in DOS software,
orbuy another computer just to run XENIX.
Several programs make this possible. The dos(C) utilities allow access to
DOS files on diskettes or on the DOS partition on the hard disk. These util-

ities are discussed later in this chapter. The utility which partitions the disk
is called fdisk(C) and is available in DOS and XENIX versions. The next
section explains how to use fdisk to run DOS and XENIX on the same hard
disk. Another section discusses installing XENIX on the hard disk along
with DOS. There is also a section explaining various booting
configurations, for users who mostly use XENIX and for users who mostly
use DOS.

3.2 Partitioning the Hard Disk Using fdisk
Each version of fdisk is documented in the respective operating system's
manual. fdisk(C) is found in the XENIX Reference and, unless otherwise
noted, this chapter refers to the XENIX fdis k.
fdisk is interactive, using a menu to display your options. Here is an example fdiskmenu:

1.
2.
3.
4.
5.

Display Partition Table
Use Entire Disk ForXENIX
Create XENIX Partition
Activate Partition
Delete XENIX Partition

Enter your choice or 'q' to quit:
The fdisk utility allows you to set up separate areas (partitions) on your
hard disk for your operating system. The hard disk is divided into tracks.
The number of tracks depends upon the size of the hard disk.
A partition consists of a group of tracks. One hard disk may contain up to
four partitions. Each partition can have a different operating system and
associated directories and files.

3-1

XENIX Installation Guide

The fdisk command allows you to specify which partition is "active". This
means that when you turn on (boot) your computer, the operating system
installed in the active partition will start running. The XENIX partition
must be active when you intend to use the XENIX operating system.
The fdisk command allows you to specify the number of tracks used by the
partition. This will vary according to the size of your hard disk. We recommend using at least a 10 megabyte hard disk to run XENIX. The size of the
XENIX partition also depends on the number of software packages you
want to install. Refer to the custom(C) manual page for information on
the installing and removing packages from the three XENIX distribution
Systems. You will generally need the size of your XENIX partition to be at
least six megabytes. You can install the XENIX Operating System package
in this space, and have space for user files.
The fdisk command allows you to specify where the partition begins. fdisk
will not allow you to construct overlapping partitions. You do not need to
install XENIX in the first partition. When you are runningXENIX , the device name of the partition runningXENIX is /dev/hdOa.
One option of fdisk tabulates the current state of the partitions (the
Display Partition Table option). This option lists, for each partition,
whether the partition is active, the first track, the last track, the number of
tracks used, and the associated operating system. If you enter the Display
Partition Table option and press RETURN to see the partition table, the
result may look like this:
Current Hard Disk Drive: /dev/hdOO
Partition

Status

Type

Start

End

Size

1
2

Active
Inactive

XENIX
DOS

001
801

800
1219

800
420

Total disk size: 2300 tracks (9 tracks reserved for masterboot and diagnostics ).
There are two ways to switch operating systems once you have set up
separate XENIX and DOS partitions:
•

Use a floppy diskette with the files necessary to boot the DOS
operating system

•

Use fdisk to change the current active partition.

3-2

Using DOS and XENIX On the Same Disk

If you change operating systems frequently, you should use a bootable DOS
diskette to switch between DOS and XENIX. [<'ollow this procedure:

Make sure all users are logged off XENIX .

Run shutdown(C) to shut down theXENIX system. This command
makes sure all users know the system is being shut down, terminates
all processes, then halts the system.

Once XENIX has shut down, insert the bootable DOS diskette into
the primary (boot) drive.

BootDOS.

To get back to XENIX , remove any disks from the floppy drive(s)
and press (or tum the computer off,
then on). Since the XENIX partition is still active, the XENIX
operating system boots.

We recommend that you use a boot floppy to boot the DOS operating system. Booting from a floppy is generally easier, faster and safer than constantlyusingfdisk to change active partitions.
The other way to change operating systems is to run fdisk and change the
active partition from XENIX to DOS. Then, after you shut down XENIX
(see the previous steps) DOS boots from the hard disk. You do not need a
bootableDOS floppy disk.
To switch back to XENIX, run fdisk under DOS and make theXENIX partition active. Then press (or tum the computer off, then on) to reboot XENIX.
Because the XENIX partition must be active for XENIX to operate, you
cannot use a bootable floppy to boot XENIX . This second method is
appropriate for an occasional change of the active operating system.
The following hard disk device names:
Idev/hdOd
Idev/rhdOd
Idev/hdld
Idev/rhdld
are similar to I devlhdOa in that the disk driver determines which partition is
the DOS partition and uses that as hd?d. This means that software using
the DOS partition does not need to know which partition is DOS (the disk
driver determines that).

3-3

XENIX Installation Guide

Remember that if you have an active XENIX partition and boot DOS from
a floppy you can transfer to C: to work with the DOS files.
3.3 Ins talling XENIX on a DOS Sys tern
If you wish to setupXENIX on ahard disk which previously contained only
DOS, follow these steps:

1. Copy (back up) all the DOS files and directories on the hard disk
onto floppies, or whatever backup media you wish to use.
2.

Run fdisk, under DOS. If there is enough free space (at least 6
megabytes) for XENIX on your hard disk, skip to step 4. Otherwise,
delete the DOS partition, then recreate it, leaving enough room on
the disk for XENIX. Allow at least 6 megabytes for XENIX .

Return the DOS files to the hard disk from the backup media. Keep
the backups in case there is an error of some kind, so you will not
lose any data.

4. Turn off your computer.
5 . Follow the installation procedure outlined in Chapter 2 of this guide
to install XENIX .
You will see a message warning that the contents of the hard disk
will be destroyed. Don't worry, you've backed up the DOS files and
transferred them to the new DOS partition. The new partition being
created will con tain XENIX .
6.

During the installation procedure fdisk is invoked to partition the
hard disk. Use fdisk to assign a partition which is at least 6 megabytes to XENIX .

Designate "XENIX " as the active operating system.

Finish installingtheXENIX operating system.

3-4

Using DOS and XENIX On the Same Disk

Note
XENIX fdisk displays DOS partitions as DOS while DOS fdisk displays
XENIX partitions as Other.

You can only create DOS partitions using DOS fdisk, and only XENIX
partitions using XENIX fdisk.
Be aware that DOS fdisk reports sizes in terms of cylinders, while
XENIX fdisk reports sizes in terms of tracks.

3.4 Using XENIX and DOS With Two Hard Disks
Your computer always boots the operating system in the active partition on
the first hard disk. XENIX must boot from the first hard disk. There are
several ways to configure your system if you have two hard disks. Two ways
are discussed here.
One configuration consists of designating the entire first disk as a XENIX
partition. You then use aDOS boot floppy to start DOS and specify:

A: D:

to switch to the DOS area on the second hard disk, where D is the designation for the second hard disk.
Another method is to maintain a small DOS partition on the first hard disk.
The DOS partition is designated the active partition. In this configuration,
the computer always boots DOS. This requires changing the active partition to boot the XENIX operating system.

Note
Be sure to make a backup copy of your boot floppies if you use them
to boot your secondary operating system.

3-5

XENIX Installation Guide

3.5 Removing An Operating System From the Hard Disk
You may find that you no longer need one of the operating systems
installed on your hard disk. If you want to delete an operating system, use
fdisk to delete the partition in question. Deleting the partition removes the
contents of that partition and leaves unallocated space.
You can then reallocate that space by either adding another XENIX or
DOS partition, or enlarging an existing partition. Enlarging a partition
requires reinstalling the operating system and (for a XENIX partition)
remaking the filesystem on the partition using mkfs (C). Refer to Chapter
7, "Using Peripheral Devices," of the XENIX Operations Guide if you add a
second XENIX partition and want to designate this partition as a mounted
filesystem.
3.6 DOS Accessing Utilities
There is a set of utility programs which help you bridge the two operating
systems. These are the XENIX commands, such as dosls and dosca t.
described in the XENIX manual page dos(C). These programs allow you
to access DOS files and directories which reside in a non-active DOS partition while running XENIX .
Note that you must have a bootable, although not active DOS partition on
the hard disk in order to use these XENIX commands.
You can list, copy, move and view the contents of DOS files and DOS
directories. You may also be able to use the XENIX dd(C) and diskcp(C)
commands to copy and compare DOS floppies. The XENIX dtype(C)
command tells you what type of floppies you have (various DOS and
XENIX types).
Also, the file letcldefaultlmsdos describes which DOS file systems (e.g.
A:, B:, C: ... ) correspond to which XENIX devices.

Note
You can not execute (run) DOS programs or applications under
XENIX.

If you have the XENIX Development System, with the cmerge compiler,
you can create and compile programs that can be run under DOS operating
systems. Refer to tIle XENIX C User's Guide appendix entitled "XE1'-JIX to
MS-DOS: A Cross Developmen t System" and the C Library Guide A ppendix entitled "A Common Library for XENIX and MS-DOS" for more on

3-6

Using DOS and XENIX On the Same Disk

using XENIX to create DOS programs. Also, see the DOS section in the
Programmer's Reference.
3.7 XENIX and DOS On Non- Standard Disks
XENIX provides support for "non-standard" hard disks. The term
"non-standard" refers to hard disks for which there are no correct disk
parameter entries in your computer's ROM.
The correct parameters you specify for your non-standard disk(s) are
stored in the masterboot block, which is the first sector of your boot hard
disk drive. You can specify the hard disk characteristics during XENIX
installation and these characteristics are then written out with the rest of
the masterboot block. The special masterboot block resets the disk
parameters to the specified values no matter which operating system is
"Active". This mechanism provides non-standard disk support for both
XENIX and DOS.
Although the special masterboot supports non-standard disks under
DOS, you cannot use XENIX to install DOS on your hard disk. If a nonstandard disk is being used, it is assumed that the user already has some
method to transfer his DOS files to the hard disk.
You should only use the XENIX fdisk to manipulate your hard disk partition table. Using DOS fdisk or custom fdisks provided by hard disk
manufacturers after XENIX has been installed may disable non-standard
disk characteristics, rendering your disk unusable.

3-7

Chapter4
Using the Link Kit
4.1

Introduction

4-1

4.2

Device Drivers 4-1
4.2.1 Installing Device Drivers 4-2
4.2.2 InstallingPreconfigured Drivers 4-3
4.2.3 Installing Older Drivers and Drivers Unaccompanied by
Configuration Shell Scripts 4-4
4.2.4 Troubleshooting 4-7
4.2.5 Creating Special Device Files 4-8

4.3

Allocating and Deallocating Kernel Resources 4-8
,4.3.1 Reconfiguring Because of Persistent Error Messages 4-9
4.3.2 Reconfiguringfor Performance 4-10
4.3.3 Increasing Limited Resources 4-11
4.3.4 Freeing Kernel Space for Drivers 4-13

4.4 Testing and Installing the New Kernel 4-14
4.4.1 Booting the New Kernel 4-14
4.4.2 Creating A New Ixenix 4-15
4.4.3 Removing the Link Kit 4-15

Using the Link Kit

4.1 Introduction
This chapter explains how to add device drivers to the XENIX kernel, tailor
various kernel resource allocations to a given application, and customize
many details of the operating environment.
To change any component of the XENIX kernel it is necessary to use the
Link Kit to relink the kernel. The Link Kit consists of a set of kernel components in the form of relocatable object modules plus various programs
and shell scripts used to link the components together.
The most common use for the Link Kit is to add device drivers to the system. A device driver is the software interface between a peripheral device
and the operating system. Each device that can be used with XENIX must
have a device driver. New drivers are generally supplied when adding a
peripheral device to the system; they must be configured into XENIX
before the device will function.
The Link Kit is also necessary to create new device drivers, and is used in
conjunction with other tools that are included with the XENIX Development System. The device driver material in this chapter is intended for
those who want to install an existing device driver. Driver writers should
read Chapter 8, "Writing Device Drivers", of the C User's Guide. Example device drivers are in Chapter 9, "Sample Device Drivers" of the
C User's Guide.
Users of specialized applications will also find the Link Kit useful for making the operating system conform more closely to the needs of the application. For example, users with large databases may find that they need to
lock more files simultaneously than the current allocation of file locks will
permit. Users who have no need for specialized XENIX features such as
message handling may find that they can get a slight performance boost by
deallocating those features and allocating additional disk buffers.
4.2 Device Drivers
A device driver is a set of routines that communicates with a hardware device, and provides a means by which XENIX can control the device in order
to perform Input/Output (I/O) operations.
A device driver is usually supplied as a single software module. Installing
this software into the kernel is as important as the actual hardware installation. It must be completed before the device can be used. A driver is usually accompanied by an auxiliary program or shell script that helps to form
the links between driver and kernel.

4-1

XENIX Installation Guide

To install a new device driver:
Install the hardware device on the system according to the
manufacturer's instructions.
Boot the system and enter system maintenance mode. All the
operations described as part of the installation process are carried
out in this mode
Make sure the Link Kit is installed. If it is not already installed,
install it using the custom(C) command, described in the Reference
Manual.
If this system's kernel has already been modified, copy the
configuration files back from where they were previously stored.
For example, type:
# cd lusrlsys/conf
# cp .. lio/master . .fio/xenixconf . .fio/linkJenix . .fioldriver. 0

where driver. 0 is the name of the driver installed earlier, if any.
Note that the number sign (#) that precedes example commands is the
super-user prompt. Do not type the number sign. In the example, this
indicates that all link kit use should be carried out while logged in as the
super-user, orin Single User Maintenance Mode.
4.2.1 Ins talling Device Drivers
The exact instructions for installing a new device driver are different for
each type of device. This section contains example commands that may be
slightly different than the actual commands. Read the specific installation
instructions that are provided with the device driver software.
After the Link Kit is installed and the instructions read, the next step
depends on how much of the work has already been done by the driver's
vendors.
Many software vendors provide automatic driver installation utilities compatible with the standard System V installation utilities. If so, insert the
vendor's floppy in the floppy drive and enter:
# custom

Select the option to add a supported product, and follow the instructions
that appear on the screen. custom should run any System V compatible,
automatic installation software provided with the driver. This installs the
device driver software and links a version of the kernel that contains the
new device driver. After cus tom completes, the next step is usually to test

4-2

Using the Link Kit

the newly created kernel. See the device driver documen tation for details.
If no mention is made of custom in the documentation for the individual

driver, use the following procedure.
Move to the directory containing the link kit and copy the necessary files by
entering:

# cd lusrlsys/conf
# cp master master.old
# cp xenixconf xenixconLold
Some older installation sets contain their own versions of master and
xenixconf. These files record the system configuration. If the installation
floppy contains its own master and xenixconf files, an out-of-date and
possibly obsolete kernel will be generated.
Insert the floppy containing the driver into the floppy drive and enter the
following to extract the con ten ts of the installation floppy:

# tar xvf Idev/install
Examine the names of the extracted files. If there are no files named master, xenixconf, c.o, or c.c on the driver installation floppy, the driver is
preconfigured. Proceed to "Installing Preeonfigured Drivers" of this
chapter. Otherwise, proceed to "Installing Older Drivers and Drivers
Unaccompanied by Configuration Shell Scripts" to determine the commands necessary to configure the driver.

4.2.2 Ins taIling Pre configured Drivers
The driver installation floppy may come with a shell script that edits the
link command line to include the new driver. If such a script is present, run
it by entering:
# .Iscript
The documentation should indicate the actual name of script; it is unlikely
to literally be script. Most scripts also create all necessary device nodes; if
this is the case, proceed to "Booting the New Kernel."
If no such script is present, edit the file link-xenix to include the names of
all object files provided. The object files are the files on the distribution
media whose names end in ".0", as in tape.o. Add the names of any new
modules to the ld command line, just before the pairs of arguments of the

4-3

XENIX Installation Guide

form "-1 libJxxx".
Enter
# .I1inkJenix

Linking will take approximately 10 minutes. Once a new XENIX kernel has
been created, proceed to "Creating Special Device Files."
4.2.3 Installing Older Drivers
Configuration Shell Scripts

and

Drivers

Unaccompanied

Any driver configuration shell script that neither installs a preconfigured
driver nor calls configure dates from before the 2.2 release of XENIx.
Many older drivers will work fine with the XENIX 2.2 release, but their shell
scripts are no longer usable. If this is the case, the script must be ignored
and the procedure is the same as for a driver unaccompanied by a
configuration shell script.

Note
SCO makes no warranty, expressed or implied, that any driver working with any earlier release will remain compatible with a 2.2 or later
kernel. The following procedure will allow an earlier driver to be
configured. However, there are dozens of reasons why an earlier
driver may no longer function, few of them directly determinable.

Out of date drivers may simply malfunction when attempting to access
their peripherals, or they may cause a system crash or even more insidious
malfunctions. For this reason, make backup copies of all important files
before attempting to configure an older driver, and test drivers only in Single User Maintenance Mode.

1. Repeat the following procedure for each device driver. Enter:
# rm c.o c.*.o space.o space.*.o

Ignore any error messages of the form "c.o non-existent" or
"space.o non-existent."
2.

4-4

If files named master and xenixconf were extracted when the tar
command was entered, copy the old master and xenixconffiles back
to their original names. This will overwrite the versions of master

Using the Link Kit

and xenixconfthat came with the driver. For example, use the commands:
# cp master. old master

# cp xenixconLold xenixconf
3. Enter the following to obtain the Major DeFice Number (write it
down for later use):

# ./configure -j NEXTMAJOR

4. The driver module is the remaining file or group of files from the
installation media whose names end in ".0". Enter:
# ./routines module1.o module2.0 ...
where modillel.o modllle2.o ... are the list of the driver modules
provided. The list is most likely one module long, but if there's
more than one, list them all.
This command can take as long as 5 minutes. Write down the names
produced. Most of these names are either configurable driver routines or driver priority levels. Some names may be spurious.

5. Driver priority levels have names consisting of the string spl followed by a number between 0 and 7. If there are any strings beginningwith spl present, write down the largest such number under the
heading Interrupt Priority Level. Then cross all spl routines off the
list.
6.

Configurable driver routines all have a common prefix, such as sio.
Each prefix is followed by one of a small group of suffixes: open,
close, read, write, ioctl, strategy, halt, poll, intr, init tab, Jty, or
stream. If there are files that do not fit this pattern, cross them out.
For example. running routines on the sio. 0 driver reveals a long list
of routines that begin with sio, and a single routine, ttinit. In this
case you would cross out ttinit because it doesn't begin with sio.
There are a few other routines in the sio driver that would also be
crossed out, such as siopinit, because of the extra "p." sio is an
extreme case: most drivers will not have spurious routine names
scattered throughout the relevant ones.

If any routine ends with strategy or tab, the peripheral is a block device. If any routine ends with read, write, or ioctl, the device is a character device. A peripheral may be both a block and a character device. If none of these routines are present, consider the peripheral a
character device.

If there is a routine containing the name intr, refer to the hardware
manual to figure out which vector or vectors the device is capable of

4-5

XENIX Installation Guide

interrupting. To get a list of the vectors that are currently in use,
enter:

# .Ivectorsinuse
A few drivers are written to allow vector sharing, but it is better to
give each device a unique vector whenever possible. Associate the
peripheral with an appropriate vector or vectors. Write down the
numbers chosen for the "Vectors".
9. The configure command has the following syntax and must be
entered on a single line:
# .Iconfigure -b -c -m MajocDcvice_Nllmber -v VcctococVectocList

-a LisCOLDrivecRoutines -1 InterrupcPriority_Level

The options have the following definitions and restrictions:
-b

Use if configuring a "block" device .

•c

Use if configuring a "character" device .

•m

Should be followed by the MajorJ)evice.-Number determined earlier.

-a

Should be followed by the list of driver routines determined by running routines and crossing out the extraneous
entries.

-v

Use only if the device has an intr routine; should be followed by the list of vectors determined earlier.

-I

Use only if spl routines appeared when routines was run
earlier, followed by the InterruptYriority_Level.

For example, had it been necessary to configure the serial I/O
driver, the following command would have been used:
# .Iconfigure -c -m 5 -v 3 4 27 28 -a sioopen sioclose sioread
sioclock sioioctl siointr siopoll sioinit -1 7

The ramdisk driver is a simpler example; had it not been present, it
would have been added with the command:
# .Iconfigure -b -m 31 -a ramopen ramclose ram strategy ramtab

configure will produce new C.o and space. 0 files containing updated

4-6

Using the Link Kit

configuration information.

Note
If when routines is run a long list appears containing a number of
different prefixes, each with a healthy complement of configuration
suffixes, this driver package contains not one driver but a driver suite
made up of several drivers. Treat each prefix as an individual driver,
and run configure once for each prefix.

10.

After configure has been run once for each driver, edit the file
linkJenix to include the names of all object files provided. The
object files are the files on the distribution media whose names end
in ".0", as in tape.o. Add the names of any new modules to the Id
command line, just before the pairs of arguments of the form "I libJXXX". Enter:

# .Ilink-xenix
Note that linking takes a while. Once a new XENIX kernel has been
linked, proceed to "Creating Special Device Files."

4.2.4 Troubleshooting
If the followingld error message appears:

Group "DGROUP" larger than 64Kbytes
Reduce the size of some of the other kernel data structures to compensate
for the extra room that the new driver is taking up. See "Allocating and
Deallocating Kernel Resources" in this chapter for detailed instructions.
For hand -configured drivers: if the new kernel links without error, but on
boot-up gets to the letter D and no farther, it is possible that an initroutine
produced when routines was run was never meant to be given on the
configure command line. After rebooting the old XENIX, enter the following commands:

# cd lusr! sysl conf
# .lconfigure -d XXinit -m
# .llink-xenix

MajocJ)evice~umber

-b -c

where Major_Device_Number is the value determined earlier, and XXinit
is the actual name of the initialization routine. Run link-xenix again, copy
the kernel produced to the root directory, reboot, and try again.

4-7

XENIX Installation Guide

4.2.5 Crea ting Special Device Files

In order for programs to gain access to the newly installed devices they
must also exist as files within the filesystem. These files are called special
files and are usually located in the Idev directory. Once again, the specific
installation instructions supplied with the device will give the precise
details of the name to be used for the special file and the other parameters
associated with it. In order to create a special file, use the mknod command. Supply the name of the special file, its type (which can be either "b"
for a block device or "c" for a character device) and the major and minor
device numbers associated with the device. For example, change directories to Idevand enter a command similar to one of these:

# I etc/mknod hcdO b 1 0
# I etc/mknod rhcdO c 1 0
# I etc/mknod hqp c 7 0
Note the convention for setting up disk device names. A digit may be
appended to the mnemonic to indicate the drive number. The "raw" device, or character special device, name has an "r" prefix.
The major device number of the device can be found in the "master" file.
Find a line in this file for an appropriate device. For example, a hypothetical tape driver might be called "tape" at the beginning of the line, and "td"
somewhat further down the same line. The name of the driver should also
correspond to the name of the object module. For example, tape. 0 should
be called "tape" inside the master file.
Next, find the columns at the top of the file marked "bmaj" and "cmaj".
Search down these two columns until a line appears that describes the
driver. Write down the block major device number (bmaj), and the character major device number (cmaD. If either bmaj or cmaj is "0", do not
create any block or character nodes, respectively. Otherwise, these entries
are the major device numbers for the driver.
4.3 Alloca ting and Dealloca ting Kernel Res ources
Besides installing device drivers, the other compelling reason to
reconfigure the kernel is to focus the allocation of the kernel resources to
the needs of a given set of applications.
Some application users will be driven to reconfigure their kernel by persistent kernel error messages appearing on the system console, such as "no
files7' or "Inode Table Overflow." Other users may reconfigure their kernel to strive for better performance during a specific application. Still others may wan t greater amounts of limited resources such as those used for
character-set mapping, orneed more space in order to add device drivers.

4-8

Using the Link Kit

In all four cases, the method is the same: install the Link Kit, run configure
to set the allocation of the appropriate resources, relink the kernel by
invoking the shell script linkJ:enix, copy the kernel to the root directory,
reboot, and test the new kernel.
If the Link Kit is not already installed, install it using the custom(C) command, described in the Reference Manual. After it is installed, enter:

# cd lusrlsys/conf
To move to the directory containing the link kit. To run configure enter:

# .I configure
When the menu appears, choose a category by typing the number preceding it. The resources in that category will be displayed, one by one, each
with its current value. Enter a new value for the resource, or to retain the
current value, simply press RETURN. After all the resources in the
category have been displayed, configure will return to the category menu
prompt. Choose another category to reconfigure or exit configure by
entering 'q'. The nex1 four subsections describe scenarios for
reconfiguring and the kernel resources.
4.3.1 Reconfiguring Because of Persistent Error Messages

The kernel should not be reconfigured because a kernel error message was
received once, or even a couple of times, but when a single message persists. First try to increase a resource by a small amount, and if the problem
persists, increase it by 50 or even 100 percent of its original value. If the
problem is still not solved, more detailed research will be required to locate
the exact program and sequence that causes the error.
System Messages
Inode Table Overflow
Increase NINODE in the Files, Inodes, and Filesystems
category. NFILE and NINODE are usually set equal, but
NINODE may be less in environments where many links are
common.
no file
Increase NFILE in the Files, Inodes, and Filesystems category.
NFILE and NINODE are usually set equal, but NINODE may
be less in environments where many links are common.
panic: Timeout table overflow
Increase NCALLin the "Clock" category.

4-9

XENIX Installation Guide

out of text
Increase NT EXT in the "Processes, Memory Management &
Swapping" category.
4.3.2 Reconfiguring for Performance
The system is configured such that greatest quantities of kernel resources
are assigned to the most common tasks such as reading and writing from
the disk, but performance of the more specialized features (such as interprocess communication) has not been ignored. This balance can be shifted
to conform to individual requirements.
For more common application mixes, the most effective means of increasing performance is to allocate additional disk buffers. More disk buffers
means that less time needs to be spent accessing data on the disk, so performance is enhanced. However. disk buffers consume about 1.1K of
memory apiece. There are two sorts of buffers. bufs and sablifs, distinguishable bywhatmust be sacrificed in order to squeeze in more of them.
The quantity of buts represents a tradeoff between buffers and user
memory. Optimum performance is achieved when there is enough
memory to hold all of the processes that normally run simultaneously, and
the rest of user memory is occupied by bUfs. Having too many disk buffers
for the application may cause excessive swapping, and will limit the size of
the largest process that can be run. Having too few buffers causes additional time to be spent performing disk I/O.
The quantity of System Addressable Buffers, or "sabufs", represents a tradeoff between buffers and other kernel resources.
A small amount of kernel resource space is available for additional device
drivers, but it can be allocated to sabufs, if desired. Beyond this, additional sabufs should only be allocated if other kernel resources are not
beingused.
By deallocating all semaphores, about 1.5K can be freed. By deallocating
all message queue structures, about 3K can be freed. No standard utilities
use either of these constructs, but they should only be entirely deallocated
if no applications that might use these constructs are present. By deallocating all shared data segments, approximately 1.2K can be freed. Since
shared data is used by applications such as spreadsheets and by the emerge
compiler in some memory models, it is usually inappropriate to deallocate
shared data entirely.

4-10

Using the Link Kit

If combined allocated resources consume more than 64K, the ld error message:
Group "DGROUP" larger than 64Kbytes
will appear when the shell script link....xenix is run.
When the configure utility Disk Buffer category is selected, the buffer
resources NBUF, NSABUF, NHBUF and MAXI3UFwill be displayed in
turn.
When the number of bufs, NBUF, is nonzero, its value is the actual
number of disk buffers. When NBUF is zero, the system will autoconfigure
buffers based on the amount of memory available. To find out how many
buffers have been autoconfigured, examine the value of "i/o bufs"
displayed during system boot. The number of sabufs, NSABUF, is not
dependent on memory size.
Each buffer needs a buffer header structure. Buffer headers are
enumerated by the constant MAXBUF. Therefore, if NBUF is changed,
MAXBUF should be set equal to NBUF + NSABUF.
The fourth disk buffer resource, NHBUF, controls the hash buffers that
allow buffered data to be found more quickly. NHBUF should always be a
power of two, such as 64 or 128: if not, all hash buffers between NB UF and
the largest power of two less than NHB UF are wasted.
The basic scheme is to deallocate any unused resources, set MAXBUF and
NBUF to equal, large, numbers, and after finding an appropriate tradeoff
between user memory and external disk buffers, use any remaining near
data space space for additional sabufs, and the few extra buffer headers
that the additionalsabufs will require.
4.3.3 Increasing Limited Resources
Tuning system resources is usually done by application developers. For
instance, a database developer who finds that 70 files rather than 50 files
need to be locked simultaneously may provide a shell script to perform the
reconfiguration. The configure utility has a command-line interface suitable for shell script use; to find the current value of any configurable
resource, enter:

# .Iconfigure -y RESOURCE
To change the value of any resource from the command line, en ter:

# .Iconfigure RESOURCE=value

4-11

XENIX Installation Guide

This interface is in addition to the interactive one; the same resources are
configurable from beth interfaces.
Some resources and motivations to reconfigure them include:
NEMAP
The number of 8-bit channel maps used for character set mapping. Each corresponds to one possible alternate character set.
NCLIST
Clists, or character lists, are small buffers used to read from
and write to serial devices. If NCLIST is insufficient, serial IJO
performance may suffer. No additional performance can possibly be achieved after there are 16 clists per character device,
and most systems need far fewer.
NMOUNT
Determines the maximum number of file systems that can be
mounted at one time. The root file system counts as a
"mounted file system" in this calculation.
NFLOCKS
The number of files that can be locked at once. Since none of
the standard utilities perform file locking, this is also a resourc e
that can be partially deallocated to save space.
NPROC
The nl!mber of processes that can be active anywhere in the system. A process attempting to fork when there are already
NPROC processes active will receive the error EAGAIN (see
intro(S)). If any significant change is made to NPROC,
CMAPSIZ ana :;MAPSIZ should also be changed (see below).
MAXUPRC
The number of processes that a single user can run simultaneously. A process attempting to fork when the user already has
MAXUPROC processes active will receive the error
EAGAIN.
CMAPSIZ, SMAPSIZ
.
These are tables used to hold lists of program segments occupying memory and program segments being swapped, respectively. While they rarely need to be changed themselves, they
should vary with NPROC, each being NPROC * 2 by default.

....

Message Que,ue ResouI-ces
;
The system can have MSGMNI message queues active at any
one time. All the queues, together, can have no more than
MSGTQL messages in them. Each message can contain no
more than MSGMAX bytes. All of the messages on a queue,

4-12

Using the Link Kit

together, can contain no more than MSGMNB bytes.
MSGSEG and MSGSSZ are multiplied to determine the
number of bytes of memory to be allocated for message segments during system initialization. If MSGSEG is zero, its
value is set relative to the amount of memory in the system at
boot time. MSGSEG * MSGSSZ should be no more than
MSGTQL * MSGMAX, but may be smaller to conserve user
memory.
Semaphore Resources
The system can have SEMMNI semaphore arrays active at any
one time. These arrays, together, can contain SEMMNS semaphores. SEMMAP is a table used to manage the memory allocated for semaphores. Each semop(S) call may contain an
array up to SEMOPM semaphore operations. semval of its
semaphores when it exits. Up to SEMMNU processes may
have semaphores whose semvals are adjusted on exit. Each one
of these processes may mark up to SEMUME of its semaphores for this privilege. The maximum value that may be subtracted from a semval on process exit is SEMAEM. The maximum value that a semval may have is SEMVMS.
Shared Data
NSDSEGS is the number of shared memory segments in the
system. NSDSLOTS * NSDSEGGS is the maximum number
of simultaneous attaches to shared memory segments.
NODE
The node name is used as a machine identifier by certain communication programs. It can be printed out by entering:
# uname -n

4.3.4 Freeing Kernel Space for Drivers
This type of resource fine-tuning is similar to reconfiguring for performance. A reasonable first attempt would be to halve the allocations of
each resource in configure's "Message Queue", "Shared Data", and
"Semaphore" categories, except for the semaphore values SEMVMX,
SEMAEM, and SEMOPM, which are not strictly resources and cause no
space to be allocated. Halving the allocation of the other resources in
these categories will free approximately2.2K.
In the 2.2 implementation of XENIX System V, no space will be freed by
decreasing external buffers (NBUF), files (NFILE), inodes (NINODE) or
multiscreens (NSCRN), as each of these resources is allocated out of user
memory, not the precious near data that drivers must occupy.

4-13

XENIX Installation Guide

After configure completes, the kernel is ready to link. Enter:

# '/link-xenix
Note that linking takes a while. Reboot the system as described below to
test the new kernel.
4.4 Testing and Installing the New Kernel

4.4.1 Booting the New Kernel
Test the new kernel before installing it as Ixenix. To do so, enter the following:
# cp /usrlsys/conflxenix /xenix.new
# letc/shutdown

The system now reboots. A boot prompt appears:
Boot
If the RETURN key is pressed, or nothing is entered for a time, the default
operating system image Ixenix is loaded and started. In order to test the
newly installed device drivers, enter the name of the new kernel at the boot
prompt:

xenix.new
and press RETURN. The system is now running with the "new" kernel.
Test the various devices (especially any that have been added).
Be aware that when an alternate kernel is used, ps(C) does not work
correctly unless the - n flag and the pathname of the alternate XENIX kernel
is specified. Forexample:
ps -n Ixenix.new
Whenever a different kernel is booted, remove lusrladmlmessages before

4-14

Using the Link Kit

switching to multi-user mode.

Note
Do not installxenixon the hard disk as Ixenixuntil it is fully tested.

4.4.2 Creating A New Ixenix
When the kernel is satisfactory, install the new kernel on the hard disk.
Enter the following:

# cd lusrlsys/conf
# .Ihdinstall
hdinstall(C) backs up the "old" Ixenix and copies lusrlsyslconflxenix to

Ixenix.
4.4.3 Removing the Link Kit
Once the kernel is made, tested, and installed as Ixenix, the Link Kit may
be removed using custom(C) to save disk space. Before this is done, it is
important to save the master, xenixconf, driver. 0, and link....xenix files.
lusrlsyslio is one suitable place for them. These files are records of system
changes. Unless these files are readily available, any further system
configuration performed after removing and reinstalling the Link Kit will
negate the work performed to reconfigure the system. Type:
# cd lusrl sysl conf
# cp master xenixconf link-xenix driver.o . .Iio
Where driver. 0 is the driver or list of drivers.
A t the beginning of this chapter you were instructed to copy any previously
created backup files into lusrlsys/conjif they existed. Now they exist. If
these files are protected, an accurate picture of the system configuration
can be maintained over anyreconfigurations to come.

4-15

Appendix A
Upgrading Your System
A.

UpgradingYourSystcm

A. UpgradingYourSystem

A-I
A-I

A.I

ShutDown the System

A.2

Backup the System

A.3

Save Special Files A-3
A.3.I Choosing Which Files To Save A-3
A.3.2 Save the Actual Files A-4
A.3.3 Save Data Files and ar(CP) Libraries A-S

A.4

Install the New Operating System

A.S

Relink the Kernel

A-2

A-7

A.6 Reinstall Applications
A.7

Merge Saved Files

A-2

A -8

A-7

A -6

Upgrading YourSystem

A. UpgradingYourSystem
The following procedure shows you how to upgrade your system from an
earlier version of XENIX and does not apply if you are installingXENIX for
the first time.
Part of the process is to com pletely reinstall XENIX. With a com plete reinstallation you are assured of having all the latest software, your disk is less
fragmented when you are finished, and, if you want, you can easily change
the size of the XENIX partition or the size of the XENIX swap zone at this
time.
This procedure does not affect any other operating systems (or partitions),
such as MS-DOS, that currently share the hard disk, unless you choose to
change partition sizes. Refer to Chapter 3 of the XENIX Installation Guide
"Using DOS and XENIX on the Same Disk" if you want to change the size
ofyourXENIX partition.
Before proceeding, be sure to read all available Release Notes, including
new manual pages. Note changes in the software since the last time you
installed XENIX .
Follow these steps to upgrade yourXENIX system:

1. Shut the system down to Single User (System Maintenance) Mode.
2.

Make a full backup of your system.

Save particular files from your current system.

Install the new Operating System.

Relinkthekernel, if necessary.

Reinstall any applications software packages.

Merge the saved files with the reinstalled system.

Note that these are the basic steps and the exact procedure may vary from
site to site. Examples are given wherever possible, but you should know
how to use commands such as tar(C) (orcpio(C».
Remember that an initial pound sign (#) in the examples is the root prompt
and is a reminder that you should execute the listed command only when
logged in as root. You do not enter the pound sign as part ofthecommand.

A-1

Installation Guide

If you have local system modifications to the kernel, such as additional

device drivers, you must relink these into the new link kit after you reinstall
XENIX. Check with the supplier of the other software and refer to "U sing
the Link Kit" in the Installation Guide for further details.
When upgrading from SCQ XENIX -86 System 3.0 to SCQ XENIX -86 System V, you must save applications data files in ASCII or symbolic form, not
as binaries. Thisis because the word order was changed from System 3.0to
System V in XENIX -86.
Binaries from SCQ, IBM, or Microsoft XENIX -286 System 3.0 are compatible with SCQ XENIX -286 System V binaries. However, saving data files
in ASCII or symbolic form is still a good idea.
When you restore files after reinstalling XENIX , use the applications to
convert your data back to binary form. The procedure for saving data files
is discussed in a following section "Data Files and ar(CP) Libraries." Restoring data files is discussed in a following section "Merging Saved Files."
A.I Shut Down the Sys tern

You should be the only person logged in to your computer when you perform the upgrade. Make sure any other users know what you are going to
do, and when you are going to do it. They may wish to make their own
backups before you bring down the system.
Also, advise users to remove unnecessary files. This makes the whole process faster and requires fewerfioppies, if they are youronlybackup media.
Refer to shutdown(C) in the XENIX Reference for information on bringing
the system down to Single User (or System Maintenance) Mode.
A.2 Backup the System
Before you do anything else, make a full backup of the system. Use the
tar(C) or cpio(C) commands. Refer to tar(C) and cpio(C) in the XENIX
Reference. You cannot use any other filesystem backup utilities.
You should make a backup immediately before you upgrade so that you
have the latest possible version of your system. This is especially important
in the case of user files, which can change frequently.
Once again, remove any old, unnecessary files. This makes the whole process faster.

A-2

Upgrading YOllrSystem

A.3 Save Special Files

You can use any backup media, including floppy and tape drives, to save
most of your files. Note that if you use a special driver with your backup
device, you cannot use that device immediately after installing the new kernel, since is not yet linked with the required device driver. Therefore, for
precautionary reasons, we recommend that you backup your files on
floppies before you perform the installation.
Before you can use any special devices, you must relink the new XENIX
kernel. If you have source for the device drivers, save the source code on
the default backup device, the floppy drive, then recompile the driver on
the new system. Also, if you need special, customized libraries, or if any
libraries are furnished with your device drivers, save these libraries with the
device driver source.
This is important, since you can only read information from the default
device, once you reinstall XENIX, until you link the kernel.
A.3.t Choosing Which Files To Save

You should save any files that are customized or are in some way particular
to your system. These files include:
•

Applications data files and arC CP) libraries.

•

Any standard system files that are modified for your site.

•

Any locally created shell scripts or programs.

•

All user directories, subdirectories and files.

At this time, make sure you have the original distributions of any applications packages you use. You must reinstall those software packages after
you upgrade the XENIX system.
Save any files you use with your applications, such as databases and control
files, in ASCII or symbolic form. For example, if you use Lyrix, you should
save all the files in the /usrllib/wp directory. Note that Lyrix data files are
already in ASCII form, and you can save them directly onto your backup
media.
If you are upgrading from XENIX 3.0, you should check the following standard XENIX system files and directories for local changes made to the
XENIX 3.0 standard distribution. Save those files which have local
modifications.

A-3

Installation Guide

XENIX 3.0Files

File or Directory:

Examine for:

I.profile
letc/profile
letc/cshrc
:j:/etc I defaul tl *
:j:/etc/group
:j:/ etc/passwd
t/etc/rc
:j:/ etc I systemid
t/etc/ttys
I etc/ttytype
I etcltermcap
Ilib
lusrlbin/*
lusrl dict/words
lusrlinclude/*
I usrIlib I mail/*
lusrllib/crontab
lusrllib/fontl*
lusrllib Ilintl *
lusrllib/tabset/*
lusr/lib/term/*
lusr/libltmac/*
lusr/lib/uucp/*
:j:/usr/news
/usrlspool/*
:j:/usr/[janed,johnd]

root sh startup script.
System widesh startup script.
System wide csh startup script.
For local changes.
Group database.
User database.
For any local additions.
The name of your system.
Terminal line configuration data.
Terminal line to terminal type mapping data.
For any local entries.
For locally developed language processors.
For local additions.
For local additions to words.
For local additions.
For local mail routing information.
cron daemon database.
For locally developed font libraries.
For locally developed lint libraries.
For locally developed tab setting files.
For locally developed nroff drivingtables.
For locally developed nroff/troffmacros.
For local uucp configuration files and dialers.
For local news.
For current mail. uucP. at, and other files.
User home directories.

It is very important that the files marked with a dagger (t) be examined
carefully before reinstalling on XENIX System V. Check the files for local
additions or changes, but do not replace the System V versions with your
XENIX 3.0 versions. There are changes to content, and sometimes format,
of these files with System V. Using the 3.0 versions of these files can cause
problems. This is the case for most of this list. Those directories marked
with a double dagger (:j:) can safely be copied from your 3.0 system. The
last item in the above list refers to all individual user directories on the Toot
file system. User directories may be in another location or lUST may be
mountable on your system.

A.3.2 Save the Actual Files
When using floppies, make sure they are error free and formatted. XENIX
requires high quality media.

A-4

Upgrading Your Sys tern

The tar command is a convenient way to save files. You can also use the
cpio command. For example, to save the standard system files located in
fete, enter:

# ed /
# tar ev .lete/profile Jcte/group .letc/re .lete/ttys .lctc/ttytypc .lctc/tcrmcap
Remember to use the "relative pathname" format with tar. For example,
specify . fete/profile, not fete/profile, where the dot (.) indicates the pathname is relative to your current directory.
Make sure you label any floppies or tapes you use with their exact contents,
the command used to create the backup, the date and time, and if they are
part of a multi-volume set. If you use more than one volume (floppy or
tape), use the k option with tar.
These commands save some user directories as well as other directories in
lusr:

# cd f
# tar cv .Iusr/johnd .Iusrfjaned .Iusr/spool .Iusrlnews
These commands save all the Lyrix custom system files in fusrllibfwp:

# cd /
# tar cv .Iusr/lib/wp
For more information on tar, see theXENIXReferenee Manual.
A.3.3 Save Data Files and ar(CP) Libraries
If you are upgrading from XENIX -86, you must follow these guidelines for
saving data files and ar libraries. These steps are not necessary under
XENIX - 286, however they are a good precaution.

Data Files
A pplications, such as Multiplan, Informix and Level II COBOL use data
files, which you must save in ASCII or symbolic form.
With Multiplan, use the TRANSFER OPTION command to save data files in
symbolic ( SYLK) format. Then transfer the SYLK files to your backup
media.

A-5

Installation Guide

See the "Command Directory" in the Multiplan User's Guide for more
information on TRANSFER OPTION. See also Appendix 4 "The SYLK
(Symbolic Link) File Format" in the Multiplan User's Guide.
You can save Informix data files using the Informix UNLOAD command.
Also, with UNLOAD you can transfer a file directly to your backup media.
For information on UNLOAD, see your Informix manual under
"dbstatus. "
All Level II COBOL programs you create are completely portable, so you
can save them using tar or cpio without any special handling. However,
C-ISAM® files created under XENIX -86 3.0 cannot be transferred to
XENIX-86 System v. You must recreate any such files on the new system.
Extracting and merging your data files is described in "Merging Data Files"
and "ar(CP) Libraries", in this appendix.
ar(CP) Libraries
To save ar archive files, you:
•

Extract the files that make up the archive from the archive file.

•

Save the eJl.iracted files on your backup media.

For example:
# cd lusr/lib
# ar xv libisam.a

When the extract command is finished, you save the resulting files on your
backup media:
# tar cv 'ar t libisam.a'

Recreating archives on the new system is discussed "Merging Data Files"
and "ar(CP) Libraries", in this appendix.
A.4 Install the New Operating System
After you have backed up the system and saved all special files that you
need for your system, install the new release. Follow the instructions in the
XENIX Installation Guide to install the XENIX Operating System.

If you have special device drivers, you need to link them into the XENIX
kernel when you are finished installing. In this case, make sure you install
the link kit software when you reinstall XENIX .

A-6

Upgrading YourSystem

Also, if you are upgrading from XENIX 3.0, you must recompile any device
drivers under SeQ XENIX System V. If you are going to recompile any
device drivers, be sure to install the Development System. If you do not
have source code for the device drivers you usc, you should obtain new
binaries which run under SeQ XENIX System V from the manufacturer or
vendor of the device.
When you are finished installing, make sure you are in Single User, or System Maintenance Mode. Then return to the next section to merge the special files you saved with your new operating system.
A.S Relink the Kernel
If you are upgrading from XENIX 3.0 and have special device drivers, you
must:

•

Recompile the software under XENIX System V, or obtain a
replacemen t.

•

Link the driver into the XENIX kernel with the link kit.

Any device drivers compiled under SeQ XENIX 3.0 must be recompiled
under System V . You may have to obtain an seQ XENIX System V version
of any driver from the driver or device manufacturer if you do not have
source code.
Make sure you installed the link kit software. If you have not done so, see
custom(C) for information on extracting packages from XENIX System V
distrib utions.
A.6 Reinstall Applications
All SeQ XENIX 3.0 applications run on SeQ XENIX System V. Therefore, you should use the original distribution floppies to reinstall any applications.
See the appropriate release notes and installation manuals for information
on installing any applications programs. Install any such programs as if this
is the first time.
Do not copy or save the applications from the old system, unless the original distributions are lost or damaged, and you cannot replace them. It is
safer to reinstall applications software packages.

A-7

Installation Guide

A.7 Merge Saved Files
Once XENIX and any applications are reinstalled, you can merge in ilew
files. This section describes the procedure for merging standard system
files, data files, and arlibraries.

Note
Remember that all commands given in this section are only examples. The exact procedure depends upon how and in what order you
saved your files and directories.

For standard system files, except for /usr/spool and /usr/fjaned,johnd]
files, prepare a temporary directory and extract the files from a backup
volume into this directory:

# mkdir lusr/convert
# cd lusrlconvert
# tar x
Move the exiracted files to their correct locations, for example if you have
exiracted files which belong in lete:

# mv .I etc/* I etc
Repeat the tar exiraction for each volume you made.
The spooling directory and the users' home directories are very simple to
exiract directly into the correct directories. For example, with the media
containing lusrlfjohnd,janed] and lusr/spool mounted in the default device, enter:

# cd lusr
# tar xv
Special Lyrix files can be extracted in place from your backup media. For
example, with the backup volume containing lusrl/iblwp mounted in the
default device:

# cd lusrllib/wp
# tar xv

A-8

Upgrading YourSystem

Other files, however, must be merged into the distributed versions by
hand, for example, with the following files already extracted into the convert directory:

# cd lusr/convert/etc; cp passwd group ttytype letc
# cd lusr/convert/usrllib
# cp crontab lusrlspooI/cron/crontabs/root
Be careful when merging files, especially complex data files like letc/rc,
letc/termcap, or letc/ttys. Use the diff(C) program to note the differences
between newly installed files, and those you save from your previous system. Add the differences, if they are necessary, to the new System V flIes.
Do not directly overwrite the System V versions with your 3.0 version files.
After all the files have been examined and local site information is merged
in to the System V files, remember to clean up:

# cd I ; rm -fr lusrlconvert

Merge Da ta Files
For Multiplan data files that are saved in symbolic form, extract them into
the appropriate directories from the backup media. Then use the Multiplan command TRANSFER OPTIONS to translate the file from symbolic
form.
With Informix, extract the data files into the appropriate directories. Use
the LOAD command, described in the "dbstatus" section of the Informix
manual.

ar(CP) Libraries
To merge archive and library files, create a scratch directory, or work in
Itmp. Mount the backup volume containing the appropriate libraries.
Remember, you saved them individually.
Extract the files, for example:
# cd Itmp
# tar xv
Rearchive the extracted files, for instance with our libisam. a example:

# ar ruv libisam.a *.0

A-9

Installation Guide

When the archive is created, run the ranIib program:

# ranlib lib isam. a
Finally, move the new archive back to the appropriate directory and
remove any unneeded files:
# mv libisam.a lusrllib
# rm *.0

Your upgrade is now com plete.

A-IO

12-19-86
512-210-041

Infonuation in this document is subject to change without notice and
does not represent a commitment on the part of The Santa Cruz
Operation, Inc. nor Microsoft Corporation. The software described
in this document is furnished under a license agreement or
nondisclosure agreement. The software may be used or copied only
in accordance with the tenus of the agreement. It is against the law to
copy this software on magnetic tape, disk, or any other medium for
any purpose other than the purchaser's personal use.

ALL
USE,
DUPLICATION,
OR
DISCLOSURE
WHATSOEVER BY THE GOVERNMENT SHALL BE
EXPRESSLY SUBJECT TO RESTRICTIONS AS SET FORTH
IN SUBDIVISION (b) (3) (ii) FOR RESTRICTED RIGHTS IN
COMPUTER SOFTWARE AND SUBDIVISION (b) (2) FOR
LIMITED RIGHTS IN TECHNICAL DATA, BOTH AS SET
FORTH IN FAR 52.227 -7013.

This document was typeset with an IMAGEN® 8/300 Laser Printer.
Microsoft, MS-DOS, and XENIX are trademarks of Microsoft
Corporation.
IMA GEN is a registered trademark ofIMA GEN Corporation.
UNIX is a trademark of AT&T Bell Lab oratories.

SCO Document Number: XG-5-1-86-3.0

Contents
1
1.1
1.2
1.3
1.4
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
3

3.1
3.2
3.3
3.4
3.5
3.6
4

4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.13

Introduction
Overview 1-1
TheXENIXSystem 1-1
The XENIX Working Environment
AboutThisGuide 1-3

1-1

Demonstration
Introduction 2-1
Before You Log In 2-1
Logging In 2-1
Typing Commands 2-2
Mistakes in Typing 2-4
Read-Ahead and Type-Ahead 2-4
Strange Terminal Behavior 2-5
Stopping a Program 2-5
Logging Out 2-5
Basic Concepts
Introduction 3-1
Files 3-1
File Systems 3-3
Naming Conventions 3-4
Commands 3-9
Input and Output 3-11
Tasks
Introduction 4-1
Gaining Access to the System 4-1
Configuring Your Terminal 4-3
Editing the Command Line 4-4
Manipulating Files 4-5
Manipulating Directories 4-11
Moving in the File System 4-15
Using File and Directory Permissions 4-17
Processing Information 4-21
Controlling Processes 4-26
Getting Status Information 4-28
Using the Lineprinter 4-30
Communicating with Other Users 4-34
-i-

4.14
4.15
4.16
4.17

Using the System Clock and Calendar 4-35
Using the Automatic Reminder Service 4-37
Using Another User's Account 4-37
Calculating 4-37

- ii-

Chapterl
Introduction
1.1

Overview 1-1

1.2 TheXENIXSystem

1-1

1.3 The XENIXWorking Environment
1.4 AboutThisGuide

1-3

1-1

Introduction

1.1 Overview

This guide introduces key concepts of the XENIX system by presenting
them in a tutorial format.

It begins with a "demonstration" that explains an actual computer session,
including command usage and correcting typing errors. Basic concepts
such as files, commands, and pattern matching are also introduced.
Finally, these and other concepts are applied to many "real world" examples, such as file manipulation, terminal configuration, process control,
and status information.

Note
This guide should be read before the other XENIX documentation;
however, for more detailed discussions of all topics covered here,
consult the other user's and reference guides in the set.

1.2 The XENIX System

The XENIX system consists of a general-purpose multi-user operating system and over one hundred utilities and application programs. In addition
to the XENIX Operating System described in this guide, two other XENIX
system packages are available: the XENIX Development System and the
XENIX Text Processing System.
1.3 The XENIX Working Environment

The XENIX system is built around the XENIX operating system. The purpose of an operating system is to efficiently organize and control the
resources of a computer so that they can be used by real people. These
resources include memory, disks, lineprinters, terminals, and any other
peripheral devices connected to the system. The heart of the XENIX system is a "multi-user" and "multi-tasking" operating system. A multi-user
system permits several users to use a computer simultaneously, thus providing lower cost in computing power per user. A multi-tasking system
permits several programs to run at the same time and increases productivity because multiple programs can run simultaneously rather than in
sequence.
Because UNIX™ (and thus XENIX) is an accepted standard for "highend" operating systems, a great deal of software is available for this

1-1

Introduction to XENIX

environment. In addition, XENIX provides file access to the MS-DOS TM
operating system, the most widely used 16-bit operating system in the
world. For systems that support DOS, XENIX provides commands that let
you access DOS format files and disks. The XENIX system also includes
several widely praised enhancements developed at the University of
California at Berkeley, and a visual interface similar to other Microsoft
productivity tool interfaces.
Other characteristics of the XENIX system include:
-

A powerful command language for programming XENIX commands. Unlike other interactive command languages, the XENIX
"shell" is a full programming language.

Simple and consistent naming conventions. Names can be used
ab solutely, or relative to any directory in the file system.

Device-independent input and output: each physical device, from
interactive terminals to main memory, is treated like a file, allowing
uniform file and device input and output.

A set of related text editors, including a full screen editor.

Flexible text processing facilities. In XENIX, commands exist to
find and extract patterns of text from files, to compare and find
differences between files, and to search through and compare directories. Text formatting, typesetting, and spelling error-detection
facilities, as well as a facility for formatting and typesetting complex
tables and equations are also available.

A sophisticated "desk-calculator" program.

Mountable and dismountable file systems that permit addition of
floppy disks to the file system.

A complete set of flexible directory and file protections that allows
all combinations of read, write, and execute access for the owner of
each file or directory, as well as for groups of users.

Facilities for creating, accessing, moving, and processing files and
directories in a simple and uniform way.

1-2

Introduction

1.4 AboutThis Guide
This guide is organized as follows:
Chapter 1, "Introduction," gives an introduction and overview of the
XENIX system.
Chapter 2, "Demonstration," gives you hands-on experience in using the
XENIX system.
Chapter 3, "Basic Concepts," explains the fundamental concepts that you
need to understand before you begin to use the system. Included here are
sections on the file system, naming conventions, commands, and input
and output.
Chapter 4, "Tasks" explains how to perform everyday tasks using
appropriate XENIX commands.

1-3

Chapter2
DeDlonstration
2.1 Introduction 2-1
2.2 Before You Log In 2-1
2.3 Logging In 2-1
2.4 Typing Commands 2-2
2.5 Mistakes in Typing 2-4
2.6 Read - Ahead and Type-Ahead 2-4
2.7 Strange Terminal Behavior 2-5
2.8 Stopping a Program 2-5
2.9 Logging Out 2-5

- 2-i-

Demonstration

2.1 Introduction
This chapter contains a demonstration run designed to help you get used to
the XENIX system, so that you can quickly start to make effective use of it.
It shows you how to login, how to enter at your keyboard, what to do about
mistakes in entering, how to enter commands and how to log out.
2.2 Before You Log In
Before you can log in to the system, your name must be added to the
XENIX user list. At that time you will be given a login name and a pass-

word. You may have to add your name yourself, or someone else may be
assigned this task; it all depends on the environment in which your system
is used. In any case, see the XENIX Operations Guide and mkuser(C) for
detailed information on adding users.
When you are given an account on the XENIX system you will also receive a
user name, a password, and a login directory. Once you have these, all you
need is a terminal from which you can log in to the system. XENIX supports most terminals and you should have no problem getting your terminal
to work with XENIX. Once :lgain, see the XENIX Operations Guide for
more information on how to configure your terminal.
2.3 Logging In
Normally the system is sitting idle with a "login:" prompt on the terminal
screen. If the system displays nonsense characters when you enter text,
then your terminal is probably receiving information at the wrong speed
and you should check your terminal switches. If the switches are set
correctly, push the BREAK or INTERRUPT key a few times.
When you get a "login:" message, enter your login name, then press
RETURN; the system will not do anything until you do. If a password is
required, you will be asked for it. The password that you enter does not
appear on the screen. This prevents others from viewing it. Do not forget
to press RETURN after you enter your password. Next you see the line
TERM = (unknown)
Enter your terminal type (for example, ansi) and press RETURN.
A successful log in produces a "prompt character", a single character that
indicates the system is ready to accept commands. The prompt is usually a
dollar sign ($) or a percent sign (%).

2-1

Introduction to XENIX

You may also get a login message such as:
You have mail
telling you that another system user has sent you mail.
2.4 Typing Com~ands
Once the prompt character appears, the system is ready to respond to commands entered at the terminal. Try entering:
date
followed byRETURN. The system responds by displaying something like:
MonJun 1614:17:10EST 1985
Do not forget to press the RETURN key after the command, or nothing will
happen. The RETURN key will not be mentioned again, but do not forget
-- it has to be entered at the end of each command line. On some terminals
RETURN may be labeled "ENTER" or "CR", but in all cases, the key performs the same function.
Another command you might try is who, which lists the names of everyone
who is logged in to XENIX. A typical display from the who command might
look something like this:
you
joe
ann

console

ttyOl
tty02

Jan 16
Jan 16
Jan 16

14:00
09:11
09:33

The time, given in the fourth column, indicates when the user logged in;
ttynn is the system name for each user's terminal, where nn is a unique
two-digit number. The console is the special name of the master terminal
that is the default for most operations.
If you make a mistake entering the command name, you will see a message
onyourscreen. For example, if you enter:

whom
the system responds with the message:
whom: not found
Note that case is significant in XENIX. The commands

2-2

who
and
WHO
are not the same; this differs from some operating systems, where case
does not matter.
Now try displaying a message on your screen using the echo command.
Type:
echo hello world
The echo command does what its name implies and echoes the rest of the
command line to your terminal:
hello world
N ow try this:
echo hello world> greeting.file
This time the echo command sends its output to a new file named
greeting.file, instead of to your terminal. Note the use of the greater-than
sign (> ) to "redirect" the output of the command. Now enter:

Is
to list just the name of the file. To look at the contents of display it by entering:
cat greeting. file
Here "cat" stands for concatenate. One purpose of the cat command is to
combine the contents of several files (that is, "concatenate") and put them
in some new file. However, since your terminal display is treated like any
other file in XENIX, cat is most commonly used to display the contents of
files on the screen. Therefore the above command sends the following output to your terminal screen:
hello world
To remove greeting. file, enter:
rm greeting. file

2-3

Introduction to XENIX

Note that XENIX command names are often shortened to mnemonic
names. For example, cp is short for "copy", Is is short for "list", no is
short for "remove", cat is short for "concatenate", mkdir is short for
"make directory", and chmod is short for "change mode".
2.5 Mistakes in Typing
If you make a mistake in entering while entering a command, there are two
ways to edit the line, provided you have not yet pressed RETURN. Pressing
the BKSP key causes the last character entered to be erased. Backspacing
with the BKSP key can erase characters back to the beginning of the line,
but not beyond. Thus, if you type badly, you can correct as you go. For
example, entering:
ddBKSPateRETURN
is the same as
dateRETURN
The XENIX kill character, Ctrl-u, erases all of the characters entered so
far on the current input line. So, if the line is irretrievably fouled up, enter
Ctrl- u and start the line over.
If you must enter a BKSP or Ctrl- u as part of the text, precede it with a
backslash (\), so that the character loses its special ""erase"" meaning.
To enter a BKSP or Ctrl- u in text, enter "\BKSP" or "\Ctrl- u". The system
always prints a new line on your terminal after your Ctrl-u, even if preceded by a backslash. Nevertheless, the Ctrl- u will have been recorded.

To erase a backslash, backspace twice with the BKSP key, as in
"\BKSPBKSP". The backslash is used extensively in XENIX to indicate
that the following character is in some way special. Note that the functions
performed by BKSP and Ctrl-u are available on all XENIX systems; however, the keys used to perform these functions may vary and can be set by
the user with s tty (C).
2.6 Read- Ahead and Type- Ahead
XENIX has full read-ahead, which means that you can type as fast as you
want, whenever you want, and XENIX will remember what you have
entered. If you enter any text while a command is displaying text on the
screen, your input characters appear intermixed with the output characters
on the screen, but they are stored away and interpreted in the correct
order. Therefore, you can enter severai commands (i.e., "type ahead")
one after another without waiting for the first to finish. Note that this does

2-4

Demonstration

not work when you log in; type-ahead does not work until after you have
entered your password and the dollar sign ($) prompt appears.
2.7 Strange Terminal Behavior
Occasionally, your terminal may act strangely. You can often fix such
behavior by either turning your terminal off, then quickly turning it back
on, or logging out and logging back in; this will reset your terminal characteristics. It is often helpful to enter a Ctrl- q. This restores terminals that
are (inadvertantly or otherwise) in anon -echoeing mode. Ctrl- s stops
display to the screen, Ctrl- q restarts display. If logging out and back in,
turning the terminal off and on, and entering Ctrl- q does not work, read
the description of the command stty(C) in the XENIX Reference Manual
for more information about setting terminal characteristics. Also, refer to
the next section, "Stopping a Program."
2.8 Stopping a Program
You can abort the execution of most programs and commands by pressing
the INTERRUPT key (perhaps called DEL, DELETE, Ctrl- c, or RUBOUT
on your terminal). The BREAK key found on many terminals can also be
used. Inside some programs, like most text editors, entering INTERRUPT
stops whatever the program is doing without aborting the program itself.
Throughout this manual, when we say "send an interrupt" we mean press
the INTERRUPT key.
2.9 Logging Out
To end a session with XENIX, you must log out. This is done by entering
Ctrl- d as the first character on a line. It is not sufficient just to tum off the
terminal, since this does not log you out. Some programs can also be
ended byenteringCtrl-d, so beware.

2-5

Chapter3
Basic Concepts
3.1 Introduction 3-1
3.2 Files
3.2.1
3.2.2
3.2.3
3.2.4

3-1
Ordinary Files 3-1
Special Files 3-2
Directory files 3-2
Directory Structure 3-2

3.3 File Systems 3-3
3.4 Naming Conventions 3-4
3.4.1 Filenames 3-4
3.4.2 Pathnames 3-5
3.4.3 Sample Names 3-5
3.4.4 Special Characters 3-6
3.5 Commands 3-9
3.5.1 Command Line 3-9
3.5.2 Syntax 3-10
3.6 Input and Output 3-11
3.6.1 Redirection 3-12
3.6.2 Pipes 3-13

Basic Concepts

3.1 Introduction
This chapter will give you an understanding of the basic concepts you need
to function in the XENIX environment. After reading this chapter you
should understand how the system's files, directories, and devices are
organized and named, how commands are entered, and how a command's
input and output can be manipulated. This chapter begins with a discussion of files.
3.2 Files
The file is the fundamental unit of the XENIX file system. In XENIX there
are really three different types of files: ordinary files (what we usually mean
when we say "file"), directories, and special files. Each of these types of
files is describ ed below.
3.2.1 Ordinary Files
Ordinary files typically contain textual information such as documents,
data, or program sources. Executable binary files are also of this type. An
ordinary file is simply a named concatenation of 8-bit bytes. Whether
these bytes are interpreted as text characters, binary instructions, or program statements is up to the programs that examine them. Every ordinary
file has the following attributes:
-

A filename (not necessarily unique)

A unique system number called an inode number

A size in bytes

A time of creation

A time of modification

A time of last access

A set of access permissions

Files can be protected by assigning appropriate access permissions to
assure privacy and security. This is done byprovidingread-write-execute
permissions to files so that the user can control access by the owner, by a
group of users, and by anyone else. By default, the owner of a file is its
creator. The owner can read the file or write to it. By default, other users
can read a file owned by another, but not write to it. File permissions can
be altered with the chmod command. This command is discussed in
Chapter 4 of this manual.

3-1

Introduction to XENIX

3.2.2 Special Files
Special files correspond to physical devices such as hard anp floppy disks,
lineprinters, terminals, and system memory. They are called "device special files". These files are not discussed in this manual.
3.2.3 Directory files
Directory files are read -only files containing information about the files or
directories that are conceptually (but not physically) contained within
them. This information consists ofthe name and inode number of each file
or directory residing within the given directory. An inode number is a
unique number associated with any given file. All files on the system have
inode numbers. A name/inode number pair is called a link. The Is command is used to examine directory files and to list the information about the
files conceptually within the named directory. With the inode number, the
Is command can also find other information about a file.
The nesting of directories inside other directories is the way in which
XENIX implements its characteristic tree-structured directory system.
Directories are discussed further in the next section.
Like ordinary files, directories can be protected by assigning appropriate
access permissions to assure privacy and security. This is done by giving
read-write-search permissions to directories so that the user can control
directory access by the owner, by a group of users, and by anyone else.
Write permission determines whether files can be added or removed from
a directory. By default, the owner of a directory is its creator, and the
owner can read, create or remove files within that directory. Similarly by
default, a user can read files within the directory of another, but not add or
remove files. As with file permissions, directory permissions can be altered
with the chmod command. Default permissions can be altered with the
umask command.
3.2.4 Directory Structure
With mUltiple users and multiple projects, the number of files in a file system can proliferate rapidly. Fortunately, as mentioned earlier, XENIX
organizes all files into a tree-structured directory hierarchy. This tree
structure should be thought of as a physical world in which the user can
move from place to place. "Places" are directories. Each user of the system has his own personal directory. Within that directory, the user may
have directories or other subdirectories owned and controlled only by the
user.
\Vhen you log in to XENIX, you are "in" your directory. Unless you take
special action when you create a file, the new file is created in your working

3-2

Basic Concepts

directory. This file is unrelated to any other file of the same name in someone else's directory.
A diagram of part of a typical user directory is shown in Figure 3-1.
usr

/ I\

/
\
/
\
mary
adam eve
/
\
/
\
text
text
/
\
text
temp
Figure 3-1 A Typical User Directory
In Figure 3-1, the usr directory contains each user's own personal directory. Notice that Mary's file named text is unrelated to Eve's. This is not
important if all the files of interest are in Eve's directory, but if Eve and
Mary work together, or if they work on separate but related projects, this
division of files becomes handy indeed. For example, Mary could print
Eve's text by typing:

pr /usrl eve/text
Similarly, Eve could find out what files Mary has by typing:
Is /usrlmary

3.3 File Systems
A file system is a set of files organized in a certain way. In XENIX, this set of
files consists of all available resources including data files, directories, programs, lineprinters, and disks. Thus, the XENIX file system is a system for
accessing all system resources.
To logically structure the resources of the system, the XENIX file system is
organized hierarchically in an inverted "tree structure". See Figure 3-2 for
an illustration of a typical tree-structured file system. In this typical tree of
files, the root of the tree is at the top and branches of the tree grow downward. Directories correspond to nodes in the tree; ordinary files
correspond to "leaves". If a directory contains a downward branch to
other files or directories, then those files and directories are "contained" in
the given directory. It is possible to name any file in the system by starting
at the root (where the root is at the top) and traveling down any of the
branches to the desired file. Similarly, you can specify any file in the
3-3

Introduction to XENIX

system, relative to any directory. Specification of these files depends on a
knowledge of the XENIX naming conventions, discussed in the next section.
I
II

(root)

I \\

\
usr
dev
1\\
I
\
tty
doug
neil

bin
I
cmd

II
mail news

I \\

text

data

Figure 3· 2 A Typical File System
In the typical tree-structured file system of Figure 3-2, the "tree" grows
downward. The names bin, usr, dev, doug, and neil all represent directories, and are all nodes in the tree. In XENIX the name of the root directory is given the one-character name, " I ". The names mail, news, text,
and data all represent normal data files, and are all "leaves" of the tree.
Note that the file cmd is the name of a command that can be executed. The
name tty represents a terminal and is also represented in the tree.
3.4 Naming Conventions
Every single file, directory, and device in XENIX has both a filename and
an absolute pathname. This pathname is a map of the file or directory's
location in the system. The absolute pathname is unique to all names in the
system; filenames are unique only within directories and need not be
unique system-wide. This is similar to someone whose "global" name is
John Albert Smith in a telephone directory, but who may be listed simply
as John in an office phone list.
3.4.1 Filenames
A simple filename is a sequence of one to fourteen characters other than a
slash (I). Every single file, directory, and device in the system has a
filename. Filenames are used to uniquely identify directory contents.
Thus, no two filenames in a directory may be the same. However,
filenames in different directories may be identical.
Although you can use almost any character in a filename, it is best to
confine filenames to the alphanumeric characters and the period. Other
characters, especially control characters, are discouraged for use in
filenames. When a filename contains an initial period, it is "hidden", and

3-4

Basic Concepts

is not displayed by the Ic command. However the Is-a command will
display the hidden files. The dash (-) is used in specifying command
options, and should be avoided when naming files. In addition, the question mark (?), the asterisk (*), brackets ([ and ]), and all quotation marks
should never be used in filenames, since they are treated specially when
entering commands.
3.4.2 Pathnames
A pathname is a sequence of directory names followed by a simple
filename, each separated from the previous name by a slash. H a pathname
begins with a slash, it specifies a file that can be found by beginning a search
at the root of the entire tree. Otherwise, files are found by beginning the
search at the user's current directory (also known as the working directory).
The current directory should be thought of as your location in the file system. Think of it as a physical place. When you change your current directory you are moving to some other directory or place in the file system.
A pathname beginning with a slash is called a full (or absolute) pathname
because it does not vary with regard to the user's current directory. A pathname not beginning with a slash is called a relative pathname, because it
specifies a path relative to the current directory. The user may change the
current directory at any time by using the cd command. The user may
display the current directory by using the pwd command.
3.4.3 Sample Names
Some sam pIe names follow:

The absolute pathname of the root directory of the
entire file system.

Ibin

The directory containing most of the frequently used
XENIX commands.

lusr

The directory containing each user'-s personal directory. The subdirectory, lusrlbin contains frequently
used XENIX commands not in Ibin.

I dev

The directory containing files corresponding to physical devices (e.g., terminals, lineprinters, and disks).

I devI console

The name of the system master terminal.

Idev Itty

The name of the user's terminal.

llib

The directory containing files used by some standard
commands.

3-5

Introduction to XENIX

This directory contains temporary scratch files.

Itmp

lusr/joe/projectlA
A typical full pathname; this one happens to be a file
named A in the directory named project belonging to
the user named joe.
bin/x

A relative pathname; it names the file x in subdirectory bin of the current working directory. H the
current directory is I, it names Ibinlx. H the current
directory is /usr/joe, it names /usr/joe/bin/x.

file 1

Name of an ordinary file in the current directory.

When usingtheXENIXsystem, each user resides "in" a directory called the
current directory. All files and directories have a "parent" directory. This
directory is the one immediately above, which "contains" the given file or
directory. The XENIX file system provides special shorthand notations for
this directory and for the current directory:
The shorthand name of the current directory. Thus . /filexxx
names the same file as filexxx, if such a file exists in the current
directory.
The shorthand name of the current directory's parent directory.
The shorthand name .. I .. refers to the directory that is two levels
"above" the current directory
3.4.4 Special Characters
XENIX provides a pattern -matching facility for specifying sets of
filenames that match particular patterns. For example, examine the problem that occurs when naming the parts of a large document, such as a
book. Logically, it can be divided into many small pieces such as chapters
or sections. Physically, it must be divided too, since the XENIX editor vi
cannot handle really big files.
Thus, you should divide a large document into several files. The points at
which the document is divided should follow a logical order. You might
have a separate file for each chapter:
chap1
chap2

3-6

Basic Concepts

Or, if each chapteris broken into several files, you might have:
chap1.1
chap1.2
chap 1. 3
chap2.1
chap2.2
You can then tell at a glance where a particular file fits into the whole.
There are other advantages to a systematic naming convention that are not
so obvious. What if you want to print the whole book on the lineprinter?
You could enter:
lpr chap1.1 chap1.2 chap1.3 ...
but you will tire of this quickly and will probably even make mistakes. Fortunately, there is a shortcut: a sequence of names containing a common
pattern can be specified with the use of special characters. The special
characters discussed in this chapter are:
* Matches zero or more characters
[] Matches any character inside the brackets
? Matches any single character
For example, you can enter:
lpr chap*
The asterisk (*), sometimes called "star" or "splat" in XENIX, means
"zero or more characters of any type", so this translates into "send all files
whose names begin with the word "chap" to the lineprinter".
This shorthand notation is not a unique property of the Jpr command; it
can be used in any command.
U sing this fact, you can list the names of the files in the book by typing:
Is chap*

3-7

Introduction to XENIX

This produces
chap 1. 1
chap1.2
chap 1. 3
The star is not limited to the last position in a filename; it can be used anywhere and can occur several times. A star by itself matches all filenames
not containing slashes or beginning with periods, so:
cat *
displays all files in the current directory on your terminal screen.
The star is not the only pattern-matching feature available. Suppose you
want to print only chapters 1 through 4, and 9. You can say:
Ipr chap[12349]*
The brackets ([ and ]) mean "match any of the characters inside the
brackets." A range of consecutive letters or digits can be abbreviated, so
you can also do this with:
Ipr chap[1-49]*
(Note that this does not match forty-nine filenames, but only five.) Letters
can also be used within brackets: "[a-z]" matches any character in the
range "a" through "z".
The question mark (?) matches any single character, so
Is ?
lists all files that have single-character names, and
Is -1 chap?l
lists information about the first file of each chapter (i.e., chapl.1,

chap2.1, ... ).
H you need to turn off the special meaning of any of the special characters (

*, ?, and [ ... ]) enclose the entire argument in single quotation marks.

3-8

Basic Concepts

For example, the following command will print out only files named "?"
rather than all one-character filenames:
I s '?'
.

Pattern -matching features are discussed further in Chapter 4 of the XENIX
User's Guide, "The Shell."
3.5 Commands
Commands are used to invoke executable programs. When you enter the
name of a command, XENIX reads the command line that you have
entered, looks for a program with the given name, and then executes the
program if it finds it. Command lines may also contain arguments that
specify options or files that the program may need. The command line and
command syntax are discussed in the next two sections.
3.5.1 Command Line
Whether you are entering commands at a terminal, or XENIX is reading
commands from a file, XENIX always reads commands from command
lines. The command line is a line of characters that is read by the shell
command interpreter to determine what actions to perform. This interpreter, or "shell" as it is known, reads the names of commands from the
command line, finds the executable program corresponding to the name of
the command, then executes that program. When the program finishes
executing, the shell resumes reading the command line. Thus, when you
are entering at a terminal, you are editing a line of text called the
command-line buffer that becomes a command line only when you press
RETURN. This command-line buffer can be edited with the BKSP and
Ctrl-u keys. Pressing RETURN causes the command-line buffer to be submitted to the shell as a command line. The shell reads the command line
and executes the appropriate command. If you press INTERRUPT before
you press RETURN, the command-line buffer is erased. Multiple commands can be entered on a single command line provided they are
separated by a semicolon (;). For example, the following command line
prints out the current date and the name of the current working directory:
date ;pwd
Commands can be submitted for processing in "the background" by
appending an ampersand (&) to the command line. This mode of execution is similar to "batch" processing on other systems. The main advantage

3-9

Introduction to XENIX

to placing commands in the background is that you can execute other commands from your terminal in the "foreground" while the background commands execute. Thus:
du h.1sr >diskuse&
determines the disk usage in the directory lUST, a fairly time-consuming
operation, without tying up your terminal. Note that the output is placed in
the file diskuse by redirecting output with the greater-than symbol.
Redirection is discussed in Section 3.6.1.
3.5.2 Syntax

The general syntax for commands is as follows:
cmd [switches] [ arguments] [filename] [ ••. ]
By convention, command names are lowercase. Switches, also called
options, are flags that select various options available when executing the
command. They are optional and usually precede other arguments and
filenames. Switches consist of a dash prefix (-) and an identifying letter.
For example, the Is command's -I switch (pronounced "minus ell" )
specifies a long directory listing and the command

Is -r
specifies a directory listing in reverse alphabetical order. In some cases,
switches can be grouped to form a single switch argument. For example,
the command

Is -rl
is really a combination of two switches, where the -r1 switch selects the
option that lists all files in the directory in both reverse alphabetical order
and with the long format.
Sometimes multiple switches must be given separately, as in:
copy -a -v source destination
Here the -8 switch tells the copy command to ask the user for
confirmation before copying the source to the destination. The -v switch
specifies the "verbose" option, which reports copying as it happens.

3-10

Basic Concepts

Other arguments, such as search strings, can also be given, as in:
grep' string of text ' outfile
In the above example,

, string of text'
is a single argument and is the search string the grep command searches for
in the file outfile. filename is the argument that specifies the name of a file
required by the command.
Most commands are executable programs compiled by the C compiler or
by some other language compiler. Some commands are executable command files called "shell procedures". Shell procedures are discussed in
Chapter 4 of the XENIX User's Guide, "The Shell."
3.6 Input and Output
By default, XENIX assumes that terminal input comes from the terminal
keyboard and output goes to the terminal screen. To illustrate typical command input and output, enter:
cat
This command now expects input from your keyboard. As input, it
accepts as many lines of text as you enter until you press Ctrl-d as an endof -file or end -0 f - transmission indicator.
For example, enter:
this is two linesRETURN
of inputRETURN
Ctrl-d
When you press Ctrl-d, input ends. The cat command immediately outputs each line as you enter it. Since output is sent to the terminal screen by
default, that is where the two lines are sent. Thus, the complete session
will look like this on your terminal screen:
$cat
this is two lines
this is two lines
of input
of input
$

3-11

Introduction to XENIX

The flow of command input and output can be "redirected" so that input
comes from a file instead of from the terminal keyboard and output goes to
a file or lineprinter, instead of to the terminal screen. In addition, you can
create "pipes" to make the output from one command become the input to
another. Redirection and pipes are discussed in the next two subsections.
When you use cat to send input to a file or pipe, the output is not sent until
the Ctrl-d end-of-transmission indicator is entered.
3.6.1 Redirection
In XENIX a file can replace the terminal for either input or output. For

example:
Is
displays a list of files on your terminal screen. But if you say:
Is > filelist
a list of your files is placed in the file filelist (which is created if it does not
exist). The symbol for output redirection, the greater-than sign (»,
means "put the output from the command into the following file, rather
than display it on the terminal screen." As another example of output
redirection, you can combine several files into one by capturing the output
of catin a file:
cat f1 f2 f3 > temp
The output append symbol (> » operates very much like the output
redirection symbol, except that it means" add to the end of". So:
cat file1 file2 file3 > > temp
means "concatenate filel, file2, and file3 to the end of whatever is already
in temp, instead of overwriting and destroying the existing contents." As
with normal output redirection, if temp doesn't exist, it is created for you.
In a similar way, the input redirection symbol «) means "take the input
for a program from the following file, instead of from the terminal" . Thus,
you could make a script of editing commands and put them into a file called
script. Then you could execute the commands in the script on a file by typing:

ed file < script

3-12

Basic Concepts

As another example, if you used an editor to prepare a letter in the file
letter. txt, you could send it to several people with:
mail adam eve mary joe < letter. txt

3.6.2 Pipes
One of the major innovations of the XENIX system is the concept of a
"pipe". A pipe is simply a way to connect the output of one command to
the input of another, so that the two run as a sequence of commands called
a pipeline.
For example:
sort frank.txt george.txt hank.txt
combines the three files named frank. txt, george.txt, and hank.txt, then
sorts the output. Suppose that you want to then find all unique words in
these files and view the result. You could enter:
sort frank.txt george.txt hank.txt > temp!
uniq < temp! > temp2
more temp2
rm temp! temp2
But this is more work than is necessary. What you want is to take the output of sort and connect it to the input of uniq, then take the output of uniq
and connect it to more • You would use the following pipe:
sort frank.txt george.txt hank.txt

I uniq I more

The vertical bar character ( I ) is used between the sort and uniq commands to indicate that the output from sort, which would normally have
been sent to the terminal, is to be redirected from the terminal to the standard input of the uniq command, which in tum sends its output to the
more command for viewing.
There are many other examples of pipes. For example, this command formats and paginates a list of your files in three columns:

I pr

-3

3-13

Introduction to XENIX

The program we counts the number of lines, words, and characters in its
input, and who prints a list of users currently logged on, one per line. Thus,
this command tells you the number of users who are logged in by counting
the number of lines that comes from the who command:
who

I wc

-1

This command counts the number of files in the current directory:

I wc

-1

Notice the difference in output between we ·1 and we. By default, we tells
you how many lines, word and characters, there are in the input. However,
we ·1 tells you only how many lines.
Any program that reads from the terminal keyboard can read from a pipe
instead. Any program that displays output to the terminal screen can send
input to a pipe. You can have as many elements in a pipeline as you wish.

3-14

Chapter 4
Tasks
4.1

Introduction 4-1

4.2

Gaining Access to the System 4-1
4.2.1 LoggingIn 4-1
4.2.2 Logging Out 4-2
4.2.3 ChangingYourPassword 4-2

4.3

Configuring Your Terminal 4-3
4.3.1 Changing Terminals 4-3
4.3.2 Setting Terminal Options 4-4

4.4 Editing the Command Line 4-4
4.4.1 Entering a Command Line 4-4
4.4.2 Erasing a Command Line 4-4
4.4.3 Halting Screen Output 4-5
4.5 Manipulating Files 4-5
4.5.1 CreatingaFile 4-5
4.5.2 Displaying File Contents 4-5
4.5.3 Combining Files 4-7
4.5.4 Moving a File 4-8
4.5.5 Renaming a File 4-8
4.5.6 Copying a File 4-9
4.5.7 Deleting a File 4-9
4.5.8 Finding Files 4-10
4.5.9 LinkingaFiletoAnotherFile 4-10
4.6 Manipulating Directories 4-11
4.6.1 Printing the Name of Your Working Directory 4-11
4.6.2 Listing Directory Contents 4-12
4.6.3 Creating a Directory 4-14
4.6.4 Removing a Directory 4-14
4.6.5 Renaming a Directory 4-14
4.6.6 MovingaDirectory 4-14
4.6.7 Copying a Directory 4-15
4.7

Moving in the File System 4-15
4.7.1 Finding Out Where You Are 4-16
4.7.2 Changing Your Working Directory 4-16

4.8

U sing File and Directory Permissions 4-17
4.8.1 Changing Permissions 4-19
4.8.2 Changing Directory Search Permissions 4-21

4.9 Processing Information 4-21
4.9.1 Comparing Files 4-22
4.9.2 Echoing Arguments 4-22
4.9.3 Sorting a File 4-23
4.9.4 Searching for a Pattern in a File 4-24
4.9.5 Counting Words, Lines, and Characters 4-24
4.9.6 Delaying a Process 4-25
4.10 Controlling Processes 4-26
4.10.1 Placing a Process in the Background 4-27
4.10.2 Killing a Process 4-27
4.11 Getting Status Information 4-28
4.11.1 Finding Out Who is on the System 4-28
4.11.2 Finding Out What Processes Are Running 4-29
4.11. 3 Finding Out Lineprinter Information 4-29
4.12 Usingthe Lineprinter 4-30
4.12.1 Printing Files: lp 4-31
4.12.2 Usinglp Options 4-31
4.12.3 Cancelling a Print Request: cancel 4-32
4.12.4 Finding Out the Status of A Print Request: lpstat 4-33
4.13 Communicating with Other Users 4-34
4.13.1 Sending Mail 4-34
4.13.2 ReceivingMail 4-35
4.13.3 Writing to a Terminal 4-35
4.14 Using the System Clock and Calendar 4-35
4.14.1 FindingOuttheDateandTime 4-36
4.14.2 Displaying a Calendar 4-36
4.15 Using the Automatic Reminder Service 4-37
4.16 UsingAnotherUser'sAccount 4-37
4.17 Calculating 4-37

Tasks

4.1 Introduction
This chapter explains how to perform common tasks on XENIX. The individual commands used to perform these tasks are discussed more
thoroughly in the XENIX Reference Manual.
4.2 Gaining Access to the System
To use the XENIX system, you must first gain access to it by logging in.
When you log in you are placed in your own personal working area. Loggingin, changing your password, and logging out are described below.
4.2.1 Logging In
Before you can log in to the system, you must be given a system "account."
Your name must be added to the user list, and you must be given a password and a mailbox.
Depending on how your system is administered, you may have to add your
name to the user list yourself, or someone else may be assigned this task. If
you must add your own account to the system, see the XENIX Operations
Guide and mkuser(C) in the XENIX Reference Manual for more information. This section assumes your account has already been set up.
Normally, the system sits idle and the prompt "login:" appears on the terminal screen. If your screen is blank, or displays nonsense characters,
press the INTERRUPT key a few times.
When the "login:" prompt appears, follow these steps:
1. Enter your login name and press RETURN. If you make a mistake,
press Ctrl- u to start the line again. After you press RETURN the
word "Password:" appears on your screen.
2. Enter your password carefully, then press RETURN. The letters do
not appear on your screen as you enter, and the cursor does not
move. If you make a mistake, press RETURN to restart the login
procedure.
If you have entered your login name and password correctly the "prompt
character" appears on the screen. This is usually a dollar sign ($). The
prompt tells you that the XENIX system is ready to acccept commands
from the keyboard.

4-1

Introduction to XENIX

If you make a mistake, the system displays the message:

Login incorrect
login:
If you get this message, follow the above procedure again. You must enter
all the letters of your user name and password correctly before you are
given access to the system; XENIX does not allow you to correct your mistakes when en tering your password.

Depending on how your system is set up, after you log in you may see a
"message of the day" that says something like "Welcome to XENIX", or
an announcement that is of interest to all users.
4.2.2 Logging Out
The logout procedure is simple-all you need to do is press:
Ctrl-d
alone on a line. In general, Ctrl- d signifies the end -of -file in XENIX, and is
often used within programs to signal the end of input from the keyboard.
In such cases, Ctrl- d will not log you out; it will simply terminate input to a
particular program if you are within that program. This means that it may
sometimes be necessary to press Ctrl- d several times before you can log
yourself out. For example, if you are in the mail program you must press
Ctrl- d once to exit the mail program, then again to log out.
4.2.3 ChangingYourPassword
To prevent unauthorized users from gaining access to the system, each
authorized user must have a password. When you are first given an account
on a XENIX system you are assigned a password by the system administrator. Some XENIX systems require you to change your password at regular
intervals. Whether yours does or not, it is a good idea to change your password regularly to maintain system security. This section tells you how to
change your password.
Use the pas swd command to change your password. Follow these steps:

1. Enter:
passwd
and press RETURN.

4-2

Tasks

The following message appears:
Changing password for user
Old password:
2.

Carefully enter your old password. It is not displayed on the screen.
If you make a mistake, press RETURN. The message "Sorry"

appears, then the system prompt. Begin again with step 1.
3. When you have entered your old password the message:
New password:
appears. Enter your new password and press RETURN.
4. The message:
Re-enter new password:
appears. Enter your new password again. If you make a mistake,
press RETURN. The message:
They don't match; try again
appears, and you must begin again with step 1. When you have completed the procedure, the system prompt appears.
4.3 Configuring Your Terminal
On most systems, the standard console terminal is already configured for
use with XENIX. However, other terminals of various types may be connected to a XENIX system. In these cases it is important to know how to set
terminal options and how to specify the terminal you are using. You may
also want to change the standard configuration of the standard console terminal. The following section discusses these topics.
4.3.1 Changing Terminals
The terminal type is displayed each time you log in. If you ever need to log
in to XENIX on a terminal of a type differen t than the terminal you normally
use, you may need to change your environment by editing the .profile file in
your home directory. To do this, use a text editor to locate the tset line that
looks something like this:
eval 'tset -m :\ ?unknown -s -r -Q'

4-3

Introduction to XENIX

Change unknown in this line to the terminal type of your terminal. For
example, if you normally log in on a vt100 terminal, change the line to:
eval 'tset -m :\ ?vt1oo -s -r -Q'
Each time you login you then see the message:
TERM

(vt100)

Press RETURN and the terminal type is set to vt100, or enter another terminal type and press RETURN.
4.3.2 Setting Terminal Options
There are a number of terminal options that can be set with the command
stty. When entered without parameters, stty displays the current terminal
settings. For example, typical output might look like this:
speed 9600 baud
erase '''h' ; kill ,"u'
even -nl
Each of the above characteristics can be set with stty. For more information, see stty(C) in theXENIXRe!erence Manual.
4.4 Editing the Command Line
When you sit in front of a terminal and enter commands at your keyboard,
there are a number of special keys that you can use. The most useful ones
are described below.
4.4.1 Entering a Command Line
From your terminal, entering a command line consists of typing characters
then pressing RETURN. Once you have pressed RETURN the computer
reads tIle command line and commands specified on that line are executed.
You may enter as many command lines as you want without waiting for
commands to complete, because XENIX supports type-ahead of characters.
4.4.2 Erasing a Command Line
When entering commands, typing errors are bound to occur. To erase the
current command line, press Ctrl- u.

4-4

Tasks

4.4.3 Halting Screen Output

In many cases, you will be examining the contents of a file on the terminal
screen. For longer files, the contents will often scroll off the screen faster
than you can examine them. To temporarily halt a program's output to the
terminal screen, press Ctrl- s. To resume output, press Ctrl- q.
4.5 Manipulating Files
File manipulation (creating, displaying, combining, copying, moving,
naming, and deleting files), is one of the most important capabilities an
operating system provides. The XENIX commands that perform these
functions are described in the following sections.
4.5.1 Creating a File
To create a file and place text in it, use the editor vi, described in Chapter 2
of the XENIX User's Guide, "vi: A Text Editor." H for some reason you
wish to create an empty file, enter:

> filename
where filename is the name of the empty file. In general, new files are
created by commands as needed.
4.5.2 Displaying File Contents
The more command displays the contents of a file one screenful at a time.
It has the form:
more options filename
more is useful for looking at a file when you do not want to make changes to
it. For example, to display the contents of the file memos, enter:
more memos
more can be invoked with options that control where the display begins,
and how the file is displayed.
These options include:

+linenumber
Begins the display at the line in the file designated by
linenumber.

4-5

Introduction to XENIX

+Itext
Begins the display two lines before text, where text is a word or
number. If text is two or more words, they must be enclosed in
double quotation marks.
-c

Redraws the screen instead of scrolling.

-r

Displays control characters, which are normally ignored by
more.

To begin looking at the file memo at the first occurrence of the words "net
gain", for example, enter:
more +I"net gain" memo
If the file is more than one screenfullong, the percentage of the file that
remains is displayed on the bottom line of the screen. To look at more of
the file, use the following scrolling commands:
RETURN

Scrolls down one line.

Scrolls down one-half screen.

SPACE

Scrolls down a full screen.

nSPACE

Scrolls downn lines.
Repeats the previous command.

You cannot scroll backward, toward the beginning of the file.
You can search forward for patterns in more with the slash (I) command.
For example, to search for the pattern "net gain", enter:

Inet gain!
and press RETURN. more displays the message:
at the top of the screen, and scrolls to a location two lines above "het gain."
If you are looking at a file with more and decide you want to change the file,
you can invoke the vi editor by pressing:
v

See Chapter 2 of the XENIX User's Guide, "vi: A Text Editor," for information on using vi.

4-6

Tasks

more quits automatically when it reaches the end of a file. To exit more
before the end of a file, enter:
q

The head and tail commands display the first and last ten lines of a file,
respectively. They are useful for checking the contents of a particular file.
For example, to look at the first ten lines of the file memo, enter:
head memo
You can also specify how many lines the head and tail commands display.
For example:
tail -4 memo
displays the last four lines of memo.
The cat command also displays the contents of a file. cat scrolls the file
until you press CtrI- s to stop it. Pressing Ctrl- q will continue the scrolling.
cat stops automatically at the end of a file. If you wish to stop the display
before the end of the file, press INTERRUPT. To display the contents of
one file, enter:
cat filel
To display the contents of more than one file, enter:
cat filel file2 file3

4.5.3 Combining Files
The cat command is frequently used to combine files into some other new
file.
Thus, to combine the two files namedfilel andfile2, into a new file named
bigfile, enter:
cat filel file2 > bigfile
Note here that we are putting the contents of the two files into a new file
with the name bigfile. The greater than sign ( > ) is used to redirect output
of the cat command to the new file.

4-7

Introduction to XENIX

You can also use catto append one file to the end of another file. For exampIe, to append file 1 to file 2, enter:
cat file! > > file2
The contents offile 1 are added to fUe2. file 1 still exists as a separate entity.
4.5.4 Moving a File
The mv command moves a file into another file in the same directory, or
into another directory.
For instance, to move a file named text to a new file named book, enter:
mv text book
After this move is completed, no file named text will exist in the working
directory, because the file has been renamed book.
To move a file into another directory, give the name of the destination
directory as the final name in the mv command. For instance, to move file 1
andfile2into the directory named /tmp, enter:
mv file! file2 / tmp
The two files you have moved no longer exist in your working directory, but
now exist in the directory /tmp. The above command has exactly the same
effect as entering the following two commands:
mv file! Itmp/file!
mv file2 Itmp/file2
The mv command always checks to see if the last argument is the name of a
directory and, if so, all files designated by filename arguments are moved
into that directory.
4.5.5 Renaming a File
To rename a file, simply "move" it to a file with the new name: the old
name of the file is removed. Thus, to rename the file anon to johndoe,
enter:
mv anon johndoe
Note that moving and renaming a file are essentially identical operations.

4-8

Tasks

4.5.6 Copying a File

There are two forms of the cp command: one in which files are copied in to
a directory, and another in which a file is copied to another file. Thus, to
copy three files in to a directory named flier, enter:
cp file! file2 file3 filer
In the above command, three files are copied into the directory filer; the
original versions still reside in the working directory. Note that the
filenames are identical in the two directories. Like the mv command, cp
always checks to see if the last argument is the name of a directory, and, if
so, all files designated by filename arguments are copied into that directory.

To create two copies of a file in your own working directory, you must
rename the copy. To do this, the copy command can be invoked as follows:
cp file filecopy
After the above command has executed, two files with identical contents
reside in the working directory. To learn how to copy directories, see section 4.6.7, "Copying a Directory", later in this chapter.
4.5.7 Deleting a File

To delete or remove files, enter:
rm file! file2
In the above command, the files file1 and file2 are removed from your
working directory.

The command:
rm -i file! file2
allows you to interactively remove files by asking you if you really want to
delete each of the files file1 and file2. If you press y followed by a RETURN,
the given file is removed; if you press n the file is left untouched. This command is useful when cleaning up a directory that contains many files.

4-9

Introduction to XENIX

4.5.8 Finding Files
The find command searches for files that have a specified name. find is useful for locating files that have the same name, or just for finding a file if you
have forgotten which directory it is in.
The command has the form:
find pathname -name filename -print
The pathname is the pathname of the directory you want to search. find
searches recursively, that is, it starts at the named directory and searches
downward through all files and subdirectories under the directory specified
in pathname.
The -name option indicates that you are searching for files that have a
specific filename. (There are other search conditions you can use with find;
see find ( C) in the XENIX Reference Manual.)

filename is the name of the file you are searching for.
The -print option indicates you want to print the pathnames of all the files
that match filename on your terminal screen. You may direct this output to
a file instead of your screen with the output redirection symbol, >. (There
are other actions that can be performed with find, such as removing and
moving files; see find(C) in the XENIX Reference Manual.) For example,
the following command finds every file named memo in the directory
/usr/joe and all its subdirectories:
find /usrljoe -name memo -print
The output might look like this:

lusrljoe/memo
lusrl joel accounts/memo
lusr/joe/meetings/memo
lusr/joe/maiUmemo

4.5.9 Linking a File to Another File
The In command joins two files in different directories so that when the file
is changed in one directory, it is also changed in the other directory. This
can be useful if several users need to share information, or if you want a file
to appear in more than one directory. This command has the form:

In file newfile

4-10

Tasks

where file is the original file, and newfile is the new, linked file. For example, the following command links memos in /usr/joe to joememos in
/usr/mary:
In lusr/joe/memos lusr/mary/joememos

Whenever /usr/joe/memos is updated, the file /usr/mary/joememos is also
changed.
When you link files a name is associated with an inode. An inode specifies
a unique set of data on the disk. One or more names can be associated with
this data. Thus, the above command assures that the files dir lIfile1 and
dir2/file2 have identical contents.
There are three things that are not immediately obvious about linking files:
1. Linking large sets of files to other parallel files can save a considerable amount of disk space.
2.

Linking files used by more than one person is risky, because any
party can alter the file and thus affect the contents of all files linked
to it.

Removing a file from a directory does not remove other links to the
file. Thus the file is not truly deleted from the system. For example,
if you delete a file that has 4 links, 3 links remain.

For more information about linking see In(C) in the XENIX Reference
Manual.
4.6 Manipulating Directories
Because of the hierarchical organization of the file system, there are many
directories and subdirectories in the XENIX system. Within the file system
are directories for each user of the system. Within your user directory you
can create, delete, and copy directories. Commands that let you manipulate directories are described in the following sections.
4.6.1 Printing the Name of Your Working Directory
All commands are executed relative to a "working" directory. The name
of this directory is given by the pwd command, which stands for "print
working directory." For instance, if your current working directory is
lusT/joe, when you enter:
pwd

4-11

Introduction to XENIX

you will get the output:
/usr/joe
You should always think of yourself as residing "in" your working directory.
4.6.2 Listing Directory Contents

You can list the contents of a directory with the Ie command. This command sorts the names of files and directories in a given directory, and lists
them in columns. If no directory name is given, Ie lists the contents of the
curren t directory. The Ie command has the form:
Ie options name
For example, to list the contents of the directory work, enter:
Ie work
Your output might look like this:
accounts
mail

meetings
memos

notes
todo

If no name is specified, Ie lists the contents of the current directory. If
accounts is the current directory, for example, the command:

Ie
lists the names of the files and subdirectories in that directory.
The following options control the sort order and the information displayed
by the Ic command:
-a

Lists all files in the directory, including the "hidden" files
(filenames that begin with adot, such as .profile and .mailrc).

-r

Lists names in reverse alphabetical order.

-t

Lists names in order of last modification, the latest (most recently
modified) first. When used with the -r option, lists the oldest
first.

4-12

Tasks

-R

Lists all files and directories in the current directory, plus each file
and directory below the current one. The "R" stands for "recursive."

-F

Marks directories with a backslash(\) and executable files with an
asterisk (*).

The Is command works much like the Ie command except that it lists files in
vertical, rather than collumnar, form. The Is -I command gives a "long"
listing of a directory, producing an output that might look something like
this:
total 501
drwxr-x--drwxr-x--drwxr-x---rw-r-----rw-r-----rw-r-----

2
2
2
1
1
1

boris
enid
iris
olaf
olaf
olaf

grpl
grpl
grpl
grp2
grp2
grp2

272
272
592
282
72
1403

Apr
Apr
Apr
Apr
Apr
Apr

5
5
6
7
7
1

14:33
14:33
11:12
15:11
13 :50
13 :22

dirl
dir2
dir3
filel
file2
file3

Reading from left to right, the information given for each file or directory
includes:
-

Permissions

Numberoflinks

Owner

Group

Size in bytes

Time of last modification

Filename

The information in this listing and how to change permissions are discussed below in Section 4.8, "Using File and Directory Permissions."
For more information about listing the contents of a directory, see Is(C) in
the XENIXReference Manual.

4-13

Introduction to XENIX

4.6.3 Creating a Directory

To create a subdirectory in your working directory, use the mkdir command. For instance, to create a new directory named phonenumbers, simply enter:
mkdir phonenumbers
After this command has been executed, a new empty directory will exist in
your working directory.
4.6.4 Removing a Directory

To remove a directory located in your working directory, use the rmdir
command. For instance, to remove the directory named phonenumbers
from the current directory, simply enter:
rmdir phonenumbers
Note that the directory phonenumbers must be empty before it can be
removed; this prevents catastrophic deletions of files and directories. H
you want to live dangerously, it is possible to recursively remove the contents of a directory using the rm command, but that will not be explained
here. See rm (C) in the XENIX Reference Manual for more information.
4.6.5 Renaming a Directory

To rename a directory, use the mv command. For instance, to rename the
directory little. dir to big. dir, enter:
mv little.dir big.dir
This is a simple renaming operation; no files are moved.
4.6.6 Moving a Directory

The mv command also moves directories. This command has the form:
mv oldirectory newdirectory
where newdirectory is a directory that already exists.

4-14

Tasks

For example, to move
/usr/joe/overdue enter:

the

directory

/usr/joe/accounts

into

mv /usr/joe/accounts /usr/joe/overdue
The newpathname of /usr/joe/accounts is /usr/joe/overdue/accounts.
4.6.7 Copying a Directory
The copy command copies directories. This command has the form:
copy options olddir newdir
To copy all the files in the directory /usr/joe/memos into /usr/joe/notes
enter:
copy /usr/joe/memos /usr/joe/notes
The files in /usr/joe/memos are copied into /usr/joe/notes. The copy command has the following options:
-1

Links the copied files to the original.

-m

Gives the copied files the same modification dates as the original
files.

-r

Copies the directory recursively, i.e., copies all the directories
under the named directory.

4.7 Moving in the File System
When using the XENIX system, it helps to imagine a large tree structure of
files and directories. Each directory should be thought of as a place that
you can move into or out of. At all times you are "someplace" in the tree
structure. This place is called either your working directory or current
directory. The commands used to find out where you are and to move
around in the tree structure are discussed below.

4-15

Introduction to XENIX

4.7.1 Finding Out Where You Are

Your current location in the file system is the name of the working directory. You can find out this name by using the pwd command, which stands
for "print working directory." For example, if you are in the directory lusr
then entering the command:
pwd
prints out the name:

lusr

4.7.2 Changing Your Working Directory

Your working directory represents your location in the file system: it is
"where you are" inXENIX. To alter this location in theXENIXfile system,
use the change directory (cd) command:
cd
This changes your working directory to your home directory. To move to
any other directory, specify that directory as an argument to cd.
For instance, the following command:
cd lusr
moves you to the lusr directory. Because you are always "in" your working
directory, changing working directories is much like "traveling" from
directory to directory.
To move up one directory from your current directory, enter:
cd ..
For example, the above command would move you from the directory

lusrljoelworkto lusrljoe. Similarly, the command:
cd . .1 ..
would move you from the directory lusrljoelwork to lusr, moving you up
two directories.

4-16

Tasks

4.8 Using File and Directory Pennissions
The XENIX system allows the file owner to restrict access to files and directories, limiting who can read, write and execute files owned by him. To
determine the permissions associated with a given file or directory, use the
Is -I command. The output from the Is -I command should look something like this:
total 501
drwxr-x--drwxr-x--drwxr-x---rw-r-----rw-r-----rw-r-----

2
2
2
1
1
1

boris
enid
iris
olaf
olaf
olaf

grpl
grpl
grpl
grp2
grp2
grp2

272
272
592
282
72
1403

Apr
Apr
Apr
Apr
Apr
Apr

5
5
6
7
7
1

14:33
14:33
11:12
15:11
13:50
13 :22

dirl
dir2
dir3
filel
file2
file3

Permissions are indicated by the first ten characters of the output. The permissions for dirl, the first file in the above list, are:
drwxr-x--The first character indicates the type of file and must be one of the following:
Indicates an ordinary file.
d

Indicates a directory.

Indicates a character special device such as a lineprinter or
terminal.

Indicates a block special device such as a hard or floppy disk.

Indicates a name special file (i.e., a semaphore used for controlling access to some resource).

Indicates a shared data file.

Indicates a named pipe.

From left to right, the next nine characters are interpreted as three sets of
three permissions each. Each respective set of three indicates the followingpermissions:
-

Owner permissions

Group permissions

All other user permissions

4-17

Introduction to XENIX

Within each set, the three characters indicate permission to read, to write,
and to execute the file as a command, respectively. For a directory, "execute" permission means permission to search the directory for any
included files or directories.
Ordinary file permissions have the following meanings:
r

The file is readable.

The file is writeable.

The file is executable.
The indicated permission is not granted.

For directories, permissions have the following meanings:
r

Files can be listed in the directory; the directory must also
have "x" permission.

Files can be created or deleted in the directory; as with "r",
the directory itself must also have "x" permission.

The directory can be searched. A directory must have "x"
permission before you can move to it with the cd command
(i.e., cd to it), access a file within it, or list the files in it.
Remember that a user must have "x" permission to do anything useful to the directory.

The following are some typical directory permission combinations:

d--------

No access at all. This is the mode that denies access to
the directory to a class of users.

drwx------

Allows access by only the owner to use lc, create files,
delete files, access files (subject to file permissions),
and cd to the directory. This is the typical permission
for the owner of a directory.

drwxr-x---

Allows access by members of the group to use Ie, and
access files subject to file permissions. Group
members can cd to this directory, but cannot create or
delete files in it. This is the typical permission an
owner gives to others who need access to files in his
directory.

drwx--x--x

With these permission settings users other than the
owner cannot use Ic but can cd to the directory. Other

4-18

Tasks

users can only access a file within this directory by its
exact name; they cannot use special characters. Files
cannot be created or deleted in the directory by anyone except the owner. This mode is rarely used, but
can be useful if you want to give someone access to a
specific file in a directory without permitting access to
other files in the same directory.
This chapter discusses ordinary files, executable files, and directories only.
For information about other types of files, see Is (C) in the XENIX Reference Manual.

4.8.1 Changing Permissions
The chmod command changes the read, write, execute, and search permissions of a file or directory. This command is useful if you have created a
file in one mode, but want to give others permission to read, write or execute it.
The chmod command has the form:
chmod instruction filename
The instruction segment of the command indicates which permissions you
want to change for which class of users. There are three classes of users,
and they are are indicated as follows:
u

User, the owner of the file or directory

Group, the group the owner of the file belongs to

Other, all users of the system

All classes of users

There are three types of permissions, as follows:
r

Read, which allows permitted users to look at but not change or
delete the file.

w Write, which allows permitted users to change or even delete the

file.
x

Execute, which allows permitted users to execute the file as a command.

4-19

Introduction to XENIX

For example, assume filel exists with the following permissions:
-rw-r- - --In the above example, the owner of the file has read and write permission,

group members have read permission, and others have no access at all.
To g).vefilel read permission for all classes of users, enter:
chmod a+r filel
In the instruction segment of the command (a+r) the "a" stands for "all."

The resulting permissions are:
-rw-r--r-For filel with the attributes:
-rw------The following command g).ves write and execute permissions to members
of a group only:
chmod g+wx filel
This command would alter the permission attributes so they look like this:
-rw--wx--To remove write and execute permission by the user (owner) and group
associated withfilel, enter:
chmod ug-wx filel

4-20

Tasks

4.8.2 Changing Directory Search Pennissions

Directories also have an execute permission. This attribute signifies search
permission, rather than execute permission, since directories cannot be
executed. If this permission is denied to a particular user, then that user
cannot even list the names of the files in the directory.
For example, assume that the directory dir1 has the following attributes:
drwxr-xr-x
To remove search permission for other users to examine dir 1, enter:
chmod o-xr dir1
The new attributes for dir1 are:
drwxr-x---

4.9 Processing Infonnation
In many cases, files will contain information that you may want to process.
Various utility programs exist on XENIX to process information. A set of
these programs and their uses are described in the following sections.

4-21

Introduction to XENIX

4.9.1 Comparing Files

To compare two text files use the dUf command to print out those lines that
differ b etween the files that you specify.
For example, suppose that a file named men has the contents:
Now is the time for all good men to
Come to the aid of their party.
and that a file named women has the following con ten ts:
Now is the time for all good women to
Come to the aid of their party.
If this is the case, then the command:

diff men women
produces the following results:
lcl

< Now is the time for all good men to
> N ow is the time for all good women to
A three-way difference listing can be created with the diJf3 command. For
information about difO see diJf3( C) in the XENIX Reference Manual.
4.9.2 Echoing Arguments

The echo command echos arguments to the standard output. For example,
entering:
echo hello
outputs:
hello
on the terminal screen. To output several lines of text, surround the
echoed argument in double quotation marks and press RETURN between

4-22

Tasks

lines. A secondary prompt will appear until you enter the final double quotationmark. For example, enter:
echo ''Now is the time
For all good men
To come to the
Aid of their party."
This will output:
Now is the time
For all good men
To come to the
Aid of their party.
echo is particularly useful if you should ever program in the shell command
language. For more information about the shell, see Chapter 4, "The
Shell", XENIX User's Guide.
4.9.3 Sorting a File
One of the most useful file processing commands is sort. By default, sort
sorts the lines of a file according to the ASCII collating sequence (Le., it
alphabetizes them).
For example, to sort a file named phonelist, enter:
sort phonelist
In the above case, the sorted contents of the file are displayed on the
screen. To create a sorted version of phonelist named phonesort, enter:

sort phonelist > phonesort
Note that sort is useful for sorting the output from other commands. For
example, to sort the output from execution of a who command, enter:
who

I sort

>whosort

This command takes the output from who, sorts it, and then sends the
sorted output to the file whosort.
A wide variety of options are available for sort. For more information, see
sort(C) in the XENIX Reference Manual.

4-23

Introduction to XENIX

4.9.4 Searching fora Pattern in a File
The grep command selects and extracts lines from a file, printing only
those lines that match a given pattern. For example, to print out all lines in
a file containing the word "tty38", enter:
grep 'tty38' file
In general, you should always enclose the pattern you are searching for in

single quotation marks C), so that special metacharacters are not
expanded unexpectedly by the shell.
As another example, assume that you have a file named phonelist that contains a name followed by a phone number on each line. Assume also that
there are several thousand lines in this list. You can use grep to find the
phone number of someone named Joe, whose phone number prefix is 822,
as follows:
grep 'joe' phonelist

I grep

'822-' >joes.number

grep finds all occurrences of lines containing the word "joe" in the file
phonelist. The output from this command is then filtered through another
grep command, which searches for an "822-" prefix, thus removing any
unwanted joes. Finally, assuming that a unique phone number for joe
exists with the "822-" prefix, that name and number are placed in the file
joes. number.
For more information about grep, its relatives fgrep and egrep, and the
types of patterns it can be used to search for (called regular expressions)
see grep (C) in the XENIX Reference Manual.
4.9.5 Counting Words, Lines, and Characters
wc is a utility for counting words in a file. The letters "wc" stand for word
count. Words are presumed to be separated by punctuation, spaces, tabs,
or newlines. wc also counts characters and lines; all three counts are
reported by default.
For example, to count the number of lines, words, and characters in the
file textfile, enter:
wc text file
Typical output describing lines, words and characters might be:
4432

18188

97808 textfile

To specify a count of characters, words, or lines only, you must use an
appropriate mnemonic switch.

4-24

Tasks

To illustrate, examine the following three commands and the output produced byeach:
wc -c textfile
97808 textfile
wc -w textfile
18188 textfile
wc -1 textfile
4432 textfile
The first example prints out the number of characters in textfile, the second
prints out the number of words, and the third prints out the number of
lines.
4.9.6 Delaying a Process

The at program allows you to set up commands to be executed at a
specified time. It is useful if you want to execute a command when you are
not planning to be at your terminal, or even logged in.
The at command accepts standard input and has the form:
cat file

I at

time day

file is the name of the file that contains the command or commands to be
executed. time is the time of day, in digits, followed by "am" or "pm."
One- and two-digit numbers are interpreted as hours, three- and fourdigit numbers as hours and minutes. More than four digits is not permitted.
day is optional. It is either a month name followed by a day number, or a
day of the week. H no day is specified, the command will be executed
today.

For example, if you want to find out what processes are running at 10 pm on
Tuesday, place the following line in a file named use:
ps -a > lusrlmyname/use
(See Chapter 2, "vi: A Text Editor," of the XENIX User's Guide for information on creating and inserting text into files.)

4-25

Introduction to XENIX

After you have written out the file and returned to command level, enter:
cat use

I at

10pm tues

Press RETURN. The XENIX prompt reappears and you may continue
working. At 10 pm on Tuesday, XENIX will execute ps -a and place the
output in the file use. at is unaffected by logging out.
To check what files you have waiting to be processed, use the at -I command. at -I lists the files the user owns to be processed, along with the following information:
-

Thefile'sIDnumber

The command invoking the file (atorbatch).

The date and time the file will be processed

To cancel an at command, first check the list of files you have to be processed and note the file ID number. Then use the at -r command to
remove the file or files from the list.
The at -rcommand has the form:
at -r number
For example:
at -r 504510300.a
removes file number 504510300.a, canceling whatever commands were
included in that file. A user can only remove his own files.
4.10 Controlling Processes
In XENIX, several processes can run at the same time. For example, you
may run the sort program on a file in the "background", and edit another
file in the "foreground" while the sort program is running. Things that you
directly control at your keyboard are called foreground processes. Other
processes, which you can initiate but that you otherwise have little control
over, are called background processes. At anyone time you can have only
one foreground process executing, but multiple background processes
may execute simultaneously. Controlling foreground and background
processes is the sub ject of this section.

4-26

Tasks

4.10.1 Placing a Process in the Background
Normally, commands sent from the keyboard are executed in strict
sequence; one command must finish executing before the next can begin.
Executing commands of this type are called foreground processes. A
background process, in contrast, need not finish executing before you give
your next command. Background commands are especially useful for
commands that may take a long time to complete.
To place a process in the background, enter an ampersand (&) at the end
of the command. For example, to count the number of words in several
large files while simultaneously continuing with whatever else you have to
do, enter:
wc file! file2 file3 > count&
Output is collected in the file count. If output were not put in count, it
would appear on the screen at unpredictable times as you continue with
your work.
When processes are placed in the background, you lose control of them as
they execute. For instance, entering INTERRUPT does not abort a background process. You must use the kill command, described in the following section, instead.
4.10.2 Killing a Process
To stop execution of a foreground process, press your terminal's INTERRUPT key. This kills whatever foreground command is currently running.
To kill all your processes executing in the background, enter:
kill 0
To kill only a specified process executing in the background, first enter:
ps
ps displays the Process Identification Numbers (PIDs) of your existing
processes, for example:
PID TTY TIME CMD
3459 03 0: 15 -sh
4831 03 1:52 cc program.s
5185 03 0:00 ps

4-27

Introduction to XENIX

In the above example, you might enter:

kill 4831
where 4831 is the PID of the process that you want killed.

Note
Killing a process associated with the vi editor may leave the terminal
in a strange mode. Also, temporary files that are normally created
when a command starts, and then deleted when the command
finishes, may b e left behind after a kill command. Temporary files are
normally kept in the directory /tmp. This directory should be
checked periodically and old files deleted.

4.11 Getting Status Infonnation

Because XENIX is a large, self-contained computing environment, there
are many things that you may want to find out about the system itself, such
as who is logged in, how much disk space there is, what processes are
currently running. This section explains the types of information available
from the system and how to get it.
4.11.1 FindingOutWho is on the System

The who command lists the names, terminal line numbers, and login times
of all users currently logged on to the system. For example, enter:
who
This command produces something like the following output on your terminal screen:
arnold
daphne
elliot
ellen
gus
adrian

4-28

tty02
tty21
tty23
tty25
tty26
tty28

Apr
Apr
Apr
Apr
Apr
Apr

7
7
7
7
7
7

10:02
07:47
14:21
08:36
09:55
14:21

Tasks

The finger command provides more detailed information, such as office
numbers and phone extensions. For more information, about using finger
see finger(C) in the XENIXReference Manual.
4.11.2 Finding Out What Processes Are Running
Because commands can be placed in the background for processing, it is
not always obvious which processes you are responsible for. The ps command stands for "process status" and displays information about currently
running processes associated with your terminal. For instance, the output
from a ps command might look like this:
PID TTY TIME CMD
10308 38 1:36 ed chap02.man
49 38 0:29 -sh
11267 38 0:00 ps
The PID column gives a unique process identification number that can be
used to kill a particular process. The TTY column shows the terminal that
the process is associated with. The TIME column shows the cumulative
execution time for the process. Processes can be killed using the kill command. See section 4.10.2, "Killing a Process," for information on how to
use the kill command.
To find out all the processes running on the system, use the a option:
ps -a
To find out about the processes running on a terminal other than the terminal you are using, use the· t option and specify the terminal number. For
example, to find out what processes are associated with terminal 13, enter:
ps -t13
For more information about ps and its options, see ps(C) in the XENIX
Reference Manual.
4.11.3 Finding Out Lineprinter Infonnation
You can find out the status of files you requested printed with the lpstat
command. lpstat displays information on an individual file or on all your
files waiting to be printed.

4-29

Introduction to XENIX

To find out the status of one file, you need to know the "request ID." When
you make print requests using the Jp command, you find a request ID
displayed on your terminal screen. The request ID has the form:

printer- idnumber
printer is the name of the printer your file will be printed on (check with
your system manager for the names of printers available to you) and
idnumber is a unique numberidentifyingyour file.
To find out the status of a particular file, enter:
lpstat request ID
Jpstat responds by displaying the date and time you made your print
request and the number of characters remaining to be printed.
To find out the status of all your files waiting to be printed on the lineprinters, enter:
lpstat
Ips tat responds by displaying the request IDs and status information for all
your files.
You can find out what files are waiting to be printed on a particular printer
by using Jpstatwith the -p option. This command has the form:
Jpstat -p printer
Jpstat responds by printing the request IDs and status information for all
the files waiting to be printed on the named printer.
For more information on Jpstat and its options, see Jpstat(C) in the XENIX
Reference Manual.
4.12 Using the Lineprinter
The XENIX lineprinter commands are easy to use and give you great flexibility when you want to print a file. With a few simple commands, you can
print multiple copies of a file, cancel a print request, or ask for a special
option on a particular printer. Since the XENIX lineprinter system is
designed to be easily adapted to many different environments, check with
your system manager to find out what lineprinters and printer options are
available to you.

4-30

Tasks

4.12.1 Printing Files: Ip

To print copies of your files, you can use either the Ip command or Ipr.
These commands are equivalent. The examples in this section use Ip.
For example, to print one copy of a file named memo, enter:
lp memo
You can request that several files be printed. For example, to print three
files named memo ,report, and letter, enter:
lp memo report letter
When you make print requests, Ip responds by displaying your "request
ID" on your terminal screen. Your request ID might look like this:
pr4-532
The first part (pr4) is the name of the printer your file will be printed on.
The second part (532) identifies your file. Should you later wish to cancel
your print request or check its status, you will find it useful to remember
your request ID. For more information on these tasks, see sections 4.12.3,
"Canceling a Print Request," and 4.12.4, "Finding Out the Status of A
Print Request: lpstat."
One copy of each file you named will be printed on the default destination
printer on your system.
You can use Ip with pipes and other commands. The command to paginate
a file is pro To paginate and print a file named text/tie, enter:
pr textfile

I lp

To sort, paginate, and print a file named datafile, enter:
sort datafile

I pr I lp

4.12.2 Usinglp Options

The Ip command has several options to help you control the output from
your printer.

4-31

Introduction to XENIX

You can specify the number of copies you want printed by using the
number option, -no For example, to print two copies of a file named
report, enter:
lp report - n2
Another option, - d, specifies your file's destination, that is, which printer
your file will be printed on. Check with your system manager for the names
of the printers available to you. To have two copies of a file named report
printed on a printer named quick, enter:
lp report -n2 -dquick
Other useful options include:
-c

Makes a copy of the files you are printing. This prevents you from
inadvertently removing or changing the file before it is printed.

-m

Sends you mail telling you your file has been printed.

-0

Specifies printer options. For example, you may be able to
request that your document be printed using 12 pitch type. Check
with your system manager to see what options are available for
each printer or groups of printers on your system.

-r

Removes your files after printing.

For more information on options available for the lp command, see Ip(C)
in the XENIXReference Manual.

4.12.3 Cancelling a Print Request: cancel
You can cancel a print request. For example, to stop printing a file with a
request ID of laser- 245, enter:
cancel laser-245
The cancel command immediately stops the file from being printed, even if
the printer has already begun the print request.
'
You can also use the cancel command to stop whatever is currently printing on a particular printer. With cancel, you can easily free up a printer to
print the next file, or stop it from printing strange output without contactingyour system manager.

4-32

Tasks

For example, to cancel whatever file is currently printing on· a printer
named slow, enter:
cancel slow
If the file did not belong to you, mail will automatically be sent to the file's

owner reporting that the print request was canceled.
4.12.4 Finding Out the Status of A Print Request: Ipstat
To find outthe status of your files waiting to be printed, enter:
Ipstat
Ipstat gives output similar to:

prtl-121
laser-450

chrisw
chrisw

450
4968

Dec 1509:30
Dec 1509:46

The first column shows the request ID for each of your files being printed;
the second column is your login name. In the third column, the number of
characters to be printed is shown, and the fourth column lists the dates and
times you made your print requests.
To learn the status of a particular file, use the Ipstat command with your
request ID. For example, to find out the status of a file with the request ID
of daisy- 256, enter:
Ipstat daisy-256
Ips tat displays the status of that file only.
You can also request the status of various printers on your system by using
the - p option or by giving the name of the particular printer you are
interested in.

4-33

Introduction to XENIX

To find out the status of all the printers on your system, enter:
lpstat -p
To find out the status of a printer named quick, enter:
lpstat -pquick
Ipstat displays the request ID and status information for each file currently
waiting to be printed on the printer named quick.
For more information on Ipstat and its options, see Ipstat(C) in theXENIX
Reference Manual.
4.13 CommunicatingwithOtherUsers
Because the XENIX system supports mUltiple users, it is very convenient to
communicate with other users of the system. The various methods of communication are described below.
4.13.1 Sending Mail
mail is a system-wide facility that permits you and other system users to
send and receive mail. To send mail to another user on the system, enter:
mail joe
where joe is the name of any user of the system. Following entry of the
command, you enter the actual text of the message you want to send. Entry
of text is terminated by pressing Ctrl- d.
A complete session at the terminal might look like this on your screen:
mail -s "Meeting today" joe
There will be a meeting at 2:00 today
to review recent problems with the
new system.
Ctrl-d
Note the use of the -s switch to specify the subject ofthe message.
Forpractice, send mail toY-ourself. (This is not as strange as it might sound
- mail to yourself is a handy reminder mechanism. ) You can also send a
previously prepared letter, and you can send mail to an umb er of people all
at once. For more details, see Chapter 3, "MaiF;, of the XENIX User's
Guide, and mail (C) in the XENIXReference Manual.

4-34

Tasks

4.13.2 Receiving Mail
When you log in, you may sometimes get the message:
you have mail
To read your mail, enter:
mail
A heading for each message is then displayed on your terminal screen.
When you press RETURN, the contents of the first message are displayed.
Subsequent messages are displayed, one message at a time, most recent
message first, each time you press RETURN.
After each message is displayed, mail waits for you to tell it what to do with
the message. The two basic responses are d, which deletes the message,
and RETURN, which does not delete the message (so it will still be there the
next time you read your mailbox). To exit mail, enter: q, for "quit." Other
responses are described in the XENIXReference Manual undermail(C).

4.13.3 Writing to a Terminal
To write directly to another user's terminal, use the write command. For
example, to write to joe's terminal, enter:
write joe
After you have executed the command by pressing RETURN, each subsequent line that you enter is displayed both on your own terminal screen and
on joe's. To terminate the writing of text to joe, enter a CtrI- d alone on a
line.
The procedure for a two-way write is for each party to end each message
with a distinctive signal, normally (0) for "over"; when a conversation is
about to be terminated use the signal (00) for "over and out."

4.14 Using the Sys tern Clock and Calendar
There are several XENIX commands that will tell you the date and time, or
display a calendar for any month or year you choose. The following sections explain these commands.

4-35

Introduction to XENIX

4.14.1 Finding Out the Date and Time
The date command displays the time and date. Enter:
date
The date and time are displayed.
4.14.2 Displaying a Calendar
The cal command displays the calendar of any month or year you specify.
This command has the form:
cal month year
For example, to display the calendar for March, 1952 enter:
cal 3 1952
The result is:
March 1952
SMTuWThFS
1

2
9
16
23
30

3 4 5 678
10 11 12 13 14 15
17 18 19 20 21 22
24 25 26 27 28 29
31

The month must always be expressed as a digit. To display the calendar for
an entire year, leave out the month. The year must always be expressed in
full; the command "cal 85" displays the calendar for the year 85, not 1985.

4-36

Tasks

4.15 Using the Automatic Reminder Service
An automatic reminder service is normally available for all XENIX users.
Once each day, XENIX uses the calendar command to examine each user's
home directory for a file named calendar, the conten ts of which might look
something like this:
1/23
2/9
3/30
4/27
9/1
10/3

David's wedding
Mira's birthday
Paul's birthday
Meeting at 2:00
Karen's birthday
License renewal

calendar examines each line of the calendar file, extracting from the file
those lines containing today's and tomorrow's dates. These lines are then
mailed to you to remind you of the specified events.
4.16 Using AnotherUser's Account
You can easily access another user's files, regardless of the permission settings, with the su command. The su procedure resembles logging in, and
you must know the other user's password.
For example, to become user Joe, enter:
su joe
and press RETURN. When the password prompt appears, enter Joe's password. To cancel the effect of the su command and return to your own
account, press Ctrl- d.

4.17 Calculating
The bc command invokes an interactive desk calculator that can be used as
if it were a hand-held calculator. A typical session with bc is shown below.
Commen ts explain what action is performed after each input line.

4-37

Introduction to XENIX

1* This is a comment *1
123.456789 + 987.654321
1* Add and output
1111.111110
9.0000000 - 9.0000001 1* Subtract and output *1
-.0000001
64/8
1* Divide and output
*I
8
1.12345678934 * 2.3
1* Note precision *1
2.58395061548
19%4
1* Find remainder *1
3
3"4 1* Exponentiation

81
2/1 *2
4
2/(1 *2)
1

1* Note precedence

1* Note precedence again */

x = 46.5 1* Assign value to x
*1
y = 52.5 1* Assign value to y
*1
x + y + 1.0000 1* Add and output
100.0000
obase=16 1* Set hex output base *1
15 1* Convert to hex
*1

16 1* Convert to hex
10
64 1* Convert to hex
40
255 1* Convert to hex

*1
*1
*1

256 /* Convert to hex
*/
100
512 /* Convert to hex
*/
200
quit!* Must type whole word *1
Also available are scaling, function definition, and programming statements much like those in the C programming language. Other features
include assignment to named registers and subroutine calling. For more
information, see Chapter 5, "bc: A Calculator", XENIX User's Guide.

4-38

Index
at command 4-25

Characters
(0), write command message end 4-35
(00), write command message end 4-35
* See Asterisk (*)
- See Dash (-)
-a option
function 3-10
-I option
function 3-10
-r option 3-10
-R option, recursive listing 4-13
-s option
mail, subject specification 4-34
-v option
function 3-10
. See Period (.)
I See Slash (I)
Ibin directory
contents 3-5
Idev directory
contents 3-5
Idev/console directory
contents 3-5
Idev/tty directory
contents 3-5
llib directory
contents 3-5
Itmp directory 4-28
contents 3-6
lusr directory
contents 3-5
lusr/bin directory
contents 3-5
? See Question mark (?)

A
a character, permission change 4-20
Absolute pathname, See Pathname
Account, new user 2-1
Addition, See Calculation
Alphabetizing, See sort command
Ampersand (&)
background command 3-9
background process 4-27
Appending files 4-8
Appending, See Output
Argument
switch, See Switch
Asterisk (*)
filename wildcard 3-8
filename, use avoidance 3-5
pattern matching functions 3-7
at -r command 4-26

B
Background process 4-27,4-27
ampersand (&) operator 4-27
Backslash (\)
erasing 2-4
escape character 2-4
BACKSPACE key
erasure function 2-4
literal 2-4
Batch processing, See Command
bc command
calculation 4-37
Binary file, See File
BKSP key
command-line buffer editing 3-9
Block special device 4-17
Brackets ([])
filename, use avoidance 3-5
pattern-matching functions 3-8
BREAK key
program stopping 2-5
terminal nonsense character removal 2-]

c
cal command 4-36
Calculation
example 4-37
calendar command 4-37
cancel
Case significance 2-2
cat command
file
combining 4-7
contents display 2-3
command 4-7
cd command 4-16
directory change 3-5
Changing password 4-2
Changing terminal types 4-3
Character counting 4-24
Character special device 4-17
chmod command 4-19,4-21
directory permission change 3-2
file permission change 3-1
Command line
ampersand (&) effect 3-9
buffer defined 3-9
defined 3-9
entry 4-4
erasure 4-4
interpretation 3-9

1-1

Index
Command line (continued)
multiple commands entry 3-9
RETURN key effect 4-4
See also Specific Command
background submittal 3-9
batch processing, See background submittal
dash (-) use 3-5
directory, See Ibin directory
directory, See Directory
entering error correction 2-4
execution 3-9
RETURN key required 2-2
sequence 4-27
lowercase letters 3-10
multiple commands entry 3-9
name error 2-2
program invocation 3-9
RETURN key required 2-2
syntax 3-10
typing error correction 2-4
Commands
at 4-25
at -r 4-26
cal 4-36
cat 4-7,4-8
cd 4-16
copy 4-15
cp 4-9
date 4-36
diff 4-22
diff34-22
echo 4-22
find 4-10
head 4-7
kill 4-29
lc 4-12
In 4-10
mkdir 4-14
more 4-5
mv 4-8
passwd 4-2
ps 4-27
pwd 4-16
rm 4-9
rmdir 4-14
sort 4-23
stty 4-4
tail 4-7
wc 4-24
Comparing files 4-22
Concatenate, See cat command
Control characters
filename use restrictions 3-4
Copy command 4-15
Copying a directory 4-15
Copying flies 4-9
Copying, See cp command
Counting, wc command 4-24

1-2

Introduction to XENIX
cp command 4-9
Creating a directory 4-14
Creating a file 4-5
Ctrl-c, program stopping 2-5
Ctrl-d
end-of-file 4-2
logging out 2-5
mail 4-34
Ctrl-q, output resumption 4-5
Ctrl-s, output stopping 4-5
Ctrl-u
command-line buffer editing 3-9
kill character 2-4
line kill 4-4
literal 2-4
Current directory
change 3-5
procedure 4-16
description 4-16
printing 4-11
shorthand name 3-6
user residence 3-6

D
d command
mail, message deletion, See Mail
Dash (-), permission
denial notation 4-18
ordinary file notation 4-17
command option use 3-5
filename, use avoidance 3-5
switch use 3-10
date command 2-2
Date command 4-36
DELETE key
program stopping 2-5
Deleting a file 4-9
Deletion, See d command
Demonstration 2-1
Device special file, See Special file
filename 3-4
filenamerequired 3-4
pathname 3-4
Diff command 4-22
diff3 4-22
Directory
Ibin, See Ibin directory
Idev, See Idev directory
llib, See llib directory
Itmp directory 4-28
Itmp, See Itmp directory
Itty, See Itty directory
lusr, See lusr directory
access permission, See Permission
changing 4-16
command, See cd command

Introduction to XENIX
Directory (continued)
composition 3-2
copying 4-15
creating 4-14
current directory, See Current directory
description 3-2
diagram 3-3
file, See File
filename
required 3-4, 3-4
unique to directory 3-4, 3-4
listing 4-13
columns 4-12
logging in result 3-3
long listing 4-13
nesting 3-2
parent directory, See Parent directory
pathname required 3-4
permission notation 4-17
permission, See Permission
protection 3-2
recursive listing 4-13
removing 4-14
renaming 4-14
search permission, See Permission
user control 3-2
working directory, See Current directory
Displaying a file 4-5
Division, See Calculation
Double quotation marks, See Quotation
marks, double

E
echo command 4-22
description, use 2-3
egrep, See grep command
Entering error correction 2-4
Exponentiation, See bc
Exponentiation, See Calculation

F
fgrep, See grep command
File permission
changing 4-19
File permissions, listing 4-13
File system
defined 3-3
diagram 3-4
organization 3-3
access

Index
File system (continued)
access (continued)
control 3-1
last access time 3-1
permission, See Permission
addition, See creation
alphabetizing, See sort
appending 4-8
attributes 3-1
binary file 3-1
combining 4-7
composition 3-1
copying 4-9
creating 4-5
creation
permission, See Permission
time 3-1
write permission control 3-2
defined 3-1
deleting 4-9
deletion
write permission control 3-2
directory, See Directory
displaying 4-5, 4-7, 4-7
editing, See vi
filename, See Filename
inode number, See Inode number
linking 4-10
listing 3-2
manipulation 4-5
modification time 3-1
moving 4-8, 4-8
name, See Filename
pathname required 3-4
pathname, printing 4-16
pattern search, See Pattern matching facilit
permission, See Permission
permissions 4-17
protection 3-1
removal 4-9
renaming 4-8
scratch file directory 3-6
size in bytes 3-1
sorting 4-23
special file, See Special file
temporary file, See Temporary file
types designated 3-1
Filename
asterisk (*) wildcard 3-8
characters use restrictions 3-4
description 3-4
example designated 3-6
long listing 4-13
question mark (?) representation 3-8
required 3-1, 3-4, 3-4
unique to directory 3-4, 3-4
Files
comparing 4-22

1-3

Introduction to XENIX

Index
find command 4-10
Finding a file 4-10
finger command 4-29
Foreground process 4-27, 4-27
Full pathname, See Pathname

G
Greater-than symbol (»
file combination 4-7
output redirection 3-12
redirection symbol 2-3
grep command 4-24
Group permission, See Permission

H
head command 4-7
Home directory 4-16

I
Inode number
defined 3-2
link, See Link
Is command 3-2
required for file 3-1, 3-2
Input
keyboard origin 3-11
redirection, See Redirection
termination 4-2
INTERRUPT key
command-line buffer cancellation 3-9
foreground process killing 4-27
logging in, nonsense character removal 2-1
program stopping 2-5

K
Kill character, See Ctrl-u
kill command 4-27,4-29
Killing a process 4-27

L
1 command 4-13
Ie command 4-12
listing 2-3
Less-than symbol «)
input redirection 3-12
Line
counting, See wc command
Lineprinter
status information 4-29
Link
command, See In command
defined 3-2
description 4-11
long listing 4-13
Linking files 4-10
Listing directory contents 4-12
Listing, See I command
Listing, See Ic command
In command 4-10, 4-11
Logging in 4-1
nonsense character removal 2-1
procedure 2-1
prompt character 2-1
terminal behavior remedy 2-5
type-ahead restriction 2-5
Logging out
procedure 2-5, 4-2
terminal behavior remedy 2-5
Login directory
new user 2-1
Login message 2-2
Login name
new user 2-1
procedure 4-1
lp 4-31
Ip 4-31,4-31, 4-31
Ip 4-32
Ip 4-32, 4-32, 4-32, 4-32, 4-32, 4-33
Ipr
Ipstat 4-33, 4-33
Ipstat command 4-29
Is command
function 3-2
inode number use 3-2

M
Mail
-s option 4-34
command
d command 4-35

I-4

Index

Introduction to XENIX

Mail (continued)
exit
q command 4-35
message
deletion 4-35
display 4-35
prompt 4-35
q command
exit 4-35
reading 4-35
reminder service 4-37
sending 4-34
you have mail message 2-2
Make directory, See mkdir command
mkdir command 4-14
more command 4-5
Move, See mv command
mv command 4-8, 4-8
directory moving 4-14

N
Name special file 4-17
Named pipe 4-17

o
Option
configuration 3-10
grouping 3-10
multiple options
grouping, See grouping
separate listing 3-10
position 3-10
Options
terminal 4-4
Ordinary file, See File
Output
appending
procedure 3-12
symbol (») 3-12
control 4-5
file reception 2-3
redirection 2-3, 4-7
resumption 4-5
terminal screen destination 3-11

p
Parent directory
description 3-6
shorthand name 3-6
passwd command 4-2
Password
changing 4-2
invisible on screen 2-1
logging in 2-1
new user 2-1
Path name
absolute path name
example 3-6
required 3-4
slash (/) significance 3-5, 3-5
unique to system 3-4
defined 3-5
full pathname, See absolute pathname
relative pathname
defined 3-5
example designated 3-6
structure 3-5
Pattern matching facility
cancellation 3-8
characters 3-7
description 3-6
grep command 4-24
Period (.)
filename use 3-5
working directory change 4-16
Permission types 4-17
block special device notation 4-17
change 3-2
denial notation 4-18
directory permission
assignment 3-2
change 3-2, 4-19
combinations designated 4-18
file creation, deletion notation 4-18
file listing notation 4-18
notation 4-17
search notation 4-18
search permission 4-21
write permission 3-2
execute notation 4-18
file permission
change 3-1
denial notation 4-18
execute permission 4-18
file creation, deletion notation 4-18
file listing notation 4-18
file protection 3-1
notation 4-17
read notation 4-18

1-5

Index

Introduction to XENIX

Permission types 4-17 (continued)
file permission (continued)
required 3-1
write notation 4-18
listing 4-17
notation 4-17
read notation 4-18
search notation 4-18
symbols designated 4-17
user class specification 4-20
write notation 4-18
PID
process identification number 4-27,4-29
Pipe
function 3-13
procedure 3-13
symbol (I) 3-13
Pipeline
defined 3-13
Print working directory, See pwd command
Printing
Process identification number, See PID
background, See Background process
foreground, See Foreground process
status
status 4-29
Program stopping 2-5
Prompt character 2-1,4-1
ps command 4-27, 4-29
pwd command 4-11, 4-16

Q
q command
mail
exit 4-35
Question mark (?)
filename, use avoidance 3-5
pattern-matching functions 3-8
single character representation 3-8
Quit, See q command
Quotation marks, double (3-5
Quotation marks, single (")
filename, use avoidance 3-5
grep command 4-24
pattern matching cancellation 3-8

R
r character, read permission notation 4-18
Read-ahead 2-4
Redirection
input redirection

1-6

Redirection (continued)
input redirection (continued)
procedure 3-12
symbol «) 3-12
output redirection 4-7
symbol (» 3-12
Reference Manual
directory removal information 4-14
linking information 4-11
sort command information 4-23
stty information 4-4
terminal characteristics setting 2-5
Relative pathname, See Pathname
Reminder seIVice
automatic 4-37
Remove directory, See rmdir command
Remove, See rm command
Removing a directory 4-14
Renaming a file 4-8
Request 4-31
RETURN key
command execution 2-2, 4-4
command-line buffer submittal 3-9
mail, message display 4-35
rm command 2-3, 4-9
rmdir command 4-14
RUBOUT key, program stopping 2-5

s
Screen, See Scrolling screen
Screen, See Terminal screen
Scrolling commands
more 4-6
Scrolling screen
stopping 4-5
Scrolling, control 4-5
Search permission, See Permission
Search strings
example designated 3-11
Searching for a file 4-10
Semaphore 4-17
Semicolon (;)
command separation 3-9
Shared data file 4-17
Shell
command interpretation 3-9
echo command 4-23
Single quotation marks, See Quotation marks.
single (")
Slash (/)
absolute pathname significance 3-5
pathname significance 3-5
sort command 4-23
Special characters
designated 3-7
pattern matching 3-6

Index

Introduction to XENIX
Special file
description 3-2
Status
command, See ps command
information procedures 4-28
stty command 4-4
terminal setting 2-5
Subdirectory 4-16
Subtraction, See Calculation
Switch
defined 3-10
regulations, See Option
System
basic concepts 3-1
characteristics 1-2
composition 1-1
tree-structured directory system 3-2

T
tail command 4-7
Temporary file
directory (/tmp) 4-28
kill command warning 4-28
Terminal screen
output, See Output
scrolling screen, See Scrolling screen
changing 4-3
name designation 2-2
options setting 4-4
resetting 2-5
strange behavior remedy 2-5
writing to, See write command
tty, terminal system name 2-2
Type-ahead 2-4, 4-4
Typing error correc~ion 2-4

v
Vertical bar (I)
pipe symbol 3-13

w
w character
directory permission notation 4-18
file permission, write notation 4-18
wc command 4-24
word count 3-14
who command 4-28
logged in users list 3-14
Word
counting, See wc command
Working directory, See Current directory
write command 4-35

x
x character
directory permission search 4-18
file permission, execute notation 4-18

u
ugo, permission classification 4-20
umask command
directory permission change 3-2
User classes 4-19
addition 2-1
classification 4-19
mail, See Mail
new user 2-1
permission, See Permission

I-7

XENIX® System V
Operating Systelll

Operations Guide

Infonnation in this document is subject to change without notice and does not represent a
commitment on the part of The Santa Cruz Operation, Inc. nor Microsoft Corporation.
The software described in this document is furnished under a license agreement or
nondisclosure agreement. The software may be used or copied only in accordance with
the tenns of the agreement. It is against the law to copy this software on magnetic tape,
disk, or any other medium for any purpose other than the purchaser's personal use.

This document was typeset with an IMAGEN@ 8/300 Laser Printer.
Hayes is a registered trademark of Hayes Microcom puter Products, Inc.
Microsoft, MS-DOS. and XENIX are trademarks of Microsoft Corporation.
IMA GEN is a registered trademark ofIMA GEN Corporation.

SCO Document Number: XG-12-19-86-3.0

Contents
1
1.1
1.2
1.3
1.4
1.5
2

2.1
2.2
2.3
2.4
3

3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
4
4.1
4.2
4.3
4.4
4.5
4.6
5

5.1
5.2
5.3

Introduction
Overview 1-1
The System Manager 1-1
The Super-User Account 1-1
The Keyboard 1-2
AboutThisGuide 1-'"3
Starting and Stopping the System
Introduction 2-1
Starting the System 2-1
LoggingInAstheSuper-User 2-3
Stopping the System 2-4
Preparing XENIX for Users
Introduction 3-1
Adding a User Account 3-1
Changing a User's Password 3-5
ForcingaNewPassword 3-5
Creating a Group 3-7
Changing a User's Login Group 3-8
Changing a User ID 3-9
Removing a User Account 3-11
Using File Systems
Introduction 4-1
File Systems 4-1
Permissions 4-5
Managing File Ownership 4-9
System Security 4-10
UsingXENIX Accounting Features 4-13
Maintaining File Systems
Introduction 5-1
Maintaining Free Space 5-1
File System Integrity 5-6

-i-

6
6.1
6.2
6.3
6.4
6.5

7
7.1
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.9
7.10
7.11
7.12
7.13
7.14
8
8.1
8.2
8.3
8.4
8.5
8.6
8.7
8.8
8.9
8.10
8.11
8.12
9
9.1
9.2
9.3
9.4
9.5

Backing Up File Systems
Introduction 6-1
The Sysinfo Account 6-1
Strategies for Backups 6-1
UsingthesysadminProgram 6-2
Using the tar Command 6-6
Using Peripheral Devices
Introduction 7-1
UsingMultiscreen 7-1
Adding a Terminal 7-2
Setting Terminal Lines 7-3
Changing Serial Line Operation 7-7
Setting the Terminal Type 7-9
Removing a Terminal 7-10
Configuring Serial Ports 7-11
Setting Up a Serial Console 7-12
Modem Usage UnderXENIX 7-13
AddingaLineprinter 7-18
AddingAdditional Memory 7-28
AddingaHardDisk 7-30
Creating Boot and Root Floppy Disks 7-40
Solving System Problems
Introduction 8-1
Restoring a NonechoingTerminal 8-1
Solving Lineprinter Problems 8-1
Stopping a Runaway Process 8-2
Replacing a Forgotten Password 8-3
Removing Hidden Files 8-3
Restoring Free Space 8-3
Restoring Lost System Files 8-3
Restoring an Inoperable System 8-4
Recovering from a System Crash 8-4
Mapping a Bad Track 8-5
ChangingXENIXInitialization 8-5
Building a Micnet Network
Introduction 9-1
Planning a Network 9-1
BuildingaNetwork 9-5
Starting the Network 9-11
Testing a Micnet Network 9-12
-ii-

9.6
A
A.l
A.2
A.3
A.4
A.s
A.6
B
B.l
B.2
B.3
B.4
B.s
B.6
B.7
B.8
B.9
B.I0

Using a Uucp System 9-15
XENIX Special Device Files
Introduction A-l
File System Requirements A-l
Special Filenames A-l
Block Sizes A-l
Gap and Block Numbers A-2
Terminal and Network Requirements
XENIX Directories
Introduction B-1
The Root Directory B-1
The Ibin Directory B-1
The IdevDirectory B-1
The/etcDirectory B-2
The llib Directory B-3
The Imnt Directory B-3
The Itmp Directory B-3
The lusrDirectory B-3
Log Files B-4

- iii-

A-2

Chapter!
Introduction
1.1 Overview 1-1
1.2 The System Manager 1-1
1.3 The Super-User Account 1-1
1.4 The Keyboard 1-2
1.S About This Guide 1-3

-1-i -

Introduction

1.1 Overview
The XENIX operating system is a powerful system of programs, which
allows you to accomplish a full spectrum of tasks, from developing highlevel and assembly language programs to creating, editing, and typesetting
documents. To keep this powerful system running smoothly, the XENIX
system requires careful control of its operation and a regular schedule of
maintenance. This guide explains how to operate and maintain the XENIX
operating system on your computer, ensuring maximum performance with
the least number of system problems.
This guide also explains how to expand a XENIX system with a Micnet network. A Micnet network allows serial communication between other
XENIX systems in your work environment. The Micnet programs and
commands include the netutil program, which is used to install the network, and the mail, rep, and remote commands, which are used to pass
messages, files, and commands over the network.
See Chapter 9, "Building A Micnet Network" for a complete explanation
of this facility.
1.2 The System Manager
Every XENIX system should have one person in charge of system maintenance and operation. In this guide, that person is called the system
manager. It is the system manager's duty to ensure the smooth operation of
the system and to perform tasks that require special privileges.
Depending on the size of the system and the number of users on the system, a system manager's job can be anything from a once-a-week task to a
full-time job. Even if the system is small, the system manager should faithfully perform each required maintenance task, since sloppy maintenance
can affect XENIX performance.
All tasks in this guide are presented from the system manager's point of
view, but many can also be accomplished by ordinary users. Since some of
the tasks dramatically change the system's operation, we recommend that,
whenever possible, the system manager perform these tasks. This can
preven t un wan ted or unnecessary changes to the system.
1.3 The Super- User Account
The super~user account is a special account for performing system maintenance tasks. It gives the system manager unusual privileges that ordinary
users do not have, such as accessing all files in the system, and executing
privileged commands. Many of the tasks presented in this guide require
that the system manager be logged in asthe super-user. To do this, the sys-

1-1

XENIX Operations Guide

tern manager must know the super-user password created during the installation of the XENIX system (see the XENIX Installation Guide).
Users who are authorized to act as the super-user, including the system
manager, should log in as the super-user only when it is necessary to perform a system maintenance task. Even if the system manager is the only
person using the system, he should create a user account for himself and
use it for day-to-day work, reserving the super-user account for system
maintenance tasks only.
The number of individuals who are given the super-user password should
be kept to a minimum. Misuse of the super-user powers by naive users can
result in a loss of data, programs, and even the XENIX system itself.

1.4 The Keyboard
Many keys and key combinations have special meanings in the XENIX system. These keys and key combinations have special names that are unique
to the XENIX system, and mayor may not correspond to the keytop labels
on your keyboard. To help you find the special keys, the following table
shows which keys on a typical console correspond to XENIX system keys.
A list for your particular console is in keyboard(HW).
In this table, a hyphen (-) between keys means "hold down the first key
while pressing the second."

1-2

XENIX N arne

Key top

Action

BREAK

Delete

Stops current action and
returns to the shell. This
key is also called the
INTERRUPT
or
DELETE key.

BACKSPACE

Backspace

Deletes the first character to the left of the cursor.

Ctrl-d

Signals the end of input
from the keyboard; also
exits current shell or initiates the "logout" procedure if the current
shell is the login shell.

Ctrl-h

Erase

Deletes the first character to the left of the cursor. Also calied the
ERASE key.

Introduction

Ctrl-q

Restarts printing after it
has been stopped with
Ctrl-s.

Ctrl-s

Stops printing at the
standard output device,
for example a terminal.
Does not stop the program.

Ctrl-u

Deletes all characters on
the current line. Also
called the KILL key.

Ctrl-\

Quits current command
and creates a core file
(Recommended
for
debugging only). See
core(F) for more information.

ESCAPE

Esc

Exits the current mode;
for example, exits insert
mode when in the editor
vi.

RETURN

Return

Terminates a command
line and initiates an
action from the shell.

Many of these special function keys can be modified by the user. See
s tty( C) for more information.
1.5 AboutThis Guide
The tasks presented in this guide range from simple ones requiring very littIe knowledge about XENIX, to quite complex tasks requiring extensive
knowledge about XENIX and your computer.
Each chapter explains the tools and knowledge you need to complete the
tasks described in that chapter. In some cases, you may be required to
refer to other manuals, such as the XENIX User's Guide.
Chapter 1, "Introduction," introduces this guide.
Chapter 2, "Starting and Stopping the System," explains how to start and
stop the XENIX system and how to log in as the super-user, the XENIX
system's special system manager account.

1-3

XENIX Operations Guide

Chapter 3, "Preparing XENIX for Users," explains how to create accounts
for the users who work on your system, how to assign groups, and how to
manage user IDs.
Chapter 4, "Using File Systems," explains how to create and mount file
systems, how to set permissions, and how to keep the system secure.
Chapter 5, "Maintaining File Systems," explains how to maintain free
space on the root file system and other file systems.
Chapter 6, "Backing Up File Systems," explains how to create backup
copies of the root file system and other file systems.
Chapter 7, "Using Peripheral Devices," explains how to add terminals,
printers and other peripheral devices.
Chapter 8, "Solving System Problems," explains how to solve system prob1ems such as a jammed lineprinter or a forgotten password.
Chapter 9, "Building a Micnet Network," explains how to create a multiple
system mailing network with Micnet.
A ppendix A, "XENIX Special Device Files," presents a list of the XENIX
system special files, and explains how to use these files when creating and
maintaining file systems.
Appendix B, "XENIX Directories," presents a list of commonly used
XENIX directories and log files.

1-4

Chapter 2
Starting and
Stopping the System
2.1

Introduction

2-1

2.2

Starting the System 2-1
2.2.1 Loading the Operating System 2-1
2.2.2 Cleaning the File System 2-1
2.2.3 Choosing the Mode of System Operation 2-2

2.3

LoggingInAstheSuper-User 2-3

2.4 Stopping the System 2-3
2.4.1 Using the shutdown Command 2-4
2.4.2 UsingthehaltsysCommand 2-4

-2-i -

Starting and Stopping the System

2.1 Introduction

This chapter explains how to start and stop the XENIX system. It also
explains how to log in as the super-user.
2.2 Starting the System

Starting a XENIX system requires more than just turning on the power. You
must also perform a series of steps to initialize the system for operation.
Starting the system requires:
-

Loadingthe operating system

Cleaning the file system (if the system was improperly stopped)

Choosing the mode of system operation

The following sections describe each of these procedures,.
2.2.1 Loading the Operating System

The first step in starting the system is to load the operating system from the
computer's hard disk. Follow these steps:
1. Turn on power to the computer and hard disk. The computer loads
the XENIXbootstrap program and displays the message:
Boot
2.

Press the RETURN key. The bootstrap program loads the XENIX
operating system.

When the system is loaded, it displays information about itself and checks
to see if the "root file system" (i.e., all files and directories) is clean. If it is
clean, you may choose the mode of operation. If not, the system requires
you to clean the file system before choosing.
2.2.2 Cleaning the File System

You must clean the file system if the system displays the message:
Proceed with cleaning (yorn)?
This message indicates that the system was not stopped properly as
described in the section, "Stopping the System", given later in this

2-1

XENIX Operations Guide

chapter. The XENIX operating system requires a clean file system to perform its tasks.
To clean the file system, enter y (for "yes") and press the RETURN key.
The system cleans the file system, repairing damaged files or deleting files
that cannot be repaired. It reports on its progress as each step is completed. At some point, it may ask if you wish to salvage a file. Always
answer by enteringy and pressing the RETURN key.
When cleaning is complete, the system usually asks you to choose the
mode of operation, but it may also display the message: .

** Normal System Shutdown **
** Safe to Power Off **
-or-

** Press Any Key to Reboot **
If it displays this message, you must reload the system. You can do this by
pressing any key or resetting the computer and repeating the steps given in
the previous section. For instructions on how to reset your computer, see
the hardware man ual provided with the computer.
2.2.3 Choosing the Mode of System Operation

You may choose the mode of XENIX operation as soon as you see the message:
Type CONTROL-d to continue with normal startup,
(or give the root password for system maintenance):
The system has two modes: normal operation and system maintenance
mode. Normal operation is for ordinary work on the system. This is the
mode you should choose to allow multiple users to log in and begin work.
System maintenance mode is a specialized mode reserved for work to be
done by the system manager. It does not allow multiple users.
To choose normal operation, press the Ctrl-d key. The system displays a
startup message and begins to execute commands found in the command
file letclrc described in Chapter 8, "Solving System Problems." When the
commands are finished, the system displays the "login:" prompt. You may
then log in as a normal user, as decribed in the XENIX Introduction to
XENIX, or as the super-user, as described in the next section.

2-2

Starting and Stopping the Sys tern

To choose system maintenance mode, enter the super-user's password
(sometimes called the "root password") and press the RETURN key. The
system displays the message of the day and the maintenance mode prompt
(#). The commands in the letclrc file are not executed. (Choose system
maintenance mode only if you must do system maintenance work that
requires all other users to be off the system.)
2.3 Logging In As the Super- User
Many system maintenance tasks, when performed during normal operation, require that you log in as the super-user. For example, you must be
logged in as the super-user to stop the system.
Before you may log in as the super-user, you need the super-user password. You also need to see the "login:" message on your terminal's screen.
If you do not see this message, press the Ctrl-d key until it appears.
To login as the super-user, follow these steps:

1. When you see the "login:" message, enter the super-user's login
name
root
and press the RETURN key. The system prompts you for the superuser's password.
2. Enter the super-user's password and press the RETURN key. The
system does not display the password as you enter it, so enter each
letter carefully.
The system opens the super-user account and displays the message of the
day and the super-user prompt (#).
Take reasonable care when you are logged in as the super-user. In particular, you should be very careful when deleting or modifying files or directories. Avoid using wildcard designators in filenames and frequently check
your current working directory. Small errors can cause annoying and
unwanted changes to the system and user files. Some errors can cause irretrievable damage to a file or the system.
You can leave the super-user account at any time by pressing Ctrl-d.

2-3

XENIX Operations Guide

2.4 Stopping the System
Stopping the XENIX system takes more than just turning off the computer.
You must prepare the system for stopping by using either the shutdown or
the haltsys command. The following sections describe each command.
2.4.1 Using the shutdown Command
The shutdown command is the normal way to stop the system and should
be used whenever the system is in normal operation mode. It warns other
users that the system is about to be stopped and gives them an opportunity
to finish their work.
To stop the system with the shutdown command, follow these steps:
1. Log in as the super-user (see the section "Logging in as SuperUser" in this chapter). The system opens the super-user account
and displays the message ofthe day and the super-user's prompt.

Enter:
/etc/shutdown
'and press the RETURN key. The system loads the command which
in tum prompts you for the number of minutes you wish to elapse
before the computer stops:
Minutes till shutdown? (0-15):

3. Enter any number from 0 to 15 and press the RETURN key. The system displays a warning message at each terminal, asking logged in
users to finish their work and logout. As soon as all users are logged
out or the specified time has elapsed, the system closes all accounts
and displays the message:

** Normal System Shutdown **
** Safe to Power Off **
-or-

** Press Any Key to Reboot **
and stops.
Youmaynowturn off the computer.

2-4

Starting and Stopping the System

2.4.2 Using the haltsys Command
The haltsys command maybe used to halt the system immediately. In general, it should be used only when no other users are on the system or when
the system is in system main tenance mode.
To stop the system with the haltsys command, follow these steps:
1. Log in as the super-user (not required when in system maintenance
mode). The system opens the super-user account and displays the
message of the day and the super-user prompt.
2.

Enter:

I etc/haltsys
and press the RETURN key. The system displays the message:

** Normal System Shutdown **
** Safe to Power Off **
-or-

** Press A ny Key to Reboot **
and stops.
You may now tum off the hard disk and computer.

2-5

Chapter 3
Preparing XENIX for Users
3.1 Introd uction 3-1
3.2 Addinga User Account 3-1
3.3 Changing a User's Password 3-5
3.4 Forcing a New Password 3-5
3.5 Creating a Group 3-7
3.6 Changing a User's Login Group 3-8
3.7 Changing a User ID 3-9
3.8 Removing a User Account 3-11

- 3-i-

Preparing XENIX for Users

3.1 Introduction

User accounts help the XENIX system manager keep track of the people
using the system, and control their access to the system's resources.
Ideally, each user should have a user account. Each account has a unique
"login name" and "password" with which the user enters the system, and a
"horne directory" where the user does his work.
It is the system manager's job to create accounts for all users on the system.
It is also the manager's job to maintain user accounts by changing user
passwords, login groups, and user IDs when necessary.

This chapter explains how to:
-

Add user accounts to the system

Change an account's password

Force new passwords

Create a group

Change an account's login group
Change an account's userID

Remove user accounts from the system

The following sections describe each in detail.
3.2 Adding a User Account

You may add a user account to the system with the mkuser program. The
program creates a new entry in the XENIX system's /etc/passwd file. This
entry contains information about the new user, such as login name and initial password, that the system uses to let the user log in and begin work.
The program also creates a home directory for the user, a mailbox for use
with the mail command, and a .profile or .login file which contains XENIX
commands that are executed when the user logs in.
To create a new user account, follow these steps:

1. Login as the super-user.
2.

Enter:
mkuser

3-1

XENIX Operations Guide

and press the RETURN key. The system displays the followingmessage:
Mkuser
Add a userto the system
Do you require detailed instructions? (yIn):
3. Enter the letter y (for "yes"), if you want information about the program, otherwise type the letter n (for "no"). Enter q (for "quit")
only if you wish to stop the program and return to the system. If you
type a "q" to any "(yIn)" prompt, the program will stop and no
changes will be made.
When the program continues, it prompts you to enter the new user's
login name:
Enter new user's login name:
The login name is the name by which XENIX will know the user. It is
usually a short version of the user's actual name, typed in lowercase
letters. For example, either "johnd" (a first name and last initial) or
"jdoe" (a first initial and last name) is customary for the user John
Doe.
4.

Enter the new name, and press the RETURN key. The program now
prompts you for information about the new user's group name and
group number.
A group name is the name of the group of users to which the new
user will belong. Users in a group have access to a common set of
files and directories. The group name is optional. If not given, the
XENIX system's common group "group" (with group ill 50) is used.
The program prompts:
Do you want to use the default group? (yIn):
If you enter "y", the user's group name will be "group" and the
groupID number will be50.
If you en ter "n" , the program responds with a list of existing groups:

Existing groups are:
Group "group" (50): demo vdemo cdemo
Do you want to use one of these groups? (yIn):

3-2

Preparing XENIX for Users

If you enter either "y" or "n", you are asked which group you want
to use. Enter the name of the group. You may create a new group by
entering in thenewname.

Next, you are prompted for a group number. The group ID, or
number, may be any number from 50 to 3()()()() that isn't already used
for another group.
5. After entering the group name and ID, you are prompted for the initial password.
Enter password:
The initial password is the password you assign to the new user. The
user will use the initial password to enter the account for the first
time. Once in the account, the user should create a new password
for himself, one that is hard to guess. (See the section "Changing
Your Password" in Chapter 4 of the Introduction to XENIX.)
6.

Enter the password, and press the RETURN key.

7. Next, you are prompted for a shell type. You see a list and brief
explanation of the available shells (sh, vsh, csh, rsh, and uucp
login) and the prompt:
ENTER Shell type (1, 2, 3, 4 or 5) and press RETURN:

sh is the standard (Bourne) shell. vsh is the menu driven "visual"
shell, csh is the c-shell rsh is the restricted shell, and uucp login is
an entry in /usr/Ub/uucp/uucico enabling logging in to the system via
uucp. For more information, see vsh (C) in the XENIX Reference
Guide.
8. Enter the desired shell number and press RETURN. After you have
entered the shell type, the program prompts you for a comment:
Please enter Comment

>------------------->

A comment is information about the new user, such as a department name and phone extension. Although, the comment is
optional, it is useful if the finger command is often used to display
information about users. If given, the comment must be no more
than 20 characters long, including spaces. It must not contain any
colons (:). The example
John Doe, 123
shows the recommended form for a comment.

3-3

XENIX Operations Guide

9. Enter the comment. Make sure it is 20 characters or less. If you do
not wish to en ter a comment, just press the RETURN key.
The program now displays what you have entered and the special
user entry that it has created for the new user. This entry is copied to
the special system file letc!passwd. The entry shows the login name,
the password (encrypted), the user ID, the group ID, the comment,
the user's home directory, and the startup program. Items in the
entry are separated by colons (:). (For a full description of each
item, see passwd(M) in the XENIX Reference Manual.)
The program then gives you an opportunity to change the user
name, password, group, or comment:
Username is "johnd", user ID is 2001.
Group name is "group", group number is SO.
Comment field is: John Doe, 12
Shell is "/binl csh"
Do you want to change anything? (yIn):
10. Enter the letter y (for "yes") and press the RETURN key, if you wish
to change something. Enter n (for "no") and skip to the next step if
you wish to complete the new account. (Enter q, for "quit", only if
you wish to leave the program and abort the new account.)
If you enter y, the program prompts for the item you wish to change:

username
password
group
comment
shell
Enter the name of the item you wish to change and press RETURN.
After you have changed an item, you see the complete list of items
and are asked if you wish to make other changes. When you are
finished with any changes, the program adds the user.
11. The program displays the message:
Password file updated
followed by a description of the actions it has taken to add the new
user account to the system. The program then asks if you wish to
add another user to the system.
12. Enter y if you wish to add another user. Otherwise, enter n to stop
the program and return to the super-user prompt.

3-4

Preparing XENIX for Users

A user can log into a new account as soon as it is created. For details see the
Introduction to XENIX.
3.3 Changing a User's Password
Normally, an ordinary user can change the password of his own account
with the passwd command (see the Introduction to XENIX). Sometimes,
however, it may be necessary for the super-user to change the password for
him, for example, if the user has forgotten his password and cannot get
into the account to change it. The super-user may change the password of
any user (including himself) with the passwd command.
To change a password, follow these steps:

1. Log in as the super-user.
2.

Enter:
passwd login- name
(where login- name is the user's login name) and press the RETURN
key. The command displays the message:
New password:

3. Enter the new password and press the RETURN key. The command does not display the password as you type it, so type carefully.
The command then prompts you to enter the password again:
Retype new password:
4.

Enter the password again and press the RETURN key.

To see how an ordinary user can change his own password with the passwd
command, see the Introduction to XENIX.
3.4 Forcing a New Password
From time to time, a user account may need a higher level of security than
ordinary. Since the security of any account depends its password, it is
important to keep the password as secret as possible. One way to provide
greater security is to force users to change their passwords on a regular
basis.
You can force users to change their passwords by using the pwadmin command. This command automatically dates each password and requires the
user to provide a new password when the specified number of weeks have
passed. The command also requires users to wait a minimum number of

3-5

XENIX Operations Guide

weeks before allowing them to restore their previous password. To use the
pwadmin command, you must login as the super-user.
You can enable password aging for a specified user by using the -a option.
Enter:
pwadmin -a login-name
where login-name is the login name of a user. The user will then be
required to wait a minimum number of weeks before he can change his
password, and will be forced to change his password after a maximum
number of weeks have elapsed. The -a option uses the default minimum
and maximum values found in the letc!defaultlpasswd file.
You can choose your own minimum and maximum number of weeks by
using the -min and -max options. For example, a common pair of
minimum and maximum values is 2 and 8. To set the minimum and maximum dates, enter:
pwadmin -min num -max num login- name

where num is a number in the range to 63, and login- name is simply the
login name of the user whose password you are administering. Note that
the minimum and maximum cannot both be 0, and that the minimum must
not be greater than the maximum.
If you are unsure of the current minimum and maximum values for a password, you can display them by entering:

pwadmin -d login- name
This command does not change the current values.
If you wish to force a user to change his password immediately, enter:

pwadmin -f login-name
The user is prompted on his next login to supply a new password.
When a password no longer requires extra security, you can remove the
current minimum and maximum values for the password by entering:
pwadmin -n login- name
The system will no longer prompt for changes.
For more information about password aging, see pwadmin(C) and
passwd(M)intheXENIXReference Manual.

3-6

Preparing XENIX for Users

3.5 Creating a Group
A group is a collection of users who share a common set of files and directories. The advantage of groups is that users who have a common interest
in certain files and directories can share these files and directories without
revealing them to others. Initially, all users belong to the common system
group named "group", but you can create new groups by modifying the
XENIX system file fete/group using a XENIX text editor.
To create a new group, you need to choose a group name and a group
identification number (group ID). You also need to make a list of the users
in the new group. The group name may be any sequence of letters and
numbers up to eight characters long, and the group ID may be any number
in the range 50 to 30000. Both the group name and ID must be unique, i.e.,
they must not be the same as any existing group name or ID.
To create a new group, follow these steps:
1. Login as the super-user.

Display the contents of the fete/group file by entering:
cat / etcf group
and pressing the RETURN key. The ca t command displays the contents of the fete/group file. The file contains several entries, each
defining the group name, group ID, and users for a group. Each
entry has the form:
group- name: :group- ID :users

The users are shown as a list of login names separated by commas
(,). For example, a typical file may look like this:
other:x:l:demo
sys:x:2:
group: :50:johnd, suex
3. Check the fete/group file entries to see that the group name and ID
you have chosen are unique.
4.

If the group name and ID are unique, invoke a XENIX text editor
(see the XENIX User's Guide) and specify fete/group as the file to
edit.

3-7

XENIX Operations Guide

5. Locate the last line in the file, then insert the new entry in the form
given above. For example, if you wish to create a group named
"shipping" with group ID "142" and users "johnd", "marym", and
"suex", enter:
shipping: :142:johnd,marym,suex
6. Exit the editor.
To make sure you have entered the group names correctly, use the
grpcheck command to check each entry in the Jete/group file. If the new
en try is free of errors, no other changes to the file are req uired.
You can create any number of new groups. Each group may have any
number of members. Furthermore, any user may be a member of any
number of groups. Multiple group membership is especially convenient
for users who have interests that span a variety of areas.
If a user is a member of several groups, he can gain access to each group by

using the newgrp command. See the Introduction to XENIX for details.
3.6 Changing a User's Login Group
When a user logs in, the system automatically places the user in his "login
group". This is the group given by the group ID in the user's Jetc/passwd file
entry (see the section "Adding a User Account" in this chapter). You can
change the user's login group by changing the group ID. To change the
group ID you need the group ID of the new login group, and you need to
know how to use a XENIX lext editor (see the XENIX User's Guide).
To change the group ID, follow these steps:
1. Login as the super-user.
2.

Use the cd command to change the current directory to the Jetc
directory. Enter:
cd letc

3. Use the cp command to make a copy of the Jetc/passwd file. Enter:
cp passwd passwd+

3-8

Preparing XENIX for Users

Invoke a text editor and specify fetcfpasswd+ as the file to edit.

5. Locate the desired user's password entry. Each entry begins with
the user's login name.
6. Locate the user's group ID number in the user's password entry. It is
the fourth item in the entry. Items are separated by colons (:). For
example, the entry:
marym:9iKlwp:205:50:MaryMarch, 122:fusrlmarym:fbinfsh
has group ID "50".
7. Delete the old group ID and insert the new one. Be sure you do not
delete any other portion of the user's password en try.
8.

Exit the editor.

Use the mv command to save the old /etclpasswd file. Enter:
mv passwd passwd-

10. Use the mv command to make the edited file the new fetclpassword
file. Enter:
mv passwd+ passwd
You can make sure you have en tered the new login group correctly by using
the pwcheck command. If the new entry is correct, no other changes to the
file are required.
You must not change the group IDs for system accounts such as "cron" and
"root". System accounts are any accounts whose user IDs are less than
200. The user ID is the third item in the password entry.
Note that changing a user's login group does not change the "group ownership" of his file-s. Group ownership defines which group has access to a
user's files. If users in the new group wish to access the user's files, you
must change the group ownership with the chgrp (for "change group")
command. For details, see the section "Changing Group Ownership" in
Chapter 4.
3.7 Changing a UserID
Sometimes it is necessary to change the user ID in a user's account entry to
allow a user to access files and directories transferred from other computers. In particular, if a user has different accounts on different computers
and frequently transfers files and directories from one computer to
another, the user IDs in each of his account entries must be made the same.

3-9

XENIX Operations Guide

You can make them the same by modifying the account entries in the
letclpasswd file.
To change a user ID, follow these steps at every computer for which the
user has an account:

Use the cd command to change the current directory to the fete
directory. Enter:
cd letc

Use the cp command to make a copy of the Ietclpasswd file. Enter:
cp passwd passwd+

Invoke a XENIX text editor and specify letc!passwd+ as the file to
edit.

5. Locate the user's account entry. Each entry begins with the user's
login name.
6.

Locate the current user ID. The ID is the third item in the entry. For
example, the entr~:
marym:9iKlwp:20S:S0:MaryMarch, 122:/usrlmarym:/bin/sh
has a user ID "205". Sub stitute the new user ID for the old one.

Exit the text editor.

Use the mv command to save the old letclpasswd file. Enter:
mv passwd passwd-

Use the mv command to make the edited file the new letelpasswd
file. Enter:
mv passwd+ passwd

No other changes to the file are required.
In most cases, you can change the user ID to the same number as the user's
most-used account. But the new number must be unique at every system
for which the user has an account. If there is any conflict (for example, if
the number already belongs to another user on one of the svstems). vou
must choose a new~numbe;' You can choose any number gre~ter th;n: 200.
Just make sure it is unique, and that you copy it to all systems on which the
user has an account.

3-10

Preparing XENIX for Users

Once a user's ID has been changed, you must change the "user ownership"
of the user's files and directories from the old user ID to the new one. You
can do this with the chown (for "change owner") command described in
Chapter 4, "Using File Systems."
For example, to change the ownership of johnd's home directory, enter:
chown johnd lusr/johnd
Note that you may use the find command described in Chapter 6, "Backing
Up File Systems," to locate all files and directories with the user's old user
ID.

3.8 Removing a User Account
It is sometimes necessary to remove a user account from the system. You

can remove a user account with the rmuserprogram. The program deletes
the user's entry from the letclpasswd file and removes the user's home
directory and mailbox.
Before you can remove the user account, you must remove all files and
directories from the user's home directory, or move them to other directories. If you wish to save the files, you may us~ the tar command to copy
the files to a floppy disk (see the section "Copying Files to a tar disk" in
Chapter6).
To remove a user account, follow these steps:

1. Login as the super-user.
2. Enter:
cd lusrllogin- name
and press the RETURN key to change to the user's home directory.
The login- name must be the user's login name.
3. Make sure that you have made copies of all important files and
directories in the user's home directory.
4.

Use the nn (for "remove") command to remove all files and directories from the user's home directory. This includes any files that
begin with a period (.). Directories can be removed by using the -r
(for "recursive") option of the rm command. For example, the
command:
rm -r bin

3-11

XENIX Operations Guide

removes the directory named bin and all files within this directory.
5.

After removing all files and directories, make sure the user's mailboxisempty. Enter:
cat lusrl spool/mailllogin- name
and press the RETURN key, where login- name is the user's login
name. If the mailbox contains text, enter:
cat Idev/null > lusrlspool/mailllogin- name
and press the RETURN key.

When the user's home directory and mailbox are empty, enter:
cd lusr
and press the RETURN key. The user's home directory cannot be
removed until you have moved to another directory.

Enter:
rmuser
and press the RETURN key. The program displays a message
explaining how to remove a user:
****rmuser-remove a user from the system ****
Press ENTER when you are ready.
The program then prompts you for the login name of the user you
wish to remove:
Enternameofid to be removed.

Enter the user's login name. You should now see the message:
Removing user name from the system. CONFIRM? (y/n/q):

Enter y (for "yes") to remove the user from the system. Otherwise
enter n (for "no") to stop the removal, or q (for "quit") to stop the
program. The program removes the user's entry from the
letclpasswd file, the user's mailbox, .profile file, and home directory. The program displays the message:
User name removed from the system

3-12

Preparing XENIX for Users

The program now gives you a chance to remove another user:
Do you want to remove another user? (y/n/q):
10. Enter y to remove another user. Otherwise, enter nor q to stop the
program.
Note that the nnuser program will refuse to remove an account that has a
system name, such as "root", "sys", "sysinfo", "cron", "uucp", or a system ID (user ID below 2(0). Also, the program cannot remove a user
account if the user's mailbox still has mail in it, or if the user's home directory contains files other than .profile.

3-13

Chapter4
Using' File Systems
4.1

Introduction 4-1

4.2

File Systems 4-1
4.2.1 Creating a File System 4-1
4.2.2 Mounting a File System 4-3
4.2.3 UnmountingaFile System 4-4
4.2.4 Formatting Floppy Disks 4-5

4.3

Permissions 4-5
4.3.1 Displaying Permissions 4-6
4.3.2 Changing Permissions 4-7
4.3.3 Changing the File Creation Mask

4-8

4.4 Managing File Ownership 4-9
4.4.1 Changing User Ownership 4-9
4.4.2 Changing Group Ownership 4-9
4.5

System Security 4-10
4.5.1 Physical Security 4-10
4.5.2 Access Security 4-11
4.5.3 Protecting Special Files 4-11
4.5.4 Copying Floppy Disks 4-11

4.6

UsingXENIX Accounting Features 4-13
4.6.1 Starting Process Accounting 4-13
4.6.2 DisplayingAccountingInformation 4-14

-4-i -

Using File Systems

4.1 Introduction
This chapter describes one of the most important responsibilities of a system manager: controlling and recording users' access to the files and directories on the system. It introduces file systems, permissions, system security, and process accounting.
4.2 File Sys terns
A file system is the XENIX system's way of organizing files on mass storage
devices such as hard and floppy disks. A file system consists of files, directories, and the information needed to locate and access these items.
Each XENIX system has at least one file system. This file system is called
the root file system and is represented by the symbol "I". The root file system contains all the XENIX programs that may be used by the system
manager. It usually contains all the user directories as well.
A XENIX system may also have other file systems that contain user directories and application programs. One reason for using other file systems is
to expand the available storage space of the system. Each additional file
system adds its free space to the system's total space. New file systems can
be specifically created by a user, then mounted onto the system so they can
be used.
You can create a file system with the mkfs command. This command sets
the size and format of the file system and may also copy some files to the
new system. You can mount a file system with the mount command. Once
mounted, you may access the files and directories in the file system as easily
as files and directories in the root file system. (The root file system is permanently mounted.) When you are finished with a file system, you can
unmount it with the umount command.
You can create new file systems on any media with the mkfs command. A
reason for creating new file systems on floppy disks is to establish a collection of application programs and data files that can be easily mounted and
used when needed.
The following sections explain how to create and use file systems.
4.2.1 Creating a File System
You can create a file system on a formatted floppy disk by using the mkfs
command.

4-1

XENIX Operations Guide

To create a file system on a floppy disk, you need:
-

A formatted floppy disk

The special filename of a floppy disk drive

The disk block size ofthe disk

The gap and block numbers for the disk

To format a floppy disk, see the section "Formatting Floppy Disks" in this
chapter. The special filenames for the disk drives, the disk block size, and
the gap and block numbers depend on the specific system and are given in
AppendixA.
Note that if a file system already exists on the disk, it will be destroyed by
this procedure. For this reason, be particularly careful not to create a new
file system on the root file system. If you destroy the root file system, you
will have to reinstall the XENIX system.
To make a file system on a floppy disk, follow these steps:

1. Log in. You do not have to be logged in as the super-user to use the
mkfs command.
2.

Insert a formatted floppy disk into a floppy disk drive. Make sure
there is no read-only tab on the disk jacket.

3. Enter:
letc/mkfs specialjile blocksize gap block

(where specialjile, blocksize, gap, and block are supplied by you)
and press the RETURN key. The system automatically creates the
file system. If it discovers data already on the disk, the system
displays the message:
mkfs: specialjile contains data. Overwrite? (yIn):
If you are sure the disk contains nothing that you want to save, enter
y and press the RETURN key to overwrite the data and continue
creating the file system. Otherwise, enter n. If you enter n, no file
system is created.

4-2

Using File Systems

For example, the following command creates a file system on the floppy
disk drive Idevlfdl, with blocksize 320 and gap and block numbers 2 and 8:

letc/mkfs Idev/fdl 320 2 8
The actual filename, blocksize, gap, and block numbers vary. For the
infonnation specific to your machine see Appendix A.
4.2.2 Mounting a File System
Once you have created a file system, you can mount it with the mount command. To mount a file system you need:
-

The special filename of a disk drive

The name of an empty directory

The special filenames of disk drives are given in Appendix A. The directory to receive the file system may be any directory as long as it is empty
(contains no files) and is not your current working directory. Note that the
directory Imnt is specifically reserved for mounted file systems.
To mount a file system, follow these steps:

1. Log in. You do not have to be logged in as the super-user to use this
command.
2.

Insert the disk containing the file system into a floppy disk drive.

3. Enter the appropriate mount command, and press the RETURN
key. The command should have thefonn:
letc/mount speciaZjiZe directoryname
where speciaZjiZe is the special filename of the disk drive containing
the disk, and directoryname is the name of the directory to receive
the file system. If the disk has a read -only tab, make sure you
include the switch -r at the end of the command.
For example, you can use the following command to mount the disk in disk
drive Idevlfdl onto the directory named laccount:
/etc/mount Idev/fdl /account

Remember to make sure that the specified directory is empty before issuing the command. If the command displays the message:
mount: Structure needs cleaning

4-3

XENIX Operations Guide

use the fsck command to clean the file system and try to mount it again (see
the section "File System Integrity" in Chapter 5). If the command displays
the message:
mount: Device busy
either the file system has already been mounted and cannot be mounted
twice, or a user is currently in the directory. You must wait for users to
leave a directory before you can moun t the directory.
To check that the file system was properly mounted, use the cd command
to change to the directory containing the mounted system and the I command to list the contents. The command displays the files and directories
in the file system. Be sure to use the cd command to leave the directory
after finishing your work in it.
Note that frequently used file systems can be mounted automatically when
starting the system by appending the appropriate mount commands to the
letc!rc file. See the section,"Changing the letc!rc File," in Chapter 8 for
details.
4.2.3 Unmounting a File Sys tern
You can unmount a mounted file system with the umount command.
Unmounting a file system does not destroy its contents. It merely removes
access to the files and directories in the file system.
To unmount a mounted file system, enter:

letc/umount specialjile
and press the RETURN key. The specialjile is the name of the special file
corresponding to the disk drive containing the disk with the file system.
The command empties the directory that previously contained the file system, and makes the directory and the corresponding disk drive available
for mounting another file system.
For example, the following command unmounts a file system from the disk
drive Idevlfdl:

letc/umount Idev/fdl
Before unmounting a file system, make sure that no files or directories are
being accessed by other commands or programs. The umount command
displays the following message if you or another user are currently in the
directory con taining the file system:
umount: Device busy

4-4

Using File Systems

4.2.4 Formatting Floppy Disks
You can format floppy disks with the format program. Formatted disks are
required whenever you create a file system. They are also required when
you back up a file system with the sysadmin program (see Chapter 6, "File
System Backups").
To format a floppy disk, follow these steps:

Insert a disk into floppy disk drive O. Make sure there is no readonly tab on the disk jacket.

Enter:
format /dev/device-name
and press the RETURN key. The program formats the disk.

Warning: The format command is machine-specific. Refer to the format
(C) manual page originally included in the XENIX InstallationGuide for
more information.
If you do not insert the disk properly into the drive, the program displays

an error message and stops.
In general, the system manager should format spare floppy disks in

advance. Note that formatting removes all data from the disk, so if you are
formatting a disk that already contains data, make sure that the data is
nothing you wish to save.
4.3 Permissions
Permissions control access to all the files and directories in a XENIX system. In XENIX, ordinary users may access those files and directories for
which they have permission. All other files and directories are inaccessible.
There are three different levels of permissions: user, group, and other.
User permissions apply to the owner of the file; group permissions apply to
users who have the same group ID as the owner; and other permissions
apply to all other users.

4-5

XENIX Operations Guide

4.3.1 DisplayingPennissions
You can display the permission settings for all the files in a directory with
the I (for "list directory") command. This command lists the permissions
along with the name of the file's owner, the size (in bytes), and the date and
time the file was last changed. The command display has the following format:
-rw-rw----ljohnd group 11515Nov1714:21filel
The permissions are shown as a sequence of ten characters at the beginning
of the display. The sequence is divided into four fields. The first field (the
"type" field) has a single character, the other fields ("user", "group", and
"other") have three characters each. The characters in the fields have the
following meanings.
In the type field:
d

Indicates the item is a directory
Indicates the item is an ordinary file

Indicates the item is a device special block I/O file

Indicates the item is a device special character I/O file

In the "user", "group", and "other" fields:
r

Indicates read permission. Read permission for a file means you
may copy or display the file. Read permission for a directory
means you may display the files in that directory.

Indicates write permission. Write permission for a file means you
may change or modify the file. Write permission for a directory
means you may create files or sub directories within that directory.

Indicates execute permission (for ordinary files) or search permission (for directories). Execute permission for a file means you
may invoke the file as you would a program. Execute permission
for a directory means you may enter that directory with the cd
command.
Indicates no permission.

For example, the permissions:
-rwxrwxrwx
indicate an ordinary file with full read, write, and execute access for everyone (user, group, and other).

4-6

Using File Systems

The permissions:
-rw------indicate an ordinary file with read and write access for the user only.
The permissions:
drwxr-x--x
indicate a directory with search access for everyone, read access for the
user and group, and write access for only the user.
When you create a file, the XENIX system automatically assigns the following permissions:
-rw-r--r-This means that everyone may read the file, but only the user may write to
it. When you create a directory, the system assigns the permissions:
drwxr-xr-x
This means everyone may search and read the directory, but only the user
may create and remove files and directories within it.
4.3.2 Changing Permissions
You can change the permissions of a file or a directory with the chmod (for
"change mode") command. This command requires that you tell it how to
change the permissions of a specific file or directory. You do so byindicating which levels of permissions you wish to change (user "u", group "g", or
other "0"), how you wish to change them (add "+" or remove ". "), and
which permissions you wish to change (read "r", write "w", or execute
"x"). For example, the pattern:
u+x
adds execute permission for the user. The pattern:
go-w
removes write permission for group and other.
The chmod command has the form:
chmod pattern file ...

4-7

XENIX Operations Guide

where file is the name of a file or directory. If more than one name is given,
they must be separated by spaces. For example, to change the permissions
of the file "receivables" from "-rw-r- -r- -" to "-rw- - - - - - -", enter:
chmod go-r receivables
Press the RETURN key.
After using chmod, use the I command to check the results. If you have
made a mistake, use chmod again to correct the mistake.
4.3.3 Changing the File Creation Mask
The file creation mask is a special number, kept by the system, that defines
the permissions given to every file and directory created by a user. Initially,
the mask has the value "022" which means every file receives the permissions:
-rw-r--r-Every directory receives the permissions:
drwxr-xr-x
You can change the mask and the initial permissions your files and directories receive byusingtheumaskcommand.
The umask command has the form:
umask value
where value is a three-digit number. The three digits represent user,
group, and other permissions, respectively. The value of a digit defines
which permission is given as shown by the following table:
Digit

Permission

Read and write (also execute for directories)
Read and write
Read (also execute for directories)
Read
Write (also execute for directories)
Write
Execute for directories
No permissions

1
2
3
4
5
6

17
4-8

Using File Systems

For example, the command:
umask 177
sets the file creation mask so that all files and directories initially have read
and write permission for the user, and no permissions for all others.
4.4 Managing File Ownership
Whenever a file is created by a user, the system automatically assigns "user
ownership" of that file to that user. This allows the creator to access the file
according to the "user" permissions. The system also assigns a "group
ownership" to the file. The group ownership defines which group may
access the file according to the "group" permissions. The group is the same
group to which the user who created the file belongs.
Only one user and one group may have ownership of a file at anyone time.
(These are the owner and group displayed by the I command.) However,
you may change the ownership of a file by using the chown and chgrp commands.
4.4.1 ChangingUserOwnership
You can change the user ownership of a file with the chown command.
The command has the form:
chown login- name file ...
where login- name is the name of the new user, and file is the name of the
file or directory to be changed. For example, the command:
chown johnd projects.june
changes the current owner of the file projects.june to "johnd".
The chown command is especially useful after changing the user ID of a
user account (see the section, "Changing a User's ID" in Chapter 3).
You must be logged in as the super-user to use this command.
4.4.2 Changing Group Ownership
You can change the group ownership of a file with the chgrp command.

4-9

XENIX Operations Guide

The command has the form:
chgrp group- name file
where group-name is the name of a group given in the Jete/group file and
files are the name of the file you wish to change. For example, the command:
chgrp shipping projects.june
changes the group ownership of the file projects. june to the group named
"shipping" .
The chgrp command is especially useful if you have changed the login
group of a user (see the section, "Changing a User's Login Group" in
Chapter 3).
4.5 System Security

Every system, no matter what its size, should have some form of protection
from unauthorized access to the computer, disks, and system files. The
following sections suggest ways for a system manager to protect the system.

4.5.1 Physical Security
You can protect the physical components of the computer, especially system disks, by taking these steps:
1. Keep unessential personnel out of the work area.
2.

Organize and lock up all floppy disks when not in use. They should
notbe stored with the computer itself.

3. Keep disks away from magnetism, direct sunlight, and severe
changes in temperature.
4.

Do not use ball point pens to write labels on disks.

5. Make backup copies of all floppy disks (see the section, "Copying
Floppy Disks," in this chapter).

4-10

Using File Systems

4.5.2 Access Security
You can protect the system from access by unauthorized individuals by
taking these steps:

1. Remind users to log out of their accounts before leaving the terminal.
2.

Discourage users from choosing passwords that are easy to guess.
Passwords should be at least six chara,cters long and include letters,
digits, and punctuation marks.

Keep the super-user password secret from all but necessary personnel.

4.5.3 Protecting Special Files
You can prevent ordinary users from gaining direct access to the data and
program files on the system's hard and floppy disks by protecting the
system's special files. The XENIX special files, in the Idev directory, are
used primarily by the system to transfer data to and from the computer's
hard and floppy disks, as well as other devices, but can also beused byordinary users to gain direct access to these devices.
Since direct access bypasses the system's normal protection mechanisms
and allows ordinary users to examine and change all files in the system, it is
wise to protect the special files to ensure system security.
To protect the XENIX special files, log in as the super-user and use the
chmod command to set appropriate permissions. For example, to disallow any access by ordinary users, set the permissions of such special files as
Idevlmem, Idevlkmem, Idevlroot, and Idevlusrto read and write access for
the user only. Note that you must not change the permissions for the
Idevltty files.
4.5.4 Copying Floppy Disks
To ensure against the loss of data stored on floppy disks, you can use the
diskcp(C) command, or the dd(C) command to make copies of floppy
disks on new, formatted disks.
diskcp makes use of dd and provides a simple interface to that program.
dd is very powerful, and you can use it to perform many different kinds of
copying.
You must copy information onto formatted disks. H you format floppies
under XENIX, you can use them over again without reformatting.

4-11

XENIX Operations Guide

If you have disks that have been formatted under another operating system, you must reformat them under XENIX before you can use them to
make copies of XENIX disks. Be aware that floppies formatted under
some operating systems cannot be used under other operating systems,
even with reformatting.

You can use the fonna t( C) command to format floppies. This command is
described in the section "Formatting Floppy Disks" in this chapter. The
diskcp can also format floppies for you. This is discussed in the next steps.
To copy a floppy disk using dis kcp:
1. Insert the disk you want to copy, also known as the source floppy, in
drive 0, your primary floppy drive.
2. Insert another floppy in the other drive. This floppy is also known
as the target disk. Note that any information already on the target
disk will be destroyed.
If you have only one disk drive, leave the source floppy in the drive.
diskcp will prompt you to remove the source disk at the correct

time.
3. To format the floppy disk before the image is copied, enter the command:
diskcp -f
and press RETURN.
If your computer has dual floppy drives. Enter the following com-

mand to copy the image directly on the target floppy:
diskcp -d
and press RETURN.
If you do not need to format the target floppy, simply enter:

diskcp
and press RETURN.
4. Follow the instructions as they appear on your screen. Note that
with a single drive system, you are prompted to remove the source
disk and insert the target disk.

4-12

Using File Systems

To copy a disk usingdd, follow these steps:

1. Insert the disk to be copied into floppy drive O.
2. Insert a formatted disk into drive 1. If necessary, you can format a
disk with the fonnat command described in "Fonnatting Floppy
Disks" in this chapter.
3. Enter:
dd if=/dev/fdO of=/dev/fd1 count=blkcount
and press the RETURN key. The blkcount is the number of blocks
on the disk to be copied (see Appendix A for details).
This command copies the first disk to the second, then displays a record of
the number of blocks copied.
4.6 Using XENIX Accounting Features
The XENIX system provides a set of commands that allow the system
manager to perform process accounting. Process accounting is a simple
way to keep track of the amount of time each user spends on the system.
The process accounting commands keep a record of the number of
processes (i.e., programs) started by a user, how long each process lasts,
and other information such as how often the process accesses I/O devices,
and how big the process is in bytes.
Process accounting is helpful on systems where users are being charged for
their access time, but it may also be used to develop a detailed record of
system, command, and system resource usage.
There are several commands which maybe used to do process accounting.
Of these, the most useful are accton and acctcom. The accton command
starts and stops process accounting. When invoked, the command copies
pertinent information about each process to the file named
/usr/adm/pacct. The acctcom command is used to display this information. The command has several options for displaying different types of
accounting information.
4.6.1 Starting Process Accounting
Process accounting can be started at any time, but is typically started when
the system itself is started. You can start process accounting with the accton command. Enter:
accton /usr/ adm/pacct

4-13

XENIX Operations Guide

The command automatically creates a new file /usr/adm/pacct and begins
to copy process accounting information to it. If the /usr/adm/pacct file
exists before starting accton, the file contents are deleted.
You can start process accounting automatically whenever you reboot the
system. To do this, edit the system startup file /etclrc. Among other commands, there are several that start up process accounting, as well as backup
the accounting log file /usr/adm/pacct.
These commands are commented out, but if you remove the comment
characters at the beginning of those lines, the commands are executed
everytime you reboot the system. Make these lines in /etclrc:

# mv lusr/adm/pacct /usr/adm/opacct
# > /usr/adm/pacct ; chmod 644 /usr/adm/pacct
# [ -x /etc/accton ] && letc/accton /usr/adm/pacct
look like this:
mv lusr/adm/pacct /usr/adm/opacct
> /usr/adm/pacct ; chmod 644 /usr/adm/pacct
[ -x letc/accton ] && letc/accton /usr/adm/pacct
Note that when you start the system afterediting/etclrc, the contents of the
/usr/adm/pacct file is saved in the file /usr/adm/opacct overwriting the
contents of /usr/adm/opacct.
4.6.2 Displaying Accounting Infonnation
The acctcom command reads processing accounting information from the
/usr/adm/pacct file by default, then displays selected information on your
terminal screen. The command usually displays basic accounting inform ation, such as the process's program name, the name of the user who
invoked the process, the start and stop times for the process, and the
number of execution seconds in real time and CPU time. The command
has several options that can be used to display selected information.
To display the average size of each process, enter:
acctcom
The command displays the basic information plus the average size of each
process.
To displaybasic accounting information about a specific command, enter:
acctcom -n command

4-14

Using File Systems

where command is the name of the command you are interested in. The
command responds by displaying each entry for the specified command.
For example, to display each entry for the system command, enter:
acctcom -n units
displays each entry for the system command units.
To display information about the number and size of input and output
counts, enter:
acctcom -i
The command displays basic program information plus the number of
characters and blocks transferred or read by each program.
To display information about a program's use of system resources, enter:
acctcom -h
The command displays the basic information plus the "use factor." The
use factor is a number generated and used by the system to determine how
each process should be scheduled for execution. Processes with high use
factors use a high percentage of the system resources and are therefore
scheduled after processes with lower factors.

4-15

ChapterS
Maintaining File SystelDs
5.1

Introduction

5-1

5.2

Maintaining Free Space 5-1
5.2.1 Strategies for Maintaining Free Space 5-1
5.2.2 Displaying Free Space 5-2
5.2.3 SendingaSystem-WideMessage 5-2
5.2.4 Displaying Disk Usage 5-3
5.2.5 Displaying Blocks by Owner 5-3
5.2.6 Mailing a Message to a User 5-4
5.2.7 Locating Files 5-4
5.2.8 Locating core and Temporary Files 5-5
5.2.9 Clearing Log Files 5-5
5.2.10 Expanding the File System 5-6

5.3

File System Integrity 5-6
5.3.1 Repairing the File System 5-7
5.3.2 Automatic File System Check 5-7

- 5-i-

Maintaining File Systems

5.1 Introduction
File system maintenance, an important task of the system manager, keeps
the XENIX system running smoothly, keeps the file systems clean, and
ensures adequate space for all users. To maintain the file systems, the system manager must monitor the free space in each file system, and take
corrective action whenever it gets too low.
This chapter explains the file system maintenance commands. These commands report how much space is used, locate seldom-used files, and
remove or repair damaged files.
5.2 Maintaining Free Space
The XENIX system operates best when at least 15% of the space in each file
system is free. In any system, the amount of free space depends on the size
of the disk containing the file system and the number of files on the disk.
Since all disks have a fixed amount of space, it is important to carefully
control the number of files stored on the disk.
If a file system has less than 15% free space, system operation usually
becomes sluggish. If no free space is available, the system stops any
attempts to write to the file system. This means that the user's normal work
on the computer (creating new files and expanding existing ones) stops.

The only remedy for a file system which has less than 15% free space is to
delete one or more files from the file system. The following sections
describe strategies for keeping the free space available.
5.2.1 Strategies for Maintaining Free Space
The system manager should regularly check the amount of free space of all
mounted file systems and remind users to keep their directories free of
unused files. You can remind uSers by including a reminder in the message
ofthedayfileletclmotd. (Seethe section, "Changingtheletc/motd File"
in Chapter 8).

5-1

XENIX Operations Guide

If the amount of free space slips below 15%, the system manager should:

1. Send a system-wide message asking users to remove unused files.
2.

Locate exceptionally large directories and files, and send mail to the
owner asking him to remove unnecessary files.

Locate and remove temporary files and files named core.

Clear the contents of system log files.

Finally, if the system is chronically short of free space, it maybe necessary
to create and mount an additional file system.
5.2.2 Displaying Free Space
You can find out how much free space exists in a particular file system with
the df (for "disk free") command. This command displays the number of
"blocks" available on the specific file system. A block is 512 characters (or
bytes) of data.
The df command has the form:
df specialjile
where specialjile can be the name ofaXENIX special file corresponding to
the disk drive containing the file system (see Appendix A, "XENIX Special
Device Files"). If you do not give a special filename, then the free space of
all normally mounted file systems is given.
For example, to display the free space of the root file system Idevlroot,
enter:
df Idev/root
and press the RETURN key. The command displays the special filename
and the number of free blocks. You may compute the percentage of free
space by comparing the displayed value with the total number of blocks in
the file system. See A ppendix A, "XENIX Special Device Files," for a list
of the total blocks.
5.2.3 Sending a Sys tern- Wide Mes sage
If free space is low, you may send a message to all users on the system with
the wall (for "write to all") command. This command copies the messages
you enter at your terminal to the terminals oia11 users currently logged in.

5-2

Maintaining File Sys terns

To send a message, enter:
wall
and press the RETURN key. Enter the message, pressing the RETURN key
to start a new line if necessary. After you have entered the message, press
Ctrl-d. The command displays the message on all terminals in the system.
To leave the wall command, press Ctrl-d. This removes the link to other
terminals.
5.2.4 Displaying Disk Usage
You can display the number of blocks used within a directory by using the
du command. This command is useful for finding excessively large directories and files.
The du command has the form:
du directory
The optional directory must b~ the name of a directory in a mounted file
system. If you do not give a directory name, the command displays the
number of blocks in the current directory.
For example, to display the number of blocks used in the directory
lusr/johnd, enter:
du /usr/johnd
and press the RETURN key. The command displays the name of each file
and directory in the lusrljohnd directory and the number of blocks used.
5.2.5 Displaying Blocks by Owner
You can display a list of users and the number of b locks they own by using
the quot (for "quota") command. The command has the form:
quot specialjile
The specialjile must be the name of the special file corresponding to the
disk drive containing the file system (see Appendix A, "XENIX Special
Devices Files").
For example, to display the owners of files in the file system mounted on
the disk drive / devlfdl, enter:
quot /dev/fdl

5-3

XENIX Operations Guide

and press the RETURN key. The command displays the users who have
files in the file system and the number of b locks in these files.
5.2.6 Mailing a Message to a User
If a particular user has excessively large directories or files, you may send a
personal message to the user with the mail command.

To begin sending a message through the mail, enter:
mail login- name
and press the RETURN key. The login- name must be the login name of the
recipient. To send a message, enter the message, press the RETURN key,
and then press Ctrl-d. If the message has more than one line, press the
RETURN key at the end of each line. The mail command copies the message to the user's mailbox, where he mayview it also by using the mail command. See the XENIX User's Guide for details.
5.2.7 Locating Files
You may locate all files with a specified name, size, date, owner, and/or
last access date by using the find command. The command is useful for
locating seldom - used and excessively large files.
The find command has the form:
find directory parameters
The directory must be the name of the first directory to be searched. (It will
also search all directories within that directory.) The parameters are special names and values that tell the command what to search for (see find
(C) in the XENIX Reference Manual for complete details). The most useful
parameters are:
-name file
-atime number
-print
The -name parameter causes the command to look for the specified file.
The - atime parameter causes the command to search for files which have
not been accessed for the number of days. The - print parameter causes the
command to display the locations of any files it finds.

5-4

Maintaining File Systems

For example, to locate all files named core in the directory lusr, enter:
find lusr -name core -print
and press the RETURN key. The command displays the locations of all files
it finds.
5.2.8 Locating core and Temporary Files
You can locate core, and temporary files with the find command.
A core file contains a copy of a terminated program. The XENIX system
sometimes creates such a file when a program causes an error from which it
cannot recover. A temporary file contains data created as an intermediate
step during execution of a program. These files may be left behind if a program contained an error or was prematurely stopped by the user. The
name of a temporary file depends on the program that created it.
In most cases, the user has no use for either core or temporary files, and

they can be safely removed.
When searching for core or temporary files, it is a good idea to search for
files which have not been accessed for a reasonable period of time. For
example, to find all core files in the lusr directory which have not been
accessed for a week, enter:
find lusr -name core -atime +7 -print
and press the RETURN key.
5.2.9 Clearing Log Files
The XENIX system maintains a number of files, called log files, that contain information about system usage. When new information is generated,
the system automatically appends this information to the end of the
corresponding file, preserving the file's previous contents. This means the
size of each file grows as new information is appended. Since the log files
can rapidly become quite large, it is important to periodically clear the files
by deleting their contents.
You can clear a log file by entering:
cat < /dev/null > filename

5-5

XENIX Operations Guide

where filename is the full pathname of the log file you wish to clear. A log
file normally receives information to be used by one and only one program,
so its name usually refers to that program. Similarly, the format of a file
depends on the program that uses it. See Appendix B, "XENIX Files and
Directories," for descriptions of the log files.
In some cases, clearing a file affects the subsequent output of the
corresponding program. For example, clearing the file letc!ddate forces
the next backup to be a periodic backup (see Chapter 6, "Backing Up File
Systems").

5.2.10 Expanding the File Sys tern
If free space is chronically low, it maybe to your advantage to expand the

system's storage capacity by creating and mounting a new file system. Once
mounted, you may use this new file system for your work, or even copy user
or system directories to it.
A chronic shortage of space usually results from having more users on the
system than the current hard disk can reasonably handle, or having too
many directories or files. In either case, creating a new file system allows
some of the users and directories to be transferred from the hard disk, freeing a significant amount of space on the existing file system and improving
system operation. For details about creating and mounting file systems,
see Chapter 4, "Using File Systems."
5.3 File System Integrity
Since file systems are normally stored on hard and floppy disks, occasional
loss of data from the file system through accidental damage to the disks is
not unusual. Such damage can be caused by conditions such as an
improper system shutdown, hardware errors in the disk drives, or a worn
out disk.
Such damage usually affects one or two files, making them inaccessible. In
very rare cases, the damage causes the entire file system to become inaccessible.
The XENIX system provides a way to restore and repair a file system if it has
been damaged. The fsck (for "file system check") command checks the
consistency of file systems and, if necessary, repairs them. The command
does its best to restore the information required to access the files, but it
cannot restore the contents of a file once they are lost. The only way to
restore lost data is to use backup files. For details about backup disks, see
Chapter 6, "Backing Up File Systems."

5-6

Maintaining File Systems

5.3.1 Repairing the File System
You can repair a file system with the fsck command. The command has the
form:
fsck speciaZfiZe
The specialfiZe must be the name of the special file corresponding to the
disk drive containing the file system (see Appendix A, "XENIX Special
Device Files").
For example, to check the file system on the disk in the disk drive Idevlfdl,
enter:
fsck Idev/fd1
and press the RETURN key. The program checks the file system and
reports on its progress with the following messages.

** Phase 1- Check Blocks and Sizes
** Phase 2 - Pathnames
** Phase 3 - Connectivity
** Phase 4 - Reference Counts
** Phase 5 - Check Free List
If a damaged file is found during anyone of these phases, the command
asks if it should be repaired or salvaged. Enter y to repair a damaged file.
You should always allow the system to repair damaged files even if you have
copies of the files elsewhere or intend to delete the damaged files.

Note that the fsck command deletes any file that it considers too damaged
to be repaired. If you suspect a file system problem and wish to try to save
some of the damaged file or files, check other possible remedies before you
invoke the command.
5.3.2 Automatic File System Check
The XENIX system sometimes requests a check of the file system when you
first start it. This usually occurs after an improper shutdown (for example,
after a power loss). The file system check repairs any files disrupted during
the shutdown. For details, see the section "Cleaning the File System" in
Chapter 2.

5-7

Chapter6
Backing Up File SystelDs
6.1

Introduction

6-1

6.2

TheSysinfoAccount 6-1

6.3

Strategies for Backups 6-1

6.4

Using the sysadmin Program 6-3
6.4.1 Creating Backups 6-3
6.4.2 Getting a Backup Listing 6-4
6.4.3 Restoring a Backup File 6-5

6.5

Using the tar Command 6-6
6.5.1 CopyingFilestoatarDisk 6-6
6.5.2 Restoring Files From a tar Disk 6-7

- 6-i-

Backing Up File Systems

6.1 Introduction
A file system backup is a copy, on floppy disk, of the files in the root directory and other regularly mounted file systems. A backup allows the system
manager, when logged in as root or sysinfo to save a copy of the file system
as it was at a specific time. The copy may be used later to restore files that
are accidentally lost or temporarily removed from the file system to save
space.
This chapter explains how to create backups of the root directory and
other file systems, and how to restore files from the backups.
6.2 The Sysinfo Account
Always use the sysinfo account whenever you make or restore backups.
This is because:
•

You should always perform backups using the same user and group
ID,and;

•

sysinfo has restricted root permissions for backups.

If you try to create backups as an ordinary user, you do not have access permissions for all files. If you make backups as root you may accidentally
destroy files because root can do amything at all.

The sysinfo account solves this dilemma by having restricted root permissions. The sysinfo user can read all files but may overwrite only those
owned by sysinfo.
The sysinfo account is already set in /etc/passwd. Only root can become
sysinfo, and only then using the su(C) command. No one may log in as
sysinfo.
6.3 Strategies for Backups
The system manager should back up the root directory (and any other
mounted file systems) on a regular basis. In particular, the manager should
make daily copies of all files modified during the day, and should make
periodic (e.g., weekly) copies of the entire root directory and other
mounted file systems.
The XENIX system offers three ways to back up file systems, the sysadmin
program and the tar and cpio commands.
The sysadmin program is a formal maintenance program for systems that
require a rigorous schedule of file system backups. The program automatically locates modified files, copies them to backup media, and optionally
6-1

XENIX Operations Guide

produces a list of the files. H your system has many users and a large
number of files that are modified daily, use sysadmin to make regular backups.
The tar command is useful on systems with one or two users, or on any system where ordinary users wish to make personal copies of their directories
and files. The command lets the system manager or user choose the files
and directories to be copied. The command does not, however, automatically locate modified files.
The cpio command is similar to the tar command. Refer to cpio(C) in the
XENIX Reference.
A typical backup schedule includes a daily backup once a day and a
periodic backup once a week. A daily backup copies only those files
modified during that day; a periodic backup copies all files in the file system. The appropriate schedule for a system depends on how heavily the
system is used, and how often files are modified. In all cases, a periodic
backup should be done at least once a month.
The system manager should schedule backups at times when few (if any)
users are on the system. This ensures that the most recent version of each
file is copied correctly.
A regular schedule of backups requires a large number of floppy disks and
adequate storage for the disks. Daily backups should be saved at least two
weeks; periodic backups should be saved indefinitely. Disks should be
properly labeled with the date of the backup and the names of the files and
directories contained in the backup. After a backup has expired, the disk
may be used to create new backups.

Note

H the number of floppies needed for making backups grows too
large, the system manag~r can use the backup command instead of
sysadmin. backup is called by sysadmin and by using backup
directly, the system administrator can tailor the number of floppies
used to fit the needs of the individual site. Refer to backup(C) in the
XENIX Reference.

6-2

Backing Up File Systems

6.4 Using the sysadmin Program
The sysadmin program performs daily and periodic backups, lists backup
files, and restores individual files from backup disks. The program
presents each task as an item in a menu. To perform a task, simply choose
the appropriate item from the men u and supply the required information.
6.4.1 Creating Backups
To create backups with the sysadmin program, you need several formatted
floppy disks. The exact number depends on the number of files to be
copied; for example, some periodic backups require as many as nine disks.
For details on how to format a floppy disk, see the section "Formatting
Floppy Disks" in Chapter 4.
To create a backup, follow these steps:
1. Login as the super-user.

2. Enter:
sysadmin
and press the RETURN key. The program displays a file system
maintenance menu.
File System Maintenance
Type 1 to do daily backup
2 to do a periodic backup
3 to get a backup listing
4 to restore a file
5toquit
3. Enter 1 for a daily backup or 2 for a periodic backup. Then press the
RETURN key. Note that if the system has never had a periodic
backup, it automatically performs one, even if you have chosen a
daily backup.
4.

Insert a floppy disk in drive 1, wait for the drive to accept the disk
(all drive noise should stop), and press the RETURN key. The system displays the current date and the date of the last backup (it
displays "the epoch" if there has been no backup). The system then
begins to copy files to the floppy disks. If the disk runs out of space,
the program displays the message:
Change volumes

6-3

XENIX Operations Guide

5. Remove the first disk and insert a new disk. Wait for the drive to
accept the disk, then press the RETURN key. The program continues to copy files to the new disk. Repeat this step until the program
displays the message:

DONE
When doing a periodic backup, you may need to repeat the last step several
times before the backup is complete. You should label each disk as you
remove it from the disk drive. For example, label the first disk "Volume
1", the second "Volume 2", and so on.
6.4.2 Getting a Backup Listing

You can keep a record of the files you have backed up by invoking the
sysadmin program and selecting the third item in the menu. The program
copies the names of all files from the backup disks to the temporary file
Itmplbackup.list. This listing is especially convenient if you keep detailed
records of the files copied in each backup. The backup listing is available
after every daily or periodic backup.
To get the listing, follow these steps:

1. Login as the super-user.
2.

Enter:
sysadmin
and press the RETURN key. The program displays the system
maintenance menu.

3. Enter 3 and press the RETURN key. The program prompts you to
reinsert the backup disks in the same order that you inserted them
during the backup.
4.

Insert the first disk, wait until the drive accepts the disk, then press
the RETURN key. The program automatically reads the filenames
off the backup disk and places them in the list file. When the program has read all the names, it asks for the next disk.

5. Remove the first disk and insert the next. Wait for the drive to
accept the disk and press the RETURN key. Repeat this step until all
disks have been read.

6-4

Backing Up File Systems

You may produce a printed copy of the backup list by printing the list at the
lineprinter. Enter:
Ipr /tmp/backup.list
and press the RETURN key. To save space after printing the file, you
should remove it from the Itmp directory with the rm command.
6.4.3 Restoring a Backup File
You can restore files from the backup disks by invoking the sysadmin program and selecting the fourth item in the menu. You will need the complete set of backup disks containing the latest version of the file you wish to
restore. You will also need the "full pathname" of the file you wish to
restore. This is the name given for the file in the backup listing.
To restore a file, follow these steps:
1. Login as the super-user.
2.

Enter:
sysadmin
and press the RETURN key. The program displays the file system
maintenance menu.

3. Enter 4 and press the RETURN key. The program prompts you to
enter the full pathname of the file you wish to restore.
4.

Enter the pathname and press the RETURN key. The program
prompts for anotherpathname.

5. Repeat step 4 to enter another pathname, or press the RETURN key
to continue the program. If you press the RETURN key, the program prompts you to insert the first disk in the backup set.
6.

Insert the first disk in the set ofbackup disks (volume 1), wait for the
drive to accept the disk, and press the RETURN key. The program
displays the inode numbers of the files you have given, then prompts
for the volume number ofthe backup disk containing the files.

Insert the disk having the correct volume number, enter the volume
number, and press the RETURN key. The program searches the
disk for the specified files. If found, the files are copied to your
current directory. IT not found, the program prompts for the next
volume.

6-5

XENIX Operations Guide

Repeat step 7 until all files have been found and copied.

The sysadmin program does not restore the file's original name. Instead, it
names the file a unique number called an "inode" number. You can
restore the file's original name using the mv (for "move") command:
mv inode filename

inode is the name given to the file by sysadmin. filename is the new name
you want for the file.
For example, to restore a file
lusrljohndlprojects.june from 224, enter:
mv 224 lusr/johnd/projects.june

6.5 Using the tar Command

The tar command copies specified files and directories to and from floppy
disks. On systems with one or more users, it gives the system manager a
direct way to make backup copies of the files modified during a day. On
systems with many users, it gives ordinary users a way to make personal
copies of their own files and directories.
6.5.1 Copying Files to a tar Disk

You can copy a small number of files or directories to a floppy disk with the
tar command. The command has the form:
tar cvf specialjile files
The specialfile must be the name of the special file corresponding to a disk
drive (see Appendix A, "XENIX Special Device Files"). The drive must
contain a formatted disk. The files are the names of the files or directories
you wish to copy.
To use the tar command, you need a formatted floppy disk and the names
of the files and/or directories you wish to copy. For details about how to
format a disk, see the section "Formatting Floppy Disks" in Chapter 4. If
you give a directory name, the command copies all files in the directory
(including subdirectories) to the disk.

6-6

Backing Up File Systems

For example, to copy the files a, b, and c to the disk in the disk drive
Idevlfdl, enter:
tar cvf Idev/fdl abc
and press the RETURN key.
6.5.2 Restoring Files From a tarDisk
You may also use the tar command to restore files from a disk. The command simply copies all files on the disk to your current directory. In this
case, the command has the form:
tar xvf speciaZjiZe
The speciaZjiZe must be the name of the special file corresponding to the
disk drive containing the tar disk.
For example, to restore files from the disk in the drive Idevlfdl, enter:
tar xvf I devlfdl
and press the RETURN key. The command copies files on the disk in the
drive to the current directory.
Since the tar command copies files only to the current directory, make sure
you are in the desired directory before you invoke the command. You can
change to the desired directory with the cd command.

6-7

Chapter7
Using Peripheral Devices
7.1

Introduction 7-1

7.2

Using Multiscreen

7.3

Adding a Terminal 7-2

7-1

7.4 SettingTerminal Lines 7-3
7.4.1 The gettydefs File 7-3
7.4.2 Changing the gettydefs File 7-5
7.4.3 Checking the Terminal Settings 7-7
7.5

Changing Serial Line Operation 7-7

7.6 Setting the Terminal Type

7-9

7.7 Removing a Terminal 7-10
7.8 Configuring Serial Ports 7-11
7.9 Setting Up a Serial Console 7-12
7.10 Modem UsageunderXENIX 7-13
7.10.1 Serial Lines 7-13
7.10.2 Dialing Out From Your Computer 7-13
7.10.3 Dialing Into Your Computer Under XENIX
7.10.4 Shared Dial-In/Dial-Out 7-16
7.10.5 Hayes Modem Settings 7-16
7.10.6 Modem Control 7-18

7-16

7.11 Adding a Lineprinter 7-18
7.11.1 Installing a Printer: lpinit 7-19
7.11.2 Stopping the Print Spooling Daemon: lpsched 7-22
7.11.3 CreatinganInitDeviceFile 7-23
7.11.4 Moving Requests Between Printers: lpmove 7-24
7.11.5 A ccepting and Rejecting Print Requests: accept 7 -25
7.11.6 Enabling and Disabling Printers 7-26
7.11. 7 Prin ter In terface Programs 7- 26
7.12 Adding Additional Memory 7-28

7.13 AddingaHardDisk 7-30
7.13.1 Mounting Another File system 7-37
7.13.2 UsingA Second File System 7-38
7.14 Creating Boot and Root Floppy Disks

7-40

Using Peripheral Devices

7.1 Introduction
One important task of the system manager is to add peripheral devices
such as terminals, hard disks, and lineprinters to the system. Adding these
devices lets more users access the system, gives extra storage space for
user's files and directories, and adds to the system's overall capabilities.
To add a peripheral device, the system manager must make the physical
connection between the device and the computer, then use the correct system commands to enable the device for operation. This chapter explains
how to do this and how to maintain the devices once they are added.
Note that all physical connections between a device and the system are
device-dependent. For information about these connections, see the
hardware manual provided with the device and your computer.
7.2 Using Multiscreen
The multiple screen feature uses the console and Idevltty[02 ... 10] device
files. These device files provide character I/O between the system and the
computer's screen and keyboard. The actual number of multiscreens
available depends upon the amount of memory in your personal computer
and is displayed when the system boots. There are generally between two
and sixmultiscreens enabled.
Each multi screen (device file) is independent of the rest, so you can log in
and run programs on each screen. Output from programs is saved in a
screen buffer, and when you switch back to a screen, you see the latest
screenfull of output. If you stop output to a screen, for example by entering Ctl-s, this affects only that screen. Output continues on all the other
screens.
Although all of the multiscreens may be open and active at the same time,
only one can be seen at any given time. The selected multiscreen is the terminal currently "connected" to the keyboard. Rotate through the screens
by pressing Ctrl-PrtSc (using the Ctrl key and the PrtSc key. Any active
screen may be selected by pressing alt- Fn where Fn is one of the ten function keys on the far left side of the keyboard. For example, entering:
alt-F6
switches you to screen 6, corresponding to Idev Itty 06. Refer to the XENIX
Reference for more on multiscreen(HW) and console(M).
Note that error messages from the kernel appear on the console screen. In
such cases, the console screen displays instead of the current screen.

7-1

XENIX Operations Guide

The system displays the number of multiscreens available on boot. This
number is determined by the amount of memory in your computer. Do not
try to use more than the auto-configured number of screens.

7.3 Adding a Terminal
You can give two or more users simultaneous access to the system by
adding extra terminals. You can add a terminal by connecting it to an RS232 serial line on the system and enabling it with the enable(C) command.
Many different terminals work well with the XENIX operating system. A
short list of recommended models is given in terminals (M) in the XENIX
Reference Manual.
Before you add a terminal, you must know how to connect the terminal to a
serial line on the computer. You also need to know the name of the serial
line. Physical connections for the terminal are usually explained in the
terminal's hardware manual. The names of the system's available serial
lines are given in Appendix A, "XENIX Special Device Files." Once a terminal has been connected, you may then enable the terminal for use with
the enable command.
To add a terminal, follow these steps:
1. Using the recommended procedure in the terminal's hardware
manual, connect the terminal to one of the computer's RS-232
serial lines. Make sure that the terminal is compatible with the line
configuration.
2.

For multi-port expansion cards, you must use the mkdev(C) program to create more than the default number of ports. See
mkdev(C) in theXENIXReferenceManual.

3. Login as the super-user.
4.

Use the enable command to enable the terminal. The command
has the form:
enable specialjile
where specialjile is the name of the serial line to which the terminal is
attached. This name depends on your system's configuration (see
Appendix A, "XENIX Special Device Files"). For example, the
command
enable Idev/ttyla
enab les the terminal connected on serial line / dev / tty la.

7-2

Using Peripheral Devices

5. Turn on the power to the terminal and press the RETURN key
several times. The system should display a "login:" message. When
it does, you may log in and begin work.
If no "login:" message appears on the screen, if random characters

appear, or if the terminal does not respond to your attempt to log in, you
may need to change the baud rate (or line speed) of the terminal to match
the serial line. You can change the baud rate with the stty(C) command
described in the next section.
When using the enable command, make sure that you wait a full minute
between each use of the command. Failure to do so can cause a system
crash.
7.4 Setting Terminal Lines
Your XENIX system can adapt itself to several different terminal baud rates
and settings. The same program that displays the login message, getty(C),
reads these terminal line values from a table, trying each setting until one is
successful, and the user can log in to the system. This table provides
several default settings for different kinds of terminals lines.
On your XENIX system, getty automatically executes as part of the login
process. The table of terminal settings is found in a file called
letc!gettydefs. You can edit gettydefs to add different sets of terminal
characteristics or to change the existing ones.
7.4.1 The gettydefs File
The file letc!gettydefs contains the information that getty uses to set up terminalline characteristics such as baud rate. The file is in the form of a
table. Each table entry is divided into five fields. These fields include:
label# initial-flags # final-flags #
login- prompt #next-label[#login program]

where:
label

Identifies the gettydefs entry to getty. This could be a
number or a letter. label corresponds to the line mode
field in letc!ttys. init passes the line mode to getty as
an argument.

in itia 1- flags

Sets terminal line characteristics when getty first
establishes the connection. getty recognizes the flags
listed in tty(M), XENIX Reference Manual. Often the
only flag in this field is the one setting the baud rate.
For example, B300 would set the speed to 300.

7-3

XENIX Operations Guide

final- flags

Sets the terminal line characteristics just before getty
executes login. These flags describe the operating
characteristics for the line. The baud rate (B) is set
again. Other common flags include SANE (a composite flag that sets a number of terminal characteristics
to reasonable values), TAB3 (expands tabs with
spaces), IXANY (enables any character to restart
output), and HUPCL (hangs up line on final close).
Flags can be entered in any order.

Contains the login prompt message that greets users.
This field is printed exactly as it is entered including
spaces and tabs. The '@' in the login-prompt field is
expanded to the first line in the file fetclsystemid
(unless the '@' is preceded by a '\').
Several character sequences are recognized, including:
\n
\r
\v
\nnn

next-label

Line feed
Carriage return
Vertical tab
(3 octal digits)
The specified
ASCII characters

\t
\f
\b

Tab
Form feed
Backspace

Identifies the next label in gettydefs for getty to try if
the current one is not successful. getty tries the next
label if a user presses the BREAK key while attempting
to log in to the system. Groups of entries, such as
dial-up or TTY lines, should form a closed set so that
getty cycles back to the original entry if none of the
entries is successful.

login- program The name of the program which actually logs users
onto XENIX. The default program is fetcllogin.
If preceded by the keyword "A UTO," getty does not
prompt for a username, but instead uses its first argument as the username and immediately executes the
login- program

Each field is separated by pound sign (#), and each entry in gettydefs is
separated by a blank line.

7-4

Using Peripheral Devices

An entry in gettydefs might look like this:
4# B1200 # B1200 SANE TAB3 HUPCL #Login: #2#A UTO

The number 4 identifies this entry to getty. In the next field, the baud rate is
set to 1200. The final settings in the third field include the baud rate
(B1200), SANE (a composite flag for a number of characteristics), and
HUPCL (hangs up line on final close). The login prompt appears as
"Login:", and if this setting is not successful, getty proceeds to label 2 in
gettydefs. AUTO attempts to log in the user "Idevlconsole (or other tty)"
executing letcllogin.
If the last entry also contains a filename, that login program is executed.

(Note that the filename and the corresponding login program are user
created.) For example, including a file such as lete!diaLJogin for a line connected to a modem can be used. It would set the user ID, acquire a password, validate the user, and then become the user. It could possibly
require a password for the system in addition to an account password and
even have a special set of login environment variables included in
lete!defaultl diaLJogin.
7.4.2 Changing the gettydefs File
The file letclgettydefs already exists on your XENIX system and has sets of
entries for the operator's console, dial-up lines, and terminal lines. These
different sets correspond to line mode settings in letclttys. The init program passes the line mode as an argument to getty.
You can edit gettydefs to add new terminal settings or to change existing
ones. For example, the settings for terminal lines on your XENIX system
might look like this:

1# B2400 # B2400 SANE IXANY TAB3 #@!login: #2
2# B4800 #B4800 SANE IXANY TAB3 #@!login: #3
3# B9600 # B9600 SANE IXANY TAB3 #@!login: #1
To change the sample gettydefs file so that the first baud rate getty attempts
is 1200, do the following:
1. En ter a text editor to edit the first line of the file gettydefs.
2.

Change the second and third fields from B2400 to B1200.

7-5

XENIX Operations Guide

3. Exit the text editor, savinggettydefs.
The sample file should look like this:

1# B1200 # B1200 SANE IXANY T AB3 #@!login: #2
2# B4800 #B4800 SANE IXANY TAB3 #@!login: #3
3# B9600 # B9600 SANE IXANY T AB3 #@!login: #1

You can also add additional terminal line settings to gettydefs. Flags and
permissible values for terminal settings are listed in tty (M), XENIX
Reference Manual.
When you add a new entry, be sure that the groups of entries in gettydefs
form a closed set, so the next-label field of the last entry directs getty back
to the first entry in the group.
To add an entry for a baud rate of 300 to the precedingsamplegettydefsfile,
follow these steps:
1. Enter a text editor to edit the file letclgettydefs.
2.

Locate the point where you want to insert the new settings for gettydefs. The order of the entries does not matter; getty only looks for
the label. In this example, the new entry will be the last entry in the
file.

3. Insert a carriage return after the last line in the file and enter the following on a newline:
4# B300 # B300 SANE IXANY TAB3 #@!login: #1
4. To incorporate label 4 into the set of labels, change the next label
field for entry 3 to 4:
3# B4800 # B4800 SANE IXANYTAB3 #@!1ogin: #4
getty is now directed from label 3 to 4, and then back to 1.
5. EJlit the text editor> saving the revised gettydefs file.

7-6

U sing Peripheral Devices

The new gettydefs looks like this:

1# B1200 # B1200 SANE IXANY TAB3 #@!login: #2
2# B4800 #B4800 SANE IXANY TAB3 #@!login: #3
3# B9600 # B9600 SANE IXANY TAB3 #@!login: #4
4# B300 # B300 SANE IXANY TAB3 #@!login: #1

7.4.3 Checking the Tenninal Settings

Each time you change the terminal line settings or add new entries to gettydefs, you should check to make sure that the new values that make sense
to getty. To do this you use the command getty with the check option, -c,
and the filename.
For example, to checkgettydefs, enter:
getty -c letc/gettydefs
If any of the values and settings in gettydefs are not permitted, getty - c

displays them on your terminal screen.
For more information on getty and gettydefs, see getty(M) and
gettydefs (F), XENIX ReferenceMan ual.
7.5 Changing Serial Line Operation

Whenever you enable a terminal with the enable command, the system
automatically sets the operating characteristics of the serial line to a set of
default values. Sometimes these values do not match the values used by
the terminal and, therefore, must be changed to allow communication
between the system and the terminal. You can display and change the
operating characteristics of a serial line with the stty (for "set tty") command.

7-7

XENIX Operations Guide

You can display the current operating characteristics of a serial line by
entering:
stty
at the terminal connected to that line. If it is impossible to log in at that terminal, you may use another terminal to display the characteristics. Log in
as the super-user at another terminal, and enter:
stty :
cu -s2400 -1 tt)i1a dir
Next, enter the following commands to configure the modem. They will be
saved in the modem's non -volatile memory. If you do not want to save the
settings, do not enter the last command (at&w). Commands are in the left
column and short descriptions ofwhattheydo are in the right column. Follow each command with a RETURN:
at&f

Fetch factory configuration.

att

Tone dialing.

atlO

Low speaker volume.

at&d2

Set dtr "2": go on hook when dtr drops.

at&c1

Set dcd "I": dcd tracks remote carrier.

ats0=1

Answer phone after 1 ring (AA light should
come on).

7-17

XENIX Operations Guide

ateO

No echo (modem will no longer echo what is
sent to it).

atq1

Quiet mode (modem will not respond with
"OK" after this command or any that follow).

at&w

Saves settings in non -volatile memory.

Exit from cu by entering a "tilde" and a "period" , followed by a RETURN:

The modem is now configured and ready for use.

lusr/ lib I uucpt L.sys is the file containing information about systems to
which uucp can connect. In order to prefix a number in L.sys with a nonnumeric character, that character must be defined in the file
lusrllibluucp/ L-dialcodes. In some cases this is needed to pass special
codes on to modems. For example, a modem might require the string "P"
to pulse dial (to dial on a line with pulse dial, instead of touch tone dial). A
sample L- dialcodes line is:
PULSE P
The number would be listed in L.sys as "PULSE4085551234". For more
information on L- dialcodes and L.sys, refer to Chapter 6 in the XENIX
User's Guide "Building a Communications System"
7.11.6 ModemControl
uucp must be used with modem control serial lines.
The modem must be set to respond to DTR (Data Terminal Ready).
Check your modem manual for instructions on setting DTR. Note that the
dialer port should be owned by uucp.
7.12 Adding a Lineprinter
This section explains how to add new lineprinters to your XENIX system
and how to use the lineprinter commands to organize and control your
printing.
The XENIX lineprinter spooling system is a collection of commands that
help you, as system manager, to efficiently install, monitor, and control the
lineprinters serving your system. When a user requests a file to be printed
using the Ip( C) command, the lineprinter system responds with a "request
ID." This consists of the name of the printer on which the file "Will be
printed and a unique number identifying the file. With this request ID, the

7-18

Using Peripheral Devices

user can find out the status of the print request or cancel it. The Ip options
help the user to easily control printer output. For more information on Ip,
see "Using the Lineprinter," in the Introduction to XENIX .
There are several terms used to describe the line printer system:

device

The target for Ip output. It can be a hard-wired
printer, a terminal that is sometimes used as a
printer, or a regular file. A device can be
represented by a full XENIX pathname.

printer

The name assigned by the system manager to
represent a device. This name can have up to 14
characters. At different times, a printer may be
associated with different devices.

class

An ordered list of printers. Print requests sent
to a class of printers are printed by the first available member of that class.

destination

A destination is where print requests are sent. A
destination can be a class or a printer.

Consult your computer and lineprinter hardware manuals for information
on making the connection between your system and printing devices.
7.12.1 Installing a Printer: Ipinit
To install new printing devices on your XENIX system, use the Ipinit(C)
command. Before you use lpinit you should first know the port to which
the lineprinter is connected or the XENIX pathname of the device (for
example, /dev/tty 1a) and the lineprinter interface program. A model interface program is supplied with your XENIX system. For more information
on printer interface programs, see "Printer Interface Programs."
When you give the Ipinit command, you are prompted with a series of questions. For most of them you need to supply your own answers, entering the
information as you are prompted. When you are prompted for the printer
name, however, you are given a default name option. If you wish to choose
the default answer, simply press the RETURN key. If you make a mistake
while responding to the questions, just press the DELETE key or the
INTERRUPT key and start again.

7-19

XENIX Operations Guide

Example
The following example shows how to add a line printer to your system. The
printer name is printerl, the device pathname is Idev!ttyla, and it will be
the default printer for your system:
1. Enter the command:
letc/lpinit
2. If the scheduler is running you are reminded that any jobs which are
printing may be interrupted and you are prompted if you want to
continue.
3. The following menu is displayed:
Do you wish to:
1 - Add a new printer.
2 - Remove a printer.
3 - Reconfigure an existing printer.
4 - Assign a default printer.
S - Print lp status information.
Select an option or enter q to quit:

Enter" I" and press RETURN.
4. Next you are prompted:

Are you adding a (P)arallel or (S)erial printer?

Enter"P" or"S" and press RETURN.
S. lpinit displays a list of available parallel or serial ports.
Enter your choice and press RETURN.

7-20

Using Peripheral Devices

6. Ipinit displays the following message:

Enter a name for the printer, press to use the default
name (printer) or enter q to return to the previous menu.

Printer names can be·up to 14 characters long and can be any combination of numbers, letters, or underscore characters. Enter the
printer name, printer1, and press the RETURN key.
7. Ipinit displays the following message on your screen:

If you have an unusual printer you must create an interface
program in lusrlspoolllp/model. For a sample interface program
look at lusrlspooI/lp/modeI/dumb.

8. Now you are prompted for a printer type. The screen displays a
numbered list of the available printer types on your system, followed by these instructions:

Enter one of the interface programs above or the full pathname of an interface
program or enter q to return to the previous menu:

Enter one of the options, then press RETURN.
9. After you have finished responding to these questions, Ipinit
displays the following message:

destination "printer1" now accepting requests
printer "printer!" now enabled

Then, Ipinit automatically gives the instructions to enable printer1
and allow it to accept print requests.

7-21

XENIX Operations Guide

10. After enablingprinterl, Ipinit prompts you to respond to one more
question:

IIs this the default printer? (yIn)
You can enter Y (for yes) or N (for no) depending upon whether you
want user print requests to be automatically routed to printerl or
not.
11. One last message is displayed:

H you need to modify your interface program after installing it,
the installed version is in lusrlspoolllp/interface/printer1.

After you have responded to these questions, Ipinit starts Ipsched, and
users can begin printing files on the new printer.
You can also add printers to your system using the Ipadmin command discussed in "Installing a Printer." However, you will need to give separate
commands to stop Ipsched, to enable the printer, and to allow it to accept
print requests. For more information on these programs and commands,
see sections "Stopping the Print Spooling Daemon," "Accepting and
Rejecting Print Requests," and "Enabling and Disabling Printers."
7.12.2 Stopping the Print Spooling Daemon: Ipsched
The spooling daemon, Ipsched, routes print requests through the correct
printer interface program and then to the lineprinter. No printing can be
done on your system unless Ipsched is running. The program Ipsched starts
automatically each time your XENIX system is restarted. Sometimes it is
necessary to stop Ipsched, especially if you want to reconfigure printers or
if you want to add new printers using the Ipadmin command (Ipinit
automatically stops and restarts Ipsched).
This section explains how to find out whether or not Ipsched is running,
how to stop and restart it, and howto recreate it if necessary.

7-22

Using Peripheral Devices

To find out whether or not Ips ched is running, enter:
lpstat -r
The system responds with a message indicating whether Ipsched is either·
running or not.
To shutdown the scheduler, Ipscbed, enter:
lusr/lib/lpshut
Ipscbed stops running and all printing stops as well. Printing requests
stopped in the middle of printing reprint when Ipscbed starts again.
After you have finished configuring the printers, you should restart
Ipscbed. To do this, enter:
lusr/lib/lpsched
Ips ta t • r should confirm that Ips cbed is running.
Each time Ipscbed sends a print request to an interface program, it records
an entry in a log file, lusrlspoollip/log. The entry includes the user name,
the request ID, the name of the printer the request will be printed on, and
the date and time requested. lpscbed also records any error messages in
this file. After you have stopped Ipsched, the log file is renamed
/usrlspoolliploidlog and Ipscbed starts a new log file. Requests waiting to
be printed before lpscbed was stopped may have an entry in both log files.
For more information on Ipscbed, see Ipsched(C),
Manual.

~NIX

Reference

7.12.3 erea ting an Init Device File
The standard parallel printer devices (/dev/lp, IdevllpO, Idev/lpJ, and
/devllp2) send a printer initialization string (in it) the first time the device is
opened after the system boots. This is done on the first open only so that
printers with large text buffers will not be flushed by the sending of another
file.
Some parallel printers require initialization every time a file is received for
printing. Others require an init if the printer is turned off and back on again
(for example, after changing paper or ribbons). The symptom of this situation is that the printer works fine until it is turned off and then back on.
lf you need to initialize the printer more often than the standard devices

provide, you can create an additional device file for the parallel port in use.
This "init device file" can be used when necessary to initialize the printer.

7-23

XENIX Operations Guide

1. Login as super-user
2. Determine which device is the parallel port you are using. This
example assumes the device is the main parallel port (/dev/lpO).
3. Use lpinit to associate one of the parallel init devices (lpOl, lpli,
Ip2i) with the printer (select option 3 "reconfiguring an existing
printer").
If your printer needs an in it when it is turned off and on, use the following command line after the printer is turned on. Initialize the
printer before the first file is sent to the printer (this example
assumes the main parallel port):

>/dev/lpOi

If your printer needs an init every time a file is sent (and it doesn't
have a large internal text buffer) you can use the /dev/lpOi device all
the,time.

The Ip(C) command now sends an init every time a file is sent to the
printer.
Some printers do not have newlinelcarriage return mapping. If
your printer needs to have newlines mapped to newline/carriage
returns, specify the ernlmap filter when you set up the printer using
the Ipinit(C) command. When you are prompted for the type of
printer (dumb printer, Imagen laser printer (parallel interface),
Imagen laser printer (serial interface), or other), enter "other".
You are then prompted for the pathname of the interface program.
The printer filter file is found in /usr/spoolllp/model/crnlmap.
7.12.4 Moving Requests Between Printers: Ipmove
You can move print requests between printing destinations by using
the command Ipmove. This command does not move print requests
while the scheduler, Ipscbed, is running. To stop Ipsched, see "Stopping the Print Spooling Daemon." Ipmove will move individual
print requests by request ID, or all requests waiting to be printed on
a particular printer.
For example, to move a request with a request ID of quick- 532 to a
printer named slow, enter:
lusr/lib/lpmove quick-532 slow
The print request now has a new request ID: slow- 532.

7-24

Using Peripheral Devices

To move all requests on a printer named quick to slow, enter:
lusr/lib/lpmove quick slow
For more information on lpmove, see lpsched (C), in the XENIX
Reference Manual.
7.12.S Accepting and Rejecting Print Requests: accept
The accept command allows printers or classes of printers to accept
print requests made with the lp command. You can allow a printer
to accept requests after it has been properly configured. The
printer, however, will not begin printing the requests until the
enable command is given. If you added a printer to your system
using the lpinit command, these steps were automatically performed. For information on enable, see "Enabling and Disabling
Printers."
For example, to have print requests accepted for a class of printers
named classl, enter:
lusr/lib/accept class!
If you want to prevent requests from being routed to a printer, you

can use the reject command. The -r options allows you to send
users a message explaining why a printer is out of service.
For example, to prevent printing requests, from being routed to a
printer, printer4, because of repairs, enter:
lusr/lib/reject -r"printer4 needs repair" printer4
A user who requests a file to be printed on printer4 will receive the
following message:

lp:can not accept requests for destination "printer4"
--printer printer4 needs repair
To find out the acceptance status of printing destinations, enter:
lpstat -a
For more information on lpstat, see "Using the Lineprinter" in the
Introduction to XENIX . For more information on aceeptlrej eet,
see aceept(C), in the XENIXReference Manual.

7-25

XENIX Operations Guide

7.12.6 Enabling and Disabling Printers
The enable command allows Ipscbed to print files on printers. A
printer can accept requests for printing after the accept command is
given for it, but in order for the files to be printed, the enable command must be given as well.
For example, to enable a printer named daisy, enter:
enable daisy
You can disable printers with the disable command. The
scheduler, Ipsched, will not send printing requests to disabled
printers regardless of their acceptance status. The· r options allows
you to send a message to users explaining why a printer has been disabled.
For example, to disable a printer named laser because of a paper
jam, enter:
disable -r"paper jam" laser
Users requesting the status of laser with the command Ipstat •
plaserwill receive the following message:
printer "laser" disabled since Dec 5 10:15
paper jam
For more information on these two commands, seeenable(C) and
dis a ble( C) in the XENIX Reference Manual.
7.12.7 Printer Interface Programs
Each printer on your system must have a printer interface program.
This can be a shell script, C program, or any other executable program. Your XENIX system provides a model interface program. It is
written as a shell script and can be found in /usr/spoollip/model.
You can use this program as is, modify it, or write your own interface program.
H you want to write or modify a printer interface program, the following information may be helpful.

7-26

Using Peripheral Devices

When Ipsched routes a printing request to a printer P, IUSTIspoollip
invokes the interface program for Pas follows:
interface P id user title copies options file
with
interface

the directory which contains executable copies of
interface programs

the interface program being executed

the request id returned by Ip

user

the login name of the user who made the request

title

an optional title given by the user

copies

the number of copies requested

options

a list of printer dependent options separated by
blanks

file

the full pathname of a file to be printed

When the interface program is started, its standard input comes from
Idevlnull and both standard output and standard error output are directed
to the printer's device. Devices are opened for reading as well as writing
when file modes permit. H a device is a regular file, all output is appended
to the end of that file.
Interface programs may format their output in any way. They must, however, ensure proper stty modes for terminal characteristics such as baud
rate and output options. In a shell script interface, this means that printer's
device must be open for reading -- take the standard input for the stty command from the device.
The file letc/deJault/lpd contains a line "BANNERS=d" where d is the
number of banner pages to be printed at the front of every printing request.
Interface programs should examine this file and behave accordingly.
After printing is completed, the interface program should exit with a code
showing that the print job was successful. Exit codes are interpreted by the
printer scheduler, fpsched, as follows:

7-27

XENIX Operations Guide

~eaningtolpsched

Exit Code
0
1 to 127

greater than 127

Print job was successful
lpsched found a problem while printing this
particular request, for example, too many
unprintable characters. This problem will not
affect future printing requests. Ipsched
notifies users by mail that there was an error in
printing the request.
These codes are reserved for internal use by
lpsched. Interface programs must not exit
with codes in this range.

Finally, when problems occur in printing that are likely to affect future
printing"requests, the printer interface program should disable printers so
that print requests are not lost. When a busy printer is disabled, the interface program will be terminated with a signal 15 so that print requests are
not lost.
For more information on printer interface programs, see Ipadmin(C), in
the XENIXReference Manual.
7.13 Adding Additional Memory
You can improve system performance and run larger programs by increasing the amount of in ternal memory.
To increase internal memory follow these steps:
1. Tum off your computer.
2. Install additional memory according to the manufacturer's instructions. Make sure you have set all switches as noted in the instructions.
3. Boot XENIX. The boot screen details how the additional memory
has affected your system.
1. Some features of XENIX may have been expanded. For
example, you may have:

7-28

•

~ore multiscreens

•

More buffers

•

A larger maximum user process size

Using Peripheral Devices

The number of multiscreens may be unchanged. Since the number of multiscreens can be set by the user, you may have already set a specific limit to
the number of multiscreens available. If you have not set a limit to the
number of multiscreens then you are already using the maximum number
of multiscreens that XENIX allows.
The number of buffers may also be unchanged. Since the number of
buffers can also be set by the user, you may have already set a specific limit
to the number of buffers available. If you have not set a limit to the number
of buffers then you are already using the maximum number of buffers that
XENIX allows.
If the maxim urn user process size is unchanged, then it is now limited by the
size of the swap file system instead of the amount of internal memory. You
can:

•

Reinstall XENIX and increase the size of the swap file system. See
Chapter 2, "Installation Procedure," of the Installation Guide for
details on reinstallation.

•

Change the process so that it runs without being swapped. Refer to
proctl(S) for details.

You can follow the same procedure if you wish to remove internal memory
from the system.
If the memory hardware reports an error to XENIX , XENIX displays the
message:

panic: parity
You then see the software reboot message:
•• Normal System Shutdown ••
•• Safe to Power Off ••
- or •• Press Any Key to Reboot ••
If the system repeatedly panics from parity errors, consider replacing the
memory chips.

7-29

XENIX Operations Guide

Note

Some machines have a hardware limitation on the maximum amount
of memory that can be installed. Refer to your computer hardware
manual to determine the maximum amount of memory you can
install.

7.14 Adding a Hard Disk
You can give the system extra room for storing users' files and directories
by adding a hard disk to the system. This is often~he only remedy for a system that has one hard disk and suffers from chronic lack of space. See the
Release Notes for a list of hard disks compatible with the current XENIX
release.
You can only have one disk controller card. Software support is now provided for hard disks that do not have matching entries in the ROM tables.
Switch settings on the disk controller card may need to be changed. Check
your hardware manual for the hard disk drive and the computer for this
information.
'
Before adding the new disk, you must know how to connect it to the computer. Connecting the hard disk is explained in the hardware manual provided with the disk. Make sure the second drive passes the manufacturers
diagnostics before runningXENIX.
This is an outline of the procedure to add another hard disk:
•

Connect the hard disk, then boot the system and enter system
maintenance mode.

•

Use the letc/mkdev program. mkdev executes hdinit which, in
turn, runs four interactive programs: dkinit to inititalize the hard
disk characteristics, fdisk(C), to separate the disk into MS-DOS
and XENIX areas (the DOS area is optional), badtrk(M), to identify
and map any bad areas on your disk, and divvy(C), to partition your
disk into file systems.

7-30

Using Peripheral Devices

Note
In the steps outlined below, you are prompted to respond to a variety
of prompts. Although it is not always designated in this documentation, remember to press RETURN (or ENTER) after you have typed
each response. XENIX waits indefinitely until this is done.

These are the steps to add another hard disk with one XENIX file system
and no DOS area:
1. Connect the hard disk, then boot the system and enter system
maintenance mode.

2. When you are in system maintenance mode, enter:

/etc/mkdev hd
3. The first utility invoked by hdinit is dkinit, which sets parameters for
non -standard hard disks. You see the menu

Hard Disk Drive 1 Configuration
1. Display current disk parameters
2. Modify current disk parameters
3. Select default disk parameters

Enter an op,tjon or'q' to quit:
If you have a standard hard disk, type "q" followed by
. This selects the default parameters for your hard

disk. Unless you know that your disk is non-standard, assume that
it is standard and continue.
If your disk is non -standard, dkinit operates as follows:
If you enter" 1" or "2" , you see the following display:

Disk Parameters
.1. Cylinders
, 2. Heads
3. Write Reduce
4. Write Precomp
S.Bec
6. Control
7. Landing Zone
8. Sectors/track

Values

value
value
value
value
value
value
value
value
7-31

XENIX Operations Guide

When you see the display, "value" is replaced with the default value
for that variable.
If you entered a "I", you now see the first menu again. If you

entered a "2", you are now prompted:
Enter a parameter to modify or 'q' to return to the main menu:
If you enter "q", you see the first menu again. If you enter anyof"I"

- "8", you see the prompt:
Enter the new value or to use the existing value:
If you wish to change the value, enter a new value now or enter
to use the existing value.

After the table values are displayed or modified, the initial menu is
again displayed and you must type "q" to exit dkinit. Exiting dkinit
by typing "q" overwrites any parameters you have changed with the
new values. If you wish to restore the default parameters after making modifications, enter "3" from the first menu before typing "q"
to exit dkinit.
dkinit is used to support non-standard hard disks. The normal
user, while adding a second hard disk, will simply enter "q" when
confronted with the dkinit initial menu. When the dkinit program
exits, the hdinit program invokes fdisk(C), which partitions the
hard disk.
4. When fdisk starts, you see this menu:
Select one of the following options or 'q' to exit the program
1.
2.
3.
4.
S.

Display Partition Table
Use Entire Disk for XENIX
Create Partition
Activate Partition
Delete Partition

Enter your choice or 'q' to quit:
If you want to use your whole disk for XENIX , enter '2', then press
RETURN. If your hard disk already contains valid partitions, fdisk
displays the current partition tab Ie followed by the message:

Warning! All data on your disk will be lost!
Do you wish to continue? (yIn)

7-32

Using Peripheral Devices

If you would like XENIX to occupy the whole disk, enter 'y' and
press RETURN.
If no partitions were previously installed on your hard disk, fdisk
will allocate the entire disk for XENIX without displaying the above
warning.

Note that fdisk reserves the first track for masterboot and the last
cylinder of the hard disk for disk diagnostics. Thus your partition
begins on track 1 in$tead of track 0 and it ends on track 1219 instead
of track 1223.
You see the partition table again, with the following changes:
Current Hard Disk Drive: Idev/rhd01

Total disk size: 1224 (5 tracks reserved for masterboot and diagnostics)
Press to continue.
After you press RETURN, you see the main fdisk menu, shown
above. Note that the XENIX partition must be active before exiting
edisk. Type 'q' to exit fdisk and continue with the installation.
For more information on having DOS and XENIX on your hard
disk, seefdisk(C).
If you had a large portion of the disk already allocated to DOS, you
must run DOS to deallocate this area. See fdisk(C) for more information on sharing disks between DOS and XENIX. No matter what
configuration you produce with fdisk, the active partition must be
the XENIX partition when you are through.

5. The next menu is from the bad track mapping program, badtrk. It
displays this menu:
1.
2.
3.
4.
5.
6.

Print Current Bad Track Table
Scan Disk (You may choose Read-Only or Destructive later)
Add Entries to Current Bad Track Table by CylinderlHead Number
Add Entries to Current Bad Track Table by Sector Number
Delete Entries Individually From Current Bad Track Table
Delete All Entries From Bad Track Table

Please enter your choice or 'q' to quit:

7-33

XENIX Operations Guide

Enter '2', then press RETURN. If badtrk thinks that the table may
have been changed, you are prompted if you want to update this
device with a new table. You should answer 'y'. Next, you are
prompted if you want to salvage any data on the bad tracks, and
warned that this may take a longtime. You should answer 'n' unless
you have data on the bad tracks that you need to restore and there is
no other way (i.e. backups) to recover the information, in which
case you should respond 'y'.
You see the following submenu:
1. Scan entire XENIX partition
2. Scan a specified range of tracks
3. Scan a specified filesystem
Enter the number corresponding to the type of scan you wish to perform. If this is afresh installation, (that is you are installing XENIX
for the first time or performing a complete reinstallation), you probablywantto select option '1'.
If you choose option '2' or '3' , you are then prompted to specify the
area you want badtrk to scan.

After you have selected the area you want scanned, you are given
the choice:
1. Quick scan (approximately 1 min/megabyte)
2. Thorough scan (approximately 7 mins/megabyte)
Option '2' should be selected if this is a fresh installation. Once you
respond to the above prompt, you are prompted:
Do you want this to be a destructive scan? (y/n)
If you respond 'n', a non -destructive, readonly scan begins. However, for your fresh installation, respond 'y' . You are warned:
This will destroy the present contents of the region you are scanning.
Do you wish to continue? (yIn)

Respond 'y' for your fresh installation and you see the following
message:
Scanning in progress, press 'q' to interrupt at anytime.
After you have responded to the above prompts, the program scans
the active partition of the hard disk for flaws. The larger your disk,
the longer the scanning process takes, so a veri large disk may ta.1ce a
while.
7-34

Using Peripheral Devices

As badtrk scans the disk, it displays the number of each track it
examines, and the percentage ofthe disk already scanned. Pressing
"q" at any time interrupts the scan. You will then be prompted to
continue scanning or to return to the main menu. Whenever badtrk
finds a defective track, it lists the location of that track using both-the sector number and cylinder/head conventions.

H your disk comes with a flaw map, cross-check your map against
the results of the disk scanning. Because most disk flaws are marginal or intermittent, any flaw map will almost certainly contain more
flaws than the scanning process will reveal. Depending on the format of your flaw map, select either option '3', "Add Entries to
Current Bad Track Table by Cylinder/Head Number", or option
'4', "Add Entries to Current Bad Track Table by Sector Number",
and enter the flaws, one per line. Enter 'q' when you are finished.
Exit badtrk by entering 'q' at the main menu.
The program now displays the number of identified bad tracks. You
are prompted to enter the number of tracks to be allocated as
replacements for bad tracks. You will see a recommended number
of tracks to allocate as space for replacement. This numberis based
on the number of known bad tracks and an allowance for tracks that
will go bad in the future. You should choose to allocate at least as
many tracks as recommended. Please make this choice carefully,
because if you want to change this amount later, you will have to
reinstall XENIX .
Next, badtrk prompts:
Do you want to update this device with the new table?
To save the changes made to the bad track table, enter 'y'. If an irrevocable mistake has been made in the bad track table at some time
during this process, enter 'n', modify the bad track table to contain
the desired entries, and then enter 'q' at the main menu to return to
the prompt displayed above.
You are prompted:
Do you want to attempt to salvage any valid data
on the bad tracks? [maytakealongtime](y/n)
Generally you should respond en' to this prompt. However, if you
have not made a backup of needed data on the bad tracks and there
is no other way of recovering this information, you may want to
respond 'y' , keeping in mind that this process may take a long time.

7-35

XENIX Operations Guide

6. Next, you see a prompt from divvy. The divvy program divides a
partition into file systems. You can create up to seven divisions on a
single partition, and name them anything you like.
If the hard disk you are installing is 20 megabytes or larger, you will
be prompted for the number of file systems you want to create.
Press RETURN to use the default value of one file system. Smaller
hard disks automatically default to creating one file system.

You are next prompted for block control of your hard disk. You
see:
Do you require block by block control over
the layout of the XENIX partition? (yIn)
Enter 'y' and press.RETURN. This allows you to create up to seven
file systems on a single XENIX partition, and assign specific names
to whatever file systems you create. You must enter 'y' if you
prompted to create more than 1 file system in the previous prompt.
You see the main divvy menu and a display that shows you how your
disk is divided:
Block
Partition

Character
Part.

dl150

rd1150

dl157a11

d[isplay]
b[1ock]
c[haracter]
o[verwrite]
p[revent]
s[tart]
e[nd]
t[rade]
r[estore]

rd1157all

OvelWrite?
yes
no
no
no
no
no
no
no

First Block

Last Block

24344

25546

Display the divvy table.
Change the name of a division's block interface.
Change the name of a division's character device.
OveIWrite a division with a new file system.
Prevent a division from being ovelWritten as a new file system.
Start a division on a different block.
End a division on a different block.
Trade the blocks that two divisions refer to.
Restore default root partition table.

Please choose one of these conmumds:

7-36

#
0
1
2
3
4
5
6
7

Using Peripheral Devices

Each line in the divvy table corresponds to a file system. For example, the default names for file system 0 are d1150 for the block device and rdl150 for the character device.
To change the name of a file system, use option 'b' to change its
block name. You could name it u (for "user"), for example. Then
use option 'c' to change the character name of that same file system
to, for example, rUe The character name should be the same as the
block name, except that it should start with the letter 'r' .
Do not change the configuration of file system· 7. It is reserved for
internal use byXENIX.
Exit from divvy by entering 'q'. The program may prompt whether
to install the new partition table, return to the main menu or exit the
program without installing partition table. Select option 'i' to install
the partition table.
If you have a large file system, you maybe prompted if you want a

scratch device to be created for you. You should answer yes.
For more information on divvy(C) see the XENIX Reference
Manual.
7.14.1 Mounting Another File sys tern
To use an additional disk, or create a second, mounted file system,
enter this command:
mkdev fs Idev/u lu
This command does the following:
•

Creates a directory lu (also known as the mount point).

•

Creates the lost+found directory (used by fsck to recover
files if the file system is corrupted).

•

Mounts the device (ldevlu) on lu, cleans it, and unmounts it.

•

Removes write permissions on the directory lu for group and
all other users except root.

•

Creates files in the lullost+found directory, then removes
them. This allocates inodes for the directory, so that if the
file system is corrupted and runs out of inodes, fsck(C) is still
able to recover files.

7-37

XENIX Operations Guide

•

Adds the following line to /etc!checklist:
Idev/u

•

Modifies letc!defaultlfilesys so that the new file system is
automatically mounted, checked and cleaned when appropriate.

To mount or unmount Idevlu on lu, use the following two commands,
respectively:
mount fs Idev/u lu
umount fs /dev/u lu

7.14.2 UsingASecondFlleSystem
You can access the files on your new file system by first mounting it in the
appropriate directory (we used lu as an example in the preceding section).
After you mount the file system, all directories and files on it are usable just
as any others on the system.
If you want to have user accounts on your mountable file system, change
the variable "HOME" in the file letc!defaultlmkuser. The "HOME" variable defines the directory where user accounts are placed. This variable is
used by the mkuser(C) program, which adds new users to the system.

Edit the file I etc!defaultlmkuser. There is a line which may look like this:
HOME=/usr
Change lusr to the name of the directory where you want to place user
accounts. In our example, thisis/u. The line should now read:
HOME=/u
Now, whenever you run themkuser(C) scriptto add a new user, that user's
account will be in lu.
If there are already users on the system, and you want to move their

accounts to the new file system, you can use the copy(C) command to copy
their accounts to the new file system. You must also change the users'
entries in /etc/passwd to reflect the new pathnames of their home directories.
Follow these steps to move user accounts from one file system to another:
1. Make sure the new file system is mounted, Also, be sure you are
either in system maintenance mode, or logged in as root.

7-38

Using Peripheral Devices

2. Change directories to the top of the current user account directory.
If, for example, the user accounts are in lUST, enter:
cd lusr
and press RETURN.

3. List the contents of this directory:
Ie

You see a list of account names, for example:
alisonb
blf
buckm

dean
gregt

jeffj

jerrys
lost+found
pj

sams
tammyr
vicki

4. Enter:
copy -orm /usr lu
and press RETURN.
5. When the copy command has finished, enter:
cd lu
and press RETURN. List the new contents of lu to make sure all of
the accounts have been copied correctly.
6. After you are sure that all of the accounts have been completely
copied, you can remove the user accounts in the previous user file
system.
7.

Change the home directory for each user as listed in letc/passwd.
An example entry in letc/passwd might be:
alisonb :CoHiKN s. :271: l04:Alison Berry:/usrlalisonb :/binl csh

You see one such line for every user on your system. Change the
field:

:/usrlalisonb :
to match the user's new home directory:

7-39

XENIX Operations Guide

:/u/alisonb:
Do this for every user whose home directory has changed.
7.1S Creating Bootand Root Floppy Disks
mkdev(C) provides a utility to create bootable and root system floppy
disks. mkdev invokes/dinit, a menu-driven program which allows the user
to select the disk format and file system type. There are three basic types
generated: boot and root on a single disk (96 tpi only), boot and root pair
(48 tpi), or filesystem only (which simply invokes mkfs(C)). The formats
supported are: 48 tpi, 96 tpi-15 sectors/track, in 5 114 and 31/2 inch formats. To create the floppies, enter:
/etc/mkdev fd
and you will see the following display:

Choices for type of floppy filesystem.
1. 48 tpi, double sided, 9 sectors per track
2. 96 tpi, double sided, 15 sectors per track
Enter an option or enter q to quit:

Enter the correct type and press RETURN. You are then prompted for the
disk:

Insert a xx tpi floppy into drive O. Press Return to continue.

Insert your floppy and press RETURN. The program responds with

7-40

Using Peripheral Devices

another menu:

Choices for contents of floppy filesystem.
1.
2.
3.
4.

Filesystem only
Bootable only
Root filesystem only
Root and Boot (only available for 96tpi floppy)

Enter an option or enter q to quit:

Select the appropriate filesystem and press RETURN. fdinit generates the
filesystem and will display the following message when complete:

xx tpi file system floppy complete.

7-41

ChapterS
Solving System Problems
8.1

Introduction

8-1

8.2

Restoring a NonechoingTerminal

8.3

Solving Lineprinter Problems 8-1

8.4 Stopping a Runaway Process
8.5

8-2

Replacing a Forgotten Password

8.6 Removing Hidden Files

8-1

8-3

8.7

Restoring Free Space 8-3

8.8

Restoring Lost System Files

8-3

8.9 Restoring an Inoperable System

8-4

8.10 Recovering from a System Crash

8-4

8.11 Mapping a Bad Track

8-5

8.12 ChangingXENIXlnitialization 8-5
8.12.1 Changing the letc/rc File 8-6
8.12.2 Changing the. profile Files 8-6
8.12.3 Changing the letc/motd File 8-7

Solving System Problems

8.1 Introduction
This chapter explains how to solve problems that affect the operation of
the system. The problems range in complexity from howto fix a nonechoing terminal, to how to restore lost system files.

8.2 Res toring a Nonechoing Terminal
A non echoing terminal is any terminal that does not display characters
entered at the keyboard. This abnormal operation can occur whenever a
program stops prematurely as a result of an error, or when the user presses
the BREAK key.
To restore the terminal to normal operation, follow these steps:
1. Press the Ctrl-j key. The system may display an error message. If it
does, ignore the message.
2.

Enter:
sttysane
and press the Ctrl-j key. The terminal does not display what you
enter, so enter accurately.

After pressing Ctrl-j, the terminal should be restored and you may continue your work.

8.3 Solving Lineprinter Problems
No printing can be done on the lineprinter spooling system unless the print
scheduler, lpsched, is running. To check the status oflpsched, enter:
lpstat -r
To restart lpsched, enter the following on two lines:
lusr/lib/lpshut
lusr/lib/lpsched
Calling the file lustllibllpshut cleans the system and lusrllibllpsched start it
up again.
Access to files and directories in lusrlspoolllp by lp can be another source
of spooling problems. You can check the lpsched log file,
lusrlspoolllp/log. This is a record of the print scheduler's activity and
8-1

XENIX Operations Guide

errors. Iflpscbed refuses to run or a printer refuses to print, check to make
sure that:
-

Theprinterisenabled; seelp(C) in theXENIXReferenceManual.

The files and directories in /usrispoollip are readable and writable
bylp.

For more information on the lineprinter spooling system, see the section
"Adding A Lineprinter" in Chapter 7.
8.4 Stopping a Runaway Process
A runaway process is a program that cannot be stopped from the terminal
at which it was invoked. This occurs whenever an error in the program
"locks up" the terminal, that is, prevents anything you enter from reaching
the system.
To stop a runaway process, follow these steps:

1. Go to a terminal that is not locked up.
2.

3. Enter:
ps-a
and press the RETURN key. The system displays all current
processes and their process identification numbers (PIDs). Find the
PID of the runaway program.
4. Enter:
killPID

and press the RETURN key. The PID is the process identification
number of the runaway program. The program should stop in a few
seconds. If the process does not stop, enter:
kill-9PID

and press the RETURN key.
The last step is sure to stop the process, but may leave temporary files or a
nonechoing terminal. To restore the terminal to normal operation, follow
the instructions in the section "Restoring a Nonechoing Terminal" in this
chapter.

8-2

Solving System Problems

8.5 Replacing a Forgotten Password

The XENIX operating system does not provide a way to decipher an existing password. If a user forgets his password, the system manager must
change the password to a new one. To change an ordinary user password,
follow the instructions in the section "Changing a User's Password" in
Chapter 3.

8.6 Removing Hidden Files
A hidden file is any file whose name begins with a dot (.). You can list the

hidden files in a directory by entering:
lc -a
and pressing the RETURN key.
You can remove most hidden files from a directory by entering:

rm .[a-z]*
and pressing the RETURN key. Remaining files can be removed individually.

8.7 Res to ring Free Space

The system displays an "out of space" message whenever the root directory has little or no space left to work. To restore system operation, you
must delete one or more files from the root directory. To delete files, follow the steps outlined in the section "Maintaining Free Space" in Chapter

8.8 Restoring Lost System Files
If a system program or data file is accidentally modified or removed from

the file system, you can recover the file from the periodic backup disk with
the sysadmin program. To restore the files, follow the instructions in the
section "Restoring a Backup File" in Chapter 6.

8-3

XENIX Operations Guide

8.9 Restoring an Inoperable System
On very rare occasions, one or more of the critical XENIX system files may
be accidentally modified or removed, preventing the system from operating. In such a case, you must reinstall the XENIX system, and restore user
program and data files from backup disks. To reinstall the system, follow
the instructions in the XENIX Installation Guide. To restore files from
backup disks, follow the instructions in the section "Restoring a Backup
File" in Chapter 6.

8.10 Recovering from a System Crash
A system crash is a sudden and dramatic disruption of system operation
that stops all work on the computer. System crashes occur very rarely.
They are usually the result of hardware errors or damage to the root file system which the operating system cannot correct by itself. When a system
crash occurs, the system usually displays a message explaining the cause of
the error, then stops. This gives the system manager the chance to recover
from the crash by correcting the error (if possible), and restarting the system.
A system crash has occurred if the system displays a message beginning
with "panic:" on the system console, or the system refuses to process all
input (including INTERRUPT and QUIT keys) from the system console
and all other terminals.
To recover from a system crash, follow these steps:
1. Use the error message(s) displayed on the system console to determine the error that caused the crash. If there is no message, skip to
step 3.
2.

Correct the error, if possible. A complete list of error messages and
descriptions for correcting the errors is given in messages (M) in the
XENIX Reference Manual. (Even if the problem cannot be located
or corrected, it is generally worthwhile to try to restart the system at
least once by completing the remaining steps in this procedure.)

3. Turn off the computer and follow the steps described in Chapter 2,
"Starting the System," to restart the system.
4. If the system will not restart, or crashes each time it is started, the
operating system is inoperable and must be reinstalled. Follow the
procedures described in the XENIX Installation Guide to reinstall
the system and in Chapter 6, "Backing Up File Systems," to restore
user's files.

8-4

Solving System Problems

5. If the system cannot be started from the "Boot" disk in the distribution set for installation, the computer has a serious hardware malfunction. Contact a hardware service representative for help.

8.11 Mapping a BadTrack
Bad tracks on the hard disk are mapped during the XENIX installation procedure. This allows XENIX to avoid those areas of the disk that cannot be
read or written. However, hard disks can develop bad tracks afterXENIX
is installed and running. If this occurs, the badtrk(M) utility should be run
by the super-user (root) enabling XENIX to avoid the new bad track(s).
badtrk must be run in single-user mode. Use /etc/shutdown su to enter
single-user mode from multi-user mode (see shutdown(C)).
badtrk is a menu-driven utility for viewing, adding, or deleting entries to
the bad track table. See badtrk(M) in the XENIX Reference Manual for
more on its options and their use.
8.12 Changing XENIX Initialization
One common problem is adapting the system initialization to suit your system environment. This problem occurs whenever you have added new devices such as terminals or disk drives to the system, and wish these devices
to be automatically enabled or mounted whenever you start normal system
operation. You can adapt system initialization by modifying the system initialization files.
The XENIX initialization files contain XENIX commands and/or data
which the system reads at system startup or whenever a user logs in. The
files typically mount file systems, start programs, and set home directories
and terminal types. The initialization files are named /etc/rc, .profile, and
/etc/motd.
The system manager may modify these files to create any desired initial
environment. The files are ordinary text files and may be modified using a
text editor such as ed (see the XENIX User's Guide). Note, however, that
the /etc/rc and ~profile files contain XENIXcommands and comments, and
have the command file format described in Chapter 4, "The Shell," in the
XENIX User's Guide.

8-5

XENIX Operations Guide

8.12.1 Changing the letclrc File

The letc!rc file contains XENIX system initialization commands. The system executes the commands at system startup. The commands display a
startup message, start various system daemons, and mount file systems.
You can display the contents of the file with the more command. Enter:

more/etc/rc
and press the RETURN key.
You may change the contents of the file so that the system executes any set
of commands you wish. For example, if you want the system to automatically mount a new file system, simply append the appropriate mount command in the file. The system will execute the command on each startup.
To append a command to the file, follow these steps:
1. Login as the super-user.

Invoke a text editor and specify the letclrc as the file to be edited.

Locate the place in the file you wish to insert the command (e.g., if
the command mounts a file system, insert it with other mounting
commands).

Insert the command on a new line. Make sure you enter the command correctly. The system rejects any incorrect commands and
the commands that follow it when the file is read at system startup.

5. Exitthe editor.
No other changes to the file are required. Be careful not to delete any commands already in the file unless you are sure they are not needed.
8.12.2 Changing the .profile Files

The .profile files contain commands that initialize the environment for
each user. The commands in the file are executed whenever the user logs
in. The file usually contains commands that set and export various system
variables (e.g., TERM, PATH, MAIL). These variables give the system
information such as what terminal type is being used, where to look for
programs the user runs, where to look for the user's mailbox, what keys to
expect for the "kill" and "backspace" functions, and so on (see Chapter 4,
"The Shell," in theXENIX User's Guide).
There is one .proJfile file for each user aCCOullt on the system. The files are
placed in the user's home directory when the account is created. An ordinary user may modify his own .profile file or allow the system manager to

8-6

Solving System Problems

make modifications. In either case, the file can be edited like the fetcfrc
file by using a text editor. Commands can be added or removed as desired.
8.12.3 Changing the letc/motd File
The message of the day file, fete/motd, contains the greeting displayed
whenever a user logs in. Initially, this file contains the name and version
number of the XENIX system. It can be modified to include messages such
as a reminder to clean up directories, a notice of the next periodic backup,
and so on.
The f ete/motd file is an ordinary text file, so you can change the message by
editing the file with a text editor. One common change is to include a reminder to delete unused files in order to preserve disk space. In general, you
should limit the size of the file to include no more than a screenful of information.

8-7

Chapter 9
Building a Micnet Network
9.1 Introduction 9-1
9.2 Planning a Network 9-1
9.2.1 Choosing Machine Names 9-2
9.2.2 ChoosingaNetworkTopology 9-2
9.2.3 Drawing a Network Topology Map 9-3
9.2.4 Assigning Lines and Speeds 9-3
9.2.5 Choosing Aliases 9-4
9.3 BuildingaNetwork 9-5
9.3.1 Creating the Micnet Files 9-5
9.3.2 Saving the Micnet Files 9-9
9.3.3 Restoring Micnet Files 9-10
9.4 Starting the Network 9-11
9.5 TestingaMicnetNetwork 9-12
9.5.1 Checking the Network Connections 9-12
9.5.2 Using the LOG File to Locate a Problem 9-13
9.5.3 Stopping the Network 9-15
9.5.4 Modifying the Micnet Network 9-15
9.6 UsingaUucpSystem 9-15

-9-i -

Building a Micnet Network

9.1 Introduction
A Micnet network allows communications between two or more independent XENIX systems. The network consists of computers connected by
serial communication lines (that is, RS-232 ports connected by cable).
Each computer in the network runs as an independent system, but allows
users to communicate with the other computers in the network through the
mail, rep, and remote commands. These commands pass information
such as mail, files, and even other commands, from one computer to
another.
It is the system manager's task to build and maintain a Micnet network.
The system manager decides how the computers are to be connected,
makes the actual physical connections, then uses the netutil program to
define and start the network.

This chapter explains how to plan a network and then build it with the
netutil program. In particular, it describes:
-

How to choose machine names and aliases

Howto draw the network topologymap

How to assign serial lines

How to create the Micnet files

Howto distribute the Micnet files

How to test the Micnet network

9.2 Planning a Network
To build a Micnet network, the netutil program requires that you provide
the names of the computers that will be in the network, a description of
how the computers are to be connected, a list of the serial lines to be used,
the names of the users who will use the network, and what aliases (if any)
they will be known by.
To keep the task as simple as possible, you should take some time to plan
the network and make lists of the information you will be required to supply. To help you make these lists, the following sections suggest ways to
plan a network.

9-1

XENIX Operations Guide

9.2.1 Choosing Machine Names
A Micnet network requires that each computer in the network have a
unique "machine name." A machine name helps distinguish each computer from other computers in the network. It is best to choose machine
names as the first step in planning the network. This prevents confusion
later on, when you build the network with the netutil program.
A machine name should suggest the location of the computer or the people
who use it. You can also use any name you wish. The name must be unique
and consist of letters and digits. The Micnet programs use only the first
eight characters of each name, so be sure those characters are unique.
The netutil program saves the machine name of a computer in a
letclsystemid file. One file is created for each computer. After you have
built and installed the network, you can find out the machine name of the
computer you are using by displaying the contents of this file.
9.2.2 Choosing a Network Topology
The network topology is a description of how the computers in the network are connected. In any Micnet network, there are two general topologies from which all topologies can be constructed. These are "star" and
"serial. "
In a star topology, all computers are directly connected to a central computer. All communications pass through the central computer to the
desired destination.

In a serial topology, the computers form a chain, with each computer
directly connected to no morethan two others. All communications pass
down the chain to the desired destination.

A network may be strictly star, strictly serial, or a combination of star and
serial topologies. The only restriction is that no network may form a ring.
For example, you cannot close up a serial network by connecting the two
computers at each end.
The kind oftopologyyou choose depends on the number of computers you
have to connect, how quickly you want communications to proceed, and
how you want to distribute the task of passing along communications. A
star topology provides fast communication between computers, but
requires both a large portion of the central computer's total operation time
and a large number of serial lines on the central computer. A serial topology distributes the communication burden evenly, requiring only two serial
lines per computer, but is slow if the chain is very long (communication
between computers can take several minutes). Often a combination of star
and serial topologies makes the best network. In any case, make the

9-2

Building a Micnet Network

choice you think is best. If you discover you have made a wrong choice,
you may change the network at any time.
9.2.3 Drawing aN etwork Topology Map
A network topology map is a sketch of the connections between computers in the network. You use the map to plan the number and location of the
serial lines used to make the network.
You can make the map while you work out the topology. Simply arrange
the machine names of each computer in the network on paper, then mark
each pair of computers you wish to connect with serial lines. For example,
the topology map for three computers might look like this:
a ---------- b ---------- c

As you draw, make sure that there is no more than one connection
between any two computers in the network. Furthermore, make sure that
no rings are formed (a ring is a series of connections that form a closed circle). Multiple connections and rings are not permitted.
9.2.4 Assigning Lines and Speeds
Once you have made the topology map, you can decide which serial lines to
use. Since every connection between computers in the network requires
exactly two serial lines (one on each computer), you need to be very careful
about assigning the lines. Follow these steps:

1. Make a list of the serial lines (TTY lines) available for use on each
computer in the network. You can display a list of the serial lines on
a computer by displaying the file letclttys. A line is available if it is
not connected to any device such as a terminal or modem.
2. Using the topology map, first pick a computer, then assign one (and
only one) serial line to each connection shown for that computer.
The serial lines must be from the list of available lines for that computer. No line may be assigned more than once. For example, if
computer a has only one available serial line (ttyla), then the topologymap should look like this:
a ---------- b ---------- c

ttyla

9-3

XENIX Operations Guide

Repeat step 2 for all computers in the topology map. Make sure that
each connection is assigned a line and that no two connections on
any given computer have the same line. When finished, the map
should look like this:
a ---------- b ---------- c
ttyla
tty2a tty3a tty4a
If a computer does not have enough available serial lines to meet its

needs, you can make the lines available by removing the devices
already connected to them. If you cannot remove devices, you must
redraw your topology map.
4.

Using the topology map, assign a serial line transmission speed for
each computer pair. The speed must be within the normal range for
XENIX serial lines (typically 110 to 9600). Transmission speeds are a
matter of preference. In general, a higher speed means a smaller
amount of time to complete a transmission, but a greater demand
on system's input and output capabilities. In some cases, transmission speeds are a matter of hardware capabilities. Some hardware is
not capable of transmission speeds greater than 1200 baud. For this
reason, 1200 is the recommended speed when first installing Micnet. You may then increase the speed if you find the hardware can
support it.

S. After the topology map is completely filled in, make a list of all computer pairs, showing their machine names, serial lines, and
transmission speeds. You will use this list when installing the network.
9.2.5 Choosing Aliases
Once you have decided how to connect the computers in the network, you
can choose aliases for users in the network. An alias is a simple name that
represents both a location (computer) and a user. Aliases are used by the
mail command to allow you to refer to specific computers and users in a
network without giving the explicit machine and user names. Although not
a required part of the network, aliases can make the network easier to use
and maintain.
There are three kinds of aliases: standard, machine, and forward. A standard alias is a name for a single user or a group of users. A machine alias is
a name for a computer or an entire network (called a site). A forward alias
is a temporary alias for a single user or group of users. A forward alias
allows users who normaHy receive network communications at one computer to receive them at another.

9-4

Building a Micnet Network

When you build a network with the netutil program, you are asked to provide standard aliases only. (You can incorporate machine and forward
aliases into the network at your leisure.) Each standard alias must have a
unique name and a list of the login names of the users it represents. You
may choose any name you wish as long as it consists of letters and numbers,
begins with a letter, and does not have the same spelling as the login names.
The name should suggest the user or group of users it represents. The login
names must be the valid login names of users in the network.
T (j help you prepare the aliases for en try during the netutil program, fo llow
these steps:
1. Make a list of the user aliases (that is, the aliases that refer to just
one user) and the corresponding login names of each user.

2. Make a separate list of the group aliases (that is, the aliases that refer
to two or more users) and the login names or user aliases (from the
first list) of the corresponding users. A group alias may have any
number of corresponding users.
Note that there are a number of predefined group aliases. The name all is
the predefined alias for all users in the network. The machine names of the
com puters in the network are predefined aliases for the users on each computer. Do not use these names when defining your own aliases.
9.3 Building a Network
You build a network with the netutil program. The program allows you to
define the machines, users, and serial lines that make up the network.
To build a network, you must first create the Micnet files that define the
network and then transfer these files to each computer in the network.
After each computer receives the files, you may start the network and use it
to communicate between computers.
The following sections describe how to build the network.
9.3.1 Creating the Micnet Files
The Micnet files are created with the install option of the netutil program.
The install option asks for the names, aliases, and serial lines of each computer in the network. As you supply the information, it automatically
creates the files needed for each computer. These files can then be
transferred to the other computers in the network with the save and
restore options of netutil. This means you can build the entire network
from just one computer.

9-5

XENIX Operations Guide

To use the ins tall option, follow these steps:

1. Log in as the super-user.
2.

Enter:
netutil
and press the RETURN key. The program displays the network utilitymenu. The install option is the first item in the menu.

3. Enter the number 1, and press the RETURN key. The program
displays the following message:
Compiling new network topology
Overwrite existing network files? (yes/no)?
Enter y and press the RETURN key to overwrite the files. The existing network files must be overwritten to create the new network.
The first time you install the network, these files contain default
information that need not be saved. If you install the system a
second time or expand the system, it may be wise to save a copy of
these files before starting the ins tall option. The files can be saved
on a floppy or a hard disk with the save option described later in this
chapter.
Once you have entered y, the program displays the following message:
Enter the name of each machine
(or press RETURN to continue installation).
Machine name:
4.

Enter the machine name and press the RETURN key. You may
enter more than one name on a line by separating each with a
comma or a space. After you have entered all the names, press the
RETURN key to continue to the hext step. The program displays
the names you entered and asks if you wish to make changes.

5. Enter y (for "yes") if you wish to enter all the names again. Otherwise, enter n (for "no") or just press the RETURN key to move on to
the next step. If you enter n, the program displays the message:
For each machine, enter the names of the machines
to be connected with it
Machine a:
Connect to:

9-6

Building a Micnet Network

6. Using the list of machine pairs you created when planning the network, enter the machine names of the computers connected to the
given computer. You may enter more than one name on a line by
separating each name with a comma (,) or a space. When you have
entered the machine names of all computers connected to the given
computer, press the RETURN key. The program prompts for the
names of the computers connected to the next computer.
7. Repeat step 5 for all remaining computers. As the program prompts
for each new set of connections, it will show a list of the machine
names it already knows to be connected with the current computer.
You need not enter these names. The program automatically
checks for loops. If it finds one, it ignores the machine name that
creates the loop and prompts for another.
Finally, when you have given the connections for all computers in
the network, the program displays a list of the connections and asks
if you wish to make corrections.
8. Enter y, if you wish to enter the connections again. Otherwise,
enter n, to move to the next step. If you enter n, the program
displays the message:
For each machine pair, enter the tty name and tty speeds
For the a <==> b machine pair.
Ttyona:
9. Using the list of serial line assignments you created when planning
the network, enter the serial line name or number (for example,
tty03 or 3) for the first computer in the pair and press the RETURN
key. The program displays the message:
Ttyonb:
10. Enter the serial line name for the second computer in the pair and
press the RETURN key. The program displays the message:
Speed:
11. Enter the speed (for example, 12(0) and press the RETURN key.
The program asks for the serial lines and transmission speed of the
next pair.
12. Repeat step 8 for all remaining machine pairs. When you have given
serial lines and speeds for all pairs, the program displays this information and asks if you wish to make corrections.
13. Enter y, if you wish to enter the serial lines and speeds again. Otherwise, enter n, to move to the next step.

9-7

XENIX

Operation~

Guide

The program displays the message:
Enter the names of users on each machine:
For machine a:
Users on a:
14. Enter the login name of a user on the given computer, then press
the RETURN key. You may enter more than one name on a line by
separating each name with a comma (,) or a space. When you have
entered all names for the given computer, press the RETURN key.
The program displays the names of the users on the computer and
asks if you wish to make corrections.
15. Entery, if you wish to enter the user names again. Otherwise, enter
n. If you enter n, the program prompts you for the names of the
users on the next computer.
16. Repeat steps 13 and 14 for all remaining computers. After you have
entered the names of users for every computer, the program
prompts you to enter any aliases:
Do you wish to enter any aliases? (yes!no)?
17. Entery, if you wish to enter aliases. Otherwise, enter n, to complete
the installation. H you enter y, the program displays the message:
Each alias consists of two parts, the first is the alias name,
the second is a list of one or more of the following:
valid user names
previously defined aliases
machine names
Aliases:
18. Using the list of aliases you created when planning the network,
enter the name of an alias and press the RETURN key. The program
displays the message:
Users! Aliases:
19.

H the alias is to name a single user, enter the login name of that user
and oress the RETURN kev. The orOQTam then oromots for another
alias£.
.,
£..,
£
£
H, on the other hand, the alias is to name several users, enter the
login names of the users. If one or more of the users to be named by
the alias are already named by other aliases, enter the aliases instead
of the login names. H all the users on one computer are to be named
by the alias, enter the machine name instead of the login names. In

9-8

Building a Micnet Network

any case, make sure that each item entered on the line is separated
from the next by a comma (,) or a space. If there are more items than
can fit on the line, enter a comma after the last item on that line and
press the RETURN key. You can then continue on the next line.
After all names and aliases have been entered, press the RETURN
key. The program then prompts you for another alias.
20. Repeat steps 17 and 18 for all remaining user aliases in your list.
When you have given all aliases, press the RETURN key. The program displays a list of all aliases and their users and asks if you wish
to make corrections.
21. Entery, if you wish to enter all aliases again. Otherwise, enter n, to
complete the installation.
Once you direct netutil to complete the installation, it copies the information you have supplied to the network files, displaying the name of each file
as it is updated. Once the files are updated, you may use the save option to
copy the Micnet files to floppy disk.
9.3.2 Saving the Micnet Files
You can save copies of the Micnet files on backup media (floppy disk) or
hard disk with the save option of the netutil program. Saving the files
allows you to transfer them to the other computers in the network. Before
you can save the files to a floppy you need to format a floppy disk (see the
section "Formatting Floppy Disks" in Chapter 4). Saving the files to the
hard disk enables you to use uucp(C) to transfer the files to other
machines.
To save the files, follow these steps:
1. Login as the super-user.
2. Enter:
netutil
Press the RETURN key. The program displays the network utility
menu.
3. Enter the number 2, and press the RETURN key. The program
displays the message:
Save to /dev/fdx (yes/no)?
where x is a drive number.

9-9

XENIX Operations Guide

4. If you wish to use the specified disk drive, insert a blank, formatted
floppy disk into the drive, wait for the drive to accept the disk, then
enter "yes", and press the RETURN key. If you do not wish to use
the drive, enter "no", and press the RETURN key. The program
displays a prompt asking you for the filename of the disk drive (or
file) you wish to use. Insert a blank, formatted disk into your chosen
drive, wait for the drive to accept the disk, then enter the filename
of the drive. The name of the default backup device (disk drive) is
specified in the file letcldefaultlmicnet. This device can be changed
depending on system configuration.
In either case, the program copies the Micnet files to the floppy
disk.

Remove the floppy disk from the drive. Using a soft tip marker (do
not use a ball point pen), label the disk "Micnet disk".

As soon as all files have been copied, you can transfer them to all computers in the network.
9.3.3 Res toring Micnet Files
The last step in building a Micnet network is to copy the Micnet files from
the Micnet disk to all computers in the network. Do this with the restore
option of the netutil program. For each computer in the network, follow
these steps:

1. Login as the super-user.
2.

Enter:
netutil
Press the RETURN key. The program displays the network utility
menu.

3. Enter the number 3, and press the RETURN key. The program
displays the message:
Restore from Idev/fdx (yes/no)?
wherexis the number of a drive.

9-10

Building a Micnet Network

If you wish to use the specified disk drive, insert the Micnet disk into

the drive, wait for the drive to accept the disk, then enter "yes" and
press the RETURN key. If you do not wish to use the drive, enter
"no" and press the RETURN key. The program displays a prompt
asking you for the filename of the disk drive you wish to use. Insert
the Micnet disk into your chosen drive, wait for the drive to accept
the disk, then enter the filename of the drive.
In either case, the program copies the network files to the appropriate directories, displaying the name of each file as it is copied.
Finally, the program displays the message:
Enter the name of this machine:
5.

Enter the machine name of the computer you are using and press
the RETURN key. The program copies this name to the new
letclsystemid file for the computer. If necessary, it also disables the
serial lines to be used on the computer, preparing them for use with
the network.

When the files have been copied, you may start the network with the start
option.
9.4 Starting the Network
Once the Micnet files have been transferred to a computer, you can start
the network with the start option of the netutil program. The start option
starts the Micnet programs which perform the tasks needed to communicate between the computers in the network.
To start the network, follow these steps for each computer in the network:

1. Log in as the super-user.
2.

Enter:
netutil
Press the RETURN key. The system displays the network utility
menu.

3. Enter 4, and press the RETURN key. The program searches for the
letclsystemid file. If it finds the file it starts the network. If it does
not, it prompts you to enter the machine name of the computer and
then creates the file. The program also asks if you wish to log errors
and transmissions. In general, these are not required except when
checking or testing the network. When starting the network for the
first time, enter n in response to each question and press the
RETURN key.

9-11

XENIX Operations Guide

Once the network has started, you may move to the next computer and
start the network there.
Note that, for convenience, you can let each computer start the network
automatically whenever the system itself is started. Simply include the
command:
netutil start
in the system initialization file, lete/re, of each computer. To add this command, use a text editor as described in the section "Changing the letc/rc
File" in Chapter 8. You can add the -x or -e options to this command line
if you wish to log transmissions or errors. Even if you do not use these
options, Micnet copies a log in and log out message to the system LOG file
each time you start and stop the network. This means you will need to
periodically clear the file. See the section "Clearing Log Files" in Chapter

5.
9.S Testing a MicnetNetwork
After you have started a network for the first time, you should test the network to see that it is properly installed. In particular, you must determine
whether or not each computer is connected to the network.
To test the network, you will need to know how to use the mail command
(see Chapter 3, "Mail," in the XENIX User's Guide). The following sections explain how to test the network and how to correct the network if
problems are discovered.
9.S.1 Checking the Network Connections
You can make sure that all computers are connected to the network by
mailing a short message to all (the alias for all users in the network) with the
mail command. Follow these steps:
1. Choose a computer.
2. Login as the super-user.
3. Use the mail command (see the XENIX User's Guide) and the all
."1;.",,, tn n->.,,;1 thA n->"""'''v.

Micnettest
to all users in the network.

9-12

Building a Micnet Network

4. Check the mailboxes of each user in the network to see if the message was received. To check the mailboxes, log in as the super-user
at each computer and use the cat command to display the contents
of each user's mailbox.
The name of each user's mailbox has the form:

lusrl spoollmailllogin- name
where login- name is the user's login name.
The network is properly installed when all users have received the message.
If the users at one or more computers fail to receive the message, the computers are not properly connected to the network. To fix the problem, you
need to locate the computer which has failed to make a connection. The
next section explains how to do this.
9.5.2 Using the LOG File to Locate a Problem
You can locate a problem with connections by examining the LOG files on
each computer in the network. The LOG files contain records of the
interaction between each pair of computers. There are two LOG files for
each pair of computers (one file on each computer). The LOG files on any
given computer are kept in subdirectories of the /usr/spool/micnet directory. Each subdirectory has as its name the machine- name of the other
computer in the pair. You can examine the contents of a LOG file by entering:
cat /usr/spoollmicnet/remote/machine- name/LOG
and pressing the RETURN key. The machine- name must be the name of a
computer that is paired with the computer you are using.
Each LOG file should contain a "startup message" which lists the name of
each computer in the pair, and the serial line through which the pair is connected. It also shows the date and time at which the network was started.
The message should look like:
daemon.mn: running as MASTER
Local system: a
Remote system: b, IdevlttyOO
Tue Sep 24 22:30:351985
A startup message is added to the file each time the network starts successfully. H the message is not present, one or more of the the network files
and directories cannot be found. Make sure that you have used the res tore
option to transfer all the network files to the computer. Also, make sure
that the /etclsystemid file contains the correct machine name for the given
computer.
9-13

XENIX Operations Guide

Each LOG file will contain a "handshake" message if the connection
between the computer pair has been established. The message:
first handshake complete
is added to the file on a successful connection. If the message is not
present, make sure that the network has been started on the other computer in the pair. The network must be started on both computers before
any connection can be made. If the network is started on both computers
but the handshake message does not appear, then the serial line may be
damaged or improperly connected. Check the serial line to make sure that
the cable is firmly seated and attached to the correct RS-232 connectors on
both computers. If necessary, replace the cable with one known to work.
If both the startup and handshake messages appear in the LOG file but the
network is still not working, then there is a problem in transmission. You
can create a record of the transmissions and errors encountered while
transmitting by restarting the network and requesting Micnet to log all
transmissions and errors. Just enter y (for "yes") when the start option
asks if you wish to log errors or transmissions.

Error entries contain the error messages generated during transmission.
Each message lists the cause of the error and the subroutine which
detected the error. For example, the message:
rsync: bad Probe resp: 68
shows that the rsync subroutine received a bad response (character 68 hexadecimal) from the other computer. You may use this information to track
down the cause of the problem. One common problem is stray information being passed down the serial line by electronic noise. Make sure that
the serial line's cable is properly protected against noise (for example, that
the cable does not lie near any electric motor, generator, or other source of
electromagnetic radiation). Also make sure the cable is in good condition.
Transmission entries contain a record of normal transmissions between
computers. Each entry lists the direction, byte count, elasped time, and
time of day of the transmission. For example, the entry:
rx: Oc 0122:33:49
shows that 12 characters (Oc hexadecimal) were received (rx) at 22:33:49.
The elasped time for the transmission \:'las 1 second. You can use the
records to see if messages are actually being transmitted.

9-14

Building a Micnet Network

9.5.3 Stopping the Network
You can stop the network with the s top option of the netutil program. This
option stops the Micnet programs, stopping communication between
computers in the network.
To stop the network, follow these steps on each computer in the network:

1. Login as the super-user.
2.

Enter:
netutil
Press the RETURN key. The program displays the network utility
menu.

3. Enter 5, and press the RETURN key. The program stops the network programs running on the computer.

9.5.4 Modifying the MicnetNetwork
You can modify a Micnet network at any time by changing one or more of
the Micnet files. You can reinstall the network with the netutil program.
For very small changes (for example, correcting the spelling of an alias),
you can modify the Micnet files directly with a text editor. The files and
their contents are described in detail in the M section of the XENIX Reference Manual.
Before making any changes to a file, a copy should be made. You can make
a copy with the cp command. You can replace an old file with the updated
file using the mv command. Once one or more files have been changed on
one computer, the files mustbe transferred to the other systems in the network using the save and restore options. These options can only be used
after you have stopped the network.
Note that changes to the aliases file will not be incorporated into the system
until the aliashash program is executed. This program produces the
aliases. hash file needed by the network to resolve aliases. See aliashash
(M) in the XENIX Reference Manual for a description of this command.
9.6 Using a Uucp System
You can send and receive mail from other Micnet sites by installing a uucp
system on one computer in your site. A uucp system is a set of XENIX programs that provide communication between computers using ordinary
telephone lines.

9-15

XENIX Operations Guide

To use a uucp system with your Micnet network, follow these steps:
1. Install a uucp system on one computer in the Micnet site. Installation of a uucp system requires a modem and the uucp software provided with the XENIX Operating System. See the XENIX User's
Guide for complete details.
2. Add the entry:
uucp:
to the maliases file of the computer on which the uucp system is
installed.
3. For all other computers in your site, add the entry:

uucp:machine- name:
to the maliases file. The machine- name must be the name of the
computer on which the uucp system is installed. One may also use
the longer form of entry on the computer on which the uucp system
is installed.
You can test the uucp system by mailing a short letter to yourself via
another site. For example, if you are on the site "chicago", and there is
another Micnet site named "seattle" in the system, then the command:
mail seattle!chicago!johnd
will send mail to the "seattle" site, then back to your "chicago" site, and
finally to the user "johnd" in your Micnet network. Note that a uucp system usually performs its communication tasks according to a fixed
schedule, and may not return mail immediately.

9-16

Appendix A
XENIX Special Device Files
A.I

Introduction

A-I

A.2

File System Requirements

A.3

Special Filenames

A-I

AA Block Sizes A-I
A.S

Gap and Block Numbers

A-2

A.6 Terminal and Network Requirements

-A-i-

A-2

XENIX Special Device Files

A.1 Introduction
This appendix contains information needed to create file systems and add
terminals to the XENIX system. For a full description of the special files
mentioned here, see section M-HW of the XENIX Reference Manual
found at the back of this volume.
A.2 File System Requirements
Many of the file system maintenance tasks described in this guide require
the use of special filenames, block sizes, and gap and block numbers. The
following sections describe each in detail.
A.3 Special Filenames
A special filename is the name of the device special block or character I/O
file, which corresponds to a peripheral device, such as a hard or floppy disk
drive. These names are required in such commands as mkfs, mount, and
dfto specify the device containing the file system to be created, mounted,
or searched.
The following table lists the special filenames and corresponding devices,
for hard and floppy disk drives on a typical computer.

Device Special Filenames - Disks
Filename

Disk Drive

/dev/fdO

Floppy Drive 0

/dev/fd1

Floppy Drive 1

/dev/hdOO

Entire hard disk

/dev/root

Root file system

/dev/usr

User file system

A.4 Block Sizes
The block size of a disk is the number of blocks of storage space available
on the disk, where a block is typically 512 or 1024 bytes of storage. Refer to
the machine(HW) manual page or use cmchk(C) to determine the size of
blocks on your system. Many commands require input that defines the
number of blocks to be operated on. Other commands report disk space
in terms of 512 byte blocks, in particular df, du, Is, Ie, and find. A 500 byte
file on a 1024 byte block file system is reported as using 2 blocks by these
utilities, as the file uses one system block which is equivalent to two 512
A-I

XENIX Operations Guide

byte blocks. The size of a 10 megabyte hard disk in 1024 byte blocks is 9792.
Note that some of the blocks on the disk are reserved for system use and
cannot be accessed by user programs. The block size of a typical floppy
disk depends on the total storage capacity of the disk, as given by the
manufacturer.
A.S Gap and Block Numbers
The gap and block numbers are used by the mkfs, and possiblyfsck, commands to describe how the blocks are to be arranged on a disk. The following table lists the gap and block numbers for the floppy and hard disks used
with a typical computer.
Disks

Gap

Block

Floppy Disk, 48ds9

Floppy Disk, 96ds15

Hard Disk

The number of blocks can also be determined by multiplying the number
of sectors per track (usually 17) by the number of heads on the hard disk.
A.6 Tenninal and Network Requirements
The enable and disable commands are used to add and remove terminals
on a system. The install option of the netutil program is used to build a network. The preceding commands and option require the names of the serial
lines through which a terminal or network is to be connected. The following table lists the device special filenames of the two serial lines (actually
two serial ports either with or without modern control). The character I/O
files correpsonding to these serial lines can be found in the Idev directory.
Note that the files Idevlconsole and Idevitty02through IdevlttylOrepresent
"hardwired" devices and are not available for connection to terminals or
hardware. Also, refer to serial(HW) for more information on serial lines.

A-2

Filename

Line

Idev/tty1a

main serial line (without modern control)

I dev Itty2a

alternate serial line (without modern control)

Idev/tty1A

main serial line (with modern control)

Idev/tty2A

alternate serial line (with modern control)

AppendixB
XENIX Directories
B.l

Introduction B-1

B.2 The Root Directory B-1
B.3 The Ibin Directory B-1

BA The Idev Directory B-1
B.S

The Ietc Directory B-2

B.6 The IUb Directory B-3
B.7 The Imnt Directory B-3
B.8 The Itmp Directory B-3
B.9 The Iusr Directory B-3
B.lO Log Files

B-4

- B-i-

XENIX Directories

B.l Introduction
This appendix lists the most frequently used files and directories in the
XENIX system. Many of these files and directories are required for proper
XENIX operation and must not be removed or modified. The following
sections briefly describe each directory.
B.2 The Root Directory
The root directory (I) contains the following system directories:
Ibin
I dev
I etc
llib
Imnt
lusr
Itmp

XENIX command directory

Device special directory
Additional program and data file directory
C program library directory
Mount directory (reserved for mounted file systems)
User service routines (may contain user home directories)
'Temporary directory (reserved" for temporary files
created by programs)

All of the above directories are required for system operation.
The root directory also contains a few ordinary files. Of these files, the
most notable is the xenix file which contains the XENIX kernel image.
B.3 The Ibin Directory
The Ibin directory contains the most common XENIX commands, that is,
the commands likely to be used by anyone on the system. The following is
a list of a few of the commands:
basename
cp
date
dump
dumpdir

echo
expr
fsck
login
mv

passwd
rm

sh
sleep
stty

su
sync
tar
restor
test

These commands and all others in the Ibin directory are required.
B.4 The Idev Directory
The Idev directory contains special device files which control access to
peripheral devices. All files in this directory are required, and must not b e
removed.

B-1

XENIX Operations Guide

The following is a list of the files:
Idev/console System console
Idev/lp
Lineprinter
Idev/mem Physicalmemory
Idev/null
Null device (used to redirect unwanted output)
Idev/rXX
Unbuffered interface to corresponding device name
Idev/root
Root file structure
Idev/swap Swap area
Idev/ttyXX Terminals
Idev/tty
The terminal you are using

B.S The lete Directory
The lete directory contains miscellaneous system program and data files.
All files are required, but manymaybe modified.
The following program and data files must not be removed or modified:

letc/mnttab
letc/mount
I etc I mkfs
letc/init

Mounted device table
For mounting a file structure
For creatin g a file structure
First process after boot

The following data files may be modified, if desired. No files may be
removed.
letc/passwd Password file
letc/rc
Bootup shell script
letc/ttys
Terminal set up
letc/termcap Terminal capability map
letc/motd Message of the day

B-2

XENIX Directories

The data files in the directory letcldefault contain default information
which is used by system commands (see default(M». The following data
files may be modified. No files may be removed.
/ etc/default/b ackup
/ etc/default/boot
/etc/default/cron
/ etc/default!dumpdir
/ etcldefault/login
/etc/default/lpd
/ etcldefault/ micnet
/ etc/default/mkuser
/ etc/default/msdos
/ etc/default/passwd
/etc/default/quot
/etc/default/restor
/ etc/default/ su
/ etc/default!tar

backup (C) default information
autoboot(M) information
cron(C) default logging information
dumpdir(C) default information
login(M) default information
Ip(C) default information
micnet(M) default information
mkuser(C) default information
Location of DOS disks (A:, B:, ... )
passwd(C) default information
quot(C) default information
res tore (C) default information
su(C) default information
(Note that you must create
this file yourself.)
tar(C) default information

B.6 The llib Directory
The llib directory contains runtime library files for C and other language
programs. The directory is required.
.
B.7 ThelmntDirectory

The /mnt directory is an empty directory reserved for mounting removable
file systems.
B.8 The /tmp Directory
The Itmp directory contains temporary files created by XENIX programs.
The files are normally present when the corresponding program is running,
but may also be left in the directory if the program is prematurely stopped.
You may remove any temporary file that does not belong to a running program.
B.9 The JUST Directory
The lUST directory contains the home directories of all users on the system.
It also contains several other directories which provide additional XENIX
commands and data files.

B-3

XENIX Operations Guide

The lusTlbin directory contains more XENIX commands. These commands are less frequently used or considered nonessential to XENIX system operation.
The lusrlinclude directory contains header files for compiling C programs.
The /usrllib directory contains more libraries and data files used by various
XENIX commands.
The lusrlspool directory contains various directories for storing files to be
printed, mailed, or passed through networks.
The lusr/tmp directory contains more temporary files.
The lusr/adm directory contains data files associated with system administration and accounting. In particular, the lusrladm/messages file contains
a record of all error messages sent to the system console. This file is especially useful for locating hardware problems. For example, an unusual
number of disk errors on a drive indicates a defective or misaligned drive.
Since messages in the file can accumulate rapidly, the file must be deleted
periodically.
B.10 Log Files

A variety of directories contain log files that grow in size during the normal
course of system operation. Many of these files must be periodically
cleared to prevent them from taking up valuable disk space (see the section
"Clearing Log Files" in Chapter 5). The following table lists the files (by
full pathname) and their contents.
Filename

Description

letc/ddate
Records date of each backup.

lusr/ adm/pacct
Records accounting information; grows rapidly when process
accounting is on.
/usr/ adm/messages
Records error messages generated by the system when
started.

letc/wtmp
Records user logins and logouts.
/usr/adm/sulog
Records each use of the su command; grows only if option is
set in the letcldefaultlsu file. You must create
B-4

XENIX Directories

/etc/default/su. See su(C) in the XENIXReference.

lusr/libl cronl cronlog
Records each use of the at and cron commands.
lusrl spool/micnet/remote/* ILOG
Records transmissions between machines in a Micnet network. The * must be the name of a remote machine connected
to the current machine.
For more information on these files, see the appropriate sections in the
XENIX Reference.

B-S

Index
Ctrl-U key 1-2

A
accept command 7-25
AUTO
gettydefs file 7-5

B
BACKSPACE key 1-2
Backup system see File system
Ibin directory contents B-1
Block
arrangement on disk A-2
defined 5-2
number A-2
ownership 5-3
size A-I
Bootstrap program 2-1
BREAK key 1-2

c
C program
compilation header files B-4
library files B-3
Checking terminal settings 7-7
chmod command
permissions change 4-7
special file protection 4-11
Command
/etc/rc file, inclusion 8-6
location
Ibin directory B-1
/usrlbin directory B-4
.profile file, inclusion 8-6
Computer
see also micnet network,
machine name
micnet network
connection test 9-12
Copying
directories to floppy disk 6-6
files to floppy disk 6-6
floppy disks 4-11
Core file, described 5-5
Ctrl-\ key 1-2
Ctrl-H key 1-2
Ctrl-Q key 1-2
Ctrl-S key 1-2

D
Daily backup see File system
dd
copying a floppy 4-13
/dev directory
special file 4-11, B-1
Device special filenames A-I
dfcommand
free space display 5-2
diaUogin
gettydefs file entry 7-5
Directory
access permissions see Permissions
block usage 5-3
location 5-4
making copies on floppy disk 6-6
permissions see Permissions
removal 3-11
disable
command 7-10
lineprinters 7-26
terminal 7 -10
Disk
block number A-2
block size A-I
damage see File system
free space see File system
gap number A-2
security 4-10
usage 5-3
diskcp
formatting a floppy 4-12
du command 5-3

E
enable
command 7-2, 7-26
lineprinters 7-26
terminal 7-2
Error messages B-4
ESCAPE key 1-2
/etc directory contents B-2
/etc/default/archive file
contents B-3
/etc/defaultlbackup file
contents B-3
/etc/defaultlboot file
contents B-3
/etc/default/cron file

1-1

Index
/etc/default/cron file (continued)
contents B-3
/etc/default/dumpdir file
contents B-3
/etc/default/filesys file
contents B-3
/ etc/default/login file
contents B-3
/etc/default/lpd file
contents B-3
/etc/default/micnet file
contents B-3
/etc/default/mkuser file
contents B-3
/etc/default/msdos file
contents B-3
/etc/default/passwd file
contents B-3
/etc/default/quot file
contents B-3
/etc/default/restor file
contents B-3
/etc/default/su file
contents B-3
/etc/default/tar file
contents B-3
/etc/default directory
contents B-3
/ etc/gettydefs file 7-3
changing the file 7-5
/etc/group file, modification 3-7
/etc/motd file
contents 8-7, B-2
free space reminder 5-1
modification 8-5, 8-7
/etc/passwd file
user entry 3-4
user ID change 3-10
/etc/password file
contents B-2
/etc/rc file
contents 8-5, B-2
micnet network startup 9-12
modification 8-5
/etc/systemid file
machine name contents 9-2
micnet network startup 9-11
/etc/termcap file, terminal 7-9
contents B-2
Execute permission 4-6

F
HIe
access
permissions see Permissions
backup see File system

1-2

HIe (continued)
copies on floppy disk 6-6
core file, described 5-5
damage see HIe system
data loss 5-6
determining block size 5-3
hidden file removal 8-3
inaccessibility 5-6
initialization file see Initialization file
location 5-4
log 5-5
log clearing 5-5
lost file restoration see File system
making copies on floppy disk 6-6
name
device special files A-1
permissions see Permissions
recovery from backup see File system
removal
unused files 5-2
repair see File system
restoration see HIe System
system see HIe system
temporary file removal 5-5
time of last access 5-4
unused file removal 5-2
File system
amount of free space 5-1
automatic check 5-7
backups
creation 6-3
daily 6-2
disk storage 6-2
floppy disk labeling 6-4
frequency 6-1
listing procedure 6-4
periodic 6-2
restoration 6-5
schedule 6-2
sysadmin program 6-1
sysinfo account 6-1
tar command 6-1
cleaning 2-1
copies 6-1
creation 4-1
damage
causes 5-6
restoration 5-6
data loss 5-6
defined 4-1
destruction 4-2
display free space 5-2
expansion 5-6
free space
display 5-2
lack of 5-1
maintaining 5-1
restoration 8-3
maintenance 5-1

Index
HIe system (continued)
mounting
automatic 4-4
initialization files 8-5
procedure 4-1, 4-3
repair 5-6
root 4-1
unmounting 4-1, 4-4
find command 5-4
Floppy disk
block size A-I
bootable floppy disk 7-40
copying 4-11
damage see HIe system
file system creation 4-1
formatting 4-5
micnet file saving 9-9
root filesystem disk 7-40
security 4-10
Formatting floppy disks 4-5
Free space see HIe system
fsck command 5-6

G
Gap number A-2
getty program 7-3
-c option 7-7
gettydefs file
alternate login programs 7-5
autologin 7-5
changing the file 7-5, 7-3
Group
access 3-8
changing the ID 3-8
creation 3-7
defined 3-7
ID 3-2,3-7
name 3-2, 3-7
number 3-2
permissions see Pennissions

H
haltsys command 2-5
Hard disk
adding a second
installing user accounts 7-38
using a mountable file system 7-30 7-38
block size A-I
'
damage see HIe system
mounting 7-37
Hayes modem with XENIX 7-16
Hidden file removal 8-3

Home directory
removal 3-11
setting, initilization files 8-5
user account 3-1

I
Initialization file
contents 8-5
/etc/motd file see /etc/motd file
/etc/rc file see /etc/rc file
modification 8-5
.profile see .profile file
Internal memory
addition of 7-28
INTERRUPT key 1-2

K
Keyboard, described 1-2
kill command
runaway process stopping 8-2
KILL key 1-2

L
I command
listing pennissions 4-6
/lib directory contents B-3
Lineprinter
accept command 7-25
adding
Ipinit command 7-19, 7-18
creating init device
Ipinit command 7-23
disable command 7-26
dumb model interface 7-26
enable command 7-26
interface programs 7-26
Ipinit command 7-23
Ipmove command 7-24
Ipsched program 7-22
Ipshut command 7-23
Ipstat command 7-Z2
moving requests
lpmove command 7-24
reject command 7-25
scheduler program
lpsched program 7-22
solving problems 8-1
Login
group 3-8

1-3

Index
Login (continued)
name see Login name
programs, alternate
gettydefs file 7-5
diaUogin 7-5
LOG file
contents 9-13
micnet network
connection error location 9-13
Log files 5-5
Login name
micnet network
entry 9-8
new user 3-1, 3-2
sending mail 5-4
lpinit command 7-19,7-23
lpmove command 7-24
lpsched program
finding out the status 7-22
lpshut command 7-23
lpstat command 7-22
stopping Ipsched 7-22, 7-23, 8-1
lpshut command 7-23
lpstat command 7-22, 8-1

M
Mailbox removal 3-13
mail command
message 5-4
micnet network
alias 9-4
testing 9-12
lusrtspool directory B-4
Memory
adding internal 7-28
parity errors 7-29
removing internal 7-29
Message
system wide message 5-2
Message of the day file see tetc/motd file
micnet network
alias
description 9-4
entry 9-8
preparation 9-5
composition 9-1
computer
connection test 9-12
machine name 9-2
connection see Computer
I etctsystemid file
machine name contents 9-2
system startup 9-11
file
copying to computers 9-10
creation 9-5

1-4

micnet network (continued)
file (continued)
modification 9-15
restoration 9-10
saving 9-9
transfer 9-5
forward alias.9-4
group alias
creation 9-5
handshake message 9-13
install option 9-5
LOG file
connection error location 9-13
contents 9-13
machine alias 9-4
machine name
choice 9-2
file entry 9-6
saving 9-2
modification 9-15
netutil program
information required 9-1
install option 9-5
network building 9-5
restore option 9-5, 9-10
save option 9-5, 9-9
start option 9-11
stop option 9-15
planning 9-1
restore option 9-5, 9-10
save option 9-5, 9-9
serial line
assignment 9-3
name entry 9-7
transmission speed 9-4
serial topology
description 9-2
standard alias 9-4
star topology
description 9-2
start option 9-11
startup procedure 9-11
stop option 9-15
stopping 9-15
testing 9-12
topology
map 9-3
types 9-2
transmission speed
assignment 9-4
file entry 9-7
mkfs command
file system creation 4-1
mkuser program
creating a user account 3-1
passwd 3-3
shell type 3-3
stopping 3-2
tmnt directory, mounted file systems 4-3, B-3

Index
Modem Usage
available serial lines 7-13
dialing in 7-16
dialing out with cu 7-14
Hayes settings 7-16
L-devices file 7-13
Modes of operation, described 2-2
more command 8-6
mount command
file system mounting 4-1 4-3
Multiple screens, access 7-'1
Multiscreen 7-1

N
netutil program see micnet network
New user 3-1
newgrp command 3-8
Normal operation
mode 2-2
stopping 2-4

o
Operating system
loading 2-1
Out of space message 8-3

p
Parallel lineprinter, adding 7-18
Parity errors, memory 7-29
passwd command 3-5
Password
change procedure 3-5
complexity, system aCcess security 4-11
forgotten 8-3
new user 3-3
user account 3-1
Periodic backup see File system
Permissions
change 4-7
description 4-5
execute permission 4-6
fields 4-6
group permissions 4-5
initial assignment 4-7
levels 4-5
no permission 4-6
other permissions 4-5
r~d permission 4-6
search permission 4-6

Permissions (continued)
special files 4-11
user permissions 4-5
write permission 4-6
PID
~illing, runaway process stopping 8-2
Printer
see Lineprinter
Printing scheduler
see Ipsched program
Process
runaway 8-2
stopping 8-2
.profile file
contents 8-6
modification 8-5, 8-6
removal 3-13
setting the terminal type 7-10
Program
runaway process 8-2
start, initilization files 8-5
termination, core file placement 5-5

Q
quotcommand
block ownership display 5-3

R
rcp command 9-1
Read permission 4-6
reject command 7-25
remote command 9-1
rm command 8-3
rmuser command
limitations 3-13
stopping 3-13
user account removal 3-11
root
directory backup 6-1
directory contents B-1
super-user login name 2-3
symbol (/) 4-1

s
Screens, multiple
access 7-1
console 7-1
Search permission 4-6
Serial console 7-12

1-5

Index
Serial line
adding terminals 7-2
device special filenames A-2
micnet network
assignment 9-3
name entry 9-7
transmission speed 9-4
Serial ports, configuring 7-11
Setting
console 7-12
terminal lines 7-3
terminal type 7-9
Shutdown
command 2-4
improper shutdown
file check 5-7
Slash (I), root symbol 4-1
Special file
protection 4-11
security 4-11
Starting the system 2-1
Stopping the system 2-4
Super-user
account 1-1
leaving the account 2-3
login name (root) 2-3
login 2-3
password 1-1
precautions 2-3
prompt (*) 2-3
restricted use 1-2
special file access 4-11
Super-user password
secrecy 4-11
sysadmin program
creating backups 6-3
description 6-1
file restoration 6-5, 8.-3
listing backups 6-4
sysinfo account
backups 6-1
System
access security 4-11
accounts 3-13
adding disk storage 4-1
administration directory B-4
cleaning the file system 2-1
inoperable system restoration 8-4
maintenance
account 1-1
mode 2-2, 2-5
manager
backups 6-1
duties 1-1
file access 4-1
file system maintenance 5-1
free space maintenance 5-1
initia1i7.ation fiJes modification 8-5
micnet network maintenance 9-1

1-6

System (continued)
manager (continued)
super-user account 1-1
system maintenance mode 2-2
user account creation, maintenance 3·
messase 5-2
physical security 4-10
problems, fixing 8-1
reinstallation
security 4-10
starting 2-1
stopping 2-4
System wide message 5-2

T
tar command
creating copies 6-6
description 6-2
restoring copies from disk 6-6
Temporary file removal 5-5
Terminal
adding 7-2
disabling 7 -10
enabling 7-2
lockup, runaway process 8-2
nonechoing terminal 8-1
setting the type 7-9
type setting
initialization files 8-5
TERM variable 7-9
Time
file access 5-4
Itmp directory contents B-3
tty line see Serial line

u
umount command 4-1, 4-4
User
account
adding 3-1
comments 3-3
directory removal 3-11
file removal 3-11
login name 3-2
.profile file modification 8-6
removal procedure 3-11
block ownership display 5-3
changing the ID 3-10
group see Group
ID 3-10
login group see Login group
new user 3-1

Index
User (continued)
password see Password
permissions see Permissions
Using a serial console 7-12
Iusr directory contents B-4
lusr/spoo1l1p/model file 7-26

w
wall command 5-2
Write permission 4-6

x
xenix file B-1
XENIX keys, described 1-2

1-7

Contents
Hardware Dependent (HW)
8087
intro
boot
clockrate
cmos
console

Cd
hd
keyboard
Ip, Ipu, Ipl, Ip2
machine
parallel
ramdisk
serial, ttyl[a-h],
ttyl[A-H],
tty2[a-h],
tty2[A-H]
scre.en, tty[Ol- n],
color,
monochrome,
ega,pga
stty
tape
terminal

Math co-processerfor Intelfamily CPU s.
Introduction to miscellaneous features and files.
XENIX boot program.
Changes clock rate.
Displays and sets the configuration data base.
Computer screen.
Floppy devices.
Internal fixed disk drive.
Name and function of special keyboard keys.
Line printer device interfaces.
Description of host machine.
Interface to parallel ports.
Memory block device.

Interfaces to serial ports.

Display adapter and video monitor.
Sets options for the video monitor.
Cartridge tape device.
Login terminal.

INTRO (HW)

Name
intro - Introduction to machine related miscellaneous features and
files.
Description
This section contains information useful in maintaining the system.
Included are descriptions of files, devices, tables and programs that
are important in maintaining the entire system that are directly
related to the kind of computer the system runs on. This section is
intended for use with the 86 family of Intel CPUs, specifically 8086,
8088, 80186, and 80286 based computers.

May 1, 1986

Page 1

BOOT (HW)

Name
boot - XENIX boot program.
Description

boot is an interactive program used to load and execute standalone
XENIX programs. It is used primarily for loading and executing the
XENIX kernel, but can load and execute any other programs that

are linked for standalone execution. boot is a required part of the
XENIX Operating System and must be present in the root directory
of the root file system to ensure successful loading of the XENIX

kernel.
The boot program is invoked by the system each time the computer
is started.
For diskette boot, the procedure has three stages:

1. The ROMs load the boot block from sector 0 of the floppy,
where sector 0 of the disk is the same as sector 0 of the filesystern.
2. The boot block-loads !boot from the floppy filesystem.
3. !boot executes and prompts the user.
For fixed disk boot, the procedure has five stages:

1. The ROMs load in the masterboot block from sector 0 on the
hard disk.
2. The masterboot block then loads the partition boot block from
sector 0 of the active partition (see fdisk(C».
3. Then, boot! is loaded from the next four tracks.
4. boot1loads !boot from the XENIX file system.
5. /boot executes and prompts the user.
!boot and Ixenix may lie on tracks that have been mapped by
badtrk(M) .
The fixed disk boot procedure is invoked if the diskette drive is
empty.

December 19, 1986

Page 1

BOOT (HW)

When first invoked, boot prompts for the location of a program to
load by displaying the message:
XENIX System V
Boot
To specify the location of a program, a device and filename must
be given. The filename must include the full pathname of the file
containing the standalone program. You can display a list of the
current allowable device names by typing the question mark (?).
The format for the device and pathname is as follows:
xx(m, 0 )filename
or
xx(m)filename
where:
xx = device name
('hd' for the hard disk or 'fd' for diskette device)
m = minor device number
(40 for the root file system on the hard disk)
o = offset in the partition (usually 0). This is optional.
filename = standard XENIX pathname. Must start with a
slash if the program is not in the root directory.
All numbers are in decimal. See the manual pages for hd (HW) and
fd (HW) for minor device numbers of these devices. Specifying the
offset is optional. The location of the program to be loaded must
always be entered first on the command line and be present if other
boot options are specified either on the command line or in
Jetcl defauItlboot.
If you want boot to pause and wait for a before executing the program that it loads, enter the word "prompt" on the
command line. For example, if you enter "prompt" and press
, boot prints the following message and waits for you
to press the return key again:
I

Loaded, press .-·
The prompt can be changed to another string as in this example:
prompt="change diskettes now"
boot loads xenix from the diskette, prints the message "change
diskettes now", and waits for to be pressed. No other
characters can appear between prompt, the "=" sign and. the
prompt string, although string may contain spaces. When you press
, xenix will begin execution. "Prompt" can be set

December 19, 1986

Page 2

BOOT (HW)

either on the command line or in letc/defaultlboot. If a prompt is
not specified, boot executes the loaded program without pausing.
If you have just loaded the boot program from the distribution
diskette, simply press and boot defaults to the correct

values.
To load XENIX from a hard disk, enter:
hd(40,O)xenix
To use the default boot string specified in letc/defaulUboot, simply
press when the system displays the boot prompt, and
boot uses the values specified by DEFBOOTSTR in
letc/defaultlboot.
If nothing is typed after a short while and LOADXENIX is set to
YES in the default root file system's letc/defaultlboot file, boot
times out and behaves as though a had been pressed,
except that an "auto" is added to the boot string. boot proceeds
through the boot procedure, and init(M) is passed a -a flag with no
"prompt" .

It is recommended that you install DOS on the hard disk before
XENIX. See the manual page for dos(C). However, once you install

DOS you can boot it at the XENIX "Boot" prompt by entering
"dos" .
During XENIX installation, a custom masterboot is placed on the
hard disk. If a non-standard disk is specified, its parameters are
stored and enabled in this masterboot.
Configuring The Kernel

boot passes any boot string typed at the boot prompt to the kernel,
except for the "prompt" string.
The kernel reads the boot string to determine which peripherals are
the root, pipe and swap devices. If no devices are specified in
either the letc/defaulUboot description or on the command line,
the default devices compiled into the kernel are used.

December 19, 1986

Page 3

BOOT (HW)

Additional arguments in the boot string can alter this default
action. These arguments have the form:
dev=xx(m,o)
or
dev=xx(m)
where:
dev = The desired system device (root[dev], pipe [dev] ,
or swap[dev])
xx, m, 0 = same as for the boot device
If any combination of root, pipe or swap is specified, then those

system devices will reside on that device, with the unspecified system devices using the defaults compiled in the kernel. Setting one
device does not affect the default values for the other system
devices.
.
Selecting The System Console
You can select the system console at boot time either by entering
the command sys tty=x at the boot prompt, or by placing the keywords SYSTTY=x in the file /etc/default/boot. The letter x
represents either a number or a string parameter.
If you use the stty=x command at boot time, boot uses the string
parameter x to pass the selected console device to the kernel. The
values of the boot string parameter systty are:

sio
scrn

Serial port COM1
Display adapter

For example, to assign the system console to the serial port at
COMl, enter this command at the boot prompt:
systty=sio
If you do not specifically set the system console at boot time, the

boot program follows these .steps to determine the system console:
boot reads /etc/deraultlboot and looks for the keywords
SYSTTY=x where x is a number that specifies the system console device.
I K indicates the serial adapter at COMl.
indicates the display adapter.

o ,l'.

If SYSTTY is not found or /etc/defauIUboot is unreadable,

boot checks for a display adapter and assigns it as the system
console.

December 19, 1986

Page 4

BOOT (HW)

H no display adapter is found, boot looks for COMl, sets the
serial port to 9600 baud, 8 data bits, 1 stop bit, and no parity,
and uses it as the system console.
Thus, to have boot automatically set the system console to the
serial port at COMl, enter this line in letc/defaultlboot:
STTY=g' .1Aliasing
A set of system devices can be aliased to a single keyword by
defining the keyword in the file letc/defaultlboot. This keyword
can then be entered on the "Boot" command line and the boot
program then reads the corresponding system devices from
letc/defaultlboot and pass them to the kernel. An alias has the
following form:
key=file [root=xx(m) pipe=xx(m) swap=xx(m) prompt[="string"]]
In all cases, the device specification can also have the format

dev=xx(m,o), where

is the offset.

For example, if you have a root file system on a· second hard disk
and want to use it, but want to boot using the xenix located on the
first hard disk, enter the following line into the letc/defaultlboot
gescription:
disk2=hd(40,O)xenix root=hd(104,O) prompt="Using second disk"
The next time you boot the system from the first hard disk, enter
"disk2" in response to the "Boot" prompt. xenix will be loaded
from the first hard disk, and when you see the message, "Using
second disk", press . xenix will now boot and use the
root file system on the second hard disk. Note that you must edit
the letc/default/boot file in the root file system on the device from
which boot will be read, in this case the first hard disk.
Boot options
Boot options can be changed via keywords in letc/defaultlboot.
The following keywords are recognized by boot:
LOA DXENIX=YES

December 19, 1986

If YES, boot automatically loads XENIX
after a moderate delay.

Page 5

BOOT (HW)

DEFBOOTSTR=string

string is used as the default boot string for
time outs and for no input on the command line. There can be no white space
between DEFBOOTSTR, the "=" sign
and string.

SYSTTY=x

If x is zero (0), the system console device
is set to the serial adapter at COMl. If x
is one (1), the system console is set to the
main display adapter.

RONLYROOT=NO

Whether or not the root filesystem is to be
mounted readonly. This should only be
set to "yes" during installation.

Diagnostics
If an error occurs, masterboot displays an error message, and locks
the system. The following is a list of the most common messages
and their meanings:
10 ERR

An error occurred when masterboot tried to read in the partition
boot of the active operating system.
BAD TBL
The bootable partition indicator of at least one of the operating
systems in the fdisk table contains an unrecognizable code.
NO OS
There was an unrecoverable error that prevented the active
operating system's partition boot from executing.

When boot displays error messages, it returns to the "Boot"
prompt. The following is a list of the most common messages and
their meanings:
bad magic number
The given file is not an executable program.
can't open
The supplied pathname does not correspond to an existing file,
or the device is unknown.
Stage 1 boot failure
The bootstrap loader cannot find or read the boot file. You
must restart the computer and supply a file system disk with the
boot file in the root directory.

December 19, 1986

Page 6

BOOT (HW)

not a directory
The specified area on the device does not contain a valid XENIX
filesystem.
zero length directory
Although an otherwise valid filesystem was found, it contains a
directory of apparently zero length. This most often occurs
when a pre- System V XENIX filesystem (with incorrect, or
incompatible word ordering) is in the specified area.
fload:read(x) =y
An attempted read of x bytes of the file returned only y bytes.
This is probably due to a premature end-of-file. It could also
be caused by a corrupted file, or incorrect word ordering in the
header.
Files
/boot
/etc/default/boot
/etc/masterboot
/etc/hdbootO
/etclhdbootl
See Also
autoboot(M), badtrk(M), fd(HW), fdisk(M), hd(HW), init(M),
sulogin(M)
Notes
The computer tries to boot off any diskette in the drive. If the
diskette does not contain a valid bootstrap program, errors occur.
The boot program cannot be used to load programs that have not
been linked for standalone execution. To create standalone programs, the '::"A option of the XENIX linker (/d(ep» and special
standalone libraries must be used.
Standalone programs can operate in real or protected mode, but
they must not be large or huge models. Programs in real mode can
use the input/output routines of the computer's startup ROM.

RONLYROOT should only be set to "yes" for installation. If it is
set to "yes" during day-to-day operations, it will prevent you making changes to the root filesystem. You will then be required to
boot from the floppy drive, edit the /etc/defaultlhoot file and
reboot.

December 19, 1986

Page 7

CLOCKRATE (HW)

Name
clockrate - Changes clock rate.
Syntax

letc/clockrate frequency
Description
letc/clockrate alters the interrupt timer clock frequency (different
from the CPU clock frequency) to bring the system clock in sync
with the computer's clock. This frequency is expressed in
Megahertz (megaHZ) and can be found in the computer's hardware
reference manual.
To set a new clockrate to 1.22878, for example, type:
# letc/clockrate 1.22878

letc/clockrate is a compiled "C" program, which modifies the kernel found in Ixenix.
letc/clockrate only needs to be run once, unless you reinstall the
XENIX distribution floppies.
Files

Ietcl clockrate
Notes
Your computer may not be able to change the clockrate with this
utility.

December 19, 1986

Page 1

CMOS (HW)

Name
cmos - Displays and sets the configuration data base.
Syntax

cmos [ address [ value ] ]
Description
The cmos command displays and/or sets the values in the CMOS
configuration data base. This battery-powered data base stores
configuration information about the computer that is used at power
up to define the system hardware configuration and to direct boot
procedures. The data base is 64 bytes long and is reserved for system operation. Refer to your computer hardware manual for more
information.
The cmos command is typically used to alter the current hardware
configuration when new devices are added to the system. When
only address is given, the command displays the value at that
address. If both address and a value are given, the command
assigns the value to that address. If no arguments are given, the
command displays the entire contents of the data base.
The CMOS configuration data base may also be examined and
modified by reading from and writing to /dev/cmos file. Because
successful system operation depends on correct configuration information, the data base should be modified by experienced system
administrators only.
The computer manufacturer's diagnostic diskette should be run
before setting the CMOS data base.
Files
/etc/cmos
/dev/cmos
Notes
Not all computers have a CMOS configuration data base. Some
computers use switches on the main system board to configure the
system. Refer to your computer hardware reference manual to
determine whether you have a configuration data base.

May 1, 1986

Page 1

CONSOLE (HW)

Name
console, tty [02-n ] - Computer screen
Syntax
#include
iocd(fd, cmd, but)
int fd, cmd;
char *buf;
Description
The console and tty [02-n] device files provide character 110
between the system and the computer screen and keyboard. Each
file corresponds to a separate teletype device. The number of
device files available, n, depends upon the amount of memory in
the computer. The system displays the number of available screens
during the boot process.
The console screens are modeled after a 25 line, 80 column ASCII
terminal. Although the color graphics, enhanced graphics and professional graphics also support 40 column lines, XENIX does not.
The console is the default device for system error messages, and is
the only teletype device open when in single user mode and during
the system boot sequence.
To get to the next consecutive screen, enter Ctrl-PrtSc using the
Ctrl key, and the PrtSc key. Any active screen may be selected by
entering alt-Fn, where Fn is one of the function keys. Fl refers to
the system console screen (Jdev/console).
The console is configurable via the mapkey(M) utilities, or at a
lower level through ioctl(S).
Keyboard processing goes through two tables. The key mapping
table maps keystrokes to either an ASCII value or a special function
and the string table maps functions keys to ASCII strings. See
keyboard (HW).

May 1,1986

Page 1

CONSOLE (HW)

Access
fd must be a file descriptor open to the console.
cmd can be one of:

GIOJ .
Refer to your computer hardware manual for information on scan
codes generated by the keyboard and character ROM arrangement.
Keyboard mapping is discussed in the XENIX Reference section

keyboard(HW).
Screen Mapping (GIO.-sCRNMAP, PIO.-sCRNMAP)
The screen mapping table maps extended ASCII (8-bit) characters
to ROM characters. It is an array [256] of char (typedef scrnmapJ)
and is indexed by extended ASCII values. The value of the elements of the array are the ROM character to display.
For example the following will change the ASCII character '#' to be
displayed as a English pound sign.

May 1, 1986

Page 2

CONSOLE (HW)

#include
change-poundO

{
scrnmap_t scrntab;

get screen mapping table of standard output

*1
if(ioctl(O, GIO_SCRNMAP, scmtab) == -1)
{
perror("screenmap read ");
exit(-l);
}
1* 156 is the ROM value of English pound sign and 30 is the ASCII
* value of '#'.

scrntab[30] = 156;
if(ioctl(O, PIO_SCRNMAP, scmtab)
{
perror("screenmap write ");
exit(-l);
}

-1)

}
Notes
ASCII characters are mapped to ROM characters via the screen

map on a per screen basis. String key mapping is also on a per
screen basis, but keyboard mapping is on a global basis. Only the
super-user can use PIOJ(EYMAP, otherwise the ioctlO call will
fail with errno set to EACCES.
ASCII characters less than 32 do not go through the screen output
mapping and thus can not be mapped to ROM characters.

May 1,1986

Page 3

CONSOLE (HW)

ANSI

Sequence

Action

Tenncap
Code

ED
(Erase in
Display)

ESC[Pn J

Erases all or part
display.
of
a
Pn=O: erases from
active position to
end of display.
Pn=1: erases from
the beginning of
display to active
position.
Pn=2:
erases entire display.

EL
(Erase in
Line)

ESC[Pn K

Erases all or part
of a line. Pn=O:
erases from active
position to end of
line. Pn=1: erases
from beginning of
line to active position. Pn=2: erases
entire line.

ECH
(Erase
Character)

ESC[PnX

Erases Pn characters

nla

CBT
(Cursor
Backward
Tabulation)

ESC[PnZ

Moves active position back Pn tab
stops.

SU
(Scroll
Up)

ESC[PnS

Scroll screen up Po
introducing
lines,
new blank lines at
bottom.

SD
(Scroll
Down)

ESC[PnT

screen
Scrolls
down Pn lines,
introducing
new
blank lines at top.

CUP
(Cursor
Position)

ESC[Pl;P2 H

Moves active position to location PI
(vertical) and P2
(horizontal).

May 1, 1986

Page 4

CONSOLE (HW)

HVP
(Horizontal
& Vertical
Position)

ESC [P1 ; P2 f

Moves active position to location PI
(vertical) and P2
(horizontal).

nla

CUU
(Cursor Up)

ESC[Pn A

Moves active position up Po number
of lines.

up (ku)

CUD
(Cursor
Down)

ESC[Pn B

Moves active position down Po number of lines.

do (kd)

CUF
(Cursor
Forward)

ESC[Pn C

Moves active posi tion Po spaces to
the right.

nd (kr)

CUB
(Cursor
Backward)

ESC[Pn D

Moves active position Po spaces
backward.

bs (kl)

HPA
(Horizontal
Position
Absolute)

ESC[Pn '

Moves active position to column
given by Po.

nla

HPR
(Horizontal
Position
Relative)

ESC[Pn a

Moves active posi tion Po characters
to the right.

nl a

VPA
(Vertical
Position
Absolute)

ESC[Pn d

Moves active position to line given
by Po.

n/a

VPR
(Vertical
Position
Relative)

ESC[Pn e

Moves active posi tion down Po number of lines.

nl a

ESC[Pn L

Inserts Po
blank lines.

new,

ESC[Pn @

Inserts Po blank
places for Po characters.

(Inse~

Line)
ICH
(Insert
Character)

May 1, 1986

Page 5

CONSOLE (HW)

DL
(Delete
Line)

ESC[Pn M

Deletes Pn lines.

DCH
(Delete
Character)

ESC [Pn P

Deletes Pn number
of characters.

CPL
(Cursor to
Previous
Line)

ESC[PnF

Moves active position to beginning of
line, Pn lines up.

nla

CNL
(Cursor
Next
Line)

ESC[PnE

Moves active position to beginning of
Pn
line,
lines
down.

nla

SGR
(Select
Graphic
Rendition)

ESC[O m

Resets bold, blink,
blank, underscore,
and
reverse.
Color:
Restores
normal
selected
colors.

nla

ESC[1 m

Sets bold. Color:
Sets
intensity
(changes color to

nla

ILcolor).

May 1,1986

ESC[ 4m

Sets
underscore.
Color: No effect.

nla

ESC[Sm

Sets blink. Color:
Changes
background ILcolor to
color; foreground
blinks.

nla

ESC[7m

Sets reverse video.
Color: Uses reverse
selected colors.

ESC[10m

Select primary font.

ESC[11m

Select first alternate font. Allows
characters
ASCII
less than 32 to be
displayed as ROM
characters.

nla

Page 6

CONSOLE (HW)

ESC [12m

Select second alternate font. Toggles
of
high
bit
extended
ASCII
code before displaying as ROM
characters.

The following color codes and sequences are defined by International Organization for Standardization ISO DP 6429.
C
0
1
2
3
4
5
6
7

Color
Black
Red
Green
Yellow
Blue
Magenta
Cyan
White

ISO

Sequence

Action

Tenncap
Code

SGR
(Select
Graphic
Rendition)

ESC[3Cm

Color: Selects foreground color C.

n/a

ESC[4Cm

Color:
Selects
background color
C.

n/a

ESC[8m

Sets blank
display).

n/a

May 1,1986

(non-

Page· 7

CONSOLE (HW)

The following color codes and sequences are additional control
sequences.
Cn
0
1
2
3
4
5
6
7

Color
Black
Blue
Green
Cyan
Red
Magenta
Brown
White

Cn
8
9
10
11
12
13
14
15

Color
Grey
Lt. Blue
Lt. Green
Lt. Cyan
Lt. Red
Lt. Magenta
Yellow
Lt. White

Tenncap
Code

Name

Sequence

Action

SGR

ESC[2;C1;C2 m

Color only. Sets
foreground
(C1)
and
background
(C2) colors.

nla

SGR

ESC [7 ; C1 ; C2 m

Reverse

video.
Sets foreground (C1) and
background
(C2)
reverse
video
colors.

nla

Color:

SGR

ESC[3;0 m

Color only.
Clears blink bit.

nla

SGR

ESC[3;1 m

Color only.
Sets blink bit.

nla

SGR

ESC[4 m

Underscores.

nla

Color: No effect
nla

May 1,1986

ESC [Png

Accesses alternate
graphics set. Not
the
same
as
"graphics mode."
Refer
to
your
owner's manual for
decimal! character
codes (Pn) and
possible
output
characters.

nla

Page 8

CONSOLE (HW)

n/a

ESC Q Fn 'string ,

Define function key
Fn
with string.
String
delimiters
, and' may be any
character not in
string.
Function
keys are numbered
o through 9 (Fl =
0, F2 = 1, etc.).,

n/a

A listing of the keyboard functions, codes, characters and escape
sequences that are sent by each key, appear in the files:
lusr/lib Ikeyb oard/keys
lusrllib Ikeyb oardl strin gs
lusr/libl consolel screens

Files
Idev/console
/dev/tty[02 -n]
/usrllib/ consolel screens
/usr/lib/keyboard/keys
/usr/lib/keyboard/strings

See Also
keyboard (HW), termcap (M), mapkey(M), multiscreen (M),
setcolor(C), setkey(M)

May 1,1986

Page 9

FD (HW)

Name
fd - floppy devices
Description
The fd devices implement the XENIX interface with floppy disk
drives. Typically, the tar(C), cpio(C) or dd(C) commands are used
to read or write floppy disks. For instance,
tar tvf Idev/fdO
tabulates the contents of the floppy disk in drive a (zero).
The block special fd devices are also block-buffered. The floppy
driver can read or write 512 bytes at a time using raw i/o. Note that
block transfers are always a mUltiple of the 1K disk block size.
The floppy devices are named /dev/fdO and /dev/fd! (see Notes,
below, for more information about device naming procedure).
The corresponding character special (raw) devices, /dev/rfdO and
/dev/rfd!, afford direct, unbuffered transmission between the
floppy and the user's read or write transfer address in the user's
program.
For information about formatting, see format (C).
The minor device number determines what kind of physical device
is attached to each device file (see Notes).
Files
Idev/fdO
Idev/fd1
Idev/rfdO
Idev/rfd!

Idev/rfd048ds8
Idev/rfd148ds8
Idev/rfd048ds9
/dev/rfd148ds9

Idev/rfd096ds15
Idev/rfd196ds15
Idev/rfd096ds8
Idev/rfd196ds8
Idev/rfd048ss8
I dey Irfdl48ss9

Notes
When accessing the character special floppy devices, the user's
buffer must begin on a word boundary. The count in a read (S),
write (S), or Iseek(S) call to a character special floppy device must
be a multiple of 512 bytes.
Device names determine the particular drive and media configuration. The device names have the form: fd048ds9 Where: fda =
drive number (0, 1, 2 or 3) 48 = number of disk tracks per inch (48

May 1,1986

Page 1

FD (HW)

or 96) ds = single or double sided floppy (ss or ds) 9 = number of
sectors on the floppy (S or 9)
For instance, /dev/fd048ss9 indicates a 4S track per inch, single
sided, 9 sector floppy disk device in drive O.
The minor device numbers for floppy drives depend on the drive
and media configuration. The most common are:

ds/S

4Stpi
ds/9

ss/S

ss/9

96tpi
dsl15 ds/S

Minor Device Number

Drive
12
13
14
15

0
1
2
3

4
5
6
7

S
9
10
11

0
1
2
3

52
53
54
55

45
46
47

The scheme for creating minor device numbers is as follows. When
interpreted as a binary number, each bit of the minor device
number represents some aspect of the device/media configuration.
For example, the minor device number for /dev/fd048ss8 is "S."
Interpreted as a binary number, 8 is:

00001000
This is how each bit, or binary digit, is significant:
4Stoi - 0
96toi - 1
32
0

May 1, 1986

Sectors per
Track
16
S
0

ss - 0
ds - 1

Drive

Page 2

FD (HW)

Only the last six digits of the number are used in minor device identification. The first significant digit is the third from the left. In
this example, the third digit from the left is zero, thus the device is
48tpi. The next two digits mean:
Sectors per
Track

Bits
16

0
0
1

0
1
0

9
8
15

The fourth digit tells whether the floppy is single sided (ss - 0) or
double sided (ds - 1). The last two signify the drive number:
Bits

0
0
1
1

0
1
0
1

Drive
Number

0
1
2
3

Using this information, you can construct any minor device
numbers you need.
It is not advisable to format a low density (48tpi) diskette on a high
density (96tpi) floppy drive. Low density diskettes written on a high
density drive should be read on high density drives. They mayor
may not be readable on a low density drive.

Use error-free floppy disks for best results on reading and writing.

May 1,1986

Page 3

HD (HW)

Name

hd - Internal hard disk drive
Description
The files hdOO, hdOl through hd04, hdOa through hdOd, root, and
swap provide block-buffered access to the primary hard disk. The
corresponding files for a second hard disk are listed below.
root refers to the root file system; swap refers to the swap area;
hdOO is the entire disk; hdOl through hd04 are the four partitions
recognized by ROM-BIOS. Partition one is generally the XENIX
partition. These special device files access the disks via the
system's normal buffering mechanism and may be read and written
without regard to the size of physical disk records.

The following are the names of the fixed disk partitions. Each partition can be accessed through a block interface, for example
Idev/hdOl, or through a character (raw) interface, for example
Idev/rhdOl.

December 19, 1986

Page 1

HD (HW)

HD (HW)
Device File Names for Fixed Disks
Disk 1

Disk 2

Idev/hdOO
Idev/rhdOO

Idev/hd10
Idev/rhd10

entire disk

Idev/hdOl
Idev/rhdOl

Idev/hdll
Idev/rhdll

first partition

Idev/hd02
Idev/rhd02

Idev/hd12
Idev/rhd12

second partition

Idev/hd03
Idevlrhd03

Idev/hd13
Idev/rhd13

third partition

Idev/hd04
Idev/rhd04

Idev/hd14
Idev/rhd14

fourth partition

Idev/hdOa
Idev/rhdOa

Idev/hdla
Idev/rhdla

active partition

Idev/hdOd
Idev/rhdOd

Idev/hd1d
Idev/rhd1d

DOS partition

Partition

Idev/u
Idev/ru
Idev/root
Idev/rroot

root file system

Idev/swap
Idev/rswap

swap area

Note that the last three file names do not exist for a second disk.
The device file names for DOS partitions function similarly to
Idev/hd?a.
To access DOS partitions, specify letters such as "C:" or "D:" to
indicate first or second partitions. The file letc/default/msdos
contains lines that assign a letter abbreviation for the DOS device
name. Refer to dos(C).
The following table lists the minor device numbers for possible disk
partitions. The minor device names for the raw devices are identical.

December 19, 1986

Page 2

HD (HW)

Minor Device Numbers
Partition:
hdOO
hdOl
hd02
hd03
hd04
hdOa
hdOd
root
swap
u (on 1st disk)
recover

Minor
Device
Number:
0
15
23
31
39
47
55
40
41
42
46

Partition:
hdl0
hdll
hd12
hd13
hd14
hdla
hdld
u (user choice)
ul
u2

Minor
Device
Number:
64
79
87
95
103
111
119
104
105
106

Files
Idev/hdOa
Idev/rhdOa
Idev/hdO?
Idev/rhdO?
Idev/hdOd
Idev/rhdOd

Idev/hdla
Idev/rhdla
Idev/hdl?
Idev/rhdl ?
Idev/hdld
Idev/rhdld

Idev/u
Idev/ru
Idev/root
Idev/rroot
Idev/swap
Idevlrswap

See Also
badtrk(C), divvy(C), dos(C), mkdev(C)
Diagnostics
The following messages may be printed on the console:
invalid fixed disk parameter table
and:
Error on Fixed Disk (minor n), blkno = nnnnn,
cmd=nnnnn, status=nnnn,
sector = nnnnn, Cylinder/head = nnnnn

December 19, 1986

Page 3

HD (HW)

Possible reasons for the first error include:
-

The kernel is unable to get drive specifications, such as number
of heads, cylinders, and sectors per track, from the disk controller ROM.

Improper configuration.

The disk is not turned on.

The disk is not supported.

The second error specifies the following information:

blkno: The XENIX block number within the device.

cmd: The last command sent to the disk controller.

status: The first byte of error status from the disk controller.

sector and Cylinder/head specify the location of a possible flaw.
This information is used with badtrk (M).

Notes
On the first disk, hdOO denotes the entire disk and is used to access
the master boot record and partition table. For the second disk,
hdlO denotes the entire disk and is used to access its partition
table. Do not write to hdlO and hdOO.

December 19, 1986

Page 4

KEYBOARD (HW)

Name
keyboard - The PC keyboard.
Description
The PC keyboard is used to enter data, switch screens, and send
certain control signals to the computer. XENIX performs terminal
emulation on the PC screen and keyboard, and, in doing so, makes
use of several particular keys and key combinations. These keys
and key combinations have special names that are unique to the
XENIX system, and mayor may not correspond to the keytop
labels on your keyboard. These keys are described later.
When you press a key, one of the following happens:
- An ASCII value is entered
- A string is sent to the computer.
- A function is initiated.
- The meaning of another key, or k~ys, is changed.
When a key is pressed (a keystroke), the keyboard sends a scancode to the computer, it is interpreted by the keyboard driver. The
interpretation of key codes may be modified so that keys can function differently from their default actions.
There are three special occurrences, or keystrokes:
- Switch screens.
- Send signals.
- Change the value of previous character, characters or string.

Switching Screens (Muitiscreen)
To get to the next consecutive screen, enter CtrI-PrtSc using the
Ctrl key, and the PrtSc key. Any active screen may be selected by
entering ait-Fn, where Fn is one of the function keys. Fl refers to
the PC display (/dev/ttyOl).

December 19, 1986

Page 1

KEYBOARD (HW)

Signals

A signal affects some process or processes. Examples of signals are
Ctrl-d (end of input, exits from shell), Ctrl-\ (quits a process),
Ctrl-s (stop output to the screen), and Ctrl-q (resume sending
output).
Typically, characters are mapped to signals using stty(C). The only
way to map signals is using stty.
Altering Values

The actual code sent to the keyboard driver can be changed by
using certain keys in combination. For example, the SHIFf key
changes the ASCII values of the alphanumeric keys. Holding down
the Ctrl key while pressing another key sends a control code
(Ctrl-d, Ctrl-s, Ctrl-q, etc.).
Special Keys

To help you find the special keys, the following table shows which
keys on a typical console correspond to XENIX system keys. In
this table, a hyphen (-) between keys means 'hold down the first
key while pressing the second.'
XENIX Name

Key top

Action

INTR

Del

Stops current action and
returns to the shell. This key
is also called the RUB OUT or
INTERRUPT key.
Deletes the first character to
the left of the cursor.
Note that the "cursor left"
key also has a left arrow (+-)
on its keytop, but you cannot
backspace using that key.

BACKSPACE

Ctrl-d

Ctrl-h

Ctrl-q

December 19, 1986

Signals the end of in put from
the keyboard; also exits
current shell.
Deletes the first character to
the left of the cursor. Also
called the ERASE key.
Restarts printing after it has
been stopped with Ctrl-s.

Page 2

KEYBOARD (HW)

Ctrl-s

Ctrl-u

Ctrl-\

Quits current command and
creates a core file, if allowed.
(Recommended for debugging
only.)

ESCAPE

Esc

RETURN

(down-left arrow
or ENTER)

Special code for some programs. For example, changes
from insert mode to command
mode in the vi(C) text editor.
Terminates a command line
and initiates an action from
the shell.
Function key n. F1-F12 are
unshifted, F13-F14 are shifted
F1-F12, F25-F36 are Ctrl-F1
through F12, and F37-F48 are
Ctrl-Shift-F1 through F12.

Suspends printing on the
screen (does not stop the program).
Deletes all characters on the
current line. Also called the
KILL key.

The next Fn keys (F49- F60)
are on the number pad
(unshifted):
F49
F50
F51
F52
F53
F54

'7'
'8'
'9'
'-'
'4'
'5'

F55
F56
F57
F58
F59
F60

'6'

'+'
'1'
'2'
'3'
'0'

For keys F61 through F96, see
/usr/lib/keyboard/s trlngs.
These function keys are not
available on all keyboards, but
you can map other keys to
represent them.
The keyboard mappi~g is performed through a structure defined in
/usr/include/sys/keyboard.h. Each key can have ten states. The
first eight are:
-

Base
Shift
Ctrl
Alt

December 19, 1986

Ctrl-Shift
Alt-Shift
Alt-Ctrl
Alt-Ctrl-Shift

Page 3

KEYBOARD (HW)

There are two additional states indicated by two special bytes. The
first is a "special state" byte whose bits indicate whether the key is
"special" in one or more of the first eight states.
The second is one of four characters (C, N, B, 0) which indicate
how the lock keys affect the particular key. This is discussed
further in the next section, "Scan Codes."
Scan Codes
The following table describes the default
Ius r/lib/keybo ard/keys . The column headings are:

contents

SCAN CODE- The scan code generated by the keyboard hardware
when a key is pressed. There is no user access to the scan code
generated by releasing a key.
BASE - The normal value of a key press.
SHIFT - The value of a key press when the SHIFT is also being
held down.
LOCK - Indicates which lock keys affect that particular key:
-

C indicates Capslock
N indicates Numlock
B indicates both
0 indicates locking is off

Keys affected by the lock keys C, B, or N, send the shifted value
(scan code) of current state when that lock key is on. When the
shift key is depressed while a lock key is also on, the key reverts
(t~gg1es) to its original state.
The other columns are the values of key presses when combinations of the CTRL, ALT and SHIFT keys are also held down.
All values, except for keywords, are ASCII character values. The
keywords refer to the special function keys.

December 19, 1986

Page 4

KEYBOARD (HW)

ALT
SCAN
CODE

BASE

SHIFI'

nop
esc

2
3

'1'
'2'

'!'

'#'

'3'
'4'

6
7

'5'
'6'

'%'

8
9

'7'

'&'

'8'

'.'

'9'
'0'

'('
')'

'@'

'$'
,~,

CTRL

CTRL
SHIFT

nop
nop
nop
nop
nop
nop
nop

nop
nop
nop
nop
ns
nop
del
nop

nak

ht
si
die

esc

cr
ctrl

'a'

'A'

dc3

soh
dc3

ctrl
soh

nl
ctrl

's'

dc3

eot

'D'
'P'
'G'
'H'
'J'
'K'
'L'

eot

ack

'd'
'f'
'g'
'h'
'j'
'k'
'1'

eot

ack
bel
bs
nl

ack

bel

bs
nl

np
nop
nop
nop

Ishift
fs

lshift
fs

cr
ctrl

'a'
's'

'A'

34
35
36
37

'd'

'f'
'g'
'h'
'j'
'k'
'I'

'.',

40
41
42
43
44
45
46

'\"

'.'

Ishift

'\\'
'z'
'x'
'c'
'v'

'j'
'Z'
'X'
'C'
'V'

December 19, 1986

nop
nop
nop
nop
ns
nop
del
nop
dc1

enq
dc2
dc4

'S'
'D'
'P'
'G'
'H'
'J'
'K'
'L'

enq
dc2
dc4

31
32

enq
dc2
dc4

'E'
'R'
'T'
'Y'
'U'
'I'
'0'
'P'
'{'
'}'

'&'

,~,

'E'
'R'
'T'
'Y'
'U'
'I'
'0'
'P'
'{'
'}'

'r'
't'
'y'
'u'
'i'
'0'
'p'
'['
']'

23
24
25
26
27
28
29

'7'
'8'
'9'
'0'

'$'

etb

'e'

'%'

etb

'5'
'6'

'W'

etb

'#'

'Q'

'W'

'@'

'3'
'4'

btab

del
etb

'2'

'q'
'w'
'e'
'r'
't'
'y'
'u'
'i'
'0'
'p'
'['
']'

'Q'

'+'

'!'

nop
nop
nop
nop
nop
nop
nop

btab

'q'
'w'

'=='

'1'

nop
nop
nop
nop
nop
nop
\ nop

'-'

nop
esc

CTRL
SHIFT

'='
bs

16
17
18

12
13
14
15

nop
esc

ALT
CTRL

nop
nop
nop
nop
ns
nop
del
nop
dc1

ALT

ALT
SHIFT

nak

ht
si
dIe

ht
si

esc

die
esc

ctrl
soh

ctrl

bel

bs
nl

np
nop
nop
nop

lshift
fs
sub

Ishift
fs
sub
can

can
etx
syn

etx
syn

'.'
'('
')'

'-'
'+'

Ishift Ishift

'\\'
'z'
'x'
'c'
'v'

'j'
'Z'
'X'
'C'
'V'

soh

dc3

sub

can

etx

syn

LOCK

o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
C
C
C
C
C
C
C
C
C
C

o
o
o

o
C
C
C
C
C
C
C
C
C

o
o
o
o
o
C
C
C
C

Page 5

KEYBOARD (HW)
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64

65
66

67
68
69
70
71
72

73
74
75
76
77

78
79
80

81
82
83
84

85
86

'b'
'n'
'm'

"B'

KEYBOARD (HW)

'/'

'?'

rshift

alt

stx
so
er
nop
nop
nop
rshift
nser
alt

clock
fkey1
fkey2
fkey3
fkey4
fkey5
fkey6
fkey7
fkey8
fkey9
fkey10
nlock
slock
fkey49
fkey50
fkey51
fkey52
fkey53
fkey54
fkey55
fkey56
fkey57
fkey58
fkey59
fkey60
del
nop
fkeyll
fkey12

clock
fkey13
fkey14
fkeylS
fkey16
fkey17
fkey18
fkey19
fkey20
fkey21
fkey22
nlock
slack
'7'
'8'
'9'

clock
fkey25
fkey26
fkey27
fkey28
fkey29
fkey30
fkey31
fkey32
fkey33
fkey34
dc3
del
'7'
'8'
'9'

'-'

'4'
'5'
'6'

'+'

'1'
'2'
'3'
'0'

'1'
'2'
'3'
'0'
del
nap
fkey35
fkey36

'1'
'2'
'3'
'0'
del
nap
fkey47
fkey48

',,
',

,*,

'N'
'M'

'<'
'>'

'*'

nap
fkey23
fkey24

stx
so
er
nop
nop
nap
rshift
nser
alt
clock
fkey37
fkey38
fkey39
fkey40
fkey41
fkey42
fkey43
fkey44
fkey45
fkey46
dc3
del
'7'
'8'
'9'

'b'
'n'
'm'

'B'

,*,

alt

stx
so
er
nop
nop
nap
rshift
nser
alt

clock
serl
ser2
ser3
ser4
ser5
sero
ser7
serB
ser9
serlO
nlock
slock
'7'
'8'
'9'

clock
serll
serl2
serl3
serl4
serl5
serl6
ser7
serB
ser9
serlO
nlock
slock
'7'
'8'
'9'

clock
serl
ser2
scr3
ser4
ser5
sero
ser7
ser8
ser9
serlO
dc3
del
'7'
'8'
'9'

cloek
serH
ser12
ser13
scr14
ser1S
ser16
ser7
ser8
ser9
serlO
dc3
del
'7'
'8'
'9'

'4'
'5'
'6'

'+'

'1'
'2'
'3'
'0'
del
nop
scrll
ser12

'1'
'2'
'3'
'0'
del
nop
serll
scrl2

'1'
'2'
'3'
'0'
del
nop
serll
serl2

'1'
'2'
'3'
'0'
del
nap
serll
ser12

'N'
'M'

,,,
"

'<'
'>'

'I'

'?'

rshift rshift

'-'

stx
so
er
nop
nap
nap
rshift
nser
alt

C
C
C
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
N
N
N
N
N
N
N
N
N
N
N
N
N

0
0
0

The next table lists the "value" of each of the special keywords
used in lusr/lib/keyboard/keys (and the preceding table).
mapkey(M) places a "value" in the ioetl buffer during key mapping.
The keywords are only used in the scan code file
(/usr/lib/keyboard/keys) for readability.

December 19, 1986

Page 6

KEYBOARD (HW)

Name

Value

Meaning

nop
lshift
rshift
clock
nlock
slock
alt
btab
ctrl
nscr
scrl

0
2
3
4
5
6
7
8
9
10
11

No operation - no action from keypress
Left hand shift
Right hand shift
Caps lock
Numeric lock
Scroll lock
Alt key
Back tab key - generates fixed sequence (esc [ Z)
Control key
Switch to the next screen
Switch to screen #1

scrl6
fkeyl

26
27

Switch to screen #16
Function key #1

fkey96

122

Function key #96

This table lists names and decimal values that are interchangeable
in the mapkey file. Names are used in place of numeric constants
to make it easier to read the scan code table. Again, only the
decimal values are placed in the ioetl buffer. These are taken from
ascii(M).
Name
nul
soh
stx
etx
eot
enq
ack
bel
bs
ht
nl
vt
np
cr
so
si
dIe

Value
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

Name
dcl
dc2
dc3
dc4
nak
syn
etb
can
em
sub
esc
fs
gs
rs
ns
del

Value
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
127

Keyboard Mapping

The PC keyboard is mapped as part of terminal emulation. This
kind of mapping is performed only on the computer keyboard, not
on remote terminals. Use mapkey to change keyboard mapping.
To change the mapping for individual channels (multiscreens), use
mapehan (M).

December 19, 1986

Page 7

KEYBOARD (HW)

Keyboard mapping can also be performed using ioctl. The syntax
is the same as for string key mapping (see previous section).
For keyboard mapping, cmd is GIOJ(EYMAP to display the current
map, and PIOJ(EYMAP puts the prepared buffer into place.
String Key Mapping

To map string (function) keys, use the mapstr (see mapkey(M)) utility. mapstr modifies the string mapping table where function keys
are defined.
The string mapping table is an array of 512 bytes (typedef strmap_t)
containing null terminated strings that redefine the function keys.
The first null terminated string is assigned to the first string key, the
second string to the second string key, and so on.
There is no limit to the length of any particular string as long as the
whole table does not exceed 512 bytes, including nulls. Strings are
made null by the introduction of extra null characters.
The following is a list of default function key values:
Default Function Key Values
Key #

Function

ESC[M
ESC[N
ESC [0
ESC[P
ESC[Q
ESC[R
ESC[S
ESC[T
ESC[U
ESC [V
ESC[W
ESC [X

2
3
4

5
6
7

8
9
10
11
12

Home
Up arrow
Page up
Left arrow
Right arrow

December 19, 1986

Shift

Ctrl

Function

Ctrl
Shift
Function

ESC[Y
ESC[Z
ESC [a
ESC[b
ESC[c
ESC[d
ESC[e
ESC[f
ESC[g
ESC[h
ESC[i
ESC[j

ESC[k
ESC [I
ESC[m
ESC[n
ESC [0
ESC[p
ESC[q
ESC[r
ESC[s
ESC[t
ESC[u
ESC [v

ESC[w
ESC[x
ESC[y
ESC[z
ESC[@
ESC[[
ESC[\
ESC[]
ESC[A
ESC[_
ESC['
ESC[{

ESC[H
ESC [A
ESC [I
ESC[D
ESC[C

End
Down arrow
Page down
5
Insert

ESC[F
ESC[B
ESC[G
ESC[E
ESC[L

Page 8

KEYBOARD (HW)

You can also map string keys using ioctl(S). The syntax is:
#include
ioctl(fd,cmd,buf)
int fd, cmd;
char *buf;
For string key mapping where cmd is GIO_STRMAP to display the
string mapping table and PIO_STRMAP to put the new string mapping table in place.
Files

lusrllib Ikeyb oard/k eys
lusr/lib/keyboardl strings
See Also
mapchan(F),
mapchan(M),
screen(HW), setkey(C), stty(C)

December 19, 1986

mapkey(M),

multiscreen(M),

Page 9

LP(HW)

Name
lp, IpO, Ip1, Ip2 - Line printer device interfaces.
Description
The JpO, Jp1, and Jp2 files provide access to the optional parallel
ports of the computer. The IpO and Ip2 files provide access to
parallel ports 1 and 2, respectively. The Ip1 file provides access to
the parallel port on the monochrome adaptor.
Only one of IpO and Ip1 may be used on a given system. To access
two parallel printers on a system, use either IpO or lp 1, and Jp2.
Files
/dev/lpO
/dev/ip1
/dev/lp2
See Also
Ip(C), Ipadmin(C), Ipsched(C), Ipinit(C)
Notes
The standard Ip ports, IpO, Ip1, and Ip2 send a printer initialization
string the first time the file is opened after the system is booted.
Not all computers have an alternate parallel port slot.

December 19, 1986

Page 1

MACHINE (HW)

Name

Machine - Description of host machine.
Description

This page lists the internal characteristics of personal computers
which use the Intel 8086 processor family and its associated
hardware. The information is intended for software developers
who wish to transfer relocatable object or executable files from
other XENIX machines to a personal computer then prepare the
files for execution on the personal computer.
Central Processing Unit

Intel 8086, 8088, 80186, 80286

Disk Block Size (BSIZE)

1024 bytes

Memory Management Scheme

Unmapped (8086, 8088, 80186)
Segmented (80286)

Split Instruction and Data

Supported

Variable Stack Size

Supported (8086 only)
(8086 default configuration)

Fixed Stack Size

Supported
(80286 default configuration)

Clock Ticks

.05 second (8086, 8088, 80186)
.02 second (80286)

Binary Compatibility

The small and middle model binary programs created by the C
compiler cc(CP) run on many processors. The following chart
shows which XENIX systems running on which processors produce
code executable on other machines. It is assumed that system
specific system calls are not used to produce portable code. cc(CP)
produces code by default, but can also be used as a cross development compiler, by using the appropriate flags.

SCO-nn is XENIX distributed by The Santa Cruz Operation, Inc.
MS-nn is XENIX distributed by Microsoft Corporation. Intel
XENIX is distributed by Intel Corporation. Altos XENIX is distri-

buted by Altos Computer Systems. nn designates the machine processor. System designates the version of XENIX, either 2.3, 3.0, or
System V.

May 1, 1986

Page 1

MACHINE (HW)

MACHINE (HW)
Binary Compatibility
Default compiler

Runs default

produces programs

programs

development)

which run on

created on

programs for

Processor

SystemlProcessor

sCO-86 3.0

SCO-86 [3.0, Sys Vj

SCO-863.0

DOS·

Your
System

SCO-86 SystemV

SCO-1863.0

SCO-186 System V

SCO-2863.0

SCO-286 System V

MS-286 3.0t

SCO-186 [3.0, Sys V]

SCO-1863.0

scO-286 SysV

Intel, Altos-86 2.3,3.0

Compiles (cross

SCO-86 Sys V

SCo-86 [3.0, Sys V]

MS-2863.0t

SCO-186 Sys V

SCO-186 [3.0, Sys Vj

DOS·

SCO-286 Sys V

sCO-286 Sys V

MS-286 Sys V

Intel, Altos-86 2.3, 3.0

sCO-86 [3.0, Sys V]

SCO-863.0

SCO-186 [3.0, Sys V]

SCO-1863.0

SCO-286 Sys V

Intel, Altos-86 2.3, 3.0

DOS·

sco-86 Sys V

SCO-86 [3.0, Sys V]

MS-286 3.0t

SCO-186 Sys V

SCO-l86 [3.0, Sys V]

DOS·

SCO-286 Sys V

MS-286 Sys V

Intel, Altos-86 2.3, 3.0

SCO-286 [3.0, Sys V]

SCo-286 3.0

MS-286 [3.0t, Sys V]

MS-2863.0t

SCO-86 Sys V

SCO-86 [3.0, Sys V]

SCO-2863.0

SCO-186 Sys V

SCO-l86 [3.0, Sys Vj

MS-286 3.0t

SCO-286 Sys V

SCO-286 [3.0, Sys V]

DOS*

MS-286 Sys V

Ms-286 [3.0t, Sys Vj

Ms-286 [3.0t, Sys V]

SCO-286 3.0

DOS·

Ms-286 Sys V

SCO-86 [3.0, Sys V]*

DOS*

SCO-286 Sys V

SCO-l86 [3.0, Sys V]*

DOS·

SCO-286 Sys V
MS-286 System V

sCO-286 [3.0, Sys Vn

MS-DOS for i8086/8088, i80186 and i80286 processors.
MS-286 3.0 XENIX is equivalent to Intel 286 3.0 XENIX.
:j: untested, pending release of this product.

SCO_XENIX_System_V_Run_Time_Environment_2.2A_Apr87 SCO XENIX System V Run Time Environment 2.2A Apr87

SCO_XENIX_System_V_Run_Time_Environment_2.2A_Apr87 SCO_XENIX_System_V_Run_Time_Environment_2.2A_Apr87

Navigation menu

Versions of this User Manual:

Views

Navigation