summaryrefslogtreecommitdiff
path: root/static/unix-v10/man4/rf.4
diff options
context:
space:
mode:
Diffstat (limited to 'static/unix-v10/man4/rf.4')
-rw-r--r--static/unix-v10/man4/rf.437
1 files changed, 37 insertions, 0 deletions
diff --git a/static/unix-v10/man4/rf.4 b/static/unix-v10/man4/rf.4
new file mode 100644
index 00000000..134889be
--- /dev/null
+++ b/static/unix-v10/man4/rf.4
@@ -0,0 +1,37 @@
+.pa 1
+.he 'RF (IV)'3/15/72'RF (IV)'
+.ti 0
+NAME rf -- RF11-RS11 fixed-head disk file
+.sp
+.ti 0
+DESCRIPTION This file refers to the
+concatenation of both RS-11 disks.
+It may be either read or written, although writing is inherently
+very dangerous, since
+a file system resides there.
+
+The disk contains 2048 256-word blocks,
+numbered 0 to 2047.
+Like the other block-structured devices (TC, RK)
+this file is addressed in blocks, not bytes.
+This has two consequences:
+seek____ calls refer to block numbers, not byte numbers;
+and sequential reading or writing always advance the read
+or write pointer by at least one block.
+Thus successive reads of 10 characters from this file
+actually read the first 10 characters from successive
+blocks.
+.sp
+.ti 0
+FILES /dev/rf0
+.sp
+.ti 0
+SEE ALSO tc(IV), rk(IV)
+.sp
+.ti 0
+BUGS The fact that this device
+is addressed in terms of blocks, not bytes, is extremely
+unfortunate. It is due entirely to the fact that
+read and write pointers (and consequently the arguments
+to seek____) are single-precision
+numbers.