glm94/pdp7-unix
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

I've converted all the man pages so far into roff format.

Browse Source
This commit is contained in:
Warren Toomey
2016-03-28 13:24:27 +10:00
parent dfb61a274f
commit fed6525853
9 changed files with 344 additions and 293 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/chrm.1
+38 -26
View File
@@ -1,26 +1,38 @@
11/3/70 CHRM (I) .oh '11/3/70''CHRM(I)'
.ta 18 21
NAME chrm -- remove (unlink) files
NAME chrm -- remove (unlink) files .sp
SYNOPSIS
SYNOPSIS chrm directory name1 ... .ul
chrm
DESCRIPTION chrm removes the entries for one or more files from the directory name1 ...
named directory. If an entry was the last link to the file, .sp
the file is destroyed. Removal of a file requires write DESCRIPTION
permission in its directory, but neither read nor write .ul
permission on the file itself. chrm
removes the entries for one or more files
Directories cannot be removed by rm; cf. rmdir. from the named directory. If an entry was the
last link to the file, the file is destroyed.
FILES none. Removal of a file requires write permission in
its directory, but neither read nor write
SEE ALSO rmdir, for removing directories. permission on the file itself.
.sp
DIAGNOSTICS If the file cannot be removed or does not exist, the name Directories cannot be removed by
of the file followed by a question mark is typed. .ul
chrm.
BUGS rm probably should ask whether a read-only file is really .sp
to be removed. FILES --
.sp
OWNER ken, dmr SEE ALSO --
.sp
DIAGNOSTICS If the file cannot be removed or does not exist,
the name of the file followed by a question mark
is typed.
.sp
BUGS
.ul
chrm
probably should ask whether a read-only
file is really to be removed.
.sp
OWNER ken, dmr
man/cp.1
+25 -23
View File
@@ -1,23 +1,25 @@
11/3/70 CP (I) .oh '11/3/70''CP(I)'
.ta 18 21
NAME cp -- copy
NAME cp -- copy .sp
SYNOPSIS
SYNOPSIS cp file11 file12 file21 file22 ... .ul
cp
DESCRIPTION Files are taken in pairs; the first is opened for reading, file11 file12 file21 file22 ...
the second created mode 17. Then the first is copied into .sp
the second. DESCRIPTION Files are taken in pairs; the first is opened
for reading, the second created mode 17. Then
FILES the first is copied into the second.
.sp
SEE ALSO cat, pr FILES --
.sp
DIAGNOSTICS Error returns are checked at every system call, and SEE ALSO cat, pr
appropriate diagnostics are produced. .sp
DIAGNOSTICS Error returns are checked at every system call,
BUGS The second file should be created in the mode of the first. and appropriate diagnostics are produced.
.sp
A directory convention as used in mv should be adopted to cp. BUGS The second file should be created in the mode of
the first. A directory convention as used in mv
OWNER ken, dmr should be adopted to cp.
.sp
OWNER ken, dmr
man/date.1
+19 -18
View File
@@ -1,19 +1,20 @@
11/3/70 DATE (I) .oh '11/3/70''DATE(I)'
.ta 18 21
NAME date - print the date
NAME date - print the date .sp
SYNOPSIS
SYNOPSIS date .ul
date
DESCRIPTION The current date is printed to the second. .sp
DESCRIPTION The current date is printed to the second.
FILES .sp
FILES --
SEE ALSO .sp
SEE ALSO --
DIAGNOSTICS It is always 1970. .sp
DIAGNOSTICS --
BUGS .sp
BUGS It is always 1970.
OWNER wkt .sp
OWNER wkt
man/dir.5
+36 -34
View File
@@ -1,34 +1,36 @@
11/3/70 DIRECTORY (V) .oh '11/3/70''DIRECTORY(I)'
.ta 18 21
NAME format of directories
NAME format of directories .sp
SYNOPSIS --
SYNOPSIS .sp
DESCRIPTION A directory behaves exactly like an ordinary
DESCRIPTION A directory behaves exactly like an ordinary file, save file, save that no user may write into a
that no user may write into a directory. The fact that a directory. The fact that a file is a directory
file is a directory is indicated by a bit in the flag word is indicated by a bit in the flag word of its
of its i-node entry. i-node entry.
.sp
Directory entries are 8 words long. The first word is the Directory entries are 8 words long. The first
i-node of the file represented by the entry, if non-zero; word is the i-node of the file represented by
if zero, the entry is empty. the entry, if non-zero; if zero, the entry is
empty.
Words 1-4 represent the (8-character) file name, space .sp
padded on the right. These words are not necessarily Words 1-4 represent the (8-character) file name,
cleared for empty slots. space padded on the right. These words are not
necessarily cleared for empty slots.
By convention, the first entry in each directory is .sp
for "dd", which is the "directory directory" that holds By convention, the first entry in each directory
all the users' home directories and the "system" directory. is for "dd", which is the "directory directory"
The "system" directory contains "init" and "sh". that holds all the users' home directories and
the "system" directory. The "system" directory
FILES contains "init" and "sh".
.sp
SEE ALSO file system format FILES --
.sp
DIAGNOSTICS SEE ALSO file system format
.sp
BUGS DIAGNOSTICS --
.sp
OWNER ken, dmr BUGS --
.sp
OWNER ken, dmr
man/filesys.5
+119 -104
View File
@@ -1,104 +1,119 @@
11/3/70 FILE SYSTEM (V) .oh '11/3/70''FILE SYSTEM(V)'
.ta 18 21 24
NAME format of file system
NAME format of file system .sp
SYNOPSIS --
SYNOPSIS .sp
DESCRIPTION The RB09 fixed head disk has 8,000 64-word
DESCRIPTION The RB09 fixed head disk has 8,000 64-word blocks on blocks on each of its two surfaces. Unix uses
each of its two surfaces. Unix uses the second surface the second surface (physical blocks 8,000 to
(physical blocks 8,000 to 15,999) and numbers them 15,999) and numbers them from logical block 0 to
from logical block 0 to logical block 7,999. The following logical block 7,999. The following discussion
discussion refers to logical blocks. refers to logical blocks.
.sp
The Unix filesystem is divided into 8,000 blocks of 64 words The Unix filesystem is divided into 8,000 blocks
per block. Block 0 is the "sysdata" block. The first word of 64 words per block. Block 0 is the "sysdata"
points to the first block of the free-storage map. Each block block. The first word points to the first block
in the free-storage map is structured as follows: the first of the free-storage map. Each block in the
word is the block number of the next block in the free-storage free-storage map is structured as follows: the
map, or zero if this is the end of the free-storage map. The first word is the block number of the next block
next nine words hold free block numbers, or zero (no block number). in the free-storage map, or zero if this is the
end of the free-storage map. The next nine words
Block 1 on the filesystem is unused. (?) hold free block numbers, or zero (no block
number).
I-numbers begin at 1, and the storage for i-nodes begins at .sp
block 2. Blocks 2 to 711 contain the i-nodes, with five Block 1 on the filesystem is unused. (?)
consecutive i-nodes per block. Certain i-nodes are reserved for .sp
special files, directories and devices: I-numbers begin at 1, and the storage for
i-nodes begins at block 2. Blocks 2 to 711
1 The core file written by "sys save" or a bad system call contain the i-nodes, with five consecutive
2 The "dd" directory directory i-nodes per block. Certain i-nodes are reserved
3 The "system" directory for special files, directories and devices:
6 The "ttyin" special file .sp
7 The "keyboard" (graphic-2) special file 1 The core file written by "sys save" or a
8 The "pptin" (paper tape reader) special file bad system call
10 The "ttyout" special file 2 The "dd" directory directory
11 The "display" (graphic-2) special file 3 The "system" directory
12 The "pptout" (paper tape punch) special file 6 The "ttyin" special file
7 The "keyboard" (graphic-2) special file
8 The "pptin" (paper tape reader) special
There is only one file system which is always mounted; file
it resides on the RB disk. This device is also used for 10 The "ttyout" special file
swapping. The swap areas are at the high blocks on this device: 11 The "display" (graphic-2) special file
blocks 6,400 to 7,999. These blocks do not appear in the free list. 12 The "pptout" (paper tape punch) special
file
Each i-node represents one file. The format of .sp
an i-node is as follows, where the left column represents There is only one file system which is always
the offset in words from the beginning of the i-node: mounted; it resides on the RB disk. This device
is also used for swapping. The swap areas are at
0 flags (see below) the high blocks on this device: blocks 6,400 to
1 first indirect block or contents block 7,999. These blocks do not appear in the free
... list.
7 seventh indirect block or contents block .sp
8 user ID of owner Each i-node represents one file. The format of
9 link count an i-node is as follows, where the left column
10 size in words represents the offset in words from the
11 unique value assigned at creation beginning of the i-node:
.sp
The flags are as follows: 0 flags (see below)
1 first indirect block or contents block
400000 i-node is allocated ...
200000 large file 7 seventh indirect block or contents block
?????? allocated bit (always on) 8 user ID of owner
000040 special file 9 link count
000020 directory 10 size in words
000010 read, owner 11 unique value assigned at creation
000004 write, owner .sp
000002 read, non-owner The flags are as follows:
000001 write, non-owner .sp
400000 i-node is allocated
The allocated bit (flag ??????) is believed even if the i-node 200000 large file
map says the i-node is free; thus corruption of the map may ?????? allocated bit (always on)
cause i-nodes to become unallocatable, but will not cause active 000040 special file
nodes to be reused. 000020 directory
000010 read, owner
Word number n of a file is accessed as follows: n is 000004 write, owner
divided by 64 to find its logical block number (say b) in 000002 read, non-owner
the file. If the file is small (flag 200000 is 0), then b 000001 write, non-owner
must be less than 7, and the physical block number corresponding .sp
to b is the bth entry in the address portion of the i-node. The allocated bit (flag ??????) is believed even
if the i-node map says the i-node is free; thus
If the file is large, b is divided by 64 to yield a number corruption of the map may cause i-nodes to
which must be less than 8 (or the file is too large for become unallocatable, but will not cause active
UNIX to handle). The corresponding slot in the i-node nodes to be reused.
address portion gives the physical block number of an .sp
indirect block. The residue mod 64 gives a word offset Word number n of a file is accessed as follows:
in the indirect block, and the word found there is the n is divided by 64 to find its logical block
physical address of the block corresponding to b. number (say b) in the file. If the file is small
(flag 200000 is 0), then b must be less than 7,
If block b in a file exists, it is not necessary that all and the physical block number corresponding to b
blocks less than b exist. A zero block number either in the is the bth entry in the address portion of the
address words of the i-node or in an indirect block i-node.
indicates that the corresponding block has never been .sp
allocated. Such a missing block reads as if it contained If the file is large, b is divided by 64 to
all zero words. yield a number which must be less than 8 (or
the file is too large for UNIX to handle).
FILES The corresponding slot in the i-node address
portion gives the physical block number of an
SEE ALSO format of directories indirect block. The residue mod 64 gives a
word offset in the indirect block, and the
DIAGNOSTICS word found there is the physical address of
the block corresponding to b.
BUGS .sp
If block b in a file exists, it is not necessary
OWNER that all blocks less than b exist. A zero block
number either in the address words of the i-node
or in an indirect block indicates that the
corresponding block has never been allocated.
Such a missing block reads as if it contained
all zero words.
.sp
FILES --
.sp
SEE ALSO format of directories
.sp
DIAGNOSTICS --
.sp
BUGS --
.sp
OWNER ken
man/ln.1
+21 -19
View File
@@ -1,19 +1,21 @@
11/3/70 LN (I) .oh '11/3/70''LN(I)'
.ta 18 30
NAME ln -- link to a file
NAME ln -- link to a file .sp
SYNOPSIS
SYNOPSIS ln name1 name2 .ul
ln
DESCRIPTION ln adds another filename to the first filename name1 name2
.sp
FILES DESCRIPTION ln adds another filename to the first filename
.sp
SEE ALSO FILES --
.sp
DIAGNOSTICS "twofiles" - please provide two filenames SEE ALSO --
"? file" - unable to make the link .sp
DIAGNOSTICS "twofiles" - please provide two filenames
BUGS "? file" - unable to make the link
.sp
OWNER wkt BUGS --
.sp
OWNER wkt
man/mv.1
+26 -19
View File
@@ -1,19 +1,26 @@
11/3/70 MV (I) .oh '11/3/70''MV(I)'
.ta 18 31
NAME mv -- move or rename a file
NAME mv -- move or rename a file .sp
SYNOPSIS
SYNOPSIS mv name1 name2 .ul
mv
DESCRIPTION mv changes the name of name with the rename system call. name1 name2
.sp
FILES DESCRIPTION
.ul
SEE ALSO mv
changes the name of name with the rename
DIAGNOSTICS "twofiles" - please provide two filenames system call.
"? file" - either unable to remove or create a file .sp
FILES --
BUGS The second diagnostic is ambiguous. .sp
SEE ALSO --
OWNER wkt .sp
DIAGNOSTICS "twofiles" - please provide two filenames
"? file" - either unable to remove or create
a file
.sp
BUGS The second diagnostic is ambiguous.
.sp
OWNER wkt
man/stat.1
+58 -50
View File
@@ -1,50 +1,58 @@
11/3/70 STAT (I) .oh '11/3/70''STAT(I)'
.ta 18 21
NAME stat - get file status
NAME stat - get file status .sp
SYNOPSIS
SYNOPSIS stat name .ul
stat
DESCRIPTION stat gives several kinds of information about one file: name
files: .sp
DESCRIPTION stat gives several kinds of information about
access mode one file:
number of links .sp
owner access mode
size in words number of links
name owner
size in words
All information is self-explanatory except the mode. The name
mode is a five-character string whose characters mean the .sp
following: All information is self-explanatory except the
mode. The mode is a five-character string whose
1 s: file is small (smaller than 4096 words) characters mean the following:
l: file is large .sp
d: file is a directory 1 s: file is small (smaller than 4096 words)
l: file is large
2 r: owner can read d: file is a directory
-: owner cannot read .sp
2 r: owner can read
3 w: owner can write -: owner cannot read
-: owner cannot write .sp
3 w: owner can write
4 r: non-owner can read -: owner cannot write
-: non-owner cannot read .sp
4 r: non-owner can read
5 w: non-owner can write -: non-owner cannot read
-: non-owner cannot write .sp
5 w: non-owner can write
All numeric values are printed in octal -: non-owner cannot write
if he cannot be found in "/etc/uids" a number is given. .sp
All numeric values are printed in octal.
.sp
FILES FILES
.sp
SEE ALSO ls with the -l option gives the same information as stat, SEE ALSO
except that it also shows the i-node number for each file. .ul
ls
DIAGNOSTICS "name ?" for any error. "nofiles" if no file name is given. with the -l option gives the same information
as
BUGS none .ul
stat,
OWNER wkt except that it also shows the i-node
number for each file.
.sp
DIAGNOSTICS "name ?" for any error.
"nofiles" if no file name is given.
.sp
BUGS none
.sp
OWNER wkt
tools/roff.c
+2
View File
@@ -43,6 +43,7 @@ int o_ll = 65, o_ad = 1, o_po = 0, o_ls = 1, o_ig = 0, o_fi = 1;
int o_pl = 66, o_ro = 0, o_hx = 0, o_sp = 0, o_sk = 0; int o_pl = 66, o_ro = 0, o_hx = 0, o_sp = 0, o_sk = 0;
int o_ce = 0, o_ul = 0; int o_ce = 0, o_ul = 0;
int o_li = 0, o_bp = -1, o_hy = 1; int o_li = 0, o_bp = -1, o_hy = 1;
int o_m2 = 1;
int o_nn = 0; /* #LINES TO SUPPRESS NUMBERING */ int o_nn = 0; /* #LINES TO SUPPRESS NUMBERING */
int o_ti = -1; /* TEMPORARY INDENT */ int o_ti = -1; /* TEMPORARY INDENT */
int page_no = -1; int page_no = -1;
@@ -779,6 +780,7 @@ void beginpage()
{ {
int i; int i;
writetitle(page_no & 1 ? ohead : ehead); writetitle(page_no & 1 ? ohead : ehead);
for (i = 0; i < o_m2; i++) spit('\n');
line_no = 0; line_no = 0;
} }