docs: Added All NetBSD Manuals

1 files changed, 87 insertions, 0 deletions

diff --git a/static/netbsd/man8/man8.prep/boot.8 3.html b/static/netbsd/man8/man8.prep/boot.8 3.html
new file mode 100644
index 00000000..aa126c52
--- /dev/null
+++ b/static/netbsd/man8/man8.prep/boot.8 3.html
@@ -0,0 +1,87 @@
+<table class="head">
+  <tr>
+    <td class="head-ltitle">BOOT(8)</td>
+    <td class="head-vol">System Manager's Manual (prep)</td>
+    <td class="head-rtitle">BOOT(8)</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">boot</code> &#x2014; <span class="Nd">system
+    bootstrapping procedures</span></p>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
+<table class="Nm">
+  <tr>
+    <td><code class="Nm">boot</code></td>
+    <td></td>
+  </tr>
+</table>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
+<section class="Ss">
+<h2 class="Ss" id="Power_fail_and_crash_recovery"><a class="permalink" href="#Power_fail_and_crash_recovery">Power
+  fail and crash recovery</a></h2>
+<p class="Pp">Normally, the system will reboot itself at power-up or after
+    crashes. An automatic consistency check of the file systems will be
+    performed as described in <a class="Xr">fsck(8)</a>, and unless this fails,
+    the system will resume multi-user operations.</p>
+</section>
+<section class="Ss">
+<h2 class="Ss" id="Cold_starts"><a class="permalink" href="#Cold_starts">Cold
+  starts</a></h2>
+<p class="Pp">The prep architecture does not allow the direct booting of a
+    kernel from the hard drive. Instead it requires a complete boot image to be
+    loaded. This boot image contains a <span class="Ux">NetBSD</span> kernel,
+    which will then provide access to the devices on the machine. The image can
+    be placed on any device that the firmware considers a bootable device.
+    Usually this is either a SCSI disk, tape, CD-ROM, or floppy drive.</p>
+</section>
+<section class="Ss">
+<h2 class="Ss" id="Boot_program_options"><a class="permalink" href="#Boot_program_options">Boot
+  program options</a></h2>
+<p class="Pp">The prep architecture and bootloader does not support any option
+    parsing at the boot prompt.</p>
+</section>
+<section class="Ss">
+<h2 class="Ss" id="Boot_partition"><a class="permalink" href="#Boot_partition">Boot
+  partition</a></h2>
+<p class="Pp">The prep port requires a special boot partition on the primary
+    boot device in order to load the kernel. This partition consists of a
+    PC-style i386 partition label, a small bootloader, and a kernel image. The
+    prep firmware looks for a partition of type 0x41 (65) and expects the
+    bootloader, immediately followed by the kernel, to be there. The
+    <a class="Xr">prep/mkbootimage(8)</a> command needs to be used to generate
+    this image.</p>
+</section>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1>
+<dl class="Bl-tag Bl-compact">
+  <dt><span class="Pa">/netbsd</span></dt>
+  <dd>system code</dd>
+  <dt><span class="Pa">/usr/mdec/boot</span></dt>
+  <dd>system bootstrap</dd>
+  <dt><span class="Pa">/usr/mdec/boot_com0</span></dt>
+  <dd>system bootstrap with serial console</dd>
+</dl>
+</section>
+<section class="Sh">
+<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
+  ALSO</a></h1>
+<p class="Pp"><a class="Xr">disklabel(8)</a>, <a class="Xr">fsck(8)</a>,
+    <a class="Xr">halt(8)</a>, <a class="Xr">init(8)</a>,
+    <a class="Xr">installboot(8)</a>, <a class="Xr">prep/mkbootimage(8)</a>,
+    <a class="Xr">rc(8)</a>, <a class="Xr">shutdown(8)</a>,
+    <a class="Xr">syslogd(8)</a></p>
+</section>
+</div>
+<table class="foot">
+  <tr>
+    <td class="foot-date">February 17, 2017</td>
+    <td class="foot-os">NetBSD 10.1</td>
+  </tr>
+</table>