.\" Copyright (c) 1980, 1986, 1988 The Regents of the University of California.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" @(#)4.t 6.6 (Berkeley) 4/17/91
.ds LH "Installing/Operating \*(4B
This section describes procedures used to set up a \*(Mc UNIX system.
These procedures are used when a system is first installed
or when the system configuration changes. Procedures for normal
system operation are described in the next section.
The procedures for making the various UNIX boot media are described in this
section. If you have an 8200 or 11/780, you will need to make a floppy.
For an 11/730, you will need to make a cassette. For an
8600, you will need to make a console RL02 pack.
The boot command files are all set up for booting off of the first
UNIBUS or MASSBUS. If you are booting off of a different UNIBUS
or MASSBUS, you will need to modify the boot command files appropriately.
Making a UNIX boot console RL02 pack
If you have an 8600 you will want to create a
boot console RL02 pack by adding some files to your current DEC
If you do not want to modify your current DEC console pack, you may
make a copy of it first using
This pack will make standalone system operations such as
bootstrapping much easier.
First change into the directory where the console RL02
\fB#\fI cd /sys/consolerl\fR
then set up the default boot device.
If you have an RK07 as your primary root do:
\fB#\fI cp defboo.hk defboo.com\fR
If you have a drive on a UDA50 (e.g. an RA81) as your
\fB#\fI cp defboo.ra defboo.com\fR
If you have a second vendor
UNIBUS storage module as your primary root do:
\fB#\fI cp defboo.up defboo.com\fR
\fB#\fI cp defboo.hp defboo.com\fR
The final step in updating the console RL02 pack is:
More copies of this console RL02 pack can be made using
Making a UNIX boot floppy
If you have an 8200 or 11/780 you will want to create a
boot floppy by adding some files to a copy of your current DEC
console floppy, using either
This floppy will make standalone system operations such as
bootstrapping much easier.
First change into the directory where the console floppy
\fB#\fI cd /sys/floppy\fR
then set up the default boot device.
If you have an RK07 as your primary root do:
\fB#\fI cp defboo.hk defboo.cmd\fR
If you have a drive on a UDA50 (e.g. an RA81) as your
\fB#\fI cp defboo.ra defboo.cmd\fR
If you have a second vendor
UNIBUS storage module as your primary root do:
\fB#\fI cp defboo.up defboo.cmd\fR
If you have a drive on a KDB50 as your primary root do:
\fB#\fI cp defboo.kra defboo.cmd\fR
\fB#\fI cp defboo.hp defboo.cmd\fR
if the local configuration requires any changes in restar.cmd
or defboo.cmd (e.g., for interleaved old-style memory controllers see
defboo.MS780C-interleaved),
these should be made now.
The following command will then copy your DEC local console floppy,
updating the copy appropriately.
\fBChange Floppy, Hit return when done.\fP
(waits for you to put clean floppy in console)
\fBAre you sure you want to clobber the floppy?\fI yes\fR
More copies of this floppy can be made using
On an 8200, copy any of the DEC diagnostic floppies
by placing the source in console drive 1 and the destination
in console drive 2, then:
.\" XXX be sure to put /dev/csa? in root fs, or makedev first
\fB#\fI dd if=/dev/csa1 of=/dev/csa2 bs=400k\fR
Next remove all but the first few files, leaving only those
that lead up to ``boot58.exe'' (as well as boot58.exe itself).
It is a good idea to remove
the original floppy from drive 1 first.
\fB#\fI arff tmf /dev/csa2\fR
\&...(should list something like ``fg81.ve0'', followed by ``boot58.exe'';
then a series of files that may be deleted)...\fP
\fB#\fI arff dmf /dev/csa2\fR files to delete from previous list
Finally, add UNIX boot files:
\fB#\fI arff rmf /dev/csa2 boot format copy *boo.cmd\fR
Put the new boot floppy in drive 1. To make copies of this floppy,
Making a UNIX boot cassette
If you have an 11/730 you will want to create a
boot cassette by adding some files to a copy of
your current DEC console cassette, using
\fIflcopy\fP\|(8) and \fIarff\fP\|(8).
This cassette will make standalone system operations such as
bootstrapping much easier.
First change into the directory where the console cassette
\fB#\fI cd /sys/cassette\fR
then set up the default boot device.
If you have an IDC storage module as your primary root do:
\fB#\fI cp defboo.rb defboo.cmd\fR
If you have an RK07 as your primary root do:
\fB#\fI cp defboo.hk defboo.cmd\fR
If you have a drive on a UDA50 as your primary root do:
\fB#\fI cp defboo.ra defboo.cmd\fR
\fB#\fI cp defboo.up defboo.cmd\fR
To complete the procedure place your DEC local
drive 0 (the drive at front of the CPU);
the following command will then copy it,
updating the copy appropriately.
\fBChange Floppy, Hit return when done.\fP
(waits for you to put clean cassette in console drive 0)
\fBAre you sure you want to clobber the floppy?\fI yes\fR
More copies of this cassette can best be made using
This section briefly describes the layout of the kernel code and
how files for devices are made.
For a full discussion of configuring
and building system images, consult the document ``Building
4.3BSD UNIX Systems with Config''.
As distributed, the kernel source is in a
separate tar image. The source may be physically
located anywhere within any file system so long as
a symbolic link to the location is created for the
(many files in /usr/include are normally symbolic links
relative to /sys). In further discussions of the
system source all path names will be given relative to
contains the mainline machine independent
Files within this directory are conventionally
named with the following prefixes:
init_ system initialization
kern_ kernel (authentication, process management, etc.)
sys_ system calls and similar
uipc_ interprocess communication
The remaining directories are organized as follows:
/sys/h machine-independent include files
/sys/conf site configuration files and basic templates
/sys/kdb machine-independent part of the kernel debugger
/sys/net protocol-independent, but network-related code
/sys/netimp IMP support code
/sys/netinet DARPA Internet code
/sys/stand machine-independent standalone code
/sys/tahoe Tahoe-specific mainline code
/sys/tahoealign Tahoe unaligned-reference emulation code
/sys/tahoedist Tahoe distribution files
/sys/tahoeif Tahoe network interface code
/sys/tahoevba Tahoe VERSAbus device drivers and related code
/sys/tahoemath Tahoe floating point emulation code
/sys/tahoestand Tahoe standalone device drivers and related code
/sys/vax VAX-specific mainline code
/sys/vaxbi VAX BI device drivers and related code
/sys/vaxdist VAX distribution files
/sys/vaxif VAX network interface code
/sys/vaxmba VAX MASSBUS device drivers and related code
/sys/vaxstand VAX standalone device drivers and boot code
/sys/vaxuba VAX UNIBUS device drivers and related code
Many of these directories are referenced through /usr/include with
symbolic links. For example, /usr/include/sys is a symbolic
link to /sys/h. The system code, as distributed, is totally
independent of the include files in /usr/include. This allows
the system to be recompiled from scratch without the /usr file
Devices and device drivers
Devices supported by UNIX are implemented in the kernel
by drivers whose source is kept in
/sys/vax, /sys/vaxbi, /sys/vaxuba, or /sys/vaxmba.
/sys/tahoe or /sys/tahoevba.
into the system when included in a cpu specific configuration file
kept in the conf directory. Devices are accessed through special
files in the file system, made by the
program and normally kept in the /dev directory.
For all the devices supported by the distribution system, the
files in /dev are created by the /dev/MAKEDEV
Determine the set of devices that you have and create a new /dev
directory by running the MAKEDEV script.
First create a new directory
/newdev, copy MAKEDEV into it, edit the file MAKEDEV.local
to provide an entry for local needs,
and run it to generate a /newdev directory.
For instance, if your machine has a single DZ11, a single
DH11, a single DMF32, an RM03 disk, an EMULEX UNIBUS SMD disk controller, an
AMPEX 9300 disk, and a TE16 tape drive you would do:
For instance, if your machine has a single VIOC terminal
multiplexor, two CDC 340 megabyte Winchester drives, and
a single Cipher tape drive you would do:
\fB#\fP \fImkdir newdev\fP
\fB#\fP \fIcp dev/MAKEDEV newdev/MAKEDEV\fP
\fB#\fP \fIMAKEDEV dz0 dh0 dmf0 hp0 up0 ht0 std LOCAL\fP
\fB#\fP \fIMAKEDEV vx0 dk0 dk1 cy0 std LOCAL\fP
Note the ``std'' argument causes standard devices
such as \fI/dev/console\fP, the machine console,
the console floppy disk interface for the 11/780 and 11/785, and
\fI/dev/tu0\fP and \fI/dev/tu1\fP, the console cassette interfaces
for the 11/750 and 11/730,
\fB#\fP \fImv dev olddev ; mv newdev dev\fP
to install the new device directory.
Building new system images
The kernel configuration of each UNIX system is described by
a single configuration file, stored in the \fI/sys/conf\fP directory.
To learn about the format of this file and the procedure used
start by reading ``Building 4.3BSD UNIX Systems with Config'',
look at the manual pages in section 4
of the UNIX manual for the devices you have,
and look at the sample configuration files in the /sys/conf
The configured system image ``vmunix'' should be
copied to the root, and then booted to try it out.
It is best to name it /newvmunix so as not to destroy
the working system until you're sure it does work:
\fB#\fP \fIcp vmunix /newvmunix\fP
It is also a good idea to keep the previous system around under some other
name. In particular, we recommend that you save the generic distribution
version of the system permanently as \fI/genvmunix\fP for use in emergencies.
To boot the new version of the system you should follow the
bootstrap procedures outlined in section 6.1.
After having booted and tested the new system, it should be installed
as \fI/vmunix\fP before going into multiuser operation.
A systematic scheme for numbering and saving old versions
of the system may be useful.
This section describes how to layout file systems to make use
of the available space and to balance disk load for better system
Change into the directory /etc and copy the appropriate file from:
fstab.up160m (160MB up drives)
fstab.hp400m (400MB hp drives)
fstab.up (other up drives)
fstab.hp (other hp drives)
to the file /etc/fstab, i.e.:
\fB#\fI cp \fIfstab.xxx\fP fstab\fR
This will set up the default information about the usage of disk
partitions, which we see how to update more below.
The names of the disks on \*(4B all use the basename \fIdk\fP,
unlike other systems on the Tahoe.
Unfortunately, the console processor reads the file \fI/etc/fstab\fP
and expects disk names that indicate the type of disk drive.
Therefore, the first line in \fI/etc/fstab\fP is a dummy line
to satisfy the console processor:
If your root disk is a type other than \fIfsd\fP,
edit \fI/etc/fstab\fP to change the first device
Disk naming and divisions
Each physical disk drive can be divided into up to 8 partitions;
UNIX typically uses only 3 or 4 partitions.
For instance, on an \*(Dn,
the first partition, \*(Dk0a,
is used for a root file system, a backup thereof,
or a small file system like, /tmp;
the second partition, \*(Dk0b,
is used for paging and swapping; and
the third partition, \*(Dk0\*(Pa,
holds a user file system.
On an RM05, the first three partitions
are used as for the \*(Dn, and the fourth partition, \*(Dk0h,
holds the /usr file system, including source code.
The disk partition sizes for a drive are based on a
set of four prototype partition tables; c.f. \fIdiskpart\fP\|(8).
table used is dependent on the size of the drive.
The ``a'' partition is the same size across all drives,
15884 sectors. The ``b'' partition, used for paging and
swapping, is sized according to the total space on the disk.
For drives less than about 400 megabytes the partition
is 33440 sectors, while for larger drives the partition size
is doubled to 66880 sectors. The ``c'' partition is always
used to access the entire physical disk, including the space
at the back of the disk reserved for the bad sector
forwarding table. If the disk is larger than about 250 megabytes,
an ``h'' partition is created with size 291346 sectors, and
no matter whether the ``h'' partition is created or not, the
remainder of the drive is allocated to the ``g'' partition.
Sites that want to split up the ``g'' partition into several
smaller file systems may use the ``d'', ``e'', and ``f''
partitions that overlap the ``g'' partition. The default
sizes for these partitions are 15884, 55936, and the remainder
of the disk, respectively*.
* These rules are, unfortunately, not evenly applied to all
disks. \fI/etc/disktab\fP, and the pack label or driver tables,
give the final word; consult section 4 of the manual, and
read /etc/disktab, for more information.
The disk partition sizes for DEC RA60, RA80, and RA81 have
changed since 4.2BSD. If upgrading from 4.2BSD,
you will need to decide if you want
to use the new partitions or the old partitions. If you
desire to use the old partitions, you will need to label your packs
as `racompat', or create your own by updating
other partition sizes that were modified at your site will
require the same consideration;
if the device driver does not support pack labels, you will have to
update its compiled-in tables as well.
The space available on a disk varies per device. The amount of space
available on the common disk partitions is listed in the following table.
Not shown in the table are the partitions of each drive devoted
to the root file system and the paging area.
Many other partitions are listed in the standard partitions,
but most of them are not useful.
Note that the standard partition tables usually list several alternative
ways to divide a disk, but that only nonoverlapping partitions may be used
rm05 hp?g 80 Mb hp?h 145 Mb
ra60 ra?g 78 Mb ra?h 96 Mb
ra81 ra?g 257 Mb ra?h 145 Mb
rb80 rb?g 41 Mb rb?h 56 Mb
rp07 hp?g 315 Mb hp?h 145 Mb
up300 up?g 80 Mb up?h 145 Mb
up330 up?g 90 Mb up?h 145 Mb
up400 hp?g 216 Mb hp?h 145 Mb
xfd dk?c 225 Mb dk?g,h 112 Mb
Here up300 refers to either an AMPEX or CDC 300 megabyte disk on a
MASSBUS or UNIBUS disk controller, up330 refers to either an AMPEX
or FUJITSU 330 megabyte disk on a MASSBUS or UNIBUS controller,
up160 refers to a FUJITSU 160 megabyte disk
on the UNIBUS, and up400 refers to a FUJITSU Eagle 400 megabyte
disk on a MASBUS or UNIBUS disk controller. ``hp'' should be
substituted for ``up'' above if the disk is on the MASSBUS.
Consult the manual pages for the specific controllers for other
supported disks or other partitions.
Each disk also has a paging area, typically 16 megabytes, and
a root file system of 7.5 megabytes.
Each disk also has a paging area and a root file system of between 10 and 30
The distributed system binaries occupy about 34 megabytes
while the major sources occupy another 32 megabytes.
This overflows dual RK07, dual RL02 and single RM03 systems,
but fits easily on most other hardware configurations.
overflow even the smallest Tahoe configurations.
Be aware that the disks have their sizes
measured in disk sectors (usually 512 bytes), while the UNIX file
system blocks are variable sized. All user programs report
disk space in kilobytes and, where needed, disk sizes are always
sectors. The /etc/disktab file used in labelling disks and making file systems
specifies disk partition sizes in sectors; the default sector size
(DEV_BSIZE as defined in /sys/h/param.h)
may be overridden with the ``se'' attribute.
All SMD disks on Tahoe currently use a sector size of 512 bytes.
There are several considerations in deciding how
to adjust the arrangement of things on your disks.
The most important is making sure that there is adequate space
for what is required; secondarily, throughput should be maximized.
Paging space is an important parameter.
The system, as distributed, sizes the configured
paging areas each time the system is booted. Further,
multiple paging areas of different size may be interleaved.
Drives smaller than 400 megabytes have swap partitions of 16 megabytes
while drives larger than 400 megabytes have 32 megabytes. These
values may be changed to get more paging space by changing
the label (or, if labels are unsupported,
the appropriate partition table in the disk driver).
Many common system programs (C, the editor, the assembler etc.)
create intermediate files in the /tmp directory,
so the file system where this is stored also should be made
large enough to accommodate
most high-water marks; if you have several disks, it makes
sense to mount this in a ``root'' (i.e. first partition)
file system on another disk.
All the programs that create files in /tmp take
care to delete them, but are not immune to rare events
The directory should be examined every so often and the old
The efficiency with which UNIX is able to use the CPU
is often strongly affected by the configuration of disk controllers.
For general time-sharing applications,
the best strategy is to try to split the root file system (/), system binaries
(/usr), the temporary files (/tmp),
and the user files among several disk arms, and to interleave
the paging activity among several arms.
It is critical for good performance to balance disk load.
There are at least five components of the disk load that you can
divide between the available disks:
The following possibilities are ones we have used at times
when we had 2, 3 and 4 disks:
l | lw(5) | lw(5) | lw(5).
The most important things to consider are to
even out the disk load as much as possible, and to do this by
decoupling file systems (on separate arms) between which heavy copying occurs.
Note that a long term average balanced load is not important; it is
much more important to have an instantaneously balanced
load when the system is busy.
Intelligent experimentation with a few file system arrangements can
pay off in much improved performance. It is particularly easy to
file system and the paging areas. Place the
directory as space needs dictate and experiment
with the other, more easily moved file systems.
Each file system is parameterized according to its block size,
fragment size, and the disk geometry characteristics of the
medium on which it resides. Inaccurate specification of the disk
characteristics or haphazard choice of the file system parameters
can result in substantial throughput degradation or significant
waste of disk space. As distributed,
file systems are configured according to the following table.
File system Block size Fragment size
The root file system block size is
made large to optimize bandwidth to the associated
disk; this is particularly important since the
/tmp directory is normally part of the root file or a similar filesystem.
The large block size is also
important as many of the most heavily used programs
are demand paged out of the /bin directory. The
fragment size of 1 kbyte is a ``nominal'' value to use
with a file system. With a 1 kbyte fragment size
disk space utilization is about the same
as with the earlier versions of the file system.
The usr file system would like to use a 4 kbyte block size
with 512 byte fragment size in an effort to get high performance
while conserving the amount of space wasted by a large fragment
size. However, the tahoe disk controllers require a minimum
block size of 1 Kbyte. Space compaction
has been deemed important here because the source code
for the system is normally placed on this file system.
If the source code is placed on a separate filesystem,
use of an 8 kbyte block size with 1 kbyte fragments might
be considered for improved performance when paging from \fI/usr\fP binaries.
The file systems for users have a 4 kbyte block
size with 1 kbyte fragment size. These parameters
have been selected based on observations of the
performance of our user file systems. The 4 kbyte
block size provides adequate bandwidth while the
1 kbyte fragment size provides acceptable space compaction
Other parameters may be chosen in constructing file
systems, but the factors involved in choosing a block
size and fragment size are many and interact in complex
ways. Larger block sizes result in better
throughput to large files in the file system as
larger I/O requests will then be performed by the
consideration must be given to the average file sizes
found in the file system and the performance of the
internal system buffer cache. The system
currently provides space in the inode for
12 direct block pointers, 1 single indirect block
pointer, and 1 double indirect block pointer.*
* A triple indirect block pointer is also reserved, but
If a file uses only direct blocks, access time to
it will be optimized by maximizing the block size.
If a file spills over into an indirect block,
increasing the block size of the file system may
decrease the amount of space used
by eliminating the need to allocate an indirect block.
However, if the block size is increased and an indirect
block is still required, then more disk space will be
used by the file because indirect blocks are allocated
according to the block size of the file system.
In selecting a fragment size for a file system, at least
two considerations should be given. The major performance
tradeoffs observed are between an 8 kbyte block file system
and a 4 kbyte block file system. Because of implementation
constraints, the block size / fragment size ratio can not
be greater than 8. This means that an 8 kbyte file system
will always have a fragment size of at least 1 kbytes. If
a file system is created with a 4 kbyte block size and a
1 kbyte fragment size, then upgraded to an 8 kbyte block size
and 1 kbyte fragment size, identical space compaction will be
observed. However, if a file system has a 4 kbyte block size
and 512 byte fragment size, converting it to an 8K/1K
file system will result in significantly more space being
used. This implies that 4 kbyte block file systems that
might be upgraded to 8 kbyte blocks for higher performance should
use fragment sizes of at least 1 kbytes to minimize the amount
of work required in conversion.
A second, more important, consideration when selecting the
fragment size for a file system is the level of fragmentation
on the disk. With an 8:1 fragment to block ratio, storage fragmentation
occurs much sooner, particularly with a busy file system running
near full capacity. By comparison, the level of fragmentation in a
4:1 fragment to block ratio file system is one tenth as severe. This
means that on file systems where many files are created and
deleted, the 512 byte fragment size is more likely to result in apparent
space exhaustion because of fragmentation. That is, when the file
system is nearly full, file expansion that requires locating a
contiguous area of disk space is more likely to fail on a 512
byte file system than on a 1 kbyte file system. To minimize
fragmentation problems of this sort, a parameter in the super
block specifies a minimum acceptable free space threshold. When
normal users (i.e. anyone but the super-user) attempt to allocate
disk space and the free space threshold is exceeded, the user is
returned an error as if the file system were really full. This
parameter is nominally set to 10%; it may be changed by supplying
a parameter to \fInewfs\fP(8), or by updating the super block of an
existing file system using \fItunefs\fP\|(8).
In general, unless a file system is to be used
for a special purpose application (for example, storing
image processing data), we recommend using the
Remember that the current
implementation limits the block size to at most 8 kbytes
and the ratio of block size / fragment size must be 1, 2, 4, or 8.
The disk geometry information used by the file system
affects the block layout policies employed. The file
/etc/disktab, as supplied, contains the data for most
all drives supported by the system. Before constructing
a file system with \fInewfs\fP\|(8)
you should label the disk (if it has not yet been labeled,
and the driver supports labels).
If labels cannot be used, you must instead
specify the type of disk on which the file system resides;
\fInewfs\fP then reads /etc/disktab instead of the pack label.
This file also contains the default
sizes, and default block and fragment sizes. To
override any of the default values you can modify the file,
or use an option to \fInewfs\fP.
To put a chosen disk layout into effect, you should use the
command to create each new file system.
Each file system must also be added to the file
so that it will be checked and mounted when the system is bootstrapped.
As an example, consider a system with \*(Dn's. On the first \*(Dn, \*(Dk0,
we will put the root file system in \*(Dk0a, and the /usr
file system in \*(Dk0\*(pa, which has enough space to hold it and then some.
The /tmp directory will be part of the root file system,
as no file system will be mounted on /tmp.
If we had only one \*(Dn, we would put user files
in the \*(Dk0\*(pa partition with the system source and binaries.
If we had a second \*(Dn, we would place \fI/usr\fP in \*(Dk1\*(Pa.
We would put user files in \*(Dk0g, calling the file system /a.
We would also interleave the paging
between the 2 \*(Dn's. To do this we would build a system configuration
config vmunix root on \*(Dk0 swap on \*(Dk0 and \*(Dk1
to get the swap interleaved, and \fI/etc/fstab\fP would then contain
We would keep a backup copy of the root
file system in the \fB\*(Dk1a\fP disk partition.
Alternatively, that partition could be used for \fI/tmp\fP.
To make the /a file system we would do:
\fB#\fP \fIMAKEDEV \*(Dk1\fP
\fB#\fP \fIdisklabel -wr \*(Dk1 \*(Dn "disk name"\fP
\fB#\fP \fInewfs \*(Dk1\*(Pa\fP
(information about file system prints out)
\fB#\fP \fImount /dev/\*(Dk1\*(Pa /a\fP
If UNIX is to support simultaneous
access from directly-connected terminals other than the console,
the file \fI/etc/ttys\fP (\fIttys\fP\|(5)) must be edited.
Terminals connected via DZ11 interfaces are conventionally named \fBttyDD\fP
where DD is a decimal number, the ``minor device'' number.
The lines on dz0 are named /dev/tty00, /dev/tty01, ... /dev/tty07.
By convention, all other terminal names are of the form \fBtty\fPCX, where
C is an alphabetic character according to the type of terminal multiplexor
and X is a digit for the first ten lines on the interface
and an increasing lower case letter for the rest of the lines.
C is defined for the number of interfaces of each type listed below.
Interface Number of lines Number of
Type Characters per board Interfaces
Terminals connected via VIOC-X interfaces are conventionally named tty\fIDD\fP
where \fIDD\fP is a hexadecimal number, the ``minor device'' number.
The first digit is the multiplexor unit number, and the second digit
For VIOC's with fewer than 16 connectors, the missing unit numbers are unused.
Terminals connected using 16 port MPCC interfaces are conventionally named
tty\fICD\fP where \fIC\fP is a single upper-case letter and \fID\fP is a
single hexidecimal digit. The upper-case letter is the multiplexor unit
number (with \fIA\fP being mpcc 0) and the hexidecimal digit is the port
To add a new terminal device, be sure the device is configured into the system
and that the special files for the device have been made by /dev/MAKEDEV.
(For example, use ``cd /dev; MAKEDEV dz1'' to make the special files
(For example, use ``cd /dev; MAKEDEV vx1'' to make the special files
Then, enable the appropriate lines of /etc/ttys by setting the ``status''
field to \fBon\fP (or add new lines).
Note that lines in \fI/etc/ttys\fP are one-for-one with entries
in the file of current users (\fI/etc/utmp\fP),
and therefore it is best to make changes
while running in single-user mode
and to add all of the entries for a new device at once.
To add mpcc controllers, and additional step is required. At boot time,
the firmware for each mpcc controller must be downloaded. The program
\fI/etc/dlmpcc\fP must therefore be invoked from \fI/etc/rc.local\fP.
The file \fI/etc/mpcctab\fP describes each mpcc controller and is used
by \fI/etc/dlmpcc\fP to determine how many mpcc's are on the system.
See \fImpcc\fP(4) and \fIdlmpcc\fP(8) for more information.
The format of the /etc/ttys file is completely new in 4.3BSD.
Each line in the file is broken into four tab separated
fields (comments are shown by a `#' character and extend to
the end of the line). For each terminal line the four fields
the device (without a leading /dev),
the program /etc/init should startup to service the line
(or \fBnone\fP if the line is to be left alone),
the terminal type (found in /etc/termcap),
and optional status information describing if the terminal is
enabled or not and if it is ``secure'' (i.e. the super user should
be allowed to login on the line). All fields are character strings
with entries requiring embedded white space enclosed in double
Thus a newly added terminal /dev/tty00 could be added as
tty00 "/etc/getty std.9600" vt100 on secure # mike's office
The std.9600 parameter provided
to /etc/getty is used in searching the file /etc/gettytab; it specifies
a terminal's characteristics (such as baud rate).
To make custom terminal types, consult
before modifying /etc/gettytab.
Dialup terminals should be wired so that carrier is asserted only when the
For non-dialup terminals, from which modem control is not available,
you must either wire back the signals so that
the carrier appears to always be present, or show in the system
configuration that carrier is to be assumed to be present
with \fIflags\fP for each terminal device. See
you must wire back the signals so that
the carrier appears to always be present. For further details, see
For network terminals (i.e. pseudo terminals), no program should
be started up on the lines. Thus, the normal entry in /etc/ttys
(Note, the fourth field is not needed here.)
When the system is running multi-user, all terminals that are listed
in /etc/ttys as \fBon\fP have their line enabled.
If, during normal operations, you wish
to disable a terminal line, you can edit the file
to change the terminal's status to \fBoff\fP and
then send a hangup signal to the \fIinit\fP process, by doing
Terminals can similarly be enabled by changing the status field
from \fBoff\fP to \fBon\fP and sending a hangup signal to \fIinit\fP.
Note that if a special file is inaccessible when \fIinit\fP tries
to create a process for it, init will log a message to the
system error logging process (/etc/syslogd)
and try to reopen the terminal every minute, reprinting the warning
message every 10 minutes. Messages of this sort are normally
printed on the console, though other actions may occur depending
on the configuration information found in /etc/syslog.conf.
Finally note that you should change the names of any dialup
where ? is in [0-9a-zA-Z], as some programs use this property of the
names to determine if a terminal is a dialup.
Shell commands to do this should be put in the /dev/MAKEDEV.local
While it is possible to use truly arbitrary strings for terminal names,
the accounting and noticeably the
command make good use of the convention that tty names
(by default, and also after dialups are named as suggested above)
are distinct in the last 2 characters.
Change this and you may be sorry later, as the heuristic
uses based on these conventions will then break down and \fIps\fP will
The procedure for adding a new user is described in \fIadduser\fP(8).
You should add accounts for the initial user community, giving
each a directory and a password, and putting users who will wish
to share software in the same groups.
Several guest accounts have been provided on the distribution
system; these accounts are for people at Berkeley,
Bell Laboratories, and others
who have done major work on UNIX in the past. You can delete these accounts,
or leave them on the system if you expect that these people would have
occasion to login as guests on your system.
All programs that require the site's name, or some similar
characteristic, obtain the information through system calls
or from files located in /etc. Aside from parts of the
system related to the network, to tailor the system to your
site you must simply select a site name, then edit the file
The first lines in /etc/netstart use a variable to set the hostname,
hostname=\fImysitename\fP
to define the value returned by the
system call. If you are running the name server, your site
name should be your fully qualified domain name. Programs such as
use this system call so that the binary images are site
Setting up the line printer system
The line printer system consists of at least
the following files and commands:
/usr/ucb/lpq spooling queue examination program
/usr/ucb/lprm program to delete jobs from a queue
/usr/ucb/lpr program to enter a job in a printer queue
/etc/printcap printer configuration and capability data base
/usr/lib/lpd line printer daemon, scans spooling queues
/etc/lpc line printer control program
/etc/hosts.lpd list of host allowed to use the printers
The file /etc/printcap is a master data base describing line
printers directly attached to a machine and, also, printers
accessible across a network. The manual page
describes the format of this data base and also
shows the default values for such things as the directory
in which spooling is performed. The line printer system handles
multiple printers, multiple spooling queues, local and remote
printers, and also printers attached via serial lines that require
line initialization such as the baud rate. Raster output devices
such as a Varian or Versatec, and laser printers such as an Imagen,
are also supported by the line printer system.
Remote spooling via the network is handled with two spooling
queues, one on the local machine and one on the remote machine.
When a remote printer job is started with
queued locally and a daemon process created to oversee the
transfer of the job to the remote machine. If the destination
machine is unreachable, the job will remain queued until it is
possible to transfer the files to the spooling queue on the
program shows the contents of spool
queues on both the local and remote machines.
To configure your line printers, consult the printcap manual page
and the accompanying document, ``4.3BSD Line Printer Spooler Manual''.
program should be present in /etc/rc.
Setting up the mail system
The mail system consists of the following commands:
/bin/mail old standard mail program, described in \fIbinmail\fP\|(1)
/usr/ucb/mail UCB mail program, described in \fImail\fP\|(1)
/usr/lib/sendmail mail routing program
/usr/spool/mail mail spooling directory
/usr/spool/secretmail secure mail directory
/usr/bin/xsend secure mail sender
/usr/bin/xget secure mail receiver
/usr/lib/aliases mail forwarding information
/usr/ucb/newaliases command to rebuild binary forwarding database
/usr/ucb/biff mail notification enabler
/etc/comsat mail notification daemon
Mail is normally sent and received using the
command (found in /usr/ucb/mail),
which provides a front-end to edit the messages sent
and received, and passes the messages to
The routing algorithm uses knowledge of the network name syntax,
aliasing and forwarding information, and network topology, as
defined in the configuration file /usr/lib/sendmail.cf, to
process each piece of mail.
Local mail is delivered by giving it to the program /bin/mail
that adds it to the mailboxes in the directory /usr/spool/mail/\fIusername\fP,
using a locking protocol to avoid problems with simultaneous updates.
After the mail is delivered, the local mail delivery daemon /etc/comsat
is notified, which in turn notifies
users who have issued a ``\fIbiff\fP y'' command that mail has arrived.
Mail queued in the directory /usr/spool/mail is normally readable
only by the recipient. To send mail that is secure against perusal
(except by a code-breaker) you should use the secret mail facility,
To set up the mail facility you should read the instructions in the
file READ_ME in the directory /usr/src/usr.lib/sendmail and then adjust
the necessary configuration files.
You should also set up the file /usr/lib/aliases for your installation,
creating mail groups as appropriate. Documents describing
operation and installation are also included in the distribution.
Setting up a UUCP connection
The version of \fIuucp\fP included in \*(4B is a greatly
enhanced version of the one originally distributed with 32/V*.
* The \fIuucp\fP included in this distribution is the result
of work by many people; we gratefully acknowledge their
contributions, but refrain from mentioning names in the
interest of keeping this document current.
The enhancements include:
support for many auto call units and dialers
in addition to the DEC DN11,
breakup of the spooling area into multiple subdirectories,
addition of an \fIL.cmds\fP file to control the set
of commands that may be executed by a remote site,
enhanced ``expect-send'' sequence capabilities when
logging in to a remote site,
new commands to be used in polling sites and
obtaining snap shots of \fIuucp\fP activity,
additional protocols for different communication media.
This section gives a brief overview of \fIuucp\fP
and points out the most important steps in its installation.
To connect two UNIX machines with a \fIuucp\fP network link using modems,
one site must have an automatic call unit
and the other must have a dialup port.
It is better if both sites have both.
You should first read the paper in the UNIX System Manager's Manual:
``Uucp Implementation Description''.
It describes in detail the file formats and conventions,
and will give you a little context.
the document ``setup.tblms'',
located in the directory /usr/src/usr.bin/uucp/UUAIDS,
may be of use in tailoring the software to your needs.
The \fIuucp\fP support is located in three major directories:
User commands are kept in /usr/bin,
operational commands in /usr/lib/uucp,
and /usr/spool/uucp is used as a spooling area.
The commands in /usr/bin are:
/usr/bin/uucp file-copy command
/usr/bin/uux remote execution command
/usr/bin/uusend binary file transfer using mail
/usr/bin/uuencode binary file encoder (for \fIuusend\fP)
/usr/bin/uudecode binary file decoder (for \fIuusend\fP)
/usr/bin/uulog scans session log files
/usr/bin/uusnap gives a snap-shot of \fIuucp\fP activity
/usr/bin/uupoll polls remote system until an answer is received
/usr/bin/uuname prints a list of known uucp hosts
/usr/bin/uuq gives information about the queue
The important files and commands in /usr/lib/uucp are:
/usr/lib/uucp/L-devices list of dialers and hard-wired lines
/usr/lib/uucp/L-dialcodes dialcode abbreviations
/usr/lib/uucp/L.aliases hostname aliases
/usr/lib/uucp/L.cmds commands remote sites may execute
/usr/lib/uucp/L.sys systems to communicate with, how to connect, and when
/usr/lib/uucp/SEQF sequence numbering control file
/usr/lib/uucp/USERFILE remote site pathname access specifications
/usr/lib/uucp/uucico \fIuucp\fP protocol daemon
/usr/lib/uucp/uuclean cleans up garbage files in spool area
/usr/lib/uucp/uuxqt \fIuucp\fP remote execution server
while the spooling area contains the following important files and directories:
/usr/spool/uucp/C. directory for command, ``C.'' files
/usr/spool/uucp/D. directory for data, ``D.'', files
/usr/spool/uucp/X. directory for command execution, ``X.'', files
/usr/spool/uucp/D.\fImachine\fP directory for local ``D.'' files
/usr/spool/uucp/D.\fImachine\fPX directory for local ``X.'' files
/usr/spool/uucp/TM. directory for temporary, ``TM.'', files
/usr/spool/uucp/LOGFILE log file of \fIuucp\fP activity
/usr/spool/uucp/SYSLOG log file of \fIuucp\fP file transfers
To install \fIuucp\fP on your system,
start by selecting a site name
(shorter than 14 characters).
A \fIuucp\fP account must be created in the password file and a password set up.
create the appropriate spooling directories with mode 755
and owned by user \fIuucp\fP, group \fIdaemon\fP.
If you have an auto-call unit,
the L.sys, L-dialcodes, and L-devices files should be created.
The L.sys file should contain
the phone numbers and login sequences
required to establish a connection with a \fIuucp\fP daemon on another machine.
For example, our L.sys file looks something like:
adiron Any ACU 1200 out0123456789- ogin-EOT-ogin uucp
chico Never Slave 1200 out2010123456
The first field is the name of a site,
the second shows when the machine may be called,
the third field specifies how the host is connected
(through an ACU, a hard-wired line, etc.),
then comes the phone number to use in connecting through an auto-call unit,
and finally a login sequence.
may contain common abbreviations that are defined in the L-dialcodes file.
The device specification should refer to devices
specified in the L-devices file.
Listing only ACU causes the \fIuucp\fP daemon, \fIuucico\fP,
to search for any available auto-call unit in L-devices.
Our L-dialcodes file is of the form:
while our L-devices file is:
ACU cul0 unused 1200 ventel
Refer to the README file in the \fIuucp\fP source directory
for more information about installation.
As \fIuucp\fP operates it creates (and removes) many small
files in the directories underneath /usr/spool/uucp.
Sometimes files are left undeleted;
these are most easily purged with the \fIuuclean\fP program.
The log files can grow without bound unless trimmed back;
\fIuulog\fP maintains these files.
Many useful aids in maintaining your \fIuucp\fP installation
are included in a subdirectory UUAIDS beneath /usr/src/usr.bin/uucp.
Peruse this directory and read the ``setup'' instructions also located there.
projects / unix-history / blob