diff options
Diffstat (limited to 'static/netbsd/man8')
49 files changed, 0 insertions, 9977 deletions
diff --git a/static/netbsd/man8/MAKEDEV.8 4.html b/static/netbsd/man8/MAKEDEV.8 4.html deleted file mode 100644 index 786c20ed..00000000 --- a/static/netbsd/man8/MAKEDEV.8 4.html +++ /dev/null @@ -1,815 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">MAKEDEV(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">MAKEDEV(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">MAKEDEV</code> — <span class="Nd">create - system and device special files</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">MAKEDEV</code></td> - <td>[<code class="Fl">-fMsu</code>] [<code class="Fl">-m</code> - <var class="Ar">mknod</var>] [<code class="Fl">-p</code> - <var class="Ar">pax</var>] [<code class="Fl">-t</code> - <var class="Ar">mtree</var>] {<var class="Ar">special</var> | - <var class="Ar">device</var>} [<var class="Ar">...</var>]</td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">MAKEDEV</code> is used to create system and - device special files. As arguments it takes the names of known devices, like - <var class="Ar">sd0</var>, or of special targets, like - <span class="Pa">all</span> or <span class="Pa">std</span>, which create a - collection of device special files, or <span class="Pa">local</span>, which - invokes <a class="Xr">MAKEDEV.local(8)</a> with the - <span class="Pa">all</span> argument.</p> -<p class="Pp">The script is in <span class="Pa">/dev/MAKEDEV</span>. Devices are - created in the current working directory; in normal use, - <code class="Nm">MAKEDEV</code> should be invoked with - <span class="Pa">/dev</span> as the current working directory.</p> -<p class="Pp">Supported options are:</p> -<dl class="Bl-tag"> - <dt id="f"><a class="permalink" href="#f"><code class="Fl">-f</code></a></dt> - <dd>Force permissions to be updated on existing devices. This works only if - <code class="Nm">MAKEDEV</code> invokes <a class="Xr">mknod(8)</a>; it is - not compatible with the <code class="Fl">-p</code>, - <code class="Fl">-s</code>, or <code class="Fl">-t</code> options.</dd> - <dt id="M"><a class="permalink" href="#M"><code class="Fl">-M</code></a></dt> - <dd>Create a memory file system, union mounted over the current directory, to - contain the device special files. The memory file system is created using - <a class="Xr">mount_tmpfs(8)</a> or <a class="Xr">mount_mfs(8)</a>, in - that order of preference. - <p class="Pp">If the <code class="Fl">-M</code> flag is specified more than - once, then <code class="Nm">MAKEDEV</code> assumes that it is being - invoked from <a class="Xr">init(8)</a> to populate a memory file system - for <span class="Pa">/dev</span>. In this case, - <code class="Nm">MAKEDEV</code> will also redirect its output to the - system console.</p> - </dd> - <dt id="m"><a class="permalink" href="#m"><code class="Fl">-m</code></a> - <var class="Ar">mknod</var></dt> - <dd>Force the use of <a class="Xr">mknod(8)</a>, and specify the name or path - to the <a class="Xr">mknod(8)</a> program. [Usually, $TOOL_MKNOD or - mknod.]</dd> - <dt id="p"><a class="permalink" href="#p"><code class="Fl">-p</code></a> - <var class="Ar">pax</var></dt> - <dd>Force the use of <a class="Xr">pax(1)</a>, and specify the name or path to - the <a class="Xr">pax(1)</a> program. [Usually, $TOOL_PAX or pax.]</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>Generate an <a class="Xr">mtree(8)</a> specfile instead of creating - devices.</dd> - <dt id="t"><a class="permalink" href="#t"><code class="Fl">-t</code></a> - <var class="Ar">mtree</var></dt> - <dd>Force the use of <a class="Xr">mtree(8)</a>, and specify the name or path - to the <a class="Xr">mtree(8)</a> program. [Usually, $TOOL_MTREE or - mtree.]</dd> - <dt id="u"><a class="permalink" href="#u"><code class="Fl">-u</code></a></dt> - <dd>Don't re-create devices that already exist.</dd> -</dl> -<p class="Pp"><code class="Nm">MAKEDEV</code> has several possible methods of - creating device nodes:</p> -<ul class="Bl-bullet"> - <li>By invoking the <a class="Xr">mknod(8)</a> command once for each device - node. This is the traditional method, but it is slow because each device - node is created using a new process. - <p class="Pp">The <code class="Fl">-m</code> option forces - <code class="Nm">MAKEDEV</code> to use the <a class="Xr">mknod(8)</a> - method.</p> - </li> - <li>By internally creating a specfile in a format usable by - <a class="Xr">mtree(8)</a>, and providing the specfile on standard input - to a <a class="Xr">pax(1)</a> or <a class="Xr">mtree(8)</a> command, - invoked with options that request it to create the device nodes as well as - any necessary subdirectories. This is much faster than creating device - nodes with <a class="Xr">mknod(8)</a>, because it requires much fewer - processes; however, it's not compatible with the - <code class="Fl">-f</code> option. - <p class="Pp">The <code class="Fl">-p</code> or <code class="Fl">-t</code> - options force <code class="Nm">MAKEDEV</code> to use the - <a class="Xr">pax(1)</a> or <a class="Xr">mtree(8)</a> methods.</p> - </li> - <li>If the <code class="Fl">-s</code> option is specified, then - <code class="Nm">MAKEDEV</code> will not create device nodes at all, but - will output a specfile in a format usable by - <a class="Xr">mtree(8)</a>.</li> -</ul> -<p class="Pp">The <code class="Fl">-m</code>, <code class="Fl">-p</code>, - <code class="Fl">-s</code>, and <code class="Fl">-t</code> flags are - mutually exclusive. If none of these flags is specified, then - <code class="Nm">MAKEDEV</code> will use <a class="Xr">mtree(8)</a>, - <a class="Xr">pax(1)</a>, or <a class="Xr">mknod(8)</a>, in that order of - preference, depending on which commands appear to be available and usable. - In normal use, it's expected that <a class="Xr">mtree(8)</a> will be - available, so it will be chosen. If <code class="Nm">MAKEDEV</code> is - invoked by <a class="Xr">init(8)</a>, it's expected that - <a class="Xr">mtree(8)</a> will not be available, but - <a class="Xr">pax(1)</a> may be available.</p> -<p class="Pp">The special targets supported on <span class="Ux">NetBSD</span> - are:</p> -<p class="Pp"></p> -<dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">all</var></dt> - <dd>Makes all known devices, including local devices. Tries to make the - 'standard' number of each type.</dd> - <dt><var class="Ar">init</var></dt> - <dd>A set of devices that is used for MFS /dev by init. May be equal to - ``all''.</dd> - <dt><var class="Ar">floppy</var></dt> - <dd>Devices to be put on install floppies</dd> - <dt><var class="Ar">ramdisk</var></dt> - <dd>Devices to be put into INSTALL kernel ramdisks.</dd> - <dt><var class="Ar">std</var></dt> - <dd>Standard devices</dd> - <dt><var class="Ar">local</var></dt> - <dd>Configuration specific devices</dd> - <dt><var class="Ar">lua</var></dt> - <dd>Lua device</dd> - <dt><var class="Ar">wscons</var></dt> - <dd>Make wscons devices</dd> - <dt><var class="Ar">usbs</var></dt> - <dd>Make USB devices</dd> -</dl> -<p class="Pp">Please note that any hash marks (“#”) in the - following list of supported device targets must be replaced by digits when - calling <code class="Nm">MAKEDEV</code>:</p> -<dl class="Bl-tag"> - <dt>Tapes:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">st#</var></dt> - <dd>SCSI tapes, see <a class="Xr">st(4)</a></dd> - <dt><var class="Ar">wt#</var></dt> - <dd>QIC-interfaced (e.g. not SCSI) 3M cartridge tape, see - <a class="Xr">wt(4)</a></dd> - <dt><var class="Ar">ht#</var></dt> - <dd>MASSBUS TM03 and TU??, see <a class="Xr">vax/ht(4)</a></dd> - <dt><var class="Ar">mt#</var></dt> - <dd>MSCP tapes (e.g. TU81, TK50), see <a class="Xr">vax/mt(4)</a></dd> - <dt><var class="Ar">tm#</var></dt> - <dd>UNIBUS TM11 and TE10 emulations (e.g. Emulex TC-11), see - <a class="Xr">vax/tm(4)</a></dd> - <dt><var class="Ar">ts#</var></dt> - <dd>UNIBUS TS11, see <a class="Xr">vax/ts(4)</a></dd> - <dt><var class="Ar">ut#</var></dt> - <dd>UNIBUS TU45 emulations (e.g. si 9700), see - <a class="Xr">vax/ut(4)</a></dd> - <dt><var class="Ar">uu#</var></dt> - <dd>TU58 cassettes on DL11 controller, see - <a class="Xr">vax/uu(4)</a></dd> - </dl> - </dd> - <dt>Disks:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">dk#</var></dt> - <dd>Wedge disk slices, see <a class="Xr">dk(4)</a></dd> - <dt><var class="Ar">ccd#</var></dt> - <dd>Concatenated disk devices, see <a class="Xr">ccd(4)</a></dd> - <dt><var class="Ar">cd#</var></dt> - <dd>SCSI or ATAPI CD-ROM, see <a class="Xr">cd(4)</a></dd> - <dt><var class="Ar">cgd#</var></dt> - <dd>Cryptographic disk devices, see <a class="Xr">cgd(4)</a></dd> - <dt><var class="Ar">raid#</var></dt> - <dd>RAIDframe disk devices, see <a class="Xr">raid(4)</a></dd> - <dt><var class="Ar">sd#</var></dt> - <dd>SCSI disks, see <a class="Xr">sd(4)</a></dd> - <dt><var class="Ar">wd#</var></dt> - <dd>``winchester'' disk drives (ST506,IDE,ESDI,RLL,...), see - <a class="Xr">wd(4)</a></dd> - <dt><var class="Ar">bmd#</var></dt> - <dd>Nereid bank memory disks, see <a class="Xr">x68k/bmd(4)</a></dd> - <dt><var class="Ar">ed#</var></dt> - <dd>IBM PS/2 ESDI disk devices, see <a class="Xr">edc(4)</a></dd> - <dt><var class="Ar">fd#</var></dt> - <dd>``floppy'' disk drives (3 1/2", 5 1/4"), see - <a class="Xr">amiga/fdc(4)</a>, <a class="Xr">sparc64/fdc(4)</a>, - <a class="Xr">x86/fdc(4)</a></dd> - <dt><var class="Ar">fss#</var></dt> - <dd>Files system snapshot devices, see <a class="Xr">fss(4)</a></dd> - <dt><var class="Ar">gdrom#</var></dt> - <dd>Dreamcast ``gigadisc'' CD-ROM drive, see - <a class="Xr">dreamcast/gdrom(4)</a></dd> - <dt><var class="Ar">hk#</var></dt> - <dd>UNIBUS RK06 and RK07, see <a class="Xr">vax/hk(4)</a></dd> - <dt><var class="Ar">hp#</var></dt> - <dd>MASSBUS RM??, see <a class="Xr">vax/hp(4)</a></dd> - <dt><var class="Ar">ld#</var></dt> - <dd>Logical disk devices (e.g., hardware RAID), see - <a class="Xr">ld(4)</a></dd> - <dt><var class="Ar">mcd#</var></dt> - <dd>Mitsumi CD-ROM, see <a class="Xr">mcd(4)</a></dd> - <dt><var class="Ar">md#</var></dt> - <dd>Memory pseudo-disk devices, see <a class="Xr">md(4)</a></dd> - <dt><var class="Ar">ofdisk#</var></dt> - <dd>OpenFirmware disk devices</dd> - <dt><var class="Ar">ra#</var></dt> - <dd>MSCP disks (RA??, RD??)</dd> - <dt><var class="Ar">rb#</var></dt> - <dd>730 IDC w/ RB80 and/or RB02</dd> - <dt><var class="Ar">rd#</var></dt> - <dd>HDC9224 RD disks on VS2000, see <a class="Xr">hp300/rd(4)</a></dd> - <dt><var class="Ar">rl#</var></dt> - <dd>UNIBUS RL02, see <a class="Xr">vax/rl(4)</a></dd> - <dt><var class="Ar">rx#</var></dt> - <dd>MSCP floppy disk (RX33/50/...)</dd> - <dt><var class="Ar">up#</var></dt> - <dd>Other UNIBUS devices (e.g. on Emulex SC-21V controller), see - <a class="Xr">vax/up(4)</a></dd> - <dt><var class="Ar">vnd#</var></dt> - <dd>``file'' pseudo-disks, see <a class="Xr">vnd(4)</a></dd> - <dt><var class="Ar">xbd#</var></dt> - <dd>Xen virtual disks, see <a class="Xr">xbd(4)</a></dd> - <dt><var class="Ar">xd#</var></dt> - <dd>Xylogic 753/7053 disks, see <a class="Xr">sparc/xd(4)</a></dd> - <dt><var class="Ar">xy#</var></dt> - <dd>Xylogic 450/451 disks, see <a class="Xr">sparc/xy(4)</a></dd> - </dl> - </dd> - <dt>Pointing devices:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">wsmouse#</var></dt> - <dd>wscons mouse events, see <a class="Xr">wsmouse(4)</a></dd> - <dt><var class="Ar">lms#</var></dt> - <dd>Logitech bus mouse, see <a class="Xr">i386/lms(4)</a></dd> - <dt><var class="Ar">mms#</var></dt> - <dd>Microsoft bus mouse, see <a class="Xr">dreamcast/mms(4)</a>, - <a class="Xr">i386/mms(4)</a></dd> - <dt><var class="Ar">qms#</var></dt> - <dd>``quadrature mouse'', see <a class="Xr">acorn32/qms(4)</a></dd> - <dt><var class="Ar">pms#</var></dt> - <dd>PS/2 mouse</dd> - <dt><var class="Ar">mouse</var></dt> - <dd>Mouse (provides events, for X11)</dd> - </dl> - </dd> - <dt>Keyboard devices:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">wskbd#</var></dt> - <dd>wscons keyboard events, see <a class="Xr">wskbd(4)</a></dd> - <dt><var class="Ar">kbd</var></dt> - <dd>Raw keyboard (provides events, for X11), see - <a class="Xr">sparc/kbd(4)</a>, <a class="Xr">sun2/kbd(4)</a>, - <a class="Xr">sun3/kbd(4)</a></dd> - <dt><var class="Ar">kbdctl</var></dt> - <dd>Keyboard control</dd> - </dl> - </dd> - <dt>Terminals/Console ports:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">tty[01]#</var></dt> - <dd>Standard serial ports, see <a class="Xr">tty(4)</a></dd> - <dt><var class="Ar">tty0#</var></dt> - <dd>SB1250 (``sbscn'') serial ports (sbmips), see - <a class="Xr">tty(4)</a></dd> - <dt><var class="Ar">ttyE#</var></dt> - <dd>wscons - Workstation console (``wscons'') glass-tty emulators</dd> - <dt><var class="Ar">ttyCZ?</var></dt> - <dd>Cyclades-Z multiport serial boards. Each ``unit'' makes 64 ports., see - <a class="Xr">cz(4)</a></dd> - <dt><var class="Ar">ttyCY?</var></dt> - <dd>Cyclom-Y multiport serial boards. Each ``unit'' makes 32 ports., see - <a class="Xr">cy(4)</a></dd> - <dt><var class="Ar">ttye#</var></dt> - <dd>ITE bitmapped consoles, see <a class="Xr">amiga/ite(4)</a></dd> - <dt><var class="Ar">ttyv0</var></dt> - <dd>pccons</dd> - <dt><var class="Ar">ttyC?</var></dt> - <dd>NS16550 (``com'') serial ports</dd> - <dt><var class="Ar">ttyS#</var></dt> - <dd>SA1110 serial port (hpcarm)</dd> - <dt><var class="Ar">ttyTX?</var></dt> - <dd>TX39 internal serial ports (hpcmips)</dd> - <dt><var class="Ar">ttyB?</var></dt> - <dd>DEC 3000 ZS8530 (``scc'') serial ports (alpha)</dd> - <dt><var class="Ar">ttyA#</var></dt> - <dd>Mfc serial ports (amiga)</dd> - <dt><var class="Ar">ttyB#</var></dt> - <dd>Msc serial ports (amiga)</dd> - <dt><var class="Ar">ttyC#</var></dt> - <dd>Com style serial ports (DraCo, HyperCom) (amiga) On the DraCo, units 0 - and 1 are the built-in ``modem'' and ``mouse'' ports, if - configured.</dd> - <dt><var class="Ar">ttyA0</var></dt> - <dd>8530 Channel A (formerly ser02) (atari)</dd> - <dt><var class="Ar">ttyA1</var></dt> - <dd>8530 Channel B (formerly mdm02) (atari)</dd> - <dt><var class="Ar">ttyB0</var></dt> - <dd>UART on first 68901 (formerly mdm01) (atari)</dd> - <dt><var class="Ar">ixpcom</var></dt> - <dd>IXP12x0 COM ports</dd> - <dt><var class="Ar">epcom</var></dt> - <dd>EP93xx COM ports</dd> - <dt><var class="Ar">plcom</var></dt> - <dd>ARM PL01[01] serial ports</dd> - <dt><var class="Ar">wmcom</var></dt> - <dd>EPOC Windermere COM ports</dd> - <dt><var class="Ar">ttyM?</var></dt> - <dd>HP200/300 4 port serial mux interface (hp300)</dd> - <dt><var class="Ar">ttya</var></dt> - <dd>``ttya'' system console (luna68k)</dd> - <dt><var class="Ar">ttyb</var></dt> - <dd>Second system serial port (luna68k)</dd> - <dt><var class="Ar">tty#</var></dt> - <dd>Onboard serial ports (mvme68k) On the mvme147 these are: ttyZ1, ttyZ2 - and ttyZ3. On the mvme167, and '177: ttyC1, ttyC2 and ttyC3. Note that - tty[CZ]0 is grabbed by the console device so is not created by - default, see <a class="Xr">tty(4)</a></dd> - <dt><var class="Ar">dc#</var></dt> - <dd>PMAX 4 channel serial interface (kbd, mouse, modem, printer)</dd> - <dt><var class="Ar">scc#</var></dt> - <dd>82530 serial interface (pmax)</dd> - <dt><var class="Ar">ttyZ#</var></dt> - <dd>Zilog 8530 (``zstty'') serial ports, see - <a class="Xr">zstty(4)</a></dd> - <dt><var class="Ar">tty[abcd]</var></dt> - <dd>Built-in serial ports (sparc)</dd> - <dt><var class="Ar">tty#</var></dt> - <dd>Z88530 serial controllers (sparc64), see <a class="Xr">tty(4)</a></dd> - <dt><var class="Ar">ttyh#</var></dt> - <dd>SAB82532 serial controllers (sparc64), see - <a class="Xr">sparc64/sab(4)</a></dd> - <dt><var class="Ar">tty[a-j]</var></dt> - <dd>Built-in serial ports (sun2, sun3)</dd> - <dt><var class="Ar">ttyC?</var></dt> - <dd>pccons (arc)</dd> - <dt><var class="Ar">dz#</var></dt> - <dd>UNIBUS DZ11 and DZ32 (vax), see <a class="Xr">emips/dz(4)</a>, - <a class="Xr">vax/dz(4)</a></dd> - <dt><var class="Ar">dh#</var></dt> - <dd>UNIBUS DH11 and emulations (e.g. Able DMAX, Emulex CS-11) (vax), see - <a class="Xr">vax/dh(4)</a></dd> - <dt><var class="Ar">dmf#</var></dt> - <dd>UNIBUS DMF32 (vax), see <a class="Xr">vax/dmf(4)</a></dd> - <dt><var class="Ar">dhu#</var></dt> - <dd>UNIBUS DHU11 (vax), see <a class="Xr">vax/dhu(4)</a></dd> - <dt><var class="Ar">dmz#</var></dt> - <dd>UNIBUS DMZ32 (vax), see <a class="Xr">vax/dmz(4)</a></dd> - <dt><var class="Ar">dl#</var></dt> - <dd>UNIBUS DL11 (vax), see <a class="Xr">vax/dl(4)</a></dd> - <dt><var class="Ar">xencons</var></dt> - <dd>Xen virtual console</dd> - </dl> - </dd> - <dt>Terminal multiplexors:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">dc#</var></dt> - <dd>4 channel serial interface (keyboard, mouse, modem, printer)</dd> - <dt><var class="Ar">dh#</var></dt> - <dd>UNIBUS DH11 and emulations (e.g. Able DMAX, Emulex CS-11), see - <a class="Xr">vax/dh(4)</a></dd> - <dt><var class="Ar">dhu#</var></dt> - <dd>UNIBUS DHU11, see <a class="Xr">vax/dhu(4)</a></dd> - <dt><var class="Ar">dl#</var></dt> - <dd>UNIBUS DL11, see <a class="Xr">vax/dl(4)</a></dd> - <dt><var class="Ar">dmf#</var></dt> - <dd>UNIBUS DMF32, see <a class="Xr">vax/dmf(4)</a></dd> - <dt><var class="Ar">dmz#</var></dt> - <dd>UNIBUS DMZ32, see <a class="Xr">vax/dmz(4)</a></dd> - <dt><var class="Ar">dz#</var></dt> - <dd>UNIBUS DZ11 and DZ32, see <a class="Xr">emips/dz(4)</a>, - <a class="Xr">vax/dz(4)</a></dd> - <dt><var class="Ar">scc#</var></dt> - <dd>82530 serial interface</dd> - </dl> - </dd> - <dt>Call units:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">dn#</var></dt> - <dd>UNIBUS DN11 and emulations (e.g. Able Quadracall), see - <a class="Xr">vax/dn(4)</a></dd> - </dl> - </dd> - <dt>Pseudo terminals:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">ptm</var></dt> - <dd>Pty multiplexor device, and pts directory, see - <a class="Xr">ptm(4)</a></dd> - <dt><var class="Ar">pty#</var></dt> - <dd>Set of 16 master and slave pseudo terminals, see - <a class="Xr">pty(4)</a></dd> - <dt><var class="Ar">opty</var></dt> - <dd>First 16 ptys, to save inodes on install media</dd> - <dt><var class="Ar">ipty</var></dt> - <dd>First 2 ptys, for install media use only</dd> - </dl> - </dd> - <dt>Printers:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">arcpp#</var></dt> - <dd>Archimedes parallel port</dd> - <dt><var class="Ar">lpt#</var></dt> - <dd>Stock lp, see <a class="Xr">lpt(4)</a>, - <a class="Xr">acorn32/lpt(4)</a>, <a class="Xr">mvme68k/lpt(4)</a>, - <a class="Xr">x86/lpt(4)</a></dd> - <dt><var class="Ar">lpa#</var></dt> - <dd>Interruptless lp</dd> - <dt><var class="Ar">par#</var></dt> - <dd>Amiga motherboard parallel port</dd> - <dt><var class="Ar">cpi#</var></dt> - <dd>Macintosh Nubus CSI parallel printer card, see - <a class="Xr">mac68k/cpi(4)</a></dd> - </dl> - </dd> - <dt>USB devices:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">usb#</var></dt> - <dd>USB control devices, see <a class="Xr">usb(4)</a></dd> - <dt><var class="Ar">uhid#</var></dt> - <dd>USB generic HID devices, see <a class="Xr">uhid(4)</a></dd> - <dt><var class="Ar">ulpt#</var></dt> - <dd>USB printer devices, see <a class="Xr">ulpt(4)</a></dd> - <dt><var class="Ar">ugen#</var></dt> - <dd>USB generic devices, see <a class="Xr">ugen(4)</a></dd> - <dt><var class="Ar">uscanner#</var></dt> - <dd>USB scanners, see <a class="Xr">uscanner(4)</a></dd> - <dt><var class="Ar">ttyHS#</var></dt> - <dd>USB Option N.V. modems</dd> - <dt><var class="Ar">ttyU#</var></dt> - <dd>USB modems, see <a class="Xr">ucom(4)</a></dd> - <dt><var class="Ar">ttyY#</var></dt> - <dd>USB serial adapters</dd> - </dl> - </dd> - <dt>Video devices:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">bwtwo#</var></dt> - <dd>Monochromatic frame buffer, see <a class="Xr">sparc/bwtwo(4)</a>, - <a class="Xr">sun2/bwtwo(4)</a>, <a class="Xr">sun3/bwtwo(4)</a></dd> - <dt><var class="Ar">cgtwo#</var></dt> - <dd>8-bit color frame buffer, see <a class="Xr">sparc/cgtwo(4)</a>, - <a class="Xr">sun3/cgtwo(4)</a></dd> - <dt><var class="Ar">cgthree#</var></dt> - <dd>8-bit color frame buffer, see <a class="Xr">sparc/cgthree(4)</a></dd> - <dt><var class="Ar">cgfour#</var></dt> - <dd>8-bit color frame buffer, see <a class="Xr">sparc/cgfour(4)</a>, - <a class="Xr">sun3/cgfour(4)</a></dd> - <dt><var class="Ar">cgsix#</var></dt> - <dd>Accelerated 8-bit color frame buffer, see - <a class="Xr">sparc/cgsix(4)</a></dd> - <dt><var class="Ar">cgeight#</var></dt> - <dd>24-bit color frame buffer, see <a class="Xr">sparc/cgeight(4)</a></dd> - <dt><var class="Ar">etvme</var></dt> - <dd>Tseng et-compatible cards on VME (atari)</dd> - <dt><var class="Ar">ik#</var></dt> - <dd>UNIBUS interface to Ikonas frame buffer, see - <a class="Xr">vax/ik(4)</a></dd> - <dt><var class="Ar">leo</var></dt> - <dd>Circad Leonardo VME-bus true color (atari)</dd> - <dt><var class="Ar">ps#</var></dt> - <dd>UNIBUS interface to Picture System 2, see - <a class="Xr">vax/ps(4)</a></dd> - <dt><var class="Ar">qv#</var></dt> - <dd>QVSS (MicroVAX) display</dd> - <dt><var class="Ar">tcx#</var></dt> - <dd>Accelerated 8/24-bit color frame buffer, see - <a class="Xr">sparc/tcx(4)</a></dd> - </dl> - </dd> - <dt>Maple bus devices:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">maple</var></dt> - <dd>Maple bus control devices, see - <a class="Xr">dreamcast/maple(4)</a></dd> - <dt><var class="Ar">mlcd#</var></dt> - <dd>Maple bus LCD devices, see <a class="Xr">dreamcast/mlcd(4)</a></dd> - <dt><var class="Ar">mmem#</var></dt> - <dd>Maple bus storage devices, see - <a class="Xr">dreamcast/mmem(4)</a></dd> - </dl> - </dd> - <dt>IEEE1394 bus devices:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">fw#</var></dt> - <dd>IEEE1394 bus generic node access devices</dd> - <dt><var class="Ar">fwmem#</var></dt> - <dd>IEEE1394 bus physical memory of the remote node access devices</dd> - </dl> - </dd> - <dt>Special purpose devices:</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">ad#</var></dt> - <dd>UNIBUS interface to Data Translation A/D converter, see - <a class="Xr">vax/ad(4)</a></dd> - <dt><var class="Ar">agp#</var></dt> - <dd>AGP GART devices, see <a class="Xr">agp(4)</a></dd> - <dt><var class="Ar">altq</var></dt> - <dd>ALTQ control interface, see <a class="Xr">altq(4)</a></dd> - <dt><var class="Ar">amr#</var></dt> - <dd>AMI MegaRaid control device, see <a class="Xr">amr(4)</a></dd> - <dt><var class="Ar">apm</var></dt> - <dd>Power management device, see <a class="Xr">i386/apm(4)</a></dd> - <dt><var class="Ar">audio#</var></dt> - <dd>Audio devices, see <a class="Xr">audio(4)</a></dd> - <dt><var class="Ar">bell#</var></dt> - <dd>OPM bell device (x68k)</dd> - <dt><var class="Ar">bktr</var></dt> - <dd>Brooktree 848/849/878/879 based TV cards, see - <a class="Xr">bktr(4)</a></dd> - <dt><var class="Ar">bpf</var></dt> - <dd>Packet filter, see <a class="Xr">bpf(4)</a></dd> - <dt><var class="Ar">bthub</var></dt> - <dd>Bluetooth Device Hub control interface, see - <a class="Xr">bthub(4)</a></dd> - <dt><var class="Ar">cfs#</var></dt> - <dd>Coda file system device</dd> - <dt><var class="Ar">ch#</var></dt> - <dd>SCSI media changer, see <a class="Xr">ch(4)</a></dd> - <dt><var class="Ar">cir#</var></dt> - <dd>Consumer IR, see <a class="Xr">cir(4)</a></dd> - <dt><var class="Ar">clockctl</var></dt> - <dd>Clock control for non root users, see - <a class="Xr">clockctl(4)</a></dd> - <dt><var class="Ar">cpuctl</var></dt> - <dd>CPU control</dd> - <dt><var class="Ar">crypto</var></dt> - <dd>Hardware crypto access driver, see <a class="Xr">crypto(4)</a></dd> - <dt><var class="Ar">dmoverio</var></dt> - <dd>Hardware-assisted data movers, see <a class="Xr">dmoverio(4)</a></dd> - <dt><var class="Ar">dpt#</var></dt> - <dd>DPT/Adaptec EATA RAID management interface, see - <a class="Xr">dpt(4)</a></dd> - <dt><var class="Ar">dpti#</var></dt> - <dd>DPT/Adaptec I2O RAID management interface, see - <a class="Xr">dpti(4)</a></dd> - <dt><var class="Ar">drm#</var></dt> - <dd>Direct Rendering Manager interface, see <a class="Xr">drm(4)</a></dd> - <dt><var class="Ar">dtv#</var></dt> - <dd>Digital TV interface, see <a class="Xr">dtv(4)</a></dd> - <dt><var class="Ar">fb#</var></dt> - <dd>PMAX generic framebuffer pseudo-device</dd> - <dt><var class="Ar">fd</var></dt> - <dd>File descriptors</dd> - <dt><var class="Ar">gpiopps#</var></dt> - <dd>1PPS signals on GPIO pins, see <a class="Xr">gpiopps(4)</a></dd> - <dt><var class="Ar">grf#</var></dt> - <dd>Graphics frame buffer device, see <a class="Xr">amiga/grf(4)</a></dd> - <dt><var class="Ar">hdaudio#</var></dt> - <dd>High Definition audio control device, see - <a class="Xr">hdaudio(4)</a></dd> - <dt><var class="Ar">hdmicec#</var></dt> - <dd>HDMI CEC devices</dd> - <dt><var class="Ar">hil</var></dt> - <dd>HP300 HIL input devices, see <a class="Xr">hil(4)</a></dd> - <dt><var class="Ar">icp</var></dt> - <dd>ICP-Vortex/Intel RAID control interface, see - <a class="Xr">icp(4)</a></dd> - <dt><var class="Ar">iic#</var></dt> - <dd>IIC bus device, see <a class="Xr">iic(4)</a></dd> - <dt><var class="Ar">io</var></dt> - <dd>X86 IOPL access for COMPAT_10, COMPAT_FREEBSD, see - <a class="Xr">hppa/io(4)</a>, <a class="Xr">i386/io(4)</a></dd> - <dt><var class="Ar">iop#</var></dt> - <dd>I2O IOP control interface, see <a class="Xr">iop(4)</a></dd> - <dt><var class="Ar">ipmi#</var></dt> - <dd>OpenIPMI compatible interface, see <a class="Xr">ipmi(4)</a></dd> - <dt><var class="Ar">ipl</var></dt> - <dd>IP Filter</dd> - <dt><var class="Ar">irframe#</var></dt> - <dd>IrDA physical frame, see <a class="Xr">irframe(4)</a></dd> - <dt><var class="Ar">ite#</var></dt> - <dd>Terminal emulator interface to HP300 graphics devices, see - <a class="Xr">amiga/ite(4)</a></dd> - <dt><var class="Ar">joy#</var></dt> - <dd>Joystick device, see <a class="Xr">joy(4)</a></dd> - <dt><var class="Ar">kttcp</var></dt> - <dd>Kernel ttcp helper device, see <a class="Xr">kttcp(4)</a></dd> - <dt><var class="Ar">lockstat</var></dt> - <dd>Kernel locking statistics</dd> - <dt><var class="Ar">magma#</var></dt> - <dd>Magma multiport serial/parallel cards, see - <a class="Xr">sparc/magma(4)</a></dd> - <dt><var class="Ar">midi#</var></dt> - <dd>MIDI, see <a class="Xr">midi(4)</a></dd> - <dt><var class="Ar">mfi#</var></dt> - <dd>LSI MegaRAID/MegaSAS control interface, see - <a class="Xr">mfi(4)</a></dd> - <dt><var class="Ar">mlx#</var></dt> - <dd>Mylex DAC960 control interface, see <a class="Xr">mlx(4)</a></dd> - <dt><var class="Ar">mly#</var></dt> - <dd>Mylex AcceleRAID/eXtremeRAID control interface, see - <a class="Xr">mly(4)</a></dd> - <dt><var class="Ar">np#</var></dt> - <dd>UNIBUS Ethernet co-processor interface, for downloading., see - <a class="Xr">vax/np(4)</a></dd> - <dt><var class="Ar">npf</var></dt> - <dd>NPF packet filter</dd> - <dt><var class="Ar">nsmb#</var></dt> - <dd>SMB requester, see <a class="Xr">nsmb(4)</a></dd> - <dt><var class="Ar">nvme#</var></dt> - <dd>Non-Volatile Memory Host Controller Interface device driver, see - <a class="Xr">nvme(4)</a></dd> - <dt><var class="Ar">nvme#ns*</var></dt> - <dd>Non-Volatile Memory namespace</dd> - <dt><var class="Ar">nvmm</var></dt> - <dd>NetBSD Virtual Machine Monitor, see <a class="Xr">nvmm(4)</a></dd> - <dt><var class="Ar">openfirm</var></dt> - <dd>OpenFirmware accessor</dd> - <dt><var class="Ar">pad#</var></dt> - <dd>Pseudo-audio device driver, see <a class="Xr">pad(4)</a></dd> - <dt><var class="Ar">pci#</var></dt> - <dd>PCI bus access devices, see <a class="Xr">pci(4)</a></dd> - <dt><var class="Ar">pf</var></dt> - <dd>PF packet filter</dd> - <dt><var class="Ar">putter</var></dt> - <dd>Pass-to-Userspace Transporter</dd> - <dt><var class="Ar">px#</var></dt> - <dd>PixelStamp Xserver access, see <a class="Xr">px(4)</a></dd> - <dt><var class="Ar">qemufwcfg#</var></dt> - <dd>QEMU Firmware Configuration, see <a class="Xr">qemufwcfg(4)</a></dd> - <dt><var class="Ar">radio#</var></dt> - <dd>Radio devices, see <a class="Xr">radio(4)</a></dd> - <dt><var class="Ar">random</var></dt> - <dd>Random number generator, see <a class="Xr">rnd(4)</a></dd> - <dt><var class="Ar">rtc#</var></dt> - <dd>RealTimeClock, see <a class="Xr">atari/rtc(4)</a>, - <a class="Xr">evbppc/rtc(4)</a>, <a class="Xr">hp300/rtc(4)</a></dd> - <dt><var class="Ar">scsibus#</var></dt> - <dd>SCSI busses, see <a class="Xr">scsi(4)</a></dd> - <dt><var class="Ar">se#</var></dt> - <dd>SCSI Ethernet, see <a class="Xr">se(4)</a></dd> - <dt><var class="Ar">ses#</var></dt> - <dd>SES/SAF-TE SCSI Devices, see <a class="Xr">ses(4)</a></dd> - <dt><var class="Ar">speaker</var></dt> - <dd>PC speaker, see <a class="Xr">speaker(4)</a></dd> - <dt><var class="Ar">spi#</var></dt> - <dd>SPI bus device, see <a class="Xr">spi(4)</a></dd> - <dt><var class="Ar">sram</var></dt> - <dd>Battery backuped memory (x68k)</dd> - <dt><var class="Ar">srt#</var></dt> - <dd>Source-address based routing, see <a class="Xr">srt(4)</a></dd> - <dt><var class="Ar">ss#</var></dt> - <dd>SCSI scanner, see <a class="Xr">ss(4)</a></dd> - <dt><var class="Ar">stic#</var></dt> - <dd>PixelStamp interface chip</dd> - <dt><var class="Ar">sysmon</var></dt> - <dd>System Monitoring hardware, see <a class="Xr">envsys(4)</a></dd> - <dt><var class="Ar">tap#</var></dt> - <dd>Virtual Ethernet device, see <a class="Xr">tap(4)</a></dd> - <dt><var class="Ar">tprof</var></dt> - <dd>Task profiler, see <a class="Xr">tprof(4)</a></dd> - <dt><var class="Ar">tun#</var></dt> - <dd>Network tunnel driver, see <a class="Xr">tun(4)</a></dd> - <dt><var class="Ar">twa</var></dt> - <dd>3ware Apache control interface, see <a class="Xr">twa(4)</a></dd> - <dt><var class="Ar">twe</var></dt> - <dd>3ware Escalade control interface, see <a class="Xr">twe(4)</a></dd> - <dt><var class="Ar">uk#</var></dt> - <dd>Unknown SCSI device, see <a class="Xr">uk(4)</a></dd> - <dt><var class="Ar">veriexec</var></dt> - <dd>Veriexec fingerprint loader, see <a class="Xr">veriexec(4)</a></dd> - <dt><var class="Ar">vhci</var></dt> - <dd>Virtual host controller interface</dd> - <dt><var class="Ar">video#</var></dt> - <dd>Video capture devices, see <a class="Xr">video(4)</a></dd> - <dt><var class="Ar">view#</var></dt> - <dd>Generic interface to graphic displays (Amiga)</dd> - <dt><var class="Ar">wsfont#</var></dt> - <dd>Console font control, see <a class="Xr">wsfont(4)</a></dd> - <dt><var class="Ar">wsmux#</var></dt> - <dd>wscons event multiplexor, see <a class="Xr">wsmux(4)</a></dd> - <dt><var class="Ar">xenevt</var></dt> - <dd>Xen event interface</dd> - </dl> - </dd> - <dt>iSCSI communication devices</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">iscsi#</var></dt> - <dd>ISCSI driver and /sbin/iscsid communication</dd> - </dl> - </dd> - <dt>Trusted Computing devices</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">tpm</var></dt> - <dd>Trusted Platform Module, see <a class="Xr">tpm(4)</a></dd> - </dl> - </dd> - <dt>Debugging and tracing</dt> - <dd> - <dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">dtrace</var></dt> - <dd>Dynamic tracing framework</dd> - </dl> - </dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="ENVIRONMENT"><a class="permalink" href="#ENVIRONMENT">ENVIRONMENT</a></h1> -<p class="Pp">The following environment variables affect the execution of - <code class="Nm">MAKEDEV</code>:</p> -<dl class="Bl-tag"> - <dt id="MAKEDEV_AS_LIBRARY"><a class="permalink" href="#MAKEDEV_AS_LIBRARY"><code class="Ev">MAKEDEV_AS_LIBRARY</code></a></dt> - <dd>If this is set, then <code class="Nm">MAKEDEV</code> will define several - shell functions and then return, ignoring all its command line options and - arguments. This is used to enable <a class="Xr">MAKEDEV.local(8)</a> to - use the shell functions defined in <code class="Nm">MAKEDEV</code>.</dd> -</dl> -</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">/dev</span></dt> - <dd>special device files directory</dd> - <dt><span class="Pa">/dev/MAKEDEV</span></dt> - <dd>script described in this man page</dd> - <dt><span class="Pa">/dev/MAKEDEV.local</span></dt> - <dd>script for site-specific devices</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<p class="Pp">If the script reports an error that is difficult to understand, - you can get more debugging output by using</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">sh</code> - <code class="Fl">-x</code> <var class="Ar">MAKEDEV</var> - <var class="Ar">argument</var></code></div> -. -</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">config(1)</a>, <a class="Xr">pax(1)</a>, - <a class="Xr">intro(4)</a>, <a class="Xr">diskless(8)</a>, - <a class="Xr">init(8)</a>, <a class="Xr">MAKEDEV.local(8)</a>, - <a class="Xr">mknod(8)</a>, <a class="Xr">mount_mfs(8)</a>, - <a class="Xr">mount_tmpfs(8)</a>, <a class="Xr">mtree(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">MAKEDEV</code> command appeared in - <span class="Ux">4.2BSD</span>. The <code class="Fl">-f</code>, - <code class="Fl">-m</code>, and <code class="Fl">-s</code> options were - added in <span class="Ux">NetBSD 2.0</span>. The <code class="Fl">-p</code>, - <code class="Fl">-t</code>, and <code class="Fl">-M</code> options were - added in <span class="Ux">NetBSD 5.0</span>. The ability to be used as a - function library was added in <span class="Ux">NetBSD 5.0</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The <code class="Fl">-f</code> option is not compatible with the - use of <a class="Xr">mtree(8)</a> or <a class="Xr">pax(1)</a>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="NOTES"><a class="permalink" href="#NOTES">NOTES</a></h1> -<p class="Pp">Not all devices listed in this manpage are supported on all - platforms.</p> -<p class="Pp">This man page is generated automatically from the same sources as - <span class="Pa">/dev/MAKEDEV</span>, in which the device files are not - always sorted, which may result in an unusual (non-alphabetical) order.</p> -<p class="Pp">In order to allow a diskless <span class="Ux">NetBSD</span> client - to obtain its <span class="Pa">/dev</span> directory from a file server - running a foreign operating system, one of the following techniques may be - useful to populate a directory of device nodes on the foreign server:</p> -<ul class="Bl-bullet"> - <li>If the foreign server is sufficiently similar to - <span class="Ux">NetBSD</span>, run <code class="Nm">MAKEDEV</code> in an - appropriate directory of the foreign server, using the - <code class="Fl">-m</code> flag to refer to a script that converts from - command line arguments that would be usable with the - <span class="Ux">NetBSD</span> <a class="Xr">mknod(8)</a> command to the - equivalent commands for the foreign server.</li> - <li id="TOOLDIR">Run <code class="Nm">MAKEDEV</code> with the - <code class="Fl">-s</code> flag to generate an <a class="Xr">mtree(8)</a> - specification file; this can be done on any host with a POSIX-compliant - shell and a few widely-available utilities. Use the - <a class="Xr">pax(1)</a> command with the <code class="Fl">-w</code> - <code class="Fl">-M</code> flags to convert the <a class="Xr">mtree(8)</a> - specification file into an archive in a format that supports device nodes - (such as <var class="Ar">ustar</var> format); this can be done on a - <span class="Ux">NetBSD</span> host, or can be done in a cross-build - environment using - <a class="permalink" href="#TOOLDIR"><b class="Sy">TOOLDIR</b></a><span class="Pa">/bin/nbpax</span>. - Finally, use appropriate tools on the foreign server to unpack the archive - and create the device nodes.</li> -</ul> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">April 1, 2020</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/MAKEDEV.local.8 4.html b/static/netbsd/man8/MAKEDEV.local.8 4.html deleted file mode 100644 index d5bd6117..00000000 --- a/static/netbsd/man8/MAKEDEV.local.8 4.html +++ /dev/null @@ -1,92 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">MAKEDEV.LOCAL(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">MAKEDEV.LOCAL(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">MAKEDEV.local</code> — - <span class="Nd">create site-specific device special files</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">MAKEDEV.local</code></td> - <td>[<code class="Fl">-fMsu</code>] [<code class="Fl">-m</code> - <var class="Ar">mknod</var>] [<code class="Fl">-p</code> - <var class="Ar">pax</var>] [<code class="Fl">-t</code> - <var class="Ar">mtree</var>] {<span class="Pa">all</span> | - <span class="Pa">site-specific-argument</span>} - [<var class="Ar">...</var>]</td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">MAKEDEV.local</code> is used to create - site-specific device special files. Each argument may be the word - <span class="Pa">all</span> or a site-specific argument. By default, there - are no valid site-specific arguments, and the <span class="Pa">all</span> - argument has no effect; This may be changed by editing the script.</p> -<p class="Pp">The script is in <span class="Pa">/dev/MAKEDEV.local</span>. - Devices are created in the current working directory; in normal use, - <code class="Nm">MAKEDEV.local</code> should be invoked with - <span class="Pa">/dev</span> as the current working directory.</p> -<p class="Pp">Supported options for <code class="Nm">MAKEDEV.local</code> are - the same as for <a class="Xr">MAKEDEV(8)</a>.</p> -</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">/dev</span></dt> - <dd>special device files directory</dd> - <dt><span class="Pa">/dev/MAKEDEV</span></dt> - <dd>script that invokes <code class="Nm">MAKEDEV.local</code> with the - <span class="Pa">all</span> argument.</dd> - <dt><span class="Pa">/dev/MAKEDEV.local</span></dt> - <dd>script described in this man page</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">config(1)</a>, <a class="Xr">intro(4)</a>, - <a class="Xr">MAKEDEV(8)</a>, <a class="Xr">mknod(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">MAKEDEV.local</code> command appeared in - <span class="Ux">4.2BSD</span>. Handling of the same command line options as - <a class="Xr">MAKEDEV(8)</a>, and the use of <a class="Xr">MAKEDEV(8)</a> as - a function library, was added in <span class="Ux">NetBSD 5.0</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="NOTES"><a class="permalink" href="#NOTES">NOTES</a></h1> -<p class="Pp">The relationship between <code class="Nm">MAKEDEV.local</code> and - <a class="Xr">MAKEDEV(8)</a> is complex:</p> -<ul class="Bl-bullet"> - <li>If <a class="Xr">MAKEDEV(8)</a> is invoked with the - <span class="Pa">all</span> or <span class="Pa">local</span> argument, - then it will invoke <code class="Nm">MAKEDEV.local</code> as a child - process, with options similar to those that were originally passed to - <a class="Xr">MAKEDEV(8)</a>, and with the <span class="Pa">all</span> - argument.</li> - <li><code class="Nm">MAKEDEV.local</code> uses shell functions defined in - <a class="Xr">MAKEDEV(8)</a>. This is done by loading - <a class="Xr">MAKEDEV(8)</a> using the shell “.” command, - with the <code class="Ev">MAKEDEV_AS_LIBRARY</code> variable set (to - inform <a class="Xr">MAKEDEV(8)</a> that it should behave as a function - library, not as an independent program).</li> -</ul> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">August 6, 2011</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/afterboot.8 4.html b/static/netbsd/man8/afterboot.8 4.html deleted file mode 100644 index 870e185b..00000000 --- a/static/netbsd/man8/afterboot.8 4.html +++ /dev/null @@ -1,795 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">AFTERBOOT(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">AFTERBOOT(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">afterboot</code> — <span class="Nd">things - to check after the first complete boot</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<section class="Ss"> -<h2 class="Ss" id="Starting_Out"><a class="permalink" href="#Starting_Out">Starting - Out</a></h2> -<p class="Pp">This document attempts to list items for the system administrator - to check and set up after the installation and first complete boot of the - system. The idea is to create a list of items that can be checked off so - that you have a warm fuzzy feeling that something obvious has not been - missed. A basic knowledge of <span class="Ux">UNIX</span> is assumed.</p> -<p class="Pp">Complete instructions for correcting and fixing items is not - provided. There are manual pages and other methodologies available for doing - that. For example, to view the man page for the <a class="Xr">ls(1)</a> - command, type:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">man 1 ls</code></pre> -</div> -<p class="Pp">Administrators will rapidly become more familiar with - <span class="Ux">NetBSD</span> if they get used to using the manual - pages.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Login"><a class="permalink" href="#Login">Login</a></h2> -<p class="Pp">On a fresh install with no other user accounts, login as - “<code class="Ic">root</code>”. You can do so on the console, - or over the network using <a class="Xr">ssh(1)</a>. If you have enabled the - SSH daemon (see <a class="Xr">sshd(8)</a>) and wish to allow root logins - over the network, edit the <span class="Pa">/etc/ssh/sshd_config</span> file - and set “PermitRootLogin” to “yes” (see - <a class="Xr">sshd_config(5)</a>). The default is to not permit root logins - over the network after fresh install in <span class="Ux">NetBSD</span>.</p> -<p class="Pp">Upon successful login on the console, you may see the message - “We recommend creating a non-root account...”. For security - reasons, it is bad practice to login as root during regular use and - maintenance of the system. In fact, the system will only let you login as - root on a secure terminal. By default, only the console is considered to be - a secure terminal. Instead, administrators are encouraged to add a - “regular” user, add said user to the “wheel” - group, then use the <a class="Xr">su(1)</a> command when root privileges are - required:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">useradd -G wheel -m myuser</code> -<code class="Ic">passwd myuser</code></pre> -</div> -</section> -<section class="Ss"> -<h2 class="Ss" id="Root_password"><a class="permalink" href="#Root_password">Root - password</a></h2> -<p class="Pp">Change the password for the root user. (Note that throughout the - documentation, the term “superuser” is a synonym for the root - user.) Choose a password that has numbers, digits, and special characters - (not space) as well as from the upper and lower case alphabet. Do not choose - any word in any language. It is common for an intruder to use dictionary - attacks. Type the command <code class="Ic">/usr/bin/passwd</code> to change - it.</p> -<p class="Pp">It is a good idea to always specify the full path name for both - the <a class="Xr">passwd(1)</a> and <a class="Xr">su(1)</a> commands as this - inhibits the possibility of files placed in your execution - <code class="Ev">PATH</code> for most shells. Furthermore, the superuser's - <code class="Ev">PATH</code> should never contain the current directory - (“.”).</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="System_date"><a class="permalink" href="#System_date">System - date</a></h2> -<p class="Pp">Check the system date with the <a class="Xr">date(1)</a> command. - If needed, change the date, and/or change the symbolic link of - <span class="Pa">/etc/localtime</span> to the correct time zone in the - <span class="Pa">/usr/share/zoneinfo</span> directory.</p> -<p class="Pp">Examples:</p> -<dl class="Bl-tag"> - <dt id="date"><a class="permalink" href="#date"><code class="Cm">date - 202010051820</code></a></dt> - <dd>Set the current date to October 5th, 2020 6:20pm.</dd> - <dt id="ln"><a class="permalink" href="#ln"><code class="Cm">ln -fs - /usr/share/zoneinfo/Europe/Helsinki /etc/localtime</code></a></dt> - <dd>Set the time zone to Eastern Europe Summer Time.</dd> -</dl> -</section> -<section class="Ss"> -<h2 class="Ss" id="Console_settings"><a class="permalink" href="#Console_settings">Console - settings</a></h2> -<p class="Pp">One of the first things you will likely need to do is to set up - your keyboard map (and maybe some other aspects about the system console). - To change your keyboard layout, edit the - “<var class="Va">encoding</var>” variable found in - <span class="Pa">/etc/wscons.conf</span>.</p> -<p class="Pp"><a class="Xr">wscons.conf(5)</a> contains more information about - this file.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Security_alerts"><a class="permalink" href="#Security_alerts">Security - alerts</a></h2> -<p class="Pp">All significant and easily fixed problems will be reported at - <a class="Lk" href="https://www.NetBSD.org/support/security/">the security - advisories web page</a>. It is recommended that you check this page - regularly.</p> -<p class="Pp">Additionally, you should set - “fetch_pkg_vulnerabilities=YES” in - <span class="Pa">/etc/daily.conf</span> to allow your system to - automatically update the local database of known vulnerable packages to the - latest version available on-line. The system will later check, on a daily - basis, if any of your installed packages are vulnerable based on the - contents of this database. See <a class="Xr">daily.conf(5)</a> and - <a class="Xr">security.conf(5)</a> for more details.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Entropy"><a class="permalink" href="#Entropy">Entropy</a></h2> -<p class="Pp">If your machine does not have a hardware random number generator, - it may not be safe to use on the internet until it has enough entropy to - generate unpredictable secrets for programs like web browsers and - <a class="Xr">ssh(1)</a>. You can use <a class="Xr">rndctl(8)</a> to list - the entropy sources with <code class="Ic">rndctl -l</code>, or save entropy - from another machine running <span class="Ux">NetBSD</span> with - <code class="Ic">rndctl -S</code> and load it on this one with - <code class="Ic">rndctl -L</code> (as long as there are no eavesdroppers on - the medium between the two machines). See <a class="Xr">entropy(7)</a> for - more details.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Check_hostname"><a class="permalink" href="#Check_hostname">Check - hostname</a></h2> -<p class="Pp">Use the <code class="Ic">hostname</code> command to verify that - the name of your machine is correct. See the man page for - <a class="Xr">hostname(1)</a> if it needs to be changed. You will also need - to change the contents of the “<var class="Va">hostname</var>” - variable in <span class="Pa">/etc/rc.conf</span> or edit the - <span class="Pa">/etc/myname</span> file to have it stick around for the - next reboot. Note that “<var class="Va">hostname</var>” is - supposed include a domainname, and that this should not be confused with YP - (NIS) <a class="Xr">domainname(1)</a>. If you are using - <a class="Xr">dhcpcd(8)</a> to configure network interfaces, it might - override these local hostname settings if your DHCP server specifies - client's hostname with other network configurations.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Verify_network_interface_configuration"><a class="permalink" href="#Verify_network_interface_configuration">Verify - network interface configuration</a></h2> -<p class="Pp">The first thing to do is an <code class="Ic">ifconfig -a</code> to - see if the network interfaces are properly configured. Correct by editing - <span class="Pa">/etc/ifconfig.</span><var class="Ar">interface</var> or the - corresponding - “<var class="Va">ifconfig_</var><var class="Ar">interface</var>” - variable in <a class="Xr">rc.conf(5)</a> (where - <var class="Ar">interface</var> is the interface name, e.g., - “le0”) and then using <a class="Xr">ifconfig(8)</a> to - manually configure it if you do not wish to reboot.</p> -<p class="Pp">Alternatively, many networks allow interfaces to be configured - automatically via DHCP. To get <a class="Xr">dhcpcd(8)</a> to start - automatically on boot, you will need to have this line in - <span class="Pa">/etc/rc.conf</span>:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">dhcpcd=YES</code></div> -<p class="Pp">See <a class="Xr">dhcpcd(8)</a> and - <a class="Xr">dhcpcd.conf(5)</a> for more information on setting up a DHCP - client. For information on setting up Wi-Fi, see - <a class="Sx" href="#Wireless_networking">Wireless networking</a>.</p> -<p class="Pp">You can add new “virtual interfaces” by adding the - required entries to - <span class="Pa">/etc/ifconfig.</span><var class="Ar">interface</var>. Read - the <a class="Xr">ifconfig.if(5)</a> man page for more information on the - format of - <span class="Pa">/etc/ifconfig.</span><var class="Ar">interface</var> files. - The loopback interface will look something like:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 32972 - inet 127.0.0.1 netmask 0xff000000 - inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 - inet6 ::1 prefixlen 128</pre> -</div> -<p class="Pp">an Ethernet interface something like:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>le0: flags=9863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> - inet 192.168.4.52 netmask 0xffffff00 broadcast 192.168.4.255 - inet6 fe80::5ef0:f0f0%le0 prefixlen 64 scopeid 0x1</pre> -</div> -<p class="Pp">and a PPP interface something like:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> - inet 203.3.131.108 --> 198.181.0.253 netmask 0xffff0000</pre> -</div> -<p class="Pp">See <a class="Xr">mrouted(8)</a> for instructions on configuring - multicast routing.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Check_routing_tables"><a class="permalink" href="#Check_routing_tables">Check - routing tables</a></h2> -<p class="Pp">Issue a <code class="Ic">netstat -rn</code> command. The output - will look something like:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>Routing tables - -Internet: -Destination Gateway Flags Refs Use Mtu Interface -default 192.168.4.254 UGS 0 11098028 - le0 -127 127.0.0.1 UGRS 0 0 - lo0 -127.0.0.1 127.0.0.1 UH 3 24 - lo0 -192.168.4 link#1 UC 0 0 - le0 -192.168.4.52 8:0:20:73:b8:4a UHL 1 6707 - le0 -192.168.4.254 0:60:3e:99:67:ea UHL 1 0 - le0 - -Internet6: -Destination Gateway Flags Refs Use Mtu Interface -::/96 ::1 UGRS 0 0 32972 lo0 => -::1 ::1 UH 4 0 32972 lo0 -::ffff:0.0.0.0/96 ::1 UGRS 0 0 32972 lo0 -fc80::/10 ::1 UGRS 0 0 32972 lo0 -fe80::/10 ::1 UGRS 0 0 32972 lo0 -fe80::%le0/64 link#1 UC 0 0 1500 le0 -fe80::%lo0/64 fe80::1%lo0 U 0 0 32972 lo0 -ff01::/32 ::1 U 0 0 32972 lo0 -ff02::%le0/32 link#1 UC 0 0 1500 le0 -ff02::%lo0/32 fe80::1%lo0 UC 0 0 32972 lo0</pre> -</div> -<p class="Pp">The default gateway address is stored in the - “<var class="Va">defaultroute</var>” variable in - <span class="Pa">/etc/rc.conf</span>, or in the file - <span class="Pa">/etc/mygate</span>. If you need to edit this file, a - painless way to reconfigure the network afterwards is to issue</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">service network restart</code></pre> -</div> -<p class="Pp">Or, you may prefer to manually configure using a series of - <code class="Ic">route add</code> and <code class="Ic">route delete</code> - commands (see <a class="Xr">route(8)</a>). If you run - <a class="Xr">dhcpcd(8)</a> you will have to kill it by running</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">service dhcpcd stop</code></pre> -</div> -<p class="Pp">before you flush the routes.</p> -<p class="Pp">If you wish to route packets between interfaces, add one or both - of the following directives (depending on whether IPv4 or IPv6 routing is - required) to <span class="Pa">/etc/sysctl.conf</span>:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">net.inet.ip.forwarding=1</code></div> -<div class="Bd - Bd-indent"><code class="Li">net.inet6.ip6.forwarding=1</code></div> -<p class="Pp">As an alternative, compile a new kernel with the - “GATEWAY” option. Packets are not forwarded by default, due to - RFC requirements.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Device_nodes"><a class="permalink" href="#Device_nodes">Device - nodes</a></h2> -<p class="Pp">By default, nodes are created in <span class="Pa">/dev</span> for - a fairly typical number of devices.</p> -<p class="Pp">However, if this system has a large number of devices connected - (e.g. for large scale storage), you may want to enable - <a class="Xr">devpubd(8)</a> to ensure a sufficient number of nodes are - available. Set “<var class="Va">devpubd=YES</var>” in - <span class="Pa">/etc/rc.conf</span> to create nodes automatically during - system runtime. You can also run the node creation script by hand:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">cd /dev && sh MAKEDEV</code></pre> -</div> -</section> -<section class="Ss"> -<h2 class="Ss" id="Secure_Shell_(SSH)"><a class="permalink" href="#Secure_Shell_(SSH)">Secure - Shell (SSH)</a></h2> -<p class="Pp">By default, all services are disabled in a fresh - <span class="Ux">NetBSD</span> installation, and SSH is no exception. You - may wish to enable it so you can remotely control your system. Set - “<var class="Va">sshd=YES</var>” in - <span class="Pa">/etc/rc.conf</span> and then starting the server with the - command</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">service sshd start</code></pre> -</div> -<p class="Pp">The first time the server is started, it will generate a new - keypair, which will be stored inside the directory - <span class="Pa">/etc/ssh</span>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Host_names_and_DNS"><a class="permalink" href="#Host_names_and_DNS">Host - names and DNS</a></h2> -<p class="Pp">The system resolves host names according the rules for hosts in - the name service switch configuration at - <span class="Pa">/etc/nsswitch.conf</span>. By default, it will query - <span class="Pa">/etc/hosts</span> first, and then the DNS resolver - specified in <span class="Pa">/etc/resolv.conf</span>.</p> -<p class="Pp">Multicast DNS and DNS Service Discovery are usually not enabled by - default on a fresh <span class="Ux">NetBSD</span> system, and can be enabled - by setting “mdnsd=YES” in - <span class="Pa">/etc/rc.conf</span>, and either rebooting or running the - following command:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">service mdnsd start</code></pre> -</div> -<p class="Pp">You may also wish to enable mdnsd as a source for host lookups in - <span class="Pa">/etc/nsswitch.conf</span>, see - <a class="Xr">nsswitch.conf(5)</a>.</p> -<p class="Pp">If your network does not have a usable DNS resolver, e.g. one - provided by DHCP, you can run a local caching recursive resolver by setting - “named=YES” in <span class="Pa">/etc/rc.conf</span> and either - rebooting or running the following command:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">service named start</code></pre> -</div> -<p class="Pp"><a class="Xr">named(8)</a> is configured in - <span class="Pa">/etc/named.conf</span> by default to run as a local caching - recursive resolver. Then, to make the system use it, put the following in - <span class="Pa">/etc/resolv.conf</span>:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>nameserver 127.0.0.1</pre> -</div> -</section> -<section class="Ss"> -<h2 class="Ss" id="Wireless_networking"><a class="permalink" href="#Wireless_networking">Wireless - networking</a></h2> -<p class="Pp">To configure the system to connect to a Wi-Fi network with a - password using WPA:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">wpa_passphrase networkname password >> /etc/wpa_supplicant.conf</code></pre> -</div> -<p class="Pp">To configure the system to connect to an open wireless network - with no password, edit <span class="Pa">/etc/wpa_supplicant.conf</span> - instead of using <a class="Xr">wpa_passphrase(8)</a>:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>network={ - ssid="Public-WiFi" - key_mgmt=NONE - priority=100 -}</pre> -</div> -<p class="Pp">Then bring up the interface and start the necessary daemons:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">ifconfig iwm0 up</code> -<code class="Ic">service wpa_supplicant onestart</code> -<code class="Ic">service dhcpcd onestart</code></pre> -</div> -<p class="Pp">To automatically connect at boot, add the following to - <span class="Pa">/etc/rc.conf</span>:</p> -<p class="Pp"></p> -<div class="Bd - Bd-indent"><code class="Li">ifconfig_iwm0="up"</code></div> -<div class="Bd Bd-indent"><code class="Li">dhcpcd=YES</code></div> -<div class="Bd Bd-indent"><code class="Li">wpa_supplicant=YES</code></div> -<p class="Pp">While using <a class="Xr">wpa_supplicant(8)</a>, you can easily - retrieve network scan results with <a class="Xr">wpa_cli(8)</a>:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">wpa_cli scan_results</code></pre> -</div> -<p class="Pp">Or trigger a rescan:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">wpa_cli scan</code></pre> -</div> -</section> -<section class="Ss"> -<h2 class="Ss" id="RPC-based_network_services"><a class="permalink" href="#RPC-based_network_services">RPC-based - network services</a></h2> -<p class="Pp">Several services depend on the RPC portmapper - <a class="Xr">rpcbind(8)</a> - formerly known as - <code class="Ic">portmap</code> - being running for proper operation. This - includes YP (NIS) and NFS exports, among other services. To get the RPC - portmapper to start automatically on boot, you will need to have this line - in <span class="Pa">/etc/rc.conf</span>:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">rpcbind=YES</code></div> -</section> -<section class="Ss"> -<h2 class="Ss" id="YP_(Network_Information_Service)_Setup"><a class="permalink" href="#YP_(Network_Information_Service)_Setup">YP - (Network Information Service) Setup</a></h2> -<p class="Pp">Check the YP domain name with the <a class="Xr">domainname(1)</a> - command. If necessary, correct it by editing the - <span class="Pa">/etc/defaultdomain</span> file or by setting the - “<var class="Va">domainname</var>” variable in - <span class="Pa">/etc/rc.conf</span>. The - <span class="Pa">/etc/rc.d/network</span> script reads this file on bootup - to determine and set the domain name. You may also set the running system's - domain name with the <a class="Xr">domainname(1)</a> command. To start YP - client services, simply run <code class="Ic">ypbind</code>, then perform the - remaining YP activation as described in <a class="Xr">passwd(5)</a> and - <a class="Xr">group(5)</a>.</p> -<p class="Pp">In particular, to enable YP passwd support, you'll need to update - <span class="Pa">/etc/nsswitch.conf</span> to include “nis” - for the “passwd” and “group” entries. A - traditional way to accomplish the same thing is to add following entry to - local passwd database via <a class="Xr">vipw(8)</a>:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Li">+:*::::::::</code></pre> -</div> -<p class="Pp">Note this entry has to be the very last one. This traditional way - works with the default <a class="Xr">nsswitch.conf(5)</a> setting of - “passwd”, which is “compat”.</p> -<p class="Pp">There are many more YP man pages available to help you. You can - find more information by starting with <a class="Xr">nis(8)</a>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Check_disk_mounts"><a class="permalink" href="#Check_disk_mounts">Check - disk mounts</a></h2> -<p class="Pp">Check that the disks are mounted correctly by comparing the - <span class="Pa">/etc/fstab</span> file against the output of the - <a class="Xr">mount(8)</a> and <a class="Xr">df(1)</a> commands. - Example:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Li">#</code> <code class="Ic">cat /etc/fstab</code> -/dev/sd0a / ffs rw 1 1 -/dev/sd0b none swap sw -/dev/sd0e /usr ffs rw 1 2 -/dev/sd0f /var ffs rw 1 3 -/dev/sd0g /tmp ffs rw 1 4 -/dev/sd0h /home ffs rw 1 5 - -<code class="Li">#</code> <code class="Ic">mount</code> -/dev/sd0a on / type ffs (local) -/dev/sd0e on /usr type ffs (local) -/dev/sd0f on /var type ffs (local) -/dev/sd0g on /tmp type ffs (local) -/dev/sd0h on /home type ffs (local) - -<code class="Li">#</code> <code class="Ic">df</code> -Filesystem 1024-blocks Used Avail Capacity Mounted on -/dev/sd0a 22311 14589 6606 69% / -/dev/sd0e 203399 150221 43008 78% /usr -/dev/sd0f 10447 682 9242 7% /var -/dev/sd0g 18823 2 17879 0% /tmp -/dev/sd0h 7519 5255 1888 74% /home - -<code class="Li">#</code> <code class="Ic">pstat -s</code> -Device 512-blocks Used Avail Capacity Priority -/dev/sd0b 131072 84656 46416 65% 0</pre> -</div> -<p class="Pp">Edit <span class="Pa">/etc/fstab</span> and use the - <a class="Xr">mount(8)</a> and <a class="Xr">umount(8)</a> commands as - appropriate. Refer to the above example and <a class="Xr">fstab(5)</a> for - information on the format of this file.</p> -<p class="Pp">You may wish to do NFS mounts now too, or you can do them - later.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Clock_synchronization"><a class="permalink" href="#Clock_synchronization">Clock - synchronization</a></h2> -<p class="Pp">In order to make sure the system clock is synchronized to that of - a publicly accessible NTP server, make sure that - <span class="Pa">/etc/rc.conf</span> contains the following:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">ntpdate=YES</code></div> -<div class="Bd Bd-indent"><code class="Li">ntpd=YES</code></div> -<p class="Pp">See <a class="Xr">date(1)</a>, <a class="Xr">ntpdate(8)</a>, - <a class="Xr">ntpd(8)</a>, <a class="Xr">rdate(8)</a>, and - <a class="Xr">timed(8)</a> for more information on setting the system's - date.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Installing_packages"><a class="permalink" href="#Installing_packages">Installing - packages</a></h2> -<p class="Pp">The <span class="Ux">NetBSD</span> packages collection, pkgsrc, - includes a large set of third-party software. A lot of it is available as - binary packages that you can download from - <a class="Lk" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/">https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/</a> - or a mirror.</p> -<p class="Pp">For most users, using pkgin to manage binary packages is - recommended.</p> -<p class="Pp">To install pkgin, if it was not done by the installer:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">PKG_PATH=https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/[...]</code> -<code class="Ic">export PKG_PATH</code> -<code class="Ic">pkg_add pkgin</code> -<code class="Ic">pkgin update</code> -<code class="Ic">pkgin install bash mpg123 fluxbox ...</code></pre> -</div> -<p class="Pp">See - <a class="Lk" href="https://www.pkgsrc.org/">https://www.pkgsrc.org/</a> and - <span class="Pa">pkgsrc/doc/pkgsrc.txt</span> for more details.</p> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="CHANGING_/etc_FILES"><a class="permalink" href="#CHANGING_/etc_FILES">CHANGING - /etc FILES</a></h1> -<p class="Pp">The system should be usable now, but you may wish to do more - customizing, such as adding users, etc. Many of the following sections may - be skipped if you are not using that package (for example, skip the - <a class="Sx" href="#Kerberos">Kerberos</a> section if you won't be using - Kerberos). We suggest that you <code class="Ic">cd /etc</code> and edit most - of the files in that directory.</p> -<p class="Pp">Note that the <span class="Pa">/etc/motd</span> file is modified - by <span class="Pa">/etc/rc.d/motd</span> whenever the system is booted. To - keep any custom message intact, ensure that you leave two blank lines at the - top, or your message will be overwritten.</p> -<section class="Ss"> -<h2 class="Ss" id="Add_new_users"><a class="permalink" href="#Add_new_users">Add - new users</a></h2> -<p class="Pp">To add new users and groups, there are - <a class="Xr">useradd(8)</a> and <a class="Xr">groupadd(8)</a>; see also - <a class="Xr">user(8)</a> for further programs for user and group - manipulation. You may use <a class="Xr">vipw(8)</a> to add users to the - <span class="Pa">/etc/passwd</span> file and edit - <span class="Pa">/etc/group</span> by hand to add new groups. The manual - page for <a class="Xr">su(1)</a>, tells you to make sure to put people in - the ‘wheel’ group if they need root access (non-Kerberos). For - example:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>wheel:*:0:root,myself</pre> -</div> -<p class="Pp">Follow instructions for <a class="Xr">kerberos(8)</a> if using - Kerberos for authentication.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="System_boot_scripts_and_/etc/rc.local"><a class="permalink" href="#System_boot_scripts_and_/etc/rc.local">System - boot scripts and /etc/rc.local</a></h2> -<p class="Pp"><span class="Pa">/etc/rc</span> and the - <span class="Pa">/etc/rc.d/*</span> scripts are invoked at boot time after - single user mode has exited, and at shutdown. The whole process is - controlled by the master script <span class="Pa">/etc/rc</span>. This script - should not be changed by administrators.</p> -<p class="Pp">The directory <span class="Pa">/etc/rc.d</span> contains a series - of scripts used at startup/shutdown, called by - <span class="Pa">/etc/rc</span>. <span class="Pa">/etc/rc</span> is in turn - influenced by the configuration variables present in - <span class="Pa">/etc/rc.conf</span>.</p> -<p class="Pp">The script <span class="Pa">/etc/rc.local</span> is run as the - last thing during multiuser boot, and is provided to allow any other local - hooks necessary for the system.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="rc.conf"><a class="permalink" href="#rc.conf">rc.conf</a></h2> -<p class="Pp">To enable or disable various services on system startup, - corresponding entries can be made in <span class="Pa">/etc/rc.conf</span>. - You can take a look at <span class="Pa">/etc/defaults/rc.conf</span> to see - a list of default system variables, which you can override in - <span class="Pa">/etc/rc.conf</span>. Note you are - <a class="permalink" href="#not"><i class="Em" id="not">not</i></a> supposed - to change <span class="Pa">/etc/defaults/rc.conf</span> directly, edit only - <span class="Pa">/etc/rc.conf</span>. See <a class="Xr">rc.conf(5)</a> for - further information.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Automounter_daemon_(AMD)"><a class="permalink" href="#Automounter_daemon_(AMD)">Automounter - daemon (AMD)</a></h2> -<p class="Pp">To use the <a class="Xr">amd(8)</a> automounter, create the - <span class="Pa">/etc/amd</span> directory, copy example config files from - <span class="Pa">/usr/share/examples/amd</span> to - <span class="Pa">/etc/amd</span> and customize them as needed. - Alternatively, you can get your maps with YP.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Concatenated_disks_(ccd)"><a class="permalink" href="#Concatenated_disks_(ccd)">Concatenated - disks (ccd)</a></h2> -<p class="Pp">If you are using <a class="Xr">ccd(4)</a> concatenated disks, edit - <span class="Pa">/etc/ccd.conf</span>. You may wish to take a look to - <a class="Xr">ccdconfig(8)</a> for more information about this file. Use the - <code class="Ic">ccdconfig -U</code> command to unload and the - <code class="Ic">ccdconfig -C</code> command to create tables internal to - the kernel for the concatenated disks. You then <a class="Xr">mount(8)</a>, - <a class="Xr">umount(8)</a>, and edit <span class="Pa">/etc/fstab</span> as - needed.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="NetBSD_Packet_Filter"><a class="permalink" href="#NetBSD_Packet_Filter"><span class="Ux">NetBSD - Packet</span> Filter</a></h2> -<p class="Pp"><a class="Xr">npf(7)</a> is the default firewall used on - <span class="Ux">NetBSD</span>. You may wish to enable it if your machine is - connected directly to the internet. To do this, edit - <span class="Pa">/etc/npf.conf</span> and set “npf=YES” in - <span class="Pa">/etc/rc.conf</span>. Configuration examples for NPF can be - found in <span class="Pa">/usr/share/examples/npf</span>. Before installing - a configuration, you can validate it with <a class="Xr">npfctl(8)</a>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="X_Display_Manager"><a class="permalink" href="#X_Display_Manager">X - Display Manager</a></h2> -<p class="Pp">If you've installed X, you may want to turn on - <a class="Xr">xdm(1)</a>, the X Display Manager. To do this, set - “xdm=YES” in <span class="Pa">/etc/rc.conf</span>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Printers"><a class="permalink" href="#Printers">Printers</a></h2> -<p class="Pp">Edit <span class="Pa">/etc/printcap</span> and - <span class="Pa">/etc/hosts.lpd</span> to get any printers set up. Consult - <a class="Xr">lpd(8)</a> and <a class="Xr">printcap(5)</a> if needed.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Internet_Services_(inetd)"><a class="permalink" href="#Internet_Services_(inetd)">Internet - Services (inetd)</a></h2> -<p class="Pp">Various internet services can be enabled in - <span class="Pa">/etc/inetd.conf</span>, including - <a class="Xr">httpd(8)</a> and <a class="Xr">finger(1)</a>. Note that by - default all services are disabled for security reasons. Only add things that - are really needed.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Kerberos"><a class="permalink" href="#Kerberos">Kerberos</a></h2> -<p class="Pp">If you are going to use Kerberos for authentication, see - <a class="Xr">kerberos(8)</a> and “info heimdal” for more - information. If you already have a Kerberos master, change directory to - <span class="Pa">/etc/kerberosV</span> and configure. Remember to get a - <span class="Pa">srvtab</span> from the master so that the remote commands - work.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Mail_Aliases"><a class="permalink" href="#Mail_Aliases">Mail - Aliases</a></h2> -<p class="Pp">Check <span class="Pa">/etc/mail/aliases</span> and update - appropriately if you want e-mail to be routed to non-local addresses or to - different users.</p> -<p class="Pp">Run <a class="Xr">newaliases(1)</a> after changes.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Postfix"><a class="permalink" href="#Postfix">Postfix</a></h2> -<p class="Pp"><span class="Ux">NetBSD</span> uses Postfix as its Mail Transfer - Agent. Postfix is started by default, but its initial configuration does not - cause it to listen on the network for incoming connections. To configure - Postfix, see <span class="Pa">/etc/postfix/main.cf</span> and - <span class="Pa">/etc/postfix/master.cf</span>. If you wish to use a - different MTA (e.g., sendmail), install your MTA of choice and edit - <span class="Pa">/etc/mailer.conf</span> to point to the proper - binaries.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="DHCP_server"><a class="permalink" href="#DHCP_server">DHCP - server</a></h2> -<p class="Pp">If this is a DHCP server, edit - <span class="Pa">/etc/dhcpd.conf</span> and - <span class="Pa">/etc/dhcpd.interfaces</span> as needed. You will have to - make sure <span class="Pa">/etc/rc.conf</span> has “dhcpd=YES” - or run <a class="Xr">dhcpd(8)</a> manually.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Bootparam_server"><a class="permalink" href="#Bootparam_server">Bootparam - server</a></h2> -<p class="Pp">If this is a Bootparam server, edit - <span class="Pa">/etc/bootparams</span> as needed. You will have to turn it - on in <span class="Pa">/etc/rc.conf</span> by adding - “bootparamd=YES”.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="NFS_server"><a class="permalink" href="#NFS_server">NFS - server</a></h2> -<p class="Pp">If this is an NFS server, make sure - <span class="Pa">/etc/rc.conf</span> has:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>nfs_server=YES -mountd=YES -rpcbind=YES</pre> -</div> -<p class="Pp">Edit <span class="Pa">/etc/exports</span> and get it correct. - After this, you can start the server by issuing:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">service rpcbind start</code> -<code class="Ic">service mountd start</code> -<code class="Ic">service nfsd start</code></pre> -</div> -which will also start dependencies. -</section> -<section class="Ss"> -<h2 class="Ss" id="HP_remote_boot_server"><a class="permalink" href="#HP_remote_boot_server">HP - remote boot server</a></h2> -<p class="Pp">Edit <span class="Pa">/etc/rbootd.conf</span> if needed for remote - booting. If you do not have HP computers doing remote booting, do not enable - this.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Daily,_weekly,_monthly_scripts"><a class="permalink" href="#Daily,_weekly,_monthly_scripts">Daily, - weekly, monthly scripts</a></h2> -<p class="Pp">Look at and possibly edit the - <span class="Pa">/etc/daily.conf</span>, - <span class="Pa">/etc/weekly.conf</span>, and - <span class="Pa">/etc/monthly.conf</span> configuration files. You can check - which values you can set by looking to their matching files in - <span class="Pa">/etc/defaults</span>. Your site specific things should go - into <span class="Pa">/etc/daily.local</span>, - <span class="Pa">/etc/weekly.local</span>, and - <span class="Pa">/etc/monthly.local</span>.</p> -<p class="Pp">These scripts have been limited so as to keep the system running - without filling up disk space from normal running processes and database - updates. (You probably do not need to understand them.)</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Other_files_in_/etc"><a class="permalink" href="#Other_files_in_/etc">Other - files in /etc</a></h2> -<p class="Pp">Look at the other files in <span class="Pa">/etc</span> and edit - them as needed. (Do not edit files ending in <span class="Pa">.db</span> - — like <span class="Pa">pwd.db</span>, - <span class="Pa">spwd.db</span>, nor <span class="Pa">localtime</span>, nor - <span class="Pa">rmt</span>, nor any directories.)</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Crontab_(background_running_processes)"><a class="permalink" href="#Crontab_(background_running_processes)">Crontab - (background running processes)</a></h2> -<p class="Pp">Check what is running by typing <code class="Ic">crontab -l</code> - as root and see if anything unexpected is present. Do you need anything - else? Do you wish to change things? For example, if you do not like root - getting standard output of the daily scripts, and want only the security - scripts that are mailed internally, you can type <code class="Ic">crontab - -e</code> and change some of the lines to read:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>30 1 * * * /bin/sh /etc/daily 2>&1 > /var/log/daily.out -30 3 * * 6 /bin/sh /etc/weekly 2>&1 > /var/log/weekly.out -30 5 1 * * /bin/sh /etc/monthly 2>&1 > /var/log/monthly.out</pre> -</div> -<p class="Pp">See <a class="Xr">crontab(5)</a>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Next_day_cleanup"><a class="permalink" href="#Next_day_cleanup">Next - day cleanup</a></h2> -<p class="Pp">After the first night's security run, change ownerships and - permissions on files, directories, and devices; root should have received - mail with subject: "<hostname> daily insecurity output.". - This mail contains a set of security recommendations, presented as a list - looking like this:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>var/mail: - permissions (0755, 0775) -etc/daily: - user (0, 3)</pre> -</div> -<p class="Pp">The best bet is to follow the advice in that list. The recommended - setting is the first item in parentheses, while the current setting is the - second one. This list is generated by <a class="Xr">mtree(8)</a> using - <span class="Pa">/etc/mtree/special</span>. Use <a class="Xr">chmod(1)</a>, - <a class="Xr">chgrp(1)</a>, and <a class="Xr">chown(8)</a> as needed.</p> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYSTEM_TESTING"><a class="permalink" href="#SYSTEM_TESTING">SYSTEM - TESTING</a></h1> -<p class="Pp">At this point, the system should be fully configured to your - liking. It is now a good time to ensure that the system behaves according to - its specifications and that it is stable on your hardware. Please refer to - <a class="Xr">tests(7)</a> for details on how to do so.</p> -<p class="Pp">You can use <a class="Xr">ps(1)</a>, <a class="Xr">netstat(1)</a>, - and <a class="Xr">fstat(1)</a> to check on running processes, network - connections, and opened files, respectively. Other tools you may find useful - are <a class="Xr">systat(1)</a> and <a class="Xr">top(1)</a>.</p> -</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">chgrp(1)</a>, <a class="Xr">chmod(1)</a>, - <a class="Xr">config(1)</a>, <a class="Xr">crontab(1)</a>, - <a class="Xr">date(1)</a>, <a class="Xr">df(1)</a>, - <a class="Xr">domainname(1)</a>, <a class="Xr">fstat(1)</a>, - <a class="Xr">hostname(1)</a>, <a class="Xr">make(1)</a>, - <a class="Xr">man(1)</a>, <a class="Xr">netstat(1)</a>, - <a class="Xr">newaliases(1)</a>, <a class="Xr">passwd(1)</a>, - <a class="Xr">pkg_add(1)</a>, <a class="Xr">ps(1)</a>, - <a class="Xr">ssh(1)</a>, <a class="Xr">su(1)</a>, - <a class="Xr">systat(1)</a>, <a class="Xr">top(1)</a>, - <a class="Xr">xdm(1)</a>, <a class="Xr">ccd(4)</a>, - <a class="Xr">aliases(5)</a>, <a class="Xr">crontab(5)</a>, - <a class="Xr">dhcpcd.conf(5)</a>, <a class="Xr">exports(5)</a>, - <a class="Xr">fstab(5)</a>, <a class="Xr">group(5)</a>, - <a class="Xr">hosts(5)</a>, <a class="Xr">ifconfig.if(5)</a>, - <a class="Xr">mailer.conf(5)</a>, <a class="Xr">named.conf(5)</a>, - <a class="Xr">nsswitch.conf(5)</a>, <a class="Xr">passwd(5)</a>, - <a class="Xr">printcap(5)</a>, <a class="Xr">rc.conf(5)</a>, - <a class="Xr">resolv.conf(5)</a>, <a class="Xr">sshd_config(5)</a>, - <a class="Xr">wpa_supplicant.conf(5)</a>, <a class="Xr">wscons.conf(5)</a>, - <a class="Xr">hier(7)</a>, <a class="Xr">hostname(7)</a>, - <a class="Xr">pkgsrc(7)</a>, <a class="Xr">tests(7)</a>, - <a class="Xr">amd(8)</a>, <a class="Xr">ccdconfig(8)</a>, - <a class="Xr">chown(8)</a>, <a class="Xr">devpubd(8)</a>, - <a class="Xr">dhcpcd(8)</a>, <a class="Xr">dhcpd(8)</a>, - <a class="Xr">dmesg(8)</a>, <a class="Xr">groupadd(8)</a>, - <a class="Xr">ifconfig(8)</a>, <a class="Xr">inetd(8)</a>, - <a class="Xr">kerberos(8)</a>, <a class="Xr">lpd(8)</a>, - <a class="Xr">mdnsd(8)</a>, <a class="Xr">mount(8)</a>, - <a class="Xr">mrouted(8)</a>, <a class="Xr">mtree(8)</a>, - <a class="Xr">named(8)</a>, <a class="Xr">nis(8)</a>, - <a class="Xr">ntpd(8)</a>, <a class="Xr">ntpdate(8)</a>, - <a class="Xr">rbootd(8)</a>, <a class="Xr">rc(8)</a>, - <a class="Xr">rdate(8)</a>, <a class="Xr">rmt(8)</a>, - <a class="Xr">route(8)</a>, <a class="Xr">rpc.bootparamd(8)</a>, - <a class="Xr">rpcbind(8)</a>, <a class="Xr">sshd(8)</a>, - <a class="Xr">timed(8)</a>, <a class="Xr">umount(8)</a>, - <a class="Xr">useradd(8)</a>, <a class="Xr">vipw(8)</a>, - <a class="Xr">wpa_cli(8)</a>, <a class="Xr">wpa_supplicant(8)</a>, - <a class="Xr">yp(8)</a>, <a class="Xr">ypbind(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">This document first appeared in <span class="Ux">OpenBSD - 2.2</span>. It has been adapted to <span class="Ux">NetBSD</span> and first - appeared in <span class="Ux">NetBSD 2.0</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">June 4, 2021</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/boot.8 4.html b/static/netbsd/man8/boot.8 4.html deleted file mode 100644 index 6cc9571e..00000000 --- a/static/netbsd/man8/boot.8 4.html +++ /dev/null @@ -1,223 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual</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> — <span class="Nd">system - bootstrapping procedures</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">This document provides information on using common features in the - <span class="Ux">NetBSD</span> boot loader. Additional information may be - found in architecture-specific <a class="Xr">boot(8)</a> manual pages.</p> -<section class="Ss"> -<h2 class="Ss" id="Boot_Protocol"><a class="permalink" href="#Boot_Protocol">Boot - Protocol</a></h2> -<p class="Pp">In the native <span class="Ux">NetBSD</span> boot protocol, - options are passed from the boot loader to the kernel via flag bits in the - <var class="Va">boothowto</var> variable (see - <a class="Xr">boothowto(9)</a>). Some boot loaders may also support other - boot protocols.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Menu"><a class="permalink" href="#Menu">Menu</a></h2> -<p class="Pp">Some boot loaders may present a menu, which may be configured via - <a class="Xr">boot.cfg(5)</a>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Interactive_mode"><a class="permalink" href="#Interactive_mode">Interactive - mode</a></h2> -<p class="Pp">In interactive mode, the boot loader will present a prompt, - allowing input of these commands:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="boot"><a class="permalink" href="#boot"><code class="Ic">boot</code></a> - [<var class="Va">device</var>:][<var class="Va">filename</var>] - [<code class="Fl">-1234abcdmqsvxz</code>]</dt> - <dd>The default <var class="Va">device</var> will be set to the disk that the - boot loader was loaded from. To boot from an alternate disk, the full name - of the device should be given at the prompt. <var class="Va">device</var> - is of the form <var class="Va">xd</var> - [<var class="Va">N</var>[<var class="Va">x</var>]] where - <var class="Va">xd</var> is the device from which to boot, - <var class="Va">N</var> is the unit number, and <var class="Va">x</var> is - the partition letter. - <p class="Pp">The following list of supported devices may vary from - installation to installation:</p> - <p class="Pp"></p> - <dl class="Bl-hang Bl-compact"> - <dt>hd</dt> - <dd>Hard disks.</dd> - <dt>fd</dt> - <dd>Floppy drives.</dd> - </dl> - <p class="Pp">The default <var class="Va">filename</var> is - <span class="Pa">netbsd</span>; if the boot loader fails to successfully - open that image, it then tries <span class="Pa">netbsd.gz</span> - (expected to be a kernel image compressed by gzip), followed by - <span class="Pa">netbsd.old</span>, - <span class="Pa">netbsd.old.gz</span>, <span class="Pa">onetbsd</span>, - and finally <span class="Pa">onetbsd.gz</span>. Alternate system images - can be loaded by just specifying the name of the image.</p> - <p class="Pp">Options are:</p> - <dl class="Bl-tag"> - <dt id="1"><a class="permalink" href="#1"><code class="Fl">-1</code></a></dt> - <dd>Sets the machine-dependent flag - <a class="permalink" href="#RB_MD1"><b class="Sy" id="RB_MD1">RB_MD1</b></a> - in <var class="Va">boothowto</var>.</dd> - <dt id="2"><a class="permalink" href="#2"><code class="Fl">-2</code></a></dt> - <dd>Sets the machine-dependent flag - <a class="permalink" href="#RB_MD2"><b class="Sy" id="RB_MD2">RB_MD2</b></a> - in <var class="Va">boothowto</var>.</dd> - <dt id="3"><a class="permalink" href="#3"><code class="Fl">-3</code></a></dt> - <dd>Sets the machine-dependent flag - <a class="permalink" href="#RB_MD3"><b class="Sy" id="RB_MD3">RB_MD3</b></a> - in <var class="Va">boothowto</var>.</dd> - <dt id="4"><a class="permalink" href="#4"><code class="Fl">-4</code></a></dt> - <dd>Sets the machine-dependent flag - <a class="permalink" href="#RB_MD4"><b class="Sy" id="RB_MD4">RB_MD4</b></a> - in <var class="Va">boothowto</var>.</dd> - <dt id="a"><a class="permalink" href="#a"><code class="Fl">-a</code></a></dt> - <dd>Sets the - <a class="permalink" href="#RB_ASKNAME"><b class="Sy" id="RB_ASKNAME">RB_ASKNAME</b></a> - flag in <var class="Va">boothowto</var>. This causes the kernel to - prompt for the root file system device, the system crash dump device, - and the path to <a class="Xr">init(8)</a>.</dd> - <dt id="b"><a class="permalink" href="#b"><code class="Fl">-b</code></a></dt> - <dd>Sets the - <a class="permalink" href="#RB_HALT"><b class="Sy" id="RB_HALT">RB_HALT</b></a> - flag in <var class="Va">boothowto</var>. This causes subsequent reboot - attempts to halt instead of rebooting.</dd> - <dt id="c"><a class="permalink" href="#c"><code class="Fl">-c</code></a></dt> - <dd>Sets the - <a class="permalink" href="#RB_USERCONF"><b class="Sy" id="RB_USERCONF">RB_USERCONF</b></a> - flag in <var class="Va">boothowto</var>. This causes the kernel to - enter the <a class="Xr">userconf(4)</a> device configuration manager - as soon as possible during the boot. <a class="Xr">userconf(4)</a> - allows devices to be enabled or disabled, and allows device locators - (such as hardware addresses or bus numbers) to be modified before the - kernel attempts to attach the devices.</dd> - <dt id="d"><a class="permalink" href="#d"><code class="Fl">-d</code></a></dt> - <dd>Sets the - <a class="permalink" href="#RB_KDB"><b class="Sy" id="RB_KDB">RB_KDB</b></a> - flag in <var class="Va">boothowto</var>. Requests the kernel to enter - debug mode, in which it waits for a connection from a kernel debugger; - see <a class="Xr">ddb(4)</a>.</dd> - <dt id="m"><a class="permalink" href="#m"><code class="Fl">-m</code></a></dt> - <dd>Sets the - <a class="permalink" href="#RB_MINIROOT"><b class="Sy" id="RB_MINIROOT">RB_MINIROOT</b></a> - flag in <var class="Va">boothowto</var>. Informs the kernel that a - mini-root file system is present in memory.</dd> - <dt id="q"><a class="permalink" href="#q"><code class="Fl">-q</code></a></dt> - <dd>Sets the - <a class="permalink" href="#AB_QUIET"><b class="Sy" id="AB_QUIET">AB_QUIET</b></a> - flag in <var class="Va">boothowto</var>. Boot the system in quiet - mode.</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>Sets the - <a class="permalink" href="#RB_SINGLE"><b class="Sy" id="RB_SINGLE">RB_SINGLE</b></a> - flag in <var class="Va">boothowto</var>. Boot the system in - single-user mode.</dd> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Sets the - <a class="permalink" href="#AB_VERBOSE"><b class="Sy" id="AB_VERBOSE">AB_VERBOSE</b></a> - flag in <var class="Va">boothowto</var>. Boot the system in verbose - mode.</dd> - <dt id="x"><a class="permalink" href="#x"><code class="Fl">-x</code></a></dt> - <dd>Sets the - <a class="permalink" href="#AB_DEBUG"><b class="Sy" id="AB_DEBUG">AB_DEBUG</b></a> - flag in <var class="Va">boothowto</var>. Boot the system with debug - messages enabled.</dd> - <dt id="z"><a class="permalink" href="#z"><code class="Fl">-z</code></a></dt> - <dd>Sets the - <a class="permalink" href="#AB_SILENT"><b class="Sy" id="AB_SILENT">AB_SILENT</b></a> - flag in <var class="Va">boothowto</var>. Boot the system in silent - mode.</dd> - </dl> - </dd> - <dt id="consdev"><a class="permalink" href="#consdev"><code class="Ic">consdev</code></a> - <var class="Va">dev</var></dt> - <dd>Immediately switch the console to the specified device - <var class="Va">dev</var> and reprint the banner. - <var class="Va">dev</var> must be one of <var class="Ar">pc</var>, - <var class="Ar">com0</var>, <var class="Ar">com1</var>, - <var class="Ar">com2</var>, <var class="Ar">com3</var>, - <var class="Ar">com0kbd</var>, <var class="Ar">com1kbd</var>, - <var class="Ar">com2kbd</var>, <var class="Ar">com3kbd</var>, or - <var class="Ar">auto</var>. See - <a class="Sx" href="#Console_Selection_Policy">Console Selection - Policy</a> in <a class="Xr">x86/boot_console(8)</a>.</dd> - <dt id="dev"><a class="permalink" href="#dev"><code class="Ic">dev</code></a> - [<var class="Va">device</var>]</dt> - <dd>Set the default drive and partition for subsequent filesystem operations. - Without an argument, print the current setting. - <var class="Va">device</var> is of the form specified in - <code class="Cm">boot</code>.</dd> - <dt id="help"><a class="permalink" href="#help"><code class="Ic">help</code></a></dt> - <dd>Print an overview about commands and arguments.</dd> - <dt id="ls"><a class="permalink" href="#ls"><code class="Ic">ls</code></a> - [<span class="Pa">path</span>]</dt> - <dd>Print a directory listing of <span class="Pa">path</span>, containing - inode number, filename, and file type. <span class="Pa">path</span> can - contain a device specification.</dd> - <dt id="quit"><a class="permalink" href="#quit"><code class="Ic">quit</code></a></dt> - <dd>Reboot the system.</dd> -</dl> -</div> -<p class="Pp">In an emergency, the bootstrap methods described in the - <span class="Ux">NetBSD</span> installation notes for the specific - architecture can be used.</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">/boot</span></dt> - <dd>boot program code loaded by the primary bootstrap</dd> - <dt><span class="Pa">/netbsd</span></dt> - <dd>system code</dd> - <dt><span class="Pa">/netbsd.gz</span></dt> - <dd>gzip-compressed system code</dd> - <dt><span class="Pa">/usr/mdec/boot</span></dt> - <dd>master copy of the boot program (copy to /boot)</dd> - <dt><span class="Pa">/usr/mdec/bootxx_fstype</span></dt> - <dd>primary bootstrap for filesystem type fstype, copied to the start of the - <span class="Ux">NetBSD</span> partition by - <a class="Xr">installboot(8)</a>.</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">Architecture-specific <a class="Xr">boot(8)</a> manual pages (such - as <a class="Xr">emips/boot(8)</a>, <a class="Xr">sparc64/boot(8)</a>, - <a class="Xr">x86/boot(8)</a>), <a class="Xr">ddb(4)</a>, - <a class="Xr">userconf(4)</a>, <a class="Xr">halt(8)</a>, - <a class="Xr">installboot(8)</a>, <a class="Xr">reboot(8)</a>, - <a class="Xr">rescue(8)</a>, <a class="Xr">shutdown(8)</a>, - <a class="Xr">boothowto(9)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The kernel file name must be specified before, not after, the boot - options. Any <var class="Ar">filename</var> specified after the boot - options, e.g.:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"> -<pre><code class="Cm">boot -d netbsd.test</code></pre> -</div> -<p class="Pp">is ignored, and the default kernel is booted.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">August 16, 2014</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/compat_30.8 4.html b/static/netbsd/man8/compat_30.8 4.html deleted file mode 100644 index 8126cf11..00000000 --- a/static/netbsd/man8/compat_30.8 4.html +++ /dev/null @@ -1,145 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">COMPAT_30(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">COMPAT_30(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">compat_30</code> — <span class="Nd">setup - procedure for backward compatibility on post-3.0 releases</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1> -<p class="Pp"><code class="Cd">options COMPAT_30</code></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <code class="Nm">compat_30</code> module allows - <span class="Ux">NetBSD</span> to run <span class="Ux">NetBSD 3.0</span> - executables.</p> -<p class="Pp">The support is present if the kernel was built with option - <code class="Dv">COMPAT_30</code>. It is not available as a loadable - module.</p> -<p class="Pp">Static executables typically need no additional setup. Dynamic - binaries may require shared libraries whose major version number changed - since <span class="Ux">NetBSD 3.0</span>, which are listed below. A shadow - directory under <span class="Pa">/emul</span> is not used; the libraries can - be obtained from a <span class="Ux">NetBSD 3.0</span> distribution and - installed in the original directories shown, as the major version number in - the file name will prevent conflicts. If an upgrade installation from - <span class="Ux">NetBSD 3.0</span> has been done and these libraries are - still present, nothing more need be done.</p> -<section class="Ss"> -<h2 class="Ss" id="Libraries_needed_from_3.0"><a class="permalink" href="#Libraries_needed_from_3.0">Libraries - needed from 3.0</a></h2> -<ul class="Bl-item"> - <li><span class="Pa">/lib/libcrypto.so.2.1</span> - <span class="Pa">/lib/libcrypto.so.2</span></li> - <li><span class="Pa">/usr/lib/libcrypto.so.2.1</span> - <span class="Pa">/usr/lib/libcrypto.so.2</span></li> - <li><span class="Pa">/lib/libevent.so.0.2</span> - <span class="Pa">/lib/libevent.so.0</span></li> - <li><span class="Pa">/usr/lib/libevent.so.0.2</span> - <span class="Pa">/usr/lib/libevent.so.0</span></li> - <li><span class="Pa">/usr/lib/libg2c.so.2.0</span> - <span class="Pa">/usr/lib/libg2c.so.2</span></li> - <li><span class="Pa">/usr/lib/libkadm.so.5.0</span> - <span class="Pa">/usr/lib/libkadm.so.5</span></li> - <li><span class="Pa">/usr/lib/libkafs.so.6.0</span> - <span class="Pa">/usr/lib/libkafs.so.6</span></li> - <li><span class="Pa">/usr/lib/libkdb.so.5.0</span> - <span class="Pa">/usr/lib/libkdb.so.5</span></li> - <li><span class="Pa">/usr/lib/libkrb5.so.19.1</span> - <span class="Pa">/usr/lib/libkrb5.so.19</span></li> - <li><span class="Pa">/usr/lib/libkrb.so.6.0</span> - <span class="Pa">/usr/lib/libkrb.so.6</span></li> - <li><span class="Pa">/usr/lib/libkstream.so.2.0</span> - <span class="Pa">/usr/lib/libkstream.so.2</span></li> - <li><span class="Pa">/usr/lib/libmagic.so.0.1</span> - <span class="Pa">/usr/lib/libmagic.so.0</span></li> - <li><span class="Pa">/usr/lib/libpcap.so.1.4</span> - <span class="Pa">/usr/lib/libpcap.so.1</span></li> - <li><span class="Pa">/lib/libradius.so.0.0</span> - <span class="Pa">/lib/libradius.so.0</span></li> - <li><span class="Pa">/usr/lib/libradius.so.0.0</span> - <span class="Pa">/usr/lib/libradius.so.0</span></li> - <li><span class="Pa">/usr/lib/libssh.so.1.0</span> - <span class="Pa">/usr/lib/libssh.so.1</span></li> - <li><span class="Pa">/usr/lib/libssl.so.3.0</span> - <span class="Pa">/usr/lib/libssl.so.3</span></li> - <li><span class="Pa">/usr/lib/libstdc++.so.5.0</span> - <span class="Pa">/usr/lib/libstdc++.so.5</span></li> - <li><span class="Pa">/lib/libz.so.0.4</span> - <span class="Pa">/lib/libz.so.0</span></li> - <li><span class="Pa">/usr/lib/libz.so.0.4</span> - <span class="Pa">/usr/lib/libz.so.0</span></li> - <li><span class="Pa">/usr/lib/libamu.so.2.1</span> - <span class="Pa">/usr/lib/libamu.so.2</span></li> -</ul> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="IMPLEMENTATION_NOTES"><a class="permalink" href="#IMPLEMENTATION_NOTES">IMPLEMENTATION - NOTES</a></h1> -<p class="Pp"><code class="Dv">COMPAT_30</code> enables the - <span class="Ux">NetBSD 3.0</span> versions of the following system calls, - whose syscall numbers and argument structures were changed after the 3.0 - release to accommodate 64-bit filesystems: <a class="Xr">fhstat(2)</a>, - <a class="Xr">fstat(2)</a>, <a class="Xr">getdents(2)</a>, - <a class="Xr">lstat(2)</a>, <a class="Xr">stat(2)</a>.</p> -<p class="Pp">The filehandle structure (formerly - <var class="Vt">fhandle_t</var>) was made opaque to userland and - variable-sized. A <var class="Fa">fh_size</var> argument was added to - related syscalls: <a class="Xr">fhstat(2)</a>, - <a class="Xr">fhstatvfs(2)</a>, <a class="Xr">fhstatvfs1(2)</a>, - <a class="Xr">fhopen(2)</a>, <a class="Xr">getfh(2)</a>. This changes the - API and ABI of those syscalls, <code class="Dv">COMPAT_30</code> enables - binary compatibility with the old ABI. Source compatibility is not provided, - as use of those syscalls is supposed to be rare.</p> -<p class="Pp">The error code from the <a class="Xr">socket(2)</a> syscall - changed from <code class="Er">EPROTONOSUPPORT</code> to - <code class="Er">EAFNOSUPPORT</code> in the case of an unsupported address - family. <code class="Dv">COMPAT_30</code> enables binary compatibility with - the old ABI. Source compatibility is not provided.</p> -<p class="Pp">The <var class="Vt">struct ntptimeval</var> used by - <a class="Xr">ntp_gettime(2)</a> changed with the implementation of - timecounters.</p> -</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">config(1)</a>, <a class="Xr">fhstat(2)</a>, - <a class="Xr">fstat(2)</a>, <a class="Xr">getdents(2)</a>, - <a class="Xr">lstat(2)</a>, <a class="Xr">stat(2)</a>, - <a class="Xr">options(4)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp"><span class="Ux">NetBSD</span> offers back-compatibility options - back to <span class="Ux">NetBSD 0.9</span>, but the first to be documented - with a manual page is <code class="Nm">compat_30</code>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The compatible <a class="Xr">getdents(2)</a> is unable to see - directory entries beneath the top layer of a union, even though the real 3.0 - <code class="Fn">getdents</code>() did not have that problem.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SECURITY_CONSIDERATIONS"><a class="permalink" href="#SECURITY_CONSIDERATIONS">SECURITY - CONSIDERATIONS</a></h1> -<p class="Pp">Programs with security impact that receive incorrect directory - contents from <code class="Fn">getdents</code>() may behave improperly, as - when they are unable to find, or find the wrong versions of, important - files.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">December 15, 2007</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/compat_bsdos.8 4.html b/static/netbsd/man8/compat_bsdos.8 4.html deleted file mode 100644 index dad249b8..00000000 --- a/static/netbsd/man8/compat_bsdos.8 4.html +++ /dev/null @@ -1,93 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">COMPAT_BSDOS(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">COMPAT_BSDOS(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">compat_bsdos</code> — - <span class="Nd">binary compatibility for BSDi releases</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <code class="Dv">COMPAT_NOMID</code> kernel option includes - compatibility with - BSDi<span class="No"> 1.</span><i class="Em">x</i>–3.<i class="Em">x</i> - <a class="Xr">a.out(5)</a> binaries on <span class="Ux">NetBSD</span>/i386 - and <span class="Ux">NetBSD</span>/amd64. The option is enabled by default - in the <code class="Li">GENERIC</code> kernel on i386, but needs to be set - along with <code class="Dv">EXEC_AOUT</code> on amd64.</p> -<p class="Pp">Null memory protection must be disabled with the - <a class="Xr">sysctl(7)</a> option <var class="Va">vm.user_va0_disable</var> - set to <code class="Li">0</code> for the binaries to run successfully.</p> -<p class="Pp"><span class="Ux">BSD/OS</span> binaries may be placed under - <span class="Pa">/emul</span> directory to match the location of other - non-native executables on <span class="Ux">NetBSD</span>, but the - compatibility environment does not automatically lookup libraries under - <span class="Pa">/emul/bsdos</span> as happens with the shared libraries for - <span class="Ux">NetBSD 1.0–1.5</span> <a class="Xr">a.out(5)</a> - binaries under <span class="Pa">/emul/aout</span>.</p> -<p class="Pp">BSD/386<span class="No"> 1.0–1.1</span> uses static - binaries that do not dynamically load libraries at runtime.</p> -<p class="Pp"><span class="Ux">BSD/OS 2.0</span> introduced “static - shared libraries” as the default for standard binaries. The shared - libraries are compiled from <span class="Pa">/lib</span> and - <span class="Pa">/usr/lib</span> to a custom format bound to memory loading - addresses for each library under <span class="Pa">/shlib</span>. BSDi - libraries under <span class="Pa">/shlib</span> are not in the standard - <a class="Xr">ar(5)</a> or position-independent shared object formats and - cannot be loaded by <a class="Xr">ldconfig(8)</a> on - <span class="Ux">NetBSD</span>. In order for BSDi executables to access the - objects at the hardcoded <span class="Pa">/shlib</span> path, the user may - setup a symbolic link from <span class="Pa">/shlib</span> to - <span class="Pa">/emul/bsdos/shlib</span>.</p> -<p class="Pp"><span class="Ux">BSD/OS 4.0</span> switched to an ELF binary - executable format that does not run under the compatibility layers currently - available on <span class="Ux">NetBSD</span>.</p> -</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">ld.aout_so(1)</a>, <a class="Xr">options(4)</a>, - <a class="Xr">a.out(5)</a>, <a class="Xr">elf(5)</a>, - <a class="Xr">sysctl(7)</a>, <a class="Xr">compat_netbsd32(8)</a>, - <a class="Xr">ldconfig(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">BSD/386<span class="No"> 1.0–1.1</span> was derived - from <span class="Ux">4.3BSD</span> Reno code in the Net/2 release.</p> -<p class="Pp"><span class="Ux">BSD/OS 2.0</span> was based on - <span class="Ux">4.4BSD</span> Lite, but added the new static shared library - format as the runtime default for executables. The build system included the - <code class="Li">shlicc</code> command with the - <code class="Fl">-Bstatic</code> flag that allowed reverting to the standard - library archive format that remained available under - <span class="Pa">/lib</span> and <span class="Pa">/usr/lib</span>.</p> -<p class="Pp"><span class="Ux">NetBSD 1.0</span> added shared libraries using a - standard position-independent shared object format. The previous default - relocatable libraries in the traditional <a class="Xr">ar(5)</a> format - remained available.</p> -<p class="Pp"><span class="Ux">OpenBSD 2.2–4.7</span> included a - different compatibility implementation under the - <code class="Dv">COMPAT_BSDOS</code> kernel option.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp"><span class="Ux">BSD/OS</span> compatibility was broken on - <span class="Ux">NetBSD 5–6</span>.</p> -<p class="Pp"><span class="Ux">BSD/OS 3.0</span> added SPARC support, but the - binaries are incorrectly recognized as SunOS executables and fail on - <span class="Ux">NetBSD</span>/sparc and - <span class="Ux">NetBSD</span>/sparc64.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">August 27, 2020</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/compat_freebsd.8 4.html b/static/netbsd/man8/compat_freebsd.8 4.html deleted file mode 100644 index 53475343..00000000 --- a/static/netbsd/man8/compat_freebsd.8 4.html +++ /dev/null @@ -1,258 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">COMPAT_FREEBSD(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">COMPAT_FREEBSD(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">compat_freebsd</code> — - <span class="Nd">setup procedure for running FreeBSD binaries</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<div class="Bf Sy">compat_freebsd is not maintained anymore, and new FreeBSD - binaries cannot be expected to work. The compat_freebsd feature is available - in NetBSD only to support the FreeBSD tw_cli driver.</div> -<p class="Pp"><span class="Ux">NetBSD</span> supports running - <span class="Ux">FreeBSD</span> binaries. Most binaries should work, except - programs that use <span class="Ux">FreeBSD</span>-specific features. These - include i386-specific calls, such as syscons utilities. The - <span class="Ux">FreeBSD</span> compatibility feature is active for kernels - compiled with the <code class="Dv">COMPAT_FREEBSD</code> option enabled.</p> -<p class="Pp">A lot of programs are dynamically linked. This means, that you - will also need the <span class="Ux">FreeBSD</span> shared libraries that the - program depends on, and the runtime linker. Also, you will need to create a - “shadow root” directory for <span class="Ux">FreeBSD</span> - binaries on your <span class="Ux">NetBSD</span> system. This directory is - named <span class="Pa">/emul/freebsd</span>. Any file operations done by - <span class="Ux">FreeBSD</span> programs run under - <span class="Ux">NetBSD</span> will look in this directory first. So, if a - <span class="Ux">FreeBSD</span> program opens, for example, - <span class="Pa">/etc/passwd</span>, <span class="Ux">NetBSD</span> will - first try to open <span class="Pa">/emul/freebsd/etc/passwd</span>, and if - that does not exist open the ‘real’ - <span class="Pa">/etc/passwd</span> file. It is recommended that you install - <span class="Ux">FreeBSD</span> packages that include configuration files, - etc under <span class="Pa">/emul/freebsd</span>, to avoid naming conflicts - with possible <span class="Ux">NetBSD</span> counterparts. Shared libraries - should also be installed in the shadow tree.</p> -<p class="Pp">Generally, you will need to look for the shared libraries that - <span class="Ux">FreeBSD</span> binaries depend on only the first few times - that you install a <span class="Ux">FreeBSD</span> program on your - <span class="Ux">NetBSD</span> system. After a while, you will have a - sufficient set of <span class="Ux">FreeBSD</span> shared libraries on your - system to be able to run newly imported <span class="Ux">FreeBSD</span> - binaries without any extra work.</p> -<section class="Ss"> -<h2 class="Ss" id="Setting_up_shared_libraries"><a class="permalink" href="#Setting_up_shared_libraries">Setting - up shared libraries</a></h2> -<p class="Pp">How to get to know which shared libraries - <span class="Ux">FreeBSD</span> binaries need, and where to get them? - Basically, there are 2 possibilities (when following these instructions: you - will need to be root on your <span class="Ux">NetBSD</span> system to do the - necessary installation steps).</p> -<p class="Pp"></p> -<ol class="Bl-enum Bl-compact"> - <li>You have access to a <span class="Ux">FreeBSD</span> system. In this case - you can temporarily install the binary there, see what shared libraries it - needs, and copy them to your <span class="Ux">NetBSD</span> system. - Example: you have just ftp-ed the <span class="Ux">FreeBSD</span> binary - of SimCity. Put it on the <span class="Ux">FreeBSD</span> system you have - access to, and check which shared libraries it needs by running - ‘ldd sim’: - <div class="Bd Pp Bd-indent Li"> - <pre>me@freebsd% ldd /usr/local/lib/SimCity/res/sim -/usr/local/lib/SimCity/res/sim: - -lXext.6 => /usr/X11R6/lib/libXext.so.6.0 (0x100c1000) - -lX11.6 => /usr/X11R6/lib/libX11.so.6.0 (0x100c9000) - -lc.2 => /usr/lib/libc.so.2.1 (0x10144000) - -lm.2 => /usr/lib/libm.so.2.0 (0x101a7000) - -lgcc.261 => /usr/lib/libgcc.so.261.0 (0x101bf000)</pre> - </div> - <p class="Pp">You would need go get all the files from the last column, and - put them under <span class="Pa">/emul/freebsd</span>. This means you - eventually have these files on your <span class="Ux">NetBSD</span> - system:</p> - <ul class="Bl-item Bl-compact"> - <li><span class="Pa">/emul/freebsd/usr/X11R6/lib/libXext.so.6.0</span></li> - <li><span class="Pa">/emul/freebsd/usr/X11R6/lib/libX11.so.6.0</span></li> - <li><span class="Pa">/emul/freebsd/usr/lib/libc.so.2.1</span></li> - <li><span class="Pa">/emul/freebsd/usr/lib/libm.so.2.0</span></li> - <li><span class="Pa">/emul/freebsd/usr/lib/libgcc.so.261.0</span></li> - </ul> - <p class="Pp">Note that if you already have a - <span class="Ux">FreeBSD</span> shared library with a matching major - revision number to the first column of the <code class="Ic">ldd</code> - output, you won't need to copy the file named in the last column to your - system, the one you already have should work. It is advisable to copy - the shared library anyway if it is a newer version, though. You can - remove the old one. So, if you have these libraries on your system:</p> - <ul class="Bl-item Bl-compact"> - <li><span class="Pa">/emul/freebsd/usr/lib/libc.so.2.0</span></li> - </ul> - <p class="Pp">and you find that the ldd output for a new binary you want to - install is:</p> - <div class="Bd Pp Li"> - <pre>-lc.2 => /usr/lib/libc.so.2.1 (0x10144000)</pre> - </div> - <p class="Pp">You won't need to worry about copying - <span class="Pa">/usr/lib/libc.so.2.1</span> too, because the program - should work fine with the slightly older version. You can decide to - replace the libc.so anyway, and that should leave you with:</p> - <ul class="Bl-item Bl-compact"> - <li><span class="Pa">/emul/freebsd/usr/lib/libc.so.2.1</span></li> - </ul> - <p class="Pp">Finally, you must make sure that you have the - <span class="Ux">FreeBSD</span> runtime linker and its config files on - your system. You should copy these files from the - <span class="Ux">FreeBSD</span> system to their appropriate place on - your <span class="Ux">NetBSD</span> system (in the - <span class="Pa">/emul/freebsd</span> tree):</p> - <ul class="Bl-item Bl-compact"> - <li><span class="Pa">usr/libexec/ld.so</span></li> - <li><span class="Pa">var/run/ld.so.hints</span></li> - </ul> - </li> - <li>You don't have access to a <span class="Ux">FreeBSD</span> system. In that - case, you should get the extra files you need from various ftp sites. - Information on where to look for the various files is appended below. For - now, let's assume you know where to get the files. - <p class="Pp">Retrieve the following files (from _one_ ftp site to avoid any - version mismatches), and install them under - <span class="Pa">/emul/freebsd</span> (i.e. - <span class="Pa">foo/bar</span> is installed as - <span class="Pa">/emul/freebsd/foo/bar</span>):</p> - <ul class="Bl-item Bl-compact"> - <li><span class="Pa">sbin/ldconfig</span></li> - <li><span class="Pa">usr/bin/ldd</span></li> - <li><span class="Pa">usr/lib/libc.so.x.y.z</span></li> - <li><span class="Pa">usr/libexec/ld.so</span></li> - </ul> - <p class="Pp"><code class="Ic">ldconfig</code> and - <code class="Ic">ldd</code> don't necessarily need to be under - <span class="Pa">/emul/freebsd</span>, you can install them elsewhere in - the system too. Just make sure they don't conflict with their - <span class="Ux">NetBSD</span> counterparts. A good idea would be to - install them in <span class="Pa">/usr/local/bin</span> as - <code class="Ic">ldconfig-freebsd</code> and - <code class="Ic">ldd-freebsd</code>.</p> - <p class="Pp">Run the <span class="Ux">FreeBSD</span> ldconfig program with - directory arguments in which the <span class="Ux">FreeBSD</span> runtime - linker should look for shared libs. <span class="Pa">/usr/lib</span> are - standard, you could run like the following:</p> - <div class="Bd Pp Bd-indent Li"> - <pre>me@netbsd% mkdir -p /emul/freebsd/var/run -me@netbsd% touch /emul/freebsd/var/run/ld.so.hints -me@netbsd% ldconfig-freebsd /usr/X11R6/lib /usr/local/lib</pre> - </div> - <p class="Pp">Note that argument directories of ldconfig are mapped to - <span class="Pa">/emul/freebsd/XXXX</span> by - <span class="Ux">NetBSD</span>'s compat code, and should exist as such - on your system. Make sure - <span class="Pa">/emul/freebsd/var/run/ld.so.hints</span> is existing - when you run <span class="Ux">FreeBSD</span>'s ldconfig, if not, you may - lose <span class="Ux">NetBSD</span>'s - <span class="Pa">/var/run/ld.so.hints</span>. - <span class="Ux">FreeBSD</span> <code class="Ic">ldconfig</code> should - be statically linked, so it doesn't need any shared libraries by itself. - It will create the file - <span class="Pa">/emul/freebsd/var/run/ld.so.hints</span>. You should - rerun the <span class="Ux">FreeBSD</span> version of the ldconfig - program each time you add a new shared library.</p> - <p class="Pp">You should now be set up for <span class="Ux">FreeBSD</span> - binaries which only need a shared libc. You can test this by running the - <span class="Ux">FreeBSD</span> <code class="Ic">ldd</code> on itself. - Suppose that you have it installed as - <code class="Ic">ldd-freebsd</code>, it should produce something - like:</p> - <div class="Bd Pp Bd-indent Li"> - <pre>me@netbsd% ldd-freebsd `which ldd-freebsd` -/usr/local/bin/ldd-freebsd: - -lc.2 => /usr/lib/libc.so.2.1 (0x1001a000)</pre> - </div> - <p class="Pp">This being done, you are ready to install new - <span class="Ux">FreeBSD</span> binaries. Whenever you install a new - <span class="Ux">FreeBSD</span> program, you should check if it needs - shared libraries, and if so, whether you have them installed in the - <span class="Pa">/emul/freebsd</span> tree. To do this, you run the - <span class="Ux">FreeBSD</span> version <code class="Ic">ldd</code> on - the new program, and watch its output. <code class="Ic">ldd</code> (see - also the manual page for <a class="Xr">ldd(1)</a>) will print a list of - shared libraries that the program depends on, in the form - -l<majorname> => <fullname>.</p> - <p class="Pp">If it prints “not found” instead of - <fullname> it means that you need an extra library. Which library - this is, is shown in <majorname>, which will be of the form - XXXX.<N> You will need to find a libXXXX.so.<N>.<mm> - on a <span class="Ux">FreeBSD</span> ftp site, and install it on your - system. The XXXX (name) and <N> (major revision number) should - match; the minor number(s) <mm> are less important, though it is - advised to take the most recent version.</p> - <p class="Pp"></p> - </li> - <li>In some cases, <span class="Ux">FreeBSD</span> binary needs access to - certain device file. For example, <span class="Ux">FreeBSD</span> X server - software needs <span class="Ux">FreeBSD</span> - <span class="Pa">/dev/ttyv0</span> for ioctls. In this case, create a - symbolic link from <span class="Pa">/emul/freebsd/dev/ttyv0</span> to a - <a class="Xr">wscons(4)</a> device file like - <span class="Pa">/dev/ttyE0</span>. You will need to have at least - <code class="Cd">options WSDISPLAY_COMPAT_SYSCONS</code> and probably also - <code class="Cd">options WSDISPLAY_COMPAT_USL</code> in your kernel (see - <a class="Xr">options(4)</a> and <a class="Xr">wscons(4)</a>).</li> -</ol> -</section> -<section class="Ss"> -<h2 class="Ss" id="Finding_the_necessary_files"><a class="permalink" href="#Finding_the_necessary_files">Finding - the necessary files</a></h2> -<p class="Pp"><a class="permalink" href="#Note"><i class="Em" id="Note">Note</i></a>: - the information below is valid as of the time this document was written - (June, 1995), but certain details such as names of ftp sites, directories - and distribution names may have changed by the time you read this.</p> -<p class="Pp">The <span class="Ux">FreeBSD</span> distribution is available on a - lot of ftp sites. Sometimes the files are unpacked, and you can get the - individual files you need, but mostly they are stored in distribution sets, - usually consisting of subdirectories with gzipped tar files in them. The ftp - site for the distributions is: - <a class="Lk" href="ftp://ftp.FreeBSD.org/pub/FreeBSD">ftp://ftp.FreeBSD.org/pub/FreeBSD</a></p> -<p class="Pp">This distribution consists of a number of tar-ed and gzipped - files, Normally, they're controlled by an install program, but you can - retrieve files “by hand” too. The way to look something up is - to retrieve all the files in the distribution, and ``tar ztvf'' through them - for the file you need. Here is an example of a list of files that you might - need.</p> -<div class="Bd Pp Bd-indent Li"> -<pre>Needed Files - -ld.so 2.0-RELEASE/bindist/bindist.?? -ldconfig 2.0-RELEASE/bindist/bindist.?? -ldd 2.0-RELEASE/bindist/bindist.?? -libc.so.2 2.0-RELEASE/bindist/bindist.?? -libX11.so.6.0 2.0-RELEASE/XFree86-3.1/XFree86-3.1-bin.tar.gz -libX11.so.6.0 XFree86-3.1.1/X311bin.tgz -libXt.so.6.0 2.0-RELEASE/XFree86-3.1/XFree86-3.1-bin.tar.gz -libXt.so.6.0 XFree86-3.1.1/X311bin.tgz</pre> -</div> -<p class="Pp">The files called “bindist.??” are tar-ed, gzipped - and split, so you can extract contents by “cat bindist.?? | tar zpxf - -”.</p> -<p class="Pp">Extract the files from these gzipped tarfiles in your - <span class="Pa">/emul/freebsd</span> directory (possibly omitting or - afterwards removing files you don't need), and you are done.</p> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The information about <span class="Ux">FreeBSD</span> - distributions may become outdated.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">February 10, 2018</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/compat_linux.8 4.html b/static/netbsd/man8/compat_linux.8 4.html deleted file mode 100644 index 803a4867..00000000 --- a/static/netbsd/man8/compat_linux.8 4.html +++ /dev/null @@ -1,161 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">COMPAT_LINUX(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">COMPAT_LINUX(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">compat_linux</code> — - <span class="Nd">setup procedure for running Linux binaries</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><span class="Ux">NetBSD</span> supports running Linux binaries. - This applies to aarch64, alpha, amd64, arm, i386, m68k, and powerpc systems - for now. Both the a.out and ELF binary formats are supported. Most programs - should work. <span class="Ux">NetBSD</span> aarch64 and amd64 can execute - both 32-bit and 64-bit Linux programs. Programs that will not work include - some that use i386-specific calls, such as enabling virtual 8086 mode. - Currently, sound is supported through OSSv3 compat.</p> -<p class="Pp">The Linux compatibility feature is active for kernels compiled - with the <code class="Dv">COMPAT_LINUX</code> option enabled. If support for - Linux a.out executables is desired, the <code class="Dv">EXEC_AOUT</code> - option should be enabled in addition to option - <code class="Dv">COMPAT_LINUX</code>. Similarly, if support for Linux 32-bit - and/or 64-bit ELF executables is desired, the - <code class="Dv">EXEC_ELF32</code> and/or <code class="Dv">EXEC_ELF64</code> - options (respectively) should be enabled in addition to - <code class="Dv">COMPAT_LINUX</code>. If sound support is desired, - <code class="Dv">COMPAT_OSSAUDIO</code> should be enabled.</p> -<p class="Pp">A lot of programs are dynamically linked. This means that you will - also need the Linux shared libraries that the program depends on, and the - runtime linker. Also, you will need to create a “shadow root” - directory for Linux binaries on your <span class="Ux">NetBSD</span> system. - This directory is named <span class="Pa">/emul/linux</span> or - <span class="Pa">/emul/linux32</span> for 32-bit emulation on 64-bit - systems. Any file operations done by Linux programs run under - <span class="Ux">NetBSD</span> will look in this directory first. So, if a - Linux program opens, for example, <span class="Pa">/etc/passwd</span>, - <span class="Ux">NetBSD</span> will first try to open - <span class="Pa">/emul/linux/etc/passwd</span>, and if that does not exist - open the ‘real’ <span class="Pa">/etc/passwd</span> file. It - is recommended that you install Linux packages that include configuration - files, etc under <span class="Pa">/emul/linux</span>, to avoid naming - conflicts with possible <span class="Ux">NetBSD</span> counterparts. Shared - libraries should also be installed in the shadow tree. Filenames that start - "/../" are only looked up in the real root.</p> -<p class="Pp">Generally, you will need to look for the shared libraries that - Linux binaries depend on only the first few times that you install a Linux - program on your <span class="Ux">NetBSD</span> system. After a while, you - will have a sufficient set of Linux shared libraries on your system to be - able to run newly imported Linux binaries without any extra work.</p> -<section class="Ss"> -<h2 class="Ss" id="Setting_up_shared_libraries"><a class="permalink" href="#Setting_up_shared_libraries">Setting - up shared libraries</a></h2> -<p class="Pp">Find the dependencies of a Linux binary using - <a class="Xr">readelf(1)</a>:</p> -<div class="Bd Pp Li"> -<pre>$ readelf -d ./runner | grep Shared - 0x00000001 (NEEDED) Shared library: [libstdc++.so.6] - 0x00000001 (NEEDED) Shared library: [libz.so.1] - 0x00000001 (NEEDED) Shared library: [libXxf86vm.so.1] - 0x00000001 (NEEDED) Shared library: [libGL.so.1] - 0x00000001 (NEEDED) Shared library: [libopenal.so.1] - 0x00000001 (NEEDED) Shared library: [libm.so.6] - 0x00000001 (NEEDED) Shared library: [librt.so.1] - 0x00000001 (NEEDED) Shared library: [libpthread.so.0] - 0x00000001 (NEEDED) Shared library: [libdl.so.2] - 0x00000001 (NEEDED) Shared library: [libcrypto.so.1.0.0] - 0x00000001 (NEEDED) Shared library: [libXext.so.6] - 0x00000001 (NEEDED) Shared library: [libX11.so.6] - 0x00000001 (NEEDED) Shared library: [libXrandr.so.2] - 0x00000001 (NEEDED) Shared library: [libGLU.so.1] - 0x00000001 (NEEDED) Shared library: [libssl.so.1.0.0] - 0x00000001 (NEEDED) Shared library: [libgcc_s.so.1] - 0x00000001 (NEEDED) Shared library: [libc.so.6]</pre> -</div> -<p class="Pp">For x86, you can simply install the openSUSE shared libraries - using the <span class="Pa">pkgsrc/emulators/suse131_*</span> or - <span class="Pa">pkgsrc/emulators/suse131_32_*</span> packages.</p> -<p class="Pp">For example, an application which requires - <span class="Pa">libcrypto.so.1.0.0</span>, - <span class="Pa">libXext.so.6</span>, and <span class="Pa">libGL.so.1</span> - will require <code class="Dv">openssl</code>, <code class="Dv">x11</code>, - and <code class="Dv">glx</code>, in addition to the - <code class="Dv">base</code> SUSE package.</p> -<p class="Pp">Otherwise, you may have to obtain shared libraries from another - Linux system, and copy them to e.g. - <span class="Pa">/emul/linux/lib64</span>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Setting_up_procfs"><a class="permalink" href="#Setting_up_procfs">Setting - up procfs</a></h2> -<p class="Pp">Some Linux binaries expect procfs to be mounted and that it - contains some Linux-specific extensions. If it's not the case, they behave - unexpectedly or even crash.</p> -<p class="Pp">Mount procfs on <span class="Ux">NetBSD</span> using following - command:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt>$ mount_procfs procfs /emul/linux/proc</dt> - <dd style="width: auto;"> </dd> -</dl> -</div> -<p class="Pp">You can also set up your system so that procfs is mounted - automatically on system boot, by putting an entry like the one below to - <span class="Pa">/etc/fstab</span>.</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt>procfs /emul/linux/proc procfs ro</dt> - <dd style="width: auto;"> </dd> -</dl> -</div> -<p class="Pp">Note: <a class="Xr">mount_procfs(8)</a> defaults to Linux flavored - procfs since <span class="Ux">NetBSD 5.0</span>. Ensure you do not mount - procfs with <var class="Ar">nolinux</var>.</p> -<p class="Pp">See <a class="Xr">mount_procfs(8)</a> for further information.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Setting_up_other_files"><a class="permalink" href="#Setting_up_other_files">Setting - up other files</a></h2> -<p class="Pp">Newer version of Linux use - <span class="Pa">/etc/nsswitch.conf</span> for network information, such as - NIS and DNS. You must create or get a valid copy of this file and put it in - <span class="Pa">/emul/linux/etc</span>.</p> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1> -<p class="Pp"><code class="Nm">compat_linux</code> is generally not enabled in - <code class="Dv">GENERIC</code> kernels for security reasons, but is - available as a module. It must be added to <a class="Xr">modules.conf(5)</a> - to be used. It will not be loaded automatically.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The information about Linux distributions will become - outdated.</p> -<p class="Pp">Absolute pathnames pointed to by symbolic links are only looked up - in the shadow root when the symbolic link itself was found by an absolute - pathname inside the shadow root. This is not consistent.</p> -<p class="Pp">Linux executables cannot handle directory offset cookies > 32 - bits. Should such an offset occur, you will see the message - “linux_getdents: dir offset too large for emulated program”. - Currently, this can only happen on NFS mounted file systems, mounted from - servers that return offsets with information in the upper 32 bits. These - errors should rarely happen, but can be avoided by mounting this file system - with offset translation enabled. See the <code class="Fl">-X</code> option - to <a class="Xr">mount_nfs(8)</a>. The <code class="Fl">-2</code> option to - <a class="Xr">mount_nfs(8)</a> will also have the desired effect, but is - less preferable.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">September 26, 2021</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/compat_netbsd32.8 4.html b/static/netbsd/man8/compat_netbsd32.8 4.html deleted file mode 100644 index 11755c86..00000000 --- a/static/netbsd/man8/compat_netbsd32.8 4.html +++ /dev/null @@ -1,109 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">COMPAT_NETBSD32(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">COMPAT_NETBSD32(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">compat_netbsd32</code> — - <span class="Nd">setup procedure for 32-bit compatibility on 64-bit - platforms</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <code class="Nm">compat_netbsd32</code> module allows - <span class="Ux">NetBSD</span>/sparc64 to run - <span class="Ux">NetBSD</span>/sparc executables, - <span class="Ux">NetBSD</span>/aarch64 to run - <span class="Ux">NetBSD</span>/arm executables, - <span class="Ux">NetBSD</span>/mips64 to run - <span class="Ux">NetBSD</span>/mips executables, and - <span class="Ux">NetBSD</span>/amd64 to run - <span class="Ux">NetBSD</span>/i386 executables. On - <span class="Ux">NetBSD</span>/mips64 the default userland is N32 which is a - handled by <code class="Nm">compat_netbsd32</code> framework, and 64-bit - binaries are handled similarly to the setup for 32-bit compatibility. It - also provides compatibility between OABI and EABI binaries on 32-bit - <span class="Ux">NetBSD</span>/arm ports.</p> -<p class="Pp">To use <code class="Nm">compat_netbsd32</code>, one must either - have <code class="Dv">COMPAT_NETBSD32</code> and - <code class="Dv">EXEC_ELF32</code> in the kernel, or load the - compat_netbsd32 and exec_elf32 kernel modules.</p> -<p class="Pp">Static executables typically need no additional setup. Dynamic - binaries require the dynamic linker plus shared libraries.</p> -<p class="Pp">Since <span class="Ux">NetBSD 5.0</span> the base system has - directly included support for 32-bit compatibility by installing 32-bit - libraries and dynamic linker into <span class="Pa">/usr</span>. This - includes compiler support for compiling 32-bit applications on platforms - where this is supported.</p> -<p class="Pp">For a.out compatibility, - <span class="Pa">/usr/libexec/ld.so</span> from a 32-bit distribution is - required to exist, and the a.out shared libraries must be found in - <span class="Pa">/emul/aout</span> as normal for a.out compatibility. For - 32-bit (64-bit on <span class="Ux">NetBSD</span>/mips64) ELF compatibility, - the relevant <span class="Pa">/usr/libexec/ld.elf_so</span> needs to be - found in</p> -<table class="Bl-column Bd-indent"> - <tr id="Port"> - <td><a class="permalink" href="#Port"><b class="Sy">Port</b></a></td> - <td><a class="permalink" href="#Target"><b class="Sy" id="Target">Target</b></a></td> - <td><a class="permalink" href="#Path"><b class="Sy" id="Path">Path</b></a></td> - </tr> - <tr id="amd64"> - <td><a class="permalink" href="#amd64"><code class="Li">amd64</code></a></td> - <td>i386</td> - <td>/usr/libexec/ld.elf_so-i386</td> - </tr> - <tr id="sparc64"> - <td><a class="permalink" href="#sparc64"><code class="Li">sparc64</code></a></td> - <td>sparc</td> - <td>/usr/libexec/ld.elf_so-sparc</td> - </tr> - <tr id="mips64"> - <td><a class="permalink" href="#mips64"><code class="Li">mips64</code></a></td> - <td>O32</td> - <td>/usr/libexec/ld.elf_so-o32</td> - </tr> - <tr id="mips64~2"> - <td><a class="permalink" href="#mips64~2"><code class="Li">mips64</code></a></td> - <td>N64</td> - <td>/usr/libexec/ld.elf_so-64</td> - </tr> - <tr id="powerpc64"> - <td><a class="permalink" href="#powerpc64"><code class="Li">powerpc64</code></a></td> - <td>powerpc</td> - <td>/usr/libexec/ld.elf_so-powerpc</td> - </tr> - <tr id="arm64"> - <td><a class="permalink" href="#arm64"><code class="Li">arm64</code></a></td> - <td>eabi</td> - <td>/usr/libexec/ld.elf_so-eabi</td> - </tr> -</table> -<p class="Pp">Note that the kernel handles rewriting the built-in ELF - interpreter to the above path.</p> -<p class="Pp">Before <span class="Ux">NetBSD 5.0</span> all of these files - needed to be placed under <span class="Pa">/emul/netbsd32</span>.</p> -<p class="Pp">The shared libraries for a.out binaries do not live under the - <span class="Pa">/emul/netbsd32</span> directory, but under the - <span class="Pa">/emul/aout</span> directory, where the a.out dynamic linker - will find them.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">A list of things which fail to work in compatibility mode should - be here.</p> -<p class="Pp"><a class="Xr">aio(3)</a> is not supported.</p> -<p class="Pp">Some <a class="Xr">ioctl(2)</a> commands are not supported, - including <a class="Xr">drm(4)</a>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">January 17, 2019</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/compat_sunos.8 4.html b/static/netbsd/man8/compat_sunos.8 4.html deleted file mode 100644 index 4acb2888..00000000 --- a/static/netbsd/man8/compat_sunos.8 4.html +++ /dev/null @@ -1,92 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">COMPAT_SUNOS(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">COMPAT_SUNOS(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">compat_sunos</code> — - <span class="Nd">setup procedure for m68k, sparc and sparc64 - architectures</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><span class="Ux">NetBSD</span>/sparc64, - <span class="Ux">NetBSD</span>/sparc and some of the - <span class="Ux">NetBSD</span>/m68k architectures can run SunOS executables. - Most executables will work.</p> -<p class="Pp" id="ioctl">The exceptions include programs that use the SunOS kvm - library, and various system calls, - <a class="permalink" href="#ioctl"><code class="Fn">ioctl</code></a>()'s, or - kernel semantics that are difficult to emulate. The number of reasons why a - program might fail to work is (thankfully) longer than the number of - programs that fail to run.</p> -<p class="Pp">Static executables will normally run without any extra setup. This - procedure details the directories and files that must be set up to allow - dynamically linked executables to work.</p> -<p class="Pp">The files you need are on your SunOS machine. You need to worry - about the legal issues of ensuring that you have a right to use the required - files on your machine. On your <span class="Ux">NetBSD</span> machine, do - the following:</p> -<ol class="Bl-enum Bd-indent"> - <li id="mkdir"><a class="permalink" href="#mkdir"><code class="Li">mkdir -p - /emul/sunos/usr/lib /emul/sunos/usr/5lib</code></a></li> - <li id="cp"><a class="permalink" href="#cp"><code class="Li">cp - SunOS:/usr/lib/lib*.so.*.* NetBSD:/emul/sunos/usr/lib</code></a></li> - <li id="cp~2"><a class="permalink" href="#cp~2"><code class="Li">cp - SunOS:/usr/5lib/lib*.so.*.* NetBSD:/emul/sunos/usr/5lib</code></a></li> - <li id="cp~3"><a class="permalink" href="#cp~3"><code class="Li">cp - SunOS:/usr/lib/ld.so NetBSD:/emul/sunos/usr/lib/ld.so</code></a></li> - <li>If you ever expect to use YP, you will want to create a link: - <div class="Bd Li"> - <pre>ln -s /var/run/ypbind.lock /etc/ypbind.lock</pre> - </div> - </li> -</ol> -<p class="Pp">Alternatively, you can use an NFS mount to accomplish the same - effect. On your <span class="Ux">NetBSD</span> machine, do the - following:</p> -<ol class="Bl-enum Bd-indent"> - <li id="mkdir~2"><a class="permalink" href="#mkdir~2"><code class="Li">mkdir - -p /emul/sunos/usr</code></a></li> - <li id="mount"><a class="permalink" href="#mount"><code class="Li">mount - SunOS:/usr /emul/sunos/usr</code></a></li> -</ol> -<p class="Pp">This will place the SunOS libraries on your - <span class="Ux">NetBSD</span> machine in a location where the SunOS - compatibility code will look for first, where they do not conflict with the - standard libraries.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="NOTES"><a class="permalink" href="#NOTES">NOTES</a></h1> -<p class="Pp">When using <code class="Nm">compat_sunos</code> on - <span class="Ux">NetBSD</span>/sparc64, the - <code class="Dv">COMPAT_NETBSD32</code> option must also be used.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">A list of things which fail to work in compatibility mode should - be here.</p> -<p class="Pp">SunOS executables can not handle directory offset cookies > 32 - bits. Should such an offset occur, you will see the message - “sunos_getdents: dir offset too large for emulated program”. - Currently, this can only happen on NFS mounted filesystems, mounted from - servers that return offsets with information in the upper 32 bits. These - errors should rarely happen, but can be avoided by mounting this filesystem - with offset translation enabled. See the <code class="Fl">-X</code> option - to <a class="Xr">mount_nfs(8)</a>. The <code class="Fl">-2</code> option to - <a class="Xr">mount_nfs(8)</a> will also have the desired effect, but is - less preferable.</p> -<p class="Pp">The <span class="Ux">NetBSD</span>/sparc64 support is less - complete than the other ports.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">February 3, 2001</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/compat_ultrix.8 4.html b/static/netbsd/man8/compat_ultrix.8 4.html deleted file mode 100644 index f4275366..00000000 --- a/static/netbsd/man8/compat_ultrix.8 4.html +++ /dev/null @@ -1,106 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">COMPAT_ULTRIX(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">COMPAT_ULTRIX(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">compat_ultrix</code> — - <span class="Nd">setup procedure for ULTRIX compatibility on MIPS and VAX - architectures</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><span class="Ux">NetBSD</span>/mips and - <span class="Ux">NetBSD</span>/vax architectures can run Risc ULTRIX and VAX - ULTRIX executables, respectively. However, you have to worry about the legal - issues of ensuring that you have a right to use any ULTRIX binaries on your - machine.</p> -<p class="Pp" id="ioctl">Most executables will work. The exceptions include - programs that use proprietary, ULTRIX-specific features (LAT, CI support, - DECnet support) and various system calls, - <a class="permalink" href="#ioctl"><code class="Fn">ioctl</code></a>()'s, or - ULTRIX kernel semantics that are difficult to emulate (e.g. ULTRIX - packetfilter) or buggy (e.g. ULTRIX NIS).</p> -<p class="Pp">All ULTRIX executables are static, so no shared libraries are - required for ULTRIX compatibility. However, ULTRIX is based on a - <span class="Ux">4.3BSD</span> alpha release. ULTRIX commands and libraries - are often much older than their <span class="Ux">NetBSD</span> or even SunOS - 4.x equivalents, and may require incompatible configuration files.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYSTEM_CONFIGURATION_FILES"><a class="permalink" href="#SYSTEM_CONFIGURATION_FILES">SYSTEM - CONFIGURATION FILES</a></h1> -<p class="Pp">Set up <span class="Pa">resolv.conf</span> and - <span class="Pa">svc.conf</span> as below:</p> -<p class="Pp"></p> -<div class="Bd-indent"> -<dl class="Bl-tag Bl-compact"> - <dt># mkdir -p /emul/ultrix/etc</dt> - <dd> - <br/> - </dd> - <dt># cd /emul/ultrix/etc</dt> - <dd> - <br/> - </dd> - <dt># egrep 'domain|nameserver' /etc/resolv.conf > ./resolv.conf</dt> - <dd> - <br/> - </dd> - <dt># cp -p /usr/share/examples/emul/ultrix/etc/* ./</dt> - <dd style="width: auto;"> </dd> -</dl> -</div> -<section class="Ss"> -<h2 class="Ss" id="/etc/resolv.conf"><a class="permalink" href="#/etc/resolv.conf">/etc/resolv.conf</a></h2> -<p class="Pp">The ULTRIX resolver library only understands - <a class="permalink" href="#domain"><b class="Sy" id="domain">domain</b></a> - and - <a class="permalink" href="#nameserver"><b class="Sy" id="nameserver">nameserver</b></a> - lines in <a class="Xr">resolv.conf(5)</a>. You should create a copy of - <span class="Pa">/etc/resolv.conf</span> containing only those commands and - put it in <span class="Pa">/emul/ultrix/etc/resolv.conf</span>. Note that - the domain search order used by ULTRIX executables may not be the same as - native binaries; there is no good way around this.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="/etc/svc.conf"><a class="permalink" href="#/etc/svc.conf">/etc/svc.conf</a></h2> -<p class="Pp">ULTRIX uses <span class="Pa">/etc/svc.conf</span> to select an - ordered search of NIS, Hesiod, or local flat-file mappings. You should - create an <span class="Pa">/emul/ultrix/etc/svc.conf</span> specifying - either local files or bind (DNS) lookups for all ULTRIX name services.</p> -</section> -</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">resolv.conf(5)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">RISC ULTRIX NIS (YP) is known to not work. The ULTRIX NIS - libraries have a consistent endian-ness bug. ULTRIX NIS client will not - inter-operate with the <span class="Ux">NetBSD</span> - <a class="Xr">ypbind(8)</a> process. The only workaround is to use - <span class="Pa">/etc/svc.conf</span> to disable NIS (YP).</p> -<p class="Pp">The ndbm hashed-password file used by ULTRIX are incompatible with - the db hashed-password file used by <span class="Ux">NetBSD</span>. There is - no good solution for this. NIS would be a good one, if ULTRIX NIS - worked.</p> -<p class="Pp">The API used by Xservers to talk to the kernel is currently - compatible with ULTRIX 4.1. An implementation of the ULTRIX 4.2 Xws - interface (used by X11R6) is in progress.</p> -<p class="Pp">A complete list of things which fail to work in ULTRIX - compatibility mode should be added here.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">January 16, 1999</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/creds_msdos.8 4.html b/static/netbsd/man8/creds_msdos.8 4.html deleted file mode 100644 index a9d37cce..00000000 --- a/static/netbsd/man8/creds_msdos.8 4.html +++ /dev/null @@ -1,99 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">CREDS_MSDOS(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">CREDS_MSDOS(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">creds_msdos</code> — - <span class="Nd">automatically add login credentials from MS-DOS - partition</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">creds_msdos</code></td> - <td><var class="Ar">start</var></td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <code class="Nm">creds_msdos</code> rc.d script allows - automatic addition of login credentials during boot using a special file - found on the MS-DOS partition of a bootable image. This script is not - distributed with the normal system and is only included with pre-installed - bootable images. The goal is to allow remote access of the system without - having to edit the primary root file system (which may not be accessible - from the host the image is being written from), but place this information - in the MS-DOS partition that most platforms can easily access.</p> -<p class="Pp">Typically, an installable image (such as - <span class="Pa">arm64.img</span>) is written to an SD card or similar - media, and has both a native FFS partition as well as an MS-DOS partition - for booting. If this script is enabled and has been pointed at the boot - partition it will inspect the file <span class="Pa">creds.txt</span> for any - credentials to be added to the system.</p> -<p class="Pp">The following list gives the supported options in the credentials - files. In all cases <var class="Ar">user</var> is the username to be - created, and the user will be added to the - ‘<code class="Li">wheel</code>’ group.</p> -<dl class="Bl-tag"> - <dt id="sshkeyfile"><a class="permalink" href="#sshkeyfile"><code class="Ic">sshkeyfile</code></a> - <var class="Ar">user</var> <var class="Ar">keyfile</var></dt> - <dd>Look for the <var class="Ar">keyfile</var> in the MS-DOS boot partition - and merge ssh keys from this file into user's - <span class="Pa">~/.ssh/authorized_keys</span> file.</dd> - <dt id="sshkey"><a class="permalink" href="#sshkey"><code class="Ic">sshkey</code></a> - <var class="Ar">user</var> <var class="Ar">keystring</var></dt> - <dd>Add the <var class="Ar">keystring</var> to the user's - <span class="Pa">~/.ssh/authorized_keys</span> file.</dd> - <dt id="useraddpwhash"><a class="permalink" href="#useraddpwhash"><code class="Ic">useraddpwhash</code></a> - <var class="Ar">user</var> <var class="Ar">pwhash</var></dt> - <dd>Use <var class="Ar">pwhash</var> as the users's password hash.</dd> - <dt id="useradd"><a class="permalink" href="#useradd"><code class="Ic">useradd</code></a> - <var class="Ar">user</var> <var class="Ar">password</var></dt> - <dd>Use <var class="Ar">password</var> as the users's unencrypted raw password - that will be hashed. - <p class="Pp" id="not">This method is - <a class="permalink" href="#not"><i class="Em">not recommended</i></a> - as it leaves unencrypted passwords around until such time that the - script runs. If this method is used then the - <span class="Pa">creds.txt</span> file will be shredded and deleted - using ‘<code class="Li">rm -P</code>’ after the - credentials are updated.</p> - </dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1> -<p class="Pp"><span class="Pa">/boot/creds.txt</span></p> -</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">pwhash(1)</a>, <a class="Xr">rm(1)</a>, - <a class="Xr">ssh(1)</a>, <a class="Xr">ssh_config(5)</a>, - <a class="Xr">mount_msdos(8)</a>, <a class="Xr">sshd(8)</a>, - <a class="Xr">useradd(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">creds_msdos</code> script appeared in - <span class="Ux">NetBSD 9.0</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp"><span class="An">Matthew R. Green</span> - <<a class="Mt" href="mailto:mrg@eterna23.net">mrg@eterna23.net</a>>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">June 10, 2019</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/diskless.8 4.html b/static/netbsd/man8/diskless.8 4.html deleted file mode 100644 index 0ff9e35e..00000000 --- a/static/netbsd/man8/diskless.8 4.html +++ /dev/null @@ -1,542 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">DISKLESS(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">DISKLESS(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">diskless</code> — <span class="Nd">booting - a system over the network</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The ability to boot a system over the network is useful for two - kinds of systems:</p> -<dl class="Bl-tag"> - <dt id="diskless"><a class="permalink" href="#diskless"><i class="Em">diskless</i></a></dt> - <dd>a system with no attached mass storage media to boot or run from (e.g. a - network computer).</dd> - <dt id="dataless"><a class="permalink" href="#dataless"><i class="Em">dataless</i></a></dt> - <dd>a system with a hard drive that only contains system and application - software, and user data is mounted over the network from a central - server.</dd> -</dl> -<p class="Pp">It can also be done as a temporary measure while repairing or - re-installing file systems on a local disk. This capability is necessarily - platform dependent because of its dependence on system firmware support; not - all platforms supported by <span class="Ux">NetBSD</span> are capable of - being network booted.</p> -<p class="Pp">The protocols used to obtain a network address (e.g. an IP host - address), include, but are not limited to:</p> -<p class="Pp"></p> -<div class="Bd-indent"> -<dl class="Bl-tag Bl-compact"> - <dt>RARP</dt> - <dd>Reverse Address Resolution Protocol (ARP)</dd> - <dt>DHCP</dt> - <dd>Dynamic Host Configuration Protocol</dd> - <dt>BOOTP</dt> - <dd>Bootstrap Protocol</dd> -</dl> -</div> -<p class="Pp">This information can also be derived from non-volatile RAM or by a - transform of a network interface (e.g. Ethernet) MAC address.</p> -<p class="Pp">The protocols used to load a <span class="Ux">NetBSD</span> kernel - over a network include, but are not limited to:</p> -<p class="Pp"></p> -<div class="Bd-indent"> -<dl class="Bl-tag Bl-compact"> - <dt>TFTP</dt> - <dd>Trivial File Transfer Protocol</dd> - <dt>NFS</dt> - <dd>Sun Network File System</dd> - <dt>RMP</dt> - <dd>HP Remote Maintenance Protocol</dd> - <dt>MOP</dt> - <dd>DEC Maintenance Operations Protocol</dd> -</dl> -</div> -<p class="Pp">Derivation of the filename of the secondary bootstrap program can - be done by a transform of a network interface MAC address (or other protocol - address), or provided by a server as with BOOTP, and DHCP. How this is done - is platform dependent; see <a class="Xr">boot(8)</a>.</p> -<p class="Pp">The <span class="Ux">NetBSD</span> kernel doesn't care how it gets - loaded and started. The protocols used to boot - <span class="Ux">NetBSD</span> can be completely different from the ones - that <span class="Ux">NetBSD</span> uses operationally, i.e. you can netboot - the system using HP RMP and the <span class="Ux">NetBSD</span> kernel can - use IP to communicate after bootstrap.</p> -<p class="Pp">There is no standard way to pass all the required information from - a boot loader to an operating system kernel, so the - <span class="Ux">NetBSD</span> kernel usually has to recapitulate the same - (or similar) protocol exchanges over the network to obtain a network - address, determine which servers to use, and so on. - <span class="Ux">NetBSD</span> supports obtaining this information from - RARP, BOOTP, DHCP, and Sun RPC "bootparams". See - <a class="Xr">options(4)</a> for a list of methods that can be compiled into - a <span class="Ux">NetBSD</span> kernel.</p> -<p class="Pp"><span class="Ux">NetBSD</span> only supports the Sun Network File - System (NFS) for mounting its root file system over a network. - <span class="Ux">NetBSD</span> can use any local mass storage device for - which it has a driver, after bootstrap, even if that device is not supported - by the system's firmware for booting.</p> -<p class="Pp"><b class="Sy">N.B.</b> DHCP is essentially a series of extensions - to BOOTP; the <span class="Ux">NetBSD</span> <a class="Xr">dhcpd(8)</a> is - capable of responding to both kinds of protocol requests.</p> -<p class="Pp">In the majority of configurations, network boot servers and - clients are attached to the same LAN so that broadcast queries from the - clients can be heard by the servers. Unless specially configured, routers - block broadcasts from propagating from LAN to LAN; some routers can be - configured to "forward" broadcast BOOTP packets to another LAN - attached to that router, which permits a server on that remote LAN to - respond to the client's broadcast query.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="OPERATION"><a class="permalink" href="#OPERATION">OPERATION</a></h1> -<p class="Pp">When booting a system over the network, there are three phases of - interaction between client and server:</p> -<p class="Pp"></p> -<ol class="Bl-enum Bl-compact"> - <li>The system firmware (or stage-1 bootstrap) loads a boot program.</li> - <li>The boot program loads a <span class="Ux">NetBSD</span> kernel.</li> - <li>The <span class="Ux">NetBSD</span> kernel performs an NFS mount of the - root file system.</li> -</ol> -<p class="Pp">Each of these phases is described in further detail below.</p> -<section class="Ss"> -<h2 class="Ss" id="1._loading_a_boot_program"><a class="permalink" href="#1._loading_a_boot_program">1. - loading a boot program</a></h2> -<p class="Pp">In phase 1, the system firmware loads a boot program. Firmware - designs vary widely, so this phase is inherently machine-specific. Some - examples:</p> -<p class="Pp">DEC Alpha systems use BOOTP to determine the client's IP address - and then use TFTP to load a secondary bootstrap program from the server and - filename specified in the BOOTP reply. DEC Alpha systems can also use MOP to - load a program to run the system.</p> -<p class="Pp">Sun systems use RARP to determine the client's IP address, - transform that address to a hexadecimal string to form the filename of the - secondary boot program, and then use TFTP to download the boot program from - the server that sent the RARP reply.</p> -<p class="Pp">HP 300-series systems use the HP RMP to download a boot - program.</p> -<p class="Pp">Typical personal computers may load a network boot program either - from diskette or from a PROM on a Network Interface Card (NIC). Some - BIOS<span class="No">es</span> support booting from a network interface.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="2._loading_a_kernel"><a class="permalink" href="#2._loading_a_kernel">2. - loading a kernel</a></h2> -<p class="Pp">In phase 2, the secondary boot program loads a kernel. Operation - in this phase depends on the design of the boot program. A secondary - bootstrap program that uses RARP and Sun RPC BOOTPARAMS typically does the - following:</p> -<p class="Pp"></p> -<ol class="Bl-enum Bl-compact"> - <li>gets the client IP address using RARP.</li> - <li>gets the client name and server IP address by broadcasting an RPC / - BOOTPARAMS / WHOAMI request with the client IP address.</li> - <li>gets the server path for this client's root using an RPC / BOOTPARAMS / - GETFILE request with the client name.</li> - <li>gets the root file handle by calling <a class="Xr">mountd(8)</a> with the - server path for the client root file system.</li> - <li id="lookup">gets the kernel file handle by calling NFS - <a class="permalink" href="#lookup"><code class="Fn">lookup</code></a>() - on the root file handle.</li> - <li>loads the kernel using NFS read calls on the kernel file handle.</li> - <li>transfers control to the kernel entry point.</li> -</ol> -<p class="Pp">A secondary bootstrap program that uses BOOTP and/or DHCP - typically does the following:</p> -<p class="Pp"></p> -<ol class="Bl-enum Bl-compact"> - <li>query for the client's bootstrap parameters. The response must include the - client's IP address, server's IP address, an NFS root path, and a filename - to load the <span class="Ux">NetBSD</span> kernel from.</li> - <li>gets the root file handle by calling <a class="Xr">mountd(8)</a> with the - server path for the client root file system.</li> - <li id="lookup~2">gets the kernel file handle by calling NFS - <a class="permalink" href="#lookup~2"><code class="Fn">lookup</code></a>() - on the root file handle.</li> - <li>loads the kernel using NFS read calls on the kernel file handle.</li> - <li>transfers control to the kernel entry point.</li> -</ol> -</section> -<section class="Ss"> -<h2 class="Ss" id="3._NFS_mounting_the_root_file_system"><a class="permalink" href="#3._NFS_mounting_the_root_file_system">3. - NFS mounting the root file system</a></h2> -<p class="Pp">In phase 3, the kernel performs an NFS mount of the root file - system. The kernel repeats much of the work done by the boot program because - there is no standard way for the boot program to pass the information it - gathered on to the kernel.</p> -<p class="Pp">In general, the GENERIC kernel <a class="Xr">config(1)</a> file - for any particular architecture will specify compile-time options to use the - same protocol used by the secondary boot program for that architecture. A - <span class="Ux">NetBSD</span> kernel can be compiled to use any of BOOTP, - DHCP, or Sun RPC BOOTPARAMS; see <a class="Xr">options(4)</a>.</p> -<p class="Pp">The procedure typically used by the kernel is as follows:</p> -<p class="Pp"></p> -<ol class="Bl-enum Bl-compact"> - <li>The kernel finds a boot server using the same procedures as described - above to determine the client's IP address, an NFS server, etc.</li> - <li>The kernel gets the NFS file handle for root using the same procedure as - described above.</li> - <li id="getattr">The kernel calls the NFS - <a class="permalink" href="#getattr"><code class="Fn">getattr</code></a>() - function to get the last-modified time of the root directory, and uses it - to check the system clock.</li> -</ol> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="SERVER_CONFIGURATION"><a class="permalink" href="#SERVER_CONFIGURATION">SERVER - CONFIGURATION</a></h1> -<p class="Pp">Before a client can bootstrap over the network, its server must be - configured. Each daemon that implements these protocols must be set up so - that it can answer queries from the clients. Some of these daemons are - invoked as packets come in, by <a class="Xr">inetd(8)</a>, and some must run - independently, started from <span class="Pa">/etc/rc</span>; see - <a class="Xr">rc.conf(5)</a>.</p> -<table class="Bl-column Bd-indent"> - <tr id="Protocol"> - <td><a class="permalink" href="#Protocol"><b class="Sy">Protocol</b></a></td> - <td><a class="permalink" href="#Program"><b class="Sy" id="Program">Program</b></a></td> - <td><a class="permalink" href="#Startup"><b class="Sy" id="Startup">Startup</b></a></td> - </tr> - <tr> - <td>RARP</td> - <td>rarpd</td> - <td><a class="Xr">rc.conf(5)</a></td> - </tr> - <tr> - <td>DHCP</td> - <td>dhcpd</td> - <td><a class="Xr">rc.conf(5)</a></td> - </tr> - <tr> - <td>BOOTP</td> - <td>bootpd</td> - <td><a class="Xr">inetd.conf(5)</a></td> - </tr> - <tr> - <td>TFTP</td> - <td>tftpd</td> - <td><a class="Xr">inetd.conf(5)</a></td> - </tr> - <tr> - <td>Sun RPC</td> - <td>rpcbind</td> - <td><a class="Xr">rc.conf(5)</a></td> - </tr> - <tr> - <td>Sun RPC</td> - <td>rpc.bootparamd</td> - <td><a class="Xr">rc.conf(5)</a></td> - </tr> - <tr> - <td>Sun NFS</td> - <td>mountd</td> - <td><a class="Xr">rc.conf(5)</a></td> - </tr> - <tr> - <td>Sun NFS</td> - <td>nfsiod</td> - <td><a class="Xr">rc.conf(5)</a></td> - </tr> - <tr> - <td>HP RMP</td> - <td>rbootd</td> - <td><a class="Xr">rc.conf(5)</a></td> - </tr> -</table> -<p class="Pp"><b class="Sy">N.B.</b> DHCP is essentially a series of extensions - to BOOTP; the <span class="Ux">NetBSD</span> <a class="Xr">dhcpd(8)</a> is - capable of responding to both kinds of protocol requests. Since they both - bind to the same UDP port, only one may be run on a given server.</p> -<p class="Pp">In the following examples, the client's hostname is - <b class="Sy">myclient</b>; the server is <b class="Sy">myserver</b>, and - the addresses are all fictional. In these examples the hostnames may be - Fully Qualified Domain Names (FQDN, e.g. "myclient.mydomain.com") - provided that they are used consistently.</p> -<section class="Ss"> -<h2 class="Ss" id="RARP"><a class="permalink" href="#RARP">RARP</a></h2> -<p class="Pp">For clients that use RARP to obtain their IP address, an entry - must be added for each client to <span class="Pa">/etc/ethers</span> with - the client's Ethernet MAC address and Internet hostname:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent Li"> -<pre>8:0:20:7:c5:c7 myclient</pre> -</div> -<p class="Pp">This will be used by <a class="Xr">rarpd(8)</a> to reply to - queries from the clients. There must be one entry per client system.</p> -<p class="Pp">A client system's Ethernet MAC address is often printed on the - system case, or on a chip on its motherboard, or on the NIC. If not, - "sniffing" the network with <a class="Xr">tcpdump(8)</a> when the - client is powered-on should reveal its Ethernet MAC address.</p> -<p class="Pp">Each client system that uses RARP must have its own, unique IP - address assigned to it. Assign an IP address for myclient in your - <span class="Pa">/etc/hosts</span> file, or in the master file for your DNS - zone. For <span class="Pa">/etc/hosts</span> the entry should look like:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent Li"> -<pre>192.197.96.12 myclient</pre> -</div> -</section> -<section class="Ss"> -<h2 class="Ss" id="DHCP/BOOTP"><a class="permalink" href="#DHCP/BOOTP">DHCP/BOOTP</a></h2> -<p class="Pp">The <span class="Ux">NetBSD</span> DHCP server - <a class="Xr">dhcpd(8)</a> was developed by the Internet Software Consortium - (<a class="Lk" href="http://www.isc.org/">ISC</a>).</p> -<p class="Pp">DHCP can provide a wide range of information to a requesting - client; the key data for bootstrapping a diskless client are:</p> -<p class="Pp"></p> -<ol class="Bl-enum Bl-compact"> - <li>an IP address</li> - <li>a subnet mask</li> - <li>a TFTP server address for loading the secondary bootstrap and the - <span class="Ux">NetBSD</span> kernel</li> - <li>a filename of the secondary bootstrap</li> - <li>an NFS server address for the client's file system</li> - <li>the client's root file system path, to be NFS mounted.</li> -</ol> -<p class="Pp">An example for <span class="Pa">/etc/dhcpd.conf</span></p> -<div class="Bd Pp Bd-indent Li"> -<pre>host myclient { - hardware ethernet 8:0:20:7:c5:c7; - fixed-address myclient; # client's assigned IP address - filename "myclient.netboot"; # secondary bootstrap - next-server myserver; # TFTP server for secondary bootstrap - option swap-server myserver; # NFS server for root filesystem - option root-path "/export/myclient/root"; -}</pre> -</div> -<p class="Pp" id="host">That - <a class="permalink" href="#host"><b class="Sy">host</b></a> declaration - goes inside a - <a class="permalink" href="#subnet"><b class="Sy" id="subnet">subnet</b></a> - declaration, which gives parameters for all hosts on the subnet that will be - using DHCP, such as the "routers" (the default route), - "subnet-mask", "broadcast-address", - "domain-name-servers", etc. See <a class="Xr">dhcpd.conf(5)</a> - for details. In that example, <b class="Sy">myclient</b> has an assigned IP - address.</p> -<p class="Pp">The DHCP parameters required for network bootstrapping a system - will vary from platform to platform, as dictated by each system's firmware. - In particular, because DHCP is extensible, some hardware vendors have - specified DHCP options to return information to requesting clients that are - specific to that platform. Please see your platform's - <a class="Xr">boot(8)</a> for details.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="TFTP"><a class="permalink" href="#TFTP">TFTP</a></h2> -<p class="Pp">If booting a Sun system, or other system that expects to use TFTP, - ensure that <a class="Xr">inetd(8)</a> is configured to run - <a class="Xr">tftpd(8)</a>. The <a class="Xr">tftpd(8)</a> server should be - set up to serve the directory <span class="Pa">/tftpboot</span>.</p> -<p class="Pp">If booting a SPARC system, install a copy of the appropriate - diskless secondary boot loader (such as - <span class="Pa">/usr/mdec/boot</span> or - <span class="Pa">ofwboot.net</span>) in the - <span class="Pa">/tftpboot</span> directory. Make a link such that the boot - program is accessible by a filename composed of the client's IP address in - hexadecimal, a dot, and the architecture name (all upper case). For - example:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent Li"> -<pre># cd /tftpboot -# ln -s boot C0C5600C.SUN4</pre> -</div> -<p class="Pp">For a Sun-3 or UltraSPARC system, the filename would be just - C0C5600C (these systems' firmware does not append the architecture name). - The name used is architecture dependent, it simply has to match what the - booting client's system firmware wishes it to be.</p> -<p class="Pp">If the client's system firmware fails to fetch the expected file, - <a class="Xr">tcpdump(8)</a> can be used to discover which filename the - client is requesting. Also, examination of <a class="Xr">tftpd(8)</a> log - entries (typically in <span class="Pa">/var/log/messages</span>) should show - whether the server is hearing the client system, and what filename the - client is asking for.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="HP_RMP"><a class="permalink" href="#HP_RMP">HP RMP</a></h2> -<p class="Pp">If booting an HP 300-series system, ensure that - <span class="Pa">/etc/rbootd.conf</span> is configured properly to transfer - the boot program to the client. An entry might look like this:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent Li"> -<pre>08:00:09:01:23:E6 SYS_UBOOT # myclient</pre> -</div> -<p class="Pp">The secondary bootstrap program for an HP 300-series system - <span class="Pa">SYS_UBOOT</span> (which may be called - <span class="Pa">uboot.lif</span> before installation) must be installed in - the directory <span class="Pa">/usr/mdec/rbootd</span>.</p> -<p class="Pp">See the <a class="Xr">rbootd(8)</a> manual page for more - information.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Sun_RPC_BOOTPARAMS"><a class="permalink" href="#Sun_RPC_BOOTPARAMS">Sun - RPC BOOTPARAMS</a></h2> -<p class="Pp">Add <b class="Sy">myclient</b> to the bootparams database in - <span class="Pa">/etc/bootparams</span>:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent Li"> -<pre>myclient root=myserver:/export/myclient/root \ - swap=myserver:/export/myclient/root/swap \ - dump=myserver:/export/myclient/root/swap</pre> -</div> -<p class="Pp">and ensure that <a class="Xr">rpc.bootparamd(8)</a> and - <a class="Xr">rpcbind(8)</a> are running. Both <b class="Sy">myclient</b> - and <b class="Sy">myserver</b> must have IP addresses in the DNS or - <span class="Pa">/etc/hosts</span>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Diskless_Client_File_Systems"><a class="permalink" href="#Diskless_Client_File_Systems">Diskless - Client File Systems</a></h2> -<p class="Pp">Build the swap file for <b class="Sy">myclient</b> on the NFS - server:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent Li"> -<pre># cd /export/myclient/root -# dd if=/dev/zero of=swap bs=16k count=1024</pre> -</div> -<p class="Pp">This creates a 16 megabyte swap file.</p> -<p class="Pp">Populate <b class="Sy">myclient</b><span class="No">'s</span> root - file system on the NFS server. How this is done depends on the client - architecture and the version of the <span class="Ux">NetBSD</span> - distribution. It can be as simple as copying and modifying the server's root - file system, or unpack a complete <span class="Ux">NetBSD</span> binary - distribution for the appropriate platform.</p> -<p class="Pp">If the NFS server is going to support multiple different - architectures (e.g. Alpha, PowerPC, SPARC, MIPS), then it is important to - think carefully about how to lay out the NFS server's exported file systems, - to share what can be shared (e.g. text files, configuration files, user home - directories), and separate that which is distinct to each architecture (e.g. - binary executables, libraries).</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="NFS"><a class="permalink" href="#NFS">NFS</a></h2> -<p class="Pp">Export the client-populated file systems on the NFS server in - <span class="Pa">/etc/exports</span>:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent Li"> -<pre>/usr -ro myclient -# for SunOS: -# /export/myclient -rw=myclient,root=myclient -# for NetBSD: -/export/myclient -maproot=root -alldirs myclient</pre> -</div> -<p class="Pp">If the server and client are of the same architecture, then the - client can share the server's <span class="Pa">/usr</span> file system (as - is done above). If not, you must build a properly fleshed out - <span class="Pa">/usr</span> partition for the client in some other part of - the server's file system, to serve to the client.</p> -<p class="Pp">If your server is a SPARC, and your client a Sun-3, you might - create and fill <span class="Pa">/export/usr.sun3</span> and then use the - following <span class="Pa">/etc/exports</span> lines:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent Li"> -<pre>/export/usr.sun3 -ro myclient -/export/myclient -rw=myclient,root=myclient</pre> -</div> -<p class="Pp">Of course, in either case you will have to have an NFS server - running on the server side.</p> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="CLIENT_CONFIGURATION"><a class="permalink" href="#CLIENT_CONFIGURATION">CLIENT - CONFIGURATION</a></h1> -<p class="Pp">Copy and customize at least the following files in - <span class="Pa">/export/myclient/root</span>:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent Li"> -<pre># cd /export/myclient/root/etc -# vi fstab -# cp /etc/hosts hosts -# echo 'hostname="myclient"' >> rc.conf -# echo "inet 192.197.96.12" > ifconfig.le0</pre> -</div> -<p class="Pp">Note that "le0" above should be replaced with the name - of the network interface that the client will use for booting; the network - interface name is device dependent in <span class="Ux">NetBSD</span>.</p> -<p class="Pp">Correct the critical mount points and the swap file in the - client's <span class="Pa">/etc/fstab</span> (which will be - <span class="Pa">/export/myclient/root/etc/fstab</span>) i.e.</p> -<p class="Pp"></p> -<div class="Bd Bd-indent Li"> -<pre>myserver:/export/myclient/root / nfs rw 0 0 -myserver:/usr /usr nfs rw 0 0 -/swap none swap sw 0 0</pre> -</div> -<p class="Pp" id="must">Note, you - <a class="permalink" href="#must"><i class="Em">must</i></a> specify the - swap file in <span class="Pa">/etc/fstab</span> or it will not be used! See - <a class="Xr">swapctl(8)</a>.</p> -<p class="Pp">It may be useful to set “flushroutes=NO” in - <span class="Pa">/etc/rc.conf</span> to avoid the default route supplied by - the boot setup disappearing mid-boot.</p> -</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">/etc/hosts</span></dt> - <dd>table of associated IP addresses and IP host names; see - <a class="Xr">hosts(5)</a></dd> - <dt><span class="Pa">/etc/ethers</span></dt> - <dd>table of associated Ethernet MAC addresses and IP host names used by - <a class="Xr">rarpd(8)</a>; see <a class="Xr">ethers(5)</a></dd> - <dt><span class="Pa">/etc/bootparams</span></dt> - <dd>client root pathname and swap pathname; see - <a class="Xr">bootparams(5)</a></dd> - <dt><span class="Pa">/etc/exports</span></dt> - <dd>exported NFS mount points; see <a class="Xr">exports(5)</a></dd> - <dt><span class="Pa">/etc/rbootd.conf</span></dt> - <dd>configuration file for HP RMP; see <a class="Xr">rbootd(8)</a></dd> - <dt><span class="Pa">/usr/mdec/rbootd</span></dt> - <dd>location of boot programs offered by <a class="Xr">rbootd(8)</a></dd> - <dt><span class="Pa">/tftpboot</span></dt> - <dd>location of boot programs offered by <a class="Xr">tftpd(8)</a></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">bootparams(5)</a>, <a class="Xr">dhcpd.conf(5)</a>, - <a class="Xr">ethers(5)</a>, <a class="Xr">exports(5)</a>, - <a class="Xr">fstab(5)</a>, <a class="Xr">hosts(5)</a>, - <a class="Xr">networks(5)</a>, <a class="Xr">boot(8)</a>, - <a class="Xr">dhcpd(8)</a>, <a class="Xr">mopd(8)</a>, - <a class="Xr">mountd(8)</a>, <a class="Xr">nfsd(8)</a>, - <a class="Xr">rarpd(8)</a>, <a class="Xr">rbootd(8)</a>, - <a class="Xr">reboot(8)</a>, <a class="Xr">rpc.bootparamd(8)</a>, - <a class="Xr">tftpd(8)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsT">Reverse Address Resolution - Protocol</span>, <span class="RsR">RFC</span>, <span class="RsN">903</span>, - <span class="RsD">June 1984</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsT">Bootstrap Loading using - TFTP</span>, <span class="RsR">RFC</span>, <span class="RsN">906</span>, - <span class="RsD">June 1984</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsT">Bootstrap Protocol</span>, - <span class="RsR">RFC</span>, <span class="RsN">951</span>, - <span class="RsD">September 1985</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsT">The TFTP Protocol (Revision - 2)</span>, <span class="RsR">RFC</span>, <span class="RsN">1350</span>, - <span class="RsD">July 1992</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsT">Dynamic Host Configuration - Protocol</span>, <span class="RsR">RFC</span>, - <span class="RsN">2131</span>, <span class="RsD">March - 1997</span>.</cite></p> -<p class="Pp"><cite class="Rs"><span class="RsT">DHCP Options and BOOTP Vendor - Extensions</span>, <span class="RsR">RFC</span>, - <span class="RsN">2132</span>, <span class="RsD">March - 1997</span>.</cite></p> -<p class="Pp"><a class="Lk" href="http://www.rfc-editor.org/">RFC Editor</a></p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">January 8, 2026</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/hpcboot.8 4.html b/static/netbsd/man8/hpcboot.8 4.html deleted file mode 100644 index f03ac869..00000000 --- a/static/netbsd/man8/hpcboot.8 4.html +++ /dev/null @@ -1,133 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">HPCBOOT(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">HPCBOOT(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">hpcboot</code> — <span class="Nd">load and - boot kernel from Windows CE</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">hpcboot.exe</code></td> - <td></td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">hpcboot</code> is a program that runs on - Windows CE. It loads and executes the specified - <span class="Ux">NetBSD</span> kernel. <code class="Nm">hpcboot</code> - supports hpcarm, hpcmips, and hpcsh ports.</p> -<p class="Pp">Click on the “Boot” button to start the boot process - with selected options. Click on the “Cancel” button to exit - <code class="Nm">hpcboot</code>.</p> -<section class="Ss"> -<h2 class="Ss" id="Kernel_Tab"><a class="permalink" href="#Kernel_Tab">Kernel - Tab</a></h2> -<p class="Pp">On this tab you can select the kernel to boot and options to pass - to the kernel.</p> -<dl class="Bl-tag"> - <dt>Directory</dt> - <dd>In this combobox you specify the “current” directory. The - kernel and miniroot image pathnames are taken to be relative to this - directory. - <p class="Pp"><code class="Nm">hpcboot</code> can load kernel and miniroot - from FAT and UFS filesystems, and via HTTP.</p> - </dd> - <dt>Kernel</dt> - <dd>In this text field you specify the name of the kernel to load. Kernels - compressed with <a class="Xr">gzip(1)</a> are supported.</dd> - <dt>Model</dt> - <dd>Select your H/PC model in this combobox.</dd> - <dt>Root File System</dt> - <dd>This group of controls lets you specify the desired root file system type. - You can select <a class="Xr">wd(4)</a>, <a class="Xr">sd(4)</a>, - <a class="Xr">md(4)</a>, and NFS root. - <p class="Pp">If you select <a class="Xr">md(4)</a> memory disk root file - system, you should specify the path name of the file system image in the - text field below. Miniroot images compressed with - <a class="Xr">gzip(1)</a> are supported.</p> - </dd> - <dt>Kernel Boot Flags</dt> - <dd>This group of controls is used to pass boot flags to the kernel.</dd> -</dl> -</section> -<section class="Ss"> -<h2 class="Ss" id="Option_Tab"><a class="permalink" href="#Option_Tab">Option - Tab</a></h2> -<p class="Pp">On this tab you can specify miscellaneous options that mostly - control the <code class="Nm">hpcboot</code> program itself.</p> -<dl class="Bl-tag"> - <dt>Auto Boot</dt> - <dd>If this option is selected <code class="Nm">hpcboot</code> will - automatically boot <span class="Ux">NetBSD</span> after the specified - timeout.</dd> - <dt>Reverse Video</dt> - <dd>Tells kernel if it should use the framebuffer in reverse video mode.</dd> - <dt id="before">Pause Before Boot</dt> - <dd>If selected, a warning dialog will be presented - <a class="permalink" href="#before"><i class="Em">before</i></a> anything - is done, right after the “Boot” button is pressed.</dd> - <dt>Load Debug Info</dt> - <dd>This option currently does nothing.</dd> - <dt id="after">Safety Message</dt> - <dd>If selected, a warning dialog will be presented - <a class="permalink" href="#after"><i class="Em">after</i></a> the kernel - has been loaded and prepared to be started. This will be your last chance - to cancel the boot.</dd> - <dt>Extra Kernel Options</dt> - <dd>In this text field you can specify additional options to pass to the - kernel.</dd> -</dl> -</section> -<section class="Ss"> -<h2 class="Ss" id="Console_Tab"><a class="permalink" href="#Console_Tab">Console - Tab</a></h2> -<p class="Pp">This tab gets its name from the big text area that - <code class="Nm">hpcboot</code> uses as the “console” to - report its progress.</p> -<dl class="Bl-tag"> - <dt>Save To File</dt> - <dd>If checked, the progress log will be sent to the specified file - instead.</dd> - <dt>“Checkboxes Anonymous”</dt> - <dd>The row of 8 checkboxes controls debugging options for - <code class="Nm">hpcboot</code> itself. They control the bits of an - internal variable, the leftmost checkbox being the 7th bit.</dd> - <dt>“Buttons Anonymous”</dt> - <dd>The buttons “a” to “d” control 4 - “hooks” a developer might want to use during - <code class="Nm">hpcboot</code> development.</dd> -</dl> -</section> -</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">kloader(4)</a>, <a class="Xr">boot(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">hpcboot</code> utility first appeared in - <span class="Ux">NetBSD 1.6</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp"><code class="Nm">hpcboot</code> reads the entire kernel image at - once, and requires enough free area on the main memory.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">April 3, 2004</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/intro.8 4.html b/static/netbsd/man8/intro.8 4.html deleted file mode 100644 index 6bc45052..00000000 --- a/static/netbsd/man8/intro.8 4.html +++ /dev/null @@ -1,44 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">INTRO(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">INTRO(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">intro</code> — - <span class="Nd">introduction to system maintenance procedures and - commands</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">This section contains information related to system operation and - maintenance.</p> -<p class="Pp">It describes commands used to create new file systems - (<a class="Xr">newfs(8)</a>), verify the integrity of the file systems - (<a class="Xr">fsck(8)</a>), control disk usage - (<a class="Xr">edquota(8)</a>), maintain system backups - (<a class="Xr">dump(8)</a>), and recover files when disks die an untimely - death (<a class="Xr">restore(8)</a>). Network related services like - <a class="Xr">inetd(8)</a> and <a class="Xr">ftpd(8)</a> are also - described.</p> -<p class="Pp">A number of pages in this section describe general system - management topics. For example, the <a class="Xr">diskless(8)</a> page - describes how to boot a system over a network, and the - <a class="Xr">compat_linux(8)</a> page describes how to run Linux binaries - on <span class="Ux">NetBSD</span> architectures that support it.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">intro</code> section manual page appeared in - <span class="Ux">4.2BSD</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">December 14, 2010</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.hpcarm/boot.8 3.html b/static/netbsd/man8/man8.hpcarm/boot.8 3.html deleted file mode 100644 index 728d6424..00000000 --- a/static/netbsd/man8/man8.hpcarm/boot.8 3.html +++ /dev/null @@ -1,80 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (hpcarm)</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> — <span class="Nd">system - bootstrapping procedures</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">Windows CE machines with StrongARM CPUs use the - <a class="Xr">hpcboot(8)</a> program to boot - <span class="Ux">NetBSD</span>.</p> -<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">Unfortunately, <span class="Ux">NetBSD</span> can't reboot itself - at power-up or after crashes. The machine will go through the cold reset and - boot into Windows CE. You will have to restart - <span class="Ux">NetBSD</span> manually using - <a class="Xr">hpcboot(8)</a>.</p> -<p class="Pp">Once <span class="Ux">NetBSD</span> starts, an automatic - consistency check of the file systems will be performed, 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">On cold reset Windows CE handheld machines attempt to boot - the Windows CE operating system from the boot ROM. The boot ROM is - usually not rewritable, so you cannot erase or damage Windows CE - image.</p> -<p class="Pp">You can't boot <span class="Ux">NetBSD</span> directly, skipping - Windows CE. The <span class="Ux">NetBSD</span> bootloader, - <a class="Xr">hpcboot(8)</a>, is provided as a Windows CE application - program instead. Though the bootloader is an application program, it blows - the entire running Windows CE, its data, and its settings away from - RAM (but not ROM!) when the kernel boots successfully. If - <span class="Ux">NetBSD</span> is halted the machine will go through the - cold reset and will reboot into Windows CE.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Normal_Operation"><a class="permalink" href="#Normal_Operation">Normal - Operation</a></h2> -<p class="Pp">Please, refer to the <a class="Xr">hpcboot(8)</a> manual page.</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">hpcboot.exe</span></dt> - <dd>bootloader program for Windows CE</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">hpcboot(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">There is no general way to launch the bootloader automatically, as - only a few Windows CE machines provide an “auto run” - mechanism.</p> -<p class="Pp">This port doesn't support <a class="Xr">kloader(4)</a>, which - means that when the system is rebooted, it goes back to - Windows CE.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">January 13, 2006</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.mac68k/boot.8 3.html b/static/netbsd/man8/man8.mac68k/boot.8 3.html deleted file mode 100644 index 918f9639..00000000 --- a/static/netbsd/man8/man8.mac68k/boot.8 3.html +++ /dev/null @@ -1,88 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (mac68k)</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> — <span class="Nd">system - bootstrapping procedures</span></p> -</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 <span class="Ux">NetBSD</span> kernel on the mac68k - architecture is booted from the native operating system by means of an - application program. When the kernel takes over, it initializes itself and - proceeds to boot the system. An automatic consistency check of the file - systems takes place, and unless this fails, the system comes up to - multi-user operations. The proper way to shut the system down is with the - <a class="Xr">shutdown(8)</a> command.</p> -<p class="Pp">If the system crashes, it will enter the kernel debugger, - <a class="Xr">ddb(4)</a>, if it is configured in the kernel. If the debugger - is not present, or the debugger is exited, the system will attempt a dump to - the configured dump device (which will be automatically recovered with - <a class="Xr">savecore(8)</a> during the next boot cycle). After the dump is - complete (successful or not), the system will attempt a reboot.</p> -<p class="Pp">On most mac68k machines with "soft-power" after the - IIcx, the power switch can be physically rotated and locked in the 'on' - position. The native OS can be configured to automatically start the - <span class="Ux">NetBSD</span> boot program. Additionally, the - <span class="Ux">NetBSD</span> boot program can be configured to boot - <span class="Ux">NetBSD</span> without intervention. When a system is so - configured, it can crash or lose power and reboot back to a fully multi-user - state without any intervention.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="The_boot_application"><a class="permalink" href="#The_boot_application">The - boot application</a></h2> -<p class="Pp">The boot application runs in the native OS on the system. It has a - dialog where booting preferences may be changed and an option whereby these - options may be saved. The preferences are stored in the program itself, not - in a preferences folder--thus allowing two separate copies of the program to - be configured differently (e.g. to boot different netbsd or netbsd.test, or - to boot from two different drives).</p> -<p class="Pp">One option that may be specified is a boot to single-user mode. - This stops the boot process very early on and allows system maintenance. If - one wishes to provide some security at this phase of the boot, remove the - ‘<code class="Li">secure</code>’ option from ttye0 in the - <a class="Xr">ttys(5)</a> file.</p> -<p class="Pp">Another useful option that may be specified is the "serial - console" option. This will allow a serial device (terminal or computer) - to act as a console for the system. This device must be configured to use - 9600 baud, eight bits, no parity, and one stop bit (9600-N81). Either the - printer port or the modem port (tty01 and tty00, respectively) may be used - for this.</p> -<p class="Pp">It is sometimes useful to boot a kernel that resides in a folder - in native OS rather than from the usual location in the - <span class="Ux">NetBSD</span> file system. A radio button is supplied for - this purpose. Note that some programs will not run properly if the kernel is - not found as <var class="Ar">/netbsd</var> within the - <span class="Ux">NetBSD</span> file system.</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 kernel</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">ddb(4)</a>, <a class="Xr">ttys(5)</a>, - <a class="Xr">savecore(8)</a>, <a class="Xr">shutdown(8)</a></p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">July 1, 1995</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.macppc/boot.8 3.html b/static/netbsd/man8/man8.macppc/boot.8 3.html deleted file mode 100644 index 07107669..00000000 --- a/static/netbsd/man8/man8.macppc/boot.8 3.html +++ /dev/null @@ -1,296 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (macppc)</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> — <span class="Nd">Macppc - system bootstrapping procedures</span></p> -</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 boot ROM performs a Power On Self Test (POST) then loads Open - Firmware. Depending on the Open Firmware variable - ‘<code class="Ev">auto-boot?</code>’ it will either stop at - the Open Firmware prompt or attempt to boot an operating system. Depending - on the contents of the ‘<code class="Ev">use-nvramrc?</code>’, - ‘<code class="Ev">boot-command</code>’, - ‘<code class="Ev">boot-device</code>’, and - ‘<code class="Ev">boot-file</code>’ Open Firmware variables, - it will attempt to boot MacOS, MacOS X, or - <span class="Ux">NetBSD</span>.</p> -<p class="Pp">To boot <span class="Ux">NetBSD</span>, Open Firmware loads the - bootloader <a class="Xr">macppc/ofwboot(8)</a> from the specified - ‘<code class="Ev">boot-device</code>’. The bootloader then - loads the kernel from the ‘<code class="Ev">boot-file</code>’, - (if it exists). Otherwise, it tries to load (in the following order): - <span class="Pa">netbsd</span>, <span class="Pa">netbsd.gz</span>, or - <span class="Pa">netbsd.macppc</span> on the “a” partition of - the same device that had the bootloader.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Open_Firmware_Commands"><a class="permalink" href="#Open_Firmware_Commands">Open - Firmware Commands</a></h2> -<p class="Pp">An essential but incomplete list of Open Firmware commands - follows. A more thorough list is contained in the FAQ. - <a class="Lk" href="https://www.NetBSD.org/ports/macppc/faq.html#ofw-use">https://www.NetBSD.org/ports/macppc/faq.html#ofw-use</a></p> -<p class="Pp"><code class="Ic">boot</code> [<var class="Ar">boot-device</var> - [<var class="Ar">boot-file</var>]] [<var class="Ar">options</var>]</p> -<p class="Pp">Boot an operating system. The default arguments for this command - are taken from the Open Firmware environment variables:</p> -<dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">boot-device</var></dt> - <dd>primary bootloader location</dd> - <dt><var class="Ar">boot-file</var></dt> - <dd>kernel location</dd> - <dt><var class="Ar">options</var></dt> - <dd>flags passed to the kernel</dd> -</dl> -<p class="Pp"><code class="Ic">reset-all</code></p> -<p class="Pp">Reset the system, and proceed as specified by the - ‘<code class="Ev">use-nvramrc?</code>’ and - ‘<code class="Ev">auto-boot?</code>’ variables. If - ‘<code class="Ev">use-nvramrc?</code>’ is set to - ‘<code class="Ev">true</code>’, then the system will attempt - to execute the commands stored in the - ‘<code class="Ev">nvramrc</code>’ variable. If - ‘<code class="Ev">auto-boot?</code>’ is set to - ‘<code class="Ev">true</code>’, the system will attempt to use - the values stored in ‘<code class="Ev">boot-command</code>’, - ‘<code class="Ev">boot-device</code>’, and - ‘<code class="Ev">boot-file</code>’ to boot the system. If - ‘<code class="Ev">auto-boot?</code>’ is set to - ‘<code class="Ev">false</code>’, the system will halt at the - Open Firmware prompt.</p> -<p class="Pp"><code class="Ic">shut-down</code></p> -<p class="Pp">Power off the system.</p> -<p class="Pp"><code class="Ic">setenv</code> <var class="Ar">variable</var> - <var class="Ar">value</var></p> -<p class="Pp">Set an Open Firmware variable, e.g.,</p> -<div class="Bd Pp Bd-indent Li"> -<pre>setenv auto-boot? false -setenv boot-device hd:,\ofwboot.xcf -setenv boot-file netbsd-GENERIC.gz</pre> -</div> -<p class="Pp"><code class="Ic">set-default</code> - <var class="Ar">variable</var></p> -<p class="Pp">Set an Open Firmware variable to its default value.</p> -<p class="Pp"><code class="Ic">printenv</code> - [<var class="Ar">variable</var>]</p> -<p class="Pp">Show Open Firmware variables and values.</p> -<p class="Pp"><code class="Ic">eject fd</code></p> -<p class="Pp">Eject floppy disk on systems with on-board floppy drives.</p> -<p class="Pp"><code class="Ic">mac-boot</code></p> -<p class="Pp">Attempt to boot MacOS on an Open Firmware 3 system.</p> -<p class="Pp"><code class="Ic">bye</code></p> -<p class="Pp">Attempt to boot MacOS on an Open Firmware 1.0.5, 2.0.x, or 2.4 - system.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Open_Firmware_Variables"><a class="permalink" href="#Open_Firmware_Variables">Open - Firmware Variables</a></h2> -<p class="Pp">An essential but incomplete list of Open Firmware variables - follows. A more thorough list is contained in the FAQ. - <a class="Lk" href="https://www.NetBSD.org/ports/macppc/faq.html#ofw-variables">https://www.NetBSD.org/ports/macppc/faq.html#ofw-variables</a></p> -<dl class="Bl-tag"> - <dt id="auto-boot?"><a class="permalink" href="#auto-boot?"><code class="Ev">auto-boot?</code></a></dt> - <dd>What Open Firmware will do at system startup or reset: - <dl class="Bl-tag"> - <dt><var class="Ar">true</var></dt> - <dd>automatically bootstrap an operating system using values from the - ‘<code class="Ev">boot-command</code>’, - ‘<code class="Ev">boot-device</code>’, and - ‘<code class="Ev">boot-file</code>’ variables.</dd> - <dt><var class="Ar">false</var></dt> - <dd>stop at the Open Firmware prompt.</dd> - </dl> - </dd> - <dt id="use-nvramrc?"><a class="permalink" href="#use-nvramrc?"><code class="Ev">use-nvramrc?</code></a></dt> - <dd>If ‘<code class="Ev">true</code>’ runs commands in variable - ‘<code class="Ev">nvramrc</code>’.</dd> - <dt id="real-base"><a class="permalink" href="#real-base"><code class="Ev">real-base</code></a></dt> - <dd>Kernel memory location. <i class="Em">Do not modify this value on Open - Firmware 3 systems — you may</i> <i class="Em">damage your - computer</i>. All other Open Firmware versions should use - <code class="Li">F00000</code>.</dd> - <dt id="load-base"><a class="permalink" href="#load-base"><code class="Ev">load-base</code></a></dt> - <dd>Bootloader memory location. <i class="Em">Do not modify this value on Open - Firmware 3 systems — you may</i> <i class="Em">damage your - computer</i>. All other Open Firmware versions should use - <code class="Li">600000</code>.</dd> - <dt id="boot-command"><a class="permalink" href="#boot-command"><code class="Ev">boot-command</code></a></dt> - <dd>The command to use for booting. Typically, the default of - ‘<code class="Ev">boot</code>’ is used.</dd> - <dt id="boot-device"><a class="permalink" href="#boot-device"><code class="Ev">boot-device</code></a></dt> - <dd>Device from which to load primary bootloader. Value depends on a variety - of factors. See <a class="Xr">macppc/ofwboot(8)</a>.</dd> - <dt id="boot-file"><a class="permalink" href="#boot-file"><code class="Ev">boot-file</code></a></dt> - <dd>Kernel location. Value depends on a variety of factors. See - <a class="Xr">macppc/ofwboot(8)</a>.</dd> - <dt id="input-device"><a class="permalink" href="#input-device"><code class="Ev">input-device</code></a></dt> - <dd>What type of console input device (ADB keyboard, USB keyboard, or serial - port). - <dl class="Bl-tag"> - <dt><var class="Ar">kbd</var></dt> - <dd>ADB keyboard on models with ADB, USB keyboard on models with USB, and - built-in keyboard on laptops. This is the default on some Open - Firmware 2.0.x machines and all Open Firmware 2.4 and 3 machines.</dd> - <dt><var class="Ar">ttya</var></dt> - <dd>‘Modem’ serial port on machines with serial ports. - Properties are 38400 bps, 8 bits, no parity, 1 stop bit, no - handshaking. This is the default on all Open Firmware 1.0.5 systems - and some Open Firmware 2.0.x systems.</dd> - <dt><var class="Ar">ttyb</var></dt> - <dd>‘Printer’ serial port on machines with serial ports. - Properties are the same as the ‘Modem’ port.</dd> - <dt><var class="Ar">scca</var></dt> - <dd>Serial port on Xserve models. Properties are 57600 bps, 8 bits, no - parity, 1 stop bit, no handshaking.</dd> - </dl> - </dd> - <dt>output-device</dt> - <dd>What type of console output device (On-board video, AGP video, PCI video, - built-in LCD, or serial console). Value depends on a variety of factors. - See <a class="Xr">macppc/ofwboot(8)</a> and - <a class="Lk" href="https://www.NetBSD.org/ports/macppc/faq.html#ofw-input-output-devices">https://www.NetBSD.org/ports/macppc/faq.html#ofw-input-output-devices</a></dd> - <dt>nvramrc</dt> - <dd>If ‘<code class="Ev">use-nvramrc?</code>’ is set to true, - these FORTH commands will be run when the computer is reset</dd> -</dl> -</section> -<section class="Ss"> -<h2 class="Ss" id="Normal_Operation"><a class="permalink" href="#Normal_Operation">Normal - Operation</a></h2> -<p class="Pp">When Open Firmware loads the primary bootloader, it will print - something like the following:</p> -<div class="Bd Pp Bd-indent"> -<pre> loading XCOFF - tsize=CC50 dsize=14AC bsize=2668 entry=640000 - SECTIONS: - .text 00640000 00640000 0000CC50 000000E0 - .data 0064D000 0064D000 000014AC 0000CD30 - .bss 0064E4B0 0064E4B0 00002668 00000000 - loading .text, done.. - loading .data, done.. - clearing .bss, done..</pre> -</div> -<p class="Pp">When <a class="Xr">macppc/ofwboot(8)</a> is started, it prints - something like the following:</p> -<div class="Bd Pp Bd-indent"> -<pre> >> NetBSD/macppc OpenFirmware Boot, Revision 1.7 - >> (autobuild@tgm.daemon.org, Thu Feb 6 17:50:27 UTC 2003)</pre> -</div> -<p class="Pp">When <a class="Xr">macppc/ofwboot(8)</a> is loading the kernel, it - prints something like the following:</p> -<div class="Bd Pp Bd-indent"> -<pre> 4395364+254568 [220144+193803]=0x4d477c - start=0x100000</pre> -</div> -<p class="Pp">When the <span class="Ux">NetBSD</span> kernel has started it - prints a banner similar to the following:</p> -<div class="Bd Pp Bd-indent Li"> -<pre> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 - The NetBSD Foundation, Inc. All rights reserved. - Copyright (c) 1982, 1986, 1989, 1991, 1993 - The Regents of the University of California. All rights reserved. - - NetBSD 1.6ZC (GENERIC) #0: Tue Sep 30 13:09:10 UTC 2003 - autobuild@tgm.NetBSD.org:/autobuild/HEAD/macppc/OBJ/autobuild/HEAD/src/sys/arch/macppc/compile/GENERIC</pre> -</div> -</section> -<section class="Ss"> -<h2 class="Ss" id="After_bootstrap"><a class="permalink" href="#After_bootstrap">After - bootstrap</a></h2> -<p class="Pp">Once the <span class="Ux">NetBSD</span>/macppc kernel is booted - normally it initializes itself and proceeds to start the system. An - automatic consistency check of the file systems takes place, and unless this - fails, the system comes up to multi-user operation.</p> -<p class="Pp">The proper way to shut the system down is with the - <a class="Xr">shutdown(8)</a> command.</p> -<p class="Pp">If the system crashes, it will enter the kernel debugger, - <a class="Xr">ddb(4)</a>, if it is configured in the kernel. If the crash - occurred during initialization and the debugger is not present or is exited, - the kernel will halt the system.</p> -<p class="Pp">If the crash occurred during normal operation and the debugger is - not present or is exited, the system will attempt a dump to the configured - dump device (which will be automatically recovered with - <a class="Xr">savecore(8)</a> during the next bootstrap cycle), and after - the dump is complete (successful or not) the kernel will attempt a - reboot.</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">/boot</span></dt> - <dd><span class="Ux">NetBSD</span> secondary bootstrap program (Open Firmware - 1.x and 2.x)</dd> - <dt><span class="Pa">/netbsd</span></dt> - <dd>default <span class="Ux">NetBSD</span> system kernel</dd> - <dt><span class="Pa">/usr/mdec/bootxx</span></dt> - <dd><span class="Ux">NetBSD</span> primary bootstrap program (Open Firmware - 1.x and 2.x) a.k.a. “partition zero” bootloader</dd> - <dt><span class="Pa">/usr/mdec/ofwboot</span></dt> - <dd><span class="Ux">NetBSD</span> secondary bootstrap program (Open Firmware - 1.x and 2.x)</dd> - <dt><span class="Pa">/usr/mdec/ofwboot.xcf</span></dt> - <dd>primary bootstrap for netboot and “cd9660” (ISO 9660), - “MS-DOS”, “HFS”, and “HFS+” file - systems.</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">ddb(4)</a>, <a class="Xr">intro(4)</a>, - <a class="Xr">diskless(8)</a>, <a class="Xr">halt(8)</a>, - <a class="Xr">init(8)</a>, <a class="Xr">installboot(8)</a>, - <a class="Xr">macppc/ofwboot(8)</a>, <a class="Xr">rc(8)</a>, - <a class="Xr">reboot(8)</a>, <a class="Xr">savecore(8)</a>, - <a class="Xr">shutdown(8)</a></p> -<p class="Pp"><a class="Lk" href="https://www.NetBSD.org/ports/macppc/faq.html">https://www.NetBSD.org/ports/macppc/faq.html</a> - <br/> - <a class="Lk" href="https://www.NetBSD.org/docs/network/netboot/">https://www.NetBSD.org/docs/network/netboot/</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="STANDARDS"><a class="permalink" href="#STANDARDS">STANDARDS</a></h1> -<p class="Pp"><span class="St">IEEE Std 1275-1994 (“Open - Firmware”)</span> - <a class="Lk" href="http://playground.sun.com/1275/home.html">http://playground.sun.com/1275/home.html</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The device names used by <span class="Ux">NetBSD</span>/macppc and - Open Firmware often have no relation to each other.</p> -<p class="Pp">Apple Computer's Open Firmware implementation is easily confused. - It is best to reboot your computer after a failed boot attempt, - <code class="Ic">halt</code>, or <code class="Ic">shutdown -h</code>. Use - the Open Firmware <code class="Ic">reset-all</code> command.</p> -<p class="Pp">Apple Computer's Open Firmware implementation is notoriously bad. - Thorough instructions for installing and booting - <span class="Ux">NetBSD</span> are in the install notes - (<span class="Pa">INSTALL.html</span>) included with every release of - <span class="Ux">NetBSD</span>.</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> diff --git a/static/netbsd/man8/man8.macppc/ofwboot.8 3.html b/static/netbsd/man8/man8.macppc/ofwboot.8 3.html deleted file mode 100644 index 3a16094d..00000000 --- a/static/netbsd/man8/man8.macppc/ofwboot.8 3.html +++ /dev/null @@ -1,367 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">OFWBOOT(8)</td> - <td class="head-vol">System Manager's Manual (macppc)</td> - <td class="head-rtitle">OFWBOOT(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">ofwboot</code>, - <code class="Nm">ofwboot.elf</code>, <code class="Nm">ofwboot.xcf</code> - — <span class="Nd">Open Firmware boot command</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">ofwboot</code></td> - <td></td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">Open Firmware is a FORTH-like command interpreter started by the - BootROM after the power-on self test (POST). This command interpreter allows - the user flexibility in choosing how their machine boots an operating - system. <span class="Ux">NetBSD</span> uses Open Firmware to initialize many - of the devices in a system and uses it to load the primary bootloader, - <code class="Nm">ofwboot</code>.</p> -<p class="Pp">The information in this man page should only serve as a guideline - for users. Apple has made many revisions to Open Firmware, and the earlier - versions had many problems and inconsistencies. You may find that a boot - command that works on one model will not work on another.</p> -<p class="Pp">In this man page, only one Open Firmware command will be - described, <code class="Ic">boot</code>, because it is used to pass - arguments to <code class="Nm">ofwboot</code>. The Open Firmware - <code class="Ic">boot</code> command takes up to three arguments:</p> -<div class="Bd Pp Bd-indent Li"> -<pre><code class="Ic">boot</code> [<var class="Ar">boot-device</var> [<var class="Ar">boot-file</var>]] [<var class="Ar">options</var>]</pre> -</div> -<p class="Pp">where</p> -<p class="Pp"></p> -<div class="Bd-indent"> -<dl class="Bl-tag Bl-compact"> - <dt><var class="Ar">boot-device</var></dt> - <dd>primary bootloader location</dd> - <dt><var class="Ar">boot-file</var></dt> - <dd>kernel location</dd> - <dt><var class="Ar">options</var></dt> - <dd>flags passed to the kernel (see below)</dd> -</dl> -</div> -<section class="Ss"> -<h2 class="Ss" id="boot-device"><a class="permalink" href="#boot-device">boot-device</a></h2> -<p class="Pp">The first argument, <var class="Ar">boot-device</var>, actually - designates the primary bootloader location and its name in the form:</p> -<div class="Bd Pp Bd-indent Li"> -<pre> -<var class="Ar">device</var><code class="Ic">:</code>[<var class="Ar">partition-num</var>][,\<var class="Ar">bootloader-filename</var>] -</pre> -</div> -<p class="Pp">A typical example, from a PowerBook (FireWire), is</p> -<p class="Pp"></p> -<div class="Bd - Bd-indent"><code class="Li">/pci@f2000000/mac-io@17/ata-4@1f000/@0:9,\ofwboot.xcf</code></div> -<p class="Pp">Note that colon (‘<code class="Li">:</code>’) - delimits the device to the left, and comma - (‘<code class="Li">,</code>’) separates the bootloader - filename from the first part. For Open Firmware versions before 3, the - primary bootloader is installed in partition “zero”, and it is - not necessary to specify the <var class="Ar">bootloader-filename</var>. For - Open Firmware version 3, you must specify the bootloader filename.</p> -<p class="Pp">Open Firmware stores aliases to common devices in NVRAM. In the - example the above, - <span class="Pa">/pci@f2000000/mac-io@17/ata-4@1f000/@0</span> is the path - on a PowerBook (FireWire) to the built-in ATA/100 hard drive. Use the - <code class="Ic">devalias</code> command in Open Firmware to print out a - list of common device names on a particular model. The - <var class="Ar">boot-device</var> above could then be simplified to:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">hd:9,\ofwboot.xcf</code></div> -<p class="Pp"><var class="Ar">bootloader-filename</var> is usually - <code class="Nm">ofwboot.xcf</code>. See also the - <a class="Sx" href="#FILES">FILES</a> section for further discussion.</p> -<p class="Pp">If <var class="Ar">boot-device</var> is omitted from the - <code class="Ic">boot</code> command, the Open Firmware variable - <code class="Ev">boot-device</code> is used.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="boot-file"><a class="permalink" href="#boot-file">boot-file</a></h2> -<p class="Pp">It may be necessary to specify the <var class="Ar">boot-file</var> - if Open Firmware does not know where to find the kernel. The default is to - load the file named <span class="Pa">netbsd</span> on partition - “<span class="Pa">a</span>” from the device used to load the - primary bootloader.</p> -<p class="Pp">For systems with Open Firmware versions less than 3 which are set - up using <code class="Ic">sysinst</code>, the - <var class="Ar">boot-file</var> argument is not necessary. Systems with Open - Firmware version 3 may need to specify the - <var class="Ar">boot-file</var>.</p> -<p class="Pp">The syntax is similar to the <var class="Ar">boot-device</var> - argument:</p> -<div class="Bd Pp Bd-indent Li"> -<pre> -[<var class="Ar">boot-file-device</var><code class="Ic">:</code><var class="Ar">partition-num</var><code class="Ic">/</code>][<var class="Ar">kernel-name</var>] -</pre> -</div> -<p class="Pp">This is a little different, since a kernel-name may be specified - without listing a <var class="Ar">boot-file-device</var> and - <var class="Ar">partition-num</var>. Additionally, a - <var class="Ar">boot-file-device</var> and - <var class="Ar">partition-num</var> may need to be specified, while using - the default <var class="Ar">kernel-name</var>.</p> -<p class="Pp">If no <var class="Ar">kernel-name</var> is specified, the primary - bootloader will try to find kernels named either - <span class="Pa">netbsd</span> or <span class="Pa">netbsd.gz</span> on the - boot-device or (if specified) boot-file-device.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="options"><a class="permalink" href="#options">options</a></h2> -<p class="Pp">Possible options are:</p> -<dl class="Bl-tag"> - <dt id="a"><a class="permalink" href="#a"><code class="Fl">-a</code></a></dt> - <dd>ask for the boot device</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>single-user mode boot</dd> - <dt id="d"><a class="permalink" href="#d"><code class="Fl">-d</code></a></dt> - <dd>debug mode</dd> - <dt id="exit"><a class="permalink" href="#exit"><code class="Cm">exit</code></a></dt> - <dd>exit to Open Firmware after processing arguments</dd> -</dl> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="ENVIRONMENT"><a class="permalink" href="#ENVIRONMENT">ENVIRONMENT</a></h1> -<p class="Pp">If set, the following Open Firmware variables will be used to - determine which <var class="Ar">boot-device</var> and - <var class="Ar">boot-file</var> Open Firmware should use when booting a - system. If the user specifies arguments on the command line, these values - are overridden.</p> -<dl class="Bl-tag"> - <dt id="boot-device~2"><a class="permalink" href="#boot-device~2"><code class="Ev">boot-device</code></a></dt> - <dd>used as the first argument</dd> - <dt id="boot-file~2"><a class="permalink" href="#boot-file~2"><code class="Ev">boot-file</code></a></dt> - <dd>used as the second argument</dd> - <dt id="auto-boot?"><a class="permalink" href="#auto-boot?"><code class="Ev">auto-boot?</code></a></dt> - <dd>setting this variable to <code class="Ic">false</code> will present the - user with an Open Firmware command prompt after power-on reset. A value of - <code class="Ic">true</code> will automatically boot the system using the - variables <code class="Ev">boot-device</code> and - <code class="Ev">boot-file</code>. (This is not really related to the boot - command, but is included for completeness.)</dd> -</dl> -<p class="Pp">To restore these variables to their default values, use the - <code class="Ic">set-default</code> Open Firmware command:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">set-default boot-device</code></div> -</section> -<section class="Sh"> -<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1> -<p class="Pp">The three files <code class="Nm">ofwboot</code>, - <code class="Nm">ofwboot.elf</code>, and <code class="Nm">ofwboot.xcf</code> - are the same program, in different executable formats.</p> -<dl class="Bl-tag"> - <dt><span class="Pa">ofwboot</span></dt> - <dd><code class="Nm">ofwboot</code> is installed via - <a class="Xr">installboot(8)</a> on systems with Open Firmware versions - less than 3. It is not necessary to specify this file name on the Open - Firmware <code class="Ic">boot</code> command, as it is stored in a - special location in the <span class="Ux">NetBSD</span> partition that is - marked “bootable” in the Apple partition map entry. The - bootable partition can be specified as partition “zero”. For - example, the following command might be used to boot from a SCSI device - with ID 2: <code class="Ic">0 >boot scsi-int/sd@2:0</code>.</dd> - <dt><span class="Pa">ofwboot.xcf</span></dt> - <dd><code class="Nm">ofwboot.xcf</code> is in XCOFF format. This file is used - on all Open Firmware 3 systems, and on Open Firmware systems prior to 3 - when the bootloader is not installed in partition “zero”, - such as from an ISO-9660 format CD-ROM.</dd> - <dt><span class="Pa">ofwboot.elf</span></dt> - <dd><code class="Nm">ofwboot.elf</code> is in <a class="Xr">elf(5)</a> format - and only functions on systems with Open Firmware version 3. To avoid - confusion, all users should be using <code class="Nm">ofwboot.xcf</code>, - as <code class="Nm">ofwboot.elf</code> offers no additional functionality. - It is only included for historical reasons.</dd> - <dt><span class="Pa">boot.fs</span></dt> - <dd>This 1.44 MB disk image contains everything necessary to boot and install - <span class="Ux">NetBSD</span>. It includes the partition - “zero” bootloader (<code class="Nm">ofwboot</code>), an - INSTALL kernel (with limited device drivers), and the - <code class="Ic">sysinst</code> utility in a RAM disk. Since Open Firmware - does not care what media files are loaded from, only whether they are - supported and in the correct format, this disk image may be placed on - media other than floppy disks, such as hard drives or Zip disks. Use - <a class="Xr">dd(1)</a> on Unix, or <code class="Ic">DiskCopy</code> on - MacOS 9.1 or later, or <code class="Ic">suntar</code> on any MacOS version - to copy this image onto the media.</dd> - <dt><span class="Pa">netbsd</span></dt> - <dd>production kernel, using the GENERIC set of devices which supports almost - all hardware available for this platform.</dd> - <dt><span class="Pa">netbsd_GENERIC_MD.gz</span></dt> - <dd>GENERIC kernel (the same as <var class="Ar">netbsd</var>), with RAM disk - and <code class="Ic">sysinst</code> included.</dd> - <dt><span class="Pa">NetBSD-{RELEASE}-macppc.iso</span></dt> - <dd>bootable CD-ROM image for all supported systems. Usually located at - <span class="Pa">https://cdn.NetBSD.org/pub/NetBSD/images/{RELEASE}/</span></dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1> -<p class="Pp">In the following examples - ‘<code class="Li">0 > </code>’ is the Open - Firmware prompt.</p> -<ul class="Bl-item"> - <li>Boot the default installation into single user mode. - <div class="Bd Bd-indent"><code class="Li">0 > boot -s</code></div> - </li> - <li>Boot an Open Firmware 3 system, with <var class="Ar">netbsd</var> - installed on partition “<span class="Pa">a</span>”: - <div class="Bd Bd-indent"><code class="Li">0 > boot - hd:,\ofwboot.xcf</code></div> - </li> - <li>Boot the kernel named <span class="Pa">netbsd.new</span> from partition - “<span class="Pa">a</span>” of the hard disk into - <a class="Xr">ddb(4)</a> using ELF version of - <code class="Nm">ofwboot</code> from the USB flash drive: - <div class="Bd Bd-indent"><code class="Li">0 > boot - usb0/disk:,\ofwboot.elf hd/netbsd.new -d</code></div> - or - <div class="Bd Bd-indent"><code class="Li">0 > boot - usb1/disk:,\ofwboot.elf hd/netbsd.new -d</code></div> - Note: You can check which usb device name should be used by - “<code class="Ic">devalias</code>” and - “<code class="Ic">dev usb0 ls</code>” commands etc.</li> - <li>Boot from bootable CD-ROM of <span class="Ux">NetBSD</span> release with - Open Firmware 3 or higher: - <div class="Bd Bd-indent"><code class="Li">0 > boot - cd:,\ofwboot.xcf</code></div> - </li> - <li>Boot from bootable CD-ROM (internal SCSI, id=3) of - <span class="Ux">NetBSD</span> release with Open Firmware versions prior - to 3: - <div class="Bd Bd-indent"><code class="Li">0 > boot - scsi/sd@3:0</code></div> - </li> - <li>Boot from a USB flash drive containing a bootable CD-ROM ISO image of - <span class="Ux">NetBSD</span> release with Open Firmware 3 or higher: - <div class="Bd Bd-indent"><code class="Li">0 > boot - usb0/disk@1:3,\ofwboot.xcf</code></div> - or - <div class="Bd Bd-indent"><code class="Li">0 > boot - usb1/disk@1:3,\ofwboot.xcf</code></div> - Note: The partition number “<span class="Pa">3</span>” is an - ISO9660/HFS hybrid partition specified by the Apple partition map in the - macppc CD ISO image of <span class="Ux">NetBSD</span> release.</li> - <li>Boot from floppy disk: - <div class="Bd Bd-indent"><code class="Li">0 > boot fd:0</code></div> - </li> - <li>Boot from network, with bootps, <a class="Xr">bootptab(5)</a>, - <a class="Xr">tftpd(8)</a>, and <a class="Xr">nfsd(8)</a> server - available: - <div class="Bd Bd-indent"><code class="Li">0 > boot enet:0</code></div> - </li> - <li>Boot from network, but use internal root partition of second drive: - <div class="Bd Bd-indent"><code class="Li">0 > boot enet:0 - ultra1:0</code></div> - </li> - <li>Boot MacOS, looking for the first available bootable disk: - <div class="Bd Bd-indent"><code class="Li">0 > boot - hd:,\\:tbxi</code></div> - </li> - <li>Boot MacOS X residing on partition 10: - <div class="Bd Bd-indent"><code class="Li">0 > boot - hd:10,\\:tbxi</code></div> - </li> -</ul> -</section> -<section class="Sh"> -<h1 class="Sh" id="ERRORS"><a class="permalink" href="#ERRORS">ERRORS</a></h1> -<div class="Bd"> -<pre>DEFAULT CATCH!, code=FF00300 at %SRR0: FF80AD38 %SRR1: 00001070</pre> -</div> -<p class="Pp">Could be “device not found” or I/O errors on the - device. The numbers are just for example. If the error is caused by I/O - errors (especially on CD boot), retrying the same command after restarting - Open Firmware by <code class="Ic">reset-all</code> command might help.</p> -<div class="Bd Pp"> -<pre>CLAIM failed</pre> -</div> -Open Firmware got errors on memory allocation ops etc. This could also happen by - buggy Open Firmware implementation, or improper - <code class="Ev">real-base</code> variable settings. -<div class="Bd Pp"> -<pre>Can't LOAD from this device</pre> -</div> -Open Firmware found the device, but it is not supported by - <code class="Ic">load</code>. -<div class="Bd Pp"> -<pre>0 > boot yy:0/netbsd -RESETing to change Configuration!</pre> -</div> -<var class="Ar">yy:0</var> doesn't exist, so Open Firmware ignores the string - and uses the default parameters to boot MacOS; the MacOS boot routine then - clears some of the Open Firmware variables. -<div class="Bd Pp"> -<pre>0 > boot ata/ata-disk@0:9 specified partition is not bootable - ok</pre> -</div> -As it says. -<div class="Bd Pp"> -<pre>0 > boot ata/ata-disk@0:0 ->> NetBSD/macppc OpenFirmware Boot, Revision 1.3 ->> (root@nazuha, Fri Jun 8 22:21:55 JST 2001) -no active package3337696/</pre> -</div> -and hangs: See the real-base part in the FAQ. -<p class="Pp">Note: It is recommended to restart Open Firmware by - <code class="Ic">reset-all</code> command if you get these Open Firmware - errors, to avoid further unexpected random errors.</p> -</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">installboot(8)</a></p> -<p class="Pp"><span class="Pa">INSTALL.html</span></p> -<p class="Pp"><a class="Lk" href="https://www.NetBSD.org/ports/macppc/faq.html">NetBSD/macppc - Frequently Asked Questions</a></p> -<p class="Pp"><a class="Lk" href="https://www.NetBSD.org/ports/macppc/partitioning.html">NetBSD/macppc - Partitioning HOW-TO</a></p> -<p class="Pp"><a class="Lk" href="https://www.NetBSD.org/ports/macppc/models.html">NetBSD/macppc - Model Support</a></p> -<p class="Pp"><a class="Lk" href="https://www.NetBSD.org/docs/network/netboot/">Diskless - NetBSD HOW-TO</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="STANDARDS"><a class="permalink" href="#STANDARDS">STANDARDS</a></h1> -<p class="Pp"><span class="St">IEEE Std 1275-1994 (“Open - Firmware”)</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp"><code class="Nm">ofwboot</code> can only boot from devices - recognized by Open Firmware.</p> -<p class="Pp">Early PowerMacintosh systems (particularly the 7500) seem to have - problems with netbooting. Adding an arp entry at the tftp server with</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">arp -s booting-host-name - its-ethernet-address</code></div> -<p class="Pp">may resolve this problem (see <a class="Xr">arp(8)</a>).</p> -<p class="Pp">Once boot failed,</p> -<div class="Bd Pp Bd-indent Li"> -<pre>0 > boot CLAIM failed - ok</pre> -</div> -<p class="Pp">successive boots may not be possible. You need to type - <code class="Ic">reset-all</code> or power-cycle to re-initialize Open - Firmware.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">June 9, 2024</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.pmax/boot.8 2.html b/static/netbsd/man8/man8.pmax/boot.8 2.html deleted file mode 100644 index 651d9a25..00000000 --- a/static/netbsd/man8/man8.pmax/boot.8 2.html +++ /dev/null @@ -1,162 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (pmax)</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> — <span class="Nd">system - bootstrapping procedures</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <span class="Ux">NetBSD</span> kernel is started by placing it - near the beginning of physical memory and transferring to the entry point. - Since the system is not reenterable, it is necessary to read it in from disk - or tape each time it is to be bootstrapped.</p> -<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 boot itself at power-up or after - crashes. An automatic consistency check of the file systems will be - performed, 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">At power up, all DECstation ROMs consult the - <code class="Nm">haltaction</code> environment variable in EEPROM to - determine whether or not to attempt to boot automatically. If this variable - is set to ‘h’, the ROM prints a prompt on the console and - waits for user commands. If set to ‘b’, the ROM attempts to - autoboot.</p> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="DECSTATION_2100_and_3100"><a class="permalink" href="#DECSTATION_2100_and_3100">DECSTATION - 2100 and 3100</a></h1> -<p class="Pp">On the DECstation 2100 and 3100, the path used for automatic - booting is stored in the <code class="Nm">bootpath</code> environment - variable. - <br/> - The path is made up of a device type specifier (e.g., rz, tz, mop or tftp) - followed by a triplet in the form (x,y,z), followed by a filename to - load.</p> -<p class="Pp">Within the triplet, x is the controller (always 0), y is the SCSI - id of the drive to boot from or 0 for net boots, and z is the partition to - boot from (usually 0 for SCSI devices, always zero for network booting). For - both disk and network boots, () may be specified instead of (0,0,0).</p> -<p class="Pp">The filename is optional for bootp/tftp and mop booting, since in - these cases the network protocol can be used to determine which file to - boot. When booting off the tape, no filename should be specified. When - booting off of disk, the filename is optional but is usually specified. If - no filename is specified when booting off disk, the following filenames are - tried in order: <code class="Nm">netbsd.pmax</code>, - <code class="Nm">netbsd</code>, <code class="Nm">netbsd.gz</code>, - <code class="Nm">netbsd.bak</code>, <code class="Nm">netbsd.old</code>, - <code class="Nm">onetbsd</code>, <code class="Nm">gennetbsd</code>. - Generally, the kernel is named <code class="Nm">netbsd</code>.</p> -<p class="Pp">An example bootpath setting would be:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">setenv bootpath - rz(0,1,0)netbsd</code></code></div> -<p class="Pp">At the PROM prompt, the user may boot - <span class="Ux">NetBSD</span> with either the <code class="Nm">auto</code> - or the <code class="Nm">boot</code> command. If the - <code class="Nm">auto</code> command is used, the <code class="Fl">-a</code> - argument is passed to the kernel, requesting a multi-user boot; otherwise - the <code class="Fl">-s</code> argument is passed, requesting that - <span class="Ux">NetBSD</span> boot to single user mode.</p> -<p class="Pp">When either the <code class="Nm">boot</code> or the - <code class="Nm">auto</code> command is issued with no arguments, the kernel - specified in the bootpath environment variable is booted. With the - <code class="Nm">boot</code> command, an alternative kernel may be specified - with the <code class="Fl">-f</code> flag, followed by the path of the kernel - to boot, as described above. For example:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">boot -f - rz(0,4,0)netbsd.new</code></code></div> -</section> -<section class="Sh"> -<h1 class="Sh" id="TURBOchannel_DECstations"><a class="permalink" href="#TURBOchannel_DECstations">TURBOchannel - DECstations</a></h1> -<p class="Pp">On TURBOchannel machines (all DECstation 5000 models), the boot - path is specified in the boot environment variable, along with any arguments - to be passed to the kernel. Note that to specify boot arguments (e.g., - <code class="Fl">-a</code>) when setting the <code class="Nm">boot</code> - environment variable, the filename and arguments must be enclosed in quotes. - For example:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">setenv boot</code> - “<code class="Ic">3/rz4/netbsd -a</code>”</code></div> -<p class="Pp">The device from which to boot is specified as the TURBOchannel - slot number, a TURBOchannel-option-specific device name, and a path to the - file to load, all separated by slashes. You can get a list of the devices - installed in your TURBOchannel slots (as well as any built-in devices which - appear as TURBOchannel slots) by typing the <code class="Nm">cnfg</code> - command at the boot prompt. You can get more detailed information about a - specific TURBOchannel option by typing <code class="Nm">cnfg</code> followed - by the slot number of that option.</p> -<p class="Pp">For SCSI devices, the option-specific device identifier is either - rz# for disks or tz# for tapes, where # is the SCSI id of the device. For - network devices, the option-specific protocol identifier is either mop or - tftp. Filename requirements are as for the DECstation 2100 and 3100.</p> -<p class="Pp">To start <span class="Ux">NetBSD</span> from the boot prompt, the - <code class="Nm">boot</code> command must be used. With no arguments, this - simply boots the default kernel with the default arguments as set with - <code class="Nm">setenv</code> <code class="Nm">boot</code>. If no boot - environment variable is set or if an alternative kernel is to be booted, the - path of that kernel may be specified after the boot command as described - above, and any arguments may be passed similarly. For example:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">boot - 3/rz4/netbsd.new -a</code></code></div> -</section> -<section class="Sh"> -<h1 class="Sh" id="KERNEL_ARGUMENTS"><a class="permalink" href="#KERNEL_ARGUMENTS">KERNEL - ARGUMENTS</a></h1> -<p class="Pp">The kernel supports the following arguments:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="a"><a class="permalink" href="#a"><code class="Li">a</code></a></dt> - <dd>Autoboot -- try and boot to multi-user mode without further input.</dd> - <dt id="m"><a class="permalink" href="#m"><code class="Li">m</code></a></dt> - <dd>Use a miniroot already present in memory.</dd> - <dt id="n"><a class="permalink" href="#n"><code class="Li">n</code></a></dt> - <dd>Prompt for the root file system device, the system crash dump device, and - the path to <a class="Xr">init(8)</a>.</dd> - <dt id="N"><a class="permalink" href="#N"><code class="Li">N</code></a></dt> - <dd>Do not prompt for the root file system device, the system crash dump - device, and the path to <a class="Xr">init(8)</a>. If the configured-in - devices are present, use them.</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Li">s</code></a></dt> - <dd>Boot only to single-user mode.</dd> -</dl> -</div> -<p class="Pp">Since DECstation PROMs also parse any arguments with a leading - "-", and reject unrecognized options, arguments other than - "a" or "s" should be specified after the kernel name - with no leading "-". For example:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">boot 3/rz4/netbsd - ns</code></code></div> -</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">ddb(4)</a>, <a class="Xr">halt(8)</a>, - <a class="Xr">init(8)</a>, <a class="Xr">installboot(8)</a>, - <a class="Xr">rc(8)</a>, <a class="Xr">reboot(8)</a>, - <a class="Xr">savecore(8)</a>, <a class="Xr">shutdown(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">boot</code> command is currently under - development.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">April 8, 2003</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.prep/boot.8 3.html b/static/netbsd/man8/man8.prep/boot.8 3.html deleted file mode 100644 index aa126c52..00000000 --- a/static/netbsd/man8/man8.prep/boot.8 3.html +++ /dev/null @@ -1,87 +0,0 @@ -<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> — <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> diff --git a/static/netbsd/man8/man8.sandpoint/altboot.8 3.html b/static/netbsd/man8/man8.sandpoint/altboot.8 3.html deleted file mode 100644 index dfd4be2d..00000000 --- a/static/netbsd/man8/man8.sandpoint/altboot.8 3.html +++ /dev/null @@ -1,181 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">ALTBOOT(8)</td> - <td class="head-vol">System Manager's Manual (sandpoint)</td> - <td class="head-rtitle">ALTBOOT(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">altboot</code> — <span class="Nd">program - to boot <span class="Ux">NetBSD</span> kernel from disk or - network</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">altboot</code> is a standalone program which - works on top of a NAS product's bootloader. It is capable of loading a - <span class="Ux">NetBSD</span> kernel from an IDE or SATA disk drive, or via - network with NFS or TFTP protocol. <code class="Nm">altboot</code> can be - stored in flash ROM. Typically you will first copy it from flash into RAM - and then invoke it there to boot the <span class="Ux">NetBSD</span> - kernel.</p> -<p class="Pp"><code class="Nm">altboot</code> runs in conjunction with popular - U-Boot/PPCBoot bootloaders used by NAS products. With an appropriate boot - command line, saved in the environment, <code class="Nm">altboot</code> can - load and start a <span class="Ux">NetBSD</span> kernel without manual - intervention. The original U-Boot/PPCBoot bootloaders remain useful and - altboot works as a functional extension of them.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1> -<p class="Pp"><code class="Nm">altboot</code> occupies less than 128KB in volume - and can be stored to any vacant space of the system's flash. It is made to - run at RAM address offset 0x0100'0000. U-Boot/PPCboot is instructed to copy - the program to RAM in this way:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">=> cp.b fffe0000 1000000 - 20000</code></div> -<p class="Pp">Here 0xfffe'0000 is the flash address where - <code class="Nm">altboot</code> is stored while 0x0100'0000 is the RAM - address to copy to.</p> -<p class="Pp">The invocation syntax is:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">=> go 1000000 - <var class="Ar">ide:N</var> <var class="Ar">opt1</var> <var class="Ar">opt2 - ...</var> <var class="Ar">bootname</var></code></div> -<dl class="Bl-tag"> - <dt id="ide:N"><var class="Va">ide:N</var></dt> - <dd>where <var class="Ar">N</var> is a string of digits, which defines the - number of connected drives on each PATA channel. This option is useful to - avoid the delays, when <code class="Nm">altboot</code> is trying to detect - a non-existing drive. Examples: - <dl class="Bl-tag"> - <dt>ide:<var class="Ar">10</var></dt> - <dd>A single master drive on the first channel. Nothing on the second - channel.</dd> - <dt>ide:<var class="Ar">22</var></dt> - <dd>A master and slave drive on both channels of the first - controller.</dd> - <dt>ide:<var class="Ar">1111</var></dt> - <dd>A master drive on each channel. The first two digits belong to the - first controller, the last two to the second controller.</dd> - </dl> - <p class="Pp">Unspecified digits will be read as <var class="Ar">0</var>. - The <var class="Ar">ide</var> option has only a meaning for PATA disks. - Omitting it makes it default to <var class="Ar">ide:10</var>.</p> - </dd> - <dt id="optN"><var class="Va">optN</var></dt> - <dd>multi, auto, ask, single, ddb, userconf, norm, quiet, verb, silent, debug - <p class="Pp">Omitting optN makes <code class="Nm">altboot</code> default to - multi-user mode boot.</p> - <p class="Pp">N.B., the maximum number of allowed go command arguments - varies and depends on the U-Boot/PPCBoot buildtime configuration.</p> - </dd> - <dt id="bootname"><var class="Va">bootname</var></dt> - <dd>One of the following: - <p class="Pp"></p> - <div class="Bd - Bd-indent"><code class="Li">nfs:<var class="Ar">filename</var></code></div> - <div class="Bd Bd-indent"><code class="Li">nfs:</code></div> - <div class="Bd - Bd-indent"><code class="Li">tftp:<var class="Ar">filename</var></code></div> - <div class="Bd Bd-indent"><code class="Li">tftp:</code></div> - <div class="Bd - Bd-indent"><code class="Li">wd<var class="Ar">Np</var>:<var class="Ar">filename</var></code></div> - <div class="Bd - Bd-indent"><code class="Li">wd<var class="Ar">Np</var></code></div> - : - <div class="Bd - Bd-indent"><code class="Li">mem:<var class="Ar">address</var></code></div> - <div class="Bd Bd-indent"><code class="Li">net:</code></div> - <p class="Pp">The last one is a synonym for “nfs”.</p> - </dd> - <dt>nfs:<var class="Va">filename</var></dt> - <dd>issue a DHCP request to determine the IP address and download - <var class="Ar">filename</var> from the NFS server.</dd> - <dt>nfs:</dt> - <dd>target file is determined by <b class="Sy">filename</b> field of - <span class="Pa">/etc/dhcpd.conf</span></dd> - <dt>tftp:<var class="Va">filename</var></dt> - <dd>issue a DHCP request to determine IP address and download - <var class="Ar">filename</var> from the TFTP server.</dd> - <dt>tftp:</dt> - <dd>target file is determined by <b class="Sy">filename</b> field of - <span class="Pa">/etc/dhcpd.conf</span></dd> - <dt>wd<var class="Va">Np</var>:<var class="Va">filename</var></dt> - <dd>load the ELF <span class="Ux">NetBSD</span> kernel - <var class="Ar">filename</var> from an FFSv2 or FFSv1 filesystem. - <var class="Ar">N</var> is a number to distinguish the target drive. - <var class="Ar">p</var> is a partition specifier. When omitted, partition - ‘a’ is assumed. “wd0a” means partition - ‘a’ of the first disk drive.</dd> - <dt>wd<var class="Va">Np</var>:</dt> - <dd>use filename “netbsd” for booting the ELF - <span class="Ux">NetBSD</span> kernel.</dd> - <dt>mem:<var class="Va">address</var></dt> - <dd>boots the ELF <span class="Ux">NetBSD</span> kernel from any address in - memory. The <var class="Ar">address</var> argument has to be specified as - a hexadecimal number and denotes the start address of the ELF image in - memory.</dd> -</dl> -<p class="Pp"><code class="Nm">altboot</code> can boot from RAID 1 partitions, - but only if the RAID partition is the first partition on the disk.</p> -<p class="Pp">U-Boot/PPCBoot provides a way to run a short list of commands - right after power-on. The following is a procedure to setup the system for - starting <span class="Ux">NetBSD</span> after a 5 second delay, allowing the - user to break into interactive mode. Note that a backslashed - ‘;’ is necessary to enter the script correctly.</p> -<div class="Bd Pp Bd-indent Li"> -<pre>=> setenv bootcmd cp.b fffe0000 1000000 20000\; go 1000000 wd0: -=> setenv bootdelay 5 -=> saveenv</pre> -</div> -<p class="Pp">When U-Boot/PPCBoot is lacking important commands like cp or go, - or is unable to save the environment, then there is still the option to - replace the Linux kernel module by <span class="Pa">altboot.img</span> and - save it to the same address in flash ROM. In this case you have only two - options left to pass arguments:</p> -<p class="Pp"></p> -<ul class="Bl-bullet Bl-compact"> - <li>Enter the interactive command line mode, after - <code class="Nm">altboot</code> has started. This requires a serial - console.</li> - <li id="altboot:">Write a fixed command line into flash, replacing the Linux - initrd image. The command line is a normal ASCII file, started by the - identifier - <a class="permalink" href="#altboot:"><i class="Em">altboot:</i></a> and - terminated by any control character between 0 and 31. Example: - <div class="Bd Bd-indent"><code class="Li">altboot:silent ide:1111 - wd0:netbsd</code></div> - </li> -</ul> -</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">dhcpd(8)</a>, <a class="Xr">diskless(8)</a>, - <a class="Xr">nfsd(8)</a>, <a class="Xr">raidctl(8)</a>, - <a class="Xr">tftpd(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <span class="Ux">NetBSD</span>/sandpoint - <code class="Nm">altboot</code> first appeared in <span class="Ux">NetBSD - 6.0</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The Realtek Gigabit Ethernet driver does not work correctly at - 1000 Mbps. Another known problem of this driver is that it runs into a - timeout after a coldstart. The system has to be rebooted at least once to - make it work.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">October 7, 2013</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.sgimips/boot.8 3.html b/static/netbsd/man8/man8.sgimips/boot.8 3.html deleted file mode 100644 index 6729f911..00000000 --- a/static/netbsd/man8/man8.sgimips/boot.8 3.html +++ /dev/null @@ -1,114 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (sgimips)</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> — <span class="Nd">sgimips - system bootstrapping procedures</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">Silicon Graphics MIPS-based computers all feature essentially - similar firmware systems. However, as of the Indigo R4x00 series (IP20), - quasi- ARCS (Advanced RISC Computing Specification) compatible features are - also present. All known PROM implementations support loading executables - from disk devices, as well as from the network via BOOTP and TFTP.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="Disk_Booting"><a class="permalink" href="#Disk_Booting">Disk - Booting</a></h1> -<p class="Pp">SGI provides a small filesystem at the beginning of each bootable - disk called a Volume Header, which contains a boot loader and other - standalone utilities. Booting <span class="Ux">NetBSD</span> requires that - we write our bootloader into to the volume header using - <a class="Xr">sgimips/sgivol(8)</a>.</p> -<p class="Pp">Once a bootloader is present in the volume header, it may be - executed directly by the PROM either manually, or at boot time using the - “OSLoader” PROM environment variable. The - <span class="Ux">NetBSD</span> bootloader will obtain the kernel filename to - boot from the PROM or EEPROM. This is specified by setting the PROM - environment variable “OSLoadFilename” to an appropriate value. - For instance, “/netbsd.ecoff”.</p> -<p class="Pp">For example, the following will configure the PROM to use the - bootloader “aoutboot” to load the kernel - “netbsd.old”</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">setenv OSLoader - aoutboot</code></code></div> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">setenv - OSLoadFilename netbsd.old</code></code></div> -</section> -<section class="Sh"> -<h1 class="Sh" id="Network_Booting"><a class="permalink" href="#Network_Booting">Network - Booting</a></h1> -<p class="Pp">The system firmware will obtain an IP address, TFTP server - address, and an optional filename from the BOOTP server and download it via - TFTP. The PROM's configurable network address environment variable - “netaddr” must match the address provided by the BOOTP - server.</p> -<p class="Pp">An example BOOTP entry for <a class="Xr">dhcpd(8)</a> follows:</p> -<div class="Bd Pp Bd-indent"> -<pre> host indigo3k { - hardware ethernet 08:00:69:42:42:42; - fixed-address 192.168.0.2; - option host-name "indigo3k.foo"; - #filename "/netbsd.ecoff"; - next-server 192.168.0.1; - option root-path "/export/indigo3k/root"; - server-name "192.168.0.1"; - }</pre> -</div> -<p class="Pp">To boot a kernel named “netbsd.ecoff” the user would - type:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">boot -f - bootp():/netbsd.ecoff</code></code></div> -<p class="Pp">See <a class="Xr">dhcpd.conf(5)</a> for more information on - configuring <a class="Xr">dhcpd(8)</a> as a BOOTP server.</p> -</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">dhcpd.conf(5)</a>, <a class="Xr">dhcpd(8)</a>, - <a class="Xr">sgimips/sgivol(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1> -<p class="Pp">Some older PROM revisions do not support loading of ELF images. - The build system automatically prepares ECOFF versions, which are correctly - interpreted.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp"><span class="Ux">NetBSD</span> does not support booting from disk - on systems lacking an ARCS-compatible firmware (presently supported systems - include Personal Iris and Indigo R3000). It is possible to work around this - by creating a sufficiently large volume header and placing the kernel in it, - or by network booting.</p> -<p class="Pp">Some firmware revisions have a bug, which precludes them from - communicating with TFTP servers using ports above 32767. When using - <span class="Ux">NetBSD</span> as the TFTP server, this problem may be - worked around as follows:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">sysctl -w - net.inet.ip.anonportmin=20000</code></code></div> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">sysctl -w - net.inet.ip.anonportmax=32767</code></code></div> -<p class="Pp">Another bug exists in some firmware revisions, which precludes the - PROM from communicating with TFTP servers that employ PMTU (Path MTU) - discovery. This bug may be worked around by disabling PMTU on the TFTP - server. This does not presently affect <span class="Ux">NetBSD</span> - servers.</p> -<p class="Pp">This man page is horribly incomplete.</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> diff --git a/static/netbsd/man8/man8.sgimips/sgivol.8 3.html b/static/netbsd/man8/man8.sgimips/sgivol.8 3.html deleted file mode 100644 index 3fe273d2..00000000 --- a/static/netbsd/man8/man8.sgimips/sgivol.8 3.html +++ /dev/null @@ -1,163 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">SGIVOL(8)</td> - <td class="head-vol">System Manager's Manual (sgimips)</td> - <td class="head-rtitle">SGIVOL(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">/usr/mdec/sgivol</code> — - <span class="Nd">configure SGI Volume Header</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">/usr/mdec/sgivol</code></td> - <td>[<code class="Fl">-fq</code>] <var class="Ar">device</var></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">/usr/mdec/sgivol</code></td> - <td>[<code class="Fl">-fq</code>] <code class="Fl">-i</code> - [<code class="Fl">-h</code> <var class="Ar">vhsize</var>] - <var class="Ar">device</var></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">/usr/mdec/sgivol</code></td> - <td>[<code class="Fl">-fq</code>] <code class="Fl">-r</code> - <var class="Ar">vhfilename</var> <var class="Ar">diskfilename</var> - <var class="Ar">device</var></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">/usr/mdec/sgivol</code></td> - <td>[<code class="Fl">-fq</code>] <code class="Fl">-w</code> - <var class="Ar">vhfilename</var> <var class="Ar">diskfilename</var> - <var class="Ar">device</var></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">/usr/mdec/sgivol</code></td> - <td>[<code class="Fl">-fq</code>] <code class="Fl">-d</code> - <var class="Ar">vhfilename</var> <var class="Ar">device</var></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">/usr/mdec/sgivol</code></td> - <td>[<code class="Fl">-fq</code>] <code class="Fl">-m</code> - <var class="Ar">vhfilename</var> <var class="Ar">vhfilename</var> - <var class="Ar">device</var></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">/usr/mdec/sgivol</code></td> - <td>[<code class="Fl">-fq</code>] <code class="Fl">-p</code> - <var class="Ar">partno</var> <var class="Ar">partfirst</var> - <var class="Ar">partblocks</var> <var class="Ar">parttype</var> - <var class="Ar">device</var></td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <code class="Nm">/usr/mdec/sgivol</code> program prepares an - SGI Volume Header to be used to boot <span class="Ux">NetBSD</span>. The SGI - PROM is able to load executables within the header, which in turn are used - to load the kernel from another file system.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="OPTIONS"><a class="permalink" href="#OPTIONS">OPTIONS</a></h1> -<p class="Pp">The following options are available:</p> -<dl class="Bl-tag"> - <dt id="f"><a class="permalink" href="#f"><code class="Fl">-f</code></a></dt> - <dd>Force the operation. Do not ask the user before proceeding.</dd> - <dt id="h"><a class="permalink" href="#h"><code class="Fl">-h</code></a></dt> - <dd>Set the size of the newly initialized volume header in blocks. One block - is 512 bytes. The default volume header size is 3135 blocks (1.53MB).</dd> - <dt id="q"><a class="permalink" href="#q"><code class="Fl">-q</code></a></dt> - <dd>Suppress output.</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="PARTITION_TYPES"><a class="permalink" href="#PARTITION_TYPES">PARTITION - TYPES</a></h1> -<p class="Pp">The numerical partition types for the volume header include:</p> -<div class="Bd Pp Bd-indent"> -<pre> 0: Volume Header - 1: Replicated Tracks - 2: Replicated Sectors - 3: Raw - 4: BSD4.2 file system - 5: SysV file system - 6: Entire Volume (all disk blocks) - 7: EFS - 8: Logical Volume - 9: Raw Logical Volume - 10: XFS - 11: XFS Log - 12: XLV Volume - 13: XVM Volume</pre> -</div> -</section> -<section class="Sh"> -<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1> -<p class="Pp">To display the existing volume header and partition table on disk - “sd0”:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">sgivol - sd0</code></code></div> -<p class="Pp">To initialize a new volume header 42 512-byte blocks large on disk - “sd0”:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">sgivol -i -h 42 - sd0</code></code></div> -<p class="Pp">To copy a file <span class="Pa">boot</span> from the volume header - to local file <span class="Pa">/tmp/boot</span> on disk - “sd0”:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">sgivol -r boot - /tmp/boot sd0</code></code></div> -<p class="Pp">To copy a local file <span class="Pa">/usr/mdec/ip2xboot</span> to - the volume header as <span class="Pa">boot</span> on disk - “sd0”:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">sgivol -w boot - /usr/mdec/ip2xboot sd0</code></code></div> -<p class="Pp">To delete the existing file <span class="Pa">boot</span> from the - volume header on disk “sd0”:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">sgivol -d boot - sd0</code></code></div> -<p class="Pp">To move (rename) an existing file <span class="Pa">file1</span> to - <span class="Pa">file2</span> in the volume header on disk - “sd0”:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">sgivol -m file1 - file2 sd0</code></code></div> -<p class="Pp">To change partition 0 to type 4 (BSD4.2) beginning at block offset - 3200 and continue for 28000 blocks on disk “sd0”:</p> -<div class="Bd Bd-indent"><code class="Li"><code class="Ic">sgivol -p 0 3200 - 28000 4 sd0</code></code></div> -</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">sgimips/boot(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> diff --git a/static/netbsd/man8/man8.sparc/binstall.8 3.html b/static/netbsd/man8/man8.sparc/binstall.8 3.html deleted file mode 100644 index e1a4e4ab..00000000 --- a/static/netbsd/man8/man8.sparc/binstall.8 3.html +++ /dev/null @@ -1,84 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BINSTALL(8)</td> - <td class="head-vol">System Manager's Manual (sparc)</td> - <td class="head-rtitle">BINSTALL(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">/usr/mdec/binstall</code> — - <span class="Nd">install sparc and sparc64 boot blocks</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">/usr/mdec/binstall</code></td> - <td>[<code class="Fl">-htUuv</code>] [<code class="Fl">-b</code> - <var class="Ar">bootprog</var>] [<code class="Fl">-f</code> - <var class="Ar">filesystem</var>] [<code class="Fl">-m</code> - <var class="Ar">mdec</var>] [<code class="Fl">-i</code> - <var class="Ar">installbootprog</var>] [“net” | - “ffs”] [directory]</td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <code class="Nm">/usr/mdec/binstall</code> program prepares a - sparc or sparc64 system for booting, either from local disk from a - “ffs” partition or over the network. The default type of boot - block installed is derived from the host system. If it is an UltraSPARC, the - sparc64 boot blocks will be used, otherwise the SPARC boot blocks will be - used. <code class="Nm">/usr/mdec/binstall</code> can be forced to prepare a - disk for either.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="OPTIONS"><a class="permalink" href="#OPTIONS">OPTIONS</a></h1> -<p class="Pp">The following options are available:</p> -<dl class="Bl-tag"> - <dt id="b"><a class="permalink" href="#b"><code class="Fl">-b</code></a></dt> - <dd>Set the second stage boot program to <var class="Ar">bootprog</var>. This - will typically be <span class="Pa">boot.net</span> for sparc systems and - <span class="Pa">ofwboot.net</span> for sparc64 systems.</dd> - <dt id="f"><a class="permalink" href="#f"><code class="Fl">-f</code></a></dt> - <dd>Set the path to the filesystem being installed for to - <var class="Ar">filesystem</var>. This is otherwise derived from the - [directory].</dd> - <dt id="h"><a class="permalink" href="#h"><code class="Fl">-h</code></a></dt> - <dd>Display help.</dd> - <dt id="i"><a class="permalink" href="#i"><code class="Fl">-i</code></a></dt> - <dd>Set the path to the <a class="Xr">installboot(8)</a> program to - <var class="Ar">installbootprog</var>. This is useful for using - <code class="Nm">/usr/mdec/binstall</code> on non-sparc or sparc64 - systems.</dd> - <dt id="m"><a class="permalink" href="#m"><code class="Fl">-m</code></a></dt> - <dd>Sets the path to the machine dependent directory to - <var class="Ar">mdec</var>. This is the directory that both the boot - blocks and the <a class="Xr">installboot(8)</a> program live.</dd> - <dt id="t"><a class="permalink" href="#t"><code class="Fl">-t</code></a></dt> - <dd>Test mode; does not run any program. Implies the - <code class="Fl">-v</code> option.</dd> - <dt id="U"><a class="permalink" href="#U"><code class="Fl">-U</code></a></dt> - <dd>Install sparc (SPARC) boot blocks.</dd> - <dt id="u"><a class="permalink" href="#u"><code class="Fl">-u</code></a></dt> - <dd>Install sparc64 (UltraSPARC) boot blocks.</dd> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Be verbose.</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">installboot(8)</a></p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">January 6, 2002</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.sparc/boot.8 3.html b/static/netbsd/man8/man8.sparc/boot.8 3.html deleted file mode 100644 index 8fc56545..00000000 --- a/static/netbsd/man8/man8.sparc/boot.8 3.html +++ /dev/null @@ -1,214 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (sparc)</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> — <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>[<code class="Fl">-adqsv</code>] [<var class="Ar">--</var> - ⟨<var class="Ar">boot string</var>⟩]</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 Sun boot firmware, either old-style or new-style (Open Boot - Prom), performs a Power On Self Test (POST), and then will boot an operating - system according to configuration in Open Firmware environment - variables.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Boot_program_options"><a class="permalink" href="#Boot_program_options">Boot - program options</a></h2> -<dl class="Bl-tag"> - <dt id="a"><a class="permalink" href="#a"><code class="Fl">-a</code></a></dt> - <dd>Prompt for the root file system device, the system crash dump device, and - the path to <a class="Xr">init(8)</a>.</dd> - <dt id="d"><a class="permalink" href="#d"><code class="Fl">-d</code></a></dt> - <dd>Bring the system up in debug mode. Here it waits for a kernel debugger - connect; see <a class="Xr">gdb(1)</a>.</dd> - <dt id="C"><a class="permalink" href="#C"><code class="Fl">-C</code></a></dt> - <dd>Boot kernel in compat mode. Starting with revision 1.14 (introduced on - 2003/03/01), the sparc boot program loads the - <span class="Ux">NetBSD</span> kernel at its linked virtual address. This - feature requires a kernel built after 2003/02/21 (corresponding to kernel - version 1.6Q). To load older kernels, the <code class="Fl">-C</code> - option must be used, which loads the kernel at physical address 0x4000. - The size of a kernel loaded in this way is limited to approximately - 3MB.</dd> - <dt id="q"><a class="permalink" href="#q"><code class="Fl">-q</code></a></dt> - <dd>Boot the system in quiet mode.</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>Bring the system up in single-user mode.</dd> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Boot the system in verbose mode.</dd> -</dl> -<p class="Pp">Any extra flags or arguments, or the ⟨<var class="Ar">boot - string</var>⟩ after the -- separator are passed to the boot PROM. - Other flags are currently ignored.</p> -<p class="Pp">The SPARC boot ROM comes in two flavours: an - “old-style” ROM is used in sun4 machines, while a - “new-style” ROM can be found on sun4c and sun4m models. The - “new-style” SPARC boot ROM is a full-featured Forth system - with emacs key bindings. It can be put in “old-style” - user-interface compatibility mode (in which case it shows a simple - ‘>’ prompt), but this is essentially useless. However, by - default on sun4c models, the ROM runs in old-mode; to enter new-mode type - ‘n’. The ROM then shows a Forth-style “ok” - prompt. It is recommended to have the ROM always start in its native - “new-style” mode. Utter the following incantation in new-mode - to force the ROM to always start in new-mode.</p> -<p class="Pp"><span class="Pa"> ok</span> setenv sunmon-compat? false</p> -<p class="Pp">The ROM will normally load the kernel from - “sd(0,0,0)vmunix”. To change the default so that - <span class="Ux">NetBSD</span> will be loaded from somewhere else, type the - following</p> -<p class="Pp"><span class="Pa"> ok</span> setenv boot-from sd(0,0,0)netbsd</p> -<p class="Pp">On newer SPARC machines, there are various aliases to access - common devices. A typical list of usable boot devices (extracted from the - output of the Open Boot PROM command <code class="Ic">devalias</code>) - is:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>floppy /obio/SUNW,fdtwo -net-aui /iommu/sbus/ledma@f,400010:aui/le@f,c00000 -net-tpe /iommu/sbus/ledma@f,400010:tpe/le@f,c00000 -net /iommu/sbus/ledma@f,400010/le@f,c00000 -disk /iommu/sbus/espdma@f,400000/esp@f,800000/sd@3,0 -cdrom /iommu/sbus/espdma@f,400000/esp@f,800000/sd@6,0:d -tape /iommu/sbus/espdma@f,400000/esp@f,800000/st@4,0 -tape1 /iommu/sbus/espdma@f,400000/esp@f,800000/st@5,0 -tape0 /iommu/sbus/espdma@f,400000/esp@f,800000/st@4,0 -disk3 /iommu/sbus/espdma@f,400000/esp@f,800000/sd@3,0 -disk2 /iommu/sbus/espdma@f,400000/esp@f,800000/sd@2,0 -disk1 /iommu/sbus/espdma@f,400000/esp@f,800000/sd@1,0 -disk0 /iommu/sbus/espdma@f,400000/esp@f,800000/sd@0,0</pre> -</div> -<p class="Pp" id="cdrom">For new-style machines, if a device specification - includes a partition letter (for example - <a class="permalink" href="#cdrom"><i class="Em">cdrom</i></a> in above - list), that partition is used by default, otherwise the first (a) partition - is used. If booting from the net device, there is no partition involved.</p> -<p class="Pp">At any time you can break back to the ROM by pressing the - ‘L1’ and ‘a’ keys at the same time (if the - console is a serial port the same is achieved by sending a - ‘break’). If you do this accidentally you can continue - whatever was in progress by typing ‘go’.</p> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="OPEN_BOOT_PROM_ENVIRONMENT_VARIABLES"><a class="permalink" href="#OPEN_BOOT_PROM_ENVIRONMENT_VARIABLES">OPEN - BOOT PROM ENVIRONMENT VARIABLES</a></h1> -<p class="Pp">This section only applies to new-style machines.</p> -<p class="Pp">All Open Boot PROM environment variables can be printed with the - <code class="Ic">printenv</code> command and changed with the - <code class="Ic">setenv</code> command. The boot process relevant variables - and their suggested value for booting <span class="Ux">NetBSD</span> - are:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>auto-boot? true -boot-file -boot-device disk -diag-switch? false</pre> -</div> -<p class="Pp" id="disk">Of course you may select any other boot device, if you - do not want to boot from the device aliased to - <a class="permalink" href="#disk"><i class="Em">disk</i></a>, see the - discussion on devices above.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="OPEN_BOOT_PROM_ABBREVIATED_COMMAND_SUMMARY"><a class="permalink" href="#OPEN_BOOT_PROM_ABBREVIATED_COMMAND_SUMMARY">OPEN - BOOT PROM ABBREVIATED COMMAND SUMMARY</a></h1> -<p class="Pp">This section only applies to new-style machines.</p> -<p class="Pp">The following Open Boot PROM commands are related to the boot - process:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>boot boot the system from the default device -boot device filename arguments - boot the specified device, filename and arguments -probe-ide list devices on the primary IDE controller -probe-ide-all list devices on all known IDE controllers -probe-scsi list devices on the primary SCSI controller -probe-scsi-all list devices on all known SCSI controllers -reset reset the system</pre> -</div> -For disk and tape devices, the boot device is specified as - ‘/path/device@target,lun:partition’. -</section> -<section class="Sh"> -<h1 class="Sh" id="PROM_MONITOR_ABBREVIATED_COMMAND_SUMMARY"><a class="permalink" href="#PROM_MONITOR_ABBREVIATED_COMMAND_SUMMARY">PROM - MONITOR ABBREVIATED COMMAND SUMMARY</a></h1> -<p class="Pp">This section only applies to old-style machines.</p> -<p class="Pp">The following PROM monitor commands are related to the boot - process:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>b boot the system from the default device -b device filename arguments - boot the specified device, filename and arguments -b? list boot device types -k2 reset the system</pre> -</div> -<p class="Pp">For SCSI disk and tape devices, the boot device is specified as - ‘device(controller,unit,partition)’, where - ‘unit’ is the hexadecimal value of the SCSI id of the target - multiplied by eight plus the lun, and ‘partition’ is the - partition number, starting from 0.</p> -</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">/boot</span></dt> - <dd>system bootstrap</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">crash(8)</a>, <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">rc(8)</a>, <a class="Xr">shutdown(8)</a>, - <a class="Xr">sparc64/boot(8)</a>, <a class="Xr">syslogd(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">On sun4 machines, the <span class="Ux">NetBSD</span> sparc boot - loader can only boot from RAID partitions that start at the beginning of the - disk.</p> -<p class="Pp">On sun4 and early PROM version sun4c machines, the PROM can only - boot from the first 1Gb of the disk.</p> -<p class="Pp">On later PROM version sun4c and early PROM version sun4m machines, - the PROM can only boot from the first 2Gb of the disk.</p> -<p class="Pp">On later PROM version sun4m machines, the PROM can only boot from - the first 4Gb of the disk.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">June 17, 2006</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.sparc64/boot.8 3.html b/static/netbsd/man8/man8.sparc64/boot.8 3.html deleted file mode 100644 index 678b466a..00000000 --- a/static/netbsd/man8/man8.sparc64/boot.8 3.html +++ /dev/null @@ -1,205 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (sparc64)</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>, <code class="Nm">ofwboot</code> - — <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>[<code class="Fl">-adqsv</code>] [<var class="Ar">--</var> - ⟨<var class="Ar">boot string</var>⟩]</td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">Sun UltraSPARC systems support booting from locally attached - storage media (e.g. hard disk, CD-ROM), and booting over Ethernet networks - using BOOTP.</p> -<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 Sun Open Firmware performs a Power On Self Test (POST), and - then will boot an operating system according to configuration in Open - Firmware environment variables.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Boot_program_options"><a class="permalink" href="#Boot_program_options">Boot - program options</a></h2> -<dl class="Bl-tag"> - <dt id="a"><a class="permalink" href="#a"><code class="Fl">-a</code></a></dt> - <dd>Prompt for the root file system device, the system crash dump device, and - the path to <a class="Xr">init(8)</a>.</dd> - <dt id="d"><a class="permalink" href="#d"><code class="Fl">-d</code></a></dt> - <dd>Bring the system up in debug mode. Here it waits for a kernel debugger - connect; see <a class="Xr">gdb(1)</a>.</dd> - <dt id="q"><a class="permalink" href="#q"><code class="Fl">-q</code></a></dt> - <dd>Boot the system in quiet mode.</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>Bring the system up in single-user mode.</dd> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Boot the system in verbose mode.</dd> -</dl> -<p class="Pp">Any extra flags or arguments, or the ⟨<var class="Ar">boot - string</var>⟩ after the -- separator are passed to the boot PROM. - Other flags are currently ignored.</p> -<p class="Pp">At any time you can halt the running system and get back to the - Open Firmware. If the console is the Sun framebuffer and keyboard, press the - ‘STOP’ and ‘A’ keys at the same time on the - keyboard. On older models of Sun keyboards, the ‘STOP’ key is - labeled ‘L1’.</p> -<p class="Pp">If the console is a serial port the same is achieved by sending a - ‘BREAK’.</p> -<p class="Pp">If you do this accidentally, you can continue whatever was in - progress with the <code class="Ic">go</code> command.</p> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="BOOT_DEVICES"><a class="permalink" href="#BOOT_DEVICES">BOOT - DEVICES</a></h1> -<p class="Pp">Since machines vary greatly in the way their devices are - connected, there are aliases defined by the firmware. You can either use the - fully qualified Open Firmware path of a device node, or the alias.</p> -<p class="Pp">The secondary boot loader, <code class="Nm">ofwboot</code>, takes - <code class="Nm">boot</code> commands virtually the same as Open Firmware. - Thus, the following examples apply equally to - <code class="Nm">ofwboot</code> as well as Open Firmware.</p> -<p class="Pp">A typical list of usable boot devices (extracted from the output - of the Open Firmware command <code class="Ic">devalias</code>) is:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>net /sbus/SUNW,hme@e,8c00000 -disk /sbus/SUNW,fas@e,8800000/sd@0,0 -cdrom /sbus/SUNW,fas@e,8800000/sd@6,0:f -disk6 /sbus/SUNW,fas@e,8800000/sd@6,0 -disk5 /sbus/SUNW,fas@e,8800000/sd@5,0 -disk4 /sbus/SUNW,fas@e,8800000/sd@4,0 -disk3 /sbus/SUNW,fas@e,8800000/sd@3,0 -disk2 /sbus/SUNW,fas@e,8800000/sd@2,0 -disk1 /sbus/SUNW,fas@e,8800000/sd@1,0 -disk0 /sbus/SUNW,fas@e,8800000/sd@0,0</pre> -</div> -<p class="Pp" id="cdrom">If a device specification includes a partition letter - (for example <a class="permalink" href="#cdrom"><i class="Em">cdrom</i></a> - in above list), that partition is used by default, otherwise the first (a) - partition is used. If booting from the net device, there is no partition - involved.</p> -<p class="Pp">The boot device is an optional first part of the boot string, if - no device is specified the default device is used (see below).</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="FIRMWARE_ENVIRONMENT_VARIABLES"><a class="permalink" href="#FIRMWARE_ENVIRONMENT_VARIABLES">FIRMWARE - ENVIRONMENT VARIABLES</a></h1> -<p class="Pp">All Open Firmware environment variables can be printed with the - <code class="Ic">printenv</code> command and changed with the - <code class="Ic">setenv</code> command. The boot process relevant variables - and their suggested value for booting <span class="Ux">NetBSD</span> - are:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>boot-command boot -auto-boot? true -boot-file -boot-device disk -diag-switch? false</pre> -</div> -<p class="Pp" id="disk">Of course you may select any other boot device, if you - do not want to boot from the device aliased to - <a class="permalink" href="#disk"><i class="Em">disk</i></a>, see the - discussion on devices above.</p> -</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">/ofwboot</span></dt> - <dd>system bootstrap</dd> - <dt><span class="Pa">/usr/mdec/ofwboot.net</span></dt> - <dd>alternate bootstrap when booting from the network, see - <a class="Xr">diskless(8)</a> for details.</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1> -<p class="Pp">Boot from CD-ROM:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>boot cdrom</pre> -</div> -<p class="Pp">Note that some multi-architecture CDs are not able to use the - default sparc64 partition for CD-ROMs (f), so they may require an explicit - partition letter, for example</p> -<div class="Bd Pp Bd-indent Li"> -<pre>boot cdrom:c</pre> -</div> -<p class="Pp">When using external SCSI CD-ROM drives it is important to know two - things: the Sun firmware expects the SCSI ID to be six, and the drive must - support 512-byte block reads, in addition to the standard 2048-byte - reads.</p> -<p class="Pp">Use</p> -<div class="Bd Pp Bd-indent Li"> -<pre>boot net -sd</pre> -</div> -<p class="Pp">to boot single user from network and break into the kernel - debugger as soon as possible.</p> -<p class="Pp">Use</p> -<div class="Bd Pp Bd-indent Li"> -<pre>boot net tftp:netbsd -a</pre> -</div> -<p class="Pp">to boot a kernel named netbsd obtained via tftp and have it ask - for root file system, swap partition and init location once it is up.</p> -<p class="Pp">During installation from a different operating system</p> -<div class="Bd Pp Bd-indent Li"> -<pre>boot disk:b</pre> -</div> -<p class="Pp">is used to boot a “miniroot” file system from the - swap partition.</p> -</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">diskless(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">rc(8)</a>, <a class="Xr">shutdown(8)</a>, - <a class="Xr">sparc/boot(8)</a>, <a class="Xr">syslogd(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="STANDARDS"><a class="permalink" href="#STANDARDS">STANDARDS</a></h1> -<p class="Pp">Sun developed its firmware and promoted it to become - <span class="St">IEEE Std 1275-1994 (“Open - Firmware”)</span>.</p> -<p class="Pp"><a class="Lk" href="http://www.openfirmware.org/1275/">IEEE 1275 - Open Firmware</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp"><span class="Ux">NetBSD</span> provides no way to boot UltraSPARC - systems from floppy disks. This is unlikely to change, due to very low - demand for this feature.</p> -<p class="Pp">The OBP on Ultra 1 and Ultra 2 machines can only boot from the - first 4Gb of the disk.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">November 9, 2008</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.sun2/boot.8 3.html b/static/netbsd/man8/man8.sun2/boot.8 3.html deleted file mode 100644 index a35eab08..00000000 --- a/static/netbsd/man8/man8.sun2/boot.8 3.html +++ /dev/null @@ -1,137 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (sun2)</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> — <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">b</code></td> - <td>[<var class="Ar">dev</var> [(<var class="Ar">cntrl</var>, - <var class="Ar">unit</var>, <var class="Ar">part</var>)]] - [<var class="Ar">file</var>] [<code class="Fl">-adqsv</code>]</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="Selecting_the_device_and_kernel_to_boot"><a class="permalink" href="#Selecting_the_device_and_kernel_to_boot">Selecting - the device and kernel to boot</a></h2> -<p class="Pp">Normally, the <code class="Nm">b</code> command alone is - sufficient to boot the system, as the PROM chooses a default boot device - <var class="Ar">dev</var> if none is specified. The PROM chooses the first - device present on the system from the following ordered list:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"> -<pre>sd SCSI disk -ie Intel Ethernet -ec 3Com Ethernet</pre> -</div> -<p class="Pp">Unless specified, the controller number - <var class="Ar">cntrl</var>, unit number <var class="Ar">unit</var>, and - partition number <var class="Ar">part</var> default to zero, which is almost - always correct.</p> -<p class="Pp">The controller number can be specified if there is more than one - of the given device in the system. For example, use “ie(1,,)” - to boot off of the second Intel Ethernet in the system.</p> -<p class="Pp">The unit number specifies one of the many devices attached to a - controller. The exact meaning and values vary depending on the device name. - For example, “sd(,18,)” boots the disk at target 6 on the - first SCSI controller, 18 being the target number 6, multiplied by 4, and - given in hexadecimal.</p> -<p class="Pp">The partition number specifies one of the many partitions on a - device. The exact meaning and values vary depending on the device name. For - example, “sd(,18,1)” boots the second partition on the disk at - target 6 on the first SCSI controller.</p> -<p class="Pp">The PROM only loads a first-stage boot program, currently either - <span class="Pa">/usr/mdec/bootxx</span> (for a disk boot), or - <span class="Pa">/usr/mdec/bootyy</span> (for a network boot). This - first-stage boot program then loads the second-stage boot program from the - same device, currently either <span class="Pa">/usr/mdec/ufsboot</span> (for - a disk boot), or <span class="Pa">/usr/mdec/netboot</span> (for a network - boot).</p> -<p class="Pp">The second-stage boot program will then attempt to load the kernel - named <var class="Ar">file</var> (or <span class="Pa">vmunix</span> if none - is specified). The second-stage disk boot program - <span class="Pa">/usr/mdec/ufsboot</span> loads the kernel from the same - device that it was loaded from, while the second-stage network boot program - <span class="Pa">/usr/mdec/netboot</span> will load the kernel from the NFS - root as determined by the procedure described in - <a class="Xr">diskless(8)</a>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Boot_program_options"><a class="permalink" href="#Boot_program_options">Boot - program options</a></h2> -<dl class="Bl-tag"> - <dt id="a"><a class="permalink" href="#a"><code class="Fl">-a</code></a></dt> - <dd>Prompt for the root file system device, the system crash dump device, and - the path to <a class="Xr">init(8)</a>.</dd> - <dt id="d"><a class="permalink" href="#d"><code class="Fl">-d</code></a></dt> - <dd>Bring the system up in debug mode. Here it waits for a kernel debugger - connect; see <a class="Xr">ddb(4)</a>.</dd> - <dt id="q"><a class="permalink" href="#q"><code class="Fl">-q</code></a></dt> - <dd>Boot the system in quiet mode.</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>Bring the system up in single-user mode.</dd> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Boot the system in verbose mode.</dd> -</dl> -<p class="Pp">Other flags are currently ignored.</p> -<p class="Pp">At any time you can break back to the ROM by pressing the - ‘L1’ and ‘a’ keys at the same time (if the - console is a serial port the same is achieved by sending a - ‘break’). If you do this accidentally you can continue - whatever was in progress by typing ‘c’ followed by the return - key.</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/bootxx</span></dt> - <dd>first-level boot block for disks</dd> - <dt><span class="Pa">/usr/mdec/bootyy</span></dt> - <dd>first-level boot block for NFS (diskless) boot</dd> - <dt><span class="Pa">/usr/mdec/netboot</span></dt> - <dd>boot program for NFS (diskless) boot</dd> - <dt><span class="Pa">/usr/mdec/ufsboot</span></dt> - <dd>second-level boot program for UFS disks</dd> - <dt><span class="Pa">/usr/sbin/installboot</span></dt> - <dd>program to install bootxx on a disk</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">crash(8)</a>, <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">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">April 29, 2003</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.sun3/boot.8 3.html b/static/netbsd/man8/man8.sun3/boot.8 3.html deleted file mode 100644 index d551add9..00000000 --- a/static/netbsd/man8/man8.sun3/boot.8 3.html +++ /dev/null @@ -1,92 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (sun3)</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> — <span class="Nd">system - bootstrapping procedures</span></p> -</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">A disk-boot program (<span class="Pa">/usr/mdec/ufsboot</span>) - will attempt to load <span class="Pa">netbsd</span> from partition A of the - boot device, which must currently be an “sd” disk. - Alternatively, network boot program - (<span class="Pa">/usr/mdec/netboot</span>) will load - <span class="Pa">netbsd</span> from the NFS root as determined by the - procedure described in <a class="Xr">diskless(8)</a>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Boot_program_options"><a class="permalink" href="#Boot_program_options">Boot - program options</a></h2> -<dl class="Bl-tag"> - <dt id="a"><a class="permalink" href="#a"><code class="Fl">-a</code></a></dt> - <dd>Prompt for the root file system device, the system crash dump device, and - the path to <a class="Xr">init(8)</a>.</dd> - <dt id="d"><a class="permalink" href="#d"><code class="Fl">-d</code></a></dt> - <dd>Bring the system up in debug mode. Here it waits for a kernel debugger - connect; see <a class="Xr">ddb(4)</a>.</dd> - <dt id="q"><a class="permalink" href="#q"><code class="Fl">-q</code></a></dt> - <dd>Boot the system in quiet mode.</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>Bring the system up in single-user mode.</dd> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Boot the system in verbose mode.</dd> -</dl> -<p class="Pp">Any extra flags or arguments, or the ⟨<var class="Ar">boot - string</var>⟩ after the -- separator are passed to the boot PROM. - Other flags are currently ignored.</p> -<p class="Pp">At any time you can break back to the ROM by pressing the - ‘L1’ and ‘a’ keys at the same time (if the - console is a serial port the same is achieved by sending a - ‘break’). If you do this accidentally you can continue - whatever was in progress by typing ‘c’ followed by the return - key.</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/bootxx</span></dt> - <dd>first-level boot block for disks</dd> - <dt><span class="Pa">/usr/mdec/netboot</span></dt> - <dd>boot program for NFS (diskless) boot</dd> - <dt><span class="Pa">/usr/mdec/ufsboot</span></dt> - <dd>second-level boot program for UFS disks</dd> - <dt><span class="Pa">/usr/mdec/installboot</span></dt> - <dd>program to install bootxx on a disk</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">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">April 8, 2003</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.vax/boot.8 3.html b/static/netbsd/man8/man8.vax/boot.8 3.html deleted file mode 100644 index 4b27750d..00000000 --- a/static/netbsd/man8/man8.vax/boot.8 3.html +++ /dev/null @@ -1,190 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (vax)</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> — <span class="Nd">system - bootstrapping procedures</span></p> -</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. Provided the auto-restart is enabled on the machine front panel, an - automatic consistency check of the file systems will be performed, 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">These are processor-type dependent. On an 11/780, there are two - floppy files for each disk controller, both of which cause boots from unit 0 - of the root file system of a controller located on mba0 or uba0. One gives a - single user shell, while the other invokes the multi-user automatic reboot. - Thus these files are HPS and HPM for the single and multi-user boot from - MASSBUS RP06/RM03/RM05 disks, UPS and UPM for UNIBUS storage module - controller and disks such as the EMULEX SC-21 and AMPEX 9300 pair, RAS and - RAM to boot from MSCP controllers and disks such as the RA81, or HKS and HKM - for RK07 disks. There is also a script for booting from the default device, - which is normally a copy of one of the standard multi-user boot scripts, but - which may be modified to perform other actions or to boot from a different - unit. The situation on the 8600 is similar, with scripts loaded from the - console RL02.</p> -<p class="Pp">Giving the command</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">>>>BOOT HPM</code></div> -<p class="Pp">would boot the system from (e.g.) an RP06 and run the automatic - consistency check as described in <a class="Xr">fsck(8)</a>. (Note that it - may be necessary to type control-P and halt the processor to gain the - attention of the LSI-11 before getting the >>> prompt.) The - command</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">>>>BOOT ANY</code></div> -<p class="Pp">invokes a version of the boot program in a way which allows you to - specify any system as the system to be booted. It reads from the console a - device specification (see below) followed immediately by a pathname.</p> -<p class="Pp">The scripts may be modified for local configuration if necessary. - The flags are placed in register 11 (as defined in - <code class="In"><<a class="In">sys/reboot.h</a>></code>). The boot - device is specified in register 10. The encoding of this register is also - defined in <code class="In"><<a class="In">sys/reboot.h</a>></code>. - The current encoding has a historical basis, and is shown in the following - table:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"> -<pre>bits usage -0-7 boot device type (the device major number) -8-15 disk partition -16-19 drive unit -20-23 controller number -24-27 adaptor number (UNIBUS or MASSBUS as appropriate)</pre> -</div> -<p class="Pp">The adaptor number corresponds to the normal configuration on the - 11/750, and to the order in which adaptors are found on the 11/780 and 8600 - (generally the same as the numbers used by - <span class="Ux">UNIX</span>).</p> -<p class="Pp">On an 11/750, the reset button will boot from the device selected - by the front panel boot device switch. In systems with RK07's, position B - normally selects the RK07 for boot. This will boot multi-user. To boot from - RK07 with boot flags you may specify</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"> -<pre><code class="Li">>>>B/</code><code class="Fl">-n</code> <span class="No">DMA0</span></pre> -</div> -<p class="Pp">where, giving a <var class="Ar">n</var> of 1 causes the boot - program to ask for the name of the system to be bootstrapped, giving a - <var class="Ar">n</var> of 2 causes the boot program to come up single user, - and a <var class="Ar">n</var> of 3 causes both of these actions to occur. - The ``DM'' specifies RK07, the ``A'' represents the adaptor number (UNIBUS - or MASSBUS), and the ``0'' is the drive unit number. Other disk types which - may be used are DB (MASSBUS), DD (TU58), and DU (UDA-50/RA disk). A non-zero - disk partition can be used by adding (partition times 1000 hex) to - <var class="Ar">n</var>.</p> -<p class="Pp">The boot procedure on the Micro VAX II is similar. A switch on the - back panel sets the power-up action to autoboot or to halt. When halted, the - processor may be booted using the same syntax as on the 11/750.</p> -<p class="Pp">The 11/750 boot procedure uses the boot ROMs to load block 0 off - of the specified device. The <span class="Pa">/usr/mdec</span> directory - contains a number of bootstrap programs for the various disks which should - be placed in a new pack by <a class="Xr">disklabel(8)</a>. Similarly, the - Micro VAX II boot procedure loads a boot parameter block from block 0 of the - disk. The <code class="Ic">rdboot</code> “bootstrap” contains - the correct parameters for an MSCP disk such as the RD53.</p> -<p class="Pp">On any processor, the <i class="Em">boot</i> program finds the - corresponding file on the given device (<span class="Pa">netbsd</span> by - default), loads that file into memory location zero, and starts the program - at the entry address specified in the program header (after clearing off the - high bit of the specified entry address).</p> -<p class="Pp">The file specifications used with “BOOT ANY” or - “B/3” are of the form:</p> -<p class="Pp"></p> -<div class="Bd - Bd-indent"><code class="Li">device(adaptor,controller,unit,minor)</code></div> -<p class="Pp">where <var class="Ar">device</var> is the type of the device to be - searched, <var class="Ar">adaptor</var> is the UNIBUS or MASSBUS number of - the adaptor to which the device is attached, - <var class="Ar">controller</var> is the unit number of the controller or - MASSBUS tape formatter on that adaptor, <var class="Ar">unit</var> is the - unit number of the disk or transport slave unit of the tape, and - <var class="Ar">minor</var> is the disk partition or tape file number. - Leading adaptor or controller numbers default to 0. Normal line editing - characters can be used when typing the file specification. The following - list of supported devices may vary from installation to installation:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"> -<pre>hp MASSBUS disk drive -up UNIBUS storage module drive -ht TE16,TU45,TU77 on MASSBUS -kra storage module on a KDB50 -mt TU78 on MASSBUS -hk RK07 on UNIBUS -ra storage module on a MSCP-compatible UNIBUS controller -rb storage module on a 730 IDC -rl RL02 on UNIBUS -tm TM11 emulation tape drives on UNIBUS -tms TMSCP-compatible tape -ts TS11 on UNIBUS -ut UNIBUS TU45 emulator</pre> -</div> -<p class="Pp">For example, to boot from a file system which starts at cylinder 0 - of unit 0 of a MASSBUS disk, type - ‘<code class="Li">hp(0,0)netbsd</code>’ to the boot prompt; - ‘<code class="Li">hp(2,0,1,0)netbsd</code>’ would specify - drive 1 on MASSBUS adaptor 2; - ‘<code class="Li">up(0,0)netbsd</code>’ would specify a UNIBUS - drive, ‘<code class="Li">hk(0,0)netbsd</code>’ would specify - an RK07 disk drive, - ‘<code class="Li">ra(1,0,0,0)netbsd</code>’ would specify a - UDA50 disk drive on a second UNIBUS, and - ‘<code class="Li">rb(0,0)netbsd</code>’ would specify a disk - on a 730 IDC. For tapes, the minor device number gives a file offset; - ‘<code class="Li">mt(1,2,3,4)</code>’ would specify the fifth - file on slave 3 of the formatter at - ‘<code class="Li">drive</code>’ 2 on mba 1.</p> -<p class="Pp">On an 11/750 with patchable control store, microcode patches will - be installed by <i class="Em">boot</i> if the file - <span class="Pa">pcs750.bin</span> exists in the root of the filesystem from - which the system is booted.</p> -<p class="Pp">In an emergency, the bootstrap methods described in the paper - <span class="RsT">Installing and Operating 4.3bsd</span> can be used to boot - from a distribution tape.</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">/boot</span></dt> - <dd>system bootstrap</dd> - <dt><span class="Pa">/usr/mdec/xxboot</span></dt> - <dd>sector 0-15 boot block</dd> - <dt><span class="Pa">/pcs750.bin</span></dt> - <dd>microcode patch file on 750</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">arff(8)</a>, <a class="Xr">halt(8)</a>, - <a class="Xr">reboot(8)</a>, <a class="Xr">shutdown(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">boot</code> command appeared in - <span class="Ux">4.0BSD</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">April 19, 1994</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.vax/crash.8 2.html b/static/netbsd/man8/man8.vax/crash.8 2.html deleted file mode 100644 index c24425b8..00000000 --- a/static/netbsd/man8/man8.vax/crash.8 2.html +++ /dev/null @@ -1,175 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">CRASH(8)</td> - <td class="head-vol">System Manager's Manual (vax)</td> - <td class="head-rtitle">CRASH(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">crash</code> — <span class="Nd">UNIX - system failures</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">This section explains what happens when the system crashes and - (very briefly) how to analyze crash dumps.</p> -<p class="Pp">When the system crashes voluntarily it prints a message of the - form</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">panic: why i gave up the - ghost</code></div> -<p class="Pp">on the console, takes a dump on a mass storage peripheral, and - then invokes an automatic reboot procedure as described in - <a class="Xr">reboot(8)</a>. (If auto-reboot is disabled on the front panel - of the machine the system will simply halt at this point.) Unless some - unexpected inconsistency is encountered in the state of the file systems due - to hardware or software failure, the system will then resume multi-user - operations.</p> -<p class="Pp">The system has a large number of internal consistency checks; if - one of these fails, then it will panic with a very short message indicating - which one failed. In many instances, this will be the name of the routine - which detected the error, or a two-word description of the inconsistency. A - full understanding of most panic messages requires perusal of the source - code for the system.</p> -<p class="Pp">The most common cause of system failures is hardware failure, - which can reflect itself in different ways. Here are the messages which are - most likely, with some hints as to causes. Left unstated in all cases is the - possibility that hardware or software error produced the message in some - unexpected way.</p> -<dl class="Bl-tag Bl-compact"> - <dt>iinit</dt> - <dd>This cryptic panic message results from a failure to mount the root - filesystem during the bootstrap process. Either the root filesystem has - been corrupted, or the system is attempting to use the wrong device as - root filesystem. Usually, an alternative copy of the system binary or an - alternative root filesystem can be used to bring up the system to - investigate.</dd> - <dt>Can't exec /sbin/init</dt> - <dd>This is not a panic message, as reboots are likely to be futile. Late in - the bootstrap procedure, the system was unable to locate and execute the - initialization process, <a class="Xr">init(8)</a>. The root filesystem is - incorrect or has been corrupted, or the mode or type of /sbin/init forbids - execution.</dd> - <dt>IO err in push</dt> - <dd style="width: auto;"> </dd> - <dt>hard IO err in swap</dt> - <dd>The system encountered an error trying to write to the paging device or an - error in reading critical information from a disk drive. The offending - disk should be fixed if it is broken or unreliable.</dd> - <dt>realloccg: bad optim</dt> - <dd style="width: auto;"> </dd> - <dt>ialloc: dup alloc</dt> - <dd style="width: auto;"> </dd> - <dt>alloccgblk: cyl groups corrupted</dt> - <dd style="width: auto;"> </dd> - <dt>ialloccg: map corrupted</dt> - <dd style="width: auto;"> </dd> - <dt>free: freeing free block</dt> - <dd style="width: auto;"> </dd> - <dt>free: freeing free frag</dt> - <dd style="width: auto;"> </dd> - <dt>ifree: freeing free inode</dt> - <dd style="width: auto;"> </dd> - <dt>alloccg: map corrupted</dt> - <dd>These panic messages are among those that may be produced when filesystem - inconsistencies are detected. The problem generally results from a failure - to repair damaged filesystems after a crash, hardware failures, or other - condition that should not normally occur. A filesystem check will normally - correct the problem.</dd> - <dt>timeout table overflow</dt> - <dd>This really shouldn't be a panic, but until the data structure involved is - made to be extensible, running out of entries causes a crash. If this - happens, make the timeout table bigger.</dd> - <dt>KSP not valid</dt> - <dd style="width: auto;"> </dd> - <dt>SBI fault</dt> - <dd style="width: auto;"> </dd> - <dt>CHM? in kernel</dt> - <dd>These indicate either a serious bug in the system or, more often, a glitch - or failing hardware. If SBI faults recur, check out the hardware or call - field service. If the other faults recur, there is likely a bug somewhere - in the system, although these can be caused by a flakey processor. Run - processor microdiagnostics.</dd> - <dt id="description">machine check %x: - <a class="permalink" href="#description"><i class="Em">description</i></a></dt> - <dd style="width: auto;"> </dd> - <dt>   machine dependent machine-check information</dt> - <dd>Machine checks are different on each type of CPU. Most of the internal - processor registers are saved at the time of the fault and are printed on - the console. For most processors, there is one line that summarizes the - type of machine check. Often, the nature of the problem is apparent from - this message and/or the contents of key registers. The VAX Hardware - Handbook should be consulted, and, if necessary, your friendly field - service people should be informed of the problem.</dd> - <dt>trap type %d, code=%x, pc=%x</dt> - <dd>A unexpected trap has occurred within the system; the trap types are: - <div class="Bd Pp Bd-indent Li"> - <pre>0 reserved addressing fault -1 privileged instruction fault -2 reserved operand fault -3 bpt instruction fault -4 xfc instruction fault -5 system call trap -6 arithmetic trap -7 ast delivery trap -8 segmentation fault -9 protection fault -10 trace trap -11 compatibility mode fault -12 page fault -13 page table fault</pre> - </div> - <p class="Pp">The favorite trap types in system crashes are trap types 8 and - 9, indicating a wild reference. The code is the referenced address, and - the pc at the time of the fault is printed. These problems tend to be - easy to track down if they are kernel bugs since the processor stops - cold, but random flakiness seems to cause this sometimes. The debugger - can be used to locate the instruction and subroutine corresponding to - the PC value. If that is insufficient to suggest the nature of the - problem, more detailed examination of the system status at the time of - the trap usually can produce an explanation.</p> - </dd> - <dt>init died</dt> - <dd>The system initialization process has exited. This is bad news, as no new - users will then be able to log in. Rebooting is the only fix, so the - system just does it right away.</dd> - <dt>out of mbufs: map full</dt> - <dd>The network has exhausted its private page map for network buffers. This - usually indicates that buffers are being lost, and rather than allow the - system to slowly degrade, it reboots immediately. The map may be made - larger if necessary.</dd> -</dl> -<p class="Pp">That completes the list of panic types you are likely to see.</p> -<p class="Pp">When the system crashes it writes (or at least attempts to write) - an image of memory into the back end of the dump device, usually the same as - the primary swap area. After the system is rebooted, the program - <a class="Xr">savecore(8)</a> runs and preserves a copy of this core image - and the current system in a specified directory for later perusal. See - <a class="Xr">savecore(8)</a> for details.</p> -<p class="Pp">To analyze a dump you should begin by running - <code class="Ic">adb</code> with the <code class="Fl">-k</code> flag on the - system load image and core dump. If the core image is the result of a panic, - the panic message is printed. Normally the command “$c” will - provide a stack trace from the point of the crash and this will provide a - clue as to what went wrong. For more detail see “Using ADB to Debug - the UNIX Kernel”.</p> -</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">gdb(1)</a>, <a class="Xr">reboot(8)</a> - <br/> - “VAX 11/780 System Maintenance Guide” and “VAX Hardware - Handbook” for more information about machine checks. - <br/> - “Using ADB to Debug the UNIX Kernel”</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> diff --git a/static/netbsd/man8/man8.vax/drtest.8 3.html b/static/netbsd/man8/man8.vax/drtest.8 3.html deleted file mode 100644 index 5d8aad9f..00000000 --- a/static/netbsd/man8/man8.vax/drtest.8 3.html +++ /dev/null @@ -1,85 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">DRTEST(8)</td> - <td class="head-vol">System Manager's Manual (vax)</td> - <td class="head-rtitle">DRTEST(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">drtest</code> — - <span class="Nd">stand-alone disk test program</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">drtest</code> is a stand-alone program used to - read a disk track by track. It was primarily intended as a test program for - new stand-alone drivers, but has shown useful in other contexts as well, - such as verifying disks and running speed tests. For example, when a disk - has been formatted (by <a class="Xr">vax/format(8)</a>), you can check that - hard errors has been taken care of by running - <code class="Nm">drtest</code>. No hard errors should be found, but in many - cases quite a few soft ECC errors will be reported.</p> -<p class="Pp">While <code class="Nm">drtest</code> is running, the cylinder - number is printed on the console for every 10th cylinder read.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1> -<p class="Pp">A sample run of <code class="Nm">drtest</code> is shown below. In - this example (using a 750), <code class="Nm">drtest</code> is loaded from - the root file system; usually it will be loaded from the machine's console - storage device. Boldface means user input. As usual, ``#'' and ``@'' may be - used to edit input.</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"> -<pre><code class="Li">>>></code><a class="permalink" href="#B/3"><b class="Sy" id="B/3">B/3</b></a> -<code class="Li">%%</code> -<code class="Li">loading hk(0,0)boot</code> -<code class="Li">Boot</code> -<code class="Li">:</code> <a class="permalink" href="#hk(0,0)drtest"><b class="Sy" id="hk(0,0)drtest">hk(0,0)drtest</b></a> -<code class="Li">Test program for stand-alone up and hp driver</code> -<mark id="hp(0,0)"></mark> -<code class="Li">Debugging level (1=bse, 2=ecc, 3=bse+ecc)?</code> -<code class="Li">Enter disk name [type(adapter,unit), e.g. hp(1,3)]?</code> <a class="permalink" href="#hp(0,0)"><b class="Sy">hp(0,0)</b></a> -<code class="Li">Device data: #cylinders=1024, #tracks=16, #sectors=32</code> -<code class="Li">Testing hp(0,0), chunk size is 16384 bytes.</code> -<a class="permalink" href="#(chunk"><i class="Em" id="(chunk">(chunk size is the number of bytes read per disk access)</i></a> -<code class="Li">Start ...Make sure hp(0,0) is online</code> -<code class="Li"> ...</code> -<a class="permalink" href="#(errors"><i class="Em" id="(errors">(errors are reported as they occur)</i></a> -<code class="Li"> ...</code> -<a class="permalink" href="#(...program"><i class="Em" id="(...program">(...program restarts to allow checking other disks)</i></a> -<a class="permalink" href="#(...to"><i class="Em" id="(...to">(...to abort halt machine with ^P)</i></a></pre> -</div> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<p class="Pp">The diagnostics are intended to be self explanatory. Note, - however, that the device number in the diagnostic messages is identified as - <a class="permalink" href="#typeX"><i class="Em" id="typeX">typeX</i></a> - instead of - <a class="permalink" href="#type(a,u)"><i class="Em" id="type(a,u)">type(a,u)</i></a> - where <var class="Ar">X</var> = a*8+u, e.g., hp(1,3) becomes hp11.</p> -</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">bad144(8)</a>, <a class="Xr">vax/format(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">drtest</code> command appeared in - <span class="Ux">4.2BSD</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp"><span class="An">Helge Skrivervik</span></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> diff --git a/static/netbsd/man8/man8.vax/format.8 3.html b/static/netbsd/man8/man8.vax/format.8 3.html deleted file mode 100644 index 9e7a3a19..00000000 --- a/static/netbsd/man8/man8.vax/format.8 3.html +++ /dev/null @@ -1,220 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">FORMAT(8)</td> - <td class="head-vol">System Manager's Manual (vax)</td> - <td class="head-rtitle">FORMAT(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">format</code> — <span class="Nd">how to - format disk packs</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">There are two ways to format disk packs. The simplest is to use - the <code class="Nm">format</code> program. The alternative is to use the - DEC standard formatting software which operates under the DEC diagnostic - supervisor. This manual page describes the operation of - <code class="Nm">format</code>, then concludes with some remarks about using - the DEC formatter.</p> -<p class="Pp"><code class="Nm">format</code> is a standalone program used to - format and check disks prior to constructing file systems. In addition to - the formatting operation, <code class="Nm">format</code> records any bad - sectors encountered according to DEC standard 144. Formatting is performed - one track at a time by writing the appropriate headers and a test pattern - and then checking the sector by reading and verifying the pattern, using the - controller's ECC for error detection. A sector is marked bad if an - unrecoverable media error is detected, or if a correctable ECC error too - many bits in length is detected (such errors are indicated as - “ECC” in the summary printed upon completing the format - operation). After the entire disk has been formatted and checked, the total - number of errors are reported, any bad sectors and skip sectors are marked, - and a bad sector forwarding table is written to the disk in the first five - even numbered sectors of the last track. It is also possible to reformat - sections of the disk in units of tracks. <code class="Nm">format</code> may - be used on any UNIBUS or MASSBUS drive supported by the <i class="Em">up</i> - and <i class="Em">hp</i> device drivers which uses 4-byte headers - (everything except RP's).</p> -<p class="Pp">The test pattern used during the media check may be selected from - one of: 0xf00f (RH750 worst case), 0xec6d (media worst case), and 0xa5a5 - (alternating 1's and 0's). Normally the media worst case pattern is - used.</p> -<p class="Pp"><code class="Nm">format</code> also has an option to perform an - extended “severe burn-in”, which makes a number of passes - using different patterns. The number of passes can be selected at run time, - up to a maximum of 48, with provision for additional passes or termination - after the preselected number of passes. This test runs for many hours, - depending on the disk and processor.</p> -<p class="Pp">Each time <code class="Nm">format</code> is run to format an - entire disk, a completely new bad sector table is generated based on errors - encountered while formatting. The device driver, however, will always - attempt to read any existing bad sector table when the device is first - opened. Thus, if a disk pack has never previously been formatted, or has - been formatted with different sectoring, five error messages will be printed - when the driver attempts to read the bad sector table; these diagnostics - should be ignored.</p> -<p class="Pp">Formatting a 400 megabyte disk on a MASSBUS disk controller - usually takes about 20 minutes. Formatting on a UNIBUS disk controller takes - significantly longer. For every hundredth cylinder formatted - <code class="Nm">format</code> prints a message indicating the current - cylinder being formatted. (This message is just to reassure people that - nothing is amiss.)</p> -<p class="Pp" id="zz(x,y)"><code class="Nm">format</code> uses the standard - notation of the standalone I/O library in identifying a drive to be - formatted. A drive is specified as - <a class="permalink" href="#zz(x,y)"><i class="Em">zz(x,y)</i></a>, where - <a class="permalink" href="#zz"><i class="Em" id="zz">zz</i></a> refers to - the controller type (either <i class="Em">hp</i> or <i class="Em">up</i>), - <i class="Em">x</i> is the unit number of the drive; 8 times the UNIBUS or - MASSBUS adaptor number plus the MASSBUS drive number or UNIBUS drive unit - number; and <a class="permalink" href="#y"><i class="Em" id="y">y</i></a> is - the file system partition on drive <i class="Em">x</i> (this should always - be 0). For example, “hp(1,0)” indicates that drive 1 on - MASSBUS adaptor 0 should be formatted; while “up(10,0)” - indicates that UNIBUS drive 2 on UNIBUS adaptor 1 should be formatted.</p> -<p class="Pp">Before each formatting attempt, <code class="Nm">format</code> - prompts the user in case debugging should be enabled in the appropriate - device driver. A carriage return disables debugging information.</p> -<p class="Pp"><code class="Nm">format</code> should be used prior to building - file systems (with <a class="Xr">newfs(8)</a> to ensure that all sectors - with uncorrectable media errors are remapped. If a drive develops - uncorrectable defects after formatting, either <a class="Xr">bad144(8)</a> - or <a class="Xr">badsect(8)</a> should be able to avoid the bad sectors.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1> -<p class="Pp">A sample run of <code class="Nm">format</code> is shown below. In - this example (using a VAX-11/780), <code class="Nm">format</code> is loaded - from the console floppy; on an 11/750 <code class="Nm">format</code> will be - loaded from the root file system with <a class="Xr">vax/boot(8)</a> - following a “B/3” command. Boldface means user input. As - usual, “#” and “@” may be used to edit - input.</p> -<div class="Bd Pp Bd-indent Li"> -<pre>>>><b>L FORMAT</b> - LOAD DONE, 00004400 BYTES LOADED ->>><b>S 2</b> -Disk format/check utility - -Enable debugging (0=none, 1=bse, 2=ecc, 3=bse+ecc)? <b>0</b> -Device to format? <b>hp(8,0)</b> -(<i>error messages may occur as old bad sector table is read</i>) -Formatting drive hp0 on adaptor 1: verify (yes/no)? <b>yes</b> -Device data: #cylinders=842, #tracks=20, #sectors=48 -Starting cylinder (0): -Starting track (0): -Ending cylinder (841): -Ending track (19): -Available test patterns are:</pre> -</div> -<div class="Bd Bd-indent Li"> -<pre>1 - (f00f) RH750 worst case -2 - (ec6d) media worst case -3 - (a5a5) alternating 1's and 0's -4 - (ffff) Severe burnin (up to 48 passes)</pre> -</div> -<div class="Bd Bd-indent Li"> -<pre>Pattern (one of the above, other to restart)? <b>2</b> -Maximum number of bit errors to allow for soft ECC (3): -Start formatting...make sure the drive is online - ... -(<i>soft ecc's and other errors are reported as they occur</i>) - ... -(<i>if 4 write check errors were found, the program terminates like this...</i>) - ... -Errors: -Bad sector: 0 -Write check: 4 -Hard ECC: 0 -Other hard: 0 -Marked bad: 0 -Skipped: 0 -Total of 4 hard errors revectored. -Writing bad sector table at block 808272 -(<i>808272 is the block # of the first block in the bad sector table</i>) -Done -(<i>...program restarts to allow formatting other disks</i>) -(<i>...to abort halt machine with ^P</i>)</pre> -</div> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<p class="Pp">The diagnostics are intended to be self explanatory.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="USING_DEC_SOFTWARE_TO_FORMAT"><a class="permalink" href="#USING_DEC_SOFTWARE_TO_FORMAT">USING - DEC SOFTWARE TO FORMAT</a></h1> -<p class="Pp"><a class="permalink" href="#Warning:"><i class="Em" id="Warning:">Warning: - These instructions are for people with 11/780 CPUs.</i></a> The steps needed - for 11/750 or 11/730 CPU's are similar, but not covered in detail here.</p> -<p class="Pp">The formatting procedures are different for each type of disk. - Listed here are the formatting procedures for RK07's, RP0X, and RM0X - disks.</p> -<p class="Pp">You should shut down UNIX and halt the machine to do any disk - formatting. Make certain you put in the pack you want formatted. It is also - a good idea to spin down or write protect the disks you don't want to - format, just in case.</p> -<section class="Ss"> -<h2 class="Ss" id="Formatting_an_RK07"><a class="permalink" href="#Formatting_an_RK07">Formatting - an RK07</a></h2> -<p class="Pp">Load the console floppy labeled, “RX11 VAX DSK LD DEV - #1” in the console disk drive, and type the following commands:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>>>>BOOT -DIAGNOSTIC SUPERVISOR. ZZ-ESSAA-X5.0-119 23-JAN-1980 12:44:40.03 -DS>ATTACH DW780 SBI DW0 3 5 -DS>ATTACH RK611 DMA -DS>ATTACH RK07 DW0 DMA0 -DS>SELECT DMA0 -DS>LOAD EVRAC -DS>START/SEC:PACKINIT</pre> -</div> -</section> -<section class="Ss"> -<h2 class="Ss" id="Formatting_an_RP0X"><a class="permalink" href="#Formatting_an_RP0X">Formatting - an RP0X</a></h2> -<p class="Pp">Follow the above procedures except that the ATTACH and SELECT - lines should read:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>DS>ATTACH RH780 SBI RH0 8 5 -DS>ATTACH RP0X RH0 DBA0 (RP0X is, e.g., RP06) -DS>SELECT DBA0</pre> -</div> -<p class="Pp">This is for drive 0 on mba0; use 9 instead of 8 for mba1, etc.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Formatting_an_RM0X"><a class="permalink" href="#Formatting_an_RM0X">Formatting - an RM0X</a></h2> -<p class="Pp">Follow the above procedures except that the ATTACH and SELECT - lines should read:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>DS>ATTACH RH780 SBI RH0 8 5 -DS>ATTACH RM0X RH0 DRA0 -DS>SELECT DRA0</pre> -</div> -<p class="Pp">Don't forget to put your UNIX console floppy back in the floppy - disk drive.</p> -</section> -</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">bad144(8)</a>, <a class="Xr">badsect(8)</a>, - <a class="Xr">newfs(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">An equivalent facility should be available which operates under a - running UNIX system.</p> -<p class="Pp">It should be possible to reformat or verify part or all of a disk, - then update the existing bad sector table.</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> diff --git a/static/netbsd/man8/man8.x68k/boot.8 3.html b/static/netbsd/man8/man8.x68k/boot.8 3.html deleted file mode 100644 index f069b3f4..00000000 --- a/static/netbsd/man8/man8.x68k/boot.8 3.html +++ /dev/null @@ -1,193 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (x68k)</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> — <span class="Nd">system - bootstrapping procedures</span></p> -</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, 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 X68000/X68030 system boots from the device which is determined - by the configuration of battery-backuped SRAM. By default, the boot ROM - attempts to boot from floppy disk drives (from 0 to 3) first, and then - attempts to boot from hard disk (SASI or SCSI). On the - <span class="Ux">NetBSD</span>/x68k, booting from SCSI disks (sd??) and 2HD - floppy disks (fd?a, fd?c) is currently supported.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Bootstrapping_from_a_floppy"><a class="permalink" href="#Bootstrapping_from_a_floppy">Bootstrapping - from a floppy</a></h2> -<p class="Pp">When the floppy disk is selected as the boot device, the initial - program loader of the IOCS (firmware) reads the - <span class="Pa">fdboot_ufs</span> program at the top of the disk, and then - the fdboot_ufs program loads the <span class="Pa">/boot</span> program from - the FFS or LFS file system. Normally, the <span class="Pa">/boot</span> - program then loads the <span class="Ux">NetBSD</span> kernel - <span class="Pa">/netbsd</span> from the same floppy. In addition, the - <span class="Pa">/boot</span> program has abilities to uncompress gzip'ed - kernels, to read the kernel from other disks of other file systems etc (see - below).</p> -<p class="Pp">For floppy disks, <span class="Pa">fdboot_ustar</span> is also - provided to read large kernels which do not fit one a single floppy.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Bootstrapping_from_a_SCSI_hard_disk"><a class="permalink" href="#Bootstrapping_from_a_SCSI_hard_disk">Bootstrapping - from a SCSI hard disk</a></h2> -<p class="Pp">When a SCSI hard disk is selected as the boot device, the initial - program loader on the SCSI host adapter's ROM reads the operating - system-independent IPL menu program at the top of the disk. The IPL menu - program recognizes the partition table, and selects the partition to read - the operating system kernel. During this phase, when the HELP key on the - keyboard is pressed, the IPL menu program displays the partition menu of - that disk to prompt the user to select the boot partition (although the - <span class="Ux">NetBSD</span> implementation of the IPL menu, - <span class="Pa">/usr/mdec/mboot</span>, does not have this - functionality).</p> -<p class="Pp">Next, the IPL menu reads the OS-dependent boot program from the - top of the selected partition. For <span class="Ux">NetBSD</span> FFS/LFS - file systems <span class="Pa">sdboot_ufs</span> is used. The - <span class="Pa">sdboot_ufs</span> program then loads the - <span class="Pa">/boot</span> program from that partition.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Normal_Operation"><a class="permalink" href="#Normal_Operation">Normal - Operation</a></h2> -<p class="Pp">Once running, a banner similar to the following will appear:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>NetBSD Multi-boot, Revision 1.1 -(user@buildhost, builddate) -Press return to boot now, any other key for boot menu -booting sd0a:netbsd - starting in 5</pre> -</div> -<p class="Pp">After a countdown, the system image listed will be loaded. (In the - example above, it will be - “<code class="Li">sd0a:netbsd</code>” which is the file - <code class="Nm">netbsd</code> on partition “a” of the - <span class="Ux">NetBSD</span> SCSI hard disk of ID 0. Pressing a key within - the time limit will enter interactive mode.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Interactive_mode"><a class="permalink" href="#Interactive_mode">Interactive - mode</a></h2> -<p class="Pp">In interactive mode, the boot loader will present a prompt, - allowing input of these commands:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="boot"><a class="permalink" href="#boot"><code class="Ic">boot</code></a> - [<var class="Ar">device</var>:][<var class="Ar">filename</var>] - [<code class="Fl">-adqsv</code>]</dt> - <dd>The default <var class="Ar">device</var> will be set to the disk that the - boot loader was loaded from. To boot from an alternate disk, the full name - of the device should be given at the prompt. <var class="Ar">device</var> - is of the form - <var class="Ar">xd</var>[<var class="Ar">N</var>[<var class="Ar">x</var>]] - where <var class="Ar">xd</var> is the device from which to boot, - <var class="Ar">N</var> is the unit number, and <var class="Ar">x</var> is - the partition letter. - <p class="Pp">The following list of supported devices may vary from - installation to installation:</p> - <p class="Pp"></p> - <dl class="Bl-hang Bl-compact"> - <dt>sd</dt> - <dd>SCSI disks on a controller recognized by the IOCS. The unit number is - the SCSI ID.</dd> - <dt>fd</dt> - <dd>Floppy drives as numbered by the IOCS.</dd> - </dl> - <p class="Pp">The default <var class="Ar">filename</var> is - <span class="Pa">netbsd</span>; if the boot loader fails to successfully - open that image, it then tries <span class="Pa">netbsd.gz</span> - (expected to be a kernel image compressed by <a class="Xr">gzip(1)</a>). - Alternate system images can be loaded by just specifying the name of the - image.</p> - <p class="Pp">Options are:</p> - <dl class="Bl-tag"> - <dt id="a"><a class="permalink" href="#a"><code class="Fl">-a</code></a></dt> - <dd>Prompt for the root file system device, the system crash dump device, - and the path to <a class="Xr">init(8)</a>.</dd> - <dt id="d"><a class="permalink" href="#d"><code class="Fl">-d</code></a></dt> - <dd>Bring the system up in debug mode. Here it waits for a kernel debugger - connect; see <a class="Xr">ddb(4)</a>.</dd> - <dt id="q"><a class="permalink" href="#q"><code class="Fl">-q</code></a></dt> - <dd>Boot the system in quiet mode.</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>Bring the system up in single-user mode.</dd> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Boot the system in verbose mode.</dd> - </dl> - </dd> - <dt id="help"><a class="permalink" href="#help"><code class="Ic">help</code></a></dt> - <dd>Print an overview about commands and arguments.</dd> - <dt id="ls"><a class="permalink" href="#ls"><code class="Ic">ls</code></a> - [<span class="Pa">path</span>]</dt> - <dd>Print a directory listing of <span class="Pa">path</span>, containing - inode number, filename and file type. <span class="Pa">path</span> can - contain a device specification.</dd> - <dt id="halt"><a class="permalink" href="#halt"><code class="Ic">halt</code></a></dt> - <dd>Reboot the system.</dd> -</dl> -</div> -</section> -<section class="Ss"> -<h2 class="Ss" id="Model-specific_notes"><a class="permalink" href="#Model-specific_notes">Model-specific - notes</a></h2> -<p class="Pp">Note for X68030+MC68030 systems: Nothing special to be attended - to; you can boot <span class="Ux">NetBSD</span> just like as other operating - systems such as Human68k and OS-9.</p> -<p class="Pp">Note for X68030/040turbo(68040 accelerator by BEEPs) systems: - <span class="Ux">NetBSD</span> can boot under 040 mode. It can also boot - under 030 mode if you have MC68030 on the board.</p> -<p class="Pp">Note for X68000/Xellent30(68030 accelerator by TSR)+MC68030 - systems: In order to boot <span class="Ux">NetBSD</span>, you must choose - 030 mode by using <span class="Pa">CH30.SYS</span>, which must reside in the - battery-backuped SRAM.</p> -<p class="Pp">Note for X68000/Jupiter-X(68040/060 accelerator by FTZ-net) - systems: The system must be in 040/060 processor mode.</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">/netbsd.gz</span></dt> - <dd>gzip-compressed system code</dd> - <dt><span class="Pa">/usr/mdec/xxboot_ufs</span></dt> - <dd>boot block (read by installboot), xx is disktype</dd> - <dt><span class="Pa">/usr/mdec/boot</span></dt> - <dd>source of /boot (can be just copied to the root directory)</dd> - <dt><span class="Pa">/boot</span></dt> - <dd>main part of the boot program</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">reboot(2)</a>, <a class="Xr">disklabel(8)</a>, - <a class="Xr">halt(8)</a>, <a class="Xr">reboot(8)</a>, - <a class="Xr">shutdown(8)</a></p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">August 16, 2014</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.x68k/loadbsd.8 3.html b/static/netbsd/man8/man8.x68k/loadbsd.8 3.html deleted file mode 100644 index ee2e8bab..00000000 --- a/static/netbsd/man8/man8.x68k/loadbsd.8 3.html +++ /dev/null @@ -1,130 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">LOADBSD(8)</td> - <td class="head-vol">System Manager's Manual (x68k)</td> - <td class="head-rtitle">LOADBSD(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">loadbsd</code> — <span class="Nd">load and - boot NetBSD/x68k kernel from Human68k</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">loadbsd.x</code></td> - <td>[<code class="Fl">-hvV</code>] [<code class="Fl">-abDNqs</code>] - [<code class="Fl">-r</code> <var class="Ar">root_device</var>] - <var class="Ar">kernel_file</var></td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">loadbsd</code> is a program runs on Human68k. It - loads and executes the specified <span class="Ux">NetBSD</span>/x68k - kernel.</p> -<p class="Pp">The options (for <code class="Nm">loadbsd</code> itself) are as - follows:</p> -<dl class="Bl-tag"> - <dt id="h"><a class="permalink" href="#h"><code class="Fl">-h</code></a></dt> - <dd>Show help and exit.</dd> - <dt id="N"><a class="permalink" href="#N"><code class="Fl">-N</code></a></dt> - <dd>Do not execute the kernel, if specified in combination with boot - options.</dd> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Enable verbose mode.</dd> - <dt id="V"><a class="permalink" href="#V"><code class="Fl">-V</code></a></dt> - <dd>Print version of <code class="Nm">loadbsd</code> and exit.</dd> -</dl> -<p class="Pp">The options for <span class="Ux">NetBSD</span> kernel are as - follows:</p> -<dl class="Bl-tag"> - <dt id="a"><a class="permalink" href="#a"><code class="Fl">-a</code></a></dt> - <dd>Auto (multi-user) boot. This disables <code class="Fl">-s</code> - flag.</dd> - <dt id="b"><a class="permalink" href="#b"><code class="Fl">-b</code></a></dt> - <dd>Ask boot device during boot. Pass <code class="Dv">RB_ASKNAME</code> boot - flag to the kernel.</dd> - <dt id="D"><a class="permalink" href="#D"><code class="Fl">-D</code></a></dt> - <dd>Enter kernel debugger. Pass <code class="Dv">RB_KDB</code> boot flag to - the kernel.</dd> - <dt id="r"><a class="permalink" href="#r"><code class="Fl">-r</code></a> - <var class="Ar">root_device</var></dt> - <dd>Specify boot device, which shall be mounted as root device. The default - device is ‘<code class="Li">sd@0,0:a</code>’. Note that the - boot device name is - <a class="permalink" href="#not"><i class="Em" id="not">not</i></a> the - same as that of <span class="Ux">NetBSD</span>. See - <a class="Sx" href="#BOOT_DEVICE_NAMES">BOOT DEVICE NAMES</a> below.</dd> - <dt id="q"><a class="permalink" href="#q"><code class="Fl">-q</code></a></dt> - <dd>Boot the system in quiet mode. Pass <code class="Dv">AB_QUIET</code> boot - flag to the kernel.</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>Single user boot. Pass <code class="Dv">RB_SINGLE</code> boot flag to the - kernel. This disables <code class="Fl">-a</code> flag. This flag is set by - default.</dd> -</dl> -<p class="Pp">Although listed separately, the options may be in any order.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BOOT_DEVICE_NAMES"><a class="permalink" href="#BOOT_DEVICE_NAMES">BOOT - DEVICE NAMES</a></h1> -<p class="Pp">The format of boot device names is:</p> -<p class="Pp"></p> -<div class="Bd - Bd-indent"><code class="Li">[/interface/]dev@unit[,lun][:partition]</code></div> -<dl class="Bl-tag"> - <dt>interface</dt> - <dd>SCSI interface type. One of: - ‘<code class="Li">spc@0</code>’, - ‘<code class="Li">spc@1</code>’, - ‘<code class="Li">mha@0</code>’. If the dev is a SCSI - device, and interface is omitted, the current boot interface is used.</dd> - <dt>dev</dt> - <dd>Device type. One of: ‘<code class="Li">fd</code>’ (floppy - disk drive), ‘<code class="Li">sd</code>’ (SCSI disk), - ‘<code class="Li">cd</code>’ (SCSI CD-ROM), - ‘<code class="Li">md</code>’ (Memory disk).</dd> - <dt>unit</dt> - <dd>Device unit #. You must specify the target SCSI ID if dev is a SCSI - device.</dd> - <dt>lun</dt> - <dd>SCSI LUN #. 0 is assumed if omitted.</dd> - <dt>partition</dt> - <dd>Partition letter of device. Partition - ‘<code class="Li">a</code>’ is used if omitted.</dd> -</dl> -</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">/usr/mdec/loadbsd.x</span></dt> - <dd>You will find this program here.</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">reboot(2)</a>, <a class="Xr">x68k/boot(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">loadbsd</code> utility first appeared in - <span class="Ux">NetBSD 1.4</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp"><code class="Nm">loadbsd</code> reads the entire kernel image at - once, and requires enough free area on the main memory.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">December 23, 2023</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.x68k/newdisk.8 3.html b/static/netbsd/man8/man8.x68k/newdisk.8 3.html deleted file mode 100644 index 75ed50c2..00000000 --- a/static/netbsd/man8/man8.x68k/newdisk.8 3.html +++ /dev/null @@ -1,80 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">NEWDISK(8)</td> - <td class="head-vol">System Manager's Manual (x68k)</td> - <td class="head-rtitle">NEWDISK(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">newdisk</code> — <span class="Nd">Prepare - a new disk to be usable for X680x0</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">newdisk</code></td> - <td>[<code class="Fl">-vnfcp</code>] [<code class="Fl">-m</code> - <var class="Ar">mboot</var>] <var class="Ar">raw_device</var></td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">newdisk</code> prepares a new hard disk to be - bootable from by X680x0. It should NOT be used for floppy disks.</p> -<p class="Pp">It creates a disk mark for IOCS to determine the disk geometry, - writes the primary boot program (mboot), and creates empty partition table. - The option are as follows:</p> -<dl class="Bl-tag"> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Verbose mode.</dd> - <dt id="n"><a class="permalink" href="#n"><code class="Fl">-n</code></a></dt> - <dd>Dryrun mode. Nothing is written to the disk.</dd> - <dt id="f"><a class="permalink" href="#f"><code class="Fl">-f</code></a></dt> - <dd>Force. Usually, when <code class="Nm">newdisk</code> detects existing disk - mark, it aborts with some error messages. <code class="Fl">-f</code> - option prevents this behaviour.</dd> - <dt id="c"><a class="permalink" href="#c"><code class="Fl">-c</code></a></dt> - <dd>Check only. <code class="Nm">newdisk</code> looks at the disk whether it - is already marked.</dd> - <dt id="p"><a class="permalink" href="#p"><code class="Fl">-p</code></a></dt> - <dd>Do not create the partition table.</dd> - <dt id="m"><a class="permalink" href="#m"><code class="Fl">-m</code></a> - <var class="Ar">mboot</var></dt> - <dd>Specifies the mboot program to be written.</dd> -</dl> -</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">/usr/mdec/mboot</span></dt> - <dd>The default primary boot program.</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">installboot(8)</a>, - <a class="Xr">x68k/boot(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">newdisk</code> utility first appeared in - <span class="Ux">NetBSD 1.5</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp"><code class="Nm">newdisk</code> was written by - <span class="An">MINOURA Makoto</span> - <<a class="Mt" href="mailto:minoura@NetBSD.org">minoura@NetBSD.org</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> diff --git a/static/netbsd/man8/man8.x86/boot.8 3.html b/static/netbsd/man8/man8.x86/boot.8 3.html deleted file mode 100644 index 3b446c36..00000000 --- a/static/netbsd/man8/man8.x86/boot.8 3.html +++ /dev/null @@ -1,705 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT(8)</td> - <td class="head-vol">System Manager's Manual (x86)</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> — <span class="Nd">system - bootstrapping procedures</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">Intel Architecture, 32-bit (IA-32) computers (the IBM PC and its - clones) that can run <span class="Ux">NetBSD</span>/i386 or - <span class="Ux">NetBSD</span>/amd64 can use any of the following boot - procedures, depending on what the hardware and BIOS support:</p> -<dl class="Bl-tag"> - <dt>boot</dt> - <dd>bootstrap <span class="Ux">NetBSD</span> from the system BIOS</dd> - <dt>efiboot</dt> - <dd>bootstrap <span class="Ux">NetBSD</span> from the system UEFI</dd> - <dt><a class="Xr">x86/dosboot(8)</a></dt> - <dd>bootstrap <span class="Ux">NetBSD</span> from MS-DOS</dd> - <dt><a class="Xr">x86/pxeboot(8)</a></dt> - <dd>network bootstrap <span class="Ux">NetBSD</span> from a TCP/IP LAN with - DHCP, TFTP, and NFS.</dd> -</dl> -<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, 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 386 PC AT clones attempt to boot the floppy disk drive A - (otherwise known as drive 0) first, and failing that, attempt to boot the - hard disk C (otherwise known as hard disk controller 1, drive 0). The - <span class="Ux">NetBSD</span> bootblocks are loaded and started either by - the BIOS, or by a boot selector program (such as OS-BS, BOOTEASY, the OS/2 - Boot Menu or <span class="Ux">NetBSD</span>'s - <span class="No">boot-selecting</span> master boot record - see - <a class="Xr">x86/mbr(8)</a>).</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Normal_Operation"><a class="permalink" href="#Normal_Operation">Normal - Operation</a></h2> -<p class="Pp">Once running, a banner similar to the following will appear:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>>> NetBSD BIOS Boot, revision 3.0 ->> (user@buildhost, builddate) ->> Memory: 637/15360 k -Press return to boot now, any other key for boot menu -booting hd0a:netbsd - starting in 5</pre> -</div> -<p class="Pp">After a countdown, the system image listed will be loaded. In the - example above, it will be - “<code class="Li">hd0a:netbsd</code>” which is the file - <span class="Pa">/netbsd</span> on partition - “<code class="Li">a</code>” of the - <span class="Ux">NetBSD</span> MBR partition of the first hard disk known to - the BIOS (which is an IDE or similar device — see the - <a class="Sx" href="#BUGS">BUGS</a> section).</p> -<p class="Pp">Pressing a key within the time limit, or before the boot program - starts, will enter interactive mode. When using a short or 0 timeout, it is - often useful to interrupt the boot by holding down a shift key, as some - BIOSes and BIOS extensions will drain the keystroke buffer at various points - during POST.</p> -<p class="Pp">If present, the file <span class="Pa">/boot.cfg</span> will be - used to configure the behaviour of the boot loader including setting the - timeout, choosing a console device, altering the banner text and displaying - a menu allowing boot commands to be easily chosen. See - <a class="Xr">boot.cfg(5)</a>.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Boot_Protocol"><a class="permalink" href="#Boot_Protocol">Boot - Protocol</a></h2> -<p class="Pp">The <span class="Ux">NetBSD</span>/x86 boot loader can boot a - kernel using either the native <span class="Ux">NetBSD</span> boot protocol, - or the “multiboot” protocol (which is compatible with some - other operating systems). In the native <span class="Ux">NetBSD</span> boot - protocol, options are passed from the boot loader to the kernel via flag - bits in the <var class="Va">boothowto</var> variable (see - <a class="Xr">boothowto(9)</a>). In the multiboot protocol, options are - passed from the boot loader to the kernel as strings.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Diagnostic_Output"><a class="permalink" href="#Diagnostic_Output">Diagnostic - Output</a></h2> -<p class="Pp">If the first stage boot fails to load the boot, it will print a - terse message indicating the reason for the failure. The possible error - messages and their cause are listed in <a class="Xr">x86/mbr(8)</a>.</p> -<p class="Pp">If the first stage boot succeeds, the banner will be shown and the - error messages should be self-explanatory.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Interactive_mode"><a class="permalink" href="#Interactive_mode">Interactive - mode</a></h2> -<p class="Pp">In interactive mode, the boot loader will present a prompt, - allowing input of these commands:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="boot"><a class="permalink" href="#boot"><code class="Ic">boot</code></a> - [<var class="Ar">device</var><code class="Ic">:</code>][<var class="Ar">filename</var>] - [<code class="Fl">-1234abcdmqsvxz</code>]</dt> - <dd>The default <var class="Ar">device</var> will be set to the disk from - which the boot loader was loaded. The partition is set to the first match - in this list: - <ol class="Bl-enum"> - <li>The first <a class="Xr">gpt(8)</a> partition with the - <var class="Va">bootme</var> attribute set.</li> - <li>The partition from which the boot loader was loaded from, if that can - be detected.</li> - <li>The first partition with a file system that could be bootable.</li> - <li>The first partition.</li> - </ol> - <p class="Pp">To boot from an alternate disk, the full name of the device - should be given at the prompt. <var class="Ar">device</var> is of the - form <code class="Li">NAME=</code><var class="Ar">partition_label</var> - when booting from a <a class="Xr">gpt(8)</a> partitioned disk. - Otherwise, the syntax is - <var class="Ar">xd</var>[<var class="Ar">N</var>[<var class="Ar">x</var>]] - where <var class="Ar">xd</var> is the device from which to boot, - <var class="Ar">N</var> is the unit number, and <var class="Ar">x</var> - is the partition letter.</p> - <p class="Pp">In the latter case, the following list of supported devices - may vary from installation to installation:</p> - <dl class="Bl-hang"> - <dt>hd</dt> - <dd>Hard disks as numbered by the BIOS. This includes ST506, IDE, ESDI, - RLL disks on a WD100[2367] or lookalike controller(s), and SCSI disks - on SCSI controllers recognized by the BIOS.</dd> - <dt>fd</dt> - <dd>Floppy drives as numbered by the BIOS.</dd> - <dt>cd</dt> - <dd>CD-ROM drives as numbered by the BIOS.</dd> - <dt>raid</dt> - <dd>RAIDframe configured from hard disks recognized by the BIOS. Only RAID - level 1 sets are supported by bootstrap code. If the RAID is - partitioned, the first partition is used, or the first - <a class="Xr">gpt(8)</a> partition that has the - <var class="Va">bootme</var> attribute set. Inner RAIDframe partitions - can also be given to the <code class="Ic">dev</code> command using he - <code class="Li">NAME=</code><var class="Ar">partition_label</var> - syntax.</dd> - </dl> - <p class="Pp">The default <var class="Va">filename</var> is - <span class="Pa">netbsd</span>; if the boot loader fails to successfully - open that image, it then tries <span class="Pa">netbsd.gz</span> - (expected to be a kernel image compressed by gzip), followed by - <span class="Pa">onetbsd</span>, <span class="Pa">onetbsd.gz</span>, - <span class="Pa">netbsd.old</span>, and finally - <span class="Pa">netbsd.old.gz</span>.</p> - <p class="Pp">In support of the <code class="Dv">KERNEL_DIR</code> build - option (see <a class="Xr">mk.conf(5)</a>), the boot loader will then try - <span class="Pa">netbsd/kernel</span>, - <span class="Pa">netbsd/kernel.gz</span>, - <span class="Pa">onetbsd/kernel</span>, - <span class="Pa">onetbsd/kernel.gz</span>, - <span class="Pa">netbsd.old/kernel</span>, and finally - <span class="Pa">netbsd.old/kernel.gz</span>. Alternate system images - can be loaded by just specifying the filename of the image. If the - specified <span class="Pa">filename</span> does not contain an embedded - or trailing slash character, the boot loader will also try - <span class="Pa">filename/kernel</span> and - <span class="Pa">filename/kernel.gz</span>. (A leading slash character - will be ignored.)</p> - <p class="Pp">Options are:</p> - <dl class="Bl-tag"> - <dt id="1"><a class="permalink" href="#1"><code class="Fl">-1</code></a></dt> - <dd>Sets the machine-dependent flag <code class="Dv">RB_MD1</code> in - <var class="Va">boothowto</var>. In - <span class="Ux">NetBSD</span>/x86, this disables multiprocessor boot; - the kernel will boot in uniprocessor mode.</dd> - <dt id="2"><a class="permalink" href="#2"><code class="Fl">-2</code></a></dt> - <dd>Sets the machine-dependent flag <code class="Dv">RB_MD2</code> in - <var class="Va">boothowto</var>. In - <span class="Ux">NetBSD</span>/x86, this disables ACPI.</dd> - <dt id="3"><a class="permalink" href="#3"><code class="Fl">-3</code></a></dt> - <dd>Sets the machine-dependent flag <code class="Dv">RB_MD3</code> in - <var class="Va">boothowto</var>. In - <span class="Ux">NetBSD</span>/amd64, this disables SVS.</dd> - <dt id="4"><a class="permalink" href="#4"><code class="Fl">-4</code></a></dt> - <dd>Sets the machine-dependent flag <code class="Dv">RB_MD4</code> in - <var class="Va">boothowto</var>. In - <span class="Ux">NetBSD</span>/x86, this has no effect.</dd> - <dt id="a"><a class="permalink" href="#a"><code class="Fl">-a</code></a></dt> - <dd>Sets the <code class="Dv">RB_ASKNAME</code> flag in - <var class="Va">boothowto</var>. This causes the kernel to prompt for - the root file system device, the system crash dump device, and the - path to <a class="Xr">init(8)</a>.</dd> - <dt id="b"><a class="permalink" href="#b"><code class="Fl">-b</code></a></dt> - <dd>Sets the <code class="Dv">RB_HALT</code> flag in - <var class="Va">boothowto</var>. This causes subsequent reboot - attempts to halt instead of rebooting.</dd> - <dt id="c"><a class="permalink" href="#c"><code class="Fl">-c</code></a></dt> - <dd>Sets the <code class="Dv">RB_USERCONF</code> flag in - <var class="Va">boothowto</var>. This causes the kernel to enter the - <a class="Xr">userconf(4)</a> device configuration manager as soon as - possible during the boot. <a class="Xr">userconf(4)</a> allows devices - to be enabled or disabled, and allows device locators (such as - hardware addresses or bus numbers) to be modified before the kernel - attempts to attach the devices.</dd> - <dt id="d"><a class="permalink" href="#d"><code class="Fl">-d</code></a></dt> - <dd>Sets the <code class="Dv">RB_KDB</code> flag in - <var class="Va">boothowto</var>. Requests the kernel to enter debug - mode, in which it waits for a connection from a kernel debugger; see - <a class="Xr">ddb(4)</a>.</dd> - <dt id="m"><a class="permalink" href="#m"><code class="Fl">-m</code></a></dt> - <dd>Sets the <code class="Dv">RB_MINIROOT</code> flag in - <var class="Va">boothowto</var>. Informs the kernel that a mini-root - file system is present in memory.</dd> - <dt id="q"><a class="permalink" href="#q"><code class="Fl">-q</code></a></dt> - <dd>Sets the <code class="Dv">AB_QUIET</code> flag in - <var class="Va">boothowto</var>. Boot the system in quiet mode.</dd> - <dt id="s"><a class="permalink" href="#s"><code class="Fl">-s</code></a></dt> - <dd>Sets the <code class="Dv">RB_SINGLE</code> flag in - <var class="Va">boothowto</var>. Boot the system in single-user - mode.</dd> - <dt id="v"><a class="permalink" href="#v"><code class="Fl">-v</code></a></dt> - <dd>Sets the <code class="Dv">AB_VERBOSE</code> flag in - <var class="Va">boothowto</var>. Boot the system in verbose mode.</dd> - <dt id="x"><a class="permalink" href="#x"><code class="Fl">-x</code></a></dt> - <dd>Sets the <code class="Dv">AB_DEBUG</code> flag in - <var class="Va">boothowto</var>. Boot the system with debug messages - enabled.</dd> - <dt id="z"><a class="permalink" href="#z"><code class="Fl">-z</code></a></dt> - <dd>Sets the <code class="Dv">AB_SILENT</code> flag in - <var class="Va">boothowto</var>. Boot the system in silent mode.</dd> - </dl> - </dd> - <dt id="consdev"><a class="permalink" href="#consdev"><code class="Ic">consdev</code></a> - <var class="Ar">dev</var>[<code class="Ic">,</code><var class="Ar">speed</var>]</dt> - <dd>[Not available for <a class="Xr">x86/dosboot(8)</a>] Immediately switch - the console to the specified device <var class="Ar">dev</var> and reprint - the banner. <var class="Ar">dev</var> must be one of - <code class="Li">pc</code>, <code class="Li">com0</code>, - <code class="Li">com1</code>, <code class="Li">com2</code>, - <code class="Li">com3</code>, <code class="Li">com0kbd</code>, - <code class="Li">com1kbd</code>, <code class="Li">com2kbd</code>, - <code class="Li">com3kbd</code>, or <code class="Li">auto</code>. See - <a class="Sx" href="#Console_Selection_Policy">Console Selection - Policy</a> in <a class="Xr">x86/boot_console(8)</a>. - <p class="Pp">A <var class="Ar">speed</var> for the serial port is optional - and defaults to 9600. If a value of zero is specified, then the current - baud rate (set by the BIOS) will be used. Setting the - <var class="Ar">speed</var> with the <code class="Li">pc</code> device - is not possible.</p> - <p class="Pp">UEFI may support some USB and PCI-based serial ports. See the - <a class="Sx" href="#UEFI_serial_ports">UEFI serial ports</a> section - for details. Using the <code class="Ic">consdev</code> command without - arguments lists the available ports. <var class="Ar">com0</var> to - <var class="Ar">com3</var> are reserved for standard ISA serial ports, - other ports are assigned to <var class="Ar">com4</var> and beyond. The - generic <var class="Ar">com{unit}[,speed]</var> syntax can be used to - select any port.</p> - <p class="Pp">Bootstrap can tell the kernel to use a USB-to-serial adapter - for console using the <var class="Ar">ucom{unit}[,speed]</var> syntax. - No console switch happens in bootstrap, and kernel console - initialization will be deferred after USB devices attachment. This means - early boot will be silent, and <a class="Xr">userconf(4)</a> interactive - mode cannot be used. The default <var class="Ar">ucom</var> speed is - 115200.</p> - </dd> - <dt id="kconsdev"><a class="permalink" href="#kconsdev"><code class="Ic">kconsdev</code></a> - <var class="Ar">dev</var>[<code class="Ic">,</code><var class="Ar">speed</var>]</dt> - <dd>Configure the kernel console like <code class="Ic">consdev</code> but do - not attempt to switch console in bootstrap. This is useful when using a - USB-to-serial adapter that is known as a <var class="Ar">com</var> device - in bootstrap but as a <var class="Ar">ucom</var> device for the kernel. - One may use a syntax like: - <div class="Bd Pp Bd-indent Li"> - <pre>consdev com4,115200 -kconsdev ucom0,115200</pre> - </div> - Note that command ordering matters.</dd> - <dt id="dev"><a class="permalink" href="#dev"><code class="Ic">dev</code></a> - [<var class="Ar">device</var>]</dt> - <dd>Set the default drive and partition for subsequent file system operations. - Without an argument, print the current setting. - <var class="Ar">device</var> is of the form specified in - <code class="Ic">boot</code>.</dd> - <dt id="devpath"><a class="permalink" href="#devpath"><code class="Ic">devpath</code></a></dt> - <dd>[Only available for UEFI boot] Dump UEFI device paths.</dd> - <dt id="efivar"><a class="permalink" href="#efivar"><code class="Ic">efivar</code></a></dt> - <dd>[Only available for UEFI boot] Dump UEFI environment variables from - NVRAM.</dd> - <dt id="fs"><a class="permalink" href="#fs"><code class="Ic">fs</code></a> - <var class="Ar">file</var></dt> - <dd>[Only available for BIOS and UEFI boot] Load a file system image from the - specified <var class="Ar">file</var>, and request the kernel to use it as - the root file system. The <a class="Xr">makefs(8)</a> utility may be used - to create suitable file system images.</dd> - <dt id="gop"><a class="permalink" href="#gop"><code class="Ic">gop</code></a> - [<var class="Va">mode_index</var>]</dt> - <dd>[Only available for UEFI boot] Without argument, list the available video - modes. If an argument is given, select a video mode.</dd> - <dt id="help"><a class="permalink" href="#help"><code class="Ic">help</code></a></dt> - <dd>Print an overview about commands and arguments.</dd> - <dt id="load"><a class="permalink" href="#load"><code class="Ic">load</code></a> - <var class="Ar">module</var> [<var class="Ar">arguments</var>]</dt> - <dd>[Not available for <a class="Xr">x86/dosboot(8)</a>] Load the specified - kernel <var class="Ar">module</var>, and pass it the specified - <var class="Ar">arguments</var>. If the module name is not an absolute - path, - <div class="Bd - Bd-indent"><span class="Pa">/stand/</span>⟨<var class="Ar">arch</var>⟩<span class="Pa">/</span>⟨<var class="Ar">osversion</var>⟩<span class="Pa">/modules/</span>⟨<var class="Ar">module</var>⟩<span class="Pa">/</span>⟨<var class="Ar">module</var>⟩<span class="Pa">.kmod</span></div> - is used. Possible uses of the <code class="Ic">load</code> command include - loading a memory disk image before booting a kernel, or loading a Xen DOM0 - kernel before booting the Xen hypervisor. See - <a class="Xr">boot.cfg(5)</a> for examples. - <p class="Pp">In addition to the <code class="Cm">boot</code> options - specified above, the Xen DOM0 kernel accepts - (<var class="Ar">arguments</var> being separated with spaces):</p> - <dl class="Bl-tag"> - <dt id="bootdev"><a class="permalink" href="#bootdev"><code class="Ic">bootdev</code></a>=<var class="Ar">dev</var> - (or <code class="Ic">root</code>=<var class="Ar">dev</var>)</dt> - <dd>Override the default boot device. <var class="Ar">dev</var> is of the - form - <code class="Li">NAME=</code><var class="Ar">partition_label</var> for - <a class="Xr">gpt(8)</a> partitioned disks. It can also be a unit name - (‘<code class="Li">wd0</code>’), or an interface name - (‘<code class="Li">bge0</code>’, - ‘<code class="Li">wm0</code>’, ...) for cases where the - root file system has to be loaded from network (see the - <a class="Sx" href="#BUGS">BUGS</a> section in - <a class="Xr">x86/pxeboot(8)</a>).</dd> - <dt id="console"><a class="permalink" href="#console"><code class="Ic">console</code></a>=<var class="Ar">dev</var></dt> - <dd>Console used by DOM0 kernel during boot. <var class="Ar">dev</var> - accepts the same values as the ones given for the - <code class="Cm">consdev</code> command. See - <a class="Sx" href="#Console_Selection_Policy">Console Selection - Policy</a> in <a class="Xr">x86/boot_console(8)</a>.</dd> - <dt id="ip"><a class="permalink" href="#ip"><code class="Ic">ip</code></a><code class="Li">=</code><var class="Ar">my_ip</var><code class="Li">:</code><var class="Ar">serv_ip</var><code class="Li">:</code><var class="Ar">gw_ip</var><code class="Li">:</code><var class="Ar">mask</var><code class="Li">:</code><var class="Ar">host</var><code class="Li">:</code><var class="Ar">iface</var></dt> - <dd>Specify various parameters for a network boot (IPs are in dot - notation), each one separated by a colon: - <dl class="Bl-tag"> - <dt><var class="Ar">my_ip</var></dt> - <dd>address of the host</dd> - <dt><var class="Ar">serv_ip</var></dt> - <dd>address of the NFS server</dd> - <dt><var class="Ar">gw_ip</var></dt> - <dd>address of the gateway</dd> - <dt><var class="Ar">mask</var></dt> - <dd>network mask</dd> - <dt><var class="Ar">host</var></dt> - <dd>address of the host</dd> - <dt><var class="Ar">iface</var></dt> - <dd>interface (e.g., “<code class="Li">xennet0</code>” - or “<code class="Li">eth0</code>”)</dd> - </dl> - </dd> - <dt id="nfsroot"><a class="permalink" href="#nfsroot"><code class="Ic">nfsroot</code></a>=<var class="Ar">address</var><code class="Li">:</code><var class="Ar">rootpath</var></dt> - <dd>Boot the system with root on NFS. <var class="Ar">address</var> is the - address of the NFS server, and <var class="Ar">rootpath</var> is the - remote mount point for the root file system.</dd> - <dt id="pciback.hide"><a class="permalink" href="#pciback.hide"><code class="Ic">pciback.hide</code></a>=<var class="Ar">pcidevs</var></dt> - <dd>Pass a list of PCI IDs for use with the PCI backend driver, - <a class="Xr">pciback(4)</a>. <var class="Ar">pcidevs</var> is formed - of multiple IDs (in - <var class="Ar">bus</var><code class="Li">:</code><var class="Ar">device</var><code class="Li">.</code><var class="Ar">function</var> - notation), each ID being surrounded with brackets. PCI domain IDs are - currently ignored. See <a class="Xr">pciback(4)</a>.</dd> - </dl> - </dd> - <dt id="ls"><a class="permalink" href="#ls"><code class="Ic">ls</code></a> - [<var class="Ar">path</var>]</dt> - <dd>[Not available for <a class="Xr">x86/pxeboot(8)</a>] Print a directory - listing of <var class="Ar">path</var>, containing inode number, filename, - and file type. <var class="Ar">path</var> can contain a device - specification.</dd> - <dt id="memmap"><a class="permalink" href="#memmap"><code class="Ic">memmap</code></a></dt> - <dd>[Only available for UEFI boot] Dump UEFI memory map.</dd> - <dt id="menu"><a class="permalink" href="#menu"><code class="Ic">menu</code></a></dt> - <dd>[Only available for BIOS and UEFI boot] Display the boot menu and initiate - a countdown, similarly to what would have happened if interactive mode had - not been entered.</dd> - <dt id="modules"><a class="permalink" href="#modules"><code class="Ic">modules</code></a> - {<code class="Li">on</code> <span class="No">|</span> - <code class="Li">off</code> <span class="No">|</span> - <code class="Li">enabled</code> <span class="No">|</span> - <code class="Li">disabled</code>}</dt> - <dd>[Not available for <a class="Xr">x86/dosboot(8)</a>] The values - ‘<code class="Li">enabled</code>’, - ‘<code class="Li">on</code>’ will enable module loading for - <code class="Ic">boot</code> and <code class="Ic">multiboot</code>, - whereas ‘<code class="Li">disabled</code>’, - ‘<code class="Li">off</code>’ will turn off the - feature.</dd> - <dt id="mode"><a class="permalink" href="#mode"><code class="Ic">mode</code></a> - <var class="Va">fstype</var></dt> - <dd>[Only available for <a class="Xr">x86/dosboot(8)</a>] Switch file system - type; <var class="Va">fstype</var> should be one of - <var class="Ar">dos</var> or <var class="Ar">ufs</var>.</dd> - <dt id="multiboot"><a class="permalink" href="#multiboot"><code class="Ic">multiboot</code></a> - <var class="Ar">kernel</var> [<var class="Ar">arguments</var>]</dt> - <dd>[Not available for <a class="Xr">x86/dosboot(8)</a>] Boot the specified - <var class="Ar">kernel</var>, using the “multiboot” protocol - instead of the native <span class="Ux">NetBSD</span> boot protocol. The - <var class="Ar">kernel</var> is specified in the same way as with the - <code class="Ic">boot</code> command. - <p class="Pp">The multiboot protocol may be used in the following cases:</p> - <dl class="Bl-tag"> - <dt><span class="Ux">NetBSD</span>/Xen - <span class="No">kernels</span></dt> - <dd>The Xen DOM0 kernel must be loaded as a module using the - <code class="Ic">load</code> command, and the Xen hypervisor must be - booted using the <code class="Ic">multiboot</code> command. Options - for the DOM0 kernel (such as “-s” for single user mode) - must be passed as options to the <code class="Ic">load</code> command. - Options for the hypervisor (such as - “<code class="Li">dom0_mem=256M</code>” to reserve 256MB - of memory for DOM0) must be passed as options to the - <code class="Ic">multiboot</code> command. See - <a class="Xr">boot.cfg(5)</a> for examples on how to boot - <span class="Ux">NetBSD</span>/Xen.</dd> - <dt><span class="Ux">NetBSD</span> <span class="No">multiboot - kernels</span></dt> - <dd>A <span class="Ux">NetBSD</span> kernel that was built with - <code class="Cd">options MULTIBOOT</code> (see - <a class="Xr">x86/multiboot(8)</a>) may be booted with either the - <code class="Ic">boot</code> or <code class="Ic">multiboot</code> - command, passing the same <var class="Ar">arguments</var> in either - case.</dd> - <dt>Non-<span class="Ux">NetBSD</span> - <span class="No">kernels</span></dt> - <dd>A kernel for a - <span class="No">non-</span><span class="Ux">NetBSD</span> operating - system that expects to be booted using the multiboot protocol (such as - by the GNU “GRUB” boot loader) may be booted using the - <code class="Ic">multiboot</code> command. See the foreign operating - system's documentation for the available - <var class="Ar">arguments</var>.</dd> - </dl> - </dd> - <dt id="pkboot"><a class="permalink" href="#pkboot"><code class="Ic">pkboot</code></a></dt> - <dd>[Only available for BIOS and UEFI boot] Boot a kernel that has the - <code class="Cd">KASLR</code> option set, for Kernel Address Space Layout - Randomizaton.</dd> - <dt id="quit"><a class="permalink" href="#quit"><code class="Ic">quit</code></a></dt> - <dd>Reboot the system.</dd> - <dt id="reloc"><a class="permalink" href="#reloc"><code class="Ic">reloc</code></a> - [<var class="Va">default</var> <span class="No">|</span> - <var class="Va">none</var> <span class="No">|</span> - <var class="Va">address</var>]</dt> - <dd>[Only UEFI boot] Sets where the kernel is copied by bootstrap before it is - started. Values other than default require a kernel built with the - <code class="Cd">SELFRELOC</code> option, so that can relocate itself at - the right address, otherwise a crash occurs at boot time. - <dl class="Bl-tag"> - <dt id="default"><var class="Va">default</var></dt> - <dd>Copy the kernel at ELF header load address, this is the historical - behavior.</dd> - <dt id="none"><var class="Va">none</var></dt> - <dd>Leave the kernel where it was loaded and start it as is.</dd> - <dt id="address"><var class="Va">address</var></dt> - <dd>Copy the kernel at given <var class="Va">address</var>.</dd> - </dl> - </dd> - <dt id="rndseed"><a class="permalink" href="#rndseed"><code class="Ic">rndseed</code></a> - <var class="Ar">file</var></dt> - <dd>[Only available for BIOS and UEFI boot] Load the specified - <var class="Ar">file</var> and request the kernel to use it as a seed for - the <a class="Xr">rnd(4)</a> random number generator. The - <var class="Ar">file</var> should be in the private format used by - <a class="Xr">rndctl(8)</a>, and should have been saved by - ‘<code class="Li">rndctl -S</code>’ shortly before the - previous shutdown. See the <var class="Va">random_seed</var> and - <var class="Va">random_file</var> variables in - <a class="Xr">rc.conf(5)</a>, and the - <span class="Pa">/etc/rc.d/random_seed</span> script, for a way to manage - the seed file. Using the same seed file on more then one host, or for more - than one boot on the same host, will reduce the quality of random numbers - and may impact system security.</dd> - <dt id="root"><a class="permalink" href="#root"><code class="Ic">root</code></a> - <var class="Ar">spec</var></dt> - <dd>[Only available for BIOS and UEFI boot] Pass an explicit root - specification to the kernel. See BTINFO_ROOTDEVICE for details.</dd> - <dt id="splash"><a class="permalink" href="#splash"><code class="Ic">splash</code></a> - <var class="Ar">file</var></dt> - <dd>[Only available for BIOS and UEFI boot] Load a graphical image from the - specified <var class="Ar">file</var> and request the kernel to use it as a - splash screen. The <var class="Ar">file</var> should contain an image in - one of these formats: JPEG (baseline only, not progressive), PNG (8-bit - only), TGA, BMP (non-1bpp, non-RLE), GIF, PSD (composited view only), or - PIC.</dd> - <dt id="text"><a class="permalink" href="#text"><code class="Ic">text</code></a> - [<var class="Va">mode_index</var>]</dt> - <dd>[Only available for UEFI boot] Without argument, list the available text - modes (displayed as column x line in hexadecimal, therefore - <code class="Li">50x19</code> means <code class="Li">80</code> columns and - <code class="Li">25</code> lines). With an argument, select a text - mode.</dd> - <dt id="userconf"><a class="permalink" href="#userconf"><code class="Ic">userconf</code></a> - <var class="Ar">command</var></dt> - <dd>[Not available for <a class="Xr">x86/dosboot(8)</a>] Pass command - <var class="Ar">command</var> to <a class="Xr">userconf(4)</a> at boot - time. These commands are processed before the interactive - <a class="Xr">userconf(4)</a> shell is executed, if requested.</dd> - <dt id="version"><a class="permalink" href="#version"><code class="Ic">version</code></a> - [<var class="Ar">full</var>]</dt> - <dd>[Only available for UEFI boot] Display UEFI bootstrap version. With the - [full] argument, also display information about UEFI itself.</dd> - <dt id="vesa"><a class="permalink" href="#vesa"><code class="Ic">vesa</code></a> - {<var class="Ar">modenum</var> <span class="No">|</span> - <code class="Li">on</code> <span class="No">|</span> - <code class="Li">off</code> <span class="No">|</span> - <code class="Li">enabled</code> <span class="No">|</span> - <code class="Li">disabled</code> <span class="No">|</span> - <code class="Li">list</code>}</dt> - <dd>[Only available for BIOS and <a class="Xr">x86/pxeboot(8)</a>] Initialise - the video card to the specified resolution and bit depth. The - <var class="Ar">modenum</var> should be in the form of - ‘<code class="Li">0x100</code>’, - ‘<code class="Li">800x600</code>’, - ‘<code class="Li">800x600x32</code>’. The values - ‘<code class="Li">enabled</code>’, - ‘<code class="Li">on</code>’ put the display into the - default mode, and ‘<code class="Li">disabled</code>’, - ‘<code class="Li">off</code>’ returns the display into - standard vga mode. The value ‘<code class="Li">list</code>’ - lists all supported modes.</dd> -</dl> -</div> -<p class="Pp">In an emergency, the bootstrap methods described in the - <span class="Ux">NetBSD</span> installation notes for the x86 architectures - can be used to boot from floppy or other media, or over the network.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="Locating_the_root_file_system"><a class="permalink" href="#Locating_the_root_file_system">Locating - the root file system</a></h2> -<p class="Pp">The kernel uses information from the bootloader to locate the file - system to mount as root. There are three methods:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="BTINFO_ROOTDEVICE"><a class="permalink" href="#BTINFO_ROOTDEVICE"><code class="Dv">BTINFO_ROOTDEVICE</code></a> - <var class="Va">from</var></dt> - <dd><a class="Xr">boot.cfg(5)</a> or multiboot. The bootloader passes the root - device name as driver, unit, and partition (like - ‘<code class="Li">sd0a).</code>’ This will be automatically - substituted by a <a class="Xr">dk(4)</a> wedge if one is discovered. - <p class="Pp">If the bootloader passes a wedge name as - “<code class="Li">wedge:</code>” or - “<code class="Li">NAME=</code>” followed by the name. The - kernel will search for a <a class="Xr">dk(4)</a> device with that - name.</p> - </dd> - <dt id="BTINFO_BOOTWEDGE"><a class="permalink" href="#BTINFO_BOOTWEDGE"><code class="Dv">BTINFO_BOOTWEDGE</code></a> - <var class="Va">determined by bootblock</var></dt> - <dd>The bootloader passes start offset and length of a hard disk partition and - a offset, size and hash of a “boot area”. Then kernel - searches all disks and wedges for a block sequence at that offset with a - matching hash. If one is found, the kernel will look for a wedge on that - device at the same offset. - <p class="Pp">An additional partition number is provided if the bootloader - also passed a <code class="Dv">BTINFO_BOOTDISK</code> record. This (or - partition ‘<code class="Li">a</code>’) will be used by the - kernel as a fallback if there is no matching wedge.</p> - </dd> - <dt id="BTINFO_BOOTDISK"><a class="permalink" href="#BTINFO_BOOTDISK"><code class="Dv">BTINFO_BOOTDISK</code></a> - <var class="Va">determined by bootblock</var></dt> - <dd>This uses the device number passed by the BIOS that distinguishes between - floppy, hard drive and CD-ROM boot. - <dl class="Bl-tag"> - <dt>Floppy</dt> - <dd>The kernel searches for the <a class="Xr">fd(4)</a> device with the - correct unit, the partition number is used to select a specific disk - format. See <a class="Xr">fd(4)</a> for details.</dd> - <dt>Hard drive</dt> - <dd>The bootloader passed a partition number and disklabel data (offset, - type, checksum, packname). The kernel searches all disks for a - matching disklabel. If one is found, the kernel will use that device - and partition number.</dd> - <dt>CDROM</dt> - <dd>The BIOS does not distinguish between multiple CD devices. The kernel - searches for the first <a class="Xr">cd(4)</a> device. So you can only - boot from unit 0.</dd> - </dl> - </dd> -</dl> -</div> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="UEFI_serial_ports"><a class="permalink" href="#UEFI_serial_ports">UEFI - serial ports</a></h1> -<p class="Pp">Serial ports supported by a UEFI driver can be used in UEFI and in - NetBSD bootstrap. UEFI usually supports ISA serial ports, and it may support - PCI or USB-to- serial adapters, depending on vendor-specific - implementations.</p> -<p class="Pp">An open source UEFI driver is available form Tianocore EDK2, for - USB-to-serial adapters using the FTDI FT232R chip. USB vendor ID and product - ID for those devices are <var class="Ar">0x0403</var> and - <var class="Ar">0x6001.</var></p> -<p class="Pp">To use it, obtain the <span class="Pa">FtdiUsbSerialDxe.efi</span> - driver from Tianocore EDK2 and save it in the EFI bootstrap partition, for - instance in <span class="Pa">/EFI/EDK2/FtdiUsbSerialDxe.efi</span> then - create a <span class="Pa">/EFI/boot/startup.nsh</span> script containing - something like</p> -<div class="Bd Pp Bd-indent Li"> -<pre>FS0: -load \EFI\EDK2\FtdiUsbSerialDxe.efi -bootx64.efi</pre> -</div> -<p class="Pp">Then make sure UEFI boots into the UEFI shell. If it is not - available in the built-in options, <span class="Pa">Shell.efi</span> can be - obtained from Tianocore EDK2 and installed in - <span class="Pa">/EFI/boot/Shell.efi</span>.</p> -</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">/boot</span></dt> - <dd>boot program code loaded by the primary bootstrap</dd> - <dt><span class="Pa">/boot.cfg</span></dt> - <dd>optional configuration file</dd> - <dt><span class="Pa">/netbsd</span></dt> - <dd>system code</dd> - <dt><span class="Pa">/netbsd.gz</span></dt> - <dd>gzip-compressed system code</dd> - <dt><span class="Pa">/usr/mdec/boot</span></dt> - <dd>master copy of the boot program (copy to /boot)</dd> - <dt><span class="Pa">/usr/mdec/bootxx_fstype</span></dt> - <dd>primary bootstrap for file system type fstype, copied to the start of the - <span class="Ux">NetBSD</span> partition by - <a class="Xr">installboot(8)</a>.</dd> - <dt><span class="Pa">/usr/mdec/bootia32.efi</span></dt> - <dd style="width: auto;"> </dd> - <dt><span class="Pa">/usr/mdec/bootx64.efi</span></dt> - <dd>UEFI bootstraps for <span class="Ux">NetBSD</span>/i386 and - <span class="Ux">NetBSD</span>/amd64, which should be copied to the - <span class="Pa">/EFI/boot</span> directory in a FAT formatted partition - of type EFI (either <a class="Xr">x86/mbr(8)</a> or - <a class="Xr">gpt(8)</a>, see the <a class="Sx" href="#BUGS">BUGS</a> - section). <span class="Ux">NetBSD</span> UEFI bootstrap reads its - configuration from the <span class="Pa">/EFI/NetBSD/boot.cfg</span> file - in the EFI partition.</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">ddb(4)</a>, <a class="Xr">fd(4)</a>, - <a class="Xr">pciback(4)</a>, <a class="Xr">userconf(4)</a>, - <a class="Xr">boot.cfg(5)</a>, <a class="Xr">halt(8)</a>, - <a class="Xr">installboot(8)</a>, <a class="Xr">reboot(8)</a>, - <a class="Xr">rescue(8)</a>, <a class="Xr">shutdown(8)</a>, - <a class="Xr">x86/boot_console(8)</a>, <a class="Xr">x86/dosboot(8)</a>, - <a class="Xr">x86/mbr(8)</a>, <a class="Xr">x86/multiboot(8)</a>, - <a class="Xr">x86/pxeboot(8)</a>, <a class="Xr">boothowto(9)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The kernel file name must be specified before, not after, the boot - options. Any <var class="Ar">filename</var> specified after the boot - options, e.g.:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">boot -d netbsd.test</code></div> -<p class="Pp">is ignored, and the default kernel is booted.</p> -<p class="Pp">Hard disks are always accessed by BIOS functions. Unit numbers are - BIOS device numbers which might differ from numbering in the - <span class="Ux">NetBSD</span> kernel or physical parameters (e.g., SCSI - slave numbers). There isn't any distinction between “sd” and - “wd” devices at the bootloader level. This is less a bug of - the bootloader code than a shortcoming of the PC architecture. The default - disk device's name printed in the starting message is derived from the - “type” field of the <span class="Ux">NetBSD</span> disklabel - (if it is a hard disk).</p> -<p class="Pp">UEFI implementations are supposed to support either - <a class="Xr">x86/mbr(8)</a> or <a class="Xr">gpt(8)</a> partitioning, but - some do not handle the latter. UEFI booting from a <a class="Xr">gpt(8)</a> - partitioned disk is still possible in this case, by adding an overlapping - EFI partition in the protective <a class="Xr">x86/mbr(8)</a> block. This can - be achieved using the following commands (you must adapt the hard disk and - EFI partition start end size to fit your setup):</p> -<div class="Bd Pp Bd-indent Li"> -<pre>dd if=/dev/rwd0d bs=512 count=1 of=mbr -fdisk -FIfaui1s 4/34/32768 -c /usr/mdec/mbr mbr -dd if=mbr bs=512 count=1 of=/dev/rwd0d conv=notrunc</pre> -</div> -<p class="Pp">The resulting <a class="Xr">x86/mbr(8)</a> partition table will - look like this:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>0: GPT Protective MBR (sysid 238) - start 1, size 2097151 (1024 MB, Cyls 0-130/138/8) - PBR is not bootable: Bad magic number (0x0000) -1: Primary DOS with 16 bit FAT <32M (sysid 4) - start 34, size 32768 (16 MB, Cyls 0/0/35-2/10/42), Active -2: <UNUSED> -3: <UNUSED></pre> -</div> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">October 9, 2025</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.x86/boot_console.8 3.html b/static/netbsd/man8/man8.x86/boot_console.8 3.html deleted file mode 100644 index 6658a99f..00000000 --- a/static/netbsd/man8/man8.x86/boot_console.8 3.html +++ /dev/null @@ -1,124 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">BOOT_CONSOLE(8)</td> - <td class="head-vol">System Manager's Manual (x86)</td> - <td class="head-rtitle">BOOT_CONSOLE(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_console</code> — - <span class="Nd">selection of a console device in the x86 - bootloader</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <span class="Ux">NetBSD</span> x86 bootloader selects a - console device for its user interaction and passes information about it to - the <span class="Ux">NetBSD</span> kernel. When booting from the system - BIOS, the console device and properties are saved in the primary bootstrap - by <a class="Xr">installboot(8)</a>. For other boot procedures (such as - <a class="Xr">x86/dosboot(8)</a>) the selection process is controlled by - bootloader compile-time options and system setup at the bootloader startup - time. The selection may be changed on-the-fly from within the - bootloader.</p> -<section class="Ss"> -<h2 class="Ss" id="Serial_Console_Options"><a class="permalink" href="#Serial_Console_Options">Serial - Console Options</a></h2> -<p class="Pp">The compile-time options (to be set in the booter's - “Makefile”) are:</p> -<dl class="Bl-ohang"> - <dt id="SUPPORT_SERIAL="><a class="permalink" href="#SUPPORT_SERIAL="><b class="Sy">SUPPORT_SERIAL=</b></a><var class="Fa">policy</var></dt> - <dd>enables support for serial input/output. By default this option is not set - and the standard PC keyboard and display are always used as the console - device. See <a class="Sx" href="#Console_Selection_Policy">Console - Selection Policy</a> below for valid values of - <var class="Fa">policy</var>.</dd> - <dt id="DIRECT_SERIAL"><a class="permalink" href="#DIRECT_SERIAL"><b class="Sy">DIRECT_SERIAL</b></a></dt> - <dd>causes direct hardware access to be used for serial input / output. With - this option, software handshake (XON/XOFF) is used for flow control. - Without this option, BIOS functions are employed for serial port handling, - which require hardware handshake lines to be completely wired.</dd> - <dt id="CONSPEED="><a class="permalink" href="#CONSPEED="><b class="Sy">CONSPEED=</b></a><var class="Fa">integer</var></dt> - <dd>sets the baud-rate for the serial console. This option has only an effect - when used in combination with the - “<code class="Dv">DIRECT_SERIAL</code>” option above, - otherwise, the default setting of 9600 baud is used. The value of - <var class="Fa">integer</var> must be something that makes sense as a - serial port baud rate.</dd> - <dt id="COMCONS_KEYPRESS"><a class="permalink" href="#COMCONS_KEYPRESS"><b class="Sy">COMCONS_KEYPRESS</b></a></dt> - <dd>Require a character input within seven (7) seconds from serial console - device to be selected.</dd> -</dl> -</section> -<section class="Ss"> -<h2 class="Ss" id="Console_Selection_Policy"><a class="permalink" href="#Console_Selection_Policy">Console - Selection Policy</a></h2> -<p class="Pp">The actual policy for the console selection is determined by the - value of “<code class="Dv">SUPPORT_SERIAL</code>” The - following options are available:</p> -<dl class="Bl-ohang"> - <dt id="CONSDEV_PC"><a class="permalink" href="#CONSDEV_PC"><i class="Em">CONSDEV_PC</i></a></dt> - <dd>Force use of the standard PC keyboard and display as the console.</dd> - <dt id="CONSDEV_COM0"><a class="permalink" href="#CONSDEV_COM0"><i class="Em">CONSDEV_COM0</i></a> - <code class="Li">...</code> - <a class="permalink" href="#CONSDEV_COM3"><i class="Em" id="CONSDEV_COM3">CONSDEV_COM3</i></a></dt> - <dd>Use the serial port with the corresponding BIOS number as the console. No - attempt is made to verify connectivity on the selected port. If the port - is not known to the BIOS, it falls back to - “<code class="Dv">CONSDEV_PC</code>”. (Note: This feature - can be deliberately used for console selection if the serial ports have - been disabled in the BIOS.)</dd> - <dt id="CONSDEV_COM0KBD"><a class="permalink" href="#CONSDEV_COM0KBD"><i class="Em">CONSDEV_COM0KBD</i></a> - <code class="Li">...</code> - <a class="permalink" href="#CONSDEV_COM3KBD"><i class="Em" id="CONSDEV_COM3KBD">CONSDEV_COM3KBD</i></a></dt> - <dd>If the port is known to the BIOS, and output of a character to the port - succeeds (and if “<code class="Dv">DIRECT_SERIAL</code>” is - defined the RS-232 “modem ready” status is on after the - character is output), the port is used as console. If the port is not - known to the BIOS, or the test output fails, it falls back to - “<code class="Dv">CONSDEV_PC</code>”.</dd> - <dt id="CONSDEV_AUTO"><a class="permalink" href="#CONSDEV_AUTO"><i class="Em">CONSDEV_AUTO</i></a></dt> - <dd>Auto-select the console. All serial ports known to the BIOS are probed in - sequence. If output of a character to the port succeeds (and if - “<code class="Dv">DIRECT_SERIAL</code>” is defined the - RS-232 “modem ready” status is on after the character is - output), the port is used as console. If no serial port passes the check, - “<code class="Dv">CONSDEV_PC</code>” is used. The progress - of the selection process is shown at the PC display as digits - corresponding to the serial port number currently probed.</dd> -</dl> -</section> -</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">src/sys/arch/i386/stand/{boot,pxeboot}/Makefile</span></dt> - <dd>compile time options for the boot programs.</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">console(4)</a>, <a class="Xr">installboot(8)</a>, - <a class="Xr">x86/boot(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The serial communication parameters (byte-size, parity, stop-bits) - are not settable (either at compile time or run time). The default - parameters are “8 N 1”.</p> -<p class="Pp">The baud rate is not settable when using BIOS I/O. It should be - settable at compile time with - “<code class="Dv">CONSPEED</code>” just as it is when using - “<code class="Dv">DIRECT_SERIAL</code>”. The default speed is - 9600 baud (the maximum for BIOS I/O).</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> diff --git a/static/netbsd/man8/man8.x86/dosboot.8 3.html b/static/netbsd/man8/man8.x86/dosboot.8 3.html deleted file mode 100644 index b5461c0d..00000000 --- a/static/netbsd/man8/man8.x86/dosboot.8 3.html +++ /dev/null @@ -1,111 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">DOSBOOT(8)</td> - <td class="head-vol">System Manager's Manual (x86)</td> - <td class="head-rtitle">DOSBOOT(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">dosboot</code> — <span class="Nd">boot - NetBSD/x86 from DOS</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">dosboot</code></td> - <td>[<code class="Fl">-u</code>] [<code class="Fl">-c</code> - <var class="Ar">command</var>] [<code class="Fl">-i</code>] - [<var class="Ar">path</var> [<code class="Fl">-adqsv</code>]]</td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">dosboot</code> is an MS-DOS program. It is a boot - loader for <span class="Ux">NetBSD</span>/x86 designed to permit - <span class="Ux">NetBSD</span> to be booted directly from MS-DOS. By - default, it boots a file with name <span class="Pa">NETBSD</span> in the - current MS-DOS directory. <code class="Nm">dosboot</code> shares common code - with the standard boot loader, <a class="Xr">x86/boot(8)</a>.</p> -<p class="Pp">The recognized options are:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="c"><a class="permalink" href="#c"><code class="Fl">-c</code></a></dt> - <dd>Execute <var class="Ar">command</var> (see below).</dd> - <dt id="i"><a class="permalink" href="#i"><code class="Fl">-i</code></a></dt> - <dd>Enter interactive mode. <code class="Nm">dosboot</code> will present a - prompt, allowing input of commands (see below).</dd> - <dt id="u"><a class="permalink" href="#u"><code class="Fl">-u</code></a></dt> - <dd>Boot from a UFS file system instead of an MS-DOS file system.</dd> - <dt><var class="Ar">path</var></dt> - <dd>Specifies the kernel file. In MS-DOS mode (default) a normal MS-DOS - filename (with or without drive specification) is accepted. In UFS mode - (after <code class="Fl">-u</code> or after a <code class="Ic">mode - ufs</code> command), a path in a <span class="Ux">NetBSD</span> file - system is expected. By default, the file is looked up in partition - ‘a’ of the first hard disk. Another device or partition can - be specified by prepending a block device name in terms of - <span class="Ux">NetBSD</span>, followed by a colon (see - <a class="Xr">x86/boot(8)</a> and examples).</dd> - <dt id="1234abcdmqsvxz"><a class="permalink" href="#1234abcdmqsvxz"><code class="Fl">-1234abcdmqsvxz</code></a></dt> - <dd>Flags passed to the kernel, see <a class="Xr">x86/boot(8)</a>.</dd> -</dl> -</div> -<p class="Pp">See <a class="Xr">x86/boot(8)</a> for commands accepted after the - <code class="Fl">-c</code> flag or in interactive mode.</p> -<p class="Pp"><code class="Nm">dosboot</code> is also installed in the - <a class="Xr">release(7)</a> hierarchy, under - <span class="Pa">installation/misc/dosboot.com</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1> -<p class="Pp"><span class="Pa">/usr/mdec/dosboot.com</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1> -<p class="Pp">To boot a <span class="Ux">NetBSD</span> kernel located on MS-DOS - drive D, one would issue:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>dosboot D:\NODOS\NETBSD</pre> -</div> -<p class="Pp">To boot from a <span class="Ux">NetBSD</span> floppy into single - user mode, type e.g.:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>dosboot -u fd0a:netbsd -s</pre> -</div> -</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">release(7)</a>, <a class="Xr">x86/boot(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <span class="Ux">NetBSD</span>/x86 - <code class="Nm">dosboot</code> command first appeared in - <span class="Ux">NetBSD 1.3</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp"><code class="Nm">dosboot</code> assumes that the processor is in - real mode at startup. It does not work well in the presence of MS-DOS - extenders and memory managers.</p> -<p class="Pp"><code class="Nm">dosboot</code> does not run directly under - Windows 95.</p> -<p class="Pp">In UFS mode, files can only be loaded from devices known to the - BIOS. The device names do not necessarily comply with the names later used - by the booted <span class="Ux">NetBSD</span> kernel.</p> -<p class="Pp">In MS-DOS mode, no useful boot device specification is passed to - <span class="Ux">NetBSD</span>. It is necessary to have the root device - hardwired into the kernel configuration or to enter it manually.</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> diff --git a/static/netbsd/man8/man8.x86/mbr.8 4.html b/static/netbsd/man8/man8.x86/mbr.8 4.html deleted file mode 100644 index 58f1bf01..00000000 --- a/static/netbsd/man8/man8.x86/mbr.8 4.html +++ /dev/null @@ -1,154 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">MBR(8)</td> - <td class="head-vol">System Manager's Manual (x86)</td> - <td class="head-rtitle">MBR(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">mbr</code>, <code class="Nm">bootselect</code> - — <span class="Nd">Master Boot Record bootcode</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">An IBM PC boots from a disk by loading its first sector and - executing the code in it. For a hard disk, this first sector usually - contains a table of partitions present on the disk. The first sector of a - disk containing such a table is called the Master Boot Record (MBR).</p> -<p class="Pp">The code present in the MBR will typically examine the partition - table, find the partition that is marked active, and boot from it. Booting - from a partition simply means loading the first sector in that partition, - and executing the code in it, as is done for the MBR itself.</p> -<p class="Pp"><span class="Ux">NetBSD</span> supplies several versions of the - MBR bootcode:</p> -<dl class="Bl-tag"> - <dt id="Normal"><a class="permalink" href="#Normal"><b class="Sy">Normal boot - code</b></a> <span class="Pa">/usr/mdec/mbr</span></dt> - <dd>This version has the same functionality as that supplied by DOS/Windows - and other operating systems: it picks the active partition and boots from - it. Its advantage over other, older MBRs, is that it can detect and use - extensions to the BIOS interface that will allow it to boot partitions - that cross or start beyond the 8 Gigabyte boundary.</dd> - <dt id="Bootselector"><a class="permalink" href="#Bootselector"><b class="Sy">Bootselector</b></a> - <span class="Pa">/usr/mdec/mbr_bootsel</span></dt> - <dd>The bootselecting MBR contains configurable code that will present the - user with a simple menu, allowing a choice between partitions to boot - from, and hard disks to boot from. The choices and default settings can be - configured through <a class="Xr">fdisk(8)</a>.</dd> - <dt id="Extended"><a class="permalink" href="#Extended"><b class="Sy">Extended - Bootselector</b></a> <span class="Pa">/usr/mdec/mbr_ext</span></dt> - <dd>The extended bootselecting MBR additionally allows - <span class="Ux">NetBSD</span> to be loaded from an Extended partition. It - only supports systems whose BIOS supports the extensions to boot - partitions beyond the 8 Gigabyte boundary.</dd> - <dt id="Serial"><a class="permalink" href="#Serial"><b class="Sy">Serial - Bootselector</b></a> <span class="Pa">/usr/mdec/mbr_com0</span></dt> - <dd>This has the same features as <span class="Pa">mbr_ext</span> but will - read and write from the first serial port. It assumes that the BIOS has - initialized the baud rate.</dd> - <dt id="Serial~2"><a class="permalink" href="#Serial~2"><b class="Sy">Serial - Bootselector</b></a> <span class="Pa">/usr/mdec/mbr_com0_9600</span></dt> - <dd>This has the same features as <span class="Pa">mbr_com0</span>. - Additionally, it initializes the serial port to 9600 baud.</dd> -</dl> -<p class="Pp">The rest of this manual page will discuss the bootselecting - versions of the MBR. The configurable items of the bootselector are:</p> -<dl class="Bl-tag"> - <dt>timeout</dt> - <dd>The number of seconds that the bootcode will wait for the user to press a - key, selecting a menu item. Must be in the range 0-3600, or -1 when it - will wait forever.</dd> - <dt>default</dt> - <dd>The default partition or disk to boot from, should the timeout - expire.</dd> -</dl> -<p class="Pp" id="bootmenu">The bootselector will output a menu of the - <a class="permalink" href="#bootmenu"><i class="Em">bootmenu</i></a> names - for each partition (as configured by <a class="Xr">fdisk(8)</a>). The user - can then select the partition or drive to boot from via the keyboard.</p> -<p class="Pp" id="1">The numeric keys - <a class="permalink" href="#1"><b class="Sy">1</b></a> upwards will initiate - a startup from the corresponding partition.</p> -<p class="Pp" id="F1">Function keys - <a class="permalink" href="#F1"><b class="Sy">F1</b></a> through - <a class="permalink" href="#F8"><b class="Sy" id="F8">F8</b></a> (keys - <a class="permalink" href="#a"><b class="Sy" id="a">a</b></a> through - <a class="permalink" href="#h"><b class="Sy" id="h">h</b></a> for the serial - versions) will boot from hard disks 0 through 7 (BIOS numbers 0x80 through - 0x87). Booting from a drive is simply done by reading the MBR of that drive - and executing it, so the bootcode present in the MBR of the chosen drive - determines which partition (if any) will be booted in the end.</p> -<p class="Pp" id="Enter">The - <a class="permalink" href="#Enter"><b class="Sy">Enter</b></a> key will - cause the bootcode to find the active partition, and boot from it. If no key - is pressed, the (configurable) default selection is picked.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<p class="Pp">The following errors are detected:</p> -<table class="Bl-column"> - <tr id="Code"> - <td><a class="permalink" href="#Code"><i class="Em">Code</i></a></td> - <td><a class="permalink" href="#Text"><i class="Em" id="Text">Text - message</i></a></td> - <td><a class="permalink" href="#Explanation"><i class="Em" id="Explanation">Explanation</i></a></td> - </tr> - <tr> - <td>1</td> - <td>No active partition</td> - <td>The MBR has a partition table without an active partition.</td> - </tr> - <tr> - <td>2</td> - <td>Disk read error</td> - <td>There was an error reading the bootsector for the partition or drive - selected.</td> - </tr> - <tr> - <td>3</td> - <td>No operating system</td> - <td>The bootsector was loaded successfully, but it was not valid (i.e., the - magic number check failed, or it contained no code).</td> - </tr> - <tr> - <td>L</td> - <td>Invalid CHS read</td> - <td>The boot partition cannot be read using a CHS read and the system BIOS - doesn't support LBA reads.</td> - </tr> - <tr> - <td>?</td> - <td></td> - <td>Unknown key.</td> - </tr> -</table> -<p class="Pp">The standard boot code will output the text message and stop. It - may be necessary to reset to the system to continue.</p> -<p class="Pp">The bootselect code will output 'Error <code>' and await - further input.</p> -</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">fdisk(8)</a>, - <a class="Xr">installboot(8)</a>, <a class="Xr">mbrlabel(8)</a>, - <a class="Xr">x86/boot(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The bootselect code has constraints because of the limited amount - of space available. The only way to be absolutely sure that a bootselector - will always fit on the disk when a partition table is used, is to make it - small enough to fit into the first sector (512 bytes, 404 excluding the - partition table and bootselect menu).</p> -<p class="Pp">The error messages are necessarily terse.</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> diff --git a/static/netbsd/man8/man8.x86/multiboot.8 4.html b/static/netbsd/man8/man8.x86/multiboot.8 4.html deleted file mode 100644 index 7f53ca34..00000000 --- a/static/netbsd/man8/man8.x86/multiboot.8 4.html +++ /dev/null @@ -1,85 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">MULTIBOOT(8)</td> - <td class="head-vol">System Manager's Manual (x86)</td> - <td class="head-rtitle">MULTIBOOT(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">multiboot</code> — - <span class="Nd">procedure for booting NetBSD/x86 from a Multiboot-compliant - boot loader</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">Multiboot is a specification that defines a protocol between a - boot loader and a kernel. This protocol allows passing boot information - between the two in a standard way, allowing any Multiboot-compliant boot - loader to boot any Multiboot-compliant kernel. The - <span class="Ux">NetBSD</span> kernel supports Multiboot if it was compiled - with <code class="Cd">options MULTIBOOT</code> (the default in the - ‘GENERIC’ and ‘GENERIC_LAPTOP’ - configurations).</p> -<p class="Pp">Unlike when using the native boot loader, the - <span class="Ux">NetBSD</span> kernel recognizes a set of command line - arguments if booted through a Multiboot-compliant boot loader. This is - because the Multiboot protocol is not complete enough to completely - configure a <span class="Ux">NetBSD</span> kernel.</p> -<p class="Pp">The following arguments are recognized:</p> -<dl class="Bl-tag"> - <dt id="console"><var class="Va">console</var></dt> - <dd>Specifies the console device name. Can be one of ‘com’ or - ‘pc’. If the former, <var class="Va">console_addr</var> and - <var class="Va">console_speed</var> should be given too.</dd> - <dt id="console_addr"><var class="Va">console_addr</var></dt> - <dd>Specifies the serial port address for the console. Defaults to the value - of <code class="Cd">options CONADDR</code> or ‘0x3f8’ if - this was not given.</dd> - <dt id="console_speed"><var class="Va">console_speed</var></dt> - <dd>Specifies the serial port speed for the console. Defaults to the value of - <code class="Cd">options CONSPEED</code> or ‘9600’ if this - was not given.</dd> - <dt id="root"><var class="Va">root</var></dt> - <dd>Specifies the name of the device to be mounted as the root partition. It - should not be needed because the kernel tries its best to guess which is - the root partition (basing the decision on the device from which the - kernel was loaded from). In cases where the automatic detection fails, - this flag comes useful. Example: ‘root=wd0e’.</dd> -</dl> -<section class="Ss"> -<h2 class="Ss" id="Booting_with_GRUB_Legacy"><a class="permalink" href="#Booting_with_GRUB_Legacy">Booting - with GRUB Legacy</a></h2> -<p class="Pp">GRUB Legacy is the most popular bootloader that supports - Multiboot. You can boot a <span class="Ux">NetBSD</span> kernel (assuming it - is compiled with Multiboot support) with a line similar to the following - one:</p> -<div class="Bd Pp Li"> -<pre>kernel (fd0)/netbsd.gz -c console=pc root=wd0e</pre> -</div> -</section> -</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">options(4)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp"><code class="Nm">multiboot</code> support first appeared in - <span class="Ux">NetBSD 4.0</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp"><code class="Nm">multiboot</code> support was added by - <span class="An">Julio M. Merino Vidal</span> - <<a class="Mt" href="mailto:jmmv@NetBSD.org">jmmv@NetBSD.org</a>>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">October 25, 2006</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/man8.x86/pxeboot.8 4.html b/static/netbsd/man8/man8.x86/pxeboot.8 4.html deleted file mode 100644 index 86bc5894..00000000 --- a/static/netbsd/man8/man8.x86/pxeboot.8 4.html +++ /dev/null @@ -1,240 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">PXEBOOT(8)</td> - <td class="head-vol">System Manager's Manual (x86)</td> - <td class="head-rtitle">PXEBOOT(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">pxeboot</code> — <span class="Nd">network - boot NetBSD/x86 through a PXE BIOS extension</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">pxeboot</code> is a - <span class="Ux">NetBSD</span> boot program running on top of a PXE BIOS - extension which is provided by the motherboard or a plug-in network adapter, - in accordance with the Intel Preboot eXecution Environment (PXE) - specification.</p> -<p class="Pp">By default, the <code class="Nm">pxeboot</code> program is - configured with modules loading and <a class="Xr">boot.cfg(5)</a> support - disabled. See <a class="Sx" href="#EXAMPLES">EXAMPLES</a> for how to enable - these options individually. This manual page assumes that - <a class="Xr">boot.cfg(5)</a> support is enabled.</p> -<p class="Pp">Network booting a system through PXE is a two-stage process:</p> -<ol class="Bl-enum"> - <li>The PXE BIOS issues a DHCP request and fetches the - <span class="Ux">NetBSD</span> <code class="Nm">pxeboot</code> program - using TFTP.</li> - <li>The <span class="Ux">NetBSD</span> <code class="Nm">pxeboot</code> program - takes control. It immediately issues another DHCP request to get the name - of a <a class="Xr">boot.cfg(5)</a> file to load, using - “boot.cfg” by default. If the boot config file is not found, - or if the supplied file appears not to be a boot configuration file, the - file is skipped. Otherwise it is loaded and obeyed as described in - <a class="Xr">boot.cfg(5)</a>. If a boot configuration is not loaded, the - user has the option to enter a limited version of the standard interactive - boot mode by pressing a key within five seconds. After this time, or after - the user's <code class="Ic">boot</code> command, another DHCP request is - issued and the kernel filename returned by the DHCP reply, using - “netbsd” by default, is loaded. To read the kernel file, the - NFS (version 2) or TFTP protocols can be used.</li> -</ol> -<p class="Pp">The DHCP request issued by the <span class="Ux">NetBSD</span> - <code class="Nm">pxeboot</code> program has the following special - parameters:</p> -<dl class="Bl-tag"> - <dt>Bootfile name</dt> - <dd>is set to “boot.cfg” during the first request, and then to - the <var class="Va">filename</var> argument on the - <code class="Ic">boot</code> command line typed in by the user (can be - empty), using “netbsd” in the non-interactive case.</dd> - <dt>DHCP Vendor class identifier tag</dt> - <dd>is set to “NetBSD:i386:libsa”.</dd> -</dl> -<p class="Pp">The DHCP server can use these fields (i.e. the DHCP vendor class - identifier tag and the requested file name, possibly supplied by the user's - command line input to the <code class="Nm">pxeboot</code> program) to - distinguish between the various originators of requests (PXE BIOS, first and - second <code class="Nm">pxeboot</code> stage, <span class="Ux">NetBSD</span> - kernel), and to alter its behaviour. For example, this can be used to - support alternative <span class="Ux">NetBSD</span> installations on one - machine.</p> -<p class="Pp">In addition to the standard network interface configuration, the - following fields in the DHCP reply are interpreted:</p> -<dl class="Bl-tag"> - <dt id="Root">Bootfile name</dt> - <dd>specifies the protocol to be used, and the filename of the boot config or - <span class="Ux">NetBSD</span> kernel to be booted, separated by a colon. - Available protocols are “nfs” and “tftp”. The - boot config or kernel filename part is interpreted relatively to the NFS - root directory (see the - <a class="permalink" href="#Root"><i class="Em">Root path</i></a> reply - field below) or the TFTP server's root directory (which might be a - subdirectory within the TFTP server's filesystem, depending on the - implementation), respectively. If the <i class="Em">Bootfile name</i> - field replied by the DHCP server does not contain a colon, it is ignored, - and the <var class="Va">filename</var> typed in at the - <code class="Nm">pxeboot</code> command line prompt (or the - “netbsd” default, see the section about the - <i class="Em">Bootfile name</i> field in the DHCP request above) is used. - If no protocol was specified, “nfs” is assumed.</dd> - <dt>Next server</dt> - <dd>is used as the location of the tftp server.</dd> - <dt>Swap server</dt> - <dd>can be used to override the “server IP address” if NFS is - used to access the kernel. This matches the behaviour of the - <span class="Ux">NetBSD</span> kernel to access its root file system on - NFS. This way, different TFTP and NFS servers can be communicated to the - DHCP client (it is actually a deficiency of the DHCP protocol to provide a - “root path” field but no corresponding IP address).</dd> - <dt>Root path</dt> - <dd>is used as path to be mounted in the NFS case to access the kernel file, - matching the <span class="Ux">NetBSD</span> kernel's behaviour.</dd> -</dl> -<p class="Pp">See <a class="Xr">x86/boot(8)</a> for the commands accepted in - interactive mode.</p> -<p class="Pp">By default the output from <code class="Nm">pxeboot</code> and - from the booted kernel will go to the system's BIOS console. This can be - changed to be one of the serial ports by using - <code class="Nm">installboot</code> to modify the boot options contained in - the <span class="Pa">pxeboot_ia32.bin</span> file.</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">/usr/mdec/pxeboot_ia32.bin</span></dt> - <dd style="width: auto;"> </dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1> -<p class="Pp">To enable <a class="Xr">boot.cfg(5)</a> support in the - <code class="Nm">pxeboot</code> program:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>installboot -e -o bootconf pxeboot_ia32.bin</pre> -</div> -<p class="Pp">To enable modules loading support in the - <code class="Nm">pxeboot</code> program:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>installboot -e -o modules pxeboot_ia32.bin</pre> -</div> -<p class="Pp">The first <span class="Pa">/etc/dhcpd.conf</span> example shows a - simple configuration which just loads “boot.cfg” and - “netbsd” from the client's NFS root directory, using the - defaults for protocol and kernel filename. Similar setups should be possible - with any BOOTP/DHCP server.</p> -<div class="Bd Pp Li"> -<pre>host myhost { - hardware ethernet 00:00:00:00:00:00; - fixed-address myhost; - option host-name "myhost"; - filename "pxeboot_ia32.bin"; - option swap-server mynfsserver; - option root-path "/export/myhost"; -}</pre> -</div> -<p class="Pp">The following <span class="Pa">/etc/dhcpd.conf</span> entry sets - loads the boot config and kernel over tftp. This can be used, for example, - for installing machines by using an install kernel.</p> -<div class="Bd Pp Li"> -<pre>host myhost { - hardware ethernet 00:00:00:00:00:00; - fixed-address myhost; - option host-name "myhost"; - next-server mytftpserver; - - # This section allows dhcpd to respond with different answers - # for the different tftp requests for the bootloader and kernel. - if substring (option vendor-class-identifier, 0, 20) - = "PXEClient:Arch:00000" { - filename "pxeboot_ia32.bin"; - } elsif substring (option vendor-class-identifier, 0, 17) - = "NetBSD:i386:libsa" { - if filename = "boot.cfg" { - filename "tftp:boot.cfg"; - } else if filename = "netbsd" { - filename "tftp:netbsd-INSTALL.gz"; - } - } -}</pre> -</div> -<p class="Pp">The following <span class="Pa">/etc/dhcpd.conf</span> entry shows - how different system installations can be booted depending on the user's - input on the <code class="Nm">pxeboot</code> command line.</p> -<div class="Bd Pp Li"> -<pre>host myhost { - hardware ethernet 00:00:00:00:00:00; - fixed-address myhost; - option host-name "myhost"; - next-server mytftpserver; - if substring (option vendor-class-identifier, 0, 9) = "PXEClient" { - filename "pxeboot_ia32.bin"; - } elsif filename = "boot.cfg" { - filename "tftp:boot.cfg"; - } elsif filename = "tftp" { - filename "tftp:netbsd.myhost"; - } else { - option swap-server mynfsserver; - option root-path "/export/myhost"; - if filename = "generic" { - filename "nfs:gennetbsd"; - } else { - filename "nfs:netbsd"; - } - } -}</pre> -</div> -<p class="Pp" id="next-server">The TFTP server is supplied using the - <a class="permalink" href="#next-server"><i class="Em">next-server</i></a> - directive. The NFS server for the root file system is - <a class="permalink" href="#mynfsserver"><i class="Em" id="mynfsserver">mynfsserver</i></a>. - The - <a class="permalink" href="#swap-server:root-path"><i class="Em" id="swap-server:root-path">swap-server:root-path</i></a> - is only used in the NFS case and by the <span class="Ux">NetBSD</span> - kernel to mount the root file system.</p> -</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">boot.cfg(5)</a>, <a class="Xr">dhcpd(8)</a>, - <a class="Xr">diskless(8)</a>, <a class="Xr">installboot(8)</a>, - <a class="Xr">x86/boot(8)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Intel Corporation</span>, - <span class="RsT">Preboot Execution Environment (PXE) Specification</span>, - <span class="RsN">Version 2.1</span>, <span class="RsD">September 20, - 1999</span>.</cite></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <span class="Ux">NetBSD</span>/x86 - <code class="Nm">pxeboot</code> command first appeared in - <span class="Ux">NetBSD 1.6</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">If an error is encountered while reading the - <span class="Ux">NetBSD</span> kernel file or if its file format wasn't - recognized, it is impossible to retry the operation because the PXE network - stack is already removed from the system RAM.</p> -<p class="Pp">You need the <code class="Nm">pxeboot</code> from an i386 build to - boot an i386 kernel, and that from an amd64 build to boot an amd64 - kernel.</p> -<p class="Pp">In a Xen setup, the <span class="Ux">NetBSD</span> DOM0 kernel is - loaded as a module, and cannot know the device from which the Xen hypervisor - was booted. In this case, the DOM0 kernel will fall back to the default boot - device (typically the first disk on the host). If the boot device is - different from the default one, consider passing additional arguments, like - <var class="Ar">bootdev</var>, to the DOM0 kernel as explained in the - <code class="Cm">load</code> command subsection in - <a class="Xr">x86/boot(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> diff --git a/static/netbsd/man8/nis.8 4.html b/static/netbsd/man8/nis.8 4.html deleted file mode 100644 index 7f6b534e..00000000 --- a/static/netbsd/man8/nis.8 4.html +++ /dev/null @@ -1,214 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">NIS(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">NIS(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">nis</code>, <code class="Nm">yp</code> — - <span class="Nd">description of the NIS (formerly YP) subsystem</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">ypbind</code></td> - <td>[<code class="Fl">-ypset</code>]</td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypbind</code></td> - <td>[<code class="Fl">-ypsetme</code>]</td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypset</code></td> - <td>[<code class="Fl">-h</code> <var class="Ar">host</var>] - [<code class="Fl">-d</code> <var class="Ar">domain</var>] - <var class="Ar">server</var></td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">yppoll</code></td> - <td>[<code class="Fl">-h</code> <var class="Ar">host</var>] - [<code class="Fl">-d</code> <var class="Ar">domain</var>] - <var class="Ar">mapname</var></td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypcat</code></td> - <td>[<code class="Fl">-kt</code>] [<code class="Fl">-d</code> - <var class="Ar">domainname</var>] <var class="Ar">mapname</var></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypcat</code></td> - <td><code class="Fl">-x</code></td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypmatch</code></td> - <td>[<code class="Fl">-kt</code>] [<code class="Fl">-d</code> - <var class="Ar">domainname</var>] <var class="Ar">key ... - mapname</var></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypmatch</code></td> - <td><code class="Fl">-x</code></td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypwhich</code></td> - <td>[<code class="Fl">-d</code> <var class="Ar">domain</var>] - [[<code class="Fl">-t</code>] <code class="Fl">-m</code> - [<var class="Ar">mname</var>] | <var class="Ar">host</var>]</td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypwhich</code></td> - <td><code class="Fl">-x</code></td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypserv</code></td> - <td>[<code class="Fl">-d</code>] [<code class="Fl">-x</code>]</td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">yppush</code></td> - <td>[<code class="Fl">-d</code> <var class="Ar">domainname</var>] - [<code class="Fl">-h</code> <var class="Ar">hostname</var>] - [<code class="Fl">-v</code>] <var class="Ar">mapname</var></td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypxfr</code></td> - <td>[<code class="Fl">-bcf</code>] [<code class="Fl">-d</code> - <var class="Ar">domain</var>] [<code class="Fl">-h</code> - <var class="Ar">host</var>] [<code class="Fl">-s</code> - <var class="Ar">domain</var>] [<code class="Fl">-C</code> - <var class="Ar">tid prog ipadd port</var>] - <var class="Ar">mapname</var></td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypinit</code></td> - <td><code class="Fl">-m</code> [<var class="Ar">domainname</var>]</td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">ypinit</code></td> - <td><code class="Fl">-s</code> <var class="Ar">master_server</var> - [<var class="Ar">domainname</var>]</td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">yptest</code></td> - <td></td> - </tr> -</table> -<p class="Pp"></p> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">rpc.yppasswdd</code></td> - <td>[<code class="Fl">-noshell</code>] [<code class="Fl">-nogecos</code>] - [<code class="Fl">-nopw</code>] [<code class="Fl">-m</code> - <var class="Ar">arg1 arg2 ...</var>]</td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The NIS subsystem allows network management of passwd and group - file entries through the functions <a class="Xr">getpwent(3)</a> and - <a class="Xr">getgrent(3)</a>. NIS also provides hooks for other client - programs, such as <a class="Xr">amd(8)</a> and - <a class="Xr">rpc.bootparamd(8)</a>, that can use NIS maps.</p> -<p class="Pp">Password maps in standard YP are insecure, because the pw_passwd - field is accessible by any user. A common solution to this is to generate a - secure map (using “makedbm -s”) which can only be accessed by - a client bound to a privileged port. To activate the secure map, see the - appropriate comment in <span class="Pa">/var/yp/Makefile.yp</span>.</p> -<p class="Pp">The NIS subsystem is conditionally started in - <span class="Pa">/etc/rc</span>. See the - <span class="Pa">/etc/rc.conf</span> file for configuration variables.</p> -</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">domainname(1)</a>, <a class="Xr">ypcat(1)</a>, - <a class="Xr">ypmatch(1)</a>, <a class="Xr">ypwhich(1)</a>, - <a class="Xr">ypclnt(3)</a>, <a class="Xr">group(5)</a>, - <a class="Xr">hosts_access(5)</a>, <a class="Xr">nsswitch.conf(5)</a>, - <a class="Xr">passwd(5)</a>, <a class="Xr">rc.conf(5)</a>, - <a class="Xr">rc(8)</a>, <a class="Xr">ypbind(8)</a>, - <a class="Xr">ypinit(8)</a>, <a class="Xr">yppoll(8)</a>, - <a class="Xr">yppush(8)</a>, <a class="Xr">ypserv(8)</a>, - <a class="Xr">ypset(8)</a>, <a class="Xr">yptest(8)</a>, - <a class="Xr">ypxfr(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The NIS client subsystem was originally written by Theo de Raadt - to be compatible with Sun's implementation. The NIS server suite was - originally written by Mats O Jansson.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">If <a class="Xr">ypbind(8)</a> cannot find a server, the system - behaves the same way as Sun's code: it hangs.</p> -<p class="Pp">The ‘secure map’ feature is not compatible with - non-BSD implementations as found e.g. in Solaris.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">February 26, 2005</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/pam.8 4.html b/static/netbsd/man8/pam.8 4.html deleted file mode 100644 index ba34745d..00000000 --- a/static/netbsd/man8/pam.8 4.html +++ /dev/null @@ -1,79 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">PAM(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">PAM(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">pam</code> — <span class="Nd">Pluggable - Authentication Modules framework</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The Pluggable Authentication Modules (PAM) framework is a system - of libraries that perform authentication tasks for services and - applications. Applications that use the PAM API may have their - authentication behavior configured by the system administrator through the - use of the service's PAM configuration file.</p> -<p class="Pp">PAM modules provide four classes of functionality:</p> -<dl class="Bl-tag"> - <dt>account</dt> - <dd>Account verification services such as password expiration and access - control.</dd> - <dt>auth</dt> - <dd>Authentication services. This usually takes the form of a - challenge-response conversation. However, PAM can also support, with - appropriate hardware support, biometric devices, smart-cards, and so - forth.</dd> - <dt>password</dt> - <dd>Password (or, more generally, authentication token) change and update - services.</dd> - <dt>session</dt> - <dd>Session management services. These are tasks that are performed before - access to a service is granted and after access to a service is withdrawn. - These may include updating activity logs or setting up and tearing down - credential forwarding agents.</dd> -</dl> -<p class="Pp">A primary feature of PAM is the notion of “stacking” - different modules together to form a processing chain for the task. This - allows fairly precise control over how a particular authentication task is - performed, and under what conditions. PAM module configurations may also - inherit stacks from other module configurations, providing some degree of - centralized administration.</p> -</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">login(1)</a>, <a class="Xr">passwd(1)</a>, - <a class="Xr">su(1)</a>, <a class="Xr">pam(3)</a>, - <a class="Xr">pam.conf(5)</a>, <a class="Xr">pam_chroot(8)</a>, - <a class="Xr">pam_deny(8)</a>, <a class="Xr">pam_echo(8)</a>, - <a class="Xr">pam_exec(8)</a>, <a class="Xr">pam_ftpusers(8)</a>, - <a class="Xr">pam_group(8)</a>, <a class="Xr">pam_guest(8)</a>, - <a class="Xr">pam_krb5(8)</a>, <a class="Xr">pam_ksu(8)</a>, - <a class="Xr">pam_lastlog(8)</a>, <a class="Xr">pam_login_access(8)</a>, - <a class="Xr">pam_nologin(8)</a>, <a class="Xr">pam_permit(8)</a>, - <a class="Xr">pam_radius(8)</a>, <a class="Xr">pam_rhosts(8)</a>, - <a class="Xr">pam_rootok(8)</a>, <a class="Xr">pam_securetty(8)</a>, - <a class="Xr">pam_self(8)</a>, <a class="Xr">pam_skey(8)</a>, - <a class="Xr">pam_ssh(8)</a>, <a class="Xr">pam_unix(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The Pluggable Authentication Module framework was originally - developed by SunSoft, described in DCE/OSF-RFC 86.0, and first deployed in - Solaris 2.6. It was later incorporated into the X/Open Single Sign-On - Service (XSSO) Pluggable Authentication Modules specification.</p> -<p class="Pp">The Pluggable Authentication Module framework first appeared in - <span class="Ux">NetBSD 3.0</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">February 28, 2005</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/rc.8 4.html b/static/netbsd/man8/rc.8 4.html deleted file mode 100644 index d14cb1d8..00000000 --- a/static/netbsd/man8/rc.8 4.html +++ /dev/null @@ -1,292 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">RC(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">RC(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">rc</code>, <code class="Nm">rc.local</code>, - <code class="Nm">rc.shutdown</code>, - <code class="Nm">rc.shutdown.final</code>, <code class="Nm">rc.d/</code> - — <span class="Nd">startup and shutdown scripts</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">rc</code></td> - <td></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">rc.local</code></td> - <td></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">rc.shutdown</code></td> - <td></td> - </tr> -</table> -<br/> -<table class="Nm"> - <tr> - <td><code class="Nm">rc.d/</code></td> - <td></td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">rc</code> is the command script which controls - the startup of various services, and is invoked by <a class="Xr">init(8)</a> - as part of the process of entering the automatic reboot to multi-user - startup, or after the single user mode shell has exited. If - <a class="Xr">init(8)</a> is starting the automatic reboot process, - <code class="Nm">rc</code> is invoked with the argument of - ‘autoboot’.</p> -<p class="Pp"><code class="Nm">rc.local</code> is a command script to which - local boot-time actions can be added. It is (nearly) the last thing invoked - by <code class="Nm">rc</code> during a normal boot.</p> -<p class="Pp"><code class="Nm">rc.shutdown</code> is the command script which - shuts down various services, and is invoked by <a class="Xr">shutdown(8)</a> - as part of the process of shutting down the system.</p> -<p class="Pp"><code class="Nm">rc.d/</code> is the directory which contains - various <a class="Xr">sh(1)</a> scripts, one for each service, which are - called by <code class="Nm">rc</code> at startup, - <code class="Nm">rc.shutdown</code> at shutdown, and as necessary during - system operation to stop, start, restart, reload, or otherwise control the - service.</p> -<section class="Ss"> -<h2 class="Ss" id="Operation_of_rc"><a class="permalink" href="#Operation_of_rc">Operation - of rc</a></h2> -<ol class="Bl-enum"> - <li>Source <span class="Pa">/etc/rc.subr</span> to load various - <a class="Xr">rc.subr(8)</a> shell functions to use.</li> - <li id="autoboot=yes">If autobooting, set - <a class="permalink" href="#autoboot=yes"><b class="Sy">autoboot=yes</b></a> - and enable a flag (<b class="Sy">rc_fast=yes</b>), which prevents the - <code class="Nm">rc.d</code> scripts from performing the check for already - running processes (thus speeding up the boot process). This - <b class="Sy">rc_fast=yes</b> speedup won't occur when - <code class="Nm">rc</code> is started up after exiting the single-user - shell.</li> - <li>Invoke <a class="Xr">rcorder(8)</a> to order the files in - <span class="Pa">/etc/rc.d/</span> that do not have a - “nostart” keyword (refer to <a class="Xr">rcorder(8)</a>'s - <code class="Fl">-s</code> flag), and assigns the result to a - variable.</li> - <li id="run_rc_script">Calls each script in turn using - <a class="permalink" href="#run_rc_script"><code class="Fn">run_rc_script</code></a>() - (from <a class="Xr">rc.subr(8)</a>), which sets <code class="Dv">$1</code> - to ‘start’, and sources the script in a sub-shell. If the - script has a ‘.sh’ suffix then it is sourced directly into - the current shell.</li> - <li>The output from the above steps is sent to a post-processor. If - <b class="Sy">rc_silent</b> is false, then the post-processor displays the - output. If <b class="Sy">rc_silent</b> is true, then the post-processor - invokes the command specified in <var class="Va">rc_silent_cmd</var> once - for each line, without otherwise displaying the output. Useful values for - <var class="Va">rc_silent_cmd</var> include “:” to display - nothing at all, and “twiddle” to display a spinning symbol - on the console. Regardless of the value of <b class="Sy">rc_silent</b>, - the post-processor saves the output in - <span class="Pa">/var/run/rc.log</span>.</li> -</ol> -</section> -<section class="Ss"> -<h2 class="Ss" id="Operation_of_rc.shutdown"><a class="permalink" href="#Operation_of_rc.shutdown">Operation - of rc.shutdown</a></h2> -<ol class="Bl-enum"> - <li>Source <span class="Pa">/etc/rc.subr</span> to load various - <a class="Xr">rc.subr(8)</a> shell functions to use.</li> - <li>Invoke <a class="Xr">rcorder(8)</a> to order the files in - <span class="Pa">/etc/rc.d/</span> that have a “shutdown” - keyword (refer to <a class="Xr">rcorder(8)</a>'s - <code class="Fl">-k</code> flag), reverses that order, and assigns the - result to a variable.</li> - <li>Calls each script in turn using <code class="Fn">run_rc_script</code>() - (from <a class="Xr">rc.subr(8)</a>), which sets <code class="Dv">$1</code> - to ‘stop’, and sources the script in a sub-shell. If the - script has a ‘.sh’ suffix then it is sourced directly into - the current shell.</li> - <li>Runs <span class="Pa">/etc/rc.shutdown.final</span> if it exists, passing - the currently ongoing shutdown action, which will be one of: - <ul class="Bl-bullet"> - <li>shutdown when going to single user mode.</li> - <li>halt when halting the machine (but not powering it down).</li> - <li>reboot when rebooting the machine.</li> - <li>poweroff when halting the machine and powering it off.</li> - </ul> - <p class="Pp">The script may be used to control additional actions, e.g. - powering off external devices, restarting a UPS (in case main power is - restored in the interval betweeen the computer powering off and the UPS - running out of battery).</p> - </li> -</ol> -</section> -<section class="Ss"> -<h2 class="Ss" id="Contents_of_rc.d/"><a class="permalink" href="#Contents_of_rc.d/">Contents - of rc.d/</a></h2> -<p class="Pp"><code class="Nm">rc.d/</code> is located in - <span class="Pa">/etc/rc.d</span>. The following file naming conventions are - currently used in <code class="Nm">rc.d/</code>:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt><span class="Pa">ALLUPPERCASE</span></dt> - <dd>Scripts that are ‘placeholders’ to ensure that certain - operations are performed before others. In order of startup, these are: - <dl class="Bl-tag"> - <dt><span class="Pa">NETWORKING</span></dt> - <dd>Ensure basic network services are running, including general network - configuration (<span class="Pa">network</span>) and - <span class="Pa">dhcpcd</span>.</dd> - <dt><span class="Pa">SERVERS</span></dt> - <dd>Ensure basic services (such as <span class="Pa">NETWORKING</span>, - <span class="Pa">ppp</span>, <span class="Pa">syslogd</span>, and - <span class="Pa">kdc</span>) exist for services that start early (such - as <span class="Pa">named</span>), because they're required by - <span class="Pa">DAEMON</span> below.</dd> - <dt><span class="Pa">DAEMON</span></dt> - <dd>Before all general purpose daemons such as - <span class="Pa">dhcpd</span>, <span class="Pa">lpd</span>, and - <span class="Pa">ntpd</span>.</dd> - <dt><span class="Pa">LOGIN</span></dt> - <dd>Before user login services (<span class="Pa">inetd</span>, - <span class="Pa">telnetd</span>, <span class="Pa">rshd</span>, - <span class="Pa">sshd</span>, and <span class="Pa">xdm</span>), as - well as before services which might run commands as users - (<span class="Pa">cron</span>, <span class="Pa">postfix</span>, and - <span class="Pa">sendmail</span>).</dd> - </dl> - </dd> - <dt><span class="Pa">inline.sh</span></dt> - <dd>Scripts that are sourced into the current shell rather than a sub-shell - have a ‘<span class="Pa">.sh</span>’ suffix. Extreme care - must be taken in using this, as the startup sequence will terminate if the - script causes the current shell process to terminate. - <span class="Pa">/etc/rc.d/bootconf.sh</span> uses this behaviour to allow - the user to select a different configuration (including - <span class="Pa">/etc/rc.conf</span>) early in the boot.</dd> - <dt id="stop_boot"><span class="Pa">service</span></dt> - <dd>Scripts that are sourced in a sub-shell. The boot does not stop if such a - script terminates with a non-zero status, but a script can stop the boot - if necessary by invoking the - <a class="permalink" href="#stop_boot"><code class="Fn">stop_boot</code></a>() - function (from <a class="Xr">rc.subr(8)</a>).</dd> -</dl> -</div> -<p class="Pp">Each script should contain <a class="Xr">rcorder(8)</a> keywords, - especially an appropriate “PROVIDE” entry.</p> -<p class="Pp">The scripts are expected to support at least the following - arguments:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="start"><a class="permalink" href="#start"><b class="Sy">start</b></a></dt> - <dd>Start the service. This should check that the service is to be started as - specified by <a class="Xr">rc.conf(5)</a>. Also checks if the service is - already running and refuses to start if it is. This latter check is not - performed by standard <span class="Ux">NetBSD</span> scripts if the system - is starting directly to multi-user mode, to speed up the boot - process.</dd> - <dt id="stop"><a class="permalink" href="#stop"><b class="Sy">stop</b></a></dt> - <dd>If the service is to be started as specified by - <a class="Xr">rc.conf(5)</a>, stop the service. This should check that the - service is running and complain if it's not.</dd> - <dt id="restart"><a class="permalink" href="#restart"><b class="Sy">restart</b></a></dt> - <dd>Perform a <b class="Sy">stop</b> then a <b class="Sy">start</b>.</dd> - <dt id="status"><a class="permalink" href="#status"><b class="Sy">status</b></a></dt> - <dd>If the script starts a process (rather than performing a one-off - operation), show the status of the process. Otherwise it's not necessary - to support this argument. Defaults to displaying the process ID of the - program (if running).</dd> - <dt id="poll"><a class="permalink" href="#poll"><b class="Sy">poll</b></a></dt> - <dd>If the script starts a process (rather than performing a one-off - operation), wait for the command to exit. Otherwise it's not necessary to - support this argument.</dd> - <dt id="rcvar"><a class="permalink" href="#rcvar"><b class="Sy">rcvar</b></a></dt> - <dd>Display which <a class="Xr">rc.conf(5)</a> variables are used to control - the startup of the service (if any).</dd> -</dl> -</div> -<p class="Pp">Other arguments (such as ‘reload’, - ‘dumpdb’, etc) can be added if necessary.</p> -<p class="Pp">The argument may have one of the following prefixes to alter its - operation:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="fast"><a class="permalink" href="#fast"><b class="Sy">fast</b></a></dt> - <dd>Skip the check for an existing running process. Sets - <b class="Sy">rc_fast=yes</b>.</dd> - <dt id="force"><a class="permalink" href="#force"><b class="Sy">force</b></a></dt> - <dd>Skips the <a class="Xr">rc.conf(5)</a> check, ignores a failure result - from any of the prerequisite checks, executes the command, and always - returns a zero exit status. Sets - <a class="permalink" href="#rc_force=yes"><b class="Sy" id="rc_force=yes">rc_force=yes</b></a>.</dd> - <dt id="one"><a class="permalink" href="#one"><b class="Sy">one</b></a></dt> - <dd>Skips the <a class="Xr">rc.conf(5)</a> check, but performs all other - prerequisite tests.</dd> -</dl> -</div> -<p class="Pp" id="run_rc_command">In order to simplify scripts, the - <a class="permalink" href="#run_rc_command"><code class="Fn">run_rc_command</code></a>() - function from <a class="Xr">rc.subr(8)</a> may be used.</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">/etc/rc</span></dt> - <dd>Startup script called by <a class="Xr">init(8)</a>.</dd> - <dt><span class="Pa">/etc/rc.d/</span></dt> - <dd>Directory containing control scripts for each service.</dd> - <dt><span class="Pa">/etc/rc.local</span></dt> - <dd>Local startup script.</dd> - <dt><span class="Pa">/etc/rc.shutdown</span></dt> - <dd>Shutdown script called by <a class="Xr">shutdown(8)</a>.</dd> - <dt><span class="Pa">/etc/rc.subr</span></dt> - <dd>Contains <a class="Xr">rc.subr(8)</a> functions used by various - scripts.</dd> - <dt><span class="Pa">/etc/rc.conf</span></dt> - <dd>System startup configuration file.</dd> - <dt><span class="Pa">/var/run/rc.log</span></dt> - <dd>Log file created by <code class="Nm">rc</code>.</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">rc.conf(5)</a>, <a class="Xr">init(8)</a>, - <a class="Xr">rc.subr(8)</a>, <a class="Xr">rcorder(8)</a>, - <a class="Xr">reboot(8)</a>, <a class="Xr">shutdown(8)</a></p> -<p class="Pp"><cite class="Rs"><span class="RsA">Luke Mewburn</span>, - <span class="RsT">The Design and Implementation of the NetBSD rc.d - system</span>, <i class="RsB">Proceedings of the FREENIX Track: 2001 USENIX - Annual Technical Conference</i>, <i class="RsI">USENIX Association</i>, - <a class="RsU" href="http://www.usenix.org/publications/library/proceedings/usenix01/freenix01/full_papers/mewburn/mewburn.pdf">http://www.usenix.org/publications/library/proceedings/usenix01/freenix01/full_papers/mewburn/mewburn.pdf</a>, - <span class="RsD">June 25-30, 2001</span>.</cite></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">rc</code> command appeared in - <span class="Ux">4.0BSD</span>. The <span class="Pa">/etc/rc.d</span> - support was implemented in <span class="Ux">NetBSD 1.5</span> by - <span class="An">Luke Mewburn</span> ⟨lukem@NetBSD.org⟩. The - post-processor, support for <var class="Va">rc_silent</var>, and saving - output to a file, was implemented in <span class="Ux">NetBSD 6.0</span> by - <span class="An">Alan Barrett</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">December 7, 2024</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/rc.subr.8 4.html b/static/netbsd/man8/rc.subr.8 4.html deleted file mode 100644 index 93855b5f..00000000 --- a/static/netbsd/man8/rc.subr.8 4.html +++ /dev/null @@ -1,575 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">RC.SUBR(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">RC.SUBR(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">rc.subr</code> — - <span class="Nd">functions used by system shell scripts</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1> -<ul class="Bl-item"> - <li>. <code class="Li">/etc/rc.subr</code></li> - <li id="backup_file"><a class="permalink" href="#backup_file"><code class="Ic">backup_file</code></a> - <var class="Ar">action</var> <var class="Ar">file</var> - <var class="Ar">current</var> <var class="Ar">backup</var></li> - <li id="basename"><a class="permalink" href="#basename"><code class="Ic">basename</code></a> - <var class="Ar">file</var> [<var class="Ar">suffix</var>]</li> - <li id="checkyesno"><a class="permalink" href="#checkyesno"><code class="Ic">checkyesno</code></a> - <var class="Ar">var</var></li> - <li id="check_pidfile"><a class="permalink" href="#check_pidfile"><code class="Ic">check_pidfile</code></a> - <var class="Ar">pidfile</var> <var class="Ar">procname</var> - [<var class="Ar">interpreter</var>]</li> - <li id="check_process"><a class="permalink" href="#check_process"><code class="Ic">check_process</code></a> - <var class="Ar">procname</var> [<var class="Ar">interpreter</var>]</li> - <li id="collapse_backslash_newline"><a class="permalink" href="#collapse_backslash_newline"><code class="Ic">collapse_backslash_newline</code></a></li> - <li id="dirname"><a class="permalink" href="#dirname"><code class="Ic">dirname</code></a> - <var class="Ar">file</var></li> - <li id="err"><a class="permalink" href="#err"><code class="Ic">err</code></a> - <var class="Ar">exitval</var> <var class="Ar">message</var></li> - <li id="load_rc_config"><a class="permalink" href="#load_rc_config"><code class="Ic">load_rc_config</code></a> - <var class="Ar">command</var></li> - <li id="load_rc_config_var"><a class="permalink" href="#load_rc_config_var"><code class="Ic">load_rc_config_var</code></a> - <var class="Ar">command</var> <var class="Ar">var</var></li> - <li id="mount_critical_filesystems"><a class="permalink" href="#mount_critical_filesystems"><code class="Ic">mount_critical_filesystems</code></a> - <var class="Ar">type</var></li> - <li id="no_rc_postprocess"><a class="permalink" href="#no_rc_postprocess"><code class="Ic">no_rc_postprocess</code></a> - <var class="Ar">command</var> [<var class="Ar">arguments</var>]</li> - <li id="print_rc_metadata"><a class="permalink" href="#print_rc_metadata"><code class="Ic">print_rc_metadata</code></a> - <var class="Ar">string</var></li> - <li id="print_rc_normal"><a class="permalink" href="#print_rc_normal"><code class="Ic">print_rc_normal</code></a> - [<code class="Fl">-n</code>] <var class="Ar">string</var></li> - <li id="rc_usage"><a class="permalink" href="#rc_usage"><code class="Ic">rc_usage</code></a> - <var class="Ar">command</var> [<var class="Ar">...</var>]</li> - <li id="reverse_list"><a class="permalink" href="#reverse_list"><code class="Ic">reverse_list</code></a> - <var class="Ar">item</var> [<var class="Ar">...</var>]</li> - <li id="run_rc_command"><a class="permalink" href="#run_rc_command"><code class="Ic">run_rc_command</code></a> - <var class="Ar">argument [parameters]</var></li> - <li id="run_rc_script"><a class="permalink" href="#run_rc_script"><code class="Ic">run_rc_script</code></a> - <var class="Ar">file</var> <var class="Ar">argument</var></li> - <li id="stop_boot"><a class="permalink" href="#stop_boot"><code class="Ic">stop_boot</code></a></li> - <li id="twiddle"><a class="permalink" href="#twiddle"><code class="Ic">twiddle</code></a></li> - <li id="wait_for_pids"><a class="permalink" href="#wait_for_pids"><code class="Ic">wait_for_pids</code></a> - [<var class="Ar">pid</var> [<var class="Ar">...</var>]]</li> - <li id="warn"><a class="permalink" href="#warn"><code class="Ic">warn</code></a> - <var class="Ar">message</var></li> - <li id="yesno_to_truefalse"><a class="permalink" href="#yesno_to_truefalse"><code class="Ic">yesno_to_truefalse</code></a> - <var class="Ar">var</var></li> -</ul> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">rc.subr</code> contains commonly used shell - script functions which are used by various scripts such as - <a class="Xr">rc(8)</a>, and the periodic system services which are - controlled by <a class="Xr">daily.conf(5)</a>, - <a class="Xr">monthly.conf(5)</a>, <a class="Xr">security.conf(5)</a>, and - <a class="Xr">weekly.conf(5)</a>.</p> -<p class="Pp">The <code class="Nm">rc.subr</code> functions are accessed by - sourcing <span class="Pa">/etc/rc.subr</span> into the current shell.</p> -<p class="Pp">The following shell functions are available:</p> -<dl class="Bl-tag"> - <dt id="backup_file~2"><a class="permalink" href="#backup_file~2"><code class="Ic">backup_file</code></a> - <var class="Ar">action</var> <var class="Ar">file</var> - <var class="Ar">current</var> <var class="Ar">backup</var></dt> - <dd>Make a backup copy of <var class="Ar">file</var> into - <var class="Ar">current</var>. If the <a class="Xr">rc.conf(5)</a> - variable - <a class="permalink" href="#backup_uses_rcs"><b class="Sy" id="backup_uses_rcs">backup_uses_rcs</b></a> - is ‘YES’, use <a class="Xr">rcs(1)</a> to archive the - previous version of <var class="Ar">current</var>, otherwise save the - previous version of <var class="Ar">current</var> as - <var class="Ar">backup</var>. - <p class="Pp"><var class="Ar">action</var> may be one of the following:</p> - <dl class="Bl-tag"> - <dt id="add"><a class="permalink" href="#add"><b class="Sy">add</b></a></dt> - <dd><var class="Ar">file</var> is now being backed up by or possibly - re-entered into this backup mechanism. <var class="Ar">current</var> - is created, and if necessary, the <a class="Xr">rcs(1)</a> files are - created as well.</dd> - <dt id="update"><a class="permalink" href="#update"><b class="Sy">update</b></a></dt> - <dd><var class="Ar">file</var> has changed and needs to be backed up. If - <var class="Ar">current</var> exists, it is copied to - <var class="Ar">backup</var> or checked into <a class="Xr">rcs(1)</a> - (if the repository file is old), and then <var class="Ar">file</var> - is copied to <var class="Ar">current</var>.</dd> - <dt id="remove"><a class="permalink" href="#remove"><b class="Sy">remove</b></a></dt> - <dd><var class="Ar">file</var> is no longer being tracked by this backup - mechanism. If <a class="Xr">rcs(1)</a> is being used, an empty file is - checked in and <var class="Ar">current</var> is removed, otherwise - <var class="Ar">current</var> is moved to - <var class="Ar">backup</var>.</dd> - </dl> - </dd> - <dt id="basename~2"><a class="permalink" href="#basename~2"><code class="Ic">basename</code></a> - <var class="Ar">file</var> [<var class="Ar">suffix</var>]</dt> - <dd>Just like <a class="Xr">basename(1)</a>, except implemented using shell - built-in commands, and usable before the <span class="Pa">/usr/bin</span> - direcory is available.</dd> - <dt id="checkyesno~2"><a class="permalink" href="#checkyesno~2"><code class="Ic">checkyesno</code></a> - <var class="Ar">var</var></dt> - <dd>Return 0 if <var class="Ar">var</var> is defined to ‘YES’, - ‘TRUE’, ‘ON’, or ‘1’. Return 1 - if <var class="Ar">var</var> is defined to ‘NO’, - ‘FALSE’, ‘OFF’, or ‘0’. - Otherwise, warn that <var class="Ar">var</var> is not set correctly. The - values are case insensitive. - <p class="Pp">Note that the warning message shown by this function when - <var class="Ar">var</var> is not set references a manual page where the - user can find more information. Its name is picked up from the - <b class="Sy">rcvar_manpage</b> variable.</p> - </dd> - <dt id="check_pidfile~2"><a class="permalink" href="#check_pidfile~2"><code class="Ic">check_pidfile</code></a> - <var class="Ar">pidfile</var> <var class="Ar">procname</var> - [<var class="Ar">interpreter</var>]</dt> - <dd>Parses the first word of the first line of <var class="Ar">pidfile</var> - for a PID, and ensures that the process with that PID is running and its - first argument matches <var class="Ar">procname</var>. Prints the matching - PID if successful, otherwise nothing. If <var class="Ar">interpreter</var> - is provided, parse the first line of <var class="Ar">procname</var>, - ensure that the line is of the form - <div class="Bd Bd-indent"><code class="Li">#! interpreter [...]</code></div> - and use <var class="Ar">interpreter</var> with its optional arguments and - <var class="Ar">procname</var> appended as the process string to search - for.</dd> - <dt id="check_process~2"><a class="permalink" href="#check_process~2"><code class="Ic">check_process</code></a> - <var class="Ar">procname</var> [<var class="Ar">interpreter</var>]</dt> - <dd>Prints the PIDs of any processes that are running with a first argument - that matches <var class="Ar">procname</var>. - <var class="Ar">interpreter</var> is handled as per - <code class="Ic">check_pidfile</code>.</dd> - <dt id="collapse_backslash_newline~2"><a class="permalink" href="#collapse_backslash_newline~2"><code class="Ic">collapse_backslash_newline</code></a></dt> - <dd>Copy input to output, collapsing - ⟨backslash⟩⟨newline⟩ to nothing, but leaving - other backslashes alone. <code class="Ic">dirname</code> - <var class="Ar">file</var> Just like <a class="Xr">dirname(1)</a>, except - implemented using shell built-in commands, and usable before the - <span class="Pa">/usr/bin</span> direcory is available.</dd> - <dt id="err~2"><a class="permalink" href="#err~2"><code class="Ic">err</code></a> - <var class="Ar">exitval</var> <var class="Ar">message</var></dt> - <dd>Display an error message to <i class="Em">stderr</i>, log it to the system - log using <a class="Xr">logger(1)</a>, and <code class="Cm">exit</code> - with an exit value of <var class="Ar">exitval</var>. The error message - consists of the script name (from <b class="Sy">$0</b>), followed by - “: ERROR: ”, and then <var class="Ar">message</var>.</dd> - <dt id="load_rc_config~2"><a class="permalink" href="#load_rc_config~2"><code class="Ic">load_rc_config</code></a> - <var class="Ar">command</var></dt> - <dd>Source in the <a class="Xr">rc.conf(5)</a> configuration files for - <var class="Ar">command</var>. First, <span class="Pa">/etc/rc.conf</span> - is sourced if it has not yet been read in. Then, - <span class="Pa">/etc/rc.conf.d/</span><var class="Ar">command</var> is - sourced if it is an existing file. The latter may also contain other - variable assignments to override <code class="Ic">run_rc_command</code> - arguments defined by the calling script, to provide an easy mechanism for - an administrator to override the behaviour of a given - <a class="Xr">rc.d(8)</a> script without requiring the editing of that - script.</dd> - <dt id="load_rc_config_var~2"><a class="permalink" href="#load_rc_config_var~2"><code class="Ic">load_rc_config_var</code></a> - <var class="Ar">command</var> <var class="Ar">var</var></dt> - <dd>Read the <a class="Xr">rc.conf(5)</a> variable <var class="Ar">var</var> - for <var class="Ar">command</var> and set in the current shell, using - <code class="Ic">load_rc_config</code> in a sub-shell to prevent unwanted - side effects from other variable assignments.</dd> - <dt id="mount_critical_filesystems~2"><a class="permalink" href="#mount_critical_filesystems~2"><code class="Ic">mount_critical_filesystems</code></a> - <var class="Ar">type</var></dt> - <dd>Go through a list of critical file systems, as found in the - <a class="Xr">rc.conf(5)</a> variable - <a class="permalink" href="#critical_filesystems_"><b class="Sy" id="critical_filesystems_">critical_filesystems_</b></a><var class="Ar">type</var>, - mounting each one that is not currently mounted.</dd> - <dt id="no_rc_postprocess~2"><a class="permalink" href="#no_rc_postprocess~2"><code class="Ic">no_rc_postprocess</code></a> - <var class="Ar">command</var> [<var class="Ar">arguments</var>]</dt> - <dd>Execute the specified command with the specified arguments, in such a way - that its output bypasses the post-processor that <a class="Xr">rc(8)</a> - uses for most commands. This implies that the output will not appear in - the <span class="Pa">/var/run/rc.log</span> file, and will appear on the - console regardless of the value of <var class="Va">rc_silent</var>. This - is expected to be useful for interactive commands, and this mechanism is - automatically used by <code class="Ic">run_rc_command</code> when a script - contains the <a class="Xr">rcorder(8)</a> keyword - “interactive”. - <p class="Pp">If invoked from a context that does not appear to be under the - control of <a class="Xr">rc(8)</a>, then the command is executed without - special treatment.</p> - </dd> - <dt id="print_rc_metadata~2"><a class="permalink" href="#print_rc_metadata~2"><code class="Ic">print_rc_metadata</code></a> - <var class="Ar">string</var></dt> - <dd>Print the specified <var class="Ar">string</var> in such a way that it - should be handled as meta-data by the <a class="Xr">rc(8)</a> - post-processor. If invoked from a context that does not appear to be under - the control of <a class="Xr">rc(8)</a>, then the - <var class="Ar">string</var> is discarded. - <p class="Pp">Any <a class="Xr">rc.d(8)</a> script may invoke this function - with an argument that begins with “note:”, followed by one - line of arbitrary text; the text will be logged by - <a class="Xr">rc(8)</a> but will not be displayed on the console.</p> - <p class="Pp">The use of arguments that do not begin with - “note:” is reserved for internal use by - <a class="Xr">rc(8)</a> and <code class="Nm">rc.subr</code>.</p> - </dd> - <dt id="print_rc_normal~2"><a class="permalink" href="#print_rc_normal~2"><code class="Ic">print_rc_normal</code></a> - [<code class="Fl">-n</code>] <var class="Ar">string</var></dt> - <dd>Print the specified <var class="Ar">string</var> in such a way that it - should be handled as normal output by the <a class="Xr">rc(8)</a> - post-processor. If invoked from a context that does not appear to be under - the control of <a class="Xr">rc(8)</a>, then the - <var class="Ar">string</var> is printed to standard output. - <p class="Pp">If the <code class="Fl">-n</code> flag is specified, then the - string is printed without a newline.</p> - <p class="Pp">Intended use cases include:</p> - <ul class="Bl-bullet"> - <li>An rc.d script can use “<b class="Sy">print_rc_normal</b> - <code class="Fl">-n</code>” to print a partial line in such a - way that it appears immediately instead of being buffered by - <a class="Xr">rc(8)</a>'s post-processor.</li> - <li>An rc.d script that is run via the <b class="Sy">no_rc_postprocess</b> - function (so most of its output is invisible to - <a class="Xr">rc(8)</a>'s post-processor) can use - <b class="Sy">print_rc_normal</b> to force some of its output to be - seen by the post-processor.</li> - </ul> - </dd> - <dt id="rc_usage~2"><a class="permalink" href="#rc_usage~2"><code class="Ic">rc_usage</code></a> - <var class="Ar">command</var> [<var class="Ar">...</var>]</dt> - <dd>Print a usage message for <b class="Sy">$0</b>, with - <var class="Ar">commands</var> being the list of valid arguments prefixed - by “[fast|force|one]”.</dd> - <dt id="reverse_list~2"><a class="permalink" href="#reverse_list~2"><code class="Ic">reverse_list</code></a> - <var class="Ar">item</var> [<var class="Ar">...</var>]</dt> - <dd>Print the list of <var class="Ar">items</var> in reverse order.</dd> - <dt id="run_rc_command~2"><a class="permalink" href="#run_rc_command~2"><code class="Ic">run_rc_command</code></a> - <var class="Ar">argument</var> [<var class="Ar">parameter ...</var>]</dt> - <dd>Run the <var class="Ar">argument</var> method for the current - <a class="Xr">rc.d(8)</a> script, based on the settings of various shell - variables. <code class="Ic">run_rc_command</code> is extremely flexible, - and allows fully functional <a class="Xr">rc.d(8)</a> scripts to be - implemented in a small amount of shell code. The optional set of - parameters is passed verbatim to the command, but not to its pre/post - hooks. - <p class="Pp"><var class="Ar">argument</var> is searched for in the list of - supported commands, which may be one of:</p> - <div class="Bd-indent"> - <dl class="Bl-tag"> - <dt id="start"><a class="permalink" href="#start"><b class="Sy">start</b></a></dt> - <dd>Start the service. This should check that the service is to be started - as specified by <a class="Xr">rc.conf(5)</a>. Also checks if the - service is already running and refuses to start if it is. This latter - check is not performed by standard <span class="Ux">NetBSD</span> - scripts if the system is starting directly to multi-user mode, to - speed up the boot process.</dd> - <dt id="stop"><a class="permalink" href="#stop"><b class="Sy">stop</b></a></dt> - <dd>If the service is to be started as specified by - <a class="Xr">rc.conf(5)</a>, stop the service. This should check that - the service is running and complain if it's not.</dd> - <dt id="restart"><a class="permalink" href="#restart"><b class="Sy">restart</b></a></dt> - <dd>Perform a <b class="Sy">stop</b> then a <b class="Sy">start</b>. - Defaults to displaying the process ID of the program (if - running).</dd> - <dt id="rcvar"><a class="permalink" href="#rcvar"><b class="Sy">rcvar</b></a></dt> - <dd>Display which <a class="Xr">rc.conf(5)</a> variables are used to - control the startup of the service (if any).</dd> - </dl> - </div> - <p class="Pp">If <b class="Sy">pidfile</b> or <b class="Sy">procname</b> is - set, also support:</p> - <div class="Bd-indent"> - <dl class="Bl-tag"> - <dt id="poll"><a class="permalink" href="#poll"><b class="Sy">poll</b></a></dt> - <dd>Wait for the command to exit.</dd> - <dt id="status"><a class="permalink" href="#status"><b class="Sy">status</b></a></dt> - <dd>Show the status of the process.</dd> - </dl> - </div> - <p class="Pp">Other supported commands are listed in the optional variable - <b class="Sy">extra_commands</b>.</p> - <p class="Pp"><var class="Ar">argument</var> may have one of the following - prefixes which alters its operation:</p> - <div class="Bd-indent"> - <dl class="Bl-tag"> - <dt id="fast"><a class="permalink" href="#fast"><b class="Sy">fast</b></a></dt> - <dd>Skip the check for an existing running process, and sets - <a class="permalink" href="#rc_fast=YES"><b class="Sy" id="rc_fast=YES">rc_fast=YES</b></a>.</dd> - <dt id="force"><a class="permalink" href="#force"><b class="Sy">force</b></a></dt> - <dd>Skip the checks for <b class="Sy">rcvar</b> being set to yes, and sets - <a class="permalink" href="#rc_force=YES"><b class="Sy" id="rc_force=YES">rc_force=YES</b></a>. - This ignores <var class="Ar">argument</var><b class="Sy">_precmd</b> - returning non-zero, and ignores any of the - <b class="Sy">required_*</b> tests failing, and always returns a zero - exit status.</dd> - <dt id="one"><a class="permalink" href="#one"><b class="Sy">one</b></a></dt> - <dd>Skip the checks for <b class="Sy">rcvar</b> being set to yes, but - performs all the other prerequisite tests.</dd> - </dl> - </div> - <p class="Pp"><code class="Ic">run_rc_command</code> uses the following - shell variables to control its behaviour. Unless otherwise stated, these - are optional.</p> - <div class="Bd-indent"> - <dl class="Bl-tag"> - <dt id="name"><a class="permalink" href="#name"><b class="Sy">name</b></a></dt> - <dd>The name of this script. This is not optional.</dd> - <dt id="rcvar~2"><a class="permalink" href="#rcvar~2"><b class="Sy">rcvar</b></a></dt> - <dd>The value of <b class="Sy">rcvar</b> is checked with - <code class="Ic">checkyesno</code> to determine if this method should - be run.</dd> - <dt id="rcvar_manpage"><a class="permalink" href="#rcvar_manpage"><b class="Sy">rcvar_manpage</b></a></dt> - <dd>The manual page containing information about <b class="Sy">rcvar</b>. - It will be part of the warning message shown when - <b class="Sy">rcvar</b> is undefined. Defaults to - <a class="Xr">rc.conf(5)</a>.</dd> - <dt id="command"><a class="permalink" href="#command"><b class="Sy">command</b></a></dt> - <dd>Full path to the command. Not required if - <var class="Ar">argument</var><b class="Sy">_cmd</b> is defined for - each supported keyword.</dd> - <dt id="command_args"><a class="permalink" href="#command_args"><b class="Sy">command_args</b></a></dt> - <dd>Optional arguments and/or shell directives for - <b class="Sy">command</b>.</dd> - <dt id="command_interpreter"><a class="permalink" href="#command_interpreter"><b class="Sy">command_interpreter</b></a></dt> - <dd><a class="permalink" href="#command~2"><b class="Sy" id="command~2">command</b></a> - is started with - <div class="Bd Bd-indent"><code class="Li">#! command_interpreter - [...]</code></div> - which results in its <a class="Xr">ps(1)</a> command being - <div class="Bd Bd-indent"><code class="Li">command_interpreter [...] - command</code></div> - so use that string to find the PID(s) of the running command rather than - ‘<code class="Li">command</code>’.</dd> - <dt id="extra_commands"><a class="permalink" href="#extra_commands"><b class="Sy">extra_commands</b></a></dt> - <dd>Extra commands/keywords/arguments supported.</dd> - <dt id="pidfile"><a class="permalink" href="#pidfile"><b class="Sy">pidfile</b></a></dt> - <dd>Path to pid file. Used to determine the PID(s) of the running command. - If <b class="Sy">pidfile</b> is set, use - <div class="Bd Bd-indent"><code class="Li">check_pidfile $pidfile - $procname</code></div> - to find the PID. Otherwise, if <b class="Sy">command</b> is set, use - <div class="Bd Bd-indent"><code class="Li">check_process - $procname</code></div> - to find the PID.</dd> - <dt id="procname"><a class="permalink" href="#procname"><b class="Sy">procname</b></a></dt> - <dd>Process name to check for. Defaults to the value of - <b class="Sy">command</b>.</dd> - <dt id="required_dirs"><a class="permalink" href="#required_dirs"><b class="Sy">required_dirs</b></a></dt> - <dd>Check for the existence of the listed directories before running the - default start method.</dd> - <dt id="required_files"><a class="permalink" href="#required_files"><b class="Sy">required_files</b></a></dt> - <dd>Check for the readability of the listed files before running the - default start method.</dd> - <dt id="required_vars"><a class="permalink" href="#required_vars"><b class="Sy">required_vars</b></a></dt> - <dd>Perform <code class="Ic">checkyesno</code> on each of the list - variables before running the default start method.</dd> - <dt id="$_name__chdir"><a class="permalink" href="#$_name__chdir"><b class="Sy">${name}_chdir</b></a></dt> - <dd>Directory to <code class="Ic">cd</code> to before running - <b class="Sy">command</b>, if <b class="Sy">${name}_chroot</b> is not - provided.</dd> - <dt id="$_name__chroot"><a class="permalink" href="#$_name__chroot"><b class="Sy">${name}_chroot</b></a></dt> - <dd>Directory to <a class="Xr">chroot(8)</a> to before running - <b class="Sy">command</b>. Only supported after - <span class="Pa">/usr</span> is mounted.</dd> - <dt id="$_name__env"><a class="permalink" href="#$_name__env"><b class="Sy">${name}_env</b></a></dt> - <dd>List of additional or modified environment variables to set when - starting <b class="Sy">command</b>.</dd> - <dt id="$_name__flags"><a class="permalink" href="#$_name__flags"><b class="Sy">${name}_flags</b></a></dt> - <dd>Arguments to call <b class="Sy">command</b> with. This is usually set - in <a class="Xr">rc.conf(5)</a>, and not in the - <a class="Xr">rc.d(8)</a> script. The environment variable - ‘<code class="Ev">flags</code>’ can be used to override - this.</dd> - <dt id="$_name__nice"><a class="permalink" href="#$_name__nice"><b class="Sy">${name}_nice</b></a></dt> - <dd><a class="Xr">nice(1)</a> level to run <b class="Sy">command</b> as. - Only supported after <span class="Pa">/usr</span> is mounted.</dd> - <dt id="$_name__user"><a class="permalink" href="#$_name__user"><b class="Sy">${name}_user</b></a></dt> - <dd>User to run <b class="Sy">command</b> as, using - <a class="Xr">chroot(8)</a>. if <b class="Sy">${name}_chroot</b> is - set, otherwise uses <a class="Xr">su(1)</a>. Only supported after - <span class="Pa">/usr</span> is mounted.</dd> - <dt id="$_name__group"><a class="permalink" href="#$_name__group"><b class="Sy">${name}_group</b></a></dt> - <dd>Group to run the chrooted <b class="Sy">command</b> as.</dd> - <dt id="$_name__groups"><a class="permalink" href="#$_name__groups"><b class="Sy">${name}_groups</b></a></dt> - <dd>Comma separated list of supplementary groups to run the chrooted - <b class="Sy">command</b> with.</dd> - <dt><var class="Ar">argument</var><b class="Sy">_cmd</b></dt> - <dd>Shell commands which override the default method for - <var class="Ar">argument</var>.</dd> - <dt><var class="Ar">argument</var><b class="Sy">_precmd</b></dt> - <dd>Shell commands to run just before running - <var class="Ar">argument</var><b class="Sy">_cmd</b> or the default - method for <var class="Ar">argument</var>. If this returns a non-zero - exit code, the main method is not performed. If the default method is - being executed, this check is performed after the - <b class="Sy">required_*</b> checks and process (non-)existence - checks.</dd> - <dt><var class="Ar">argument</var><b class="Sy">_postcmd</b></dt> - <dd>Shell commands to run if running - <var class="Ar">argument</var><b class="Sy">_cmd</b> or the default - method for <var class="Ar">argument</var> returned a zero exit - code.</dd> - <dt id="sig_stop"><a class="permalink" href="#sig_stop"><b class="Sy">sig_stop</b></a></dt> - <dd>Signal to send the processes to stop in the default - <b class="Sy">stop</b> method. Defaults to - <code class="Dv">SIGTERM</code>.</dd> - <dt id="sig_reload"><a class="permalink" href="#sig_reload"><b class="Sy">sig_reload</b></a></dt> - <dd>Signal to send the processes to reload in the default - <b class="Sy">reload</b> method. Defaults to - <code class="Dv">SIGHUP</code>.</dd> - </dl> - </div> - <p class="Pp">For a given method <var class="Ar">argument</var>, if - <var class="Ar">argument</var><b class="Sy">_cmd</b> is not defined, - then a default method is provided by - <b class="Sy">run_rc_command</b>:</p> - <div class="Bd-indent"> - <dl class="Bl-tag"> - <dt id="Argument"><a class="permalink" href="#Argument"><b class="Sy">Argument</b></a></dt> - <dd><a class="permalink" href="#Default"><b class="Sy" id="Default">Default - method</b></a></dd> - <dt id="start~2"><a class="permalink" href="#start~2"><b class="Sy">start</b></a></dt> - <dd>If <b class="Sy">command</b> is not running and - <code class="Ic">checkyesno</code> <b class="Sy">rcvar</b> succeeds, - start <b class="Sy">command</b>.</dd> - <dt id="stop~2"><a class="permalink" href="#stop~2"><b class="Sy">stop</b></a></dt> - <dd>Determine the PIDs of <b class="Sy">command</b> with - <code class="Ic">check_pidfile</code> or - <code class="Ic">check_process</code> (as appropriate), - <code class="Ic">kill</code> <b class="Sy">sig_stop</b> those PIDs, - and run <code class="Ic">wait_for_pids</code> on those PIDs.</dd> - <dt id="reload"><a class="permalink" href="#reload"><b class="Sy">reload</b></a></dt> - <dd>Similar to <b class="Sy">stop</b>, except that it uses - <b class="Sy">sig_reload</b> instead, and doesn't run - <code class="Ic">wait_for_pids</code>.</dd> - <dt id="restart~2"><a class="permalink" href="#restart~2"><b class="Sy">restart</b></a></dt> - <dd>Runs the <b class="Sy">stop</b> method, then the - <b class="Sy">start</b> method.</dd> - <dt id="status~2"><a class="permalink" href="#status~2"><b class="Sy">status</b></a></dt> - <dd>Show the PID of <b class="Sy">command</b>, or some other script - specific status operation.</dd> - <dt id="poll~2"><a class="permalink" href="#poll~2"><b class="Sy">poll</b></a></dt> - <dd>Wait for <b class="Sy">command</b> to exit.</dd> - <dt id="rcvar~3"><a class="permalink" href="#rcvar~3"><b class="Sy">rcvar</b></a></dt> - <dd>Display which <a class="Xr">rc.conf(5)</a> variable is used (if any). - This method always works, even if the appropriate - <a class="Xr">rc.conf(5)</a> variable is set to - ‘NO’.</dd> - </dl> - </div> - <p class="Pp">The following variables are available to the methods (such as - <var class="Ar">argument</var><b class="Sy">_cmd</b>) as well as after - <code class="Ic">run_rc_command</code> has completed:</p> - <div class="Bd-indent"> - <dl class="Bl-tag"> - <dt id="rc_arg"><a class="permalink" href="#rc_arg"><b class="Sy">rc_arg</b></a></dt> - <dd>Argument provided to <b class="Sy">run_rc_command</b>, after fast and - force processing has been performed.</dd> - <dt id="rc_flags"><a class="permalink" href="#rc_flags"><b class="Sy">rc_flags</b></a></dt> - <dd>Flags to start the default command with. Defaults to - <b class="Sy">${name}_flags</b>, unless overridden by the environment - variable ‘<code class="Ev">flags</code>’. This variable - may be changed by the - <var class="Ar">argument</var><b class="Sy">_precmd</b> method.</dd> - <dt id="rc_pid"><a class="permalink" href="#rc_pid"><b class="Sy">rc_pid</b></a></dt> - <dd>PID of <b class="Sy">command</b> (if appropriate).</dd> - <dt id="rc_fast"><a class="permalink" href="#rc_fast"><b class="Sy">rc_fast</b></a></dt> - <dd>Not empty if “fast” prefix was used.</dd> - <dt id="rc_force"><a class="permalink" href="#rc_force"><b class="Sy">rc_force</b></a></dt> - <dd>Not empty if “force” prefix was used.</dd> - </dl> - </div> - </dd> - <dt id="run_rc_script~2"><a class="permalink" href="#run_rc_script~2"><code class="Ic">run_rc_script</code></a> - <var class="Ar">file</var> <var class="Ar">argument</var></dt> - <dd>Start the script <var class="Ar">file</var> with an argument of - <var class="Ar">argument</var>, and handle the return value from the - script. - <p class="Pp">Various shell variables are unset before - <var class="Ar">file</var> is started:</p> - <div class="Bd Pp Bd-indent"><b class="Sy">name</b>, - <b class="Sy">command</b>, <b class="Sy">command_args</b>, - <b class="Sy">command_interpreter</b>, <b class="Sy">extra_commands</b>, - <b class="Sy">pidfile</b>, <b class="Sy">rcvar</b>, - <b class="Sy">required_dirs</b>, <b class="Sy">required_files</b>, - <b class="Sy">required_vars</b>, - <var class="Ar">argument</var><b class="Sy">_cmd</b>, - <var class="Ar">argument</var><b class="Sy">_precmd</b>. - <var class="Ar">argument</var><b class="Sy">_postcmd</b>.</div> - <p class="Pp">The startup behaviour of <var class="Ar">file</var> depends - upon the following checks:</p> - <ol class="Bl-enum"> - <li>If <var class="Ar">file</var> ends in <span class="Pa">.sh</span>, it - is sourced into the current shell.</li> - <li>If <var class="Ar">file</var> appears to be a backup or scratch file - (e.g., with a suffix of ‘~’, ‘#’, - ‘.OLD’, or ‘.orig’), ignore it.</li> - <li>If <var class="Ar">file</var> is not executable, ignore it.</li> - <li id="rc_fast_and_loose">If the <a class="Xr">rc.conf(5)</a> variable - <a class="permalink" href="#rc_fast_and_loose"><b class="Sy">rc_fast_and_loose</b></a> - is empty, source <var class="Ar">file</var> in a sub shell, otherwise - source <var class="Ar">file</var> into the current shell.</li> - <li>If <var class="Ar">file</var> contains the - <a class="Xr">rcorder(8)</a> keyword “interactive”, then - the command is executed using - <code class="Ic">no_rc_postprocess</code>.</li> - </ol> - </dd> - <dt id="stop_boot~2"><a class="permalink" href="#stop_boot~2"><code class="Ic">stop_boot</code></a></dt> - <dd>Prevent booting to multiuser mode. If the - <a class="permalink" href="#autoboot"><b class="Sy" id="autoboot">autoboot</b></a> - variable is ‘yes’, then a - <a class="permalink" href="#SIGTERM"><b class="Sy" id="SIGTERM">SIGTERM</b></a> - signal is sent to the parent process (which is assumed to be - <a class="Xr">rc(8)</a>). Otherwise, the shell exits with status - <code class="Li">1</code>.</dd> - <dt id="twiddle~2"><a class="permalink" href="#twiddle~2"><code class="Ic">twiddle</code></a></dt> - <dd>Display one of the characters ‘/, -, \, |’, followed by a - backspace. Repeated calls to this function will create the appearance of a - spinning symbol, as a different character is displayed on each call. - Output is to <span class="Pa">/dev/tty</span>, so this function may be - useful even inside a script whose output has been redirected.</dd> - <dt id="wait_for_pids~2"><a class="permalink" href="#wait_for_pids~2"><code class="Ic">wait_for_pids</code></a> - [<var class="Ar">pid</var> [<var class="Ar">...</var>]]</dt> - <dd>Wait until all of the provided <var class="Ar">pids</var> don't exist any - more, printing the list of outstanding <var class="Ar">pids</var> every - two seconds.</dd> - <dt id="warn~2"><a class="permalink" href="#warn~2"><code class="Ic">warn</code></a> - <var class="Ar">message</var></dt> - <dd>Display a warning message to <i class="Em">stderr</i> and log it to the - system log using <a class="Xr">logger(1)</a>. The warning message consists - of the script name (from <b class="Sy">$0</b>), followed by “: - WARNING: ”, and then <var class="Ar">message</var>.</dd> - <dt id="yesno_to_truefalse~2"><a class="permalink" href="#yesno_to_truefalse~2"><code class="Ic">yesno_to_truefalse</code></a> - <var class="Ar">var</var></dt> - <dd>Change the value of the specified variable from any of the forms - acceptable to the <code class="Ic">checkyesno</code> function, to - “true” or “false”.</dd> -</dl> -</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">/etc/rc.subr</span></dt> - <dd>The <code class="Nm">rc.subr</code> file resides in - <span class="Pa">/etc</span>.</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">rc.conf(5)</a>, <a class="Xr">rc(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp"><code class="Nm">rc.subr</code> appeared in - <span class="Ux">NetBSD 1.3</span>. The <a class="Xr">rc.d(8)</a> support - functions appeared in <span class="Ux">NetBSD 1.5</span>. Support for the - <a class="Xr">rc(8)</a> post-processor appeared in <span class="Ux">NetBSD - 6.0</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">December 17, 2012</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/rescue.8 4.html b/static/netbsd/man8/rescue.8 4.html deleted file mode 100644 index f1cfdffc..00000000 --- a/static/netbsd/man8/rescue.8 4.html +++ /dev/null @@ -1,94 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">RESCUE(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">RESCUE(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">rescue</code> — <span class="Nd">rescue - utilities in <span class="Pa">/rescue</span></span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <span class="Pa">/rescue</span> directory contains a - collection of common utilities intended for use in recovering a badly - damaged system. With the transition to a dynamically-linked root beginning - with <span class="Ux">NetBSD 2.0</span>, there is a real possibility that - the standard tools in <span class="Pa">/bin</span> and - <span class="Pa">/sbin</span> may become non-functional due to a failed - upgrade or a disk error. The tools in <span class="Pa">/rescue</span> are - statically linked and should therefore be more resistant to damage. However, - being statically linked, the tools in <span class="Pa">/rescue</span> are - also less functional than the standard utilities. In particular, they do not - have full use of the locale, <a class="Xr">pam(3)</a>, and nsswitch - libraries.</p> -<p class="Pp">If your system fails to boot, and it shows an error message - similar to:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">init: not found</code></div> -<p class="Pp">try booting the system with the boot flag - “<code class="Fl">-a</code>” and supplying - <span class="Pa">/rescue/init</span>, which is the - <code class="Nm">rescue</code> <a class="Xr">init(8)</a>, as the init - path.</p> -<p class="Pp">If your system fails to boot, and it shows a prompt similar - to:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">Enter full pathname of shell or - RETURN for /bin/sh: </code></div> -<p class="Pp">the first thing to try running is the standard shell, - <span class="Pa">/bin/sh</span>. If that fails, try running - <span class="Pa">/rescue/sh</span>, which is the - <code class="Nm">rescue</code> shell. To repair the system, the root - partition must first be remounted read-write. This can be done with the - following <a class="Xr">mount(8)</a> command:</p> -<p class="Pp"></p> -<div class="Bd Bd-indent"><code class="Li">/rescue/mount -uw /</code></div> -<p class="Pp">The next step is to double-check the contents of - <span class="Pa">/bin</span>, <span class="Pa">/lib</span>, - <span class="Pa">/libexec</span>, and <span class="Pa">/sbin</span>, - possibly mounting a <span class="Ux">NetBSD</span> installation CD-ROM and - copying files from there. Once it is possible to successfully run - <span class="Pa">/bin/sh</span>, <span class="Pa">/bin/ls</span>, and other - standard utilities, try rebooting back into the standard system.</p> -<p class="Pp">The <span class="Pa">/rescue</span> tools are compiled using - <a class="Xr">crunchgen(1)</a>, which makes them considerably more compact - than the standard utilities.</p> -</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">/rescue</span></dt> - <dd>Root of the <code class="Nm">rescue</code> hierarchy.</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">crunchgen(1)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">rescue</code> utilities first appeared in - <span class="Ux">NetBSD 2.0</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp">The <code class="Nm">rescue</code> system was written by - <span class="An">Luke Mewburn</span> - <<a class="Mt" href="mailto:lukem@NetBSD.org">lukem@NetBSD.org</a>>. - This manual page was written by <span class="An">Simon L. Nielsen</span> - <<a class="Mt" href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>>, - based on text by <span class="An">Tim Kientzle</span> - <<a class="Mt" href="mailto:kientzle@FreeBSD.org">kientzle@FreeBSD.org</a>>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">April 5, 2012</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/veriexec.8 4.html b/static/netbsd/man8/veriexec.8 4.html deleted file mode 100644 index e04a0fc5..00000000 --- a/static/netbsd/man8/veriexec.8 4.html +++ /dev/null @@ -1,176 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">VERIEXEC(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">VERIEXEC(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">veriexec</code> — <span class="Nd">file - integrity subsystem</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><i class="Em">Veriexec</i> is an in-kernel, real-time, file-system - independent, file integrity subsystem. It can be used for a variety of - purposes, including defense against trojaned binaries, indirect attacks via - third-party remote file-systems, and malicious configuration file - corruption.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="CONFIGURATION"><a class="permalink" href="#CONFIGURATION">CONFIGURATION</a></h1> -<section class="Ss"> -<h2 class="Ss" id="Signatures_Database"><a class="permalink" href="#Signatures_Database">Signatures - Database</a></h2> -<p class="Pp"><i class="Em">Veriexec</i> requires a signatures database -- a - list of monitored files, along with their digital fingerprint and - (optionally) access modes. The format of this file is described by - <a class="Xr">veriexec(5)</a>.</p> -<p class="Pp"><span class="Ux">NetBSD</span> provides a tool, - <a class="Xr">veriexecgen(8)</a>, for generating the signatures database. - Example usage:</p> -<div class="Bd Pp Bd-indent Li"> -<pre># veriexecgen</pre> -</div> -<p class="Pp">Although it should be loaded on system boot (see “RC - Configuration” below), this list can be loaded manually using - <a class="Xr">veriexecctl(8)</a>:</p> -<div class="Bd Pp Bd-indent Li"> -<pre># veriexecctl load</pre> -</div> -</section> -<section class="Ss"> -<h2 class="Ss" id="Kernel_Configuration"><a class="permalink" href="#Kernel_Configuration">Kernel - Configuration</a></h2> -<p class="Pp"><i class="Em">Veriexec</i> requires a kernel with - <a class="Xr">fileassoc(9)</a> support and a pseudo-device to run:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>options FILEASSOC -pseudo-device veriexec</pre> -</div> -<p class="Pp">Additionally, one or more options for digital fingerprint - algorithm support:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>options VERIFIED_EXEC_FP_SHA256 -options VERIFIED_EXEC_FP_SHA384 -options VERIFIED_EXEC_FP_SHA512</pre> -</div> -<p class="Pp">Some kernels already enable <i class="Em">Veriexec</i> by default. - See your kernel's config file for more information.</p> -</section> -<section class="Ss"> -<h2 class="Ss" id="RC_Configuration"><a class="permalink" href="#RC_Configuration">RC - Configuration</a></h2> -<p class="Pp"><i class="Em">Veriexec</i> also allows loading signatures and - setting the strict level (see below) during the boot process using the - following variables set in <a class="Xr">rc.conf(5)</a>:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>veriexec=YES -veriexec_strict=1 # IDS mode</pre> -</div> -</section> -</section> -<section class="Sh"> -<h1 class="Sh" id="STRICT_LEVELS"><a class="permalink" href="#STRICT_LEVELS">STRICT - LEVELS</a></h1> -<p class="Pp"><i class="Em">Veriexec</i> can operate in four modes, also - referred to as strict levels:</p> -<dl class="Bl-tag"> - <dt>Learning mode (strict level 0)</dt> - <dd>The only level at which the fingerprint tables can be modified, this level - is used to help fine-tune the signature database. No enforcement is made, - and verbose information is provided (fingerprint matches and mismatches, - file removals, incorrect access, etc.).</dd> - <dt>IDS mode (strict level 1)</dt> - <dd>IDS (intrusion detection system) mode provides an adequate level of - integrity for the files it monitors. Implications: - <p class="Pp"></p> - <ul class="Bl-dash Bl-compact"> - <li>Monitored files cannot be removed</li> - <li>If raw disk access is granted to a disk with monitored files on it, - all monitored files' fingerprints will be invalidated</li> - <li>Access to files with mismatched fingerprints is denied</li> - <li>Write access to monitored files is allowed</li> - <li>Access type is not enforced</li> - </ul> - </dd> - <dt>IPS mode (strict level 2)</dt> - <dd>IPS (intrusion prevention system) mode provides a high level of integrity - for the files it monitors. Implications: - <p class="Pp"></p> - <ul class="Bl-dash Bl-compact"> - <li>All implications of IDS mode</li> - <li>Write access to monitored files is denied</li> - <li>Access type is enforced</li> - <li>Raw disk access to disk devices with monitored files on them is - denied</li> - <li>Execution of non-monitored files is denied</li> - <li>Write access to kernel memory via <span class="Pa">/dev/mem</span> and - <span class="Pa">/dev/kmem</span> is denied</li> - </ul> - </dd> - <dt>Lockdown mode (strict level 3)</dt> - <dd>Lockdown mode provides high assurance integrity for the entire system. - Implications: - <p class="Pp"></p> - <ul class="Bl-dash Bl-compact"> - <li>All implications of IPS mode</li> - <li>Access to non-monitored files is denied</li> - <li>Write access to files is allowed only if the file was opened before - the strict level was raised to this mode</li> - <li>Creation of new files is denied</li> - <li>Raw access to system disks is denied</li> - </ul> - </dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="RUNTIME_INFORMATION"><a class="permalink" href="#RUNTIME_INFORMATION">RUNTIME - INFORMATION</a></h1> -<p class="Pp"><i class="Em">Veriexec</i> exports runtime information that may be - useful for various purposes.</p> -<p class="Pp">It reports the currently supported fingerprinting algorithms, for - example:</p> -<div class="Bd Pp Bd-indent Li"> -<pre># /sbin/sysctl kern.veriexec.algorithms -kern.veriexec.algorithms = SHA256 SHA384 SHA512</pre> -</div> -<p class="Pp">It reports the current verbosity and strict levels, for - example:</p> -<div class="Bd Pp Bd-indent Li"> -<pre># /sbin/sysctl kern.veriexec.{verbose,strict} -kern.veriexec.verbose = 0 -kern.veriexec.strict = 1</pre> -</div> -<p class="Pp">It reports a summary of currently loaded files and the - mount-points they're on, for example:</p> -<div class="Bd Pp Bd-indent Li"> -<pre># /sbin/sysctl kern.veriexec.count -kern.veriexec.count.table0.mntpt = / -kern.veriexec.count.table0.fstype = ffs -kern.veriexec.count.table0.nentries = 33</pre> -</div> -<p class="Pp">Other information may be retrieved using - <a class="Xr">veriexecctl(8)</a>.</p> -</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">options(4)</a>, <a class="Xr">veriexec(5)</a>, - <a class="Xr">sysctl(7)</a>, <a class="Xr">sysctl(8)</a>, - <a class="Xr">veriexecctl(8)</a>, <a class="Xr">veriexecgen(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp"><span class="An">Elad Efrat</span> - <<a class="Mt" href="mailto:elad@NetBSD.org">elad@NetBSD.org</a>></p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">September 13, 2017</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> diff --git a/static/netbsd/man8/wizd.8 4.html b/static/netbsd/man8/wizd.8 4.html deleted file mode 100644 index 2f5e3c05..00000000 --- a/static/netbsd/man8/wizd.8 4.html +++ /dev/null @@ -1,78 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">WIZD(8)</td> - <td class="head-vol">System Manager's Manual</td> - <td class="head-rtitle">WIZD(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">wizd</code> — - <span class="Nd">automatically correct typographical errors in man - pages</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">wizd</code></td> - <td></td> - </tr> -</table> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">wizd</code> automatically checks and corrects - spelling errors, usage problems with <a class="Xr">mdoc(7)</a> macros, and - other typographical errors in man pages.</p> -<p class="Pp"><code class="Nm">wizd</code> is invoked by any - <a class="Xr">cvs(1)</a> commit to a man page.</p> -<p class="Pp"><code class="Nm">wizd</code> also performs periodic sanity checks - on the distribution set lists. E-mail alerts will be triggered if the build - installs files that are marked as obsolete and therefore get automatically - removed.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SIGNALS"><a class="permalink" href="#SIGNALS">SIGNALS</a></h1> -<p class="Pp"><code class="Nm">wizd</code> responds to the following - signals:</p> -<dl class="Bl-tag"> - <dt><<a class="Mt" href="mailto:wiz@NetBSD.org">wiz@NetBSD.org</a>></dt> - <dd>Examine a man page for errors. The man page and particular errors in - question may be specified in standard internet mail format.</dd> -</dl> -<p class="Pp"><code class="Nm">wizd</code> additionally sometimes delivers the - following signals to other committer processes:</p> -<dl class="Bl-tag"> - <dt id="SIGWIZD"><a class="permalink" href="#SIGWIZD"><code class="Dv">SIGWIZD</code></a></dt> - <dd>An error was detected in a man page.</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">cvs(1)</a>, <a class="Xr">intro(1)</a>, - <a class="Xr">man(1)</a>, <a class="Xr">mdoc(7)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp"><code class="Nm">wizd</code> appeared in <span class="Ux">NetBSD - 1.5</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1> -<p class="Pp"><code class="Nm">wizd</code> is not only copyrighted, but also - registered.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">Sleeps sometimes. Leaves laptop at home sometimes.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">March 30, 2015</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |