blob: eea9487aa6701a0667aeacc1bc2976967dae6db8 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
<table class="head">
<tr>
<td class="head-ltitle">DRUM(4)</td>
<td class="head-vol">Device Drivers Manual</td>
<td class="head-rtitle">DRUM(4)</td>
</tr>
</table>
<div class="manual-text">
<section class="Sh">
<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
<p class="Pp"><code class="Nm">drum</code> — <span class="Nd">paging
device</span></p>
</section>
<section class="Sh">
<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
<p class="Pp">This file refers to the paging device in use by the system. This
may actually be a subdevice of one of the disk drivers, but in a system with
paging interleaved across multiple disk drives it provides an indirect
driver for the multiple drives.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1>
<dl class="Bl-tag">
<dt><span class="Pa">/dev/drum</span></dt>
<dd style="width: auto;"> </dd>
</dl>
</section>
<section class="Sh">
<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
<p class="Pp">The <code class="Nm">drum</code> special file appeared in
<span class="Ux">3.0BSD</span>.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1>
<p class="Pp">Reads from the drum are not allowed across the interleaving
boundaries. Since these only occur every .5Mbytes or so, and since the
system never allocates blocks across the boundary, this is usually not a
problem.</p>
</section>
</div>
<table class="foot">
<tr>
<td class="foot-date">June 5, 1993</td>
<td class="foot-os">NetBSD 10.1</td>
</tr>
</table>
|