Return to rk.4 CVS log

Up to [Research Unix] / researchv10dc / man / manb

Annotation of researchv10dc/man/manb/rk.4, revision 1.1.1.1

1.1       root        1: .TH RK 4
                      2: .SH NAME
                      3: rk \- RK11/RK07 disk driver
                      4: .SH DESCRIPTION
                      5: Files with minor device numbers 0 through 7
                      6: refer to various portions of drive 0,
                      7: minor devices 8 through 16 refer to drive 1,
                      8: etc.
                      9: .PP
                     10: The range and size of the pseudo-drives for each drive
                     11: are as follows:
                     12: .PP
                     13: .nf
                     14: .ta .5i +\w'000000    'u +\w'000000    'u
                     15: RK07 partitions:
                     16:        disk    start   length
                     17:        0       0       15884
                     18:        1       15906   10032
                     19:        2       0       53780
                     20:        3       0       0
                     21:        4       0       0
                     22:        5       0       0
                     23:        6       26004   27786
                     24:        7       0       0
                     25: .DT
                     26: .fi
                     27: .PP
                     28: On a dual RK07 system
                     29: partition 0 is used
                     30: for the root for one drive
                     31: and partition 6 for the /usr file system.
                     32: If large jobs are to be run,
                     33: partition 1 on both drives provides a 10Mbyte paging area.
                     34: Otherwise
                     35: partition 2 on the other drive
                     36: is used as a single large file system.
                     37: .PP
                     38: The
                     39: .I rk
                     40: files
                     41: discussed above access the disk via the system's normal
                     42: buffering mechanism
                     43: and may be read and written without regard to
                     44: physical disk records.
                     45: There is also a `raw' interface
                     46: which provides for direct transmission between the disk
                     47: and the user's read or write buffer.
                     48: A single read or write call results in exactly one I/O operation
                     49: and therefore raw I/O is considerably more efficient when
                     50: many words are transmitted.
                     51: The names of the raw RK files
                     52: begin with
                     53: .L rrk
                     54: and end with a number which selects the same disk
                     55: as the corresponding
                     56: .L rk
                     57: file.
                     58: .PP
                     59: In raw I/O the buffer must begin on a word boundary,
                     60: and counts should be a multiple of 512 bytes
                     61: (a disk block).
                     62: Likewise
                     63: .IR lseek (2)
                     64: calls should specify a multiple of 512 bytes.
                     65: .SH FILES
                     66: .F /dev/rk?
                     67: .br
                     68: .F /dev/rrk?"
                     69: .SH BUGS
                     70: In raw I/O
                     71: .I read
                     72: and
                     73: .IR write (2)
                     74: truncate file offsets to 512-byte block boundaries,
                     75: and
                     76: .I write
                     77: scribbles on the tail of incomplete blocks.
                     78: Thus,
                     79: in programs that are likely to access raw devices,
                     80: .I read, write
                     81: and
                     82: .IR lseek (2)
                     83: should always deal in 512-byte multiples.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.