1RL(4)                      Kernel Interfaces Manual                      RL(4)
2
3
4

NAME

6       rl - RL-11/RL01, RL02 moving-head disk
7

SYNOPSIS

9       /sys/conf/SYSTEM:
10            NRL  rl_drives # RL01/02
11
12       /etc/dtab:
13            #Name Unit# Addr   Vector Br Handler(s)      # Comments
14            rl    ?     174400 160    5  rlintr          # rl-01/02
15
16       major device number(s):
17            raw: 16
18            block: 7
19       minor device encoding:
20            bits 0007 specify partition of RL drive
21            bits 0070 specify RL drive
22

DESCRIPTION

24       The block files access the disk via the system's normal buffering mech‐
25       anism and may be read and  written  without  regard  to  physical  disk
26       records.   There  is  also  a `raw' interface which provides for direct
27       transmission between the disk and the user's read or write  buffer.   A
28       single  read  or  write  call  results in exactly one I/O operation and
29       therefore raw I/O is considerably more efficient when  many  words  are
30       transmitted.   The  names of the raw files conventionally begin with an
31       extra `r.'
32
33       In raw I/O the buffer must begin on a word (even) boundary, and  counts
34       should be a multiple of 512 bytes (a disk sector).  Likewise seek calls
35       should specify a multiple of 512 bytes.
36

DISK SUPPORT

38       The RL01 drives are each 10240 blocks long  and  the  RL02  drives  are
39       20480 blocks long.
40
41       On  a  RL02  there  is room for a full sized root ('a') partition and a
42       reasonable sized swap ('b') partition.  The RL01  can  only  (realisti‐
43       cally) have a single 5mb partition.
44

FILES

46       /dev/rl[0-3][a-h]   block files
47       /dev/rrl[0-3][a-h]  raw files
48       /dev/MAKEDEV        script to create special files
49       /dev/MAKEDEV.local  script to localize special files
50

SEE ALSO

52       hk(4), ra(4), ram(4), rk(4), rp(4), rx(4), si(4), xp(4), dtab(5), auto‐
53       config(8)
54

DIAGNOSTICS

56       rl%d: hard error sn%d cs=%b da=%b.   An  unrecoverable  error  occurred
57       during  transfer  of  the  specified sector of the specified disk.  The
58       contents of the two error registers are also printed in octal and  sym‐
59       bolically  with bits decoded.  The error was either unrecoverable, or a
60       large number of retry attempts could not recover the error.
61
62       rl%d: hard error  sn%d  mp=%b  da=%b.   An  unrecoverable  drive  error
63       occured  during transfer of the specified sector of the specified disk.
64       The contents of the two error registers are also printed in  octal  and
65       symbolically with bits decoded.  The error was either unrecoverable, or
66       a large number of retry attempts could not recover the error.
67
68       rl%d: write locked.  The write protect switch was set on the drive when
69       a write was attempted.  The write operation is not recoverable.
70
71       rl%d:  can't  get  status.   A  ``get status'' command on the specified
72       drive failed.  The error is unrecoverable.
73

BUGS

75       In raw I/O read and write(2) truncate file offsets  to  512-byte  block
76       boundaries,  and  write  scribbles  on  the  tail of incomplete blocks.
77       Thus, in programs that are likely to access raw  devices,  read,  write
78       and lseek(2) should always deal in 512-byte multiples.
79
80       DEC-standard error logging should be supported.
81
82       A  program to analyze the logged error information (even in its present
83       reduced form) is needed.
84
85
86
873rd Berkeley Distribution       August 20, 1987                          RL(4)
Impressum