diff options
| author | Jacob McDonnell <jacob@jacobmcdonnell.com> | 2026-04-25 15:32:58 -0400 |
|---|---|---|
| committer | Jacob McDonnell <jacob@jacobmcdonnell.com> | 2026-04-25 15:32:58 -0400 |
| commit | 5cb84ec742fd33f78c8022863fadaa8d0d93e176 (patch) | |
| tree | 1a81ca3665e6153923e40db7b0d988f8573ab59c /static/netbsd/man8 | |
| parent | a59214f344567c037d5776879bcfc5fcc1d4d5f6 (diff) | |
feat: Added NetBSD man pages
Diffstat (limited to 'static/netbsd/man8')
109 files changed, 18954 insertions, 0 deletions
diff --git a/static/netbsd/man8/MAKEDEV.8 b/static/netbsd/man8/MAKEDEV.8 new file mode 100644 index 00000000..a34b8ccc --- /dev/null +++ b/static/netbsd/man8/MAKEDEV.8 @@ -0,0 +1,1025 @@ +.\" *** ------------------------------------------------------------------ +.\" *** This file was generated automatically +.\" *** from src/etc/MAKEDEV.tmpl and +.\" *** src/share/man/man8/MAKEDEV.8.template +.\" *** +.\" *** DO NOT EDIT - any changes will be lost!!! +.\" *** ------------------------------------------------------------------ +.\" +.\" $NetBSD: MAKEDEV.8,v 1.57 2020/04/01 15:33:50 gson Exp $ +.\" +.\" Copyright (c) 2001, 2003, 2007, 2008 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Thomas Klausner. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd April 1, 2020 +.Dt MAKEDEV 8 +.Os +.Sh NAME +.Nm MAKEDEV +.Nd create system and device special files +.Sh SYNOPSIS +.\" Please keep this in sync with MAKEDEV.local.8 +.Nm +.Op Fl fMsu +.Op Fl m Ar mknod +.Op Fl p Ar pax +.Op Fl t Ar mtree +.Bro Ar special | device Brc Op Ar ... +.Sh DESCRIPTION +.Nm +is used to create system and device special files. +As arguments it takes the names of known devices, like +.Ar sd0 , +or of special targets, like +.Pa all +or +.Pa std , +which create a collection of device special files, +or +.Pa local , +which invokes +.Xr MAKEDEV.local 8 +with the +.Pa all +argument. +.Pp +The script is in +.Pa /dev/MAKEDEV . +Devices are created in the current working directory; +in normal use, +.Nm +should be invoked with +.Pa /dev +as the current working directory. +.Pp +Supported options are: +.Bl -tag -width XmXmknodXX +.It Fl f +Force permissions to be updated on existing devices. +This works only if +.Nm +invokes +.Xr mknod 8 ; +it is not compatible with the +.Fl p , +.Fl s , +or +.Fl t +options. +.It Fl M +Create a memory file system, union mounted over the current directory, +to contain the device special files. +The memory file system is created using +.Xr mount_tmpfs 8 +or +.Xr mount_mfs 8 , +in that order of preference. +.Pp +If the +.Fl M +flag is specified more than once, then +.Nm +assumes that it is being invoked from +.Xr init 8 +to populate a memory file system for +.Pa /dev . +In this case, +.Nm +will also redirect its output to the system console. +.It Fl m Ar mknod +Force the use of +.Xr mknod 8 , +and specify the name or path to the +.Xr mknod 8 +program. +[Usually, $TOOL_MKNOD or mknod.] +.It Fl p Ar pax +Force the use of +.Xr pax 1 , +and specify the name or path to the +.Xr pax 1 +program. +[Usually, $TOOL_PAX or pax.] +.It Fl s +Generate an +.Xr mtree 8 +specfile instead of creating devices. +.It Fl t Ar mtree +Force the use of +.Xr mtree 8 , +and specify the name or path to the +.Xr mtree 8 +program. +[Usually, $TOOL_MTREE or mtree.] +.It Fl u +Don't re-create devices that already exist. +.El +.Pp +.Nm +has several possible methods of creating device nodes: +.Bl -bullet +.It +By invoking the +.Xr mknod 8 +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. +.Pp +The +.Fl m +option forces +.Nm +to use the +.Xr mknod 8 +method. +.It +By internally creating a specfile in a format usable by +.Xr mtree 8 , +and providing the specfile on standard input to a +.Xr pax 1 +or +.Xr mtree 8 +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 +.Xr mknod 8 , +because it requires much fewer processes; +however, it's not compatible with the +.Fl f +option. +.Pp +The +.Fl p +or +.Fl t +options force +.Nm +to use the +.Xr pax 1 +or +.Xr mtree 8 +methods. +.It +If the +.Fl s +option is specified, then +.Nm +will not create device nodes at all, but will output +a specfile in a format usable by +.Xr mtree 8 . +.El +.Pp +The +.Fl m , Fl p , Fl s , +and +.Fl t +flags are mutually exclusive. +If none of these flags is specified, then +.Nm +will use +.Xr mtree 8 , +.Xr pax 1 , +or +.Xr mknod 8 , +in that order of preference, depending on which commands +appear to be available and usable. +In normal use, it's expected that +.Xr mtree 8 +will be available, so it will be chosen. +If +.Nm +is invoked by +.Xr init 8 , +it's expected that +.Xr mtree 8 +will not be available, but +.Xr pax 1 +may be available. +.Pp +The special targets supported on +.Nx +are: +.Pp +.\" @@@SPECIAL@@@ +.Bl -tag -width 01234567 -compact +.It Ar all +Makes all known devices, including local devices. Tries to make the 'standard' number of each type. +.It Ar init +A set of devices that is used for MFS /dev by init. May be equal to ``all''. +.It Ar floppy +Devices to be put on install floppies +.It Ar ramdisk +Devices to be put into INSTALL kernel ramdisks. +.It Ar std +Standard devices +.It Ar local +Configuration specific devices +.It Ar lua +Lua device +.It Ar wscons +Make wscons devices +.It Ar usbs +Make USB devices +.El +.Pp +Please note that any hash marks +.Pq Dq # +in the following list of supported device targets must be replaced by +digits when calling +.Nm : +.Pp +.\" @@@DEVICES@@@ +.Bl -tag -width 01 +.It Tapes : +. Bl -tag -width 0123456789 -compact +. It Ar st# +SCSI tapes, see +.Xr \&st 4 +. It Ar wt# +QIC-interfaced (e.g. not SCSI) 3M cartridge tape, see +.Xr \&wt 4 +. It Ar ht# +MASSBUS TM03 and TU??, see +.Xr \&vax/ht 4 +. It Ar mt# +MSCP tapes (e.g. TU81, TK50), see +.Xr \&vax/mt 4 +. It Ar tm# +UNIBUS TM11 and TE10 emulations (e.g. Emulex TC-11), see +.Xr \&vax/tm 4 +. It Ar ts# +UNIBUS TS11, see +.Xr \&vax/ts 4 +. It Ar ut# +UNIBUS TU45 emulations (e.g. si 9700), see +.Xr \&vax/ut 4 +. It Ar uu# +TU58 cassettes on DL11 controller, see +.Xr \&vax/uu 4 +. El +.It Disks : +. Bl -tag -width 0123456789 -compact +. It Ar dk# +Wedge disk slices, see +.Xr \&dk 4 +. It Ar ccd# +Concatenated disk devices, see +.Xr \&ccd 4 +. It Ar cd# +SCSI or ATAPI CD-ROM, see +.Xr \&cd 4 +. It Ar cgd# +Cryptographic disk devices, see +.Xr \&cgd 4 +. It Ar raid# +RAIDframe disk devices, see +.Xr \&raid 4 +. It Ar sd# +SCSI disks, see +.Xr \&sd 4 +. It Ar wd# +``winchester'' disk drives (ST506,IDE,ESDI,RLL,...), see +.Xr \&wd 4 +. It Ar bmd# +Nereid bank memory disks, see +.Xr \&x68k/bmd 4 +. It Ar ed# +IBM PS/2 ESDI disk devices, see +.Xr \&edc 4 +. It Ar fd# +``floppy'' disk drives (3 1/2", 5 1/4"), see +.Xr \&amiga/fdc 4 , +.Xr \&sparc64/fdc 4 , +.Xr \&x86/fdc 4 +. It Ar fss# +Files system snapshot devices, see +.Xr \&fss 4 +. It Ar gdrom# +Dreamcast ``gigadisc'' CD-ROM drive, see +.Xr \&dreamcast/gdrom 4 +. It Ar hk# +UNIBUS RK06 and RK07, see +.Xr \&vax/hk 4 +. It Ar hp# +MASSBUS RM??, see +.Xr \&vax/hp 4 +. It Ar ld# +Logical disk devices (e.g., hardware RAID), see +.Xr \&ld 4 +. It Ar mcd# +Mitsumi CD-ROM, see +.Xr \&mcd 4 +. It Ar md# +Memory pseudo-disk devices, see +.Xr \&md 4 +. It Ar ofdisk# +OpenFirmware disk devices +. It Ar ra# +MSCP disks (RA??, RD??) +. It Ar rb# +730 IDC w/ RB80 and/or RB02 +. It Ar rd# +HDC9224 RD disks on VS2000, see +.Xr \&hp300/rd 4 +. It Ar rl# +UNIBUS RL02, see +.Xr \&vax/rl 4 +. It Ar rx# +MSCP floppy disk (RX33/50/...) +. It Ar up# +Other UNIBUS devices (e.g. on Emulex SC-21V controller), see +.Xr \&vax/up 4 +. It Ar vnd# +``file'' pseudo-disks, see +.Xr \&vnd 4 +. It Ar xbd# +Xen virtual disks, see +.Xr \&xbd 4 +. It Ar xd# +Xylogic 753/7053 disks, see +.Xr \&sparc/xd 4 +. It Ar xy# +Xylogic 450/451 disks, see +.Xr \&sparc/xy 4 +. El +.It Pointing devices : +. Bl -tag -width 0123456789 -compact +. It Ar wsmouse# +wscons mouse events, see +.Xr \&wsmouse 4 +. It Ar lms# +Logitech bus mouse, see +.Xr \&i386/lms 4 +. It Ar mms# +Microsoft bus mouse, see +.Xr \&dreamcast/mms 4 , +.Xr \&i386/mms 4 +. It Ar qms# +``quadrature mouse'', see +.Xr \&acorn32/qms 4 +. It Ar pms# +PS/2 mouse +. It Ar mouse +Mouse (provides events, for X11) +. El +.It Keyboard devices : +. Bl -tag -width 0123456789 -compact +. It Ar wskbd# +wscons keyboard events, see +.Xr \&wskbd 4 +. It Ar kbd +Raw keyboard (provides events, for X11), see +.Xr \&sparc/kbd 4 , +.Xr \&sun2/kbd 4 , +.Xr \&sun3/kbd 4 +. It Ar kbdctl +Keyboard control +. El +.It Terminals/Console ports : +. Bl -tag -width 0123456789 -compact +. It Ar tty[01]# +Standard serial ports, see +.Xr \&tty 4 +. It Ar tty0# +SB1250 (``sbscn'') serial ports (sbmips), see +.Xr \&tty 4 +. It Ar ttyE# +wscons - Workstation console (``wscons'') glass-tty emulators +. It Ar ttyCZ? +Cyclades-Z multiport serial boards. Each ``unit'' makes 64 ports., see +.Xr \&cz 4 +. It Ar ttyCY? +Cyclom-Y multiport serial boards. Each ``unit'' makes 32 ports., see +.Xr \&cy 4 +. It Ar ttye# +ITE bitmapped consoles, see +.Xr \&amiga/ite 4 +. It Ar ttyv0 +pccons +. It Ar ttyC? +NS16550 (``com'') serial ports +. It Ar ttyS# +SA1110 serial port (hpcarm) +. It Ar ttyTX? +TX39 internal serial ports (hpcmips) +. It Ar ttyB? +DEC 3000 ZS8530 (``scc'') serial ports (alpha) +. It Ar ttyA# +Mfc serial ports (amiga) +. It Ar ttyB# +Msc serial ports (amiga) +. It Ar ttyC# +Com style serial ports (DraCo, HyperCom) (amiga) On the DraCo, units 0 and 1 are the built-in ``modem'' and ``mouse'' ports, if configured. +. It Ar ttyA0 +8530 Channel A (formerly ser02) (atari) +. It Ar ttyA1 +8530 Channel B (formerly mdm02) (atari) +. It Ar ttyB0 +UART on first 68901 (formerly mdm01) (atari) +. It Ar ixpcom +IXP12x0 COM ports +. It Ar epcom +EP93xx COM ports +. It Ar plcom +ARM PL01[01] serial ports +. It Ar wmcom +EPOC Windermere COM ports +. It Ar ttyM? +HP200/300 4 port serial mux interface (hp300) +. It Ar ttya +``ttya'' system console (luna68k) +. It Ar ttyb +Second system serial port (luna68k) +. It Ar tty# +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 +.Xr \&tty 4 +. It Ar dc# +PMAX 4 channel serial interface (kbd, mouse, modem, printer) +. It Ar scc# +82530 serial interface (pmax) +. It Ar ttyZ# +Zilog 8530 (``zstty'') serial ports, see +.Xr \&zstty 4 +. It Ar tty[abcd] +Built-in serial ports (sparc) +. It Ar tty# +Z88530 serial controllers (sparc64), see +.Xr \&tty 4 +. It Ar ttyh# +SAB82532 serial controllers (sparc64), see +.Xr \&sparc64/sab 4 +. It Ar tty[a-j] +Built-in serial ports (sun2, sun3) +. It Ar ttyC? +pccons (arc) +. It Ar dz# +UNIBUS DZ11 and DZ32 (vax), see +.Xr \&emips/dz 4 , +.Xr \&vax/dz 4 +. It Ar dh# +UNIBUS DH11 and emulations (e.g. Able DMAX, Emulex CS-11) (vax), see +.Xr \&vax/dh 4 +. It Ar dmf# +UNIBUS DMF32 (vax), see +.Xr \&vax/dmf 4 +. It Ar dhu# +UNIBUS DHU11 (vax), see +.Xr \&vax/dhu 4 +. It Ar dmz# +UNIBUS DMZ32 (vax), see +.Xr \&vax/dmz 4 +. It Ar dl# +UNIBUS DL11 (vax), see +.Xr \&vax/dl 4 +. It Ar xencons +Xen virtual console +. El +.It Terminal multiplexors : +. Bl -tag -width 0123456789 -compact +. It Ar dc# +4 channel serial interface (keyboard, mouse, modem, printer) +. It Ar dh# +UNIBUS DH11 and emulations (e.g. Able DMAX, Emulex CS-11), see +.Xr \&vax/dh 4 +. It Ar dhu# +UNIBUS DHU11, see +.Xr \&vax/dhu 4 +. It Ar dl# +UNIBUS DL11, see +.Xr \&vax/dl 4 +. It Ar dmf# +UNIBUS DMF32, see +.Xr \&vax/dmf 4 +. It Ar dmz# +UNIBUS DMZ32, see +.Xr \&vax/dmz 4 +. It Ar dz# +UNIBUS DZ11 and DZ32, see +.Xr \&emips/dz 4 , +.Xr \&vax/dz 4 +. It Ar scc# +82530 serial interface +. El +.It Call units : +. Bl -tag -width 0123456789 -compact +. It Ar dn# +UNIBUS DN11 and emulations (e.g. Able Quadracall), see +.Xr \&vax/dn 4 +. El +.It Pseudo terminals : +. Bl -tag -width 0123456789 -compact +. It Ar ptm +Pty multiplexor device, and pts directory, see +.Xr \&ptm 4 +. It Ar pty# +Set of 16 master and slave pseudo terminals, see +.Xr \&pty 4 +. It Ar opty +First 16 ptys, to save inodes on install media +. It Ar ipty +First 2 ptys, for install media use only +. El +.It Printers : +. Bl -tag -width 0123456789 -compact +. It Ar arcpp# +Archimedes parallel port +. It Ar lpt# +Stock lp, see +.Xr \&lpt 4 , +.Xr \&acorn32/lpt 4 , +.Xr \&mvme68k/lpt 4 , +.Xr \&x86/lpt 4 +. It Ar lpa# +Interruptless lp +. It Ar par# +Amiga motherboard parallel port +. It Ar cpi# +Macintosh Nubus CSI parallel printer card, see +.Xr \&mac68k/cpi 4 +. El +.It USB devices : +. Bl -tag -width 0123456789 -compact +. It Ar usb# +USB control devices, see +.Xr \&usb 4 +. It Ar uhid# +USB generic HID devices, see +.Xr \&uhid 4 +. It Ar ulpt# +USB printer devices, see +.Xr \&ulpt 4 +. It Ar ugen# +USB generic devices, see +.Xr \&ugen 4 +. It Ar uscanner# +USB scanners, see +.Xr \&uscanner 4 +. It Ar ttyHS# +USB Option N.V. modems +. It Ar ttyU# +USB modems, see +.Xr \&ucom 4 +. It Ar ttyY# +USB serial adapters +. El +.It Video devices : +. Bl -tag -width 0123456789 -compact +. It Ar bwtwo# +Monochromatic frame buffer, see +.Xr \&sparc/bwtwo 4 , +.Xr \&sun2/bwtwo 4 , +.Xr \&sun3/bwtwo 4 +. It Ar cgtwo# +8-bit color frame buffer, see +.Xr \&sparc/cgtwo 4 , +.Xr \&sun3/cgtwo 4 +. It Ar cgthree# +8-bit color frame buffer, see +.Xr \&sparc/cgthree 4 +. It Ar cgfour# +8-bit color frame buffer, see +.Xr \&sparc/cgfour 4 , +.Xr \&sun3/cgfour 4 +. It Ar cgsix# +Accelerated 8-bit color frame buffer, see +.Xr \&sparc/cgsix 4 +. It Ar cgeight# +24-bit color frame buffer, see +.Xr \&sparc/cgeight 4 +. It Ar etvme +Tseng et-compatible cards on VME (atari) +. It Ar ik# +UNIBUS interface to Ikonas frame buffer, see +.Xr \&vax/ik 4 +. It Ar leo +Circad Leonardo VME-bus true color (atari) +. It Ar ps# +UNIBUS interface to Picture System 2, see +.Xr \&vax/ps 4 +. It Ar qv# +QVSS (MicroVAX) display +. It Ar tcx# +Accelerated 8/24-bit color frame buffer, see +.Xr \&sparc/tcx 4 +. El +.It Maple bus devices : +. Bl -tag -width 0123456789 -compact +. It Ar maple +Maple bus control devices, see +.Xr \&dreamcast/maple 4 +. It Ar mlcd# +Maple bus LCD devices, see +.Xr \&dreamcast/mlcd 4 +. It Ar mmem# +Maple bus storage devices, see +.Xr \&dreamcast/mmem 4 +. El +.It IEEE1394 bus devices : +. Bl -tag -width 0123456789 -compact +. It Ar fw# +IEEE1394 bus generic node access devices +. It Ar fwmem# +IEEE1394 bus physical memory of the remote node access devices +. El +.It Special purpose devices : +. Bl -tag -width 0123456789 -compact +. It Ar ad# +UNIBUS interface to Data Translation A/D converter, see +.Xr \&vax/ad 4 +. It Ar agp# +AGP GART devices, see +.Xr \&agp 4 +. It Ar altq +ALTQ control interface, see +.Xr \&altq 4 +. It Ar amr# +AMI MegaRaid control device, see +.Xr \&amr 4 +. It Ar apm +Power management device, see +.Xr \&i386/apm 4 +. It Ar audio# +Audio devices, see +.Xr \&audio 4 +. It Ar bell# +OPM bell device (x68k) +. It Ar bktr +Brooktree 848/849/878/879 based TV cards, see +.Xr \&bktr 4 +. It Ar bpf +Packet filter, see +.Xr \&bpf 4 +. It Ar bthub +Bluetooth Device Hub control interface, see +.Xr \&bthub 4 +. It Ar cfs# +Coda file system device +. It Ar ch# +SCSI media changer, see +.Xr \&ch 4 +. It Ar cir# +Consumer IR, see +.Xr \&cir 4 +. It Ar clockctl +Clock control for non root users, see +.Xr \&clockctl 4 +. It Ar cpuctl +CPU control +. It Ar crypto +Hardware crypto access driver, see +.Xr \&crypto 4 +. It Ar dmoverio +Hardware-assisted data movers, see +.Xr \&dmoverio 4 +. It Ar dpt# +DPT/Adaptec EATA RAID management interface, see +.Xr \&dpt 4 +. It Ar dpti# +DPT/Adaptec I2O RAID management interface, see +.Xr \&dpti 4 +. It Ar drm# +Direct Rendering Manager interface, see +.Xr \&drm 4 +. It Ar dtv# +Digital TV interface, see +.Xr \&dtv 4 +. It Ar fb# +PMAX generic framebuffer pseudo-device +. It Ar fd +File descriptors +. It Ar gpiopps# +1PPS signals on GPIO pins, see +.Xr \&gpiopps 4 +. It Ar grf# +Graphics frame buffer device, see +.Xr \&amiga/grf 4 +. It Ar hdaudio# +High Definition audio control device, see +.Xr \&hdaudio 4 +. It Ar hdmicec# +HDMI CEC devices +. It Ar hil +HP300 HIL input devices, see +.Xr \&hil 4 +. It Ar icp +ICP-Vortex/Intel RAID control interface, see +.Xr \&icp 4 +. It Ar iic# +IIC bus device, see +.Xr \&iic 4 +. It Ar io +X86 IOPL access for COMPAT_10, COMPAT_FREEBSD, see +.Xr \&hppa/io 4 , +.Xr \&i386/io 4 +. It Ar iop# +I2O IOP control interface, see +.Xr \&iop 4 +. It Ar ipmi# +OpenIPMI compatible interface, see +.Xr \&ipmi 4 +. It Ar ipl +IP Filter +. It Ar irframe# +IrDA physical frame, see +.Xr \&irframe 4 +. It Ar ite# +Terminal emulator interface to HP300 graphics devices, see +.Xr \&amiga/ite 4 +. It Ar joy# +Joystick device, see +.Xr \&joy 4 +. It Ar kttcp +Kernel ttcp helper device, see +.Xr \&kttcp 4 +. It Ar lockstat +Kernel locking statistics +. It Ar magma# +Magma multiport serial/parallel cards, see +.Xr \&sparc/magma 4 +. It Ar midi# +MIDI, see +.Xr \&midi 4 +. It Ar mfi# +LSI MegaRAID/MegaSAS control interface, see +.Xr \&mfi 4 +. It Ar mlx# +Mylex DAC960 control interface, see +.Xr \&mlx 4 +. It Ar mly# +Mylex AcceleRAID/eXtremeRAID control interface, see +.Xr \&mly 4 +. It Ar np# +UNIBUS Ethernet co-processor interface, for downloading., see +.Xr \&vax/np 4 +. It Ar npf +NPF packet filter +. It Ar nsmb# +SMB requester, see +.Xr \&nsmb 4 +. It Ar nvme# +Non-Volatile Memory Host Controller Interface device driver, see +.Xr \&nvme 4 +. It Ar nvme#ns* +Non-Volatile Memory namespace +. It Ar nvmm +NetBSD Virtual Machine Monitor, see +.Xr \&nvmm 4 +. It Ar openfirm +OpenFirmware accessor +. It Ar pad# +Pseudo-audio device driver, see +.Xr \&pad 4 +. It Ar pci# +PCI bus access devices, see +.Xr \&pci 4 +. It Ar pf +PF packet filter +. It Ar putter +Pass-to-Userspace Transporter +. It Ar px# +PixelStamp Xserver access, see +.Xr \&px 4 +. It Ar qemufwcfg# +QEMU Firmware Configuration, see +.Xr \&qemufwcfg 4 +. It Ar radio# +Radio devices, see +.Xr \&radio 4 +. It Ar random +Random number generator, see +.Xr \&rnd 4 +. It Ar rtc# +RealTimeClock, see +.Xr \&atari/rtc 4 , +.Xr \&evbppc/rtc 4 , +.Xr \&hp300/rtc 4 +. It Ar scsibus# +SCSI busses, see +.Xr \&scsi 4 +. It Ar se# +SCSI Ethernet, see +.Xr \&se 4 +. It Ar ses# +SES/SAF-TE SCSI Devices, see +.Xr \&ses 4 +. It Ar speaker +PC speaker, see +.Xr \&speaker 4 +. It Ar spi# +SPI bus device, see +.Xr \&spi 4 +. It Ar sram +Battery backuped memory (x68k) +. It Ar srt# +Source-address based routing, see +.Xr \&srt 4 +. It Ar ss# +SCSI scanner, see +.Xr \&ss 4 +. It Ar stic# +PixelStamp interface chip +. It Ar sysmon +System Monitoring hardware, see +.Xr \&envsys 4 +. It Ar tap# +Virtual Ethernet device, see +.Xr \&tap 4 +. It Ar tprof +Task profiler, see +.Xr \&tprof 4 +. It Ar tun# +Network tunnel driver, see +.Xr \&tun 4 +. It Ar twa +3ware Apache control interface, see +.Xr \&twa 4 +. It Ar twe +3ware Escalade control interface, see +.Xr \&twe 4 +. It Ar uk# +Unknown SCSI device, see +.Xr \&uk 4 +. It Ar veriexec +Veriexec fingerprint loader, see +.Xr \&veriexec 4 +. It Ar vhci +Virtual host controller interface +. It Ar video# +Video capture devices, see +.Xr \&video 4 +. It Ar view# +Generic interface to graphic displays (Amiga) +. It Ar wsfont# +Console font control, see +.Xr \&wsfont 4 +. It Ar wsmux# +wscons event multiplexor, see +.Xr \&wsmux 4 +. It Ar xenevt +Xen event interface +. El +.It iSCSI communication devices +. Bl -tag -width 0123456789 -compact +. It Ar iscsi# +ISCSI driver and /sbin/iscsid communication +. El +.It Trusted Computing devices +. Bl -tag -width 0123456789 -compact +. It Ar tpm +Trusted Platform Module, see +.Xr \&tpm 4 +. El +.It Debugging and tracing +. Bl -tag -width 0123456789 -compact +. It Ar dtrace +Dynamic tracing framework +. El +.El +.Sh ENVIRONMENT +The following environment variables affect the execution of +.Nm : +.Pp +.Bl -tag -width indent +.It Ev MAKEDEV_AS_LIBRARY +If this is set, then +.Nm +will define several shell functions and then return, +ignoring all its command line options and arguments. +This is used to enable +.Xr MAKEDEV.local 8 +to use the shell functions defined in +.Nm . +.El +.Sh FILES +.Bl -tag -width "/dev/MAKEDEV.local" -compact +.It Pa /dev +special device files directory +.It Pa /dev/MAKEDEV +script described in this man page +.It Pa /dev/MAKEDEV.local +script for site-specific devices +.El +.Sh DIAGNOSTICS +If the script reports an error that is difficult to understand, +you can get more debugging output by using +.Dl Ic sh Fl x Ar MAKEDEV Ar argument . +.Sh SEE ALSO +.Xr config 1 , +.Xr pax 1 , +.Xr intro 4 , +.Xr diskless 8 , +.Xr init 8 , +.Xr MAKEDEV.local 8 , +.Xr mknod 8 , +.Xr mount_mfs 8 , +.Xr mount_tmpfs 8 , +.Xr mtree 8 +.Sh HISTORY +The +.Nm +command appeared in +.Bx 4.2 . +The +.Fl f , +.Fl m , +and +.Fl s +options were added in +.Nx 2.0 . +The +.Fl p , +.Fl t , +and +.Fl M +options were added in +.Nx 5.0 . +The ability to be used as a function library was added in +.Nx 5.0 . +.Sh BUGS +The +.Fl f +option is not compatible with the use of +.Xr mtree 8 +or +.Xr pax 1 . +.Sh NOTES +Not all devices listed in this manpage are supported on all platforms. +.Pp +This man page is generated automatically from the same sources +as +.Pa /dev/MAKEDEV , +in which the device files are not always sorted, which may result +in an unusual (non-alphabetical) order. +.Pp +In order to allow a diskless +.Nx +client to obtain its +.Pa /dev +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: +.Bl -bullet +.It +If the foreign server is sufficiently similar to +.Nx , +run +.Nm +in an appropriate directory of the foreign server, +using the +.Fl m +flag to refer to a script that converts from command line +arguments that would be usable with the +.Nx +.Xr mknod 8 +command to the equivalent commands for the foreign server. +.It +Run +.Nm +with the +.Fl s +flag to generate an +.Xr mtree 8 +specification file; this can be done on any host with a +POSIX-compliant shell and a few widely-available utilities. +Use the +.Xr pax 1 +command with the +.Fl w Fl M +flags to convert the +.Xr mtree 8 +specification file into an archive +in a format that supports device nodes +(such as +.Ar ustar +format); +this can be done on a +.Nx +host, or can be done in a cross-build environment using +.Sy TOOLDIR Ns Pa /bin/nbpax . +Finally, use appropriate tools on the foreign server +to unpack the archive and create the device nodes. +.El diff --git a/static/netbsd/man8/MAKEDEV.8.template b/static/netbsd/man8/MAKEDEV.8.template new file mode 100644 index 00000000..6d93a20f --- /dev/null +++ b/static/netbsd/man8/MAKEDEV.8.template @@ -0,0 +1,351 @@ +.\" $NetBSD: MAKEDEV.8.template,v 1.21 2017/02/13 19:49:06 abhinav Exp $ +.\" +.\" Copyright (c) 2001, 2003, 2007, 2008 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Thomas Klausner. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd @@@DATE@@@ +.Dt MAKEDEV 8 +.Os +.Sh NAME +.Nm MAKEDEV +.Nd create system and device special files +.Sh SYNOPSIS +.\" Please keep this in sync with MAKEDEV.local.8 +.Nm +.Op Fl fMsu +.Op Fl m Ar mknod +.Op Fl p Ar pax +.Op Fl t Ar mtree +.Bro Ar special | device Brc Op Ar ... +.Sh DESCRIPTION +.Nm +is used to create system and device special files. +As arguments it takes the names of known devices, like +.Ar sd0 , +or of special targets, like +.Pa all +or +.Pa std , +which create a collection of device special files, +or +.Pa local , +which invokes +.Xr MAKEDEV.local 8 +with the +.Pa all +argument. +.Pp +The script is in +.Pa /dev/MAKEDEV . +Devices are created in the current working directory; +in normal use, +.Nm +should be invoked with +.Pa /dev +as the current working directory. +.Pp +Supported options are: +.Bl -tag -width XmXmknodXX +.It Fl f +Force permissions to be updated on existing devices. +This works only if +.Nm +invokes +.Xr mknod 8 ; +it is not compatible with the +.Fl p , +.Fl s , +or +.Fl t +options. +.It Fl M +Create a memory file system, union mounted over the current directory, +to contain the device special files. +The memory file system is created using +.Xr mount_tmpfs 8 +or +.Xr mount_mfs 8 , +in that order of preference. +.Pp +If the +.Fl M +flag is specified more than once, then +.Nm +assumes that it is being invoked from +.Xr init 8 +to populate a memory file system for +.Pa /dev . +In this case, +.Nm +will also redirect its output to the system console. +.It Fl m Ar mknod +Force the use of +.Xr mknod 8 , +and specify the name or path to the +.Xr mknod 8 +program. +[Usually, $TOOL_MKNOD or mknod.] +.It Fl p Ar pax +Force the use of +.Xr pax 1 , +and specify the name or path to the +.Xr pax 1 +program. +[Usually, $TOOL_PAX or pax.] +.It Fl s +Generate an +.Xr mtree 8 +specfile instead of creating devices. +.It Fl t Ar mtree +Force the use of +.Xr mtree 8 , +and specify the name or path to the +.Xr mtree 8 +program. +[Usually, $TOOL_MTREE or mtree.] +.It Fl u +Don't re-create devices that already exist. +.El +.Pp +.Nm +has several possible methods of creating device nodes: +.Bl -bullet +.It +By invoking the +.Xr mknod 8 +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. +.Pp +The +.Fl m +option forces +.Nm +to use the +.Xr mknod 8 +method. +.It +By internally creating a specfile in a format usable by +.Xr mtree 8 , +and providing the specfile on standard input to a +.Xr pax 1 +or +.Xr mtree 8 +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 +.Xr mknod 8 , +because it requires much fewer processes; +however, it's not compatible with the +.Fl f +option. +.Pp +The +.Fl p +or +.Fl t +options force +.Nm +to use the +.Xr pax 1 +or +.Xr mtree 8 +methods. +.It +If the +.Fl s +option is specified, then +.Nm +will not create device nodes at all, but will output +a specfile in a format usable by +.Xr mtree 8 . +.El +.Pp +The +.Fl m , Fl p , Fl s , +and +.Fl t +flags are mutually exclusive. +If none of these flags is specified, then +.Nm +will use +.Xr mtree 8 , +.Xr pax 1 , +or +.Xr mknod 8 , +in that order of preference, depending on which commands +appear to be available and usable. +In normal use, it's expected that +.Xr mtree 8 +will be available, so it will be chosen. +If +.Nm +is invoked by +.Xr init 8 , +it's expected that +.Xr mtree 8 +will not be available, but +.Xr pax 1 +may be available. +.Pp +The special targets supported on +.Nx +are: +.Pp +@@@SPECIAL@@@ +.Pp +Please note that any hash marks +.Pq Dq # +in the following list of supported device targets must be replaced by +digits when calling +.Nm : +.Pp +@@@DEVICES@@@ +.Sh ENVIRONMENT +The following environment variables affect the execution of +.Nm : +.Pp +.Bl -tag -width indent +.It Ev MAKEDEV_AS_LIBRARY +If this is set, then +.Nm +will define several shell functions and then return, +ignoring all its command line options and arguments. +This is used to enable +.Xr MAKEDEV.local 8 +to use the shell functions defined in +.Nm . +.El +.Sh FILES +.Bl -tag -width "/dev/MAKEDEV.local" -compact +.It Pa /dev +special device files directory +.It Pa /dev/MAKEDEV +script described in this man page +.It Pa /dev/MAKEDEV.local +script for site-specific devices +.El +.Sh DIAGNOSTICS +If the script reports an error that is difficult to understand, +you can get more debugging output by using +.Dl Ic sh Fl x Ar MAKEDEV Ar argument . +.Sh SEE ALSO +.Xr config 1 , +.Xr pax 1 , +.Xr intro 4 , +.Xr diskless 8 , +.Xr init 8 , +.Xr MAKEDEV.local 8 , +.Xr mknod 8 , +.Xr mount_mfs 8 , +.Xr mount_tmpfs 8 , +.Xr mtree 8 +.Sh HISTORY +The +.Nm +command appeared in +.Bx 4.2 . +The +.Fl f , +.Fl m , +and +.Fl s +options were added in +.Nx 2.0 . +The +.Fl p , +.Fl t , +and +.Fl M +options were added in +.Nx 5.0 . +The ability to be used as a function library was added in +.Nx 5.0 . +.Sh BUGS +The +.Fl f +option is not compatible with the use of +.Xr mtree 8 +or +.Xr pax 1 . +.Sh NOTES +Not all devices listed in this manpage are supported on all platforms. +.Pp +This man page is generated automatically from the same sources +as +.Pa /dev/MAKEDEV , +in which the device files are not always sorted, which may result +in an unusual (non-alphabetical) order. +.Pp +In order to allow a diskless +.Nx +client to obtain its +.Pa /dev +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: +.Bl -bullet +.It +If the foreign server is sufficiently similar to +.Nx , +run +.Nm +in an appropriate directory of the foreign server, +using the +.Fl m +flag to refer to a script that converts from command line +arguments that would be usable with the +.Nx +.Xr mknod 8 +command to the equivalent commands for the foreign server. +.It +Run +.Nm +with the +.Fl s +flag to generate an +.Xr mtree 8 +specification file; this can be done on any host with a +POSIX-compliant shell and a few widely-available utilities. +Use the +.Xr pax 1 +command with the +.Fl w Fl M +flags to convert the +.Xr mtree 8 +specification file into an archive +in a format that supports device nodes +(such as +.Ar ustar +format); +this can be done on a +.Nx +host, or can be done in a cross-build environment using +.Sy TOOLDIR Ns Pa /bin/nbpax . +Finally, use appropriate tools on the foreign server +to unpack the archive and create the device nodes. +.El diff --git a/static/netbsd/man8/MAKEDEV.local.8 b/static/netbsd/man8/MAKEDEV.local.8 new file mode 100644 index 00000000..43b9e305 --- /dev/null +++ b/static/netbsd/man8/MAKEDEV.local.8 @@ -0,0 +1,130 @@ +.\" $NetBSD: MAKEDEV.local.8,v 1.8 2011/08/06 12:32:29 jmcneill Exp $ +.\" +.\" Copyright (c) 2007 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd August 6, 2011 +.Dt MAKEDEV.LOCAL 8 +.Os +.Sh NAME +.Nm MAKEDEV.local +.Nd create site-specific device special files +.Sh SYNOPSIS +.Nm +.Op Fl fMsu +.Op Fl m Ar mknod +.Op Fl p Ar pax +.Op Fl t Ar mtree +.Bro Pa all | site-specific-argument Brc Op Ar ... +.Sh DESCRIPTION +.Nm +is used to create site-specific device special files. +Each argument may be the word +.Pa all +or a site-specific argument. +By default, there are no valid site-specific arguments, +and the +.Pa all +argument has no effect; +This may be changed by editing the script. +.Pp +The script is in +.Pa /dev/MAKEDEV.local . +Devices are created in the current working directory; +in normal use, +.Nm +should be invoked with +.Pa /dev +as the current working directory. +.Pp +Supported options for +.Nm +are the same as for +.Xr MAKEDEV 8 . +.Sh FILES +.Bl -tag -width "/dev/MAKEDEV.local" -compact +.It Pa /dev +special device files directory +.It Pa /dev/MAKEDEV +script that invokes +.Nm +with the +.Pa all +argument. +.It Pa /dev/MAKEDEV.local +script described in this man page +.El +.Sh SEE ALSO +.Xr config 1 , +.Xr intro 4 , +.Xr MAKEDEV 8 , +.Xr mknod 8 +.Sh HISTORY +The +.Nm +command appeared in +.Bx 4.2 . +Handling of the same command line options as +.Xr MAKEDEV 8 , +and the use of +.Xr MAKEDEV 8 +as a function library, was added in +.Nx 5.0 . +.Sh NOTES +The relationship between +.Nm +and +.Xr MAKEDEV 8 +is complex: +.Bl -bullet +.It +If +.Xr MAKEDEV 8 +is invoked with the +.Pa all +or +.Pa local +argument, then it will invoke +.Nm +as a child process, with options similar to +those that were originally passed to +.Xr MAKEDEV 8 , +and with the +.Pa all +argument. +.It +.Nm +uses shell functions defined in +.Xr MAKEDEV 8 . +This is done by loading +.Xr MAKEDEV 8 +using the shell +.Dq \&. +command, with the +.Ev MAKEDEV_AS_LIBRARY +variable set (to inform +.Xr MAKEDEV 8 +that it should behave as a function library, +not as an independent program). +.El diff --git a/static/netbsd/man8/MAKEDEV2manpage.awk b/static/netbsd/man8/MAKEDEV2manpage.awk new file mode 100644 index 00000000..76dc0c97 --- /dev/null +++ b/static/netbsd/man8/MAKEDEV2manpage.awk @@ -0,0 +1,231 @@ +# $NetBSD: MAKEDEV2manpage.awk,v 1.13 2010/03/23 19:19:03 jakllsch Exp $ +# +# Copyright (c) 2002 +# Dieter Baron <dillo@NetBSD.org>. All rights reserved. +# Copyright (c) 1999 +# Hubert Feyrer <hubertf@NetBSD.org>. All rights reserved. +# [converted from Hubert's Perl version] +# +# Redistribution and use in source and binary forms, with or without +# modification, are permitted provided that the following conditions +# are met: +# 1. Redistributions of source code must retain the above copyright +# notice, this list of conditions and the following disclaimer. +# 2. Redistributions in binary form must reproduce the above copyright +# notice, this list of conditions and the following disclaimer in the +# documentation and/or other materials provided with the distribution. +# 3. All advertising materials mentioning features or use of this software +# must display the following acknowledgement: +# This product includes software developed by Hubert Feyrer for +# the NetBSD Project. +# 4. Neither the name of the University nor the names of its contributors +# may be used to endorse or promote products derived from this software +# without specific prior written permission. +# +# THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +# ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. +# +# +########################################################################### +# +# Convert src/etc/MAKEDEV.tmpl and +# src/share/man/man8/MAKEDEV.8.template to +# src/share/man/man8/MAKEDEV.8, replacing +# - @@@SPECIAL@@@ with all targets in the first section (all, std, ...) +# - @@@DEVICES@@@ with the remaining targets +# - @@@ARCH@@@ with the architecture name +# + +# XXX: uses non-standard AWK function toupper() + +BEGIN { + MAKEDEV = "../../../etc/MAKEDEV.tmpl"; + print ".\\\" *** ------------------------------------------------------------------"; + print ".\\\" *** This file was generated automatically"; + print ".\\\" *** from src/etc/MAKEDEV.tmpl and"; + print ".\\\" *** src/share/man/man8/MAKEDEV.8.template"; + print ".\\\" ***"; + print ".\\\" *** DO NOT EDIT - any changes will be lost!!!"; + print ".\\\" *** ------------------------------------------------------------------"; + print ".\\\""; +} + +function read1line() { + if (r1kept) + r1l = r1last; + else + getline r1l < MAKEDEV; + + while (r1l ~ /^#[ \t]*$/) + getline r1l < MAKEDEV; + + if (r1l ~ /^#[ \t]/) { + if (r1l ~ /^# /) { + # Not a device/other target + r1kept = 0; + } + else { + # Continuation line (?) + getline r1ll < MAKEDEV; + while (r1ll ~ /^#\t[ \t]/) { + sub(/^#\t[ \t]/, " ", r1ll); + r1l = r1l r1ll; + getline r1ll < MAKEDEV; + } + r1last = r1ll; + r1kept = 1; + } + } + else + r1kept = 0; + + return 1; +} + +/^@@@SPECIAL@@@$/ { + print ".\\\" " $0; + print ".Bl -tag -width 01234567 -compact"; + + while (getline l < MAKEDEV > 0 && l !~ /^#.*Device.*Valid.*argument/) + ; + while (read1line() && r1l ~ /^#\t/) { + sub(/#[ \t]*/, "", r1l); + target=r1l; + sub(/[ \t].*/, "", target); + line=r1l; + sub(/[^ \t]*[ \t]/, "", line); + # replace "foo" with ``foo'' + gsub(/\"[^\"]*\"/, "``&''", line) + gsub(/\"/, "", line) + gsub(/[ \t]+/, " ", line); + print ".It Ar " target; + print toupper(substr(line, 1, 1)) substr(line, 2); + + } + r1last = r1l; + r1kept = 1; + print ".El"; + next; +} +/^@@@DEVICES@@@$/ { + print ".\\\" " $0; + print ".Bl -tag -width 01"; + + read1line(); + do { + sub(/^#[ \t]+/, "", r1l); + if (r1l ~ /[^ \t]:$/) + sub(/:$/, " :", r1l); + print ".It " r1l; # print section heading + + print ". Bl -tag -width 0123456789 -compact"; + while(read1line() && r1l ~ /^#\t/) { + gsub(/#[ \t]+/, "", r1l); + target=r1l; + sub(/[ \t].*/, "", target); + line=r1l; + sub(/[^ \t]*[ \t]+/, "", line); + sub(/\*/, "#", target); + # replace "foo" with ``foo'' + gsub(/\"[^\"]*\"/, "``&''", line) + gsub(/\"/, "", line) + # fix collateral damage of previous + sub(/5 1\/4''/, "5 1/4\"", line) + sub(/3 1\/2``/, "3 1/2\"", line) + # gc whitespace + sub(/\(XXX[^)]*\)/, "", line); + sub(/[ \t]*$/, "", line); + + # add manpage, if available + if (target == "fd#") + page = "fdc" + else if (target == "pms#") + page = "opms" + else if (target == "ed#") + page = "edc" + else if (target == "ttye#") + page = "ite" + else if (target == "ttyh#") + page = "sab" + else if (target == "ttyU#") + page = "ucom" + else if (target == "fd") + page = "-----" # force no .Xr + else if (target == "sysmon") + page = "envsys" + else if (target == "ttyZ#") + page = "zstty" + else if (target == "ttyCZ?") + page = "cz" + else if (target == "ttyCY?") + page = "cy" + else if (target == "ttyB?") + page = "scc" + else if (target == "random") + page = "rnd" + else if (target == "scsibus#") + page = "scsi" + else { + page=target; + sub(/[^a-zA-Z]+/, "", page); + } + + str = "ls ../man4/" page ".4 ../man4/man4.*/" page ".4 2>/dev/null" + while(str | getline) { + if (system("test -f " $0) != 0) + continue + + # get the manpage including opt. arch name + sub(/^\.\.\/man4\//, "") + sub(/^man4\./, "") + sub(/\.4$/, "") + + sub(/[ \t]*$/, "", line); + if (line ~ /see/) { + # already a manpage there, e.g. scsictl(8) + line = line " ,"; + } + else + line = line ", see"; + # Add .Xr \&foo 4 - ampersand to work around + # manpages that are *roff commands at the same + # time + line = line "\n.Xr \\&" $0 " 4"; + } + close(str) + + gsub(/[ \t]+$/, "", line); + gsub(/[ \t]+/, " ", line); + + print ". It Ar " target; + line2=toupper(substr(line, 1, 1)) substr(line, 2); + sub(/Wscons/, "wscons", line2); + sub(/Pccons/, "pccons", line2); + print line2; + } + print MANPAGE ". El"; + } while (r1l ~ /^# /); + + print ".El"; + next; +} +/@@@ARCH@@@/ { + gsub(/@@@ARCH@@@/, ARCH); +} +# date is substituted in the shell script +#/@@@DATE@@@/ { +# # date +#} +/\$NetBSD/ { + sub(/\$NetBSD.*\$/, "$""NetBSD$"); +} +{ print } diff --git a/static/netbsd/man8/MAKEDEV2manpage.sh b/static/netbsd/man8/MAKEDEV2manpage.sh new file mode 100644 index 00000000..630e8eab --- /dev/null +++ b/static/netbsd/man8/MAKEDEV2manpage.sh @@ -0,0 +1,69 @@ +#!/bin/sh +# +# $NetBSD: MAKEDEV2manpage.sh,v 1.5 2005/12/28 03:54:07 dbj Exp $ +# +# Copyright (c) 2002 +# Dieter Baron <dillo@NetBSD.org>. All rights reserved. +# +# Redistribution and use in source and binary forms, with or without +# modification, are permitted provided that the following conditions +# are met: +# 1. Redistributions of source code must retain the above copyright +# notice, this list of conditions and the following disclaimer. +# 2. Redistributions in binary form must reproduce the above copyright +# notice, this list of conditions and the following disclaimer in the +# documentation and/or other materials provided with the distribution. +# 3. Neither the name of the University nor the names of its contributors +# may be used to endorse or promote products derived from this software +# without specific prior written permission. +# +# THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +# ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. +# +# +########################################################################### +# +# Convert src/etc/etc.${ARCH}/MAKEDEV and +# src/share/man/man8/MAKEDEV.8.template to +# src/share/man/man8/man8.${ARCH}/MAKEDEV.8, replacing +# - @@@SPECIAL@@@ with all targets in the first section (all, std, ...) +# - @@@DEVICES@@@ with the remaining targets +# - @@@DATE@@@ with the date from the previous version, if found +# - @@@ARCH@@@ with the architecture name +# using src/share/man/man8/MAKEDEV2manpage.awk +# + +AWK=${AWK:-awk} +DIFF=${DIFF:-diff} + +manpage="MAKEDEV.8"; +tmpfile="${manpage}.$$"; + +${AWK} -f MAKEDEV2manpage.awk MAKEDEV.8.template \ + > ${tmpfile} || { rm ${tmpfile}; exit 1; } +if ${DIFF} -I'^\.Dd ' -I'^\.\\" $NetBSD' -q ${manpage} ${tmpfile} \ + >/dev/null +then + result='unchanged'; + rm ${tmpfile}; +else + result='updated'; + if [ `wc -l < ${tmpfile}` -ne `wc -l < ${manpage}` ]; then + LC_ALL=C LC_CTYPE=C date=`date +"%B %e, %Y"` + else + date=`sed -n 's/^\.Dd //p' ${manpage}` + fi + sed "s/@@@DATE@@@/$date/" ${tmpfile} > ${tmpfile}.2 + rm ${tmpfile} + mv ${tmpfile}.2 ${manpage} +fi +echo "$manpage: ${result}" diff --git a/static/netbsd/man8/Makefile b/static/netbsd/man8/Makefile new file mode 100644 index 00000000..974dbe8e --- /dev/null +++ b/static/netbsd/man8/Makefile @@ -0,0 +1,33 @@ +MAN = $(wildcard *.8) + +SUBDIRS = man8.acorn32 \ + man8.alpha \ + man8.amiga \ + man8.atari \ + man8.cobalt \ + man8.dreamcast \ + man8.emips \ + man8.evbarm \ + man8.hp300 \ + man8.hpcarm \ + man8.hpcmips \ + man8.hpcsh \ + man8.hppa \ + man8.mac68k \ + man8.macppc \ + man8.mvme68k \ + man8.next68k \ + man8.pmax \ + man8.prep \ + man8.sandpoint \ + man8.sgimips \ + man8.sparc \ + man8.sparc64 \ + man8.sun2 \ + man8.sun3 \ + man8.vax \ + man8.x68k \ + man8.x86 + +include ../../mandoc.mk + diff --git a/static/netbsd/man8/afterboot.8 b/static/netbsd/man8/afterboot.8 new file mode 100644 index 00000000..b6bdb2d2 --- /dev/null +++ b/static/netbsd/man8/afterboot.8 @@ -0,0 +1,1095 @@ +.\" $NetBSD: afterboot.8,v 1.83 2023/03/19 17:26:12 kre Exp $ +.\" $OpenBSD: afterboot.8,v 1.72 2002/02/22 02:02:33 miod Exp $ +.\" +.\" Originally created by Marshall M. Midden -- 1997-10-20, m4@umn.edu +.\" Adapted to NetBSD by Julio Merino -- 2002-05-10, jmmv@NetBSD.org +.\" +.\" +.\" Copyright (c) 2002-2008 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.\" +.\" Copyright (c) 1997 Marshall M. Midden +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Marshall M. Midden. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd June 4, 2021 +.Dt AFTERBOOT 8 +.Os +.Sh NAME +.Nm afterboot +.Nd things to check after the first complete boot +.Sh DESCRIPTION +.Ss Starting Out +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 +.Ux +is assumed. +.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 +.Xr ls 1 +command, type: +.Bd -literal -offset indent +.Ic man 1 ls +.Ed +.Pp +Administrators will rapidly become more familiar with +.Nx +if they get used to using the manual pages. +.Ss Login +On a fresh install with no other user accounts, login as +.Dq Ic root . +You can do so on the console, or over the network using +.Xr ssh 1 . +If you have enabled the SSH daemon (see +.Xr sshd 8 ) +and wish to allow root logins over the network, edit the +.Pa /etc/ssh/sshd_config +file and set +.Dq PermitRootLogin +to +.Dq yes +(see +.Xr sshd_config 5 ) . +The default is to not permit root logins over the network +after fresh install in +.Nx . +.Pp +Upon successful login on the console, you may see the message +.Dq 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 +.Dq regular +user, add said user to the +.Dq wheel +group, then use the +.Xr su 1 +command when root privileges are required: +.Bd -literal -offset indent +.Ic useradd -G wheel -m myuser +.Ic passwd myuser +.Ed +.Ss Root password +Change the password for the root user. +(Note that throughout the documentation, the term +.Dq 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 +.Ic /usr/bin/passwd +to change it. +.Pp +It is a good idea to always specify the full path name for both the +.Xr passwd 1 +and +.Xr su 1 +commands as this inhibits the possibility of files placed in your execution +.Ev PATH +for most shells. +Furthermore, the superuser's +.Ev PATH +should never contain the current directory +.Po Dq \&. +.Pc . +.Ss System date +Check the system date with the +.Xr date 1 +command. +If needed, change the date, and/or change the symbolic link of +.Pa /etc/localtime +to the correct time zone in the +.Pa /usr/share/zoneinfo +directory. +.Pp +Examples: +.Bl -tag -width date +.It Cm date 202010051820 +Set the current date to October 5th, 2020 6:20pm. +.It Cm ln -fs /usr/share/zoneinfo/Europe/Helsinki /etc/localtime +Set the time zone to Eastern Europe Summer Time. +.El +.Ss Console settings +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 +.Dq Va encoding +variable found in +.Pa /etc/wscons.conf . +.Pp +.Xr wscons.conf 5 +contains more information about this file. +.Ss Security alerts +All significant and easily fixed problems will be reported at +.Lk https://www.NetBSD.org/support/security/ the security advisories web page . +It is recommended that you check this page regularly. +.Pp +Additionally, you should set +.Dq fetch_pkg_vulnerabilities=YES +in +.Pa /etc/daily.conf +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 +.Xr daily.conf 5 +and +.Xr security.conf 5 +for more details. +.Ss Entropy +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 +.Xr ssh 1 . +You can use +.Xr rndctl 8 +to list the entropy sources with +.Ic rndctl -l , +or save entropy from another machine running +.Nx +with +.Ic rndctl -S +and load it on this one with +.Ic rndctl -L +(as long as there are no eavesdroppers on the medium between the two +machines). +See +.Xr entropy 7 +for more details. +.Ss Check hostname +Use the +.Ic hostname +command to verify that the name of your machine is correct. +See the man page for +.Xr hostname 1 +if it needs to be changed. +You will also need to change the contents of the +.Dq Va hostname +variable in +.Pa /etc/rc.conf +or edit the +.Pa /etc/myname +file to have it stick around for the next reboot. +Note that +.Dq Va hostname +is supposed include a domainname, and that this should +not be confused with YP (NIS) +.Xr domainname 1 . +If you are using +.Xr dhcpcd 8 +to configure network interfaces, it might override these local hostname +settings if your DHCP server specifies client's hostname with other network +configurations. +.Ss Verify network interface configuration +The first thing to do is an +.Ic ifconfig -a +to see if the network interfaces are properly configured. +Correct by editing +.Pa /etc/ifconfig. Ns Ar interface +or the corresponding +.Dq Va ifconfig_ Ns Ar interface +variable in +.Xr rc.conf 5 +(where +.Ar interface +is the interface name, e.g., +.Dq le0 ) +and then using +.Xr ifconfig 8 +to manually configure it +if you do not wish to reboot. +.Pp +Alternatively, many networks allow interfaces to be configured +automatically via DHCP. +To get +.Xr dhcpcd 8 +to start automatically on boot, +you will need to have this line in +.Pa /etc/rc.conf : +.Pp +.Dl dhcpcd=YES +.Pp +See +.Xr dhcpcd 8 +and +.Xr dhcpcd.conf 5 +for more information on setting up a DHCP client. +For information on setting up Wi-Fi, see +.Sx Wireless networking . +.Pp +You can add new +.Dq virtual interfaces +by adding the required entries to +.Pa /etc/ifconfig. Ns Ar interface . +Read the +.Xr ifconfig.if 5 +man page for more information on the format of +.Pa /etc/ifconfig. Ns Ar interface +files. +The loopback interface will look something like: +.Bd -literal -offset indent +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 +.Ed +.Pp +an Ethernet interface something like: +.Bd -literal -offset indent +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 +.Ed +.Pp +and a PPP interface something like: +.Bd -literal -offset indent +ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> + inet 203.3.131.108 --> 198.181.0.253 netmask 0xffff0000 +.Ed +.Pp +See +.Xr mrouted 8 +for instructions on configuring multicast routing. +.Ss Check routing tables +Issue a +.Ic netstat -rn +command. +The output will look something like: +.Bd -literal -offset indent +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 +.Ed +.Pp +The default gateway address is stored in the +.Dq Va defaultroute +variable in +.Pa /etc/rc.conf , +or in the file +.Pa /etc/mygate . +If you need to edit this file, a painless way to reconfigure the network +afterwards is to issue +.Bd -literal -offset indent +.Ic service network restart +.Ed +.Pp +Or, you may prefer to manually configure using a series of +.Ic route add +and +.Ic route delete +commands (see +.Xr route 8 ) . +If you run +.Xr dhcpcd 8 +you will have to kill it by running +.Bd -literal -offset indent +.Ic service dhcpcd stop +.Ed +.Pp +before you flush the routes. +.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 +.Pa /etc/sysctl.conf : +.Pp +.Dl net.inet.ip.forwarding=1 +.Dl net.inet6.ip6.forwarding=1 +.Pp +As an alternative, compile a new kernel with the +.Dq GATEWAY +option. +Packets are not forwarded by default, due to RFC requirements. +.Ss Device nodes +By default, nodes are created in +.Pa /dev +for a fairly typical number of devices. +.Pp +However, if this system has a large number of devices connected +(e.g. for large scale storage), you may want to enable +.Xr devpubd 8 +to ensure a sufficient number of nodes are available. +Set +.Dq Va devpubd=YES +in +.Pa /etc/rc.conf +to create nodes automatically during system runtime. +You can also run the node creation script by hand: +.Bd -literal -offset indent +.Ic cd /dev && sh MAKEDEV +.Ed +.Ss Secure Shell (SSH) +By default, all services are disabled in a fresh +.Nx +installation, and SSH is no exception. +You may wish to enable it so you can remotely control your system. +Set +.Dq Va sshd=YES +in +.Pa /etc/rc.conf +and then starting the server with the command +.Bd -literal -offset indent +.Ic service sshd start +.Ed +.Pp +The first time the server is started, it will generate a new keypair, +which will be stored inside the directory +.Pa /etc/ssh . +.Ss Host names and DNS +The system resolves host names according the rules for hosts in the +name service switch configuration at +.Pa /etc/nsswitch.conf . +By default, it will query +.Pa /etc/hosts +first, and then the DNS resolver specified in +.Pa /etc/resolv.conf . +.Pp +Multicast DNS and DNS Service Discovery are usually not enabled by +default on a fresh +.Nx +system, and can be enabled by setting +.Dq mdnsd=YES +in +.Pa /etc/rc.conf , +and either rebooting or running the following command: +.Bd -literal -offset indent +.Ic service mdnsd start +.Ed +.Pp +You may also wish to enable mdnsd as a source for host lookups +in +.Pa /etc/nsswitch.conf , +see +.Xr nsswitch.conf 5 . +.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 +.Dq named=YES +in +.Pa /etc/rc.conf +and either rebooting or running the following command: +.Bd -literal -offset indent +.Ic service named start +.Ed +.Pp +.Xr named 8 +is configured in +.Pa /etc/named.conf +by default to run as a local caching recursive resolver. +Then, to make the system use it, put the following in +.Pa /etc/resolv.conf : +.Bd -literal -offset indent +nameserver 127.0.0.1 +.Ed +.Ss Wireless networking +To configure the system to connect to a Wi-Fi network with a password +using WPA: +.Bd -literal -offset indent +.Ic wpa_passphrase networkname password >> /etc/wpa_supplicant.conf +.Ed +.Pp +To configure the system to connect to an open wireless network with +no password, edit +.Pa /etc/wpa_supplicant.conf +instead of using +.Xr wpa_passphrase 8 : +.Bd -literal -offset indent +network={ + ssid="Public-WiFi" + key_mgmt=NONE + priority=100 +} +.Ed +.Pp +Then bring up the interface and start the necessary daemons: +.Bd -literal -offset indent +.Ic ifconfig iwm0 up +.Ic service wpa_supplicant onestart +.Ic service dhcpcd onestart +.Ed +.Pp +To automatically connect at boot, add the following to +.Pa /etc/rc.conf : +.Pp +.Dl ifconfig_iwm0="up" +.Dl dhcpcd=YES +.Dl wpa_supplicant=YES +.Pp +While using +.Xr wpa_supplicant 8 , +you can easily retrieve network scan results with +.Xr wpa_cli 8 : +.Bd -literal -offset indent +.Ic wpa_cli scan_results +.Ed +.Pp +Or trigger a rescan: +.Bd -literal -offset indent +.Ic wpa_cli scan +.Ed +.Ss RPC-based network services +Several services depend on the RPC portmapper +.Xr rpcbind 8 +- formerly known as +.Ic portmap +- 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 +.Pa /etc/rc.conf : +.Pp +.Dl rpcbind=YES +.Ss YP (Network Information Service) Setup +Check the YP domain name with the +.Xr domainname 1 +command. +If necessary, correct it by editing the +.Pa /etc/defaultdomain +file or by setting the +.Dq Va domainname +variable in +.Pa /etc/rc.conf . +The +.Pa /etc/rc.d/network +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 +.Xr domainname 1 +command. +To start YP client services, simply run +.Ic ypbind , +then perform the remaining +YP activation as described in +.Xr passwd 5 +and +.Xr group 5 . +.Pp +In particular, to enable YP passwd support, you'll need to update +.Pa /etc/nsswitch.conf +to include +.Dq nis +for the +.Dq passwd +and +.Dq group +entries. +A traditional way to accomplish the same thing is to +add following entry to local passwd database via +.Xr vipw 8 : +.Bd -literal -offset indent +.Li +:*:::::::: +.Ed +.Pp +Note this entry has to be the very last one. +This traditional way works with the default +.Xr nsswitch.conf 5 +setting of +.Dq passwd , +which is +.Dq compat . +.Pp +There are many more YP man pages available to help you. +You can find more information by starting with +.Xr nis 8 . +.Ss Check disk mounts +Check that the disks are mounted correctly by +comparing the +.Pa /etc/fstab +file against the output of the +.Xr mount 8 +and +.Xr df 1 +commands. +Example: +.Bd -literal -offset indent +.Li # Ic cat /etc/fstab +/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 + +.Li # Ic mount +/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) + +.Li # Ic df +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 + +.Li # Ic pstat -s +Device 512-blocks Used Avail Capacity Priority +/dev/sd0b 131072 84656 46416 65% 0 +.Ed +.Pp +Edit +.Pa /etc/fstab +and use the +.Xr mount 8 +and +.Xr umount 8 +commands as appropriate. +Refer to the above example and +.Xr fstab 5 +for information on the format of this file. +.Pp +You may wish to do NFS mounts now too, or you can do them later. +.Ss Clock synchronization +In order to make sure the system clock is synchronized +to that of a publicly accessible NTP server, +make sure that +.Pa /etc/rc.conf +contains the following: +.Pp +.Dl ntpdate=YES +.Dl ntpd=YES +.Pp +See +.Xr date 1 , +.Xr ntpdate 8 , +.Xr ntpd 8 , +.Xr rdate 8 , +and +.Xr timed 8 +for more information on setting the system's date. +.Ss Installing packages +The +.Nx +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 +.Lk https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/ +or a mirror. +.Pp +For most users, using pkgin to manage binary packages is recommended. +.Pp +To install pkgin, if it was not done by the installer: +.Bd -literal -offset indent +.Ic PKG_PATH=https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/[...] +.Ic export PKG_PATH +.Ic pkg_add pkgin +.Ic pkgin update +.Ic pkgin install bash mpg123 fluxbox ... +.Ed +.Pp +See +.Lk https://www.pkgsrc.org/ +and +.Pa pkgsrc/doc/pkgsrc.txt +for more details. +.Sh CHANGING /etc FILES +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 +.Sx Kerberos +section if you won't be using Kerberos). +We suggest that you +.Ic cd /etc +and edit most of the files in that directory. +.Pp +Note that the +.Pa /etc/motd +file is modified by +.Pa /etc/rc.d/motd +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. +.Ss Add new users +To add new users and groups, there are +.Xr useradd 8 +and +.Xr groupadd 8 ; +see also +.Xr user 8 +for further programs for user and group manipulation. +You may use +.Xr vipw 8 +to add users to the +.Pa /etc/passwd +file +and edit +.Pa /etc/group +by hand to add new groups. +The manual page for +.Xr su 1 , +tells you to make sure to put people in +the +.Sq wheel +group if they need root access (non-Kerberos). +For example: +.Bd -literal -offset indent +wheel:*:0:root,myself +.Ed +.Pp +Follow instructions for +.Xr kerberos 8 +if using +Kerberos +for authentication. +.Ss System boot scripts and /etc/rc.local +.Pa /etc/rc +and the +.Pa /etc/rc.d/* +scripts are invoked at boot time after single user mode has exited, +and at shutdown. +The whole process is controlled by the master script +.Pa /etc/rc . +This script should not be changed by administrators. +.Pp +The directory +.Pa /etc/rc.d +contains a series of scripts used at startup/shutdown, called by +.Pa /etc/rc . +.Pa /etc/rc +is in turn influenced by the configuration variables present in +.Pa /etc/rc.conf . +.Pp +The script +.Pa /etc/rc.local +is run as the last thing during multiuser boot, and is provided +to allow any other local hooks necessary for the system. +.Ss rc.conf +To enable or disable various services on system startup, +corresponding entries can be made in +.Pa /etc/rc.conf . +You can take a look at +.Pa /etc/defaults/rc.conf +to see a list of default system variables, which you can override in +.Pa /etc/rc.conf . +Note you are +.Em not +supposed to change +.Pa /etc/defaults/rc.conf +directly, edit only +.Pa /etc/rc.conf . +See +.Xr rc.conf 5 +for further information. +.Ss Automounter daemon (AMD) +To use the +.Xr amd 8 +automounter, create the +.Pa /etc/amd +directory, copy example config files from +.Pa /usr/share/examples/amd +to +.Pa /etc/amd +and customize them as needed. +Alternatively, you can get your maps with YP. +.Ss Concatenated disks (ccd) +If you are using +.Xr ccd 4 +concatenated disks, edit +.Pa /etc/ccd.conf . +You may wish to take a look to +.Xr ccdconfig 8 +for more information about this file. +Use the +.Ic ccdconfig -U +command to unload and the +.Ic ccdconfig -C +command to create tables internal to the kernel for the concatenated disks. +You then +.Xr mount 8 , +.Xr umount 8 , +and edit +.Pa /etc/fstab +as needed. +.Ss Nx Packet Filter +.Xr npf 7 +is the default firewall used on +.Nx . +You may wish to enable it if your machine is connected directly to the +internet. +To do this, edit +.Pa /etc/npf.conf +and set +.Dq npf=YES +in +.Pa /etc/rc.conf . +Configuration examples for NPF can be found in +.Pa /usr/share/examples/npf . +Before installing a configuration, you can validate it with +.Xr npfctl 8 . +.Ss X Display Manager +If you've installed X, you may want to turn on +.Xr xdm 1 , +the X Display Manager. +To do this, set +.Dq xdm=YES +in +.Pa /etc/rc.conf . +.Ss Printers +Edit +.Pa /etc/printcap +and +.Pa /etc/hosts.lpd +to get any printers set up. +Consult +.Xr lpd 8 +and +.Xr printcap 5 +if needed. +.Ss Internet Services (inetd) +Various internet services can be enabled in +.Pa /etc/inetd.conf , +including +.Xr httpd 8 +and +.Xr finger 1 . +Note that by default all services are disabled for security reasons. +Only add things that are really needed. +.Ss Kerberos +If you are going to use Kerberos for authentication, +see +.Xr kerberos 8 +and +.Dq info heimdal +for more information. +If you already have a Kerberos master, change directory to +.Pa /etc/kerberosV +and configure. +Remember to get a +.Pa srvtab +from the master so that the remote commands work. +.Ss Mail Aliases +Check +.Pa /etc/mail/aliases +and update appropriately if you want e-mail to be routed +to non-local addresses or to different users. +.Pp +Run +.Xr newaliases 1 +after changes. +.Ss Postfix +.Nx +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 +.Pa /etc/postfix/main.cf +and +.Pa /etc/postfix/master.cf . +If you wish to use a different MTA (e.g., sendmail), install your MTA of +choice and edit +.Pa /etc/mailer.conf +to point to the proper binaries. +.Ss DHCP server +If this is a +DHCP +server, edit +.Pa /etc/dhcpd.conf +and +.Pa /etc/dhcpd.interfaces +as needed. +You will have to make sure +.Pa /etc/rc.conf +has +.Dq dhcpd=YES +or run +.Xr dhcpd 8 +manually. +.Ss Bootparam server +If this is a +Bootparam +server, edit +.Pa /etc/bootparams +as needed. +You will have to turn it on in +.Pa /etc/rc.conf +by adding +.Dq bootparamd=YES . +.Ss NFS server +If this is an NFS server, make sure +.Pa /etc/rc.conf +has: +.Bd -literal -offset indent +nfs_server=YES +mountd=YES +rpcbind=YES +.Ed +.Pp +Edit +.Pa /etc/exports +and get it correct. +After this, you can start the server by issuing: +.Bd -literal -offset indent +.Ic service rpcbind start +.Ic service mountd start +.Ic service nfsd start +.Ed +which will also start dependencies. +.Ss HP remote boot server +Edit +.Pa /etc/rbootd.conf +if needed for remote booting. +If you do not have HP computers doing remote booting, do not enable this. +.Ss Daily, weekly, monthly scripts +Look at and possibly edit the +.Pa /etc/daily.conf , /etc/weekly.conf , +and +.Pa /etc/monthly.conf +configuration files. +You can check which values you can set by looking +to their matching files in +.Pa /etc/defaults . +Your site specific things should go into +.Pa /etc/daily.local , /etc/weekly.local , +and +.Pa /etc/monthly.local . +.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.) +.Ss Other files in /etc +Look at the other files in +.Pa /etc +and edit them as needed. +(Do not edit files ending in +.Pa .db +\(em like +.Pa pwd.db , spwd.db , +nor +.Pa localtime , +nor +.Pa rmt , +nor any directories.) +.Ss Crontab (background running processes) +Check what is running by typing +.Ic crontab -l +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 +.Ic crontab -e +and change some of the lines to read: +.Bd -literal -offset indent +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 +.Ed +.Pp +See +.Xr crontab 5 . +.Ss Next day cleanup +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: +.Bd -literal -offset indent +var/mail: + permissions (0755, 0775) +etc/daily: + user (0, 3) +.Ed +.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 +.Xr mtree 8 +using +.Pa /etc/mtree/special . +Use +.Xr chmod 1 , +.Xr chgrp 1 , +and +.Xr chown 8 +as needed. +.Sh SYSTEM TESTING +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 +.Xr tests 7 +for details on how to do so. +.Pp +You can use +.Xr ps 1 , +.Xr netstat 1 , +and +.Xr fstat 1 +to check on running processes, network connections, and opened files, +respectively. +Other tools you may find useful are +.Xr systat 1 +and +.Xr top 1 . +.Sh SEE ALSO +.Xr chgrp 1 , +.Xr chmod 1 , +.Xr config 1 , +.Xr crontab 1 , +.Xr date 1 , +.Xr df 1 , +.Xr domainname 1 , +.Xr fstat 1 , +.Xr hostname 1 , +.Xr make 1 , +.Xr man 1 , +.Xr netstat 1 , +.Xr newaliases 1 , +.Xr passwd 1 , +.Xr pkg_add 1 , +.Xr ps 1 , +.Xr ssh 1 , +.Xr su 1 , +.Xr systat 1 , +.Xr top 1 , +.Xr xdm 1 , +.Xr ccd 4 , +.Xr aliases 5 , +.Xr crontab 5 , +.Xr dhcpcd.conf 5 , +.Xr exports 5 , +.Xr fstab 5 , +.Xr group 5 , +.Xr hosts 5 , +.Xr ifconfig.if 5 , +.Xr mailer.conf 5 , +.Xr named.conf 5 , +.Xr nsswitch.conf 5 , +.Xr passwd 5 , +.Xr printcap 5 , +.Xr rc.conf 5 , +.Xr resolv.conf 5 , +.Xr sshd_config 5 , +.Xr wpa_supplicant.conf 5 , +.Xr wscons.conf 5 , +.Xr hier 7 , +.Xr hostname 7 , +.Xr pkgsrc 7 , +.Xr tests 7 , +.Xr amd 8 , +.Xr ccdconfig 8 , +.Xr chown 8 , +.Xr devpubd 8 , +.Xr dhcpcd 8 , +.Xr dhcpd 8 , +.Xr dmesg 8 , +.Xr groupadd 8 , +.Xr ifconfig 8 , +.Xr inetd 8 , +.Xr kerberos 8 , +.Xr lpd 8 , +.Xr mdnsd 8 , +.Xr mount 8 , +.Xr mrouted 8 , +.Xr mtree 8 , +.Xr named 8 , +.Xr nis 8 , +.Xr ntpd 8 , +.Xr ntpdate 8 , +.Xr rbootd 8 , +.Xr rc 8 , +.Xr rdate 8 , +.Xr rmt 8 , +.Xr route 8 , +.Xr rpc.bootparamd 8 , +.Xr rpcbind 8 , +.Xr sshd 8 , +.Xr timed 8 , +.Xr umount 8 , +.Xr useradd 8 , +.Xr vipw 8 , +.Xr wpa_cli 8 , +.Xr wpa_supplicant 8 , +.Xr yp 8 , +.Xr ypbind 8 +.Sh HISTORY +This document first appeared in +.Ox 2.2 . +It has been adapted to +.Nx +and first appeared in +.Nx 2.0 . diff --git a/static/netbsd/man8/boot.8 b/static/netbsd/man8/boot.8 new file mode 100644 index 00000000..cc083d78 --- /dev/null +++ b/static/netbsd/man8/boot.8 @@ -0,0 +1,298 @@ +.\" $NetBSD: boot.8,v 1.16 2017/02/18 21:47:11 wiz Exp $ +.\" +.\" Copyright (c) 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This code is derived from software written and contributed +.\" to Berkeley by William Jolitz. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_i386.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd August 16, 2014 +.Dt BOOT 8 +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.Sh DESCRIPTION +This document provides information on using common features in the +.Nx +boot loader. +Additional information may be found in +architecture-specific +.Xr boot 8 +manual pages. +.Ss Boot Protocol +In the native +.Nx +boot protocol, options are passed from the boot loader +to the kernel via flag bits in the +.Va boothowto +variable (see +.Xr boothowto 9 ) . +Some boot loaders may also support other boot protocols. +.Ss Menu +Some boot loaders may present a menu, which may be configured via +.Xr boot.cfg 5 . +.Ss Interactive mode +In interactive mode, the boot loader will present a prompt, allowing +input of these commands: +.\" NOTE: much of this text is duplicated in architecture-specific +.\" man pages (man8/man8.*/*boot*.8); +.\" please try to keep all relevant files synchronized. +.Bl -tag -width 04n -offset 04n +.It Ic boot Oo Va device : Oc Ns Oo Va filename Oc Oo Fl 1234abcdmqsvxz Oc +The default +.Va device +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. +.Va device +is of the form +.Xo Va xd +.Op Va N Ns Op Va x +.Xc +where +.Va xd +is the device from which to boot, +.Va N +is the unit number, and +.Va x +is the partition letter. +.Pp +The following list of supported devices may vary from installation to +installation: +.Pp +.Bl -hang -compact +.It hd +Hard disks. +.It fd +Floppy drives. +.El +.Pp +The default +.Va filename +is +.Pa netbsd ; +if the boot loader fails to successfully +open that image, it then tries +.Pa netbsd.gz +(expected to be a kernel image compressed by gzip), followed by +.Pa netbsd.old , +.Pa netbsd.old.gz , +.Pa onetbsd , +and finally +.Pa onetbsd.gz . +Alternate system images can be loaded by just specifying the name of the image. +.Pp +Options are: +.Bl -tag -width xxx +.It Fl 1 +Sets the machine-dependent flag +.Sy RB_MD1 +in +.Va boothowto . +.It Fl 2 +Sets the machine-dependent flag +.Sy RB_MD2 +in +.Va boothowto . +.It Fl 3 +Sets the machine-dependent flag +.Sy RB_MD3 +in +.Va boothowto . +.It Fl 4 +Sets the machine-dependent flag +.Sy RB_MD4 +in +.Va boothowto . +.It Fl a +Sets the +.Sy RB_ASKNAME +flag in +.Va boothowto . +This causes the kernel to prompt for the root file system device, +the system crash dump device, and the path to +.Xr init 8 . +.It Fl b +Sets the +.Sy RB_HALT +flag in +.Va boothowto . +This causes subsequent reboot attempts to halt instead of rebooting. +.It Fl c +Sets the +.Sy RB_USERCONF +flag in +.Va boothowto . +This causes the kernel to enter the +.Xr userconf 4 +device configuration manager as soon as possible during the boot. +.Xr userconf 4 +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. +.It Fl d +Sets the +.Sy RB_KDB +flag in +.Va boothowto . +Requests the kernel to enter debug mode, in which it +waits for a connection from a kernel debugger; see +.Xr ddb 4 . +.It Fl m +Sets the +.Sy RB_MINIROOT +flag in +.Va boothowto . +Informs the kernel that a mini-root file system is present in memory. +.It Fl q +Sets the +.Sy AB_QUIET +flag in +.Va boothowto . +Boot the system in quiet mode. +.It Fl s +Sets the +.Sy RB_SINGLE +flag in +.Va boothowto . +Boot the system in single-user mode. +.It Fl v +Sets the +.Sy AB_VERBOSE +flag in +.Va boothowto . +Boot the system in verbose mode. +.It Fl x +Sets the +.Sy AB_DEBUG +flag in +.Va boothowto . +Boot the system with debug messages enabled. +.It Fl z +Sets the +.Sy AB_SILENT +flag in +.Va boothowto . +Boot the system in silent mode. +.El +.It Ic consdev Va dev +Immediately switch the console to the specified device +.Va dev +and reprint the banner. +.Va dev +must be one of +.\" .Bl -item -width com[0123]kbd -offset indent -compact +.Ar pc , com0 , com1 , com2 , +.Ar com3 , com0kbd , com1kbd , com2kbd , +.Ar com3kbd , +or +.Ar auto . +See +.Sx Console Selection Policy +in +.Xr x86/boot_console 8 . +.It Ic dev Op Va device +Set the default drive and partition for subsequent filesystem +operations. +Without an argument, print the current setting. +.Va device +is of the form specified in +.Cm boot . +.It Ic help +Print an overview about commands and arguments. +.\" .It Ic load Va module Op Va arguments +.\" [x86 only] +.It Ic ls Op Pa path +Print a directory listing of +.Pa path , +containing inode number, filename, and file type. +.Pa path +can contain a device specification. +.\" .It Ic multiboot Va kernel Op Va arguments +.\" [x86 only] +.It Ic quit +Reboot the system. +.\" .It Ic userconf Va command +.\" [x86only] +.El +.Pp +In an emergency, the bootstrap methods described in the +.Nx +installation notes for the specific architecture +can be used. +.Sh FILES +.Bl -tag -width /usr/mdec/bootxx_fstype -compact +.It Pa /boot +boot program code loaded by the primary bootstrap +.\" .It Pa /boot.cfg +.\" optional configuration file +.\" [x86 only] +.It Pa /netbsd +system code +.It Pa /netbsd.gz +gzip-compressed system code +.It Pa /usr/mdec/boot +master copy of the boot program (copy to /boot) +.It Pa /usr/mdec/bootxx_fstype +primary bootstrap for filesystem type fstype, copied to the start of +the +.Nx +partition by +.Xr installboot 8 . +.El +.Sh SEE ALSO +Architecture-specific +.Xr boot 8 +manual pages (such as +.Xr emips/boot 8 , +.Xr sparc64/boot 8 , +.Xr x86/boot 8 ) , +.Xr ddb 4 , +.Xr userconf 4 , +.\" .Xr boot.cfg 5 [x86 only] , +.Xr halt 8 , +.Xr installboot 8 , +.Xr reboot 8 , +.Xr rescue 8 , +.Xr shutdown 8 , +.Xr boothowto 9 +.Sh BUGS +The kernel file name must be specified before, not after, the boot options. +Any +.Ar filename +specified after the boot options, e.g.: +.Pp +.Bd -unfilled -offset indent -compact +.Cm boot -d netbsd.test +.Ed +.Pp +is ignored, and the default kernel is booted. diff --git a/static/netbsd/man8/compat_30.8 b/static/netbsd/man8/compat_30.8 new file mode 100644 index 00000000..8aa8af82 --- /dev/null +++ b/static/netbsd/man8/compat_30.8 @@ -0,0 +1,206 @@ +.\" $NetBSD: compat_30.8,v 1.10 2025/11/22 21:24:49 andvar Exp $ +.\" +.\" Copyright (c) 2006 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from a document contributed to The NetBSD Foundation +.\" by Chapman Flack. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd December 15, 2007 +.Dt COMPAT_30 8 +.Os +.Sh NAME +.Nm compat_30 +.Nd setup procedure for backward compatibility on post-3.0 releases +.Sh SYNOPSIS +.Cd "options COMPAT_30" +.Sh DESCRIPTION +The +.Nm +module allows +.Nx +to run +.Nx 3.0 +executables. +.Pp +The support is present if the kernel was built with option +.Dv COMPAT_30 . +It is not available as a loadable module. +.Pp +Static executables typically need no additional setup. +Dynamic binaries may require shared libraries whose major version +number changed since +.Nx 3.0 , +which are listed below. +A shadow directory under +.Pa /emul +is not used; the libraries can be obtained from a +.Nx 3.0 +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 +.Nx 3.0 +has been done and these libraries are still present, nothing more need +be done. +.Ss Libraries needed from 3.0 +.Bl -item +.It +.Pa /lib/libcrypto.so.2.1 +.Pa /lib/libcrypto.so.2 +.It +.Pa /usr/lib/libcrypto.so.2.1 +.Pa /usr/lib/libcrypto.so.2 +.It +.Pa /lib/libevent.so.0.2 +.Pa /lib/libevent.so.0 +.It +.Pa /usr/lib/libevent.so.0.2 +.Pa /usr/lib/libevent.so.0 +.It +.Pa /usr/lib/libg2c.so.2.0 +.Pa /usr/lib/libg2c.so.2 +.It +.Pa /usr/lib/libkadm.so.5.0 +.Pa /usr/lib/libkadm.so.5 +.It +.Pa /usr/lib/libkafs.so.6.0 +.Pa /usr/lib/libkafs.so.6 +.It +.Pa /usr/lib/libkdb.so.5.0 +.Pa /usr/lib/libkdb.so.5 +.It +.Pa /usr/lib/libkrb5.so.19.1 +.Pa /usr/lib/libkrb5.so.19 +.It +.Pa /usr/lib/libkrb.so.6.0 +.Pa /usr/lib/libkrb.so.6 +.It +.Pa /usr/lib/libkstream.so.2.0 +.Pa /usr/lib/libkstream.so.2 +.It +.Pa /usr/lib/libmagic.so.0.1 +.Pa /usr/lib/libmagic.so.0 +.It +.Pa /usr/lib/libpcap.so.1.4 +.Pa /usr/lib/libpcap.so.1 +.It +.Pa /lib/libradius.so.0.0 +.Pa /lib/libradius.so.0 +.It +.Pa /usr/lib/libradius.so.0.0 +.Pa /usr/lib/libradius.so.0 +.It +.Pa /usr/lib/libssh.so.1.0 +.Pa /usr/lib/libssh.so.1 +.It +.Pa /usr/lib/libssl.so.3.0 +.Pa /usr/lib/libssl.so.3 +.It +.Pa /usr/lib/libstdc++.so.5.0 +.Pa /usr/lib/libstdc++.so.5 +.\" .It +.\" .Pa libtelnet lives where? +.It +.Pa /lib/libz.so.0.4 +.Pa /lib/libz.so.0 +.It +.Pa /usr/lib/libz.so.0.4 +.Pa /usr/lib/libz.so.0 +.It +.Pa /usr/lib/libamu.so.2.1 +.Pa /usr/lib/libamu.so.2 +.El +.Sh IMPLEMENTATION NOTES +.Dv COMPAT_30 +enables the +.Nx 3.0 +versions of the following system calls, whose syscall numbers and +argument structures were changed after the 3.0 release to accommodate +64-bit filesystems: +.Xr fhstat 2 , +.Xr fstat 2 , +.Xr getdents 2 , +.Xr lstat 2 , +.Xr stat 2 . +.Pp +The filehandle structure (formerly +.Vt fhandle_t ) +was made opaque to userland and variable-sized. +A +.Fa fh_size +argument was added to related syscalls: +.Xr fhstat 2 , +.Xr fhstatvfs 2 , +.Xr fhstatvfs1 2 , +.Xr fhopen 2 , +.Xr getfh 2 . +This changes the API and ABI of those syscalls, +.Dv COMPAT_30 +enables binary compatibility with the old ABI. +Source compatibility is not provided, as use of those syscalls is +supposed to be rare. +.Pp +The error code from the +.Xr socket 2 +syscall changed from +.Er EPROTONOSUPPORT +to +.Er EAFNOSUPPORT +in the case of an unsupported address family. +.Dv COMPAT_30 +enables binary compatibility with the old ABI. +Source compatibility is not provided. +.Pp +The +.Vt struct ntptimeval +used by +.Xr ntp_gettime 2 +changed with the implementation of timecounters. +.Sh SEE ALSO +.Xr config 1 , +.Xr fhstat 2 , +.Xr fstat 2 , +.Xr getdents 2 , +.Xr lstat 2 , +.Xr stat 2 , +.Xr options 4 +.Sh HISTORY +.Nx +offers back-compatibility options back to +.Nx 0.9 , +but the first to be documented with a manual page is +.Nm . +.Sh BUGS +The compatible +.Xr getdents 2 +is unable to see directory entries beneath the top layer of a union, +even though the real 3.0 +.Fn getdents +did not have that problem. +.Sh SECURITY CONSIDERATIONS +Programs with security impact that receive incorrect directory contents +from +.Fn getdents +may behave improperly, as when they are unable to find, or find the wrong +versions of, important files. diff --git a/static/netbsd/man8/compat_bsdos.8 b/static/netbsd/man8/compat_bsdos.8 new file mode 100644 index 00000000..b658c448 --- /dev/null +++ b/static/netbsd/man8/compat_bsdos.8 @@ -0,0 +1,201 @@ +.\" $NetBSD: compat_bsdos.8,v 1.7 2020/09/02 23:38:11 uwe Exp $ +.\" +.\" Copyright (c) 2020 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Dan Plassche. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd August 27, 2020 +.Dt COMPAT_BSDOS 8 +.Os +.Sh NAME +.Nm compat_bsdos +.Nd binary compatibility for BSDi releases +.Sh DESCRIPTION +The +.Dv COMPAT_NOMID +kernel option includes compatibility with +.Tn BSDi Ns No \ 1. Ns Em \^x Ns \|\(en\|3. Ns Em \^x +.Xr a.out 5 +binaries on +.Nx Ns Tn /i386 +and +.Nx Ns Tn /amd64 . +The option is enabled by default in the +.Li GENERIC +kernel on i386, +but needs to be set along with +.Dv EXEC_AOUT +on amd64. +.Pp +Null memory protection must be disabled with the +.Xr sysctl 7 +option +.Va vm.user_va0_disable +set to +.Li 0 +for the binaries to run successfully. +.Pp +.Bsx +binaries may be placed under +.Pa /emul +directory to match the location of other +non-native executables +on +.Nx , +but the compatibility environment +does not automatically lookup libraries +under +.Pa /emul/bsdos +as happens with the shared +libraries +for +.Nx 1.0\|\(en\|1.5 +.Xr a.out 5 +binaries under +.Pa /emul/aout . +.Pp +.Tn BSD/386 Ns No \ 1.0\|\(en\|1.1 +uses static binaries that do not +dynamically load libraries at runtime. +.Pp +.Bsx 2.0 +introduced +.Dq "static shared libraries" +as the default for standard binaries. +The shared libraries are compiled from +.Pa /lib +and +.Pa /usr/lib +to a custom format bound to memory +loading addresses for each library +under +.Pa /shlib . +BSDi libraries +under +.Pa /shlib +are not in the standard +.Xr ar 5 +or position-independent shared object +formats and cannot be loaded by +.Xr ldconfig 8 +on +.Nx . +In order for BSDi executables to +access the objects at the +hardcoded +.Pa /shlib +path, +the user may setup a +symbolic link from +.Pa /shlib +to +.Pa /emul/bsdos/shlib . +.\" or run a shell under a +.\" .Ic chroot +.\" with the command +.\" .Ic chroot "/emul/bsdos /bin/sh" . +.\" One could rebuild the BSDi userland +.\" from source using +.\" .Pa /emul/bsdos/lib +.\" and +.\" .Pa /emul/bsdos/usr/lib . +.\" Then adding +.\" .Pa /emul/bsdos/lib +.\" and +.\" .Pa /emul/bsdos/usr/lib +.\" to +.\" .Pa /etc/ld.so.conf +.\" and running +.\" .Ic ldconfig +.\" to regenerate +.\" .Pa /var/run/ld.so.hints +.\" for a new hybrid setup. +.Pp +.Bsx 4.0 +switched to an ELF binary executable format +that does not run under the +compatibility layers currently available on +.Nx . +.Sh SEE ALSO +.Xr ld.aout_so 1 , +.Xr options 4 , +.Xr a.out 5 , +.Xr elf 5 , +.Xr sysctl 7 , +.Xr compat_netbsd32 8 , +.Xr ldconfig 8 +.Sh HISTORY +.Tn BSD/386 Ns No \ 1.0\|\(en\|1.1 +was derived from +.Bx 4.3 Tn Reno +code in the +.Tn Net/2 +release. +.Pp +.Bsx 2.0 +was based on +.Bx 4.4 Tn Lite , +but added the new static shared library +format as the runtime default for executables. +The build system included the +.Li shlicc +command with the +.Fl Bstatic +flag that allowed reverting to the standard +library archive format that remained available +under +.Pa /lib +and +.Pa /usr/lib . +.Pp +.Nx 1.0 +added shared libraries using a standard +position-independent shared object +format. +The previous default relocatable libraries +in the traditional +.Xr ar 5 +format remained available. +.Pp +.Ox 2.2\|\(en\|4.7 +included a different compatibility implementation +under the +.Dv COMPAT_BSDOS +kernel option. +.Sh BUGS +.Bsx +compatibility was broken on +.Nx 5\|\(en\|6 . +.Pp +.Bsx 3.0 +added +.Tn SPARC +support, but the binaries are incorrectly recognized as +.Tn SunOS +executables and fail on +.Nx Ns Tn /sparc +and +.Nx Ns Tn /sparc64 . diff --git a/static/netbsd/man8/compat_freebsd.8 b/static/netbsd/man8/compat_freebsd.8 new file mode 100644 index 00000000..0205a71a --- /dev/null +++ b/static/netbsd/man8/compat_freebsd.8 @@ -0,0 +1,419 @@ +.\" $NetBSD: compat_freebsd.8,v 1.20 2026/01/02 22:22:22 nia Exp $ +.\" from: compat_linux.8,v 1.1 1995/03/05 23:30:36 fvdl Exp +.\" +.\" Copyright (c) 1995 Frank van der Linden +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 10, 2018 +.Dt COMPAT_FREEBSD 8 +.Os +.Sh NAME +.Nm compat_freebsd +.Nd setup procedure for running FreeBSD binaries +.Sh DESCRIPTION +.Bf -symbolic +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. +.Ef +.Pp +.Nx +supports running +.Fx +binaries. +Most binaries should work, except programs that use +.Fx Ns -specific +features. +These include i386-specific calls, such as syscons utilities. +The +.Fx +compatibility feature is active for kernels compiled +with the +.Dv COMPAT_FREEBSD +option enabled. +.Pp +A lot of programs are dynamically linked. +This means, that you will also need the +.Fx +shared libraries that the program depends on, and the runtime +linker. +Also, you will need to create a +.Dq shadow root +directory for +.Fx +binaries on your +.Nx +system. +This directory is named +.Pa /emul/freebsd . +Any file operations done by +.Fx +programs run under +.Nx +will look in this directory first. +So, if a +.Fx +program opens, for example, +.Pa /etc/passwd , +.Nx +will +first try to open +.Pa /emul/freebsd/etc/passwd , +and if that does not exist open the +.Sq real +.Pa /etc/passwd +file. +It is recommended that you install +.Fx +packages that include configuration files, etc under +.Pa /emul/freebsd , +to avoid naming conflicts with possible +.Nx +counterparts. +Shared libraries should also be installed in the shadow tree. +.Pp +Generally, you will need to look for the shared libraries that +.Fx +binaries depend on only the first few times that you install a +.Fx +program on your +.Nx +system. +After a while, you will have a sufficient set of +.Fx +shared libraries on your system to be able to run newly imported +.Fx +binaries without any extra work. +.Ss Setting up shared libraries +How to get to know which shared libraries +.Fx +binaries need, and where +to get them? Basically, there are 2 possibilities (when following +these instructions: you will need to be root on your +.Nx +system to do the necessary installation steps). +.Pp +.Bl -enum -compact +.It +You have access to a +.Fx +system. +In this case you can temporarily install the binary there, see what +shared libraries it needs, and copy them to your +.Nx +system. +Example: you have just ftp-ed the +.Fx +binary of SimCity. +Put it on the +.Fx +system you have access to, and check which shared libraries it +needs by running +.Sq ldd sim : +.Bd -literal -offset indent +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) +.Ed +.Pp +You would need go get all the files from the last column, and +put them under +.Pa /emul/freebsd . +This means you eventually have these files on your +.Nx +system: +.Bl -item -compact +.It +.Pa /emul/freebsd/usr/X11R6/lib/libXext.so.6.0 +.It +.Pa /emul/freebsd/usr/X11R6/lib/libX11.so.6.0 +.It +.Pa /emul/freebsd/usr/lib/libc.so.2.1 +.It +.Pa /emul/freebsd/usr/lib/libm.so.2.0 +.It +.Pa /emul/freebsd/usr/lib/libgcc.so.261.0 +.El +.Pp +Note that if you already have a +.Fx +shared library with a matching major revision number to the first +column of the +.Ic ldd +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: +.Bl -item -compact +.It +.Pa /emul/freebsd/usr/lib/libc.so.2.0 +.El +.Pp +and you find that the ldd output for a new binary you want to +install is: +.Bd -literal +\-lc.2 => /usr/lib/libc.so.2.1 (0x10144000) +.Ed +.Pp +You won't need to worry about copying +.Pa /usr/lib/libc.so.2.1 +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: +.Bl -item -compact +.It +.Pa /emul/freebsd/usr/lib/libc.so.2.1 +.El +.Pp +Finally, you must make sure that you have the +.Fx +runtime linker and its config files on your system. +You should copy these files from the +.Fx +system to their appropriate place on your +.Nx +system (in the +.Pa /emul/freebsd +tree): +.Bl -item -compact +.It +.Pa usr/libexec/ld.so +.It +.Pa var/run/ld.so.hints +.El +.It +You don't have access to a +.Fx +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. +.Pp +Retrieve the following files (from _one_ ftp site to avoid +any version mismatches), and install them under +.Pa /emul/freebsd +(i.e. +.Pa foo/bar +is installed as +.Pa /emul/freebsd/foo/bar ) : +.Bl -item -compact +.It +.Pa sbin/ldconfig +.It +.Pa usr/bin/ldd +.It +.Pa usr/lib/libc.so.x.y.z +.It +.Pa usr/libexec/ld.so +.El +.Pp +.Ic ldconfig +and +.Ic ldd +don't necessarily need to be under +.Pa /emul/freebsd , +you can install them elsewhere in the system too. +Just make sure they don't conflict with their +.Nx +counterparts. +A good idea would be to install them in +.Pa /usr/local/bin +as +.Ic ldconfig-freebsd +and +.Ic ldd-freebsd . +.Pp +Run the +.Fx +ldconfig program with directory arguments in which the +.Fx +runtime linker should look for shared libs. +.Pa /usr/lib +are standard, you could run like the following: +.Bd -literal -offset indent +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 +.Ed +.Pp +Note that argument directories of ldconfig are +mapped to +.Pa /emul/freebsd/XXXX +by +.Nx Ns 's +compat code, and should exist as such on your system. +Make sure +.Pa /emul/freebsd/var/run/ld.so.hints +is existing when you run +.Fx Ns 's +ldconfig, if not, you may lose +.Nx Ns 's +.Pa /var/run/ld.so.hints . +.Fx +.Ic ldconfig +should be statically +linked, so it doesn't need any shared libraries by itself. +It will create the file +.Pa /emul/freebsd/var/run/ld.so.hints . +You should rerun the +.Fx +version of the ldconfig program each time you add a new shared library. +.Pp +You should now be set up for +.Fx +binaries which only need a shared libc. +You can test this by running the +.Fx +.Ic ldd +on itself. +Suppose that you have it installed as +.Ic ldd-freebsd , +it should produce something like: +.Bd -literal -offset indent +me@netbsd% ldd-freebsd `which ldd-freebsd` +/usr/local/bin/ldd-freebsd: + -lc.2 => /usr/lib/libc.so.2.1 (0x1001a000) +.Ed +.Pp +This being done, you are ready to install new +.Fx +binaries. +Whenever you install a new +.Fx +program, you should check if it needs shared libraries, and if so, +whether you have them installed in the +.Pa /emul/freebsd +tree. +To do this, you run the +.Fx +version +.Ic ldd +on the new program, and watch its output. +.Ic ldd +(see also the manual page for +.Xr ldd 1 ) +will print a list +of shared libraries that the program depends on, in the +form -l<majorname> => <fullname>. +.Pp +If it prints +.Dq 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 +.Fx +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. +.Pp +.It +In some cases, +.Fx +binary needs access to certain device file. +For example, +.Fx +X server software needs +.Fx +.Pa /dev/ttyv0 +for ioctls. +In this case, create a symbolic link from +.Pa /emul/freebsd/dev/ttyv0 +to a +.Xr wscons 4 +device file like +.Pa /dev/ttyE0 . +You will need to have at least +.Cd options WSDISPLAY_COMPAT_SYSCONS +and probably also +.Cd options WSDISPLAY_COMPAT_USL +in your kernel (see +.Xr options 4 +and +.Xr wscons 4 ) . +.El +.Ss Finding the necessary files +.Em Note : +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. +.Pp +The +.Fx +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: +.Lk ftp://ftp.FreeBSD.org/pub/FreeBSD +.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 +.Dq 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. +.Bd -literal -offset indent +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 +.\" libX11.so.3 oldlibs +.\" libXt.so.3 oldlibs +.Ed +.Pp +The files called +.Dq bindist.?? +are tar-ed, gzipped and split, so you can extract contents by +.Dq cat bindist.?? | tar zpxf - . +.Pp +Extract the files from these gzipped tarfiles in your +.Pa /emul/freebsd +directory (possibly omitting or afterwards removing files you don't +need), and you are done. +.Sh BUGS +The information about +.Fx +distributions may become outdated. diff --git a/static/netbsd/man8/compat_linux.8 b/static/netbsd/man8/compat_linux.8 new file mode 100644 index 00000000..f2a5501f --- /dev/null +++ b/static/netbsd/man8/compat_linux.8 @@ -0,0 +1,224 @@ +.\" $NetBSD: compat_linux.8,v 1.47 2026/01/02 22:22:22 nia Exp $ +.\" +.\" Copyright (c) 1995 Frank van der Linden +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd September 26, 2021 +.Dt COMPAT_LINUX 8 +.Os +.Sh NAME +.Nm compat_linux +.Nd setup procedure for running Linux binaries +.Sh DESCRIPTION +.Nx +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. +.Nx +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. +.Pp +The Linux compatibility feature is active +for kernels compiled with the +.Dv COMPAT_LINUX +option enabled. +If support for Linux a.out executables is desired, the +.Dv EXEC_AOUT +option should be enabled in addition to option +.Dv COMPAT_LINUX . +Similarly, if support for Linux 32-bit and/or 64-bit ELF executables +is desired, the +.Dv EXEC_ELF32 +and/or +.Dv EXEC_ELF64 +options (respectively) should be enabled in addition to +.Dv COMPAT_LINUX . +If sound support is desired, +.Dv COMPAT_OSSAUDIO +should be enabled. +.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 +.Dq shadow root +directory for Linux binaries on your +.Nx +system. +This directory is named +.Pa /emul/linux +or +.Pa /emul/linux32 +for 32-bit emulation on 64-bit systems. +Any file operations done by Linux programs run under +.Nx +will look in this directory first. +So, if a Linux program opens, for example, +.Pa /etc/passwd , +.Nx +will +first try to open +.Pa /emul/linux/etc/passwd , +and if that does not exist open the +.Sq real +.Pa /etc/passwd +file. +It is recommended that you install +Linux packages that include configuration files, etc under +.Pa /emul/linux , +to avoid naming conflicts with possible +.Nx +counterparts. +Shared libraries should also be installed in the shadow tree. +Filenames that start "/../" are only looked up in the real root. +.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 +.Nx +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. +.Ss Setting up shared libraries +Find the dependencies of a Linux binary using +.Xr readelf 1 : +.Bd -literal +$ 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] +.Ed +.Pp +For x86, you can simply install the openSUSE shared libraries using the +.Pa pkgsrc/emulators/suse131_* +or +.Pa pkgsrc/emulators/suse131_32_* +packages. +.Pp +For example, an application which requires +.Pa libcrypto.so.1.0.0 , +.Pa libXext.so.6 , +and +.Pa libGL.so.1 +will require +.Dv openssl , +.Dv x11 , +and +.Dv glx , +in addition to the +.Dv base +SUSE package. +.Pp +Otherwise, you may have to obtain shared libraries from another Linux +system, and copy them to e.g. +.Pa /emul/linux/lib64 . +.Ss Setting up procfs +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. +.Pp +Mount procfs on +.Nx +using following command: +.Bl -tag -width 123 -offset indent +.It $ mount_procfs procfs /emul/linux/proc +.El +.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 +.Pa /etc/fstab . +.Bl -tag -width 123 -offset indent +.It procfs /emul/linux/proc procfs ro +.El +.Pp +Note: +.Xr mount_procfs 8 +defaults to Linux flavored procfs since +.Nx 5.0 . +Ensure you do not mount procfs with +.Ar nolinux . +.Pp +See +.Xr mount_procfs 8 +for further information. +.Ss Setting up other files +Newer version of Linux use +.Pa /etc/nsswitch.conf +for network information, such as NIS and DNS. +You must create or get a valid copy of this file and put it in +.Pa /emul/linux/etc . +.Sh CAVEATS +.Nm +is generally not enabled in +.Dv GENERIC +kernels for security reasons, +but is available as a module. +It must be added to +.Xr modules.conf 5 +to be used. +It will not be loaded automatically. +.Sh BUGS +The information about Linux distributions will become outdated. +.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. +.Pp +Linux executables cannot handle directory offset cookies > 32 bits. +Should such an offset occur, you will see the message +.Dq 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 +.Fl X +option to +.Xr mount_nfs 8 . +The +.Fl 2 +option to +.Xr mount_nfs 8 +will also have the desired effect, but is less preferable. diff --git a/static/netbsd/man8/compat_netbsd32.8 b/static/netbsd/man8/compat_netbsd32.8 new file mode 100644 index 00000000..4383f228 --- /dev/null +++ b/static/netbsd/man8/compat_netbsd32.8 @@ -0,0 +1,127 @@ +.\" $NetBSD: compat_netbsd32.8,v 1.14 2025/12/17 19:10:27 andvar Exp $ +.\" +.\" Copyright (c) 2001, 2019 Matthew R. Green +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd January 17, 2019 +.Dt COMPAT_NETBSD32 8 +.Os +.Sh NAME +.Nm compat_netbsd32 +.Nd setup procedure for 32-bit compatibility on 64-bit platforms +.Sh DESCRIPTION +The +.Nm +module allows +.Nx Ns Tn /sparc64 +to run +.Nx Ns Tn /sparc +executables, +.Nx Ns Tn /aarch64 +to run +.Nx Ns Tn /arm +executables, +.Nx Ns Tn /mips64 +to run +.Nx Ns Tn /mips +executables, and +.Nx Ns Tn /amd64 +to run +.Nx Ns Tn /i386 +executables. +On +.Nx Ns Tn /mips64 +the default userland is N32 which is a handled by +.Nm +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 +.Nx Ns Tn /arm +ports. +.Pp +To use +.Nm , +one must either have +.Dv COMPAT_NETBSD32 +and +.Dv EXEC_ELF32 +in the kernel, or load the compat_netbsd32 and exec_elf32 kernel +modules. +.Pp +Static executables typically need no additional setup. +Dynamic binaries require the dynamic linker plus shared libraries. +.Pp +Since +.Nx 5.0 +the base system has directly included support for 32-bit compatibility +by installing 32-bit libraries and dynamic linker into +.Pa /usr . +This includes compiler support for compiling 32-bit applications +on platforms where this is supported. +.Pp +For a.out compatibility, +.Pa /usr/libexec/ld.so +from a 32-bit distribution is required to exist, and the a.out +shared libraries must be found in +.Pa /emul/aout +as normal for a.out compatibility. +For 32-bit (64-bit on +.Nx Ns Tn /mips64 ) +ELF compatibility, the relevant +.Pa /usr/libexec/ld.elf_so +needs to be found in +.Bl -column -offset indent "powerpc64" "powerpc" "" +.It Sy Port Ta Sy Target Ta Sy Path +.It Li amd64 Ta i386 Ta /usr/libexec/ld.elf_so-i386 +.It Li sparc64 Ta sparc Ta /usr/libexec/ld.elf_so-sparc +.It Li mips64 Ta O32 Ta /usr/libexec/ld.elf_so-o32 +.It Li mips64 Ta N64 Ta /usr/libexec/ld.elf_so-64 +.It Li powerpc64 Ta powerpc Ta /usr/libexec/ld.elf_so-powerpc +.It Li arm64 Ta eabi Ta /usr/libexec/ld.elf_so-eabi +.El +.Pp +Note that the kernel handles rewriting the built-in ELF interpreter +to the above path. +.Pp +Before +.Nx 5.0 +all of these files needed to be placed under +.Pa /emul/netbsd32 . +.Pp +The shared libraries for a.out binaries do not live under the +.Pa /emul/netbsd32 +directory, but under the +.Pa /emul/aout +directory, where the a.out dynamic linker will find them. +.Sh BUGS +A list of things which fail to work in compatibility mode should +be here. +.Pp +.Xr aio 3 +is not supported. +.Pp +Some +.Xr ioctl 2 +commands are not supported, including +.Xr drm 4 . diff --git a/static/netbsd/man8/compat_sunos.8 b/static/netbsd/man8/compat_sunos.8 new file mode 100644 index 00000000..1f59b652 --- /dev/null +++ b/static/netbsd/man8/compat_sunos.8 @@ -0,0 +1,134 @@ +.\" $NetBSD: compat_sunos.8,v 1.21 2017/07/03 21:31:00 wiz Exp $ +.\" +.\" Copyright (c) 1984 Theo de Raadt +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd February 3, 2001 +.Dt COMPAT_SUNOS 8 +.Os +.Sh NAME +.Nm compat_sunos +.Nd setup procedure for m68k, sparc and sparc64 architectures +.Sh DESCRIPTION +.Nx Ns Tn /sparc64 , +.Nx Ns Tn /sparc +and some of the +.Nx Ns Tn /m68k +architectures can run +.Tn SunOS +executables. +Most executables will work. +.Pp +The exceptions include programs that use the +.Tn SunOS +kvm library, +and various system calls, +.Fn ioctl Ns '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. +.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. +.Pp +The files you need are on your +.Tn 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 +.Nx +machine, do the following: +.Bl -enum -offset 123 +.It +.Li mkdir -p /emul/sunos/usr/lib /emul/sunos/usr/5lib +.It +.Li cp SunOS:/usr/lib/lib*.so.*.* NetBSD:/emul/sunos/usr/lib +.It +.Li cp SunOS:/usr/5lib/lib*.so.*.* NetBSD:/emul/sunos/usr/5lib +.It +.Li cp SunOS:/usr/lib/ld.so NetBSD:/emul/sunos/usr/lib/ld.so +.It +If you ever expect to use YP, you will want to create a link: +.Bd -literal -compact +ln -s /var/run/ypbind.lock /etc/ypbind.lock +.Ed +.El +.Pp +Alternatively, you can use an NFS mount to accomplish the same +effect. +On your +.Nx +machine, do the following: +.Bl -enum -offset 123 +.It +.Li mkdir -p /emul/sunos/usr +.It +.Li mount SunOS:/usr /emul/sunos/usr +.El +.Pp +This will place the +.Tn SunOS +libraries on your +.Nx +machine +in a location where the +.Tn SunOS +compatibility code will look for +first, where they do not conflict with the standard libraries. +.Sh NOTES +When using +.Nm +on +.Nx Ns Tn /sparc64 , +the +.Dv COMPAT_NETBSD32 +option must also be used. +.Sh BUGS +A list of things which fail to work in compatibility mode should +be here. +.Pp +.Tn SunOS +executables can not handle directory offset cookies > 32 bits. +Should such an offset occur, you will see the message +.Dq 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 +.Fl X +option to +.Xr mount_nfs 8 . +The +.Fl 2 +option to +.Xr mount_nfs 8 +will also have the desired effect, but is less preferable. +.Pp +The +.Nx Ns Tn /sparc64 +support is less complete than the other ports. diff --git a/static/netbsd/man8/compat_ultrix.8 b/static/netbsd/man8/compat_ultrix.8 new file mode 100644 index 00000000..dec9e57b --- /dev/null +++ b/static/netbsd/man8/compat_ultrix.8 @@ -0,0 +1,147 @@ +.\" $NetBSD: compat_ultrix.8,v 1.21 2017/07/03 21:31:00 wiz Exp $ +.\" +.\" Copyright (c) 1997 Jonathan Stone +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Jonathan Stone. +.\" 4. Neither the name of the author nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd January 16, 1999 +.Dt COMPAT_ULTRIX 8 +.Os +.Sh NAME +.Nm compat_ultrix +.Nd "setup procedure for ULTRIX compatibility on MIPS and VAX architectures" +.Sh DESCRIPTION +.Nx Ns Tn /mips +and +.Nx Ns Tn /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. +.Pp +Most executables will work. +The exceptions include programs that use +proprietary, ULTRIX-specific features (LAT, CI support, DECnet +support) and various system calls, +.Fn ioctl Ns 's , +or ULTRIX kernel +semantics that are difficult to emulate (e.g. ULTRIX packetfilter) or +buggy (e.g. ULTRIX +.Tn NIS ) . +.Pp +All ULTRIX executables are static, so no shared libraries are required +for ULTRIX compatibility. +However, ULTRIX is based on a +.Bx 4.3 +alpha release. +ULTRIX commands and libraries are often much older than their +.Nx +or even +.Tn SunOS 4.x +equivalents, and may require +incompatible configuration files. +.Sh SYSTEM CONFIGURATION FILES +Set up +.Pa resolv.conf +and +.Pa svc.conf +as below: +.Pp +.Bl -tag -width 123 -compact -offset indent +.It # mkdir -p /emul/ultrix/etc +.br +.It # cd /emul/ultrix/etc +.br +.It # egrep 'domain|nameserver' /etc/resolv.conf > ./resolv.conf +.br +.It # cp -p /usr/share/examples/emul/ultrix/etc/* ./ +.El +.Ss /etc/resolv.conf +The ULTRIX resolver library only understands +.Sy domain +and +.Sy nameserver +lines in +.Xr resolv.conf 5 . +You should create a copy of +.Pa /etc/resolv.conf +containing only those commands and put it in +.Pa /emul/ultrix/etc/resolv.conf . +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. +.Ss /etc/svc.conf +ULTRIX uses +.Pa /etc/svc.conf +to select an ordered search of +.Tn NIS , +Hesiod, +or local flat-file mappings. +You should create an +.Pa /emul/ultrix/etc/svc.conf +specifying either local files or bind (DNS) +lookups for all ULTRIX name services. +.Sh SEE ALSO +.Xr resolv.conf 5 +.Sh BUGS +RISC ULTRIX +.Tn NIS +(YP) is known to not work. +The ULTRIX +.Tn NIS +libraries have a consistent endian-ness bug. +ULTRIX +.Tn NIS +client will not inter-operate with the +.Nx +.Xr ypbind 8 +process. +The only workaround is to use +.Pa /etc/svc.conf +to disable +.Tn NIS +(YP). +.Pp +The ndbm hashed-password file used by ULTRIX are incompatible with the +db hashed-password file used by +.Nx . +There is no good solution for +this. +.Tn NIS +would be a good one, if ULTRIX +.Tn NIS +worked. +.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. +.Pp +A complete list of things which fail to work in ULTRIX compatibility +mode should be added here. diff --git a/static/netbsd/man8/creds_msdos.8 b/static/netbsd/man8/creds_msdos.8 new file mode 100644 index 00000000..7850bbd9 --- /dev/null +++ b/static/netbsd/man8/creds_msdos.8 @@ -0,0 +1,114 @@ +.\" $NetBSD: creds_msdos.8,v 1.6 2024/05/13 23:10:47 gutteridge Exp $ +.\" +.\" Copyright (c) 2019 Matthew R. Green +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd June 10, 2019 +.Dt CREDS_MSDOS 8 +.Os +.Sh NAME +.Nm creds_msdos +.Nd automatically add login credentials from MS-DOS partition +.Sh SYNOPSIS +.Nm +.Ar start +.Sh DESCRIPTION +The +.Nm +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. +.Pp +Typically, an installable image (such as +.Pa arm64.img ) +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 +.Pa creds.txt +for any credentials to be added to the system. +.Pp +The following list gives the supported options in the credentials files. +In all cases +.Ar user +is the username to be created, and the user will be added to the +.Ql wheel +group. +.Bl -tag -width Ic +.\" +.It Ic sshkeyfile Ar user Ar keyfile +Look for the +.Ar keyfile +in the MS-DOS boot partition and merge ssh keys from this file into user's +.Pa ~/.ssh/authorized_keys +file. +.\" +.It Ic sshkey Ar user Ar keystring +Add the +.Ar keystring +to the user's +.Pa ~/.ssh/authorized_keys +file. +.\" +.It Ic useraddpwhash Ar user Ar pwhash +Use +.Ar pwhash +as the users's password hash. +.\" +.It Ic useradd Ar user Ar password +Use +.Ar password +as the users's unencrypted raw password that will be hashed. +.Pp +This method is +.Em not recommended +as it leaves unencrypted passwords around until such time that the script runs. +If this method is used then the +.Pa creds.txt +file will be shredded and deleted using +.Ql rm -P +after the credentials are updated. +.El +.Sh FILES +.Pa /boot/creds.txt +.Sh SEE ALSO +.Xr pwhash 1 , +.Xr rm 1 , +.Xr ssh 1 , +.Xr ssh_config 5 , +.Xr mount_msdos 8 , +.Xr sshd 8 , +.Xr useradd 8 +.Sh HISTORY +The +.Nm +script appeared in +.Nx 9.0 . +.Sh AUTHORS +.An Matthew R. Green Aq Mt mrg@eterna23.net . diff --git a/static/netbsd/man8/diskless.8 b/static/netbsd/man8/diskless.8 new file mode 100644 index 00000000..4e1eb5f6 --- /dev/null +++ b/static/netbsd/man8/diskless.8 @@ -0,0 +1,898 @@ +.\" $NetBSD: diskless.8,v 1.35 2026/01/08 18:54:00 tsutsui Exp $ +.\" +.\" Copyright (c) 1994 Gordon W. Ross, Theo de Raadt +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd January 8, 2026 +.Dt DISKLESS 8 +.Os +.Sh NAME +.Nm diskless +.Nd booting a system over the network +.Sh DESCRIPTION +The ability to boot a system over the network is useful for +two kinds of systems: +.Bl -tag -width diskless +.It Em diskless +a system with no attached mass storage media to boot or run from +.Pq e.g. a network computer . +.It Em dataless +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. +.El +.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 +.Nx +are capable of being network booted. +.Pp +The protocols used to obtain a network address +.Pq e.g. an \&IP host address , +include, but are not limited to: +.Pp +.Bl -tag -width BOOTP -offset indent -compact +.It Tn RARP +Reverse Address Resolution Protocol +.Pq Tn ARP +.It Tn DHCP +Dynamic Host Configuration Protocol +.It Tn BOOTP +Bootstrap Protocol +.El +.Pp +This information can also be derived from non-volatile +.Tn RAM +or by a transform of a network interface +.Pq e.g. Tn Ethernet +.Tn MAC +address. +.Pp +The protocols used to load a +.Nx +kernel over a network include, but are not limited to: +.Pp +.Bl -tag -width TFTP -offset indent -compact +.It Tn TFTP +Trivial File Transfer Protocol +.It Tn NFS +.Tn Sun +Network File System +.It Tn RMP +.Tn \&HP +Remote Maintenance Protocol +.It Tn MOP +.Tn DEC +Maintenance Operations Protocol +.El +.Pp +Derivation of the filename of the secondary bootstrap program can +be done by a transform of a network interface +.Tn MAC +address +.Pq or other protocol address , +or provided by a server as with +.Tn BOOTP , +and +.Tn DHCP . +How this is done is platform dependent; see +.Xr boot 8 . +.Pp +The +.Nx +kernel doesn't care how it gets loaded and started. +The protocols used to boot +.Nx +can be completely different from the ones that +.Nx +uses operationally, i.e. you can netboot the system using +.Tn \&HP +.Tn RMP +and the +.Nx +kernel can use +.Tn \&IP +to communicate after bootstrap. +.Pp +There is no standard way to pass all the required information +from a boot loader to an operating system kernel, so the +.Nx +kernel usually has to recapitulate the same +.Pq or similar +protocol exchanges over the network to obtain a network address, +determine which servers to use, and so on. +.Nx +supports obtaining this information from +.Tn RARP , +.Tn BOOTP , +.Tn DHCP , +and +.Tn Sun RPC +.Qq bootparams . +See +.Xr options 4 +for a list of methods that can be compiled into a +.Nx +kernel. +.Pp +.Nx +only supports the +.Tn Sun +Network File System +.Pq Tn NFS +for mounting its root file system over a network. +.Nx +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. +.Pp +.Sy N.B. +.Tn DHCP +is essentially a series of extensions to +.Tn BOOTP ; +the +.Nx +.Xr dhcpd 8 +is capable of responding to both kinds of protocol requests. +.Pp +In the majority of configurations, network boot servers and clients +are attached to the same +.Tn LAN +so that broadcast queries from the clients can be heard by the servers. +Unless specially configured, routers block broadcasts from propagating from +.Tn LAN +to +.Tn LAN ; +some routers can be configured to +.Qq forward +broadcast +.Tn BOOTP +packets to another +.Tn LAN +attached to that router, which permits a server on that remote +.Tn LAN +to respond to the client's broadcast query. +.Sh OPERATION +When booting a system over the network, there are three +phases of interaction between client and server: +.Pp +.Bl -enum -compact +.It +The system firmware +.Pq or stage-1 bootstrap +loads a boot program. +.It +The boot program loads a +.Nx +kernel. +.It +The +.Nx +kernel performs an +.Tn NFS +mount of the root file system. +.El +.Pp +Each of these phases is described in further detail below. +.Ss 1. loading a boot program +In phase 1, the system firmware loads a boot program. +Firmware designs vary widely, +so this phase is inherently machine-specific. +Some examples: +.Pp +.Tn DEC +Alpha systems use +.Tn BOOTP +to determine the client's +.Tn \&IP +address and then use +.Tn TFTP +to load a secondary bootstrap program from the server and filename +specified in the +.Tn BOOTP +reply. +.Tn DEC +Alpha systems can also use +.Tn MOP +to load a program to run the system. +.Pp +.Tn Sun +systems use +.Tn RARP +to determine the client's +.Tn \&IP +address, transform that address to a hexadecimal string to form +the filename of the secondary boot program, and then use +.Tn TFTP +to download the boot program from the server that sent the +.Tn RARP +reply. +.Pp +.Tn \&HP +300-series systems use the +.Tn \&HP +.Tn RMP +to download a boot program. +.Pp +Typical personal computers may load a network boot program either +from diskette or from a +.Tn PROM +on a Network Interface Card +.Pq Tn NIC . +Some +.Tn BIOS Ns No \&es +support booting from a network interface. +.Ss 2. loading a kernel +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 +.Tn RARP +and +.Tn Sun RPC BOOTPARAMS +typically does the following: +.Pp +.Bl -enum -compact +.It +gets the client +.Tn \&IP +address using +.Tn RARP . +.It +gets the client name and server +.Tn \&IP +address by broadcasting an +.Tn RPC / BOOTPARAMS / WHOAMI +request with the client +.Tn \&IP +address. +.It +gets the server path for this client's +root using an +.Tn RPC / BOOTPARAMS / GETFILE +request with the client name. +.It +gets the root file handle by calling +.Xr mountd 8 +with the server path for the client root file system. +.It +gets the kernel file handle by calling +.Tn NFS +.Fn lookup +on the root file handle. +.It +loads the kernel using +.Tn NFS +read calls on the kernel file handle. +.It +transfers control to the kernel entry point. +.El +.Pp +A secondary bootstrap program that uses +.Tn BOOTP +and/or +.Tn DHCP +typically does the following: +.Pp +.Bl -enum -compact +.It +query for the client's bootstrap parameters. +The response must include the client's +.Tn \&IP +address, server's +.Tn \&IP +address, an +.Tn NFS +root path, and a filename to load the +.Nx +kernel from. +.It +gets the root file handle by calling +.Xr mountd 8 +with the server path for the client root file system. +.It +gets the kernel file handle by calling +.Tn NFS +.Fn lookup +on the root file handle. +.It +loads the kernel using +.Tn NFS +read calls on the kernel file handle. +.It +transfers control to the kernel entry point. +.El +.Ss 3. NFS mounting the root file system +In phase 3, the kernel performs an +.Tn 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. +.Pp +In general, the GENERIC kernel +.Xr config 1 +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 +.Nx +kernel can be compiled to use any of +.Tn BOOTP , +.Tn DHCP , +or +.Tn Sun RPC BOOTPARAMS ; +see +.Xr options 4 . +.Pp +The procedure typically used by the kernel is as follows: +.Pp +.Bl -enum -compact +.It +The kernel finds a boot server using the same procedures +as described above to determine the client's +.Tn \&IP +address, an +.Tn NFS +server, etc. +.It +The kernel gets the +.Tn NFS +file handle for root using the same procedure as described above. +.It +The kernel calls the +.Tn NFS +.Fn getattr +function to get the last-modified time of the root +directory, and uses it to check the system clock. +.El +.Sh SERVER CONFIGURATION +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 +.Xr inetd 8 , +and some must run independently, started from +.Pa /etc/rc ; +see +.Xr rc.conf 5 . +.Bl -column "Protocol" "rpc.bootparamd" "inetd.conf(5)" -offset indent +.It Sy Protocol Ta Sy Program Ta Sy Startup +.It RARP Ta rarpd Ta Xr rc.conf 5 +.It DHCP Ta dhcpd Ta Xr rc.conf 5 +.It BOOTP Ta bootpd Ta Xr inetd.conf 5 +.It TFTP Ta tftpd Ta Xr inetd.conf 5 +.It Sun RPC Ta rpcbind Ta Xr rc.conf 5 +.It Sun RPC Ta rpc.bootparamd Ta Xr rc.conf 5 +.It Sun NFS Ta mountd Ta Xr rc.conf 5 +.It Sun NFS Ta nfsiod Ta Xr rc.conf 5 +.It \&HP RMP Ta rbootd Ta Xr rc.conf 5 +.El +.Pp +.Sy N.B. +.Tn DHCP +is essentially a series of extensions to +.Tn BOOTP ; +the +.Nx +.Xr dhcpd 8 +is capable of responding to both kinds of protocol requests. +Since they both bind to the same +.Tn UDP +port, only one may be run on a given server. +.Pp +In the following examples, the client's hostname is +.Sy myclient ; +the server is +.Sy myserver , +and the addresses are all fictional. +In these examples +the hostnames may be Fully Qualified Domain Names +.Pq FQDN, e.g. Qq myclient.mydomain.com +provided that they are used consistently. +.Ss RARP +For clients that use +.Tn RARP +to obtain their +.Tn \&IP +address, +an entry must be added for each client to +.Pa /etc/ethers +with the client's +.Tn Ethernet +.Tn MAC +address and Internet hostname: +.Pp +.Bd -literal -offset indent -compact +8:0:20:7:c5:c7 myclient +.Ed +.Pp +This will be used by +.Xr rarpd 8 +to reply to queries from the clients. +There must be one entry per client system. +.Pp +A client system's +.Tn Ethernet +.Tn MAC +address is often printed on the system case, or on a chip on its +motherboard, or on the +.Tn NIC . +If not, +.Qq sniffing +the network with +.Xr tcpdump 8 +when the client is powered-on should reveal its +.Tn Ethernet +.Tn MAC +address. +.Pp +Each client system that uses +.Tn RARP +must have its own, unique +.Tn \&IP +address assigned to it. +Assign an +.Tn \&IP +address for myclient in your +.Pa /etc/hosts +file, or in the master file for your +.Tn DNS +zone. +For +.Pa /etc/hosts +the entry should look like: +.Pp +.Bd -literal -offset indent -compact +192.197.96.12 myclient +.Ed +.Ss DHCP/BOOTP +The +.Nx +.Tn DHCP +server +.Xr dhcpd 8 +was developed by the Internet Software Consortium +.Pq Lk http://www.isc.org/ "ISC" . +.Pp +.Tn DHCP +can provide a wide range of information to a requesting client; +the key data for bootstrapping a diskless client are: +.Pp +.Bl -enum -compact +.It +an +.Tn \&IP +address +.It +a subnet mask +.It +a +.Tn TFTP +server address for loading the secondary bootstrap and the +.Nx +kernel +.It +a filename of the secondary bootstrap +.It +an +.Tn NFS +server address for the client's file system +.It +the client's root file system path, to be +.Tn NFS +mounted. +.El +.Pp +An example for +.Pa /etc/dhcpd.conf +.Bd -literal -offset indent +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"; +} +.Ed +.Pp +That +.Sy host +declaration goes inside a +.Sy subnet +declaration, which gives parameters for all hosts on the subnet +that will be using +.Tn DHCP , +such as the +.Qq routers +.Pq the default route , +.Qq subnet-mask , +.Qq broadcast-address , +.Qq domain-name-servers , +etc. +See +.Xr dhcpd.conf 5 +for details. +In that example, +.Sy myclient +has an assigned IP address. +.Pp +The +.Tn DHCP +parameters required for network bootstrapping a system will vary +from platform to platform, as dictated by each system's firmware. +In particular, because +.Tn DHCP +is extensible, some hardware vendors have specified +.Tn DHCP +options to return information to requesting clients that are specific +to that platform. +Please see your platform's +.Xr boot 8 +for details. +.Ss TFTP +If booting a +.Tn Sun +system, or other system that expects to use +.Tn TFTP , +ensure that +.Xr inetd 8 +is configured to run +.Xr tftpd 8 . +The +.Xr tftpd 8 +server should be set up to serve the directory +.Pa /tftpboot . +.Pp +If booting a +.Tn SPARC +system, install a copy of the appropriate diskless secondary boot +loader +.Po +such as +.Pa /usr/mdec/boot +or +.Pa ofwboot.net +.Pc +in the +.Pa /tftpboot +directory. +Make a link such that the boot program is +accessible by a filename composed of the client's +.Tn \&IP +address in hexadecimal, a dot, and the architecture name +.Pq all upper case . +For example: +.Pp +.Bd -literal -offset indent -compact +# cd /tftpboot +# ln -s boot C0C5600C.SUN4 +.Ed +.Pp +For a +.Tn Sun-3 +or +.Tn UltraSPARC +system, the filename would be just C0C5600C +.Po +these systems' firmware does not append the architecture name +.Pc . +The name used is architecture dependent, it simply has to match +what the booting client's system firmware wishes it to be. +.Pp +If the client's system firmware fails to fetch the expected file, +.Xr tcpdump 8 +can be used to discover which filename the client is requesting. +Also, examination of +.Xr tftpd 8 +log entries +.Po +typically in +.Pa /var/log/messages +.Pc +should show whether the server is hearing the client system, and +what filename the client is asking for. +.Ss HP RMP +If booting an +.Tn HP +300-series system, ensure that +.Pa /etc/rbootd.conf +is configured properly to transfer the boot program to the client. +An entry might look like this: +.Pp +.Bd -literal -offset indent -compact +08:00:09:01:23:E6 SYS_UBOOT # myclient +.Ed +.Pp +The secondary bootstrap program for an +.Tn \&HP +300-series system +.Pa SYS_UBOOT +.Po +which may be called +.Pa uboot.lif +before installation +.Pc +must be installed in the directory +.Pa /usr/mdec/rbootd . +.Pp +See the +.Xr rbootd 8 +manual page for more information. +.Ss Sun RPC BOOTPARAMS +Add +.Sy myclient +to the bootparams database in +.Pa /etc/bootparams : +.Pp +.Bd -literal -offset indent -compact +myclient root=myserver:/export/myclient/root \\ + swap=myserver:/export/myclient/root/swap \\ + dump=myserver:/export/myclient/root/swap +.Ed +.Pp +and ensure that +.Xr rpc.bootparamd 8 +and +.Xr rpcbind 8 +are running. +Both +.Sy myclient +and +.Sy myserver +must have +.Tn \&IP +addresses in the +.Tn DNS +or +.Pa /etc/hosts . +.Ss Diskless Client File Systems +Build the swap file for +.Sy myclient +on the +.Tn NFS +server: +.Pp +.Bd -literal -offset indent -compact +# cd /export/myclient/root +# dd if=/dev/zero of=swap bs=16k count=1024 +.Ed +.Pp +This creates a 16 megabyte swap file. +.Pp +Populate +.Sy myclient Ns No 's +root file system on the +.Tn NFS +server. +How this is done depends on the client architecture and the version +of the +.Nx +distribution. +It can be as simple as copying and modifying the server's root +file system, or unpack a complete +.Nx +binary distribution for the appropriate platform. +.Pp +If the +.Tn NFS +server is going to support multiple different architectures +.Po +e.g. +.Tn Alpha , +.Tn PowerPC , +.Tn SPARC , +.Tn MIPS +.Pc , +then it is important to think carefully about how to lay out the +.Tn NFS +server's exported file systems, to share what can be shared +.Pq e.g. text files, configuration files, user home directories , +and separate that which is distinct to each architecture +.Pq e.g. binary executables, libraries . +.Ss NFS +Export the client-populated file systems on the +.Tn NFS +server in +.Pa /etc/exports : +.Pp +.Bd -literal -offset indent -compact +/usr -ro myclient +# for SunOS: +# /export/myclient -rw=myclient,root=myclient +# for NetBSD: +/export/myclient -maproot=root -alldirs myclient +.Ed +.Pp +If the server and client are of the same architecture, then the client +can share the server's +.Pa /usr +file system +.Pq as is done above . +If not, you must build a properly fleshed out +.Pa /usr +partition for the client in some other part of the server's +file system, to serve to the client. +.Pp +If your server is a +.Tn SPARC , +and your client a +.Tn Sun-3 , +you might create and fill +.Pa /export/usr.sun3 +and then use the following +.Pa /etc/exports +lines: +.Pp +.Bd -literal -offset indent -compact +/export/usr.sun3 -ro myclient +/export/myclient -rw=myclient,root=myclient +.Ed +.Pp +Of course, in either case you will have to have an +.Tn NFS +server running on the server side. +.Sh CLIENT CONFIGURATION +Copy and customize at least the following files in +.Pa /export/myclient/root : +.Pp +.Bd -literal -offset indent -compact +# cd /export/myclient/root/etc +# vi fstab +# cp /etc/hosts hosts +# echo 'hostname="myclient"' >> rc.conf +# echo "inet 192.197.96.12" > ifconfig.le0 +.Ed +.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 +.Nx . +.Pp +Correct the critical mount points and the swap file in the client's +.Pa /etc/fstab +.Po +which will be +.Pa /export/myclient/root/etc/fstab +.Pc +i.e. +.Pp +.Bd -literal -offset indent -compact +myserver:/export/myclient/root / nfs rw 0 0 +myserver:/usr /usr nfs rw 0 0 +/swap none swap sw 0 0 +.Ed +.Pp +Note, you +.Em must +specify the swap file in +.Pa /etc/fstab +or it will not be used! +See +.Xr swapctl 8 . +.Pp +It may be useful to set +.Dq flushroutes=NO +in +.Pa /etc/rc.conf +to avoid the default route supplied by the boot setup +disappearing mid-boot. +.Sh FILES +.Bl -tag -width /usr/mdec/rbootd -compact +.It Pa /etc/hosts +table of associated +.Tn \&IP +addresses and +.Tn \&IP +host names; see +.Xr hosts 5 +.It Pa /etc/ethers +table of associated +.Tn Ethernet +.Tn MAC +addresses and +.Tn \&IP +host names used by +.Xr rarpd 8 ; +see +.Xr ethers 5 +.It Pa /etc/bootparams +client root pathname and swap pathname; see +.Xr bootparams 5 +.It Pa /etc/exports +exported +.Tn NFS +mount points; see +.Xr exports 5 +.It Pa /etc/rbootd.conf +configuration file for +.Tn \&HP RMP ; +see +.Xr rbootd 8 +.It Pa /usr/mdec/rbootd +location of boot programs offered by +.Xr rbootd 8 +.It Pa /tftpboot +location of boot programs offered by +.Xr tftpd 8 +.El +.Sh SEE ALSO +.Xr bootparams 5 , +.Xr dhcpd.conf 5 , +.Xr ethers 5 , +.Xr exports 5 , +.Xr fstab 5 , +.Xr hosts 5 , +.Xr networks 5 , +.Xr boot 8 , +.Xr dhcpd 8 , +.Xr mopd 8 , +.Xr mountd 8 , +.Xr nfsd 8 , +.Xr rarpd 8 , +.Xr rbootd 8 , +.Xr reboot 8 , +.Xr rpc.bootparamd 8 , +.Xr tftpd 8 +.Rs +.%R RFC +.%N 903 +.%D June 1984 +.%T "Reverse Address Resolution Protocol" +.Re +.Rs +.%R RFC +.%N 906 +.%D June 1984 +.%T "Bootstrap Loading using TFTP" +.Re +.Rs +.%R RFC +.%N 951 +.%D September 1985 +.%T "Bootstrap Protocol" +.Re +.Rs +.%R RFC +.%N 1350 +.%D July 1992 +.%T "The TFTP Protocol (Revision 2)" +.Re +.Rs +.%R RFC +.%N 2131 +.%D March 1997 +.%T "Dynamic Host Configuration Protocol" +.Re +.Rs +.%R RFC +.%N 2132 +.%D March 1997 +.%T "DHCP Options and BOOTP Vendor Extensions" +.Re +.Pp +.Lk http://www.rfc-editor.org/ "RFC Editor" diff --git a/static/netbsd/man8/hpcboot.8 b/static/netbsd/man8/hpcboot.8 new file mode 100644 index 00000000..a426d568 --- /dev/null +++ b/static/netbsd/man8/hpcboot.8 @@ -0,0 +1,165 @@ +.\" $NetBSD: hpcboot.8,v 1.6 2019/12/23 17:31:54 reed Exp $ +.\" +.\" Copyright (c) 2004 Valeriy E. Ushakov +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Neither the name of the author nor the names of any +.\" contributors may be used to endorse or promote products derived +.\" from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd April 3, 2004 +.Dt HPCBOOT 8 +.Os +.Sh NAME +.Nm hpcboot +.Nd load and boot kernel from Windows\ CE +.Sh SYNOPSIS +.Nm hpcboot.exe +.Sh DESCRIPTION +.Nm +is a program that runs on Windows\ CE. +It loads and executes the specified +.Nx +kernel. +.Nm +supports hpcarm, hpcmips, and hpcsh ports. +.Pp +Click on the +.Dq Boot +button to start the boot process with selected options. +Click on the +.Dq Cancel +button to exit +.Nm . +.\" +.Ss Kernel Tab +.\" +On this tab you can select the kernel to boot and options to pass to +the kernel. +.Bl -tag -width "xx" +.It Directory +In this combobox you specify the +.Dq current +directory. +The kernel and miniroot image pathnames are taken to be relative to +this directory. +.Pp +.Nm +can load kernel and miniroot from FAT and UFS filesystems, and via +HTTP. +.\" FIXME: describe the syntax for each of the above +.It Kernel +In this text field you specify the name of the kernel to load. +Kernels compressed with +.Xr gzip 1 +are supported. +.It Model +Select your H/PC model in this combobox. +.It Root File System +This group of controls lets you specify the desired root file system +type. +You can select +.Xr wd 4 , +.Xr sd 4 , +.Xr md 4 , +and NFS root. +.Pp +If you select +.Xr md 4 +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 +.Xr gzip 1 +are supported. +.It Kernel Boot Flags +This group of controls is used to pass boot flags to the kernel. +.El +.\" +.Ss Option Tab +.\" +On this tab you can specify miscellaneous options that mostly control the +.Nm +program itself. +.Bl -tag -width "xx" +.It Auto Boot +If this option is selected +.Nm +will automatically boot +.Nx +after the specified timeout. +.It Reverse Video +Tells kernel if it should use the framebuffer in reverse video mode. +.It Pause Before Boot +If selected, a warning dialog will be presented +.Em before +anything is done, right after the +.Dq Boot +button is pressed. +.It Load Debug Info +This option currently does nothing. +.It Safety Message +If selected, a warning dialog will be presented +.Em after +the kernel has been loaded and prepared to be started. +This will be your last chance to cancel the boot. +.It Extra Kernel Options +In this text field you can specify additional options to pass to the +kernel. +.El +.\" +.Ss Console Tab +.\" +This tab gets its name from the big text area that +.Nm +uses as the +.Dq console +to report its progress. +.Bl -tag -width "xx" +.It Save To File +If checked, the progress log will be sent to the specified file instead. +.It Dq Checkboxes Anonymous +The row of 8 checkboxes controls debugging options for +.Nm +itself. +They control the bits of an internal variable, the leftmost checkbox +being the 7th bit. +.It Dq Buttons Anonymous +The buttons +.Dq a +to +.Dq d +control 4 +.Dq hooks +a developer might want to use during +.Nm +development. +.El +.Sh SEE ALSO +.Xr kloader 4 , +.Xr boot 8 +.Sh HISTORY +The +.Nm +utility first appeared in +.Nx 1.6 . +.Sh BUGS +.Nm +reads the entire kernel image at once, +and requires enough free area on the main memory. diff --git a/static/netbsd/man8/intro.8 b/static/netbsd/man8/intro.8 new file mode 100644 index 00000000..68de3f22 --- /dev/null +++ b/static/netbsd/man8/intro.8 @@ -0,0 +1,70 @@ +.\" $NetBSD: intro.8,v 1.10 2010/12/14 16:39:33 jruoho Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)intro.8 8.2 (Berkeley) 12/11/93 +.\" +.Dd December 14, 2010 +.Dt INTRO 8 +.Os +.Sh NAME +.Nm intro +.Nd introduction to system maintenance procedures and commands +.Sh DESCRIPTION +This section contains information related to system operation +and maintenance. +.Pp +It describes commands used to create new file systems +.Pq Xr newfs 8 , +verify the integrity of the file systems +.Pq Xr fsck 8 , +control disk usage +.Pq Xr edquota 8 , +maintain system backups +.Pq Xr dump 8 , +and recover files when disks die an untimely death +.Pq Xr restore 8 . +Network related services like +.Xr inetd 8 +and +.Xr ftpd 8 +are also described. +.Pp +A number of pages in this section describe general system management +topics. For example, the +.Xr diskless 8 +page describes how to boot a system over a network, and the +.Xr compat_linux 8 +page describes how to run Linux binaries on +.Nx +architectures that support it. +.Sh HISTORY +The +.Nm intro +section manual page appeared in +.Bx 4.2 . diff --git a/static/netbsd/man8/man8.acorn32/Makefile b/static/netbsd/man8/man8.acorn32/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.acorn32/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.acorn32/boot32.8 b/static/netbsd/man8/man8.acorn32/boot32.8 new file mode 100644 index 00000000..d0ec07ff --- /dev/null +++ b/static/netbsd/man8/man8.acorn32/boot32.8 @@ -0,0 +1,156 @@ +.\" $NetBSD: boot32.8,v 1.4 2016/04/30 14:32:22 jakllsch Exp $ +.\" +.\" Copyright (c) 2000, 2001 Ben Harris +.\" Copyright (c) 2004 Reinoud Zandijk +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd September 4, 2009 +.Dt BOOT32 8 acorn32 +.Os +.Sh NAME +.Nm boot32 +.Nd Bootloader for +.Nx Ns /acorn32 +.Sh SYNOPSIS +.Nm *boot32 +.Op Fl acdqsv +.Op Ar root=rootdir +.Op Ar file +.Sh DESCRIPTION +.Nm +is a program that runs under +.Tn RISC OS +and launches the +.Nx Ns /acorn32 +kernel. +It needs to be installed in a RISC OS filesystem and given file +type FFA (Module). +The kernel it is to load also needs to be stored in a +.Tn RISC OS +filesystem. +.Pp +It takes the following standard +.Nx +options, which set flags in the +.Va boothowto +variable in the booted kernel (see +.Xr boothowto 9 ) . +Not all flags may be effective. +.Bl -tag -width Fl +.It Fl a +.Pq Dv RB_ASKNAME +Cause the kernel to prompt the user for the name of the device containing the +root filesystem. +This also causes +.Nm +to prompt for the name of the kernel to be loaded. +.It Fl s +.Pq Dv RB_SINGLE +Cause the kernel to ask +.Nm init +to boot into single-user mode. +.It Fl d +.Pq Dv RB_KDB +Cause the kernel to enter the kernel debugger as soon as possible. +.It Fl c +.Pq Dv RB_USERCONF +Enter the in-kernel device configuration manager before attaching any +devices. +.It Fl q +.Pq Dv AB_QUIET +Cause the kernel to emit fewer messages than normal while starting up. +.It Fl v +.Pq Dv AB_VERBOSE +Cause the kernel to emit more messages than normal while starting up. +.El +.Pp +.Nm +attempts to load the kernel from the RISC OS file specified as +.Ar file , +or from +.Pa netbsd +if +.Ar file +is not specified. +The file must be an ELF image, and may have been compressed using +.Xr gzip 1 . +.Ss Use as a module +.Nm +is implemented as a RISC OS relocatable module. +It can be loaded into memory by running +.Ql *RMLoad boot32 . +After this, +.Nx +can be booted by running +.Ql *boot32 +as usual, but the command will be handled by the module. +.Pp +It should also be possible to arrange for +.Nm +to be loaded from ROM (e.g., from the ROM on an expansion card), in which case +.Nx +could be made to boot automatically by making +.Nm +the configured language using +.Ql *Configure Language . +.Ss Screen display +When it starts up, +.Nm +displays the number of 4 kilobyte memory pages it has been delegated by RISC-OS +and gives a summary about the memory map as reported by RISC-OS followed by a +table of physical memory ranges available to the bootloader. +All this information is mainly for bughunting booting problems. +.Pp +It then checks its internal structures and kicks out RISC-OS, relocates all +memory pages loaded in to their final destinations and kickstarts +.Nm . +.Sh FILES +.Bl -tag -width Pa +.It Pa /usr/mdec/boot32,ffa +The location of +.Nm +in the +.Nx +filesystem. +.El +.Sh SEE ALSO +.Xr gzip 1 , +.Xr reboot 2 , +.Xr ddb 4 , +.Xr userconf 4 , +.Xr init 8 , +.Xr boothowto 9 +.Sh HISTORY +.Nm +was introduced in +.Nx 1.6 +as a replacement for the original +.Nx Ns /arm32 +bootloader, which was written in BBC BASIC. +.Sh BUGS +.Nm +cannot load kernels from a +.Nx +filesystem. diff --git a/static/netbsd/man8/man8.acorn32/nbfs.8 b/static/netbsd/man8/man8.acorn32/nbfs.8 new file mode 100644 index 00000000..20ce9d29 --- /dev/null +++ b/static/netbsd/man8/man8.acorn32/nbfs.8 @@ -0,0 +1,82 @@ +.\" $NetBSD: nbfs.8,v 1.3 2017/02/17 22:30:27 christos Exp $ +.\" +.\" Copyright (c) 2006 Ben Harris +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt NBFS 8 acorn32 +.Os +.Sh NAME +.Nm nbfs +.Nd NetBSD boot filing system for RISC OS +.Sh SYNOPSIS +.Nm *NBFS +.Sh DESCRIPTION +.Nm +is a filing system, implemented as a RISC OS relocatable module, to allow +read-only access to +.Nx +file systems from RISC OS. +It supports reading FFSv1, FFSv2, LFSv1, and LVSv2 partitions from disks +supported by FileCore-based filing systems such as ADFS. +.Pp +Pathnames on +.Nm +follow RISC OS conventions, as described in the various RISC OS +.%T User Guides . +The underlying FileCore instance used by +.Nm +is selected by the filing system's special field, while the disk and +.Nx +partition are selected by the disk name. +Thus, to refer to the first +.Nx +partition of the first ADFS hard disk, one +would use +.Pa NBFS#ADFS::4a . +RISC OS file names are generated from +.Nx +file names by replacing +.Ql . +with +.Ql / . +Files whose names contain characters not allowed in RISC OS file names +are not accessible through +.Nm . +Thus, as a full example, the file +.Pa /etc/resolv.conf +on the partition mentioned above would be referred to as +.Pa NBFS#ADFS::4a.$.etc.resolv/conf . +.Sh LIMITATIONS +.Nm +is very limited. +.Sh SEE ALSO +.Xr acorn32/boot32 8 +.Rs +.%Q Acorn Computers Ltd +.%T RISC OS 3.7 User Guide +.%C Cambridge +.%D January 1997 +.Re diff --git a/static/netbsd/man8/man8.alpha/Makefile b/static/netbsd/man8/man8.alpha/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.alpha/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.alpha/boot.8 b/static/netbsd/man8/man8.alpha/boot.8 new file mode 100644 index 00000000..94fb1b40 --- /dev/null +++ b/static/netbsd/man8/man8.alpha/boot.8 @@ -0,0 +1,535 @@ +.\" $NetBSD: boot.8,v 1.17 2024/09/07 19:13:29 rillig Exp $ +.\" +.\" Copyright (c) 1999 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed for the +.\" NetBSD Project. See https://www.NetBSD.org/ for +.\" information about NetBSD. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" <<Id: LICENSE,v 1.2 2000/06/14 15:57:33 cgd Exp>> +.\" +.\" +.\" Copyright (c) 1990, 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_hp300.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd February 17, 2017 +.Dt BOOT 8 alpha +.Os +.Sh NAME +.Nm boot +.Nd Alpha system bootstrapping procedures +.Sh DESCRIPTION +.Tn DEC +.Tn Alpha +systems can have either of two different firmware systems: +.Tn ARC +.Pq a.k.a. Tn AlphaBIOS , +and +.Tn SRM . +Some +.Tn Alpha +systems have both in their flash +.Tn RAM +and can switch between them on command. +.Tn ARC +is used to bootstrap Microsoft Windows NT for +.Tn Alpha . +.Tn SRM +is used to bootstrap +.Tn OpenVMS +and +.Tn Ultrix . +.Nx +requires +.Tn SRM . +.Pp +.Tn SRM +can bootstrap from supported local storage devices, e.g., +.Tn IDE +disks or +.Tn CD-ROM +drives, +.Tn SCSI +disks or +.Tn CD-ROM +drives, and floppy drives. +.Tn SRM +can also network bootstrap via supported +.Tn Ethernet +interfaces, using +.Tn BOOTP +or +.Tn MOP . +The particular capabilities of +.Tn SRM +will vary from system to system. +.Pp +When +.Tn SRM +boots the system, it performs a Power On Self Test +.Pq Tn POST , +probes the system busses to identify devices, and initializes them. +.Tn SRM +includes an x86 instruction emulator in order to run the +.Tn BIOS +initialization routines found in the +.Tn PROM +of any video cards found. +In this way, most generic +.Tn PCI +video cards can work in +.Tn Alpha +systems that have +.Tn PCI +bus slots. +.Pp +.Tn SRM +then examines the state of one of several variables: +.Ev auto_action . +If the value of +.Ev auto_action +is +.Qq halt +then +.Tn SRM +will stop, print its prompt: +.Qq >>> +and wait for commands to be entered on the console. +If the value of +.Ev auto_action +is +.Qq boot +then +.Tn SRM +will automatically bootstrap the operating system specified by +various non-volatile environment variables. +.Pp +.Tn SRM +device names are not the same as in +.Nx , +e.g., +.Sy ewa0 +is a +.Tn DEC +.Qq tulip +.Tn Ethernet +interface, +.Sy dka0 +is a +.Tn SCSI +disk on a recognized controller, +.Sy dqa0 +is an +.Tn IDE +disk on a recognized controller. +The +.Ic show device +command will list all the devices that +.Tn SRM +can bootstrap from. +.Ss SRM Commands +.Tn SRM +is somewhat +.Ux Ns No -like +in that it incorporates a simple pipe and I/O redirection, +which allows command sequences like: +.Pp +.Bd -literal -offset indent +show config | more +show * | more +.Ed +.Pp +An essential but incomplete list of +.Tn SRM +commands follows: +.\" .Pp +.\" .Bl -tag -width "boot [-file filename] [-flags value] [-protocols enet_protocol] [device]" +.\" .It Ic boot Oo Fl file Ar filename Oc Oo Fl flags Ar value Oc Oo Fl protocols Ar enet_protocol Oc Op Ar device +.Pp +.Ic boot +.Op Fl file Ar filename +.Op Fl flags Ar value +.\" .Op Fl protocols Ar enet_protocol +.Op Ar device +.Pp +Boot an operating system. +The default arguments for this command are taken from the +.Tn SRM +environment variables: +.Pp +.Bl -tag -compact -width "boot_osflags" -offset indent +.It Ev boot_file +file name to bootstrap. +.It Ev boot_osflags +flags to pass to the secondary bootstrap program. +.It Ev bootdef_dev +default bootstrap device. +.El +.\" .It Ic help Op Ar command +.Pp +.Ic help Op Ar command +.Pp +Invoke the +.Tn SRM +help system. +.\" .It Ic set Ar variable Ar value +.Pp +.Ic init +.Pp +Reset the +.Tn SRM +console, and take actions as specified by +.Tn SRM +variables. +.Pp +.Ic set Ar variable Ar value Op Fl default +.Pp +Set an +.Tn SRM +variable, e.g., +.Bd -literal -offset indent +set auto_action boot +set bootdef_dev dka0 +set ewa0_mode auto +.Ed +.Pp +If the +.Fl default +flag is used, the variable will be set to its default value. +.\" .It Ic show Ar variable or subsystem +.Pp +.Ic show Ar variable or subsystem +.Pp +Show +.Tn SRM +variables and values, or show system state or configuration. +If a wildcard is used, then all matching +.Tn SRM +variables are shown, e.g., +.Pp +.Bl -tag -width "show device" -compact -offset indent +.It Ic show \&* +will display all +.Tn SRM +variables. +.It Ic show b* +will display all variables whose names begin with +.Em b . +.It Ic show config +will display the complete system configuration. +.It Ic show device +will display all bootable devices. +.It Ic show memory +will display the system's memory configuration. +.El +.\" .El +.Ss SRM Variables +.Bl -tag -width "ew*0_protocols" +.It Ev auto_action +What +.Tn SRM +will do at system startup or reset: +.Bl -tag -width boot +.It Ar boot +automatically bootstrap the operating system. +.It Ar halt +after +.Tn POST , +prompt the user on the console for commands to execute. +.El +.Pp +Some +.Tn Alpha +systems +.Pq e.g., Tn AlphaServer 800 +have a +.Qq halt +switch, which if set, will override the action of this variable, and cause +.Tn SRM +to stop after +.Tn POST +and prompt the user for commands to execute. +.It Ev bootdef_dev +The default bootstrap device, e.g., +.Sy dka0 , +.Sy dqa0 , +.Sy ewa0 . +The +.Ic show device +command will list the available and recognized bootable devices. +.It Ev boot_file +The file to bootstrap from; this is a null string by default. +.It Ev boot_osflags +The flag passed to the secondary bootstrap program, and the +.Nx +kernel: +.Bl -tag -width "XXXX" +.It Sy a +.Pq automatic +multi-user mode bootstrap. +.It Sy c +crash dump immediately after +.Xr autoconf 4 , +if the +.Nx +kernel is compiled with +.Dv DEBUG ; +See +.Xr options 4 . +.It Sy d +break into the debugger ASAP, if the +.Nx +kernel is compiled with +.Dv DDB +or +.Dv KGDB ; +See +.Xr options 4 . +.It Sy h +on a reboot request from the +.Nx +kernel, halt the system instead of rebooting. +.It Sy i +the +.Nx +secondary bootstrap program will stop and prompt for the +.Nx +kernel file name to bootstrap. +.It Sy n +the +.Nx +kernel will ask for the root file system's device, the kernel core +dump device, and the path to +.Xr init 8 . +.It Sy q +bootstrap quietly. +.It Sy s +single-user mode bootstrap. +.It Sy v +bootstrap verbosely. +.El +.Pp +These may be used in combinations that are not mutually exclusive. +These options are case-insensitive to be compatible with +.Tn DEC +operating systems. +.It Ev console +What type of console device +.Tn SRM +and +.Nx +will use: +.Bl -tag -width "graphics" +.It Ar graphics +use a video card for output, and a +.Tn PC +keyboard for input. +.It Ar serial +use the first serial port for console. +.El +.Pp +Just as with +.Tn Sun +systems, +.Tn Alpha +systems will use the first serial port as a console if there is no +keyboard plugged into the keyboard port, even if +.Ev console +is set to +.Qq graphics . +.It Ev ew*0_mode +The media and speed for +.Tn DEC +.Qq tulip +Ethernet interfaces +.Po +e.g., +.Tn DECchip +21040, 21140, 21143 +.Pc ; +possible values are: +.Ic auto +.Po +.Tn IEEE +802.3u +.Qq Nway +negotiation +.Pc , +.Ic BNC , +.Ic AUI , +.Ic Twisted-Pair , +.Ic FastFD +.Pq Fast Full Duplex . +.It Ev ew*0_protocols +The protocol to use when netbooting, i.e., +.Tn MOP +.Pq Maintenance Operations Protocol , +or +.Tn BOOTP +.Pq Bootstrap Protocol . +.Pp +The +.Tn Alpha +.Tn SRM +firmware is picky about +.Tn BOOTP +responses; the +.Xr dhcpd.conf 5 +on the server needs the +.Pp +.Bd -literal -offset indent +always-reply-rfc1048 on; +.Ed +.Pp +directive in the section for netbooting +.Tn Alpha +systems. +.It Ev os_type +This determines which system firmware will be used after the next +power-cycle, if both +.Tn ARC +and +.Tn SRM +are present in +.Tn Flash RAM . +This should be set to any of +.Qq Ux , +.Qq osf , +or +.Qq vms +to select the +.Tn SRM +console required for +.Nx . +.Tn OSF +refers to the Open Software Foundation. +.El +.Ss After bootstrap +Once the +.Nx Ns Tn /alpha +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. +.Pp +The proper way to shut the system down is with the +.Xr shutdown 8 +command. +.Pp +If the system crashes, it will enter the kernel debugger, +.Xr ddb 4 , +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. +.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 +.Xr savecore 8 +during the next bootstrap cycle), and after the dump is complete (successful +or not) the kernel will attempt a reboot. +.Sh FILES +.Bl -tag -width /usr/mdec/bootxx_cd9660 -compact +.It Pa /boot +.Nx +secondary bootstrap program +.Pq installed +.It Pa /netbsd +default +.Nx +system kernel +.It Pa /usr/mdec/bootxx_cd9660 +primary bootstrap for +.Dq cd9660 +.Pq Tn ISO 9660 +file system +.It Pa /usr/mdec/bootxx_ffs +primary bootstrap for +.Dq ffs +file system +.Pq Berkeley Fast File System +.It Pa /usr/mdec/boot +secondary bootstrap +.It Pa /usr/mdec/netboot +network bootstrap +.It Pa /usr/mdec/ustarboot +.Dq ustar +disk and tape bootstrap +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr alpha/mkbootimage 8 , +.Xr alpha/setnetbootinfo 8 , +.Xr diskless 8 , +.Xr init 8 , +.Xr installboot 8 , +.Xr rc 8 , +.Xr reboot 8 , +.Xr savecore 8 , +.Xr shutdown 8 +.Rs +.%T "Alpha Architecture Reference Manual Third Edition" +.%Q "Alpha Architecture Committee" +.%I "Digital Press" +.%D 1998 +.Re +.Sh BUGS +The device names used by +.Nx Ns Tn /alpha +and the +.Tn SRM Console +often have no relation to each other. diff --git a/static/netbsd/man8/man8.alpha/mkbootimage.8 b/static/netbsd/man8/man8.alpha/mkbootimage.8 new file mode 100644 index 00000000..83452a68 --- /dev/null +++ b/static/netbsd/man8/man8.alpha/mkbootimage.8 @@ -0,0 +1,132 @@ +.\" $NetBSD: mkbootimage.8,v 1.11 2024/09/07 19:13:29 rillig Exp $ +.\" +.\" Copyright (c) 1999 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed for the +.\" NetBSD Project. See https://www.NetBSD.org/ for +.\" information about NetBSD. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" <<Id: LICENSE,v 1.2 2000/06/14 15:57:33 cgd Exp>> +.\" +.Dd February 17, 2017 +.Dt MKBOOTIMAGE 8 alpha +.Os +.Sh NAME +.Nm mkbootimage +.Nd turn Alpha bootstrap programs into bootable images +.Sh SYNOPSIS +.Nm /usr/mdec/mkbootimage +.Op Fl nv +.Ar infile +.Op Ar outfile +.Sh DESCRIPTION +The +.Nm +utility creates bootable image files from +.Nx Ns Tn /alpha +bootstrap programs. +Bootable image files can be placed directly on disk or tape to +create bootable media which can be booted by the SRM console. +This is primarily useful for creating bootable tapes or disk sets +with the +.Pa /usr/mdec/ustarboot +bootstrap program, or for creating firmware upgrade media +using firmware upgrade programs. +.Pp +The bootstrap program +.Ar infile +is padded to a 512-byte boundary, has a properly formed +Alpha Boot Block prepended, and is written to the output file +.Ar outfile . +If no output file is specified, the result is written to +standard output. +.Pp +The +.Nm +utility does not install bootstrap programs to make +disks bootable. +To do that, use +.Xr installboot 8 . +Similarly, it is not necessary to use +.Nm +to create images to boot over the network; network-capable +bootstrap programs are usable without modification. +.Pp +The options recognized by +.Nm +are as follows: +.Bl -tag -width flag +.It Fl n +Do not actually write the result to the output file or +standard output. +.It Fl v +Print information about what +.Nm +is doing. +.El +.Sh FILES +.Bl -tag -width /usr/mdec/ustarboot -compact +.It Pa /usr/mdec/ustarboot +.Dq ustar +file system bootstrap program +.El +.Sh EXIT STATUS +.Ex -std mkbootimage +.Sh EXAMPLES +.Bd -literal -offset indent +mkbootimage as200_v5_8.exe as200_v5_8.exe.bootimage +.Ed +.Pp +Create a bootable image from the (firmware image) file +.Pa as200_v5_8.exe . +That bootable image could then be written to floppy, +disk, CD-ROM, or tape to create bootable firmware +update media. +.Bd -literal -offset indent +(mkbootimage /usr/mdec/ustarboot; tar cvf - netbsd) | \\ + dd of=/dev/rst0 +.Ed +.Pp +Make a bootable image from the bootstrap program +.Pa /usr/mdec/ustarboot , +concatenate it with a tar file containing a kernel, +and write the output to a tape. +This is an example of how to create a tape which boots a kernel. +.Sh SEE ALSO +.Xr alpha/boot 8 , +.Xr installboot 8 +.Sh HISTORY +The +.Nx Ns Tn /alpha +.Nm +command first appeared in +.Nx 1.4 . +.Sh AUTHORS +The +.Nm +utility was written by +.An Chris Demetriou . diff --git a/static/netbsd/man8/man8.alpha/setnetbootinfo.8 b/static/netbsd/man8/man8.alpha/setnetbootinfo.8 new file mode 100644 index 00000000..7e0a40f4 --- /dev/null +++ b/static/netbsd/man8/man8.alpha/setnetbootinfo.8 @@ -0,0 +1,151 @@ +.\" $NetBSD: setnetbootinfo.8,v 1.14 2024/09/07 19:13:29 rillig Exp $ +.\" +.\" Copyright (c) 1997, 1999 Christopher G. Demetriou +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed for the +.\" NetBSD Project. See https://www.NetBSD.org/ for +.\" information about NetBSD. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.\" <<Id: LICENSE,v 1.2 2000/06/14 15:57:33 cgd Exp>> +.\" +.Dd February 17, 2017 +.Dt SETNETBOOTINFO 8 alpha +.Os +.Sh NAME +.Nm setnetbootinfo +.Nd configure Alpha network bootstrap program +.Sh SYNOPSIS +.Nm /usr/mdec/setnetbootinfo +.Op Fl vf +.Op Fl o Ar outfile +.Oo +.Fl a Ar ether-address | Fl h Ar ether-host +.Oc +.Ar infile +.Nm /usr/mdec/setnetbootinfo +.Op Fl v +.Fl u o Ar outfile Ar infile +.Sh DESCRIPTION +The +.Nm setnetbootinfo +utility configures the +.Nx Ns Tn /alpha +network bootstrap program so +that it can be used to bootstrap systems with old firmware revisions. +.Pp +The +.Nx Ns Tn /alpha +network bootstrap program needs to have the ethernet +address of the interface being used to boot the system available when +querying other hosts on the network for bootstrapping information. +Alpha systems with old firmware revisions provide no way for +network bootstrap programs to determine the ethernet address of +the interface that they are booting from, and so the +.Nx Ns Tn /alpha +network bootstrap program must find that information in another way. +(Newer firmware revisions include the ethernet address in the name of +the device that is being booted from.) +The +.Nm +utility encodes an ethernet address (and other information) directly +into the network bootstrap program. +.Pp +The options recognized by +.Nm +are as follows: +.Bl -tag -width flag +.It Fl a Ar ether-address +Encode the given ethernet address into the network bootstrap program. +(This option and the +.Fl h +option are mutually exclusive.) +.It Fl f +Force the address information being encoded in the bootstrap +program to be used regardless of whether or not the bootstrap +program can get address information from the booting system's +firmware. +.It Fl h Ar ether-host +Encode the ethernet address of the specified host into the network +bootstrap program. The host's name is translated to an ethernet +address using the +.Xr ether_hostton 3 +function. +(This option and the +.Fl a +option are mutually exclusive.) +.It Fl o Ar outfile +Output the resulting bootstrap program into the file named by +.Ar outfile , +replacing it if it already exists. If the +.Fl o +flag is not specified, the output file name will be +the name of the input bootstrap program concatenated with a +period and the digits of the ethernet address being encoded. +For instance, if the input file is named +.Pa /usr/mdec/netboot +and is being configured to encode the ethernet address +.Li 08:00:2b:bd:5d:fd , +then the default output file name would be +.Pa /usr/mdec/netboot.08002bbd5dfd . +It is safe to set the output file name to be the same as the +input file name; the input file is read in its entirety before +the output file is modified. +.It Fl u +Remove configuration information from the specified network +bootstrap program. If this option is used, an output file name must be +specified with the +.Fl o +option, and neither the +.Fl a +or the +.Fl h +options may be specified. +.It Fl v +Verbose mode. +.El +.Sh FILES +.Bl -tag -width /usr/mdec/ustarboot -compact +.It Pa /usr/mdec/netboot +network bootstrap program +.El +.\" .Sh EXAMPLES +.\" There should be some examples of how to use +.\" .Nm setnetbootinfo . +.\" XXX +.Sh SEE ALSO +.Xr alpha/boot 8 , +.Xr bootpd 8 +.Sh HISTORY +The +.Nx Ns Tn /alpha +.Nm +command first appeared in +.Nx 1.3 . +.Sh AUTHORS +The +.Nm +utility was written by Chris Demetriou. diff --git a/static/netbsd/man8/man8.amiga/Makefile b/static/netbsd/man8/man8.amiga/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.amiga/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.amiga/binpatch.8 b/static/netbsd/man8/man8.amiga/binpatch.8 new file mode 100644 index 00000000..ae21473c --- /dev/null +++ b/static/netbsd/man8/man8.amiga/binpatch.8 @@ -0,0 +1,93 @@ +.\" $NetBSD: binpatch.8,v 1.7 2001/11/26 00:06:40 wiz Exp $ +.\" +.\" Copyright (c) 1994 Christian E. Hopps +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christian E. Hopps. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 2, 1994 +.Dt BINPATCH 8 amiga +.Os +.Sh NAME +.Nm binpatch +.Nd "examine and or modify initialized data in a binary file" +.Sh SYNOPSIS +.Nm binpatch +.Op Fl b | Fl w | Fl l +.Op Fl o Ar offset +.Fl s Ar symname +.Op Fl r Ar value +.Ar binfile +.Nm binpatch +.Op Fl b | Fl w | Fl l +.Op Fl o Ar offset +.Fl a Ar addr +.Op Fl r Ar value +.Ar binfile +.Sh DESCRIPTION +.Nm +is used to modify or examine the data associated with a symbol in a binary +file +.Ar binfile . +The flags +.Fl b , +.Fl w +and +.Fl l +specify the size of the data to be modified or examined +(byte, word and long respectively.) The +.Ar binfile +is scanned in search of the symbol +.Ar symname +(specified with the +.Fl s +flag) +If the symbol is found the current data and address are printed. Next if the +.Fl r +flag has been given, the current data is replaced with that of +.Ar value . +.Pp +If the second form is used the address +.Ar addr +specified with the +.Fl a +flag is used as a direct address into the data section of the binary and +no symbol search is performed. +.Pp +The +.Fl o +flag specifies an offset in byte, word or long +.Fl ( b , +.Fl w , +or +.Fl l ) +units from the given locator +.Fl ( s +or +.Fl a ) +for +.Nm +to perform its described actions. diff --git a/static/netbsd/man8/man8.amiga/boot.8 b/static/netbsd/man8/man8.amiga/boot.8 new file mode 100644 index 00000000..846cfc5d --- /dev/null +++ b/static/netbsd/man8/man8.amiga/boot.8 @@ -0,0 +1,267 @@ +.\" $NetBSD: boot.8,v 1.18 2021/02/26 10:44:31 wiz Exp $ +.\" +.\" Copyright (c) 1990, 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" From: +.\" @(#)boot_hp300.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd February 25, 2021 +.Dt BOOT 8 amiga +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.Sh DESCRIPTION +.Ss Power fail and crash recovery +When the +.Nx +kernel is booted normally (using one of the two methods discussed below), +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 +.Xr shutdown 8 +command. +.Pp +If the system crashes, it will enter the kernel debugger, +.Xr ddb 4 , +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 +.Xr savecore 8 +during the next boot cycle). +After the dump is complete (successful +or not), the system will attempt a reboot. +.Ss Booting NetBSD using the bootloader +When a bootable +.Nx +partition is created by means of HDTOOLBOX or another RDB editing program +and a bootblock has been copied there by +.Xr amiga/installboot 8 +and the boot priority of the +.Nx +partition is either the highest or the +.Nx +partition is selected by means of the boot menu, +the Amiga ROM will automatically start the +.Nx +bootloader. +By default it will, after a short timeout, load the kernel image +.Pa /netbsd +and attempt to boot it into multi-user mode. +This behaviour can be changed by +typing in an alternate command sequence. +The command line looks like: +.Bd -ragged -offset indent +.Ar kernel-path +.Op Fl abkpqsvACDS +.Op Fl c Ar model +.Op Fl m Ar memsize +.Op Fl n Ar memsegments +.Op Fl I Ar mask +.Ed +.Bl -tag -width flag +.It kernel-path +This gives you the opportunity to boot another kernel, say: +.Pa /netbsd.old . +The default is +.Pa /netbsd . +.It Fl a +Autoboot into multi-user mode (default). +.It Fl b +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl c Ar model +force machine +.Ar model . +Use 32000+(Qlogic chip revision) for the DraCo. +.It Fl k +Reserve the first 4M of fastmem. +.It Fl m Ar memsize +Force fastmem size to be +.Ar memsize +kBytes. +.It Fl n +maximum number of +.Ar segments +of memory to use, encoded as follows: 0 (default): 1 segment, 1: +2 segments, 2: 3 or more segments. +.It Fl p +Select kernel load segment by priority instead of size. +.It Fl q +Boot in quiet mode. +.It Fl s +Boot into single-user mode. +.It Fl v +Boot in verbose mode. +.It Fl A +Enable AGA display modes. +.It Fl C +Use the serial port as console. +.It Fl D +Enter the kernel debugger (best used with +.Fl S ) . +.It Fl I Ar mask +inhibit sync negotiation as follows: The +.Ar mask +is a bitmap expressed in C notation (e.g., 0xff) +with 4*8bits, each bit, if set to 1, disabling sync negotiation for +the corresponding target. +Note that this only applies to (some of the) +real SCSI busses, but not, e.g., to internal IDE. +The bytes are used up +from right to left by SCSI bus drivers using this convention. +.It Fl S +include kernel debug symbols (for use by +.Fl D ) . +.El +.Ss Booting NetBSD using the loadbsd program +When you want (or have to) start +.Nx +from AmigaOS, you have to use the +.Ic loadbsd +program that is supplied in the utils directory of the distribution. +The loadbsd command line specification is: +.Bd -ragged -offset indent +.Nm loadbsd +.Op Fl abkpqstvACDSZ +.Op Fl c Ar model +.Op Fl m Ar memsize +.Op Fl n Ar memsegments +.Op Fl I Ar mask +.Ar kernel-path +.Ed +.Pp +Description of options: +.Bl -tag -width flag +.It Fl a +Autoboot into multi-user mode. +.It Fl b +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl c +force machine model. +.It Fl k +Reserve the first 4M of fastmem. +.It Fl m +Force fastmem size to be +.Ar memsize +kBytes. +.It Fl n +maximum number of +.Ar segments +of memory to use, encoded as follows: 0 (default): 1 segment, 1: +2 segments, 2: 3 or more segments. +.It Fl p +Select kernel load segment by priority instead of size. +.It Fl q +Boot in quiet mode. +.It Fl s +Boot into single-user mode. +.It Fl t +Test loading of the kernel but don't start +.Nx . +.It Fl v +Boot in verbose mode. +.It Fl A +enable AGA display modes. +.It Fl C +Use the serial port as console +.It Fl D +Enter the kernel debugger (best used with +.Fl S ) . +.It Fl I Ar mask +inhibit sync negotiation as follows: The +.Ar mask +is a bitmap expressed in hexadecimal (e.g., ff) +with 4*8bits, each bit, if set to 1, disabling sync negotiation for +the corresponding target. +Note that this only applies to (some of the) +real SCSI busses, but not, e.g., to internal IDE. +The bytes are used up +from right to left by SCSI bus drivers using this convention. +.It Fl S +include kernel debug symbols (for use by +.Fl D ) . +.It Fl Z +Force load via chip memory. +Won't work if kernel is larger than the chip memory size or on the +DraCo. +.El +.Pp +Note: Because the loadbsd program can only read kernels from a AmigaOS +filesystem, the file +.Ar /netbsd +is often not the same as the actual kernel booted. +This can cause some programs to fail. +However, note that you can use third-party Berkeley +filesystems such as bffs to access the +.Nx +root partition from AmigaOS. +.Sh FILES +.Bl -tag -width /usr/mdec/bootxx_ffsv1 -compact +.It Pa /netbsd +system kernel +.It Pa /usr/mdec/bootxx_ffsv1 +RDB device primary boot block for FFSv1 (and ustarfs) +.It Pa /usr/mdec/bootxx_ffsv2 +RDB device primary boot block for FFSv2 +.It Pa /usr/mdec/bootxx_fd +floppy disk primary boot block +.It Pa /usr/mdec/boot.amiga +secondary bootstrap +.It Pa /boot.amiga +secondary bootstrap (installed) +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr amiga/installboot 8 , +.Xr fsck_ffs 8 , +.Xr newfs 8 , +.Xr savecore 8 , +.Xr shutdown 8 +.Sh BUGS +Due to code size restrictions, you can't currently use an old-style file +system (created with +.Xr newfs 8 +-O +or with +.Nx 0.9 ) +with the boot block. +You can use +.Ic loadbsd +to boot from AmigaOS, or upgrade the file system with +.Ar fsck_ffs -c 2 . diff --git a/static/netbsd/man8/man8.amiga/installboot.8 b/static/netbsd/man8/man8.amiga/installboot.8 new file mode 100644 index 00000000..d6fb5fe1 --- /dev/null +++ b/static/netbsd/man8/man8.amiga/installboot.8 @@ -0,0 +1,139 @@ +.\" $NetBSD: installboot.8,v 1.25 2021/02/26 10:44:31 wiz Exp $ +.\" +.\" Copyright (c) 1996 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Paul Kranenburg. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 25, 2021 +.Dt INSTALLBOOT 8 amiga +.Os +.Sh NAME +.Nm installboot +.Nd install a bootstrap on an FFS filesystem partition +.Sh SYNOPSIS +.Nm /usr/mdec/installboot +.Op Fl l Ar newcommandline +.Ar bootblock +.Ar device +.Sh DESCRIPTION +.Nm installboot +copies the bootblock to a bootable partition. +The +bootstrap is written into the bootblock area on the partition, right +in front of the superblock, and hence limited in size to +8192 bytes. +.Pp +The bootstrap resides in the first few blocks on the partition +.Pq as specified by Commodore-Amiga Inc. +The bootstrap is loaded into memory by the ROM from bootable devices: +RDB devices, where the partition is marked as bootable, or (not on the +DraCo) floppy disks in Amiga format (880K/1760k). +.Pp +In the presence of more than one bootable partition/floppy disk, the partition +is chosen by the bootpriority (from the RDB), which can be overridden by +the operator from the boot menu (on Amiga machines, hold down the outer +mouse buttons during boot; on DraCo machines, press the left mouse button +when prompted). +.Pp +On RDB devices, the whole bootblock is loaded by the ROM. +The number of +boot blocks in the RDB partition entry must be correct. +.Pp +On floppy disks, the ROM always loads the first two blocks (1024 bytes), +and the bootblock allocates memory and loads the whole bootblock on startup. +.Pp +After receiving control, the bootblock uses the stand-alone +filesystem code in +.Dq libsa.a +to load the kernel from the filesystem on the partition it was started from. +The code for the boot program can be found in +.Pa /usr/mdec/bootxx_fd +.Pq floppy disk code , +.Pa /usr/mdec/bootxx_ffsv1 +.Pq generic RDB disk code for FFSv1 , +or +.Pa /usr/mdec/bootxx_ffsv2 +.Pq generic RDB disk code for FFSv2 . +.Pp +The arguments are: +.Bl -tag -width bootblock +.It Fl l Ar newcommandline +Specify a different command line to replace the default. +.It Ar bootblock +The file containing the bootblock (normally /usr/mdec/bootxx_ffsv1 or +bootxx_ffsv2 for RDB devices). +.It Ar device +The name of the character special device specifying the partition on which the +bootstrap is to be installed. +.El +.Sh EXAMPLES +The following command will install the +boot program for FFSv1 in the bootblock area on +.Dq sd0a : +.Bd -literal -offset indent +installboot /usr/mdec/bootxx_ffsv1 /dev/rsd0a +.Ed +.Sh SEE ALSO +.Xr dd 1 , +.Xr amiga/boot 8 +.Sh HISTORY +The +.Nm +command first appeared in +.Nx 1.3 . +.Sh BUGS +If +.Nm +is accidentally used on the whole disk partition, the RDB will be overwritten, +making your system unusable after the next reboot. +.Pp +Some third-party accelerator boards are not autoconfiguring. +You won't be able to use their memory when booting from the bootblock +after a cold start. +.Pp +Some third-party disk controllers don't support bootblock booting. +.Pp +DraCo ROMs don't support bootblock booting from floppy disks. +.Pp +Most 68060 boards, unlike the DraCo, don't set the SysBase->AttnFlags +bit for the 68060 CPU (a patch program which is called during +AmigaOS startup does this). +You need to add +.Cd options BB060STUPIDROM +to your kernel to boot on such a machine. +.Pp +There is currently no easy way to edit the RDB from within +.Nx . +Therefore, you have to use HDTOOLBOX or a similar tool to +set the partition to bootable, "use custom bootblocks" and the number +of bootblocks to 16 (for bootxx_ffsv1 or bootxx_ffsv2) or 2 (for bootxx_fd), +at least the first time you install the bootblock. +.Pp +As normal +.Xr dd 1 +is used to install the bootblock, you can only install onto +your currently used root (or any other mounted) partition from single-user +mode, or while otherwise running in insecure mode. diff --git a/static/netbsd/man8/man8.atari/Makefile b/static/netbsd/man8/man8.atari/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.atari/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.atari/ahdilabel.8 b/static/netbsd/man8/man8.atari/ahdilabel.8 new file mode 100644 index 00000000..379f723f --- /dev/null +++ b/static/netbsd/man8/man8.atari/ahdilabel.8 @@ -0,0 +1,178 @@ +.\" $NetBSD: ahdilabel.8,v 1.14 2017/07/03 21:31:00 wiz Exp $ +.\" +.\" +.\" Copyright (c) 1999 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Julian Coleman and Leo Weppelman. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.Dd February 17, 2017 +.Dt AHDILABEL 8 atari +.Os +.Sh NAME +.Nm ahdilabel +.Nd modify AHDI partitions +.Sh SYNOPSIS +.Nm +.Ar disk +.Sh DESCRIPTION +.Nm +allows you to modify the AHDI partition table on a disk partitioned with +AHDI or an AHDI compatible formatter. The AHDI partition format is usually +only present on disks shared between +.Nx +and some other OS. The partition identifiers are used by +.Nx +as a guideline to emulate a disklabel on such a disk. +.Pp +.Nm +supports the following options: +.Pp +.Bl -tag -width disk +.It Ar disk +The name of the disk you want to edit. +.Nm +will first try to open a disk of this name. If this cannot +be opened, it will attempt to open +.Ar r Ns <disk> Ns Ar c . +Finally, if this also cannot be opened, it will attempt to open +.Ar /dev/r Ns <disk> Ns Ar c . +.El +.Pp +.Nm +will display information about the number of sectors, tracks +and sectors on the disk, as well as the current AHDI partition information. +It will then prompt for input. The input choices are: +.Pp +.Bl -tag -width a-p +.It Ar a-p +Modify a partition. You will be prompted for a partition id, root, start +and size. +.Nx +recognises the following partition id's: +.Pp +.Bl -tag -width "GEM or BGM" -compact +.It NBD +Partition is reserved for +.Nx . +This can be either a root or an user partition. The first NBD +partition on a disk will be mapped to +.Nx +partition letter +.Em a . +The following NBD partitions will be mapped from letter +.Em d +up. +The filesystem type is ffs by default. +.It SWP +The first SWP partition is mapped to partition +.Em b . +.It GEM or BGM +These partitions are mapped from +.Em d +up. The filesystem type is msdos. +.El +.Pp +The root, start and size parameters can be entered using sector, +cylinder/track/sector or megabyte notations. Whole numbers of cylinders can +be entered using the shorthand <cylinder>/. Likewise, whole numbers of tracks +can be entered using the shorthand <cylinder>/<track>/. Megabytes are entered +using the suffix +.Em M . +.Pp +The following can also be used to enter partition parameters: +.Pp +.Bl -tag -width "-N (start)" -compact +.It \-N (root) +Position the root sector for this partition immediately after partition N. +.It \-N (start) +Make this partition start after partition N (leaving a gap of 1 sector for a +root sector, if necessary). +.It \-N (size) +Make this partition end immediately before partition N. +.It -1 (size) +Make this partition extend to the end of the disk. +.El +.Pp +The sector holding the primary AHDI partition table only has space for four +partitions. Thus, if a disk has more than four partitions, the extra +partition information is held in auxiliary root sectors. There is one +auxiliary root for each additional partition (and also for the fourth +partition, if the disk has more than four partitions). +.It Ar r +Recalculate the root sectors. This will automatically assign auxiliary +root sectors if the disk has more than 4 partitions. The auxiliary root +sectors will be positioned in a default location preceding the relevant +partition. +.It Ar s +Show the current partition information. +.It Ar u +Toggle the unit display between sector and cylinder/track/sector notation. +.It Ar w +Write the AHDI partition table to the disk. +.It Ar z +Options for zero'ing the boot sector and bad sector lists. The default is to +preserve them both. +.It Ar q +Quit +.El +.Sh EXAMPLES +.Dl ahdilabel sd0 +Edit the AHDI label for disk sd0. +.Sh SEE ALSO +.Xr atari/bootpref 8 , +.Xr atari/installboot 8 , +.Xr disklabel 8 +.Sh HISTORY +The +.Nm +command first appeared in +.Nx 1.5 . +.Sh BUGS +The changes made to the AHDI partitions will become active on the next +.Em first open +of the disk. You are advised to use +.Nm +only on a disk without any mounted or otherwise active partitions. This +is not enforced by +.Nm . +.Pp +Because of way +.Nx +interprets AHDI partition tables to create the +.Nx +disklabel, the +.Nx +partition ordering may change if partitions labelled NBD are created or +removed. +.Pp +Creating an AHDI partition table on a disk that previously did not have +one will almost certainly overwrite any existing partition information +and/or data on that disk. This is especially the case if auxiliary root +sectors are needed for the AHDI partition table. +.Pp +As soon as a disk contains at least one NBD partition, you are allowed to +write +.Nx +disklabels and install bootstraps. diff --git a/static/netbsd/man8/man8.atari/binpatch.8 b/static/netbsd/man8/man8.atari/binpatch.8 new file mode 100644 index 00000000..4cf9b06b --- /dev/null +++ b/static/netbsd/man8/man8.atari/binpatch.8 @@ -0,0 +1,145 @@ +.\" $NetBSD: binpatch.8,v 1.8 2009/08/24 12:55:16 tsutsui Exp $ +.\" +.\" Copyright (c) 1994 Christian E. Hopps +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Christian E. Hopps. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd August 20, 2009 +.Dt BINPATCH 8 atari +.Os +.Sh NAME +.Nm binpatch +.Nd "examine and or modify initialized data in an executable binary" +.Sh SYNOPSIS +.Nm binpatch +.Op Fl b | Fl w | Fl l | Fl d +.Op Fl o Ar offset +.Op Fl T Ar saddr +.Fl s Ar symname +.Op Fl r Ar value +.Ar binfile +.Nm binpatch +.Op Fl b | Fl w | Fl l | Fl d +.Op Fl o Ar offset +.Op Fl T Ar saddr +.Fl a Ar addr +.Op Fl r Ar value +.Ar binfile +.Sh DESCRIPTION +.Nm +is used to modify or examine the data associated with a symbol in a binary +file +.Ar binfile . +.Pp +The flags +.Fl b , +.Fl w , +.Fl l , +and +.Fl d +specify the size of the data to be modified or examined. +.Fl b +is for 8bit +.Pq Li int8_t , +.Fl w +is for 16bit +.Pq Li int16_t , +.Fl l +is for 32bit +.Pq Li int32_t , +and +.Fl d +is for 64bit +.Pq Li int64_t +variables. +.Pp +The +.Ar binfile +is scanned in search of the symbol +.Ar symname +(specified with the +.Fl s +flag). +If the symbol is found the current data and address are printed. +.Pp +Next if the +.Fl r +flag has been given, the current data is replaced with that of +.Ar value . +.Pp +If the second form is used the address +.Ar addr +specified with the +.Fl a +flag is used as a direct address into the data section of the binary and +no symbol search is performed. +.Pp +The +.Fl o +flag specifies an offset in +.Li int8_t , +.Li int16_t , +.Li int32_t , +and +.Li int64_t +.Fl ( b , +.Fl w , +.Fl l , +or +.Fl d ) +units from the given locator +.Fl ( s +or +.Fl a ) +for +.Nm +to perform its described actions. +This might be useful to patch a member of array or structure. +.Pp +The +.Fl T +flag is used to specify the starting address of a.out binary text segment. +Ignored for other binary executable formats. +.Sh SEE ALSO +.Xr gdb 1 , +.Xr mdsetimage 8 +.Sh BUGS +The +.Nm +command doesn't check if size of specified symbol is the same as the +specified size by +.Fl b , +.Fl w , +.Fl l , +or +.Fl d +flag. +.Pp +The +.Nm +command doesn't check if specified address or symbol is a patchable variable +and it might corrupt the specified executable binary. diff --git a/static/netbsd/man8/man8.atari/boot.8 b/static/netbsd/man8/man8.atari/boot.8 new file mode 100644 index 00000000..918159f1 --- /dev/null +++ b/static/netbsd/man8/man8.atari/boot.8 @@ -0,0 +1,217 @@ +.\" $NetBSD: boot.8,v 1.14 2017/02/17 22:30:28 christos Exp $ +.\" +.\" Copyright (c) 1990, 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" From: +.\" @(#)boot_hp300.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd February 17, 2017 +.Dt BOOT 8 atari +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.Sh DESCRIPTION +.Ss Power fail and crash recovery +When the +.Nx +kernel is booted normally (using one of the two methods discussed below), +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 +.Xr shutdown 8 +command. +.Pp +If the system crashes, it will enter the kernel debugger, +.Xr ddb 4 , +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 +.Xr savecore 8 +during the next boot cycle). +After the dump is complete (successful or not), the system will +attempt a reboot. +.Ss Booting NetBSD using the bootloader +When a bootable +.Nx +partition is created by means of +.Xr atari/installboot 8 +and the boot-preference bit in the NVRAM is either invalid or set to +.Nx +, the Atari BIOS will automatically start the +.Nx +bootloader. +By default it will load the kernel image +.Pa /netbsd +and attempts to boot it into multi-user mode. +This behaviour can be changed by either keeping the +.Pa Alternate +or the +.Pa Right-Shift +key pressed during the boot. +When the +.Pa Alternate +key is pressed, the bootstrap is aborted, causing the BIOS +to continue scanning the disks for a bootable partition (this is compatible +with AHDI 3.0). +Pressing the +.Pa Right-Shift +key during the boot, causes the boot loader to enter the interactive mode. +In interactive mode, the command line looks like: +.Bd -ragged -offset indent +.Pp +.Op Ar OS-type +.Op Ar boot-path +.Op Ar boot-options +.Ed +.Pp +Each component of the command can be omitted in which case the defaults +indicated will be used. +.Bl -tag -width boot-options +.It OS-type : +.Bl -tag -compact -width ".netbsd (default)" +.It .netbsd (the default) +.It .linux +.It .asv +.It .tos +.El +.Pp +If something other than +.Pa .netbsd +is specified, control is returned to the BIOS with the boot preference set to +the selected type. +Due to limitations of the BIOS however, the search for +bootblocks is continued rather than restarted. +.It boot-path +This gives you the opportunity to boot another kernel, say: +.Pa /netbsd.old . +The default is +.Pa /netbsd +.It boot-options +These options are a subset of the +.Xr loadbsd 8 +options. +.Bl -tag -width flag -compact +.It Fl a +Boot into multi-user mode (the default) +.It Fl b +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl d +Enter the kernel debugger +.It Fl q +Boot in quiet mode +.It Fl v +Boot in verbose mode +.El +.El +.Ss Booting using the loadbsd program +When you want (or have to) start +.Nx +from GEM, you have to use the +.Xr loadbsd 8 +program that is supplied on the kernel-floppy. +The loadbsd command line specification is: +.Bd -ragged -offset indent +.Nm loadbsd +.Op Fl abdhqstvwDV +.Op Fl S Ar amount +.Op Fl T Ar amount +.Ar kernel-path +.Ed +.Pp +Description of options: +.Bl -tag -width flag +.It Fl a +Boot automatically into multi-user mode. +.It Fl b +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl d +Enter the kernel debugger after booting. +.It Fl h +Print a help screen that tries to explain the same options as mentioned +here. +.It Fl o Ar outputfile +Write all output to the file +.Ar outputfile . +.It Fl q +Boot in quiet mode. +.It Fl s +Tell +.Nx +only to use ST compatible RAM. +.It Fl t +Test loading of the kernel but don't start +.Nx . +.It Fl v +Boot in verbose mode. +.It Fl w +Wait for a keypress before exiting loadbsd. +This is useful when starting this program under GEM. +.It Fl D +Show debugging output while booting the kernel. +.It Fl S Ar amount +Set the amount of available ST compatible RAM in bytes. +Normally this +value is set automatically from the values initialized by the BIOS. +.It Fl T Ar amount +Set the amount of available TT compatible RAM in bytes. +Normally this +value is set automatically from the values initialized by the BIOS. +.It Fl V +Print the version of +.Xr loadbsd 8 +that you are using. +.It Ar kernel-path +This is a GEMDOS path specification of the kernel to boot. +.El +.Pp +Note: Because the loadbsd program can only read kernels from a GEMDOS +filesystem, the file +.Ar /netbsd +is usually not the same as the actual kernel booted. +This can cause some programs to fail. +.Sh FILES +.Bl -tag -width /netbsd -compact +.It Pa /netbsd +system kernel +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr savecore 8 , +.Xr shutdown 8 diff --git a/static/netbsd/man8/man8.atari/bootpref.8 b/static/netbsd/man8/man8.atari/bootpref.8 new file mode 100644 index 00000000..ab6b1368 --- /dev/null +++ b/static/netbsd/man8/man8.atari/bootpref.8 @@ -0,0 +1,197 @@ +.\" $NetBSD: bootpref.8,v 1.13 2017/02/17 22:30:28 christos Exp $ +.\" +.\" Copyright (c) 1998 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Julian Coleman. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt BOOTPREF 8 atari +.Os +.Sh NAME +.Nm bootpref +.Nd set NVRAM boot preference +.Sh SYNOPSIS +.Nm bootpref +.Op -v +.Op -b os +.Op -d delay +.Op -l lang +.Op -k kbd +.Op -s id +.Op -f fmt +.Op -1 +.Op -2 +.Op -e sep +.Op -c colours +.Op -n +.Op -p +.Op -t +.Op -v +.Op -4 +.Op -8 +.Op -o +.Op -O +.Op -x +.Op -X +.Op -i +.Op -I +.Sh DESCRIPTION +.Nm bootpref +views and sets the NVRAM boot preferences. +.Pp +The program options are: +.Bl -tag -width Ar +.It Fl V +verbose output (when setting preferences) +.It Fl b Ar netbsd +set the boot OS to +.Nx +.It Fl b Ar tos +set the boot OS to TOS +.It Fl b Ar linux +set the boot OS to Linux +.It Fl b Ar systemv +set the boot OS to System V +.It Fl b Ar none +set the boot OS to none +.It Fl d Ar delay +set the boot delay to +.Ar delay +seconds, where +.Ar delay +is a value between 0 and 255 +.It Fl l Ar english +set the language to English +.It Fl l Ar german +set the language to German +.It Fl l Ar french +set the language to French +.It Fl l Ar spanish +set the language to Spanish +.It Fl l Ar italian +set the language to Italian +.It Fl k Ar american +set the keyboard layout to American +.It Fl k Ar german +set the keyboard layout to German +.It Fl k Ar french +set the keyboard layout to French +.It Fl k Ar british +set the keyboard layout to British +.It Fl k Ar spanish +set the keyboard layout to Spanish +.It Fl k Ar italian +set the keyboard layout to Italian +.It Fl k Ar sw f +.It Fl k Ar swiss french +set the keyboard layout to Swiss (French) +.It Fl k Ar sw g +.It Fl k Ar swiss german +set the keyboard layout to Swiss (German) +.It Fl s Ar id +set the SCSI id to +.Ar id , +where +.Ar id +is a value between 0 and 7 +.It Fl f Ar mmddyy +.It Fl f Ar ddmmyy +.It Fl f Ar yymmdd +.It Fl f Ar yyddmm +set the date format +.It Fl 1 +set the date format to 12 hour clock +.It Fl 2 +set the date format to 24 hour clock +.It Fl e Ar sep +set the date format separator to +.Ar sep +.It Fl c Ar colours +set the number of +.Ar colours +- 2, 4, 16, 256 or 65535 +.It Fl n +set the video mode to +.Ar NTSC +.It Fl p +set the video mode to +.Ar PAL +.It Fl t +set the video mode to +.Ar TV +.It Fl v +set the video mode to +.Ar VGA +.It Fl 4 +set the video mode to +.Ar 40 columns +.It Fl 8 +set the video mode to +.Ar 80 columns +.It Fl o +set the video mode to +.Ar overscan +.It Fl O +set the video mode to +.Ar no overscan +.It Fl x +set the video mode to +.Ar ST compatibility +.It Fl X +set the video mode to +.Ar no ST compatibility +.It Fl i +set the video mode to +.Ar interlace +(TV), +.Ar double line +(VGA) +.It Fl I +set the video mode to +.Ar no interlace/double line +.El +.Pp +All strings can be specified by their shortest abbreviation +.Pp +If no parameters are specified, +.Nm bootpref +shows the current boot preferences. +.Sh SEE ALSO +.Xr atari/installboot 8 +.Sh HISTORY +The +.Nm +command first appeared in +.Nx 1.4 . +.Sh AUTHORS +.An Julian Coleman +.Sh BUGS +Setting the boot OS to +.Ar none +will cause the machine not to boot from the hard disk. +.Pp +The majority of the parameters are not used under +.Nx . diff --git a/static/netbsd/man8/man8.atari/installboot.8 b/static/netbsd/man8/man8.atari/installboot.8 new file mode 100644 index 00000000..6ed6c5ea --- /dev/null +++ b/static/netbsd/man8/man8.atari/installboot.8 @@ -0,0 +1,174 @@ +.\" $NetBSD: installboot.8,v 1.14 2017/02/17 22:30:28 christos Exp $ +.\" +.\" Copyright (c) 1996 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Paul Kranenburg. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt INSTALLBOOT 8 atari +.Os +.Sh NAME +.Nm installboot +.Nd install a bootstrap on an FFS filesystem partition +.Sh SYNOPSIS +.Nm /usr/mdec/installboot +.Op Fl Nmtuv +.Ar device +.Sh DESCRIPTION +.Nm +prepares the +.Pq physically +first partition on a device for boot-strapping from the TOS-ROM. +The bootstrap is written into the bootblock area on the partition, right +in front of the disk pack label, and hence limited in size to +.Dv LABELOFFSET +bytes. +A disk pack label should be created +.Po +see +.Xr disklabel 8 +.Pc +before installing the bootstrap. +.Pp +The bootstrap is split into three parts: a small first-stage program +that resides in the +.Pq physically +first 512 bytes on the device +.Pq as specified by Atari Corp. , +a second-stage program that immediately follows the first-stage +program, and a third-stage program that resides on the root filesystem. +The first-stage program is loaded into memory by the ROM. +After receiving control, it loads the second-stage program and the +disk label. +The second-stage boot program uses the stand-alone +filesystem code in +.Dq libsa.a +to load the third-stage boot program from the root-filesystem on the device. +The third-stage boot program then loads the kernel. +The prototype code for the first-stage boot program can be found in +.Pa /usr/mdec/std/fdboot +.Pq floppy disk code , +.Pa /usr/mdec/std/sdboot +.Pq SCSI disk code +and +.Pa /usr/mdec/std/wdboot +.Pq IDE disk code . +The second-stage boot program is stored in +.Pa /usr/mdec/std/bootxx . +and the third-stage boot program is stored in +.Pa /usr/mdec/std/boot.atari . +The boot code for Milan machines is different from the other machines and +the files for the Milan can be found in the directory +.Pa /usr/mdec/milan . +Note that the Milan uses the SCSI disk code for both SCSI and IDE disks. +.Pp +For backwards compatibility with the vendor specific AHDI disk +label, a\ special first-stage boot program is provided in +.Pa /usr/mdec/std/xxboot.ahdi . +Together with the general second-stage boot program, it is installed +in the AHDI partition where the +.Nx +disk label lives. +Furthermore, +the AHDI specifications require an additional bootstrap, which is +written into the AHDI root sector +.Pq disk block zero . +The prototype code for this AHDI compliant bootstrap can be found in +.Pa /usr/mdec/std/sdb00t.ahdi +and +.Pa /usr/mdec/std/wdb00t.ahdi , +or the equivalents in +.Pa /usr/mdec/milan . +.Pp +Perform the following steps to make a file system bootable: +.Bl -enum +.It +Copy the secondary bootstrap (either +.Pa /usr/mdec/std/boot.atari +or +.Pa /usr/mdec/milan/boot.atari ) +to the root directory of the target file system. +.It +Use +.Nm +to install the primary and secondary bootstrap programs +(from +.Pa /usr/mdec/std +or +.Pa /usr/mdec/milan ) +into the +.Ar filesystem . +.El +.Pp +The options are as follows: +.Bl -tag -width flag +.It Fl N +Do not actually write anything on the disk. +.It Fl m +Use Milan boot code. +.It Fl t +Number of tracks per cylinder (IDE disk). +.It Fl u +Number of sectors per track (IDE disk). +.It Fl v +Verbose mode. +.El +.Pp +The arguments are: +.Bl -tag -width device +.It Ar device +The name of the device on which the bootstrap is to be installed. +.El +.Sh EXAMPLES +The following command will install the first-stage and second-stage +boot programs in the bootblock area on +.Dq sd0c : +.Bd -literal -offset indent +installboot sd0 +.Ed +.Sh SEE ALSO +.Xr atari/bootpref 8 , +.Xr disklabel 8 +.Sh HISTORY +The +.Nm +command first appeared in +.Nx 1.1 +.Sh BUGS +.Nm +knows too much about kernel internal details, forcing it to +check the running kernel's release and revision. +.Pp +Because neither the floppy disk driver nor +.Xr disklabel 8 +are capable of creating a disk pack label on a floppy disk, +.Nm +has to create a\ fictitious label, that is not used by the kernel. +.Pp +Except for installation of the bootcode on floppy, +.Nm +automatically sets the boot preference in NVRAM to +.Nx . diff --git a/static/netbsd/man8/man8.cobalt/Makefile b/static/netbsd/man8/man8.cobalt/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.cobalt/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.cobalt/boot.8 b/static/netbsd/man8/man8.cobalt/boot.8 new file mode 100644 index 00000000..0af7d557 --- /dev/null +++ b/static/netbsd/man8/man8.cobalt/boot.8 @@ -0,0 +1,479 @@ +.\" $NetBSD: boot.8,v 1.11 2024/09/07 19:13:29 rillig Exp $ +.\" +.\" Copyright (c) 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This code is derived from software written and contributed +.\" to Berkeley by William Jolitz. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_i386.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd August 16, 2014 +.Dt BOOT 8 cobalt +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.Sh DESCRIPTION +.Tn Cobalt +Networks' MIPS-based Microservers +.Po +now known as +.Tn Sun +Server Appliances +.Pc +that can run +.Nx Ns /cobalt +can use any of the following boot procedures: +.Pp +.Bl -bullet +.It +bootstrap +.Nx +from disk using the standard +.Tn Cobalt +.Tn Firmware +boot sequence +.It +bootstrap +.Nx +from disk using the +.Nx +boot loader +.It +network bootstrap +.Nx +using the standard +.Tn Cobalt +.Tn Firmware +means from a +.Tn TCP/IP +.Tn LAN +with +.Tn DHCP +and +.Tn NFS . +.It +network bootstrap +.Nx +using the +.Nx +boot loader which can be loaded by the standard Cobalt Firmware +with DHCP and NFS. +.El +.Ss Power fail and crash recovery +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. +.Ss Cobalt Boot Sequence +The first program to take a control after reboot or at power-on is the +.Tn Cobalt +.Tn Firmware . +The +.Tn Firmware +can load a compressed kernel from disk, subject to a few limitations. +The +.Tn Firmware +expects the disk to contain DOS-style partition information with +the first partition being a boot one which is special in that it +should reside close to the beginning of the disk and must contain +an +.Tn ext2 +file system with a +.Pa boot +directory which is treated specially by the +.Tn Firmware . +The default sequence is pretty straightforward, the +.Tn Firmware +finds the boot partition, mounts the Ext2 file system from it and +tries to load a compressed kernel image from the +.Pa boot +directory. +The name of the kernel image differs from machine to machine and +this is the reason for having multiple copies of +.Nx +kernel installed under different names. +The following kernel image names are known to be in use by certain +.Tn Cobalt +flavors: +.Bd -unfilled -offset indent +.Pa /boot/vmlinuz.gz +.Pa /boot/vmlinux.gz +.Pa /boot/vmlinux-nfsroot.gz +.Pa /boot/vmlinux_RAQ.gz +.Pa /boot/vmlinux_raq-2800.gz +.Ed +.Pp +where +.Pa /boot +is the directory on the boot partition. +.Pp +The +.Tn Firmware +console provides the means to alter the default boot sequence and/or +to specify boot parameters. +Pressing +.Sq Aq space +right after the +.Tn Firmware +printed its greeting brings the +.Tn Firmware +console prompt and pressing +.Sq \&? +at the prompt prints a help screen with all commands supported by +the +.Tn Firmware . +For example, the +.Sq bfd +command can be used to boot a kernel image: +.Bd -unfilled -offset indent +Cobalt: bfd /boot/<kernel image> [options] +.Ed +.Pp +where +.Dq options +are the kernel options. +.Ss Bootstrap from disk using the standard Firmware sequence +The +.Tn Firmware +enters the standard boot sequence after reboot or at power-on when +no front-panel buttons are pressed and the +.Tn Firmware +console is not used to change the boot procedure. +At boot time, the +.Tn Firmware +checks the hardware, prints the banner and performs the standard +.Tn Cobalt +boot sequence. +There are a few culprits tightly connected to this boot method. +First of all, the kernel must be compressed. +Second, the +.Tn Firmware +enforces a hard restriction on the kernel size +.Po +it cannot exceed approximately 900,000/2,500,000 bytes +compressed/uncompressed +.Pc +resulting in a lock-up should this requirement not be fulfilled. +For +.Nx , +another pitfall is that the uncompressed kernel should be copied to +the root directory to make certain system binaries +.Po +such as e.g. netstat +.Pc +work, and the kernel images in the +.Pa boot +directory should always be in sync with the ones installed in the +root directory. +.Ss Bootstrap from disk using the NetBSD boot loader +The +.Nx +boot loader is an attempt to break through the limitations enforced +by the +.Tn Firmware +loader. +The main idea is to make the +.Tn Firmware +load the +.Nx +boot loader and let the latter take care of loading the kernel. +To achieve this goal, multiple copies of the boot loader are +installed in the +.Pa boot +directory on the boot partition, one copy per each kernel image +name the +.Tn Cobalt +.Tn Firmware +might look for. +The +.Nx +kernel is located in the root directory +.Po +usually +.Pa /dev/wd0a +.Pc +like it is on other platforms. +Once running, the boot loader prints a banner to the serial console +similar to the following: +.Bd -unfilled -offset indent +>> NetBSD/cobalt 5.0 Bootloader, Revision 0.9 [@0x80f00000] +>> (user@buildhost, builddate) +>> Model: Cobalt Qube 2 +>> Memory: 32768 k +>> PROM boot string: root=/dev/hda1 ro +Boot [wd0a:netbsd]: +Loading: wd0a:netbsd +3763776+312244 [216944+209676]=0x44b97c +Starting at 0x80001000 +.Ed +.Pp +The boot loader also prints a banner to the LCD panels as the following: +.Bd -unfilled -offset indent +.Nx Ns /cobalt +Bootloader +.Pp +Loading: +wd0a:netbsd +.Ed +.Ss Boot loader Options +It is possible to specify some options and boot devices on the boot loader +prompt: +.Pp +.Xo No boot [wd0a:netbsd]: +.Op Va device : Ns +.Op Va filename +.Op Fl acdmqsvxz +.Xc +.Pp +The default +.Va device +will be set to the disk that the boot loader was loaded from. +To boot from an alternate disk or partition, the full name of the device should +be given at the prompt. +.Va device +is of the form +.Va xdNx +where +.Va xd +is the device from which to boot, +.Va N +is the unit number, and +.Va x +is the partition letter of the NetBSD +.Xr disklabel 5 +in the NetBSD partition of the MBR partitions. +The +.Nx +boot loader recognizes FFS (both UFS1 and UFS2) and Linux Ext2fs. +.Pp +The following list of supported devices may vary from installation to +installation: +.Pp +.Bl -hang -compact +.It wd +IDE hard disks recognized by the +.Tn Firmware . +.El +.Pp +The default +.Va filename +is +.Pa netbsd ; +if the boot loader fails to successfully +open that image, it then tries +.Pa netbsd.gz +(expected to be a kernel image compressed by +.Xr gzip 1 ) , +followed by +.Pa netbsd , +.Pa netbsd.gz , +.Pa onetbsd , +.Pa onetbsd.gz , +.Pa netbsd.bak , +.Pa netbsd.bak.gz , +.Pa netbsd.old , +.Pa netbsd.old.gz , +.Pa netbsd.cobalt , +.Pa netbsd.cobalt.gz , +.Pa netbsd.elf , +and finally +.Pa netbsd.elf.gz . +Alternate system images can be loaded by just specifying the name +of the image, so it is always a good idea to have a copy of working kernel +in the +.Nx +root partition before trying a new kernel. +.Pp +Options are: +.Bl -tag -width xxx +.It Fl a +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl c +Bring the system up into the device configuration manager. +From here the device locators can be tuned to the hardware; see +.Xr userconf 4 . +.It Fl d +Bring the system up in debug mode. +Here it waits for a kernel debugger connect; see +.Xr ddb 4 . +.It Fl q +Boot the system in quiet mode. +.It Fl s +Bring the system up in single-user mode. +.It Fl v +Boot the system in verbose mode. +.El +.Pp +As the older version of the boot loader, it is also possible to specify +options to the boot loader by breaking into the +.Tn Firmware +and using the +.Dq bfd +command: +.Bd -unfilled -offset indent +Cobalt: bfd /boot/boot.gz [options] +.Ed +.Pp +The boot loader allows the following options: +.Bl -tag -width 04n -offset 04n +.It Ic nbsd= Oo Va device : Oc Ns Oo Va filename Oc Oo Fl acdqsv Oc +.Pp +The device, filename and options on the bfd prompt are same with the boot +loader. +.El +.Pp +It is also a good idea to have a small rescue kernel in the +.Pa boot +directory in the Ext2 partition for the Firmware boot. +In an emergency case, this will allow you to use the +.Tn Firmware +.Sq bfd +command to boot the rescue image: +.Bd -unfilled -offset indent +Cobalt: bfd /boot/netbsd.gz +.Ed +.Ss Network bootstrap using the standard Firmware sequence +The +.Tn Cobalt +.Tn Firmware +allows to boot a kernel over the network, with all the limitations +of the +.Tn Firmware +loader described above. +The simplest method is to break into the +.Tn Firmware +prompt and use +.Dq bfd +command to specify where to boot from: +.Bd -unfilled -offset indent +Cobalt: bfd /netbsd.gz nfsroot=/home/raq/root +.Ed +.Pp +The +.Tn Firmware +is picky about syntax and in general, so if things fail mysteriously, +try to conform to the conventions described above. +For netbooting, you need to NFS-export the directory given to +.Dq nfsroot= , +and the named kernel +.Pq Pa netbsd.gz +needs to be executable and in that directory. +You will also need to setup +.Xr dhcpd 8 . +Once the kernel is loaded with the command line values, the data +given via DHCP is used to mount the root file system. +Here is a known working DHCP entry: +.Bd -unfilled -offset indent +host raq { + hardware ethernet 0:10:e0:0:52:62; # raq MAC + fixed-address 10.0.0.15; # raq address + filename "/netbsd.gz"; # kernel name in root-path + option root-path "/home/raq/root"; # absolute dir on NFS server + server-name="10.0.0.3"; # IP of NFS server +} +.Ed +.Pp +Another option is to hold down the left and right cursor buttons +during power-on which executes the command +.Bd -unfilled -offset indent +bfd /boot/vmlinux.gz root=/dev/nfs nfsroot=/nfsroot, +.Ed +.Pp +resulting in a netboot. +On RaQ 1's, the default kernel name is +.Pa vmlinux_RAQ.gz +and on RaQ 2's, it is +.Pa vmlinux_raq-2800.gz . +.Ss Network bootstrap using the NetBSD boot loader +The idea here is the same with the bootstrap from disk using the NetBSD +boot loader. +Make the firmware load the NetBSD boot loader via network and +let the latter take care of loading the kernel even via network. +A simple method to load the NetBSD boot loader is to use the +.Dq bfd +command as well as booting the NetBSD kernel via network as described above: +.Bd -unfilled -offset indent +Cobalt: bfd /boot/boot.gz nfsroot=/home/raq/root +.Ed +.Pp +Note the boot loader binary needs to be +.Xr gzip 1 Ns -compressed . +Once the boot loader is successfully loaded it prints a banner as well as +booting from disk: +.Bd -unfilled -offset indent +>> NetBSD/cobalt 5.0 Bootloader, Revision 0.9 [@0x80f00000] +>> (user@buildhost, builddate) +>> Model: Cobalt Qube 2 +>> Memory: 32768 k +>> PROM boot string: root=/dev/nfs nfsroot=/nfsroot nfsaddrs=bootp +Boot [nfs:netbsd]: +Loading: nfs:netbsd +3763776+312244 [216944+209676]=0x44b97c +Starting at 0x80001000 +.Ed +.Pp +The boot loader load the NetBSD kernel via NFS which should be specified +by the DHCP configuration on the server. +Note the nfsroot option specified on the +.Dq bfd +prompt will be ignored by the +.Nx +boot loader so it's recommended to use the same directory on the +.Dq bfd +prompt and in the DHCP configuration. +.Sh FILES +.Bl -tag -width /usr/mdec/bootxx_fstype -compact +.It Pa /boot/boot.gz +boot program code loaded by the +.Tn Firmware +loader +.It Pa /boot/netbsd.gz +.Xr gzip 1 Ns -compressed +rescue system code +.It Pa /netbsd +system code +.It Pa /netbsd.gz +.Xr gzip 1 Ns -compressed +system code +.It Pa /usr/mdec/boot +master copy of the boot program (to be compressed and copied to /boot/boot.gz) +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr userconf 4 , +.Xr dhcpd.conf 5 , +.Xr dhcpd 8 , +.Xr fdisk 8 , +.Xr halt 8 , +.Xr reboot 8 , +.Xr shutdown 8 , +.Xr printf 9 +.Pp +.Lk https://www.NetBSD.org/docs/network/netboot/ diff --git a/static/netbsd/man8/man8.dreamcast/Makefile b/static/netbsd/man8/man8.dreamcast/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.dreamcast/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.dreamcast/boot.8 b/static/netbsd/man8/man8.dreamcast/boot.8 new file mode 100644 index 00000000..ffbfc8bb --- /dev/null +++ b/static/netbsd/man8/man8.dreamcast/boot.8 @@ -0,0 +1,59 @@ +.\" $NetBSD: boot.8,v 1.3 2008/04/30 13:10:57 martin Exp $ +.\" +.\" Copyright (c) 2003 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Marcus Comstedt. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd July 4, 2003 +.Dt BOOT 8 dreamcast +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.Sh DESCRIPTION +.Tn Dreamcast +consoles can only boot from the built-in +.Tn GD-ROM +drive. +Insert a bootable CD-R containing the +.Nx +kernel and turn on the power. +.Sh FILES +.Bl -tag -width /netbsd -compact +.It Pa /netbsd +system code +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr userconf 4 , +.Xr halt 8 , +.Xr reboot 8 , +.Xr shutdown 8 +.Sh HISTORY +The +.Nm +man page appeared in +.Nx 2.0 . diff --git a/static/netbsd/man8/man8.emips/Makefile b/static/netbsd/man8/man8.emips/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.emips/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.emips/boot.8 b/static/netbsd/man8/man8.emips/boot.8 new file mode 100644 index 00000000..05506cf0 --- /dev/null +++ b/static/netbsd/man8/man8.emips/boot.8 @@ -0,0 +1,96 @@ +.\" $NetBSD: boot.8,v 1.2 2013/10/05 08:20:22 skrll Exp $ +.\" +.\" Copyright (c) 2010 Microsoft Corp. +.\" Copyright (c) 2010 NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd October 5, 2013 +.Dt BOOT 8 emips +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.Sh DESCRIPTION +The +.Nx +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 the network +each time it is to be bootstrapped. +.Ss Power fail and crash recovery +FPGA devices lose their content upon loss of power and must be re-programmed. +This is usually accomplished via a JTAG cable programmer, or using a FLASH device. +Once the eMIPS processor has been programmed into the FPGA, the system will normally boot itself. +An automatic consistency check of the file systems will be performed, +and unless this fails, the system will resume multi-user operations. +.Sh Xilinx XUP, ML401 and ML402 +On these systems the kernel is normally read in from disk. The path used for automatic booting is +.Nm /netbsd , +but it can be overridden in the optional file +.Nm /boot.config +stored in the root of the disk filesystem. The user can also type a different filename and a combination of boot options. +.Sh BeSquare BEE3 +On this system there is no local disk and booting over the network is the only option. +Network boot can also be explicitly selected by hitting +.Nm f +at the boot loader prompt. +.Sh KERNEL ARGUMENTS +At the boot loader prompt, the user may boot +.Nx +with a number of options that are passed to the kernel unmodified. Parsing of these options is +defined in the file +.Nm /sys/boot_flag.h +Some additional flags are as follows. +.Bl -tag -width xxx -offset indent +.It Li e +Empty -- this argument requests +.Nx +to ignore all symbolic information and empty its initial symbol table. +.It Li n +Name -- Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Li N +NoName -- Do not prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +If the configured-in devices are present, use them. +.It Li s +Single -- Boot only to single-user mode. +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr halt 8 , +.Xr init 8 , +.Xr installboot 8 , +.Xr rc 8 , +.Xr reboot 8 , +.Xr savecore 8 , +.Xr shutdown 8 +.Sh HISTORY +The +.Nm +command is +.Ud . diff --git a/static/netbsd/man8/man8.evbarm/Makefile b/static/netbsd/man8/man8.evbarm/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.evbarm/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.evbarm/bootmini2440.8 b/static/netbsd/man8/man8.evbarm/bootmini2440.8 new file mode 100644 index 00000000..dbf816b0 --- /dev/null +++ b/static/netbsd/man8/man8.evbarm/bootmini2440.8 @@ -0,0 +1,179 @@ +.\" $NetBSD: bootmini2440.8,v 1.4 2012/06/02 14:04:34 njoly Exp $ +.\" +.\" Copyright (c) 2012 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Paul Fleischer <paul@xpg.dk>. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd January 31, 2012 +.Dt BOOTMINI2440 8 evbarm +.Os +.Sh NAME +.Nm bootmini2440 +.Nd bootloader for FriendlyARM MINI2440 evaluation board +.Sh DESCRIPTION +.Nm +is a program to load +.Tn ELF +.Nx +kernel, which works on top of +.Tn U-Boot . +It loads and executes a kernel from an SD memory card, or over +the network using the +.Tn NFS/TFTP +protocol. +.Pp +The +.Nm +bootloader can be loaded anywhere by +.Tn U-Boot , +although care should be taken that the bootloader can load the +.Nx +kernel without overwriting itself. +The kernel is, by default, made to be loaded at 0x30200000. +The recommended location for +.Nm +is 0x30A00000. +.Pp +.Nm +takes a number of arguments, which all are optional: +.Dl Ar mac=xx:xx:xx:xx:xx:xx Ar opt1 ... Ar optN Ar bootname +.Bl -tag -width xx +.It Va mac= +is used to set the MAC-address of the on-board DM9000 Ethernet +chip. +As Mini2440 has no EEPROM to store DM9000 MAC-address, this +is necessary in order to have a working Ethernet controller. +If this argument is left unspecified, a default value of 08:08:11:18:12:27 +is used. +.It Va opt1 ... Va optN +is one of single, kdb, ask, quiet, or verbose. +Their meaning is described in +.Xr boothowto 9 . +.It Va bootname +is one of the following: +.Pp +.Dl net: Ns Ar ip Ns : Ns Ar filename +.Dl net: Ns Ar filename +.Dl net: +.Dl tftp: Ns Ar filename +.Dl tftp: +.Dl ld0 Ns Ar p : Ns Ar filename +.Dl ld0 Ns Ar p : +.Pp +.Bl -tag -width xx +.It net: Ns Va ip Ns : Ns Va filename +use +.Tn DHCP +to determine own IP-address and load kernel specified by +.Ar filename +from the server specified by +.Ar ip +using +.Tn NFS . +.It net: Ns Ar filename +use +.Tn DHCP +to determine own IP-address and server IP-address. +Load kernel specified by +.Ar filename +from the server using +.Tn NFS . +.It net: +use +.Tn DHCP +to determine own IP-address, server IP-address, and kernel to load. +Load the kernel using +.Tn NFS . +.It tftp: Ns Ar filename +use +.Tn DHCP +to determine own IP-address and server IP-address. +Load kernel specified by +.Ar filename +from the server using +.Tn TFTP . +.It tftp: +use +.Tn DHCP +to determine own IP-address, server IP-address, and kernel to load. +Load kernel using +.Tn TFTP . +.It ld0 Ns Va p : Ns Va filename +load kernel from an SD card. +The kernel specified by +.Ar filename +is attempted loaded on the partition given by +.Ar p . +.It ld0 Ns Va p : +load kernel from an SD card. +The kernel will be loaded from the file +.Dq Pa netbsd +on the partition specified by +.Ar p . +.El +.El +.Sh EXAMPLES +.Ss Loading Nm +Use +.Tn U-Boot +to load +.Nm +at 0x30A00000 from an +.Tn NFS +share: +.Dl Uboot> nfs 30A00000 10.0.0.1:/srv/mini2440/bootmini2440 +.Ss Booting Nx +Load the kernel from an +.Tn NFS +share, overwriting the default MAC-address, and +booting into single user-mode: +.Dl Uboot> go 30A00000 single mac=08:08:11:20:22:30 net:10.0.0.1:/srv/mini2440/netbsd +.Pp +Load the kernel from an SD card, overwriting the default +MAC-address, and booting into single user-mode: +.Dl Uboot> go 30A00000 single mac=08:08:11:20:22:30 ld0a:netbsd +.Sh SEE ALSO +.Xr dhcpd 8 , +.Xr diskless 8 , +.Xr nfsd 8 , +.Xr tftpd 8 , +.Xr boothowto 9 +.Sh HISTORY +The +.Nx Ns Tn /evbarm +.Nm +first appeared in +.Nx 6.0 . +.Sh BUGS +.Nm +cannot currently function properly without +.Tn U-Boot +(or equivalent). +Although it performs clock and +.Tn UART +configuration, it cannot bootstrap itself from +.Tn NAND +flash. diff --git a/static/netbsd/man8/man8.hp300/Makefile b/static/netbsd/man8/man8.hp300/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.hp300/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.hp300/boot.8 b/static/netbsd/man8/man8.hp300/boot.8 new file mode 100644 index 00000000..e3009e43 --- /dev/null +++ b/static/netbsd/man8/man8.hp300/boot.8 @@ -0,0 +1,125 @@ +.\" $NetBSD: boot.8,v 1.9 2008/09/24 20:07:05 reed Exp $ +.\" +.\" Copyright (c) 1990, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_hp300.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd April 19, 1994 +.Dt BOOT 8 hp300 +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.Sh DESCRIPTION +.Ss Power fail and crash recovery +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. +.Pp +.Ss Cold starts +On an HP300, the boot procedure uses the boot ROM to load a boot program +from an +.Tn LIF +format directory at the beginning of an attached disk. +The +.Pa /usr/mdec +directory contains a disk boot programs which should be placed in a +new pack automatically by +.Xr newfs 8 +when the +.Dq a +partition file system on the pack is created. +.Pp +This +.Em boot +program +finds the corresponding file on the given device +.Pf ( Ar netbsd +by default), +loads that file into memory, +and starts the program at the entry address specified in the program header. +.Pp +The boot program can be interrupted by typing +.Sq \&^C +(ctrl-C). +This will force the boot program to interactively prompt for a system to boot. +If not interrupted, it will boot from the device from which the boot +program itself was loaded. +.Pp +The file specifications used for an interactive boot are of the form: +.Pp +.Dl device(unit, minor) +.Pp +where +.Ar device +is the type of the device to be searched, +.Ar unit +is 8 * the HP-IB number plus the unit number of the disk or tape, +and +.Ar minor +is the disk partition or tape file number. +Normal line editing characters can be used when typing the file specification. +Currently, +.Dq rd +and +.Dq sd +are the only valid +.Ar device +specifiers. +.Pp +For example, +to boot from the +.Sq a +file system of unit 0 on HP-IB 2, +type +.Ql rd(16, 0)netbsd +to the boot prompt. +For tapes, the minor device number gives a file offset. +.Pp +In an emergency, the bootstrap methods described in the paper +.%T Installing 4.3bsd on the HP300 +can be used to boot from a distribution tape. +.Sh FILES +.Bl -tag -width /usr/mdec/installboot -compact +.It Pa /netbsd +system code +.It Pa /usr/mdec/bootrd +.Tn LIF +format boot block +.It Pa /usr/mdec/installboot +program to install boot blocks +.El +.Sh SEE ALSO +.Xr halt 8 , +.Xr reboot 8 , +.Xr shutdown 8 diff --git a/static/netbsd/man8/man8.hp300/format.8 b/static/netbsd/man8/man8.hp300/format.8 new file mode 100644 index 00000000..13ef53fd --- /dev/null +++ b/static/netbsd/man8/man8.hp300/format.8 @@ -0,0 +1,63 @@ +.\" $NetBSD: format.8,v 1.8 2003/08/07 10:31:24 agc Exp $ +.\" +.\" Copyright (c) 1990, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)format.8 8.2 (Berkeley) 1/12/94 +.\" +.Dd January 12, 1994 +.Dt FORMAT 8 hp300 +.Os +.Sh NAME +.Nm format +.Nd how to format disks and tapes +.Sh DESCRIPTION +Currently, there are no +.Dq native +.Nx +media formatting utilities. +Formatting of both disks and cartridge tapes must be done either +stand-alone or under +.Tn HP-UX +using the +.Em mediainit +utility distributed by +.Tn HP . +Note that +.Tn HP Ns -brand +cartridge tapes come pre-formatted, and +.Tn HP +disks are supposed to. +.Sh HISTORY +The +.Nm format +utility first appeared in +.Bx 4.4 . diff --git a/static/netbsd/man8/man8.hpcarm/Makefile b/static/netbsd/man8/man8.hpcarm/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.hpcarm/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.hpcarm/boot.8 b/static/netbsd/man8/man8.hpcarm/boot.8 new file mode 100644 index 00000000..cc75ec5a --- /dev/null +++ b/static/netbsd/man8/man8.hpcarm/boot.8 @@ -0,0 +1,105 @@ +.\" $NetBSD: boot.8,v 1.1 2006/01/13 23:30:13 peter Exp $ +.\" +.\" Copyright (c) 2004 Valeriy E. Ushakov +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Neither the name of the author nor the names of any +.\" contributors may be used to endorse or promote products derived +.\" from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd January 13, 2006 +.Dt BOOT 8 hpcarm +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.Sh DESCRIPTION +Windows\ CE machines with +.Tn StrongARM +CPUs use the +.Xr hpcboot 8 +program to boot +.Nx . +.Ss Power fail and crash recovery +.\" +Unfortunately, +.Nx +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 +.Nx +manually using +.Xr hpcboot 8 . +.Pp +Once +.Nx +starts, an automatic consistency check of the file systems will be +performed, and unless this fails, the system will resume multi-user +operations. +.\" +.Ss Cold starts +.\" +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. +.Pp +You can't boot +.Nx +directly, skipping Windows\ CE. +The +.Nx +bootloader, +.Xr hpcboot 8 , +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 +.Nx +is halted the machine will go through the cold reset and will reboot +into Windows\ CE. +.\" +.Ss Normal Operation +.\" +Please, refer to the +.Xr hpcboot 8 +manual page. +.Sh FILES +.\" +.Bl -tag -width hpcboot.exe -compact +.It Pa hpcboot.exe +bootloader program for Windows\ CE +.El +.\" +.Sh SEE ALSO +.\" +.Xr hpcboot 8 +.\" +.Sh BUGS +.\" +There is no general way to launch the bootloader automatically, as +only a few Windows\ CE machines provide an +.Dq auto run +mechanism. +.Pp +This port doesn't support +.Xr kloader 4 , +which means that when the system is rebooted, it goes back to Windows\ CE. diff --git a/static/netbsd/man8/man8.hpcmips/Makefile b/static/netbsd/man8/man8.hpcmips/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.hpcmips/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.hpcmips/boot.8 b/static/netbsd/man8/man8.hpcmips/boot.8 new file mode 100644 index 00000000..13f00fc0 --- /dev/null +++ b/static/netbsd/man8/man8.hpcmips/boot.8 @@ -0,0 +1,80 @@ +.\" $NetBSD: boot.8,v 1.5 2017/02/17 22:30:28 christos Exp $ +.Dd February 17, 2017 +.Dt BOOT 8 hpcmips +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.Sh DESCRIPTION +.\" +.Ss Power fail and crash recovery +.\" +Unfortunately, on most machines, the system can't reboot itself +at power-up or after crashes. +You might have to restart the system manually. +Once the system starts, an automatic consistency check of the file systems +will be performed, +and unless this fails, the system will resume multi-user operations. +.\" +.Ss Cold starts +.\" +Typical MIPS based Windows CE Handheld machines +attempt to boot Windows CE operating system in its own boot ROM. +You can't boot the +.Nx +directly skipping Windows CE. +The +.Nx +bootloaders are provided as application programs on Windows CE instead. +You can choose +.Xr hpcmips/pbsdboot 8 +or +.Xr hpcboot 8 . +Though the bootloaders are application programs, +they blow away the entire Windows CE OS and its settings +when the kernel boots successfully. +.\" +.Ss Normal Operation +.\" +Once running, a familiar window will appear. +You can choose the machine type, kernel file location and kernel boot +options with a GUI and push the button named +.Dq Li [boot] +to boot +.Nx . +.\" +.Ss Automatic mode +.\" +The bootloaders have an +.Dq Li auto boot +option. +If you enable this option, the specified kernel will be loaded +automatically after a countdown. +.\" +.Sh FILES +.\" +.Bl -tag -width pbsdboot1.exe -compact +.It Pa /netbsd +system kernel +.It Pa /netbsd.gz +gzip-compressed kernel +.It Pa pbsdboot1.exe +bootloader executable file for Windows CE version 1.01 +.It Pa pbsdboot.exe +bootloader executable file for Windows CE +.It Pa hpcboot.exe +new bootloader executable file for Windows CE +.El +.\" +.Sh SEE ALSO +.\" +.Xr kloader 4 , +.Xr hpcboot 8 , +.Xr hpcmips/pbsdboot 8 +.\" +.Sh BUGS +.\" +There is no general way to launch a bootloader automatically +while a few Windows CE machine provide an +.Dq auto run +mechanism. diff --git a/static/netbsd/man8/man8.hpcmips/pbsdboot.8 b/static/netbsd/man8/man8.hpcmips/pbsdboot.8 new file mode 100644 index 00000000..e3d88758 --- /dev/null +++ b/static/netbsd/man8/man8.hpcmips/pbsdboot.8 @@ -0,0 +1,61 @@ +.\" $NetBSD: pbsdboot.8,v 1.5 2001/12/26 01:30:52 wiz Exp $ +.Dd August 25, 2000 +.Dt PBSDBOOT 8 hpcmips +.Os +.Sh NAME +.Nm pbsdboot +.Nd load and boot NetBSD/hpcmips kernel from Windows CE +.Sh SYNOPSIS +.Nm pbsdboot.exe +.Sh DESCRIPTION +.Nm +is a program runs on Windows CE. +It loads and executes the specified +.Nx Ns Tn /netbsd +kernel. +.Pp +The menu options (for +.Nm +itself) are as follows: +.Bl -tag -width FrameXbuffer +.It kernel +Select Kernel Path. +.It Frame buffer +Select Frame Buffer type. +.It Option +option for pass kernel. +.El +.Pp +The options for +.Nx +kernel are as follows: +.Bl -tag -width flag +.It Fl d +break into the kernel debugger. +.It Fl m +use miniroot in memory. +.It Fl s +single user mode. +.It Fl h +use serial console.check also serial port on.and connect your terminal with 9600bps,8bit,non-parity,VT100 mode. +.It Fl a +ask for name:kernel ask root/dump device,filesystem. +.It Fl b=DEV +change boot device to DEV(wd0,sd0,nfs,etc) +.El +.Sh FILES +.Bl -tag -width /msdos/pbsdboot.exe -compact +.It Pa /msdos/pbsdboot.exe +You will find this program Windows CE readable disk partition. +.El +.Sh SEE ALSO +.Xr reboot 2 +.Sh HISTORY +The +.Nm +utility first appeared in +.Nx 1.5 . +.Sh BUGS +.Nm +reads the entire kernel image at once, +and requires enough free area on the main memory. diff --git a/static/netbsd/man8/man8.hpcsh/Makefile b/static/netbsd/man8/man8.hpcsh/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.hpcsh/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.hpcsh/boot.8 b/static/netbsd/man8/man8.hpcsh/boot.8 new file mode 100644 index 00000000..00c4021e --- /dev/null +++ b/static/netbsd/man8/man8.hpcsh/boot.8 @@ -0,0 +1,107 @@ +.\" $NetBSD: boot.8,v 1.4 2006/01/13 23:22:29 peter Exp $ +.\" +.\" Copyright (c) 2004 Valeriy E. Ushakov +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Neither the name of the author nor the names of any +.\" contributors may be used to endorse or promote products derived +.\" from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd April 3, 2004 +.Dt BOOT 8 hpcsh +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.Sh DESCRIPTION +Windows\ CE machines with +.Tn SuperH +CPUs use the +.Xr hpcboot 8 +program to boot +.Nx . +Once running, +.Nx +can reboot itself if +.Xr kloader 4 +is configured in the kernel. +.Ss Power fail and crash recovery +.\" +Unfortunately, +.Nx +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 +.Nx +manually using +.Xr hpcboot 8 . +.Pp +Once +.Nx +starts, an automatic consistency check of the file systems will be +performed, and unless this fails, the system will resume multi-user +operations. +.\" +.Ss Cold starts +.\" +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. +.Pp +You can't boot +.Nx +directly, skipping Windows\ CE. +The +.Nx +bootloader, +.Xr hpcboot 8 , +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 +.Nx +is halted the machine will go through the cold reset and will reboot +into Windows\ CE. +.\" +.Ss Normal Operation +.\" +Please, refer to the +.Xr hpcboot 8 +manual page. +.Sh FILES +.\" +.Bl -tag -width hpcboot.exe -compact +.It Pa hpcboot.exe +bootloader program for Windows\ CE +.El +.\" +.Sh SEE ALSO +.\" +.Xr kloader 4 , +.Xr hpcboot 8 +.\" +.Sh BUGS +.\" +There is no general way to launch the bootloader automatically, as +only a few Windows\ CE machines provide an +.Dq auto run +mechanism. diff --git a/static/netbsd/man8/man8.hppa/Makefile b/static/netbsd/man8/man8.hppa/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.hppa/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.hppa/boot.8 b/static/netbsd/man8/man8.hppa/boot.8 new file mode 100644 index 00000000..abfddd5c --- /dev/null +++ b/static/netbsd/man8/man8.hppa/boot.8 @@ -0,0 +1,339 @@ +.\" $NetBSD: boot.8,v 1.2 2017/07/03 21:31:00 wiz Exp $ +.\" +.\" $OpenBSD: boot_hppa.8,v 1.11 2004/05/25 22:27:44 jmc Exp $ +.\" +.\" Copyright (c) 2002, Miodrag Vallat. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd July 27, 2004 +.Dt BOOT 8 hppa +.Os +.Sh NAME +.Nm boot +.Nd hppa system bootstrapping procedures +.Sh DESCRIPTION +.Ss System starts +When powered on, after a panic, or if the system is rebooted via +.Xr reboot 8 +or +.Xr shutdown 8 , +the hppa firmware +.Pq Dq PDC +will proceed to its initialization, and will boot an operating system +if autoboot is enabled. +.\" +.Ss Boot process description +System boot blocks are provided as a +.Dq LIF +.Pq Logical Interchange Format +archive, either on a disk device, or via the network, using the +.Em bootp +or +.Em rboot +protocols, depending on the PDC version. +.\" A small +.\" .Xr mkboot 8 +.\" utility +.\" is provided for combining primary boot and a number +.\" of images (OS kernels or standalone binaries) +.\" into one +.\" .Dq LIF +.\" volume suitable for booting. +.Ss PDC concepts +If autoboot is enabled, the PDC will attempt to boot from the specified +.Dq boot path +value. +If no +.Dq boot path +has been specified, the PDC will then scan for bootable devices and +boot from the first found, after a few seconds allowing the user to +interrupt the boot process. +If autoboot is disabled, the PDC will enter interactive mode, after an +optional device scan. +In all cases, it is possible to enter interactive mode by holding the +escape key during the selftests, or when prompted to do so to abort +the current operation, unless the PDC has been configured in +.Dq secure mode . +.\" +.Ss ISL interaction +.Dq ISL +stands for +.Dq Initial System Loader +and is the +.Nm +program in +.Nx . +On all versions of the PDC except for the 712 and 725 models the +.Dq boot +command (see below) will be followed by the question: +.Dq Interact with IPL (Y, N, or Cancel)?> +where a positive answer will invoke an interactive prompt in the +.Nm +program later and negative will thus suppress it. +A cancellation will abort the boot process. +.Pp +On the 712 and 725 models firmware an additional +.Dq isl +argument should be given to the +.Dq boot +command to invoke the +.Nm +interactive prompt. +The default behaviour is a non-interactive boot process. +.\" +.Ss Old PDC operation +This version is used on the following models: +705, 7x0, 715/33/50/75, 725/50/75, 735, 755. +There are two levels of interactive commands in this version. +The first level is a short menu: +.Bd -literal -offset indent +b) Boot from specified device +s) Search for bootable device +a) Enter Boot Administration mode +x) Exit and continue boot sequence + +Select from menu: +.Ed +.Pp +which provides the following commands: +.Pp +.Bl -tag -width "XXX" -offset indent -compact +.It Cm b +boot from a device found during the scan, +either with its short +.Dq P# +form, or a complete name specification. +For example, to boot from the +.Tn SCSI +disk with id 6 off the built-in (first) controller, +one would enter +.Ic b Ar scsi.6.0 . +.It Cm s +rescan for bootable devices. +.It Cm a +enter the second part of interactive mode. +.It Cm x +resume an interrupted boot sequence. +.El +.Pp +The +.Dq Boot Administration +mode, recognizable with its +.Em BOOT_ADMIN> +prompt, controls the various boot options. +The complete list of commands depends on the machine and PDC version. +The following list only mentions commands impacting the boot process. +.Bl -tag -width AUTOSELECT -offset indent +.It AUTOSELECT +Displays or changes the autoboot setting. +If autoselect is set to +.Dq on , +the PDC will always attempt to boot the first bootable device found in +this order: +.Bl -enum -offset indent -compact +.It +Boot device +.Em path +setting. +.It +.Tn SCSI +devices connected to the built-in +.Tn SCSI +controller, +the highest ID numbers being preferred. +.It +Network +.Em rboot +server (see also +.Xr rbootd 8 ) . +.It +Other +.Tn SCSI +devices connected to secondary controllers, +the highest ID numbers being preferred. +.El +If the +.Em primary path +setting defines a bootable device, no device scan will occur. +.It BOOT +Boots off the specified device. +It is similar to the +.Ic b +command from the short menu above. +The +.Dq primary +and +.Dq alternate +path settings may be booted with +.Ic boot Ar pri +and +.Ic boot Ar alt +respectively. +.It PATH +Displays or changes the boot and console devices. +The boot device is defined as the +.Dq primary +path, and another setting may be stored as the +.Dq alternate +path for rescue purposes. +For example, to define the primary boot path to the +.Tn SCSI +disk with ID 5 connected to the built-in controller, one would enter +.Ic path primary Ar scsi.5 +.Pp +When invoked without parameters, +.Ic path +will list the various path settings. +.El +.\" +.Ss Modern PDC operation +Machines equipped with 7100LC, 7200, or 7300LC CPU types are +usually blessed with a different kind of PDC. +There is only one interactive mode, with a +.Em BOOT_ADMIN> +prompt, which provides both boot settings and commands. +The complete list of commands depends on the machine and PDC version. +The following list only mentions commands impacting the boot process. +.Bl -tag -width auto\ search -offset indent +.It Ic auto boot +Displays or changes the autoboot setting. +If +.Ic auto boot +is set to +.Dq on , +the PDC will always attempt to boot. +The booted device chosen will depend on the +.Ic auto search +setting. +.It Ic auto search +Displays or changes the device scan setting. +If +.Ic auto search +is set to +.Dq on , +the PDC will attempt to boot the first bootable device found in +this order: +.Bl -enum -offset indent -compact +.It +Boot device +.Em path +setting. +.It +.Tn SCSI +devices connected to the built-in +.Tn SCSI +controller, +the highest ID numbers being preferred. +.It +Network +.Em bootp +server (see also +.Xr dhcpd 8 ) . +.It +Other +.Tn SCSI +devices connected to secondary controllers, +the highest ID numbers being preferred. +.El +If +.Ic auto search +is set to +.Dq off +and the primary boot path points to a bootable device, +no device scan will occur. +.Pp +Note that setting +.Ic auto search +to +.Dq on +will force autoboot, regardless of the +.Ic auto boot +value. +.It Ic boot +Boots off the specified device. +The +.Dq primary +and +.Dq alternate +path settings may be booted with +.Ic boot Ar pri +and +.Ic boot Ar alt +respectively. +.It Ic path +Displays or changes the boot and console devices. +The boot device is defined as the +.Dq primary +path, and another setting may be stored as the +.Dq alternate +path for rescue purposes. +For example, to define the primary boot path to the +.Tn SCSI +disk with ID 5 connected to the built-in controller, one would enter +.Ic path pri Ar scsi.5 . +.Pp +When invoked without parameters, +.Ic path +will list the various path settings. +.El +.\" +.Ss Abnormal system termination +If the system crashes, it will enter the kernel debugger, +.Xr ddb 4 , +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. +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 +.Xr savecore 8 +during the next multi-user boot cycle), and after the dump is complete +(successful or not) the kernel will attempt a reboot. +.Sh FILES +.Bl -tag -width /usr/mdec/xxbootxx -compact +.It Pa boot.lif +network bootstrap and kernel combined image +.It Pa /netbsd +default +.Nx +system kernel +.It Pa /usr/mdec/xxboot +primary bootstrap for +.Dq ffs +file system +.It Pa /usr/mdec/boot +system bootstrap (usually also installed as +.Pa /boot ) +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr dhcpd 8 , +.Xr halt 8 , +.Xr init 8 , +.Xr installboot 8 , +.Xr rbootd 8 , +.Xr reboot 8 , +.Xr savecore 8 , +.Xr shutdown 8 diff --git a/static/netbsd/man8/man8.hppa/mkboot.8 b/static/netbsd/man8/man8.hppa/mkboot.8 new file mode 100644 index 00000000..515825b2 --- /dev/null +++ b/static/netbsd/man8/man8.hppa/mkboot.8 @@ -0,0 +1,64 @@ +.\" $NetBSD: mkboot.8,v 1.1 2014/02/24 07:23:41 skrll Exp $ +.\" +.\" $OpenBSD: mkboot.8,v 1.9 2007/05/31 19:20:03 jmc Exp $ +.\" +.\" Copyright (c) 1990, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd January 9, 2012 +.Dt MKBOOT 8 hppa +.Os +.Sh NAME +.Nm mkboot +.Nd create LIF files +.Sh SYNOPSIS +.Nm mkboot +.Op Fl v +.Op Fl l Ar loadpoint +.Ar program ... outfile +.Sh DESCRIPTION +Creates the LIF file containing the bootstrap +.Ar program +and possibly other programs to be used by the +.Tn HP 9000/700 +and +.Tn HP 9000/800 +systems. +.Pp +An argument to the +.Fl l +option specifies the load point for the boot program, +with the default value of zero. +.Sh HISTORY +An +.Nm +utility first appeared in +.Ox 2.4 . +It was adapted for +.Nx +and first appeared in +.Nx 3.0 . diff --git a/static/netbsd/man8/man8.mac68k/Makefile b/static/netbsd/man8/man8.mac68k/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.mac68k/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.mac68k/boot.8 b/static/netbsd/man8/man8.mac68k/boot.8 new file mode 100644 index 00000000..08e943df --- /dev/null +++ b/static/netbsd/man8/man8.mac68k/boot.8 @@ -0,0 +1,129 @@ +.\" $NetBSD: boot.8,v 1.10 2009/09/05 11:37:52 wiz Exp $ +.\" +.\" Copyright (c) 1990, 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" From: +.\" @(#)boot_hp300.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd July 1, 1995 +.Dt BOOT 8 mac68k +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.Sh DESCRIPTION +.Ss Power fail and crash recovery +Normally, the +.Nx +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 +.Xr shutdown 8 +command. +.Pp +If the system crashes, it will enter the kernel debugger, +.Xr ddb 4 , +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 +.Xr savecore 8 +during the next boot cycle). +After the dump is complete (successful +or not), the system will attempt a reboot. +.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 +.Nx +boot program. +Additionally, the +.Nx +boot program can be configured to boot +.Nx +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. +.Pp +.Ss The boot application +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). +.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 +.Ql secure +option from ttye0 in the +.Xr ttys 5 +file. +.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. +.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 +.Nx +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 +.Ar /netbsd +within the +.Nx +file system. +.Sh FILES +.Bl -tag -width /netbsd -compact +.It Pa /netbsd +system kernel +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr ttys 5 , +.Xr savecore 8 , +.Xr shutdown 8 diff --git a/static/netbsd/man8/man8.macppc/Makefile b/static/netbsd/man8/man8.macppc/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.macppc/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.macppc/boot.8 b/static/netbsd/man8/man8.macppc/boot.8 new file mode 100644 index 00000000..cfccf501 --- /dev/null +++ b/static/netbsd/man8/man8.macppc/boot.8 @@ -0,0 +1,410 @@ +.\" $NetBSD: boot.8,v 1.9 2024/09/07 19:13:29 rillig Exp $ +.\" +.\" Copyright (c) 2003 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Michael Wolfson and Erik E. Fair. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt BOOT 8 macppc +.Os +.Sh NAME +.Nm boot +.Nd Macppc system bootstrapping procedures +.Sh DESCRIPTION +.Ss Power fail and crash recovery +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 +.Xr fsck 8 , +and unless this fails, the system will resume multi-user operations. +.Ss Cold starts +The boot ROM performs a Power On Self Test (POST) then loads Open +Firmware. +Depending on the Open Firmware variable +.Sq Ev auto-boot? +it will either stop at the Open Firmware +prompt or attempt to boot an operating system. +Depending on the contents +of the +.Sq Ev use-nvramrc? , +.Sq Ev boot-command , +.Sq Ev boot-device , +and +.Sq Ev boot-file +Open Firmware variables, it will attempt to boot +.Tn MacOS , +.Tn "MacOS X" , +or +.Nx . +.Pp +To boot +.Nx , +Open Firmware loads the bootloader +.Xr macppc/ofwboot 8 +from the specified +.Sq Ev boot-device . +The bootloader then loads the kernel from the +.Sq Ev boot-file , +.Pq if it exists . +Otherwise, it tries to load (in the following order): +.Pa netbsd , netbsd.gz , +or +.Pa netbsd.macppc +on the +.Dq a +partition of the same device that had the bootloader. +.Ss "Open Firmware Commands" +An essential but incomplete list of Open Firmware commands follows. +A more thorough list is contained in the FAQ. +.Lk https://www.NetBSD.org/ports/macppc/faq.html#ofw-use +.Pp +.Ic boot +.Op Ar boot-device Op Ar boot-file +.Op Ar options +.Pp +Boot an operating system. +The default arguments for this command are taken from the Open Firmware +environment variables: +.Bl -tag -width boot-device -compact +.It Ar boot-device +primary bootloader location +.It Ar boot-file +kernel location +.It Ar options +flags passed to the kernel +.El +.Pp +.Ic reset-all +.Pp +Reset the system, and proceed as specified by the +.Sq Ev use-nvramrc? +and +.Sq Ev auto-boot? +variables. +If +.Sq Ev use-nvramrc? +is set to +.Sq Ev true , +then the system will attempt to execute the commands stored in the +.Sq Ev nvramrc +variable. +If +.Sq Ev auto-boot? +is set to +.Sq Ev true , +the system will attempt to use the values stored in +.Sq Ev boot-command , +.Sq Ev boot-device , +and +.Sq Ev boot-file +to boot the system. +If +.Sq Ev auto-boot? +is set to +.Sq Ev false , +the system will halt at the Open Firmware prompt. +.Pp +.Ic shut-down +.Pp +Power off the system. +.Pp +.Ic setenv Ar variable Ar value +.Pp +Set an Open Firmware variable, e.g., +.Bd -literal -offset indent +setenv auto-boot? false +setenv boot-device hd:,\eofwboot.xcf +setenv boot-file netbsd-GENERIC.gz +.Ed +.Pp +.Ic set-default Ar variable +.Pp +Set an Open Firmware variable to its default value. +.Pp +.Ic printenv Op Ar variable +.Pp +Show Open Firmware variables and values. +.Pp +.Ic eject fd +.Pp +Eject floppy disk on systems with on-board floppy drives. +.Pp +.Ic mac-boot +.Pp +Attempt to boot +.Tn MacOS +on an Open Firmware 3 system. +.Pp +.Ic bye +.Pp +Attempt to boot +.Tn MacOS +on an Open Firmware 1.0.5, 2.0.x, or 2.4 system. +.Ss "Open Firmware Variables" +An essential but incomplete list of Open Firmware variables follows. +A more thorough list is contained in the FAQ. +.Lk https://www.NetBSD.org/ports/macppc/faq.html#ofw-variables +.Bl -tag -width "ew*0_protocols" +.It Ev auto-boot? +What Open Firmware will do at system startup or reset: +.Bl -tag -width false +.It Ar true +automatically bootstrap an operating system using values from the +.Sq Ev boot-command , +.Sq Ev boot-device , +and +.Sq Ev boot-file +variables. +.It Ar false +stop at the Open Firmware prompt. +.El +.Pp +.It Ev use-nvramrc? +If +.Sq Ev true +runs commands in variable +.Sq Ev nvramrc . +.Pp +.It Ev real-base +Kernel memory location. +.Em "Do not modify this value on Open Firmware 3 systems \(em you may" +.Em "damage your computer" . +All other Open Firmware versions should use +.Li F00000 . +.Pp +.It Ev load-base +Bootloader memory location. +.Em "Do not modify this value on Open Firmware 3 systems \(em you may" +.Em "damage your computer" . +All other Open Firmware versions should use +.Li 600000 . +.Pp +.It Ev boot-command +The command to use for booting. +Typically, the default of +.Sq Ev boot +is used. +.Pp +.It Ev boot-device +Device from which to load primary bootloader. +Value depends on a variety of factors. +See +.Xr macppc/ofwboot 8 . +.It Ev boot-file +Kernel location. +Value depends on a variety of factors. +See +.Xr macppc/ofwboot 8 . +.Pp +.It Ev input-device +What type of console input device +.Po +.Tn ADB +keyboard, +.Tn USB +keyboard, or serial port +.Pc . +.Bl -tag -width ttya +.It Ar kbd +.Tn ADB +keyboard on models with +.Tn ADB , +.Tn USB +keyboard on models with +.Tn 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. +.It Ar ttya +.Sq 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. +.It Ar ttyb +.Sq Printer +serial port on machines with serial ports. +Properties are the same as the +.Sq Modem +port. +.It Ar scca +Serial port on Xserve models. +Properties are 57600 bps, 8 bits, no +parity, 1 stop bit, no handshaking. +.El +.Pp +.It output-device +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 +.Xr macppc/ofwboot 8 +and +.Lk https://www.NetBSD.org/ports/macppc/faq.html#ofw-input-output-devices +.Pp +.It nvramrc +If +.Sq Ev use-nvramrc? +is set to true, these +.Tn FORTH +commands will be run when the computer is reset +.Pp +.El +.Ss "Normal Operation" +When Open Firmware loads the primary bootloader, it will print something +like the following: +.Bd -unfilled -offset indent + 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.. +.Ed +.Pp +When +.Xr macppc/ofwboot 8 +is started, it prints something like the following: +.Bd -unfilled -offset indent + >> NetBSD/macppc OpenFirmware Boot, Revision 1.7 + >> (autobuild@tgm.daemon.org, Thu Feb 6 17:50:27 UTC 2003) +.Ed +.Pp +When +.Xr macppc/ofwboot 8 +is loading the kernel, it prints something like the following: +.Bd -unfilled -offset indent + 4395364+254568 [220144+193803]=0x4d477c + start=0x100000 +.Ed +.Pp +When the +.Nx +kernel has started it prints a banner similar to the following: +.Bd -literal -offset indent + 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 +.Ed +.Ss "After bootstrap" +Once the +.Nx Ns Tn /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. +.Pp +The proper way to shut the system down is with the +.Xr shutdown 8 +command. +.Pp +If the system crashes, it will enter the kernel debugger, +.Xr ddb 4 , +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. +.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 +.Xr savecore 8 +during the next bootstrap cycle), and after the dump is complete (successful +or not) the kernel will attempt a reboot. +.Sh FILES +.Bl -tag -width /usr/mdec/bootxx_cd9660 -compact +.It Pa /boot +.Nx +secondary bootstrap program (Open Firmware 1.x and 2.x) +.It Pa /netbsd +default +.Nx +system kernel +.It Pa /usr/mdec/bootxx +.Nx +primary bootstrap program (Open Firmware 1.x and 2.x) a.k.a. +.Dq "partition zero" +bootloader +.It Pa /usr/mdec/ofwboot +.Nx +secondary bootstrap program (Open Firmware 1.x and 2.x) +.It Pa /usr/mdec/ofwboot.xcf +primary bootstrap for netboot and +.Dq cd9660 +.Pq Tn ISO 9660 , +.Dq MS-DOS , +.Dq HFS , +and +.Dq HFS+ +file systems. +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr intro 4 , +.Xr diskless 8 , +.Xr halt 8 , +.Xr init 8 , +.Xr installboot 8 , +.Xr macppc/ofwboot 8 , +.Xr rc 8 , +.Xr reboot 8 , +.Xr savecore 8 , +.Xr shutdown 8 +.Pp +.Lk https://www.NetBSD.org/ports/macppc/faq.html +.br +.Lk https://www.NetBSD.org/docs/network/netboot/ +.Sh STANDARDS +.St -ieee1275-94 +.Lk http://playground.sun.com/1275/home.html +.Sh BUGS +The device names used by +.Nx Ns Tn /macppc +and Open Firmware often have no relation to each other. +.Pp +Apple Computer's Open Firmware implementation is easily confused. +It is best to reboot your computer +after a failed boot attempt, +.Ic halt , +or +.Ic "shutdown -h" . +Use the Open Firmware +.Ic reset-all +command. +.Pp +Apple Computer's Open Firmware implementation is notoriously bad. +Thorough instructions for installing and booting +.Nx +are in the install notes +.Pq Pa INSTALL.html +included with every release of +.Nx . diff --git a/static/netbsd/man8/man8.macppc/ofwboot.8 b/static/netbsd/man8/man8.macppc/ofwboot.8 new file mode 100644 index 00000000..5e9c3651 --- /dev/null +++ b/static/netbsd/man8/man8.macppc/ofwboot.8 @@ -0,0 +1,490 @@ +.\" $NetBSD: ofwboot.8,v 1.18 2024/06/09 05:42:59 tsutsui Exp $ +.\" +.\" Copyright (c) 2001 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Makoto Fujiwara, Thomas Klausner, and Michael Wolfson. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd June 9, 2024 +.Dt OFWBOOT 8 macppc +.Os +.Sh NAME +.Nm ofwboot , +.Nm ofwboot.elf , +.Nm ofwboot.xcf +.Nd Open Firmware boot command +.Sh SYNOPSIS +.Nm ofwboot +.Sh DESCRIPTION +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. +.Nx +uses Open Firmware to initialize +many of the devices in a system and uses it to load the primary bootloader, +.Nm ofwboot . +.Pp +The information in this man page should only serve as a guideline for users. +.Tn 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. +.Pp +In this man page, only one Open Firmware command will be described, +.Ic boot , +because it is used to pass arguments to +.Nm ofwboot . +The Open Firmware +.Ic boot +command takes up to three arguments: +.Bd -literal -offset indent +.Ic boot Oo Ar boot-device Oo Ar boot-file Oc Oc Op Ar options +.Ed +.Pp +where +.Pp +.Bl -tag -width ".Ar boot-device" -offset indent -compact +.It Ar boot-device +primary bootloader location +.It Ar boot-file +kernel location +.It Ar options +flags passed to the kernel (see below) +.El +.Ss boot-device +The first argument, +.Ar boot-device , +actually designates the primary bootloader location and its name in the +form: +.Bd -literal -offset indent +.Sm off +.Ar device Ic \&: Oo Ar partition-num Oc Op \&, \e Ar bootloader-filename +.Sm on +.Ed +.Pp +A typical example, from a PowerBook (FireWire), is +.Pp +.Dl /pci@f2000000/mac-io@17/ata-4@1f000/@0:9,\eofwboot.xcf +.Pp +Note that colon +.Pq Ql \&: +delimits the device to the left, and comma +.Pq Ql \&, +separates the bootloader filename from the first part. +For Open Firmware versions before 3, the primary bootloader is installed +in partition +.Dq zero , +and it is not necessary to specify the +.Ar bootloader-filename . +For Open Firmware version 3, you must specify the bootloader filename. +.Pp +Open Firmware stores aliases to common devices in +.Tn NVRAM . +In the example the above, +.Pa /pci@f2000000/mac-io@17/ata-4@1f000/@0 +is the path on a PowerBook +(FireWire) to the built-in +.Tn ATA Ns /100 +hard drive. +Use the +.Ic devalias +command in Open Firmware to print out a list of common device names on a +particular model. +The +.Ar boot-device +above could then be simplified to: +.Pp +.Dl hd:9,\eofwboot.xcf +.Pp +.Ar bootloader-filename +is usually +.Nm ofwboot.xcf . +See also the +.Sx FILES +section for further discussion. +.Pp +If +.Ar boot-device +is omitted from the +.Ic boot +command, the Open Firmware variable +.Ev boot-device +is used. +.Ss boot-file +It may be necessary to specify the +.Ar boot-file +if Open Firmware does not know where to find the kernel. +The default is to load the file named +.Pa netbsd +on partition +.Dq Pa a +from the device used to load the primary bootloader. +.Pp +For systems with +Open Firmware versions less than 3 which are set up using +.Ic sysinst , +the +.Ar boot-file +argument is not necessary. +Systems with Open Firmware version 3 may need to specify the +.Ar boot-file . +.Pp +The syntax is similar to the +.Ar boot-device +argument: +.Bd -literal -offset indent +.Sm off +.Oo Ar boot-file-device Ic \&: Ar partition-num\^ Ic \&/ Oc Op Ar kernel-name +.Sm on +.Ed +.Pp +This is a little different, since a kernel-name may be specified without +listing a +.Ar boot-file-device +and +.Ar partition-num . +Additionally, a +.Ar boot-file-device +and +.Ar partition-num +may need to be specified, while using the default +.Ar kernel-name . +.Pp +If no +.Ar kernel-name +is specified, the primary bootloader will try to find kernels named either +.Pa netbsd +or +.Pa netbsd.gz +on the boot-device or (if specified) boot-file-device. +.Ss options +Possible options are: +.Bl -tag -width Fl +.It Fl a +ask for the boot device +.It Fl s +single-user mode boot +.It Fl d +debug mode +.It Cm exit +exit to Open Firmware after processing arguments +.El +.Sh ENVIRONMENT +If set, the following Open Firmware variables will be used to determine which +.Ar boot-device +and +.Ar boot-file +Open Firmware should use when booting a system. +If the user specifies arguments on the command line, these values +are overridden. +.Bl -tag -width Ev +.It Ev boot-device +used as the first argument +.It Ev boot-file +used as the second argument +.It Ev auto-boot? +setting this variable to +.Ic false +will present the user with an Open Firmware command prompt after power-on +reset. +A value of +.Ic true +will automatically boot the system using the variables +.Ev boot-device +and +.Ev boot-file . +(This is not really related to the boot command, but is included for +completeness.) +.El +.Pp +To restore these variables to their default values, use the +.Ic set-default +Open Firmware command: +.Pp +.Dl set-default boot-device +.Sh FILES +The three files +.Nm ofwboot , +.Nm ofwboot.elf , +and +.Nm ofwboot.xcf +are the same program, in different executable formats. +.Bl -tag -width ".Pa ofwboot.xcf" +. +.It Pa ofwboot +.Nm +is installed via +.Xr installboot 8 +on systems with Open Firmware versions less than 3. +It is not necessary to specify this file name on the Open Firmware +.Ic boot +command, as it is stored in a special location in the +.Nx +partition that is marked +.Dq bootable +in the Apple partition map entry. +The bootable partition can be specified as partition +.Dq zero . +For example, the following command might be used to boot from a SCSI device +with ID 2: +.Ic "0 >boot scsi-int/sd@2:0" . +. +.It Pa ofwboot.xcf +.Nm ofwboot.xcf +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 +.Dq zero , +such as from an ISO-9660 format CD-ROM. +. +.It Pa ofwboot.elf +.Nm ofwboot.elf +is in +.Xr elf 5 +format and only functions on systems with Open Firmware version 3. +To avoid confusion, all users should be using +.Nm ofwboot.xcf , +as +.Nm ofwboot.elf +offers no additional functionality. +It is only included for historical reasons. +. +.It Pa boot.fs +This 1.44 MB disk image contains everything necessary to boot and install +.Nx . +It includes the partition +.Dq zero +bootloader +.Nm ( ofwboot ) , +an INSTALL kernel (with limited device drivers), and the +.Ic sysinst +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 +.Xr dd 1 +on Unix, or +.Ic DiskCopy +on MacOS 9.1 or later, or +.Ic suntar +on any MacOS version to copy this image onto the media. +. +.It Pa netbsd +production kernel, using the GENERIC set of devices which supports almost all +hardware available for this platform. +. +.It Pa netbsd_GENERIC_MD.gz +GENERIC kernel (the same as +.Ar netbsd ) , +with RAM disk and +.Ic sysinst +included. +. +.It Pa NetBSD-{RELEASE}-macppc.iso +bootable CD-ROM image for all supported systems. +Usually located at +.Pa https://cdn.NetBSD.org/pub/NetBSD/images/{RELEASE}/ +.El +.Sh EXAMPLES +.Pp +In the following examples +.Ql "0\~>\~" +is the Open Firmware prompt. +.Bl -item +. +.It +Boot the default installation into single user mode. +.Dl 0 > boot -s +. +.It +Boot an Open Firmware 3 system, with +.Ar netbsd +installed on partition +.Dq Pa a : +.Dl 0 > boot hd:,\eofwboot.xcf +. +.It +Boot the kernel named +.Pa netbsd.new +from partition +.Dq Pa a +of the hard disk into +.Xr ddb 4 +using +.Tn ELF +version of +.Nm +from the USB flash drive: +.Dl 0 > boot usb0/disk:,\eofwboot.elf hd/netbsd.new -d +or +.Dl 0 > boot usb1/disk:,\eofwboot.elf hd/netbsd.new -d +Note: You can check which usb device name should be used by +.Dq Ic devalias +and +.Dq Ic dev usb0 ls +commands etc. +. +.It +Boot from bootable CD-ROM of +.Nx +release with Open Firmware 3 or higher: +.Dl 0 > boot cd:,\eofwboot.xcf +. +.It +Boot from bootable CD-ROM (internal SCSI, id=3) of +.Nx +release with Open Firmware versions prior to 3: +.Dl 0 > boot scsi/sd@3:0 +. +.It +Boot from a USB flash drive containing a bootable CD-ROM ISO image of +.Nx +release with Open Firmware 3 or higher: +.Dl 0 > boot usb0/disk@1:3,\eofwboot.xcf +or +.Dl 0 > boot usb1/disk@1:3,\eofwboot.xcf +Note: The partition number +.Dq Pa 3 +is an ISO9660/HFS hybrid partition specified by the Apple partition map +in the macppc CD ISO image of +.Nx +release. +. +.It +Boot from floppy disk: +.Dl 0 > boot fd:0 +. +.It +Boot from network, with bootps, +.Xr bootptab 5 , +.Xr tftpd 8 , +and +.Xr nfsd 8 +server available: +.Dl 0 > boot enet:0 +. +.It +Boot from network, but use internal root partition of second drive: +.Dl 0 > boot enet:0 ultra1:0 +. +.It +Boot MacOS, looking for the first available bootable disk: +.Dl 0 > boot hd:,\e\e:tbxi +. +.It +Boot MacOS X residing on partition 10: +.Dl 0 > boot hd:10,\e\e:tbxi +. +.El +.Sh ERRORS +.Bd -unfilled +DEFAULT CATCH!, code=FF00300 at %SRR0: FF80AD38 %SRR1: 00001070 +.Ed +Could be +.Dq 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 +.Ic reset-all +command might help. +.Bd -unfilled +CLAIM failed +.Ed +Open Firmware got errors on memory allocation ops etc. +This could also happen by buggy Open Firmware implementation, or improper +.Ev real-base +variable settings. +.Bd -unfilled +Can't LOAD from this device +.Ed +Open Firmware found the device, but it is not supported by +.Ic load . +.Bd -unfilled +0 > boot yy:0/netbsd +RESETing to change Configuration! +.Ed +.Ar yy:0 +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. +.Bd -unfilled +0 > boot ata/ata-disk@0:9 specified partition is not bootable + ok +.Ed +As it says. +.Bd -unfilled +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/ +.Ed +and hangs: See the real-base part in the FAQ. +.Pp +Note: It is recommended to restart Open Firmware by +.Ic reset-all +command if you get these Open Firmware errors, +to avoid further unexpected random errors. +.Sh SEE ALSO +.Xr installboot 8 +.Pp +.Pa INSTALL.html +.Pp +.Lk https://www.NetBSD.org/ports/macppc/faq.html "NetBSD/macppc Frequently Asked Questions" +.Pp +.Lk https://www.NetBSD.org/ports/macppc/partitioning.html "NetBSD/macppc Partitioning HOW-TO" +.Pp +.Lk https://www.NetBSD.org/ports/macppc/models.html "NetBSD/macppc Model Support" +.Pp +.Lk https://www.NetBSD.org/docs/network/netboot/ "Diskless NetBSD HOW-TO" +.Sh STANDARDS +.St -ieee1275-94 +.Sh BUGS +.Nm +can only boot from devices recognized by Open Firmware. +.Pp +Early PowerMacintosh systems (particularly the 7500) seem to have problems +with netbooting. +Adding an arp entry at the tftp server with +.Pp +.Dl arp -s booting-host-name its-ethernet-address +.Pp +may resolve this problem (see +.Xr arp 8 ) . +.Pp +Once boot failed, +.Bd -literal -offset indent +0 > boot CLAIM failed + ok +.Ed +.Pp +successive boots may not be possible. +You need to type +.Ic reset-all +or power-cycle to re-initialize Open Firmware. diff --git a/static/netbsd/man8/man8.mvme68k/Makefile b/static/netbsd/man8/man8.mvme68k/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.mvme68k/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.mvme68k/boot.8 b/static/netbsd/man8/man8.mvme68k/boot.8 new file mode 100644 index 00000000..11147639 --- /dev/null +++ b/static/netbsd/man8/man8.mvme68k/boot.8 @@ -0,0 +1,137 @@ +.\" $NetBSD: boot.8,v 1.9 2017/07/03 21:31:00 wiz Exp $ +.\" +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_sparc.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd April 8, 2003 +.Dt BOOT 8 mvme68k +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.\" .Sh SYNOPSIS +.\" .Nm reboot +.\" .Op Fl n +.\" .Op Fl q +.\" .Oo +.\" .Ar -- <boot string> +.\" .Oc +.Sh DESCRIPTION +.Ss Power fail and crash recovery +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 +.Xr fsck 8 . +and unless this fails, the system will resume multi-user operations. +.Ss Cold starts from disk +The disk-boot program +.Pa ( /usr/mdec/bootsd ) +will attempt to load +.Pa netbsd +from partition A of the boot device, +which must currently be an +.Dq sd +disk. +.Ss Cold starts from tape +The tape-boot program +.Pa ( /usr/mdec/bootst ) +will attempt to load +.Pa netbsd +from a SCSI tape drive. +.Ss Cold starts over a network +The network boot program +.Pa ( /usr/mdec/netboot ) +will load +.Pa netbsd +from the NFS root as determined by the procedure described in +.Xr diskless 8 . +Note that the MVME147 is unable to boot directly from the +network without the help of a small bootloader program +.Pa ( /usr/mdec/sboot ) . +.Ss Boot program options +.Bl -tag -width xxx +.It Fl a +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl d +Bring the system up in debug mode. +Here it waits for a kernel debugger connect; see +.Xr ddb 4 . +.It Fl q +Boot the system in quiet mode. +.It Fl s +Bring the system up in single-user mode. +.It Fl v +Boot the system in verbose mode. +.El +.Pp +Any extra flags or arguments, or the +.Ar <boot string> +after the -- separator are passed to the boot PROM. +Other flags are currently ignored. +.Pp +At any time you can break to the kernel debugger +.Xr ddb 4 +(assuming +.Sy options DDB +was specified in the kernel configuration file) +by sending a serial line BREAK character. +If you do this accidentally you can continue whatever was in progress +by typing +.Sq c +followed by the return key. +.Sh FILES +.Bl -tag -width /usr/mdec/installboot -compact +.It Pa /netbsd +system code +.It Pa /usr/mdec/bootxx +first-level boot block for disks +.It Pa /usr/mdec/stboot +first-level boot block for tapes +.It Pa /usr/mdec/bootsd +second-level boot block for UFS disks +.It Pa /usr/mdec/bootst +second-level boot block for tapes +.It Pa /usr/mdec/netboot +boot program for NFS (diskless) boot +.It Pa /usr/mdec/sboot +network bootstrap program for MVME147 +.It Pa /usr/mdec/installboot +program to install bootxx on a disk +.El +.Sh SEE ALSO +.Xr disklabel 8 , +.Xr fsck 8 , +.Xr halt 8 , +.Xr init 8 , +.Xr rc 8 , +.Xr shutdown 8 , +.Xr syslogd 8 diff --git a/static/netbsd/man8/man8.mvme68k/installboot.8 b/static/netbsd/man8/man8.mvme68k/installboot.8 new file mode 100644 index 00000000..6fb64fdf --- /dev/null +++ b/static/netbsd/man8/man8.mvme68k/installboot.8 @@ -0,0 +1,58 @@ +.\" $NetBSD: installboot.8,v 1.8 2001/12/26 01:53:18 wiz Exp $ +.\" +.Dd May 31, 1995 +.Dt INSTALLBOOT 8 mvme68k +.Os +.Sh NAME +.Nm installboot +.Nd install a bootstrap on a UFS disk +.Sh SYNOPSIS +.Nm /usr/mdec/installboot +.Fl n | Fl v +.Ar ufsboot +.Ar bootxx +.Ar rawdev +.Sh DESCRIPTION +.Nm +is used to install a "first-stage" boot program into the boot area +of a UFS disk partition, and initialize the table of block numbers the +.Ar bootxx +program uses to load the second-stage boot program. +.Pp +The options are as follows: +.Bl -tag -width flag +.It Fl n +Do not actually write anything on the disk. +.It Fl v +Be verbose, printing out the block numbers that +.Ar bootxx +will use to load +.Ar ufsboot . +.El +.Pp +The arguments are: +.Bl -tag -width ufsboot +.It Ar ufsboot +the name of the second-stage boot program in the file system +where the first-stage boot program is to be installed. +.It Ar bootxx +the name of the prototype file for the first stage boot program. +.It Ar rawdev +the name of the raw device in which the first-stage boot program +is to be installed. This should correspond to the block device +on which the file system containing +.Ar ufsboot +is mounted. +.El +.Sh SEE ALSO +.Xr disklabel 8 , +.Xr init 8 +.Sh BUGS +.Nm +requires simultaneous access to the mounted file system and +the raw device, but that is not allowed with the kernel +.Dv securelevel +variable set to a value greater than zero (the default), so +.Nm +only works in single-user mode (or insecure mode - see +.Xr init 8 ) . diff --git a/static/netbsd/man8/man8.next68k/Makefile b/static/netbsd/man8/man8.next68k/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.next68k/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.next68k/boot.8 b/static/netbsd/man8/man8.next68k/boot.8 new file mode 100644 index 00000000..129605b4 --- /dev/null +++ b/static/netbsd/man8/man8.next68k/boot.8 @@ -0,0 +1,73 @@ +.\" $NetBSD: boot.8,v 1.5 2019/09/01 15:08:52 sevan Exp $ +.\" +.\" Copyright (c) 1990, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" From: +.\" @(#)boot_hp300.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd September 1, 2019 +.Dt BOOT 8 next68k +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.Sh DESCRIPTION +.Ss Power fail and crash recovery +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. +.Ss Cold starts +On a NeXT, the boot procedure uses the boot ROM to load a boot program +over the network using BOOTP and TFTP. +The +.Pa /usr/mdec +directory contains a network boot program which should be made available +via +.Xr tftp 1 . +The network boot program will load +.Pa netbsd +from the NFS root as determined by the procedure described in +.Xr diskless 8 . +.Sh FILES +.Bl -tag -width /usr/mdec/installboot -compact +.It Pa /netbsd +system code +.It Pa /usr/mdec/boot +boot program for NFS (diskless) boot +.El +.Sh SEE ALSO +.Xr halt 8 , +.Xr init 8 , +.Xr rc 8 , +.Xr reboot 8 , +.Xr shutdown 8 diff --git a/static/netbsd/man8/man8.pmax/Makefile b/static/netbsd/man8/man8.pmax/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.pmax/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.pmax/boot.8 b/static/netbsd/man8/man8.pmax/boot.8 new file mode 100644 index 00000000..dcdfcf9a --- /dev/null +++ b/static/netbsd/man8/man8.pmax/boot.8 @@ -0,0 +1,220 @@ +.\" $NetBSD: boot.8,v 1.16 2017/06/22 16:46:52 flxd Exp $ +.\" +.\" Copyright (c) 1990, 1991 The Regents of the University of California. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to Berkeley by +.\" the Systems Programming Group of the University of Utah Computer +.\" Science Department. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd April 8, 2003 +.Dt BOOT 8 pmax +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.Sh DESCRIPTION +The +.Nx +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. +.Ss Power fail and crash recovery +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. +.Ss Cold starts +At power up, all DECstation ROMs consult the +.Nm haltaction +environment +variable in EEPROM to determine whether or not to attempt to boot +automatically. +If this variable is set to +.Sq h , +the ROM prints a prompt on the console and +waits for user commands. +If set to +.Sq b , +the ROM attempts to autoboot. +.Sh DECSTATION 2100 and 3100 +On the DECstation 2100 and 3100, the path used for automatic booting is +stored in the +.Nm bootpath +environment variable. + 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. +.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). +.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: +.Nm netbsd.pmax , +.Nm netbsd , +.Nm netbsd.gz , +.Nm netbsd.bak , +.Nm netbsd.old , +.Nm onetbsd , +.Nm gennetbsd . +Generally, the kernel is named +.Nm netbsd . +.Pp +An example bootpath setting would be: +.Dl Ic setenv bootpath rz(0,1,0)netbsd +.Pp +At the PROM prompt, the user may boot +.Nx +with either the +.Nm auto +or the +.Nm boot +command. +If the +.Nm auto +command is used, the +.Fl a +argument is passed to the kernel, requesting a multi-user boot; otherwise +the +.Fl s +argument is passed, requesting that +.Nx +boot to single user mode. +.Pp +When either the +.Nm boot +or the +.Nm auto +command is issued with no arguments, the kernel specified in the bootpath +environment variable is booted. +With the +.Nm boot +command, an alternative kernel may be specified +with the +.Fl f +flag, followed by the path of the kernel to boot, as described above. +For example: +.Dl Ic boot -f rz(0,4,0)netbsd.new +.Sh TURBOchannel DECstations +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., +.Fl a ) +when setting the +.Nm boot +environment variable, the filename and arguments +must be enclosed in quotes. +For example: +.Dl Ic setenv boot Dq Ic "3/rz4/netbsd -a" +.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 +.Nm cnfg +command +at the boot prompt. +You can get more detailed information about a specific +TURBOchannel option by typing +.Nm cnfg +followed by the slot number of that +option. +.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. +.Pp +To start +.Nx +from the boot prompt, the +.Nm boot +command must be used. +With no arguments, this simply boots the default +kernel with the default arguments as set with +.Nm setenv +.Nm boot . +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: +.Dl Ic boot 3/rz4/netbsd.new -a +.Sh KERNEL ARGUMENTS +The kernel supports the following arguments: +.Bl -tag -width xxx -offset indent +.It Li a +Autoboot -- try and boot to multi-user mode without +further input. +.It Li m +Use a miniroot already present in memory. +.It Li n +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Li N +Do not prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +If the configured-in devices are present, use them. +.It Li s +Boot only to single-user mode. +.El +.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: +.Dl Ic boot 3/rz4/netbsd \&ns +.Sh SEE ALSO +.Xr ddb 4 , +.Xr halt 8 , +.Xr init 8 , +.Xr installboot 8 , +.Xr rc 8 , +.Xr reboot 8 , +.Xr savecore 8 , +.Xr shutdown 8 +.Sh HISTORY +The +.Nm +command is +.Ud diff --git a/static/netbsd/man8/man8.prep/Makefile b/static/netbsd/man8/man8.prep/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.prep/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.prep/boot.8 b/static/netbsd/man8/man8.prep/boot.8 new file mode 100644 index 00000000..d5c3d021 --- /dev/null +++ b/static/netbsd/man8/man8.prep/boot.8 @@ -0,0 +1,86 @@ +.\" $NetBSD: boot.8,v 1.4 2017/02/17 22:30:28 christos Exp $ +.\" Copyright (c) 2006 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Tim Rightnour +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt BOOT 8 prep +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.Sh SYNOPSIS +.Nm boot +.Sh DESCRIPTION +.Ss Power fail and crash recovery +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 +.Xr fsck 8 , +and unless this fails, the system will resume multi-user operations. +.Ss Cold starts +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 +.Nx +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. +.Ss Boot program options +The prep architecture and bootloader does not support any option +parsing at the boot prompt. +.Ss Boot partition +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 +.Xr prep/mkbootimage 8 +command needs to be used to generate this image. +.Sh FILES +.Bl -tag -width /usr/mdec/boot_com0xx -compact +.It Pa /netbsd +system code +.It Pa /usr/mdec/boot +system bootstrap +.It Pa /usr/mdec/boot_com0 +system bootstrap with serial console +.El +.Sh SEE ALSO +.Xr disklabel 8 , +.Xr fsck 8 , +.Xr halt 8 , +.Xr init 8 , +.Xr installboot 8 , +.Xr prep/mkbootimage 8 , +.Xr rc 8 , +.Xr shutdown 8 , +.Xr syslogd 8 diff --git a/static/netbsd/man8/man8.prep/mkbootimage.8 b/static/netbsd/man8/man8.prep/mkbootimage.8 new file mode 100644 index 00000000..c53d8bb8 --- /dev/null +++ b/static/netbsd/man8/man8.prep/mkbootimage.8 @@ -0,0 +1,153 @@ +.\" $NetBSD: mkbootimage.8,v 1.8 2017/02/18 21:47:11 wiz Exp $ +.\" Copyright (c) 2006 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Tim Rightnour +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt MKBOOTIMAGE 8 prep +.Os +.Sh NAME +.Nm mkbootimage +.Nd create a prep boot image +.Sh SYNOPSIS +.Nm +.Op Fl lsv +.Op Fl b Ar bootfile +.Op Fl k Ar kernel +.Op Fl m Ar machine_arch +.Op Fl r Ar rawdev +.Ar boot-image +.Sh DESCRIPTION +.Nm +is the utility used to create a bootable kernel image on +.Nx +for prep, bebox or rs6000. +.Pp +The +.Nm +utility takes the boot-program, and the optional kernel, and creates a boot +image from them. +This image contains the boot code, kernel, and optionally +an i386 partition table. +The image can be written directly to a floppy or hard drive with +the +.Xr dd 1 +command, or it can be directly netbooted via +.Xr bootpd 8 . +.Pp +The following options are available: +.Bl -tag -width indent +.It Fl b +Specifies which bootloader to embed in the bootable image. +Defaults to +.Pa /usr/mdec/boot . +.It Fl k +Specifies which kernel binary to embed in the bootable image. +Defaults to +.Pa /netbsd . +.It Fl l +Creates a partition table for a 2.88MB floppy instead of a 1.44MB floppy. +This is primarily used for El-Torrito style CD images. +.It Fl m +Selects the machine architecture to build the image for. +Currently supports prep, rs6000 and bebox. +Defaults to the machine architecture you are currently running on. +This option is required if you are building an image for another machine, such +as building a prep boot image on i386. +.It Fl r +Specifies the raw device to read to gather the current partition table. +This is generally +.Pa /dev/rsd0c . +.It Fl s +Generates a standalone image with no partition table embedded. +.It Fl v +Generates verbose output, useful for debugging. +.El +.Pp +There are three primary ways to use +.Nm +to build a bootable image: +.Pp +The first method is to build an image suitable for a floppy or netboot. +This will create an image with an embedded partition table with a +single PReP boot partition of type 0x41(65). +The image can be directly netbooted, or if it +is small enough, written directly to a floppy with +.Xr dd 1 . +.Nm +will warn you if the generated image is too large to be written to a floppy. +.Pp +The second method is to build a standalone image with no partition table. +This should be written to the PReP boot partition on your hard drive with +.Xr dd 1 . +.Pp +The third method is for use in upgrading older systems that have +been built by writing the floppy image directly to the head of the +hard drive. +This method reads the existing partition table and embeds that in +the image. +This should prevent loss of your current partition layout. +This image should be written directly to the head of the disk with +.Xr dd 1 . +.Pp +The recommended setup for a PReP machine is to build a partition table with +.Xr fdisk 8 +that contains a PReP boot partition (type 65) as partition 0, marked active, +and a second partition for +.Nx +encompassing the remainder of the disk. +You should then create a disklabel on +that disk with a partition (such as e) pointing to the PReP boot partition. +Partition c should be the whole disk, and partition d can optionally be the +.Nx +portion of the disk. +You may then use the other partitions for your normal disk layout. +The PReP boot partition can be placed anywhere on the disk, but it is +recommended that it be placed at the beginning of the disk. +.Sh EXAMPLES +Create a floppy or netboot image for prep named +.Sq boot.fs : +.Dl Ic mkbootimage -m prep -b /usr/mdec/boot -k /netbsd boot.fs +Create a standalone bebox image for booting from a hard disk: +.Dl Ic mkbootimage -s -m bebox -b /usr/mdec/boot -k /netbsd boot.fs +Use the partition information on +.Sq sd0 +to create a new bootable image with com0 as the console: +.Dl Ic mkbootimage -b /usr/mdec/boot_com0 -k /netbsd -r /dev/rsd0c boot.fs +.Sh SEE ALSO +.Xr dd 1 , +.Xr bootpd 8 , +.Xr disklabel 8 , +.Xr fdisk 8 , +.Xr prep/boot 8 +.Sh HISTORY +.Nm +first appeared in +.Nx 1.5 . +.Sh AUTHORS +.Nm +was written by +.An NONAKA Kimihiro . diff --git a/static/netbsd/man8/man8.sandpoint/Makefile b/static/netbsd/man8/man8.sandpoint/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.sandpoint/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.sandpoint/altboot.8 b/static/netbsd/man8/man8.sandpoint/altboot.8 new file mode 100644 index 00000000..177b15ed --- /dev/null +++ b/static/netbsd/man8/man8.sandpoint/altboot.8 @@ -0,0 +1,288 @@ +.\" $NetBSD: altboot.8,v 1.11 2020/08/29 13:32:27 fcambus Exp $ +.\" +.\" Copyright (c) 2011 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Tohru Nishimura. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd October 7, 2013 +.Dt ALTBOOT 8 sandpoint +.Os +.Sh NAME +.Nm altboot +.Nd program to boot +.Nx +kernel from disk or network +.Sh DESCRIPTION +.Nm +is a standalone program which works on top of a +.Tn NAS +product's bootloader. +It is capable of loading a +.Nx +kernel from an +.Tn IDE +or +.Tn SATA +disk drive, or via network with +.Tn NFS +or +.Tn TFTP +protocol. +.Nm +can be stored in flash ROM. +Typically you will first copy it from flash into RAM and then invoke +it there to boot the +.Nx +kernel. +.Pp +.Nm +runs in conjunction with popular +.Tn U-Boot/PPCBoot +bootloaders used by +.Tn NAS +products. +With an appropriate boot command line, saved in the environment, +.Nm +can load and start a +.Nx +kernel without manual intervention. +The original +.Tn U-Boot/PPCBoot +bootloaders remain useful and altboot works as a functional extension +of them. +.Sh EXAMPLES +.Nm +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. +.Tn U-Boot/PPCboot +is instructed to copy the program to RAM in this way: +.Pp +.Dl => cp.b fffe0000 1000000 20000 +.Pp +Here 0xfffe'0000 is the flash address where +.Nm +is stored while 0x0100'0000 is the RAM address to copy to. +.Pp +The invocation syntax is: +.Pp +.Dl => go 1000000 Ar ide:N Ar opt1 Ar opt2 ... Ar bootname +.Bl -tag -width xx +.It Va ide:N +where +.Ar N +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 +.Nm +is trying to detect a non-existing drive. +Examples: +.Bl -tag -width xx +.It ide: Ns Ar 10 +A single master drive on the first channel. +Nothing on the second channel. +.It ide: Ns Ar 22 +A master and slave drive on both channels of the first controller. +.It ide: Ns Ar 1111 +A master drive on each channel. +The first two digits belong to the first +controller, the last two to the second controller. +.El +.Pp +Unspecified digits will be read as +.Ar 0 . +The +.Ar ide +option has only a meaning for PATA disks. +Omitting it makes it default to +.Ar ide:10 . +.Pp +.It Va optN +multi, auto, ask, single, ddb, userconf, norm, quiet, verb, +silent, debug +.Pp +Omitting optN makes +.Nm +default to multi-user mode boot. +.Pp +N.B., the maximum number of allowed go command arguments varies +and depends on the +.Tn U-Boot/PPCBoot +buildtime configuration. +.It Va bootname +One of the following: +.Pp +.Dl nfs: Ns Ar filename +.Dl nfs: +.Dl tftp: Ns Ar filename +.Dl tftp: +.Dl wd Ns Ar Np : Ns Ar filename +.Dl wd Ns Ar Np : +.Dl mem: Ns Ar address +.Dl net: +.Pp +The last one is a synonym for +.Dq nfs . +.It nfs: Ns Va filename +issue a +.Tn DHCP +request to determine the +.Tn IP +address and download +.Ar filename +from the +.Tn NFS +server. +.It nfs: +target file is determined by +.Sy filename +field of +.Pa /etc/dhcpd.conf +.It tftp: Ns Va filename +issue a +.Tn DHCP +request to determine +.Tn IP +address and download +.Ar filename +from the +.Tn TFTP +server. +.It tftp: +target file is determined by +.Sy filename +field of +.Pa /etc/dhcpd.conf +.It wd Ns Va Np : Ns Va filename +load the +.Tn ELF +.Nx +kernel +.Ar filename +from an +.Tn FFSv2 +or +.Tn FFSv1 +filesystem. +.Ar N +is a number to distinguish the target drive. +.Ar p +is a partition specifier. +When omitted, partition +.Sq a +is assumed. +.Dq wd0a +means partition +.Sq a +of the first disk drive. +.It wd Ns Va Np : +use filename +.Dq netbsd +for booting the +.Tn ELF +.Nx +kernel. +.It mem: Ns Va address +boots the +.Tn ELF +.Nx +kernel from any address in memory. +The +.Ar address +argument has to be specified as a hexadecimal number and denotes the +start address of the +.Tn ELF +image in memory. +.El +.Pp +.Nm +can boot from RAID 1 partitions, but only if the RAID partition is the +first partition on the disk. +.Pp +.Tn 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 +.Nx +after a 5 second delay, allowing the user to break into interactive +mode. +Note that a backslashed +.Sq \&; +is necessary to enter the script correctly. +.Bd -literal -offset indent +=> setenv bootcmd cp.b fffe0000 1000000 20000\e; go 1000000 wd0: +=> setenv bootdelay 5 +=> saveenv +.Ed +.Pp +When +.Tn U-Boot/PPCBoot +is lacking important commands like +.Tn cp +or +.Tn go , +or is unable to save the environment, then there is still the option to +replace the +.Tn Linux +kernel module by +.Pa altboot.img +and save it to the same address in flash ROM. +In this case you have only two options left to pass arguments: +.Pp +.Bl -bullet -compact +.It +Enter the interactive command line mode, after +.Nm +has started. +This requires a serial console. +.It +Write a fixed command line into flash, replacing the +.Tn Linux +initrd image. +The command line is a normal +.Tn ASCII +file, started by the identifier +.Em altboot: +and terminated by any control character between 0 and 31. +Example: +.Dl altboot:silent ide:1111 wd0:netbsd +.El +.Sh SEE ALSO +.Xr dhcpd 8 , +.Xr diskless 8 , +.Xr nfsd 8 , +.Xr raidctl 8 , +.Xr tftpd 8 +.Sh HISTORY +The +.Nx Ns Tn /sandpoint +.Nm +first appeared in +.Nx 6.0 . +.Sh BUGS +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. diff --git a/static/netbsd/man8/man8.sgimips/Makefile b/static/netbsd/man8/man8.sgimips/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.sgimips/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.sgimips/boot.8 b/static/netbsd/man8/man8.sgimips/boot.8 new file mode 100644 index 00000000..71c687d4 --- /dev/null +++ b/static/netbsd/man8/man8.sgimips/boot.8 @@ -0,0 +1,132 @@ +.\" $NetBSD: boot.8,v 1.7 2017/02/17 22:30:28 christos Exp $ +.\" +.\" Copyright (c) 2006 Stephen M. Rumble +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt BOOT 8 sgimips +.Os +.Sh NAME +.Nm boot +.Nd sgimips system bootstrapping procedures +.Sh DESCRIPTION +.Tn Silicon Graphics +MIPS-based computers all feature essentially similar firmware systems. +However, as of the Indigo R4x00 series (IP20), quasi- +.Tn 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. +.Sh Disk Booting +.Tn 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 +.Nx +requires that we write our bootloader into to the volume header using +.Xr sgimips/sgivol 8 . +.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 +.Dq OSLoader +PROM environment variable. +The +.Nx +bootloader will obtain the kernel filename to boot from the PROM or EEPROM. +This is specified by setting the PROM environment variable +.Dq OSLoadFilename +to an appropriate value. +For instance, +.Dq /netbsd.ecoff . +.Pp +For example, the following will configure the PROM to use the bootloader +.Dq aoutboot +to load the kernel +.Dq netbsd.old +.Pp +.Dl Ic setenv OSLoader aoutboot +.Dl Ic setenv OSLoadFilename netbsd.old +.Sh Network Booting +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 +.Dq netaddr +must match the address provided by the BOOTP server. +.Pp +An example BOOTP entry for +.Xr dhcpd 8 +follows: +.Pp +.Bd -unfilled -offset indent + 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"; + } +.Ed +.Pp +To boot a kernel named +.Dq netbsd.ecoff +the user would type: +.Dl Ic boot -f bootp():/netbsd.ecoff +.Pp +See +.Xr dhcpd.conf 5 +for more information on configuring +.Xr dhcpd 8 +as a BOOTP server. +.Sh SEE ALSO +.Xr dhcpd.conf 5 , +.Xr dhcpd 8 , +.Xr sgimips/sgivol 8 +.Sh CAVEATS +Some older PROM revisions do not support loading of ELF images. +The build system automatically prepares ECOFF versions, which are +correctly interpreted. +.Sh BUGS +.Nx +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. +.Pp +Some firmware revisions have a bug, which precludes them from communicating +with TFTP servers using ports above 32767. +When using +.Nx +as the TFTP server, this problem may be worked around as follows: +.Pp +.Dl Ic sysctl -w net.inet.ip.anonportmin=20000 +.Dl Ic sysctl -w net.inet.ip.anonportmax=32767 +.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 +.Nx +servers. +.Pp +This man page is horribly incomplete. diff --git a/static/netbsd/man8/man8.sgimips/sgivol.8 b/static/netbsd/man8/man8.sgimips/sgivol.8 new file mode 100644 index 00000000..e2635c70 --- /dev/null +++ b/static/netbsd/man8/man8.sgimips/sgivol.8 @@ -0,0 +1,155 @@ +.\" $NetBSD: sgivol.8,v 1.10 2017/02/17 22:30:28 christos Exp $ +.\" +.\" Copyright (c) 2006 Stephen M. Rumble +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt SGIVOL 8 sgimips +.Os +.Sh NAME +.Nm /usr/mdec/sgivol +.Nd configure SGI Volume Header +.Sh SYNOPSIS +.Nm +.Op Fl fq +.Ar device +.Nm +.Op Fl fq +.Fl i +.Op Fl h Ar vhsize +.Ar device +.Nm +.Op Fl fq +.Fl r +.Ar vhfilename +.Ar diskfilename +.Ar device +.Nm +.Op Fl fq +.Fl w +.Ar vhfilename +.Ar diskfilename +.Ar device +.Nm +.Op Fl fq +.Fl d +.Ar vhfilename +.Ar device +.Nm +.Op Fl fq +.Fl m +.Ar vhfilename +.Ar vhfilename +.Ar device +.Nm +.Op Fl fq +.Fl p +.Ar partno +.Ar partfirst +.Ar partblocks +.Ar parttype +.Ar device +.Sh DESCRIPTION +The +.Nm +program prepares an SGI Volume Header to be used to boot +.Nx . +The +.Tn SGI +PROM is able to load executables within the header, which in turn are used +to load the kernel from another file system. +.Sh OPTIONS +The following options are available: +.Bl -tag -width 123456 +.It Fl f +Force the operation. +Do not ask the user before proceeding. +.It Fl h +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). +.It Fl q +Suppress output. +.El +.Sh PARTITION TYPES +The numerical partition types for the volume header include: +.Bd -unfilled -offset indent + 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 +.Ed +.Sh EXAMPLES +To display the existing volume header and partition table on disk +.Dq sd0 : +.Dl Ic sgivol sd0 +.Pp +To initialize a new volume header 42 512-byte blocks large on disk +.Dq sd0 : +.Dl Ic sgivol -i -h 42 sd0 +.Pp +To copy a file +.Pa boot +from the volume header to local file +.Pa /tmp/boot +on disk +.Dq sd0 : +.Dl Ic sgivol -r boot /tmp/boot sd0 +.Pp +To copy a local file +.Pa /usr/mdec/ip2xboot +to the volume header as +.Pa boot +on disk +.Dq sd0 : +.Dl Ic sgivol -w boot /usr/mdec/ip2xboot sd0 +.Pp +To delete the existing file +.Pa boot +from the volume header on disk +.Dq sd0 : +.Dl Ic sgivol -d boot sd0 +.Pp +To move (rename) an existing file +.Pa file1 +to +.Pa file2 +in the volume header on disk +.Dq sd0 : +.Dl Ic sgivol -m file1 file2 sd0 +.Pp +To change partition 0 to type 4 (BSD4.2) beginning at block offset 3200 +and continue for 28000 blocks on disk +.Dq sd0 : +.Dl Ic sgivol -p 0 3200 28000 4 sd0 +.Sh SEE ALSO +.Xr sgimips/boot 8 diff --git a/static/netbsd/man8/man8.sparc/Makefile b/static/netbsd/man8/man8.sparc/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.sparc/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.sparc/binstall.8 b/static/netbsd/man8/man8.sparc/binstall.8 new file mode 100644 index 00000000..da933ac5 --- /dev/null +++ b/static/netbsd/man8/man8.sparc/binstall.8 @@ -0,0 +1,102 @@ +.\" $NetBSD: binstall.8,v 1.5 2008/09/24 18:19:13 reed Exp $ +.\" +.\" Copyright (c) 2002 Matthew R. Green +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, +.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED +.\" AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, +.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd January 6, 2002 +.Dt BINSTALL 8 sparc +.Os +.Sh NAME +.Nm /usr/mdec/binstall +.Nd install sparc and sparc64 boot blocks +.Sh SYNOPSIS +.Nm +.Op Fl htUuv +.Op Fl b Ar bootprog +.Op Fl f Ar filesystem +.Op Fl m Ar mdec +.Op Fl i Ar installbootprog +.Oo +.Dq net +.Ns \&| +.Dq ffs +.Oc +.Op directory +.Sh DESCRIPTION +The +.Nm +program prepares a sparc or sparc64 system for booting, either from local +disk from a +.Dq 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. +.Nm +can be forced to prepare a disk for either. +.Sh OPTIONS +The following options are available: +.Bl -tag -width 123456 +.It Fl b +Set the second stage boot program to +.Ar bootprog . +This will typically be +.Pa boot.net +for sparc systems and +.Pa ofwboot.net +for sparc64 systems. +.It Fl f +Set the path to the filesystem being installed for to +.Ar filesystem . +This is otherwise derived from the +.Op directory . +.It Fl h +Display help. +.It Fl i +Set the path to the +.Xr installboot 8 +program to +.Ar installbootprog . +This is useful for using +.Nm +on non-sparc or sparc64 systems. +.It Fl m +Sets the path to the machine dependent directory to +.Ar mdec . +This is the directory that both the boot blocks and the +.Xr installboot 8 +program live. +.It Fl t +Test mode; does not run any program. Implies the +.Fl v +option. +.It Fl U +Install sparc (SPARC) boot blocks. +.It Fl u +Install sparc64 (UltraSPARC) boot blocks. +.It Fl v +Be verbose. +.El +.Sh SEE ALSO +.Xr disklabel 8 , +.Xr installboot 8 diff --git a/static/netbsd/man8/man8.sparc/boot.8 b/static/netbsd/man8/man8.sparc/boot.8 new file mode 100644 index 00000000..67b3e8fa --- /dev/null +++ b/static/netbsd/man8/man8.sparc/boot.8 @@ -0,0 +1,264 @@ +.\" $NetBSD: boot.8,v 1.33 2020/08/29 13:32:27 fcambus Exp $ +.\" +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_sparc.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd June 17, 2006 +.Dt BOOT 8 sparc +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.Sh SYNOPSIS +.Nm boot +.Op Fl adqsv +.Oo +.Ar -- +.Aq Ar boot string +.Oc +.Sh DESCRIPTION +.Ss Power fail and crash recovery +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 +.Xr fsck 8 , +and unless this fails, the system will resume multi-user operations. +.Ss Cold starts +The +.Tn Sun +boot firmware, either old-style or new-style (Open Boot Prom), +performs a Power On Self Test +.Pq Tn POST , +and then will boot an operating system according to +configuration in Open Firmware environment variables. +.Ss Boot program options +.Bl -tag -width xxx +.It Fl a +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl d +Bring the system up in debug mode. +Here it waits for a kernel debugger connect; see +.Xr gdb 1 . +.It Fl C +Boot kernel in compat mode. +Starting with revision 1.14 +.Pq introduced on 2003/03/01 , +the sparc boot program loads the +.Nx +kernel at its linked virtual address. +This feature requires a kernel built after 2003/02/21 +.Pq corresponding to kernel version 1.6Q . +To load older kernels, the +.Fl C +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. +.It Fl q +Boot the system in quiet mode. +.It Fl s +Bring the system up in single-user mode. +.It Fl v +Boot the system in verbose mode. +.El +.Pp +Any extra flags or arguments, or the +.Aq Ar boot string +after the -- separator are passed to the boot PROM. +Other flags are currently ignored. +.Pp +The SPARC boot ROM comes in two flavours: an +.Dq old-style +ROM is used in sun4 machines, while a +.Dq new-style +ROM can be found on sun4c and sun4m models. +The +.Dq new-style +SPARC boot ROM is a full-featured Forth system with emacs key bindings. +It can be put in +.Dq old-style +user-interface compatibility mode (in which case it shows a simple +.Sq > +prompt), but this is essentially useless. +However, by default on sun4c models, the ROM runs in old-mode; to +enter new-mode type +.Sq n . +The ROM then shows a Forth-style +.Dq ok +prompt. +It is recommended to have the ROM always start in its native +.Dq new-style +mode. +Utter the following incantation in new-mode to force the ROM to always start +in new-mode. +.Pp +.Pa \ ok +setenv sunmon-compat? false +.Pp +The ROM will normally load the kernel from +.Dq sd(0,0,0)vmunix . +To change the default so that +.Nx +will be loaded from somewhere else, type the following +.Pp +.Pa \ ok +setenv boot-from sd(0,0,0)netbsd +.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 +.Ic devalias ) +is: +.Bd -literal -offset indent +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 +.Ed +.Pp +For new-style machines, +if a device specification includes a partition letter (for example +.Em cdrom +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. +.Pp +At any time you can break back to the ROM by pressing the +.Sq L1 +and +.Sq a +keys at the same time (if the console is a serial port the same is +achieved by sending a +.Sq break ) . +If you do this accidentally you can continue whatever was in progress +by typing +.Sq go . +.Sh OPEN BOOT PROM ENVIRONMENT VARIABLES +This section only applies to new-style machines. +.Pp +All Open Boot PROM environment variables can be printed with the +.Ic printenv +command and changed with the +.Ic setenv +command. +The boot process relevant variables and their suggested value for +booting +.Nx +are: +.Bd -literal -offset indent +auto-boot? true +boot-file +boot-device disk +diag-switch? false +.Ed +.Pp +Of course you may select any other boot device, +if you do not want to boot from the device aliased to +.Em disk , +see the discussion on devices above. +.Sh OPEN BOOT PROM ABBREVIATED COMMAND SUMMARY +This section only applies to new-style machines. +.Pp +The following Open Boot PROM commands are related to the boot process: +.Bd -literal -offset indent +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 +.Ed +For disk and tape devices, the boot device is specified as +.Sq /path/device@target,lun:partition . +.Sh PROM MONITOR ABBREVIATED COMMAND SUMMARY +This section only applies to old-style machines. +.Pp +The following PROM monitor commands are related to the boot process: +.Bd -literal -offset indent +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 +.Ed +.Pp +For SCSI disk and tape devices, the boot device is specified as +.Sq device(controller,unit,partition) , +where +.Sq unit +is the hexadecimal value of the SCSI id of the target multiplied +by eight plus the lun, and +.Sq partition +is the partition number, starting from 0. +.Sh FILES +.Bl -tag -width /netbsdxx -compact +.It Pa /netbsd +system code +.It Pa /boot +system bootstrap +.El +.Sh SEE ALSO +.Xr crash 8 , +.Xr disklabel 8 , +.Xr fsck 8 , +.Xr halt 8 , +.Xr init 8 , +.Xr installboot 8 , +.Xr rc 8 , +.Xr shutdown 8 , +.Xr sparc64/boot 8 , +.Xr syslogd 8 +.Sh BUGS +On sun4 machines, the +.Nx +sparc boot loader can only boot from RAID partitions that start at the +beginning of the disk. +.Pp +On sun4 and early PROM version sun4c machines, the PROM can only boot from +the first 1Gb of the disk. +.Pp +On later PROM version sun4c and early PROM version sun4m machines, the PROM +can only boot from the first 2Gb of the disk. +.Pp +On later PROM version sun4m machines, the PROM can only boot from the first +4Gb of the disk. diff --git a/static/netbsd/man8/man8.sparc64/Makefile b/static/netbsd/man8/man8.sparc64/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.sparc64/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.sparc64/boot.8 b/static/netbsd/man8/man8.sparc64/boot.8 new file mode 100644 index 00000000..31a534f9 --- /dev/null +++ b/static/netbsd/man8/man8.sparc64/boot.8 @@ -0,0 +1,264 @@ +.\" $NetBSD: boot.8,v 1.18 2014/10/27 16:18:38 wiz Exp $ +.\" +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_sparc.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd November 9, 2008 +.Dt BOOT 8 sparc64 +.Os +.Sh NAME +.Nm boot , +.Nm ofwboot +.Nd system bootstrapping procedures +.Sh SYNOPSIS +.Nm boot +.Op Fl adqsv +.Oo +.Ar -- +.Aq Ar boot string +.Oc +.Sh DESCRIPTION +.Tn Sun +.Tn UltraSPARC +systems support booting from locally attached storage media +.Pq e.g. hard disk, Tn CD-ROM , +and booting over +.Tn Ethernet +networks using +.Tn BOOTP . +.Ss Power fail and crash recovery +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 +.Xr fsck 8 , +and unless this fails, the system will resume multi-user operations. +.Ss Cold starts +The +.Tn Sun +Open Firmware performs a Power On Self Test +.Pq Tn POST , +and then will boot an operating system according to +configuration in Open Firmware environment variables. +.Ss Boot program options +.Bl -tag -width xxx +.It Fl a +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl d +Bring the system up in debug mode. +Here it waits for a kernel debugger connect; see +.Xr gdb 1 . +.It Fl q +Boot the system in quiet mode. +.It Fl s +Bring the system up in single-user mode. +.It Fl v +Boot the system in verbose mode. +.El +.Pp +Any extra flags or arguments, or the +.Aq Ar boot string +after the -- separator are passed to the boot PROM. +Other flags are currently ignored. +.Pp +At any time you can halt the running system and get back to the Open Firmware. +If the console is the +.Tn Sun +framebuffer and keyboard, +press the +.Sq STOP +and +.Sq A +keys at the same time on the keyboard. +On older models of +.Tn Sun +keyboards, the +.Sq STOP +key is labeled +.Sq L1 . +.Pp +If the console is a serial port the same is +achieved by sending a +.Sq BREAK . +.Pp +If you do this accidentally, you can continue whatever was in progress +with the +.Ic go +command. +.Sh BOOT DEVICES +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. +.Pp +The secondary boot loader, +.Nm ofwboot , +takes +.Nm +commands virtually the same as Open Firmware. +Thus, the following examples apply equally to +.Nm ofwboot +as well as Open Firmware. +.Pp +A typical list of usable boot devices (extracted from the output of +the Open Firmware command +.Ic devalias ) +is: +.Bd -literal -offset indent +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 +.Ed +.Pp +If a device specification includes a partition letter (for example +.Em cdrom +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. +.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). +.Sh FIRMWARE ENVIRONMENT VARIABLES +All Open Firmware environment variables can be printed with the +.Ic printenv +command and changed with the +.Ic setenv +command. +The boot process relevant variables and their suggested value for +booting +.Nx +are: +.Bd -literal -offset indent +boot-command boot +auto-boot? true +boot-file +boot-device disk +diag-switch? false +.Ed +.Pp +Of course you may select any other boot device, +if you do not want to boot from the device aliased to +.Em disk , +see the discussion on devices above. +.Sh FILES +.Bl -tag -width /usr/mdec/ofwboot.netxx -compact +.It Pa /netbsd +system code +.It Pa /ofwboot +system bootstrap +.It Pa /usr/mdec/ofwboot.net +alternate bootstrap when booting from the network, see +.Xr diskless 8 +for details. +.El +.Sh EXAMPLES +Boot from +.Tn CD-ROM : +.Pp +.Bd -literal -offset indent +boot cdrom +.Ed +.Pp +Note that some multi-architecture CDs are not able to use the +default sparc64 partition for +.Tn CD-ROMs +.Pq f , +so they may require an explicit partition letter, for example +.Bd -literal -offset indent +boot cdrom:c +.Ed +.Pp +When using external +.Tn SCSI +.Tn CD-ROM +drives it is important to know two things: the +.Tn Sun +firmware expects the +.Tn SCSI +ID to be six, and the drive must support 512-byte block reads, +in addition to the standard 2048-byte reads. +.Pp +Use +.Bd -literal -offset indent +boot net -sd +.Ed +.Pp +to boot single user from network and break into the kernel debugger as +soon as possible. +.Pp +Use +.Bd -literal -offset indent +boot net tftp:netbsd -a +.Ed +.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. +.Pp +During installation from a different operating system +.Bd -literal -offset indent +boot disk:b +.Ed +.Pp +is used to boot a +.Dq miniroot +file system from the swap partition. +.Sh SEE ALSO +.Xr disklabel 8 , +.Xr diskless 8 , +.Xr fsck 8 , +.Xr halt 8 , +.Xr init 8 , +.Xr installboot 8 , +.Xr rc 8 , +.Xr shutdown 8 , +.Xr sparc/boot 8 , +.Xr syslogd 8 +.Sh STANDARDS +.Tn Sun +developed its firmware and promoted it to become +.St -ieee1275-94 . +.Pp +.Lk http://www.openfirmware.org/1275/ "IEEE 1275 Open Firmware" +.Sh BUGS +.Nx +provides no way to boot +.Tn UltraSPARC +systems from floppy disks. +This is unlikely to change, due to very low demand for this feature. +.Pp +The OBP on Ultra 1 and Ultra 2 machines can only boot from the first +4Gb of the disk. diff --git a/static/netbsd/man8/man8.sun2/Makefile b/static/netbsd/man8/man8.sun2/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.sun2/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.sun2/boot.8 b/static/netbsd/man8/man8.sun2/boot.8 new file mode 100644 index 00000000..ac7d9a5e --- /dev/null +++ b/static/netbsd/man8/man8.sun2/boot.8 @@ -0,0 +1,178 @@ +.\" $NetBSD: boot.8,v 1.7 2010/02/25 17:15:55 wiz Exp $ +.\" +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_sparc.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd April 29, 2003 +.Dt BOOT 8 sun2 +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.Sh SYNOPSIS +.Nm b +.Oo +.Ar dev +.Oo Pq Ar cntrl , unit , part +.Oc +.Oc +.Op Ar file +.Op Fl adqsv +.Sh DESCRIPTION +.Ss Power fail and crash recovery +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 +.Xr fsck 8 , +and unless this fails, the system will resume multi-user operations. +.Ss Selecting the device and kernel to boot +Normally, the +.Nm b +command alone is sufficient to boot the system, as the PROM chooses +a default boot device +.Ar dev +if none is specified. +The PROM chooses the first device present on +the system from the following ordered list: +.Pp +.Bd -unfilled -offset indent -compact +sd SCSI disk +ie Intel Ethernet +ec 3Com Ethernet +.Ed +.Pp +Unless specified, the controller number +.Ar cntrl , +unit number +.Ar unit , +and partition number +.Ar part +default to zero, which is almost always correct. +.Pp +The controller number can +be specified if there is more than one of the given device in the system. +For example, use +.Dq ie(1,,) +to boot off of the second Intel Ethernet in the system. +.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, +.Dq 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. +.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, +.Dq sd(,18,1) +boots the second partition on the disk at target 6 on the first SCSI +controller. +.Pp +The PROM only loads a first-stage boot program, currently either +.Pa /usr/mdec/bootxx +(for a disk boot), or +.Pa /usr/mdec/bootyy +(for a network boot). +This first-stage boot program then loads the +second-stage boot program from the same device, currently either +.Pa /usr/mdec/ufsboot +(for a disk boot), or +.Pa /usr/mdec/netboot +(for a network boot). +.Pp +The second-stage boot program will then attempt to load the kernel named +.Ar file +(or +.Pa vmunix +if none is specified). +The second-stage disk boot program +.Pa /usr/mdec/ufsboot +loads the kernel from the same device that it was loaded from, +while the second-stage network boot program +.Pa /usr/mdec/netboot +will load the kernel +from the NFS root as determined by the procedure described in +.Xr diskless 8 . +.Ss Boot program options +.Bl -tag -width xxx +.It Fl a +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl d +Bring the system up in debug mode. +Here it waits for a kernel debugger connect; see +.Xr ddb 4 . +.It Fl q +Boot the system in quiet mode. +.It Fl s +Bring the system up in single-user mode. +.It Fl v +Boot the system in verbose mode. +.El +.Pp +Other flags are currently ignored. +.Pp +At any time you can break back to the ROM by pressing the +.Sq L1 +and +.Sq a +keys at the same time (if the console is a serial port the same is +achieved by sending a +.Sq break ) . +If you do this accidentally you can continue whatever was in progress +by typing +.Sq c +followed by the return key. +.Sh FILES +.Bl -tag -width /usr/mdec/installbootXX -compact +.It Pa /netbsd +system code +.It Pa /usr/mdec/bootxx +first-level boot block for disks +.It Pa /usr/mdec/bootyy +first-level boot block for NFS (diskless) boot +.It Pa /usr/mdec/netboot +boot program for NFS (diskless) boot +.It Pa /usr/mdec/ufsboot +second-level boot program for UFS disks +.It Pa /usr/sbin/installboot +program to install bootxx on a disk +.El +.Sh SEE ALSO +.Xr crash 8 , +.Xr disklabel 8 , +.Xr fsck 8 , +.Xr halt 8 , +.Xr init 8 , +.Xr rc 8 , +.Xr shutdown 8 , +.Xr syslogd 8 diff --git a/static/netbsd/man8/man8.sun3/Makefile b/static/netbsd/man8/man8.sun3/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.sun3/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.sun3/boot.8 b/static/netbsd/man8/man8.sun3/boot.8 new file mode 100644 index 00000000..b4136583 --- /dev/null +++ b/static/netbsd/man8/man8.sun3/boot.8 @@ -0,0 +1,121 @@ +.\" $NetBSD: boot.8,v 1.14 2003/08/07 10:31:28 agc Exp $ +.\" +.\" Copyright (c) 1992, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_sparc.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd April 8, 2003 +.Dt BOOT 8 sun3 +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.\" .Sh SYNOPSIS +.\" .Nm reboot +.\" .Op Fl n +.\" .Op Fl q +.\" .Oo +.\" .Ar -- <boot string> +.\" .Oc +.Sh DESCRIPTION +.Ss Power fail and crash recovery +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 +.Xr fsck 8 , +and unless this fails, the system will resume multi-user operations. +.Ss Cold starts +A disk-boot program +.Pa ( /usr/mdec/ufsboot ) +will attempt to load +.Pa netbsd +from partition A of the boot device, +which must currently be an +.Dq sd +disk. +Alternatively, network boot program +.Pa ( /usr/mdec/netboot ) +will load +.Pa netbsd +from the NFS root as determined by the procedure described in +.Xr diskless 8 . +.Ss Boot program options +.Bl -tag -width xxx +.It Fl a +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl d +Bring the system up in debug mode. +Here it waits for a kernel debugger connect; see +.Xr ddb 4 . +.It Fl q +Boot the system in quiet mode. +.It Fl s +Bring the system up in single-user mode. +.It Fl v +Boot the system in verbose mode. +.El +.Pp +Any extra flags or arguments, or the +.Aq Ar boot string +after the -- separator are passed to the boot PROM. +Other flags are currently ignored. +.Pp +At any time you can break back to the ROM by pressing the +.Sq L1 +and +.Sq a +keys at the same time (if the console is a serial port the same is +achieved by sending a +.Sq break ) . +If you do this accidentally you can continue whatever was in progress +by typing +.Sq c +followed by the return key. +.Sh FILES +.Bl -tag -width /usr/mdec/installboot -compact +.It Pa /netbsd +system code +.It Pa /usr/mdec/bootxx +first-level boot block for disks +.It Pa /usr/mdec/netboot +boot program for NFS (diskless) boot +.It Pa /usr/mdec/ufsboot +second-level boot program for UFS disks +.It Pa /usr/mdec/installboot +program to install bootxx on a disk +.El +.Sh SEE ALSO +.Xr disklabel 8 , +.Xr fsck 8 , +.Xr halt 8 , +.Xr init 8 , +.Xr rc 8 , +.Xr shutdown 8 , +.Xr syslogd 8 diff --git a/static/netbsd/man8/man8.vax/Makefile b/static/netbsd/man8/man8.vax/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.vax/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.vax/boot.8 b/static/netbsd/man8/man8.vax/boot.8 new file mode 100644 index 00000000..741c1f7f --- /dev/null +++ b/static/netbsd/man8/man8.vax/boot.8 @@ -0,0 +1,321 @@ +.\" $NetBSD: boot.8,v 1.15 2018/03/18 10:54:54 ragge Exp $ +.\" +.\" Copyright (c) 1980, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_vax.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd April 19, 1994 +.Dt BOOT 8 vax +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.Sh DESCRIPTION +.Ss Power fail and crash recovery +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. +.Pp +.Ss Cold starts +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 +.Tn HPS +and +.Tn HPM +for the single +and multi-user boot from +.Tn MASSBUS +RP06/RM03/RM05 disks, +.Tn UPS +and +.Tn UPM +for +.Tn UNIBUS +storage module controller and disks +such as the +.Tn EMULEX +SC-21 +and +.Tn AMPEX +9300 pair, +.Tn RAS +and +.Tn RAM +to boot from +.Tn MSCP +controllers and disks such as the RA81, +or +.Tn HKS +and +.Tn 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. +.Pp +Giving the command +.Pp +.Dl >>>BOOT HPM +.Pp +would boot the system from (e.g.) an RP06 and run the automatic consistency +check as described in +.Xr fsck 8 . +(Note that it may +be necessary to type control-P +and halt the processor +to gain the attention of the +.Tn LSI-11 +before getting the >>> prompt.) +The command +.Pp +.Dl >>>BOOT ANY +.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. +.Pp +The scripts may be modified for local configuration if necessary. +The flags are placed in register 11 (as defined in +.In sys/reboot.h ) . +The boot device is specified in register 10. +The encoding of this register is also defined in +.In sys/reboot.h . +The current encoding has a historical basis, and is shown in the following +table: +.Pp +.Bd -unfilled -offset indent -compact +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) +.Ed +.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 +.Ux ) . +.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 +.Pp +.Bd -unfilled -offset indent -compact +.Li \&>>>B/ Ns Fl n No DMA0 +.Ed +.Pp +where, giving a +.Ar n +of 1 causes the boot program +to ask for the name of the system to be bootstrapped, +giving a +.Ar n +of 2 causes the boot program to come up single +user, and a +.Ar n +of 3 causes both of these actions to occur. +The ``DM'' specifies RK07, the ``A'' represents the adaptor number +.Pf ( Tn UNIBUS +or +.Tn MASSBUS ) , +and the ``0'' is the drive unit number. +Other disk types which may be used are DB +.Pq Tn MASSBUS , +DD (TU58), +and DU +.Pf ( Tn UDA-50/RA +disk). +A non-zero disk partition can be used by adding (partition times 1000 hex) +to +.Ar n . +.Pp +The boot procedure on the Micro +.Tn 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. +.Pp +The 11/750 boot procedure uses the boot ROMs to load block 0 off of +the specified device. +The +.Pa /usr/mdec +directory contains a number +of bootstrap programs for the various disks which should be placed +in a new pack by +.Xr disklabel 8 . +Similarly, the Micro +.Tn VAX +II boot procedure loads a boot parameter block +from block 0 of the disk. +The +.Ic rdboot +.Dq bootstrap +contains the correct parameters for an +.Tn MSCP +disk such +as the RD53. +.Pp +On any processor, the +.Em boot +program +finds the corresponding file on the given device +.Pf ( Pa netbsd +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). +.Pp +The file specifications used with +.Dq BOOT ANY +or +.Dq \&B/3 +are of the form: +.Pp +.Dl device(adaptor,controller,unit,minor) +.Pp +where +.Ar device +is the type of the device to be searched, +.Ar adaptor +is the +.Tn UNIBUS +or +.Tn MASSBUS +number of the adaptor to which the device is attached, +.Ar controller +is the unit number of the controller or +.Tn MASSBUS +tape formatter on that adaptor, +.Ar unit +is the unit number of the disk or transport slave unit of the tape, +and +.Ar minor +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: +.Pp +.Bd -unfilled -offset indent -compact +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 +.Ed +.Pp +For example, +to boot from a file system which starts at cylinder 0 +of unit 0 of a +.Tn MASSBUS +disk, type +.Ql hp(0,0)netbsd +to the boot prompt; +.Ql hp(2,0,1,0)netbsd +would specify drive 1 on +.Tn MASSBUS +adaptor 2; +.Ql up(0,0)netbsd +would specify a +.Tn UNIBUS +drive, +.Ql hk(0,0)netbsd +would specify +an RK07 disk drive, +.Ql ra(1,0,0,0)netbsd +would specify a +.Tn UDA50 +disk drive on a second +.Tn UNIBUS , +and +.Ql rb(0,0)netbsd +would specify a +disk on a 730 +.Tn IDC . +For tapes, the minor device number gives a file offset; +.Ql mt(1,2,3,4) +would specify the fifth file on slave 3 of the formatter +at +.Ql drive +2 on mba 1. +.Pp +On an 11/750 with patchable control store, +microcode patches will be installed by +.Em boot +if the file +.Pa pcs750.bin +exists in the root of the filesystem from which the system is booted. +.Pp +In an emergency, the bootstrap methods described in the paper +.%T Installing and Operating 4.3bsd +can be used to boot from a distribution tape. +.Sh FILES +.Bl -tag -width /usr/mdec/xxboot -compact +.It Pa /netbsd +system code +.It Pa /boot +system bootstrap +.It Pa /usr/mdec/xxboot +sector 0-15 boot block +.It Pa /pcs750.bin +microcode patch file on 750 +.El +.Sh SEE ALSO +.Xr arff 8 , +.Xr halt 8 , +.Xr reboot 8 , +.Xr shutdown 8 +.Sh HISTORY +The +.Nm +command appeared in +.Bx 4.0 . diff --git a/static/netbsd/man8/man8.vax/crash.8 b/static/netbsd/man8/man8.vax/crash.8 new file mode 100644 index 00000000..b3684591 --- /dev/null +++ b/static/netbsd/man8/man8.vax/crash.8 @@ -0,0 +1,205 @@ +.\" $NetBSD: crash.8,v 1.12 2009/03/09 19:24:32 joerg Exp $ +.\" +.\" Copyright (c) 1980, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)crash.8 8.1 (Berkeley) 6/5/93 +.\" +.Dd June 5, 1993 +.Dt CRASH 8 vax +.Os +.Sh NAME +.Nm crash +.Nd UNIX system failures +.Sh DESCRIPTION +This section explains what happens when the system crashes +and (very briefly) how to analyze crash dumps. +.Pp +When the system crashes voluntarily it prints a message of the form +.Pp +.Dl panic: why i gave up the ghost +.Pp +on the console, takes a dump on a mass storage peripheral, +and then invokes an automatic reboot procedure as +described in +.Xr reboot 8 . +(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. +.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. +.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. +.Bl -tag -width 8n -compact +.It iinit +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. +.It Can't exec /sbin/init +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, +.Xr init 8 . +The root filesystem is incorrect or has been corrupted, or the mode +or type of /sbin/init forbids execution. +.It IO err in push +.It hard IO err in swap +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. +.It realloccg: bad optim +.It ialloc: dup alloc +.It alloccgblk: cyl groups corrupted +.It ialloccg: map corrupted +.It free: freeing free block +.It free: freeing free frag +.It ifree: freeing free inode +.It alloccg: map corrupted +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. +.It timeout table overflow +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. +.It KSP not valid +.It SBI fault +.It CHM? in kernel +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. +.It machine check %x: Em description +.It \0\0\0machine dependent machine-check information +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. +.It trap type %d, code=%x, pc=%x +A unexpected trap has occurred within the system; the trap types are: +.Bd -literal -offset indent +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 +.Ed +.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. +.It init died +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. +.It out of mbufs: map full +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. +.El +.Pp +That completes the list of panic types you are likely to see. +.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 +.Xr savecore 8 +runs and preserves a copy of this core image and the current +system in a specified directory for later perusal. See +.Xr savecore 8 +for details. +.Pp +To analyze a dump you should begin by running +.Ic adb +with the +.Fl k +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 +.Dq $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 +.Dq Using ADB to Debug the UNIX Kernel . +.Sh SEE ALSO +.Xr gdb 1 , +.Xr reboot 8 +.br +.Dq VAX 11/780 System Maintenance Guide +and +.Dq VAX Hardware Handbook +for more information about machine checks. +.br +.Dq Using ADB to Debug the UNIX Kernel diff --git a/static/netbsd/man8/man8.vax/drtest.8 b/static/netbsd/man8/man8.vax/drtest.8 new file mode 100644 index 00000000..e67ddaa9 --- /dev/null +++ b/static/netbsd/man8/man8.vax/drtest.8 @@ -0,0 +1,112 @@ +.\" $NetBSD: drtest.8,v 1.16 2017/07/03 21:31:00 wiz Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)drtest.8 8.1 (Berkeley) 6/5/93 +.\" +.Dd February 17, 2017 +.Dt DRTEST 8 vax +.Os +.Sh NAME +.Nm drtest +.Nd stand-alone disk test program +.Sh DESCRIPTION +.Nm +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 +.Xr vax/format 8 ) , +you can check that +hard errors has been taken care of by running +.Nm . +No hard errors should be found, but in many cases +quite a few soft +.Tn ECC +errors will be reported. +.Pp +While +.Nm +is running, the cylinder number is printed on +the console for every 10th cylinder read. +.Sh EXAMPLES +A sample run of +.Nm +is shown below. +In this example (using a 750), +.Nm +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. +.Pp +.Bd -unfilled -offset indent -compact +.Li \&>>> Ns Sy B/3 +.Li \&%% +.Li \&loading hk(0,0)boot +.Li \&Boot +.Li \&: Sy \&hk(0,0)drtest +.Li Test program for stand-alone up and hp driver +.Pp +.Li Debugging level (1=bse, 2=ecc, 3=bse+ecc)? +.Li Enter disk name [type(adapter,unit),\ e.g.\ hp(1,3)]? Sy hp(0,0) +.Li Device data: #cylinders=1024, #tracks=16, #sectors=32 +.Li Testing hp(0,0), chunk size is 16384 bytes. +.Em (chunk\ size\ is\ the\ number\ of\ bytes read per disk access) +.Li Start ...Make sure hp(0,0) is online +.Li \ ... +.Em (errors are reported as they occur) +.Li \ ... +.Em (...program restarts to allow checking other disks) +.Em (...to abort halt machine with \&^P) +.Ed +.Sh DIAGNOSTICS +The diagnostics are intended to be self explanatory. Note, however, that +the device number +in the diagnostic messages is identified as +.Em typeX +instead of +.Em type(a,u) +where +.Ar X +\&= a*8+u, e.g., hp(1,3) becomes hp11. +.Sh SEE ALSO +.Xr bad144 8 , +.Xr vax/format 8 +.Sh HISTORY +The +.Nm +command appeared in +.Bx 4.2 . +.Sh AUTHORS +.An Helge Skrivervik diff --git a/static/netbsd/man8/man8.vax/format.8 b/static/netbsd/man8/man8.vax/format.8 new file mode 100644 index 00000000..9cfd7040 --- /dev/null +++ b/static/netbsd/man8/man8.vax/format.8 @@ -0,0 +1,295 @@ +.\" $NetBSD: format.8,v 1.14 2017/07/03 21:31:00 wiz Exp $ +.\" +.\" Copyright (c) 1980, 1983, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)format.8 8.1 (Berkeley) 6/5/93 +.\" +.Dd February 17, 2017 +.Dt FORMAT 8 vax +.Os +.Sh NAME +.Nm format +.Nd how to format disk packs +.Sh DESCRIPTION +There are two ways to format disk packs. The simplest is to +use the +.Nm +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 +.Nm , +then concludes with some remarks about using the DEC formatter. +.Pp +.Nm +is a standalone program used to format and check disks prior to +constructing file systems. +In addition to the formatting operation, +.Nm +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 +.Dq 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. +.Nm +may be used on any +.Tn UNIBUS +or +.Tn MASSBUS +drive supported by the +.Em up +and +.Em hp +device drivers which uses 4-byte headers (everything except RP's). +.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. +.Pp +.Nm +also has an option to perform an extended +.Dq 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. +.Pp +Each time +.Nm +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. +.Pp +Formatting a 400 megabyte disk on a +.Tn MASSBUS +disk controller usually takes about 20 minutes. +Formatting on a +.Tn UNIBUS +disk controller takes significantly longer. +For every hundredth cylinder formatted +.Nm +prints a message indicating the current cylinder being formatted. +(This message is just to reassure people that nothing is amiss.) +.Pp +.Nm +uses the standard notation of the standalone I/O library in +identifying a drive to be formatted. +A drive is specified as +.Em zz(x,y) , +where +.Em zz +refers to the controller type (either +.Em hp +or +.Em up ) , +.Em x +is the unit number of the drive; 8 times the +.Tn UNIBUS +or +.Tn MASSBUS +adaptor number plus the +.Tn MASSBUS +drive number or +.Tn UNIBUS +drive unit number; and +.Em y +is the file system partition on drive +.Em x +(this should always be 0). +For example, +.Dq hp(1,0) +indicates that drive 1 on +.Tn MASSBUS +adaptor 0 should be formatted; while +.Dq up(10,0) +indicates that +.Tn UNIBUS +drive 2 on +.Tn UNIBUS +adaptor 1 should be formatted. +.Pp +Before each formatting attempt, +.Nm +prompts the user in case debugging should be enabled in the +appropriate device driver. +A carriage return disables debugging information. +.Pp +.Nm +should be used prior to building file systems (with +.Xr newfs 8 +to ensure that all sectors with uncorrectable media errors are +remapped. +If a drive develops uncorrectable defects after formatting, either +.Xr bad144 8 +or +.Xr badsect 8 +should be able to avoid the bad sectors. +.Sh EXAMPLES +A sample run of +.Nm +is shown below. +In this example (using a +.Tn VAX-11/780 ) , +.Nm +is loaded from the console floppy; +on an 11/750 +.Nm +will be loaded from the root file system with +.Xr vax/boot 8 +following a +.Dq B/3 +command. +Boldface means user input. +As usual, +.Dq # +and +.Dq @ +may be used to edit input. +.Bd -literal -offset 0.5i +>>>\fBL FORMAT\fP + LOAD DONE, 00004400 BYTES LOADED +>>>\fBS 2\fP +Disk format/check utility +.sp +Enable debugging (0=none, 1=bse, 2=ecc, 3=bse+ecc)? \fB0\fP +Device to format? \fBhp(8,0)\fP +(\fIerror messages may occur as old bad sector table is read\fP) +Formatting drive hp0 on adaptor 1: verify (yes/no)? \fByes\fP +Device data: #cylinders=842, #tracks=20, #sectors=48 +Starting cylinder (0): +Starting track (0): +Ending cylinder (841): +Ending track (19): +Available test patterns are: +.Ed +.Bd -literal -offset 1.5i -compact +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) +.Ed +.Bd -literal -offset 0.5i -compact +Pattern (one of the above, other to restart)? \fB2\fP +Maximum number of bit errors to allow for soft ECC (3): +Start formatting...make sure the drive is online + ... +(\fIsoft ecc's and other errors are reported as they occur\fP) + ... +(\fIif 4 write check errors were found, the program terminates like this...\fP) + ... +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 +(\fI808272 is the block # of the first block in the bad sector table\fP) +Done +(\fI...program restarts to allow formatting other disks\fP) +(\fI...to abort halt machine with ^P\fP) +.Ed +.Sh DIAGNOSTICS +The diagnostics are intended to be self explanatory. +.Sh USING DEC SOFTWARE TO FORMAT +.Em Warning: These instructions are for people with 11/780 CPUs. +The steps needed for 11/750 or 11/730 CPU's are similar, but not +covered in detail here. +.Pp +The formatting procedures are different for each type of disk. +Listed here are the formatting procedures for RK07's, RP0X, and RM0X +disks. +.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. +.Ss Formatting an RK07 +Load the console floppy labeled, +.Dq RX11 VAX DSK LD DEV #1 +in the console disk drive, and type the following commands: +.Bd -literal -offset indent +>>>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 +.Ed +.Ss Formatting an RP0X +Follow the above procedures except that the +ATTACH and SELECT lines should read: +.Bd -literal -offset indent +DS>ATTACH RH780 SBI RH0 8 5 +DS>ATTACH RP0X RH0 DBA0 (RP0X is, e.g., RP06) +DS>SELECT DBA0 +.Ed +.Pp +This is for drive 0 on mba0; use 9 instead of 8 for mba1, etc. +.Ss Formatting an RM0X +Follow the above procedures except that the +ATTACH and SELECT lines should read: +.Bd -literal -offset indent +DS>ATTACH RH780 SBI RH0 8 5 +DS>ATTACH RM0X RH0 DRA0 +DS>SELECT DRA0 +.Ed +.Pp +Don't forget to put your UNIX console floppy back in the floppy disk +drive. +.Sh SEE ALSO +.Xr bad144 8 , +.Xr badsect 8 , +.Xr newfs 8 +.Sh BUGS +An equivalent facility should be available which operates under a +running UNIX system. +.Pp +It should be possible to reformat or verify part or all of a disk, +then update the existing bad sector table. diff --git a/static/netbsd/man8/man8.x68k/Makefile b/static/netbsd/man8/man8.x68k/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.x68k/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.x68k/boot.8 b/static/netbsd/man8/man8.x68k/boot.8 new file mode 100644 index 00000000..99586bf7 --- /dev/null +++ b/static/netbsd/man8/man8.x68k/boot.8 @@ -0,0 +1,241 @@ +.\" $NetBSD: boot.8,v 1.15 2014/08/16 08:43:12 apb Exp $ +.\" +.\" Copyright (c) 1980, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_i386.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd August 16, 2014 +.Dt BOOT 8 x68k +.Os +.Sh NAME +.Nm boot +.Nd system bootstrapping procedures +.Sh DESCRIPTION +.Ss Power fail and crash recovery +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. +.Ss Cold starts +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 +.Nx Ns Tn /x68k , +booting from SCSI disks (sd??) +and 2HD floppy disks (fd?a, fd?c) is currently supported. +.Ss Bootstrapping from a floppy +When the floppy disk is selected as the boot device, the initial +program loader of the IOCS (firmware) reads the +.Pa fdboot_ufs +program at the top of the disk, and then the fdboot_ufs program loads the +.Pa /boot +program from the FFS or LFS file system. +Normally, the +.Pa /boot +program then loads the +.Nx +kernel +.Pa /netbsd +from the same floppy. +In addition, the +.Pa /boot +program has abilities to uncompress gzip'ed kernels, to read +the kernel from other disks of other file systems etc (see below). +.Pp +For floppy disks, +.Pa fdboot_ustar +is also provided to read large +kernels which do not fit one a single floppy. +.Ss Bootstrapping from a SCSI hard disk +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 +.Nx +implementation of the IPL menu, +.Pa /usr/mdec/mboot , +does not have this functionality). +.Pp +Next, the IPL menu reads the OS-dependent boot program from the +top of the selected partition. +For +.Nx +FFS/LFS file systems +.Pa sdboot_ufs +is used. +The +.Pa sdboot_ufs +program then loads the +.Pa /boot +program from that partition. +.Ss Normal Operation +Once running, a banner similar to the following will appear: +.Bd -literal -offset indent +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 +.Ed +.Pp +After a countdown, the system image listed will be loaded. +(In the example above, it will be +.Dq Li sd0a:netbsd +which is the file +.Nm netbsd +on partition +.Dq a +of the +.Nx +SCSI hard disk of ID 0. +Pressing a key within the time limit will enter interactive mode. +.Ss Interactive mode +In interactive mode, the boot loader will present a prompt, allowing +input of these commands: +.Bl -tag -width helpx -offset indent +.It Ic boot Oo Ar device : Oc Ns Oo Ar filename Oc Oo Fl adqsv Oc +The default +.Ar device +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. +.Ar device +is of the form +.Xo +.Ar xd Ns Oo +.Ar N Ns Oo +.Ar x +.Oc +.Oc +.Xc +where +.Ar xd +is the device from which to boot, +.Ar N +is the unit number, and +.Ar x +is the partition letter. +.Pp +The following list of supported devices may vary from installation to +installation: +.Pp +.Bl -hang -compact +.It sd +SCSI disks on a controller recognized by the IOCS. +The unit number is the SCSI ID. +.It fd +Floppy drives as numbered by the IOCS. +.El +.Pp +The default +.Ar filename +is +.Pa netbsd ; +if the boot loader fails to successfully +open that image, it then tries +.Pa netbsd.gz +(expected to be a kernel image compressed by +.Xr gzip 1 ) . +Alternate system images can be loaded by just specifying the name of the image. +.Pp +Options are: +.Bl -tag -width xxx +.It Fl a +Prompt for the root file system device, the system crash dump +device, and the path to +.Xr init 8 . +.It Fl d +Bring the system up in debug mode. +Here it waits for a kernel debugger connect; see +.Xr ddb 4 . +.It Fl q +Boot the system in quiet mode. +.It Fl s +Bring the system up in single-user mode. +.It Fl v +Boot the system in verbose mode. +.El +.It Ic help +Print an overview about commands and arguments. +.It Ic ls Op Pa path +Print a directory listing of +.Pa path , +containing inode number, filename and file type. +.Pa path +can contain a device specification. +.It Ic halt +Reboot the system. +.El +.Ss Model-specific notes +Note for X68030+MC68030 systems: +Nothing special to be attended to; you can boot +.Nx +just like as +other operating systems such as Human68k and OS-9. +.Pp +Note for X68030/040turbo(68040 accelerator by BEEPs) systems: +.Nx +can boot under 040 mode. +It can also boot under 030 mode if you have MC68030 on the board. +.Pp +Note for X68000/Xellent30(68030 accelerator by TSR)+MC68030 systems: +In order to boot +.Nx , +you must choose 030 mode by using +.Pa CH30.SYS , +which must reside in the battery-backuped SRAM. +.Pp +Note for X68000/Jupiter-X(68040/060 accelerator by FTZ-net) systems: +The system must be in 040/060 processor mode. +.Sh FILES +.Bl -tag -width /usr/mdec/xxboot_ufs -compact +.It Pa /netbsd +system code +.It Pa /netbsd.gz +gzip-compressed system code +.It Pa /usr/mdec/xxboot_ufs +boot block (read by installboot), xx is disktype +.It Pa /usr/mdec/boot +source of /boot (can be just copied to the root directory) +.It Pa /boot +main part of the boot program +.El +.Sh SEE ALSO +.Xr reboot 2 , +.Xr disklabel 8 , +.Xr halt 8 , +.Xr reboot 8 , +.Xr shutdown 8 +.\" installboot(8) must be written diff --git a/static/netbsd/man8/man8.x68k/loadbsd.8 b/static/netbsd/man8/man8.x68k/loadbsd.8 new file mode 100644 index 00000000..a78d122e --- /dev/null +++ b/static/netbsd/man8/man8.x68k/loadbsd.8 @@ -0,0 +1,137 @@ +.\" $NetBSD: loadbsd.8,v 1.7 2023/12/23 20:15:19 andvar Exp $ +.Dd December 23, 2023 +.Dt LOADBSD 8 x68k +.Os +.Sh NAME +.Nm loadbsd +.Nd load and boot NetBSD/x68k kernel from Human68k +.Sh SYNOPSIS +.Nm loadbsd.x +.Op Fl hvV +.Op Fl abDNqs +.Op Fl r Ar root_device +.Ar kernel_file +.Sh DESCRIPTION +.Nm +is a program runs on Human68k. +It loads and executes the specified +.Nx Ns Tn /x68k +kernel. +.Pp +The options (for +.Nm +itself) are as follows: +.Bl -tag -width flag +.It Fl h +Show help and exit. +.It Fl N +Do not execute the kernel, if specified in combination with boot options. +.It Fl v +Enable verbose mode. +.It Fl V +Print version of +.Nm +and exit. +.El +.Pp +The options for +.Nx +kernel are as follows: +.Bl -tag -width flag +.It Fl a +Auto (multi-user) boot. +This disables +.Fl s +flag. +.It Fl b +Ask boot device during boot. +Pass +.Dv RB_ASKNAME +boot flag to the kernel. +.It Fl D +Enter kernel debugger. +Pass +.Dv RB_KDB +boot flag to the kernel. +.It Fl r Ar root_device +Specify boot device, which shall be mounted as root device. +The default device is +.Sq Li sd@0,0:a . +Note that the boot device name is +.Em not +the same as that of +.Nx . +See +.Sx BOOT DEVICE NAMES +below. +.It Fl q +Boot the system in quiet mode. +Pass +.Dv AB_QUIET +boot flag to the kernel. +.It Fl s +Single user boot. +Pass +.Dv RB_SINGLE +boot flag to the kernel. +This disables +.Fl a +flag. +This flag is set by default. +.El +.Pp +Although listed separately, the options may be in any order. +.Sh BOOT DEVICE NAMES +The format of boot device names is: +.Pp +.Dl "[/interface/]dev@unit[,lun][:partition]" +.Pp +.Bl -tag -width Fl +.It interface +SCSI interface type. +One of: +.Sq Li spc@0 , +.Sq Li spc@1 , +.Sq Li mha@0 . +If the dev is a SCSI device, and interface is omitted, +the current boot interface is used. +.It dev +Device type. +One of: +.Sq Li fd +(floppy disk drive), +.Sq Li sd +(SCSI disk), +.Sq Li cd +(SCSI CD-ROM), +.Sq Li md +(Memory disk). +.It unit +Device unit #. +You must specify the target SCSI ID if dev is a SCSI device. +.It lun +SCSI LUN #. +0 is assumed if omitted. +.It partition +Partition letter of device. +Partition +.Sq Li a +is used if omitted. +.El +.Sh FILES +.Bl -tag -width /usr/mdec/loadbsd.xxxx -compact +.It Pa /usr/mdec/loadbsd.x +You will find this program here. +.El +.Sh SEE ALSO +.Xr reboot 2 , +.Xr x68k/boot 8 +.Sh HISTORY +The +.Nm +utility first appeared in +.Nx 1.4 . +.Sh BUGS +.Nm +reads the entire kernel image at once, +and requires enough free area on the main memory. diff --git a/static/netbsd/man8/man8.x68k/newdisk.8 b/static/netbsd/man8/man8.x68k/newdisk.8 new file mode 100644 index 00000000..183750d6 --- /dev/null +++ b/static/netbsd/man8/man8.x68k/newdisk.8 @@ -0,0 +1,86 @@ +.\" $NetBSD: newdisk.8,v 1.12 2017/02/18 21:47:11 wiz Exp $ +.\" +.\" Copyright (c) 1998 MINOURA Makoto. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. All advertising materials mentioning features or use of this software +.\" must display the following acknowledgement: +.\" This product includes software developed by Minoura Makoto. +.\" 4. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt NEWDISK 8 x68k +.Os +.Sh NAME +.Nm newdisk +.Nd "Prepare a new disk to be usable for X680x0" +.Sh SYNOPSIS +.Nm +.Op Fl vnfcp +.Op Fl m Ar mboot +.Ar raw_device +.Sh DESCRIPTION +.Nm +prepares a new hard disk to be bootable from by X680x0. It should NOT be used +for floppy disks. +.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: +.Bl -tag -width flag +.It Fl v +Verbose mode. +.It Fl n +Dryrun mode. Nothing is written to the disk. +.It Fl f +Force. Usually, when +.Nm +detects existing disk mark, it aborts with some error messages. +.Fl f +option prevents this behaviour. +.It Fl c +Check only. +.Nm +looks at the disk whether it is already marked. +.It Fl p +Do not create the partition table. +.It Fl m Ar mboot +Specifies the mboot program to be written. +.El +.Sh FILES +.Bl -tag -width /usr/mdec/mboot -compact +.It Pa /usr/mdec/mboot +The default primary boot program. +.El +.Sh SEE ALSO +.Xr installboot 8 , +.Xr x68k/boot 8 +.Sh HISTORY +The +.Nm +utility first appeared in +.Nx 1.5 . +.Sh AUTHORS +.Nm +was written by +.An MINOURA Makoto Aq Mt minoura@NetBSD.org . diff --git a/static/netbsd/man8/man8.x86/Makefile b/static/netbsd/man8/man8.x86/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.x86/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.x86/boot.8 b/static/netbsd/man8/man8.x86/boot.8 new file mode 100644 index 00000000..d445bb17 --- /dev/null +++ b/static/netbsd/man8/man8.x86/boot.8 @@ -0,0 +1,1087 @@ +.\" $NetBSD: boot.8,v 1.40 2026/03/11 21:49:26 andvar Exp $ +.\" +.\" Copyright (c) 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" This code is derived from software written and contributed +.\" to Berkeley by William Jolitz. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_i386.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd October 9, 2025 +.Dt BOOT 8 x86 +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.Sh DESCRIPTION +Intel Architecture, 32-bit (IA-32) computers (the +.Tn IBM PC +and its clones) +that can run +.Nx Ns /i386 +or +.Nx Ns /amd64 +can use any of the following boot procedures, depending on what the hardware and +.Tn BIOS +support: +.Bl -tag -width "x86/pxeboot(8)" +.It boot +bootstrap +.Nx +from the system +.Tn BIOS +.It efiboot +bootstrap +.Nx +from the system +.Tn UEFI +.It Xr x86/dosboot 8 +bootstrap +.Nx +from +.Tn MS-DOS +.It Xr x86/pxeboot 8 +network bootstrap +.Nx +from a +.Tn TCP/IP +.Tn LAN +with +.Tn DHCP , +.Tn TFTP , +and +.Tn NFS . +.El +.Ss Power fail and crash recovery +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. +.Ss Cold starts +The 386 +.Tn "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 +.Nx +bootblocks are loaded and started either by the +.Tn BIOS , +or by a boot selector program (such as OS-BS, BOOTEASY, the OS/2 Boot Menu or +.Nx Ns 's +.No boot-selecting +master boot record - see +.Xr x86/mbr 8 ) . +.Ss Normal Operation +Once running, a banner similar to the following will appear: +.Bd -literal -offset indent +>> 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 +.Ed +.Pp +After a countdown, the system image listed will be loaded. +In the example above, it will be +.Dq Li hd0a:netbsd +which is the file +.Pa /netbsd +on partition +.Dq Li a +of the +.Nx +.Tn MBR +partition of the first hard disk known to the +.Tn BIOS +.Po +which is an +.Tn IDE +or similar device \(em see the +.Sx BUGS +section +.Pc . +.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. +.Pp +If present, the file +.Pa /boot.cfg +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 +.Xr boot.cfg 5 . +.Ss Boot Protocol +The +.Nx Ns /x86 +boot loader can boot a kernel using either the native +.Nx +boot protocol, or the +.Dq multiboot +protocol (which is compatible with some other operating systems). +In the native +.Nx +boot protocol, options are passed from the boot loader +to the kernel via flag bits in the +.Va boothowto +variable (see +.Xr boothowto 9 ) . +In the multiboot protocol, options are passed from the boot loader +to the kernel as strings. +.Ss Diagnostic Output +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 +.Xr x86/mbr 8 . +.Pp +If the first stage boot succeeds, the banner will be shown and the +error messages should be self-explanatory. +.Ss Interactive mode +In interactive mode, the boot loader will present a prompt, allowing +input of these commands: +.\" NOTE: much of this text is duplicated in the MI boot.8. +.\" Some of it is +.\" also duplicated in the x86-specific x86/dosboot.8 and x86/pxeboot.8; +.\" please try to keep all relevant files synchronized. +.Bl -tag -width 04n -offset 04n +.It Ic boot Oo Ar device Ns Ic \&: Oc Ns Oo Ar filename Oc Oo Fl 1234abcdmqsvxz Oc +The default +.Ar device +will be set to the disk from which the boot loader was loaded. +The partition is set to the first match in this list: +.Bl -enum +.It +The first +.Xr gpt 8 +partition with the +.Va bootme +attribute set. +.It +The partition from which the boot loader was loaded from, if that +can be detected. +.It +The first partition with a file system that could be bootable. +.It +The first partition. +.El +.Pp +To boot from an alternate disk, the full name of the device should +be given at the prompt. +.Ar device +is of the form +.Li NAME= Ns Ar partition_label +when booting from a +.Xr gpt 8 +partitioned disk. +Otherwise, the syntax is +.Xo Ar xd\^ Ns +.Op Ar N\^ Ns Op Ar x +.Xc +where +.Ar xd +is the device from which to boot, +.Ar N +is the unit number, and +.Ar x +is the partition letter. +.Pp +In the latter case, the following list of supported devices may +vary from installation to installation: +.Bl -hang +.It hd +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. +.It fd +Floppy drives as numbered by the BIOS. +.It cd +CD-ROM drives as numbered by the BIOS. +.It raid +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 +.Xr gpt 8 +partition that has the +.Va bootme +attribute set. +Inner RAIDframe partitions can also be given to the +.Ic dev +command using he +.Li NAME= Ns Ar partition_label +syntax. +.El +.Pp +The default +.Va filename +is +.Pa netbsd ; +if the boot loader fails to successfully +open that image, it then tries +.Pa netbsd.gz +(expected to be a kernel image compressed by gzip), followed by +.Pa onetbsd , +.Pa onetbsd.gz , +.Pa netbsd.old , +and finally +.Pa netbsd.old.gz . +.Pp +In support of the +.Dv KERNEL_DIR +build option (see +.Xr mk.conf 5 ) , +the boot loader will then try +.Pa netbsd/kernel , +.Pa netbsd/kernel.gz , +.Pa onetbsd/kernel , +.Pa onetbsd/kernel.gz , +.Pa netbsd.old/kernel , +and finally +.Pa netbsd.old/kernel.gz . +Alternate system images can be loaded by just specifying the filename of +the image. +If the specified +.Pa filename +does not contain an embedded or trailing slash character, the boot loader +will also try +.Pa filename/kernel +and +.Pa filename/kernel.gz . +(A leading slash character will be ignored.) +.Pp +Options are: +.Bl -tag -width xxx +.It Fl 1 +Sets the machine-dependent flag +.Dv RB_MD1 +in +.Va boothowto . +In +.Nx Ns /x86 , +this disables multiprocessor boot; +the kernel will boot in uniprocessor mode. +.It Fl 2 +Sets the machine-dependent flag +.Dv RB_MD2 +in +.Va boothowto . +In +.Nx Ns /x86 , +this disables ACPI. +.It Fl 3 +Sets the machine-dependent flag +.Dv RB_MD3 +in +.Va boothowto . +In +.Nx Ns /amd64 , +this disables SVS. +.It Fl 4 +Sets the machine-dependent flag +.Dv RB_MD4 +in +.Va boothowto . +In +.Nx Ns /x86 , +this has no effect. +.It Fl a +Sets the +.Dv RB_ASKNAME +flag in +.Va boothowto . +This causes the kernel to prompt for the root file system device, +the system crash dump device, and the path to +.Xr init 8 . +.It Fl b +Sets the +.Dv RB_HALT +flag in +.Va boothowto . +This causes subsequent reboot attempts to halt instead of rebooting. +.It Fl c +Sets the +.Dv RB_USERCONF +flag in +.Va boothowto . +This causes the kernel to enter the +.Xr userconf 4 +device configuration manager as soon as possible during the boot. +.Xr userconf 4 +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. +.It Fl d +Sets the +.Dv RB_KDB +flag in +.Va boothowto . +Requests the kernel to enter debug mode, in which it +waits for a connection from a kernel debugger; see +.Xr ddb 4 . +.It Fl m +Sets the +.Dv RB_MINIROOT +flag in +.Va boothowto . +Informs the kernel that a mini-root file system is present in memory. +.It Fl q +Sets the +.Dv AB_QUIET +flag in +.Va boothowto . +Boot the system in quiet mode. +.It Fl s +Sets the +.Dv RB_SINGLE +flag in +.Va boothowto . +Boot the system in single-user mode. +.It Fl v +Sets the +.Dv AB_VERBOSE +flag in +.Va boothowto . +Boot the system in verbose mode. +.It Fl x +Sets the +.Dv AB_DEBUG +flag in +.Va boothowto . +Boot the system with debug messages enabled. +.It Fl z +Sets the +.Dv AB_SILENT +flag in +.Va boothowto . +Boot the system in silent mode. +.El +.It Ic consdev Ar dev\| Ns Oo Ns Ic \&, Ns Ar speed Oc +[Not available for +.Xr x86/dosboot 8 ] +Immediately switch the console to the specified device +.Ar dev +and reprint the banner. +.Ar dev +must be one of +.\" .Bl -item -width com[0123]kbd -offset indent -compact +.Li pc , com0 , com1 , com2 , +.Li com3 , com0kbd , com1kbd , com2kbd , +.Li com3kbd , +or +.Li auto . +See +.Sx Console Selection Policy +in +.Xr x86/boot_console 8 . +.Pp +A +.Ar speed +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 +.Ar speed +with the +.Li pc +device is not possible. +.Pp +UEFI may support some USB and PCI-based serial ports. +See the +.Sx UEFI serial ports +section for details. +Using the +.Ic consdev +command without arguments lists the available ports. +.Ar com0 +to +.Ar com3 +are reserved for standard ISA serial ports, other ports are assigned to +.Ar com4 +and beyond. +The generic +.Ar com{unit}[,speed] +syntax can be used to select any port. +.Pp +Bootstrap can tell the kernel to use a USB-to-serial adapter for console +using the +.Ar ucom{unit}[,speed] +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 +.Xr userconf 4 +interactive mode cannot be used. +The default +.Ar ucom +speed is 115200. +.It Ic kconsdev Ar dev\| Ns Oo Ns Ic \&, Ns Ar speed Oc +Configure the kernel console like +.Ic consdev +but do not attempt to switch console in bootstrap. +This is useful when using a USB-to-serial adapter that is known as a +.Ar com +device in bootstrap but as a +.Ar ucom +device for the kernel. +One may use a syntax like: +.Bd -literal -offset indent +consdev com4,115200 +kconsdev ucom0,115200 +.Ed +Note that command ordering matters. +.It Ic dev Op Ar device +Set the default drive and partition for subsequent file system +operations. +Without an argument, print the current setting. +.Ar device +is of the form specified in +.Ic boot . +.It Ic devpath +[Only available for UEFI boot] Dump UEFI device paths. +.It Ic efivar +[Only available for UEFI boot] Dump UEFI environment variables from NVRAM. +.It Ic fs Ar file +[Only available for BIOS and UEFI boot] +Load a file system image from the specified +.Ar file , +and request the kernel to use it as the root file system. +The +.Xr makefs 8 +utility may be used to create suitable file system images. +.It Ic gop Op Va mode_index +[Only available for UEFI boot] Without argument, list the available +video modes. If an argument is given, select a video mode. +.It Ic help +Print an overview about commands and arguments. +.It Ic load Ar module Op Ar arguments +[Not available for +.Xr x86/dosboot 8 ] +Load the specified kernel +.Ar module , +and pass it the specified +.Ar arguments . +If the module name is not an absolute path, +.Bd -ragged -offset indent -compact +.Pa /stand/ Ns Xo Ns +.Aq Ar arch Ns +.Pa / Ns +.Aq Ar osversion Ns +.Pa /modules/ Ns +.Aq Ar module Ns +.Pa / Ns +.Aq Ar module Ns +.Pa .kmod +.Xc +.Ed +is used. +Possible uses of the +.Ic load +command include loading a memory disk image before booting a kernel, +or loading a +.Tn Xen +DOM0 kernel before booting the +.Tn Xen +hypervisor. +See +.Xr boot.cfg 5 +for examples. +.Pp +In addition to the +.Cm boot +options specified above, the +.Tn Xen +DOM0 kernel accepts +.Po Ar arguments +being separated with spaces +.Pc : +.Bl -tag -width xxx +.It Ic bootdev Ns = Ns Ar dev Po or Ic root Ns = Ns Ar dev Pc +Override the default boot device. +.Ar dev +is of the form +.Li NAME= Ns Ar partition_label +for +.Xr gpt 8 +partitioned disks. +It can also be a unit name +.Pq Ql wd0 , +or an interface name +.Po Ql bge0 , +.Ql wm0 , +\&... +.Pc +for cases where the root file system has to be loaded +from network (see the +.Sx BUGS +section in +.Xr x86/pxeboot 8 ) . +.It Ic console Ns = Ns Ar dev +Console used by DOM0 kernel during boot. +.Ar dev +accepts the same values as the ones given for the +.Cm consdev +command. +See +.Sx Console Selection Policy +in +.Xr x86/boot_console 8 . +.It Xo Ic ip Ns Li \&= Ns +.Ar my_ip Ns Li \&: Ns Ar serv_ip Ns Li \&: Ns Ar gw_ip Ns Li \&: Ns +.Ar mask Ns Li \&: Ns Ar host Ns Li \&: Ns Ar iface +.Xc +Specify various parameters for a network boot (IPs are in +dot notation), +each one separated by a colon: +.Bl -tag -width xxxxxxx +.It Ar my_ip +address of the host +.It Ar serv_ip +address of the NFS server +.It Ar gw_ip +address of the gateway +.It Ar mask +network mask +.It Ar host +address of the host +.It Ar iface +interface +.Po e.g., Dq Li xennet0 +or +.Dq Li eth0 +.Pc +.El +.It Ic nfsroot Ns = Ns Ar address Ns Li \&: Ns Ar rootpath +Boot the system with root on NFS. +.Ar address +is the address of the NFS server, and +.Ar rootpath +is the remote mount point for the root file system. +.It Ic pciback.hide Ns = Ns Ar pcidevs +Pass a list of PCI IDs for use with the PCI backend driver, +.Xr pciback 4 . +.Ar pcidevs +is formed of multiple IDs (in +.Ar bus Ns Li \&: Ns Ar device Ns Li \&. Ns Ar function +notation), +each ID being surrounded with brackets. +PCI domain IDs are currently ignored. +See +.Xr pciback 4 . +.El +.It Ic ls Op Ar path +[Not available for +.Xr x86/pxeboot 8 ] +Print a directory listing of +.Ar path , +containing inode number, filename, and file type. +.Ar path +can contain a device specification. +.It Ic memmap +[Only available for UEFI boot] Dump UEFI memory map. +.It Ic menu +[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. +.It Ic modules Bro Li \^on \ + No \(or Li off \ + No \(or Li enabled \ + No \(or Li disabled\^ \ + Brc +[Not available for +.Xr x86/dosboot 8 ] +The values +.Ql enabled , +.Ql on +will enable module loading for +.Ic boot +and +.Ic multiboot , +whereas +.Ql disabled , +.Ql off +will turn off the feature. +.It Ic mode Va fstype +[Only available for +.Xr x86/dosboot 8 ] +Switch file system type; +.Va fstype +should be one of +.Ar dos +or +.Ar ufs . +.It Ic multiboot Ar kernel Op Ar arguments +[Not available for +.Xr x86/dosboot 8 ] +Boot the specified +.Ar kernel , +using the +.Dq multiboot +protocol instead of the native +.Nx +boot protocol. +The +.Ar kernel +is specified in the same way as with the +.Ic boot +command. +.Pp +The multiboot protocol may be used in the following cases: +.Bl -tag -width indent +.It Nx Ns / Ns Xen No kernels +The +.Tn Xen +DOM0 kernel must be loaded as a module using the +.Ic load +command, and the +.Tn Xen +hypervisor must be booted using the +.Ic multiboot +command. +Options for the DOM0 kernel (such as +.Dq -s +for single user mode) must be passed as options to the +.Ic load +command. +Options for the hypervisor (such as +.Dq Li dom0_mem=256M +to reserve +.Pf 256 Tn MB +of memory for DOM0) +must be passed as options to the +.Ic multiboot +command. +See +.Xr boot.cfg 5 +for examples on how to boot +.Nx Ns / Ns Xen. +.It Nx No multiboot kernels +A +.Nx +kernel that was built with +.Cd options MULTIBOOT +(see +.Xr x86/multiboot 8 ) +may be booted with either the +.Ic boot +or +.Ic multiboot +command, passing the same +.Ar arguments +in either case. +.It Non- Ns Nx No kernels +A kernel for a +.No non- Ns Nx +operating system that expects to be booted using the +multiboot protocol (such as by the GNU +.Dq GRUB +boot loader) +may be booted using the +.Ic multiboot +command. +See the foreign operating system's documentation for the available +.Ar arguments . +.El +.It Ic pkboot +[Only available for BIOS and UEFI boot] Boot a kernel that has +the +.Cd KASLR +option set, for Kernel Address Space Layout Randomizaton. +.It Ic quit +Reboot the system. +.It Ic reloc Op Va default No \(or Va none No \(or Va address +[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 +.Cd SELFRELOC +option, so that can relocate itself at the right address, +otherwise a crash occurs at boot time. +.Bl -tag -width default +.It Va default +Copy the kernel at ELF header load address, this is the historical +behavior. +.It Va none +Leave the kernel where it was loaded and start it as is. +.It Va address +Copy the kernel at given +.Va address . +.El +.It Ic rndseed Ar file +[Only available for BIOS and UEFI boot] +Load the specified +.Ar file +and request the kernel to use it as a seed for the +.Xr rnd 4 +random number generator. +The +.Ar file +should be in the private format used by +.Xr rndctl 8 , +and should have been saved by +.Ql "rndctl -S" +shortly before the previous shutdown. +See the +.Va random_seed +and +.Va random_file +variables in +.Xr rc.conf 5 , +and the +.Pa /etc/rc.d/random_seed +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. +.It Ic root Ar spec +[Only available for BIOS and UEFI boot] +Pass an explicit root specification to the kernel. +See BTINFO_ROOTDEVICE for details. +.It Ic splash Ar file +[Only available for BIOS and UEFI boot] +Load a graphical image from the specified +.Ar file +and request the kernel to use it as a splash screen. +The +.Ar file +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. +.It Ic text Op Va mode_index +[Only available for UEFI boot] Without argument, list the available +text modes (displayed as column x line in hexadecimal, therefore +.Li 50x19 +means +.Li 80 +columns and +.Li 25 +lines). With an argument, select a text mode. +.It Ic userconf Ar command +[Not available for +.Xr x86/dosboot 8 ] +Pass command +.Ar command +to +.Xr userconf 4 +at boot time. +These commands are processed before the interactive +.Xr userconf 4 +shell is executed, if requested. +.It Ic version Op Ar full +[Only available for UEFI boot] Display UEFI bootstrap version. With the +.Op full +argument, also display information about UEFI itself. +.It Ic vesa Bro Ar \^modenum \ + No \(or Li on \ + No \(or Li off \ + No \(or Li enabled \ + No \(or Li disabled \ + No \(or Li list Brc +[Only available for BIOS and +.Xr x86/pxeboot 8 ] +Initialise the video card to the specified resolution and bit depth. +The +.Ar modenum +should be in the form of +.Ql 0x100 , +.Ql 800x600 , +.Ql 800x600x32 . +The values +.Ql enabled , +.Ql on +put the display into the default mode, and +.Ql disabled , +.Ql off +returns the display into standard vga mode. +The value +.Ql list +lists all supported modes. +.El +.Pp +In an emergency, the bootstrap methods described in the +.Nx +installation notes for the x86 architectures +can be used to boot from floppy or other media, +or over the network. +.Ss Locating the root file system +The kernel uses information from the bootloader to locate the +file system to mount as root. +There are three methods: +.Bl -tag -width 04n -offset 04n +.\" XXX: what this .Va is supposed to mean? +.It Dv BTINFO_ROOTDEVICE Va from +.Xr boot.cfg 5 +or multiboot. +The bootloader passes the root device name as driver, unit, and +partition (like +.Ql sd0a Ns ). +This will be automatically substituted by a +.Xr dk 4 +wedge if one is discovered. +.Pp +If the bootloader passes a wedge name as +.Dq Li wedge: +or +.Dq Li NAME= +followed by the name. +The kernel will search for a +.Xr dk 4 +device with that name. +.It Dv BTINFO_BOOTWEDGE Va determined by bootblock +The bootloader passes start offset and length of a hard disk partition +and a offset, size and hash of a +.Dq 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. +.Pp +An additional partition number is provided if the bootloader also +passed a +.Dv BTINFO_BOOTDISK +record. +This (or partition +.Ql a ) +will be used +by the kernel as a fallback if there is no matching wedge. +.It Dv BTINFO_BOOTDISK Va determined by bootblock +This uses the device number passed by the +.Tn BIOS +that distinguishes between floppy, hard drive and +.Tn CD-ROM +boot. +.Bl -tag -width xxx +.It Floppy +The kernel searches for the +.Xr fd 4 +device with the correct unit, the partition number is used +to select a specific disk format. +See +.Xr fd 4 +for details. +.It Hard drive +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. +.It Tn CDROM +The +.Tn BIOS +does not distinguish between multiple +.Tn CD +devices. +The kernel searches for the first +.Xr cd 4 +device. +So you can only boot from unit 0. +.El +.El +.Sh UEFI serial ports +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. +.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 +.Ar 0x0403 +and +.Ar 0x6001. +.Pp +To use it, obtain the +.Pa FtdiUsbSerialDxe.efi +driver from Tianocore EDK2 and save it in the EFI bootstrap partition, +for instance in +.Pa /EFI/EDK2/FtdiUsbSerialDxe.efi +then create a +.Pa /EFI/boot/startup.nsh +script containing something like +.Bd -literal -offset indent +FS0: +load \\EFI\\EDK2\\FtdiUsbSerialDxe.efi +bootx64.efi +.Ed +.Pp +Then make sure UEFI boots into the UEFI shell. +If it is not available in the built-in options, +.Pa Shell.efi +can be obtained from Tianocore EDK2 and installed in +.Pa /EFI/boot/Shell.efi . +.Sh FILES +.Bl -tag -width /usr/mdec/bootxx_fstype -compact +.It Pa /boot +boot program code loaded by the primary bootstrap +.It Pa /boot.cfg +optional configuration file +.It Pa /netbsd +system code +.It Pa /netbsd.gz +gzip-compressed system code +.It Pa /usr/mdec/boot +master copy of the boot program (copy to /boot) +.It Pa /usr/mdec/bootxx_fstype +primary bootstrap for file system type fstype, copied to the start of +the +.Nx +partition by +.Xr installboot 8 . +.It Pa /usr/mdec/bootia32.efi +.It Pa /usr/mdec/bootx64.efi +.Tn UEFI +bootstraps for +.Nx Ns /i386 +and +.Nx Ns /amd64 , +which should be copied to the +.Pa /EFI/boot +directory in a +.Tn FAT +formatted partition of type +.Tn EFI +(either +.Xr x86/mbr 8 +or +.Xr gpt 8 , +see the +.Sx BUGS +section). +.Nx +.Tn UEFI +bootstrap reads its configuration from the +.Pa /EFI/NetBSD/boot.cfg +file in the +.Tn EFI +partition. +.El +.Sh SEE ALSO +.Xr ddb 4 , +.Xr fd 4 , +.Xr pciback 4 , +.Xr userconf 4 , +.Xr boot.cfg 5 , +.Xr halt 8 , +.Xr installboot 8 , +.Xr reboot 8 , +.Xr rescue 8 , +.Xr shutdown 8 , +.Xr x86/boot_console 8 , +.Xr x86/dosboot 8 , +.Xr x86/mbr 8 , +.Xr x86/multiboot 8 , +.Xr x86/pxeboot 8 , +.Xr boothowto 9 +.Sh BUGS +The kernel file name must be specified before, not after, the boot options. +Any +.Ar filename +specified after the boot options, e.g.: +.Pp +.Dl boot -d netbsd.test +.Pp +is ignored, and the default kernel is booted. +.Pp +Hard disks are always accessed by +.Tn BIOS +functions. +Unit numbers are +.Tn BIOS +device numbers which might differ from numbering in the +.Nx +kernel or physical parameters +.Po +e.g., +.Tn SCSI +slave numbers +.Pc . +There isn't any distinction between +.Dq sd +and +.Dq 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 +.Dq type +field of the +.Nx +disklabel (if it is a hard disk). +.Pp +.Tn UEFI +implementations are supposed to support either +.Xr x86/mbr 8 +or +.Xr gpt 8 +partitioning, but some do not handle the latter. +.Tn UEFI +booting +from a +.Xr gpt 8 +partitioned disk is still possible in this case, by adding +an overlapping +.Tn EFI +partition in the protective +.Xr x86/mbr 8 +block. +This can be achieved using the following commands +(you must adapt the hard disk and +.Tn EFI +partition start end size to fit your setup): +.Bd -literal -offset indent +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 +.Ed +.Pp +The resulting +.Xr x86/mbr 8 +partition table will look like this: +.Bd -literal -offset indent +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> +.Ed diff --git a/static/netbsd/man8/man8.x86/boot_console.8 b/static/netbsd/man8/man8.x86/boot_console.8 new file mode 100644 index 00000000..3da8af86 --- /dev/null +++ b/static/netbsd/man8/man8.x86/boot_console.8 @@ -0,0 +1,147 @@ +.\" $NetBSD: boot_console.8,v 1.4 2017/02/18 21:39:53 wiz Exp $ +.\" +.\" Copyright (c) 1997 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt BOOT_CONSOLE 8 x86 +.Os +.Sh NAME +.Nm boot_console +.Nd selection of a console device in the x86 bootloader +.\" +.Sh DESCRIPTION +The +.Nx +x86 bootloader selects a console device for its user interaction and +passes information about it to the +.Nx +kernel. +When booting from the system BIOS, the console device and properties +are saved in the primary bootstrap by +.Xr installboot 8 . +For other boot procedures (such as +.Xr x86/dosboot 8 ) +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. +.\" +.Ss Serial Console Options +The compile-time options (to be set in the booter's +.Dq Makefile ) +are: +.Bl -ohang +.It Sy SUPPORT_SERIAL= Ns Fa policy +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 +.Sx Console Selection Policy +below for valid values of +.Fa policy . +.It Sy DIRECT_SERIAL +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. +.It Sy CONSPEED= Ns Fa integer +sets the baud-rate for the serial console. +This option has only an effect when used in combination with the +.Dq Dv DIRECT_SERIAL +option above, otherwise, the default setting of 9600 baud is used. +The value of +.Fa integer +must be something that makes sense as a serial port baud rate. +.It Sy COMCONS_KEYPRESS +Require a character input within seven (7) seconds from serial console +device to be selected. +.El +.\" +.Ss Console Selection Policy +The actual policy for the console selection is determined by the value +of +.Dq Dv SUPPORT_SERIAL +The following options are available: +.Bl -ohang +.It Em CONSDEV_PC +Force use of the standard PC keyboard and display as the console. +.It Em CONSDEV_COM0 Li ... Em CONSDEV_COM3 +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 +.Dq Dv CONSDEV_PC . +(Note: This feature can be deliberately used for console selection if +the serial ports have been disabled in the BIOS.) +.It Em CONSDEV_COM0KBD Li ... Em CONSDEV_COM3KBD +If the port is known to the BIOS, and output of a character to the port +succeeds (and if +.Dq Dv DIRECT_SERIAL +is defined the RS-232 +.Dq "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 +.Dq Dv CONSDEV_PC . +.It Em CONSDEV_AUTO +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 +.Dq Dv DIRECT_SERIAL +is defined the RS-232 +.Dq "modem ready" +status is on after the character is output), the port is used as console. +If no serial port passes the check, +.Dq Dv CONSDEV_PC +is used. +The progress of the selection process is shown at the PC display as +digits corresponding to the serial port number currently probed. +.El +.\" +.Sh FILES +.Bl -tag -width src/sys/arch/i386/stand/{boot,pxeboot}/Makefile +.It Pa src/sys/arch/i386/stand/{boot,pxeboot}/Makefile +compile time options for the boot programs. +.El +.\" +.Sh SEE ALSO +.Xr console 4 , +.Xr installboot 8 , +.Xr x86/boot 8 +.\" +.Sh BUGS +The serial communication parameters (byte-size, parity, stop-bits) are +not settable (either at compile time or run time). +The default parameters are +.Dq "8 N 1" . +.Pp +The baud rate is not settable when using BIOS I/O. +It should be settable at compile time with +.Dq Dv CONSPEED +just as it is when using +.Dq Dv DIRECT_SERIAL . +The default speed is 9600 baud (the maximum for BIOS I/O). diff --git a/static/netbsd/man8/man8.x86/dosboot.8 b/static/netbsd/man8/man8.x86/dosboot.8 new file mode 100644 index 00000000..90ad455f --- /dev/null +++ b/static/netbsd/man8/man8.x86/dosboot.8 @@ -0,0 +1,163 @@ +.\" $NetBSD: dosboot.8,v 1.4 2023/04/24 13:55:45 manu Exp $ +.\" +.\" Copyright (c) 1997 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_i386.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd February 17, 2017 +.Dt DOSBOOT 8 x86 +.Os +.Sh NAME +.Nm dosboot +.Nd boot NetBSD/x86 from DOS +.Sh SYNOPSIS +.Nm +.Op Fl u +.Op Fl c Ar command +.Op Fl i +.Op Ar path Op Fl adqsv +.Sh DESCRIPTION +.Nm +is an +.Tn MS-DOS +program. +It is a boot loader for +.Nx Ns Tn /x86 +designed to permit +.Nx +to be booted directly from +.Tn MS-DOS . +By default, it boots a file with name +.Pa NETBSD +in the current +.Tn MS-DOS +directory. +.Nm +shares common code with the standard boot loader, +.Xr x86/boot 8 . +.Pp +The recognized options are: +.Bl -tag -width "-adqsv" -offset 04n +.It Fl c +Execute +.Ar command +(see below). +.It Fl i +Enter interactive mode. +.Nm +will present a prompt, allowing input of commands (see below). +.It Fl u +Boot from a UFS file system instead of an +.Tn MS-DOS +file system. +.It Ar path +Specifies the kernel file. +In +.Tn MS-DOS +mode (default) a normal +.Tn MS-DOS +filename (with or without drive specification) is accepted. +In UFS mode (after +.Fl u +or after a +.Ic mode ufs +command), a path in a +.Nx +file system is expected. +By default, the file is looked up in partition +.Sq a +of the first hard disk. +Another device or partition can be specified +by prepending a block device name in terms of +.Nx , +followed by a colon (see +.Xr x86/boot 8 +and examples). +.It Fl 1234abcdmqsvxz +Flags passed to the kernel, see +.Xr x86/boot 8 . +.El +.Pp +See +.Xr x86/boot 8 +for commands accepted after the +.Fl c +flag or in interactive mode. +.Pp +.Nm +is also installed in the +.Xr release 7 +hierarchy, under +.Pa installation/misc/dosboot.com . +.Sh FILES +.Pa /usr/mdec/dosboot.com +.Sh EXAMPLES +To boot a +.Nx +kernel located on +.Tn MS-DOS +drive D, one would issue: +.Bd -literal -offset indent +dosboot D:\eNODOS\eNETBSD +.Ed +.Pp +To boot from a +.Nx +floppy into single user mode, type e.g.: +.Bd -literal -offset indent +dosboot -u fd0a:netbsd -s +.Ed +.Sh SEE ALSO +.Xr release 7 , +.Xr x86/boot 8 +.Sh HISTORY +The +.Nx Ns Tn /x86 +.Nm +command first appeared in +.Nx 1.3 . +.Sh BUGS +.Nm +assumes that the processor is in real mode at startup. +It does not work well in the presence of +.Tn MS-DOS +extenders and memory managers. +.Pp +.Nm +does not run directly under +.Tn Windows 95 . +.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 +.Nx +kernel. +.Pp +In +.Tn MS-DOS +mode, no useful boot device specification is passed to +.Nx . +It is necessary to have the root device hardwired into the kernel +configuration or to enter it manually. diff --git a/static/netbsd/man8/man8.x86/mbr.8 b/static/netbsd/man8/man8.x86/mbr.8 new file mode 100644 index 00000000..1113953d --- /dev/null +++ b/static/netbsd/man8/man8.x86/mbr.8 @@ -0,0 +1,135 @@ +.\" $NetBSD: mbr.8,v 1.5 2021/06/22 03:30:06 gutteridge Exp $ +.Dd February 17, 2017 +.Dt MBR 8 x86 +.Os +.Sh NAME +.Nm mbr , +.Nm bootselect +.Nd Master Boot Record bootcode +.Sh DESCRIPTION +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). +.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. +.Pp +.Nx +supplies several versions of the MBR bootcode: +.Bl -tag -width 20 +.It Sy Normal boot code Pa /usr/mdec/mbr +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. +.It Sy Bootselector Pa /usr/mdec/mbr_bootsel +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 +.Xr fdisk 8 . +.It Sy Extended Bootselector Pa /usr/mdec/mbr_ext +The extended bootselecting MBR additionally allows +.Nx +to be loaded from an Extended partition. +It only supports systems whose BIOS supports the extensions to +boot partitions beyond the 8 Gigabyte boundary. +.It Sy Serial Bootselector Pa /usr/mdec/mbr_com0 +This has the same features as +.Pa mbr_ext +but will read and write from the first serial port. +It assumes that the BIOS has initialized the baud rate. +.It Sy Serial Bootselector Pa /usr/mdec/mbr_com0_9600 +This has the same features as +.Pa mbr_com0 . +Additionally, it initializes the serial port to 9600 baud. +.El +.Pp +The rest of this manual page will discuss the bootselecting versions of +the MBR. +The configurable items of the bootselector are: +.Bl -tag -width Er +.It timeout +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. +.It default +The default partition or disk to boot from, should the timeout +expire. +.El +.Pp +The bootselector will output a menu of the +.Em bootmenu +names for each partition (as configured by +.Xr fdisk 8 ) . +The user can then select the partition +or drive to boot from via the keyboard. +.Pp +The numeric keys +.Sy 1 +upwards will initiate a startup from the corresponding partition. +.Pp +Function keys +.Sy F1 +through +.Sy F8 +(keys +.Sy a +through +.Sy h +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. +.Pp +The +.Sy Enter +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. +.Sh DIAGNOSTICS +The following errors are detected: +.Bl -column Code "No active partition" +.It Em Code Ta Em "Text message" Ta Em Explanation +.It 1 Ta "No active partition" Ta +The MBR has a partition table without an active partition. +.It 2 Ta "Disk read error" Ta +There was an error reading the bootsector for the partition or +drive selected. +.It 3 Ta "No operating system" Ta +The bootsector was loaded successfully, but it was not valid (i.e., +the magic number check failed, or it contained no code). +.It L Ta "Invalid CHS read" Ta +The boot partition cannot be read using a CHS read and the system BIOS +doesn't support LBA reads. +.It ? Ta "" Ta +Unknown key. +.El +.Pp +The standard boot code will output the text message and stop. +It may be necessary to reset to the system to continue. +.Pp +The bootselect code will output 'Error <code>' and await further input. +.Sh SEE ALSO +.Xr disklabel 8 , +.Xr fdisk 8 , +.Xr installboot 8 , +.Xr mbrlabel 8 , +.Xr x86/boot 8 +.Sh BUGS +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). +.Pp +The error messages are necessarily terse. diff --git a/static/netbsd/man8/man8.x86/multiboot.8 b/static/netbsd/man8/man8.x86/multiboot.8 new file mode 100644 index 00000000..12d52a49 --- /dev/null +++ b/static/netbsd/man8/man8.x86/multiboot.8 @@ -0,0 +1,115 @@ +.\" $NetBSD: multiboot.8,v 1.1 2013/07/31 21:01:13 soren Exp $ +.\" +.\" Copyright (c) 2006 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Julio M. Merino Vidal. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd October 25, 2006 +.Dt MULTIBOOT 8 x86 +.Os +.Sh NAME +.Nm multiboot +.Nd procedure for booting NetBSD/x86 from a Multiboot-compliant boot loader +.Sh DESCRIPTION +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 +.Nx +kernel supports Multiboot if it was compiled with +.Cd options MULTIBOOT +(the default in the +.Sq GENERIC +and +.Sq GENERIC_LAPTOP +configurations). +.Pp +Unlike when using the native boot loader, the +.Nx +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 +.Nx +kernel. +.Pp +The following arguments are recognized: +.Bl -tag -width consoleXspeedX +.It Va console +Specifies the console device name. +Can be one of +.Sq com +or +.Sq pc . +If the former, +.Va console_addr +and +.Va console_speed +should be given too. +.It Va console_addr +Specifies the serial port address for the console. +Defaults to the value of +.Cd options CONADDR +or +.Sq 0x3f8 +if this was not given. +.It Va console_speed +Specifies the serial port speed for the console. +Defaults to the value of +.Cd options CONSPEED +or +.Sq 9600 +if this was not given. +.It Va root +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: +.Sq root=wd0e . +.El +.Ss Booting with GRUB Legacy +GRUB Legacy is the most popular bootloader that supports Multiboot. +You can boot a +.Nx +kernel (assuming it is compiled with Multiboot support) with a line +similar to the following one: +.Bd -literal +kernel (fd0)/netbsd.gz -c console=pc root=wd0e +.Ed +.Sh SEE ALSO +.Xr options 4 +.Sh HISTORY +.Nm +support first appeared in +.Nx 4.0 . +.Sh AUTHORS +.Nm +support was added by +.An Julio M. Merino Vidal Aq Mt jmmv@NetBSD.org . diff --git a/static/netbsd/man8/man8.x86/pxeboot.8 b/static/netbsd/man8/man8.x86/pxeboot.8 new file mode 100644 index 00000000..bf8bfaec --- /dev/null +++ b/static/netbsd/man8/man8.x86/pxeboot.8 @@ -0,0 +1,401 @@ +.\" $NetBSD: pxeboot.8,v 1.6 2023/04/24 13:55:45 manu Exp $ +.\" +.\" Copyright (c) 2003 +.\" Matthias Drochner. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd February 17, 2017 +.Dt PXEBOOT 8 x86 +.Os +.Sh NAME +.Nm pxeboot +.Nd network boot NetBSD/x86 through a PXE BIOS extension +.Sh DESCRIPTION +.Nm +is a +.Nx +boot program running on top of a +.Tn PXE +.Tn BIOS +extension which is +provided by the motherboard or a plug-in network adapter, +in accordance with the +.Tn Intel +Preboot eXecution Environment +.Pq Tn PXE +specification. +.Pp +By default, the +.Nm +program is configured with modules loading and +.Xr boot.cfg 5 +support disabled. +See +.Sx EXAMPLES +for how to enable these options individually. +This manual page assumes that +.Xr boot.cfg 5 +support is enabled. +.Pp +Network booting a system through +.Tn PXE +is a two-stage process: +.Pp +.Bl -enum +.It +The +.Tn PXE +.Tn BIOS +issues a +.Tn DHCP +request and fetches the +.Nx +.Nm +program using +.Tn TFTP . +.It +The +.Nx +.Nm +program takes control. +It immediately issues another +.Tn DHCP +request to get the name of a +.Xr boot.cfg 5 +file to load, using +.Dq 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 +.Xr boot.cfg 5 . +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 +.Ic boot +command, another +.Tn DHCP +request is issued and the kernel filename returned by the +.Tn DHCP +reply, using +.Dq netbsd +by default, +is loaded. +To read the kernel file, the +.Tn NFS +.Pq version 2 +or +.Tn TFTP +protocols can be used. +.El +.Pp +The +.Tn DHCP +request issued by the +.Nx +.Nm +program has the following special parameters: +.Bl -tag -width xxxx +.It Bootfile name +is set to +.Dq boot.cfg +during the first request, and then to +the +.Va filename +argument on the +.Ic boot +command line typed in by the user (can be empty), using +.Dq netbsd +in the non-interactive case. +.It DHCP Vendor class identifier tag +is set to +.Dq NetBSD:i386:libsa . +.El +.Pp +The +.Tn DHCP +server can use these fields (i.e. the +.Tn DHCP +vendor class identifier tag and the requested file name, possibly +supplied by the user's command line input to the +.Nm +program) to distinguish between the various originators of requests +(PXE BIOS, first and second +.Nm +stage, +.Nx +kernel), and to alter its behaviour. +For example, this can be used to support alternative +.Nx +installations on one machine. +.Pp +In addition to the standard network interface configuration, +the following fields in the +.Tn DHCP +reply are interpreted: +.Bl -tag -width xxxx +.It Bootfile name +specifies the protocol to be used, and the filename of the +boot config or +.Nx +kernel to be booted, separated by a colon. +Available protocols are +.Dq nfs +and +.Dq tftp . +The boot config or kernel filename part is interpreted relatively to +the NFS root directory (see the +.Em Root path +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 +.Em Bootfile name +field replied by the DHCP server does not contain a colon, +it is ignored, and the +.Va filename +typed in at the +.Nm +command line prompt (or the +.Dq netbsd +default, see the section about the +.Em Bootfile name +field in the DHCP request above) is used. +If no protocol was specified, +.Dq nfs +is assumed. +.It Next server +is used as the location of the tftp server. +.It Swap server +can be used to override the +.Dq server IP address +if +.Tn NFS +is used to access the kernel. +This matches the behaviour of the +.Nx +kernel to access its root file system on +.Tn NFS . +This way, different +.Tn TFTP +and +.Tn NFS +servers can be communicated to +the +.Tn DHCP +client +.Po +it is actually a deficiency of the +.Tn DHCP +protocol to provide a +.Dq root path +field but no corresponding IP address +.Pc . +.It Root path +is used as path to be mounted in the +.Tn NFS +case to access the kernel file, matching the +.Nx +kernel's behaviour. +.El +.Pp +See +.Xr x86/boot 8 +for the commands accepted in interactive mode. +.Pp +By default the output from +.Nm +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 +.Nm installboot +to modify the boot options contained in the +.Pa pxeboot_ia32.bin +file. +.Sh FILES +.Bl -tag -width /usr/mdec/pxeboot_ia32.bin +.It Pa /usr/mdec/pxeboot_ia32.bin +.El +.Sh EXAMPLES +To enable +.Xr boot.cfg 5 +support in the +.Nm +program: +.Bd -literal -offset indent +installboot -e -o bootconf pxeboot_ia32.bin +.Ed +.Pp +To enable modules loading support in the +.Nm +program: +.Bd -literal -offset indent +installboot -e -o modules pxeboot_ia32.bin +.Ed +.Pp +The first +.Pa /etc/dhcpd.conf +example shows a simple configuration which just loads +.Dq boot.cfg +and +.Dq 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. +.Pp +.Bd -literal +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"; +} +.Ed +.Pp +The following +.Pa /etc/dhcpd.conf +entry sets loads the boot config and kernel over tftp. +This can be used, for example, for installing machines by using +an install kernel. +.Pp +.Bd -literal +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"; + } + } +} +.Ed +.Pp +The following +.Pa /etc/dhcpd.conf +entry shows how different system installations can be booted depending on +the user's input on the +.Nm +command line. +.Pp +.Bd -literal +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"; + } + } +} +.Ed +.Pp +The +.Tn TFTP +server is supplied using the +.Em next-server +directive. +The +.Tn NFS +server for the root file system is +.Em mynfsserver . +The +.Em swap-server:root-path +is only used in the +.Tn NFS +case and by the +.Nx +kernel to mount the root file system. +.Sh SEE ALSO +.Xr boot.cfg 5 , +.Xr dhcpd 8 , +.Xr diskless 8 , +.Xr installboot 8 , +.Xr x86/boot 8 +.Rs +.%T Preboot Execution Environment (PXE) Specification +.%N Version 2.1 +.%D September 20, 1999 +.%A Intel Corporation +.Re +.Sh HISTORY +The +.Nx Ns Tn /x86 +.Nm +command first appeared in +.Nx 1.6 . +.Sh BUGS +If an error is encountered while reading the +.Nx +kernel file or if its file format wasn't recognized, it is +impossible to retry the operation because the +.Tn PXE +network stack is already removed from the system RAM. +.Pp +You need the +.Nm +from an i386 build to boot an i386 kernel, +and that from an amd64 build to boot an amd64 kernel. +.Pp +In a +.Tn Xen +setup, the +.Nx +DOM0 kernel is loaded as a module, and cannot know the device +from which the +.Tn 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 +.Ar bootdev , +to the DOM0 kernel as explained +in the +.Cm load +command subsection in +.Xr x86/boot 8 . diff --git a/static/netbsd/man8/nis.8 b/static/netbsd/man8/nis.8 new file mode 100644 index 00000000..6ca48904 --- /dev/null +++ b/static/netbsd/man8/nis.8 @@ -0,0 +1,180 @@ +.\" $NetBSD: nis.8,v 1.3 2009/10/24 12:21:31 reed Exp $ +.\" +.\" Copyright (c) 1992/3 Theo de Raadt <deraadt@fsa.ca> +.\" All rights reserved. +.\" Portions Copyright (c) 1994 Jason R. Thorpe. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote +.\" products derived from this software without specific prior written +.\" permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS +.\" OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY +.\" DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.Dd February 26, 2005 +.Dt NIS 8 +.Os +.Sh NAME +.Nm nis , +.Nm yp +.Nd description of the NIS (formerly YP) subsystem +.Sh SYNOPSIS +.Nm ypbind +.Op Fl ypset +.Nm ypbind +.Op Fl ypsetme +.Pp +.Nm ypset +.Op Fl h Ar host +.Op Fl d Ar domain +.Ar server +.Pp +.Nm yppoll +.Op Fl h Ar host +.Op Fl d Ar domain +.Ar mapname +.Pp +.Nm ypcat +.Op Fl kt +.Op Fl d Ar domainname +.Ar mapname +.Nm ypcat +.Fl x +.Pp +.Nm ypmatch +.Op Fl kt +.Op Fl d Ar domainname +.Ar key ... mapname +.Nm ypmatch +.Fl x +.Pp +.Nm ypwhich +.Op Fl d Ar domain +.Oo +.Op Fl t +.Fl m Op Ar mname +| +.Ar host +.Oc +.Nm ypwhich +.Fl x +.Pp +.Nm ypserv +.Op Fl d +.Op Fl x +.Pp +.Nm yppush +.Op Fl d Ar domainname +.Op Fl h Ar hostname +.Op Fl v +.Ar mapname +.Pp +.Nm ypxfr +.Op Fl bcf +.Op Fl d Ar domain +.Op Fl h Ar host +.Op Fl s Ar domain +.Op Fl C Ar tid prog ipadd port +.Ar mapname +.Pp +.Nm ypinit +.Fl m +.Op Ar domainname +.Nm ypinit +.Fl s +.Ar master_server +.Op Ar domainname +.Pp +.Nm yptest +.Pp +.Nm rpc.yppasswdd +.Op Fl noshell +.Op Fl nogecos +.Op Fl nopw +.Op Fl m Ar arg1 arg2 ... +.Sh DESCRIPTION +The +.Tn NIS +subsystem allows network management of passwd and group file +entries through the functions +.Xr getpwent 3 +and +.Xr getgrent 3 . +.Tn NIS +also provides hooks for other client programs, such as +.Xr amd 8 +and +.Xr rpc.bootparamd 8 , +that can use +.Tn NIS +maps. +.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 +.Dq 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 +.Pa /var/yp/Makefile.yp . +.Pp +The +.Tn NIS +subsystem is conditionally started in +.Pa /etc/rc . +See the +.Pa /etc/rc.conf +file for configuration variables. +.Sh SEE ALSO +.Xr domainname 1 , +.Xr ypcat 1 , +.Xr ypmatch 1 , +.Xr ypwhich 1 , +.Xr ypclnt 3 , +.Xr group 5 , +.Xr hosts_access 5 , +.Xr nsswitch.conf 5 , +.Xr passwd 5 , +.Xr rc.conf 5 , +.Xr rc 8 , +.Xr ypbind 8 , +.Xr ypinit 8 , +.Xr yppoll 8 , +.Xr yppush 8 , +.Xr ypserv 8 , +.Xr ypset 8 , +.Xr yptest 8 , +.Xr ypxfr 8 +.Sh HISTORY +The +.Tn NIS +client subsystem was originally written by Theo de Raadt +to be compatible with Sun's implementation. The +.Tn NIS +server suite was originally written by Mats O Jansson. +.Sh BUGS +If +.Xr ypbind 8 +cannot find a server, the system behaves the same way as Sun's code: +it hangs. +.Pp +The +.Sq secure map +feature is not compatible with non-BSD implementations as found +e.g. in Solaris. diff --git a/static/netbsd/man8/pam.8 b/static/netbsd/man8/pam.8 new file mode 100644 index 00000000..381e5a9d --- /dev/null +++ b/static/netbsd/man8/pam.8 @@ -0,0 +1,108 @@ +.\" $NetBSD: pam.8,v 1.5 2015/04/28 09:48:31 prlw1 Exp $ +.\" +.\" Copyright (c) 2005 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Jason R. Thorpe. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd February 28, 2005 +.Dt PAM 8 +.Os +.Sh NAME +.Nm pam +.Nd Pluggable Authentication Modules framework +.Sh DESCRIPTION +The Pluggable Authentication Modules +.Pq 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. +.Pp +PAM modules provide four classes of functionality: +.Bl -tag -width password +.It account +Account verification services such as password expiration and access control. +.It auth +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. +.It password +Password +.Pq or, more generally, authentication token +change and update services. +.It session +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. +.El +.Pp +A primary feature of PAM is the notion of +.Dq 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. +.Sh SEE ALSO +.Xr login 1 , +.Xr passwd 1 , +.Xr su 1 , +.Xr pam 3 , +.Xr pam.conf 5 , +.Xr pam_chroot 8 , +.Xr pam_deny 8 , +.Xr pam_echo 8 , +.Xr pam_exec 8 , +.Xr pam_ftpusers 8 , +.Xr pam_group 8 , +.Xr pam_guest 8 , +.Xr pam_krb5 8 , +.Xr pam_ksu 8 , +.Xr pam_lastlog 8 , +.Xr pam_login_access 8 , +.Xr pam_nologin 8 , +.Xr pam_permit 8 , +.Xr pam_radius 8 , +.Xr pam_rhosts 8 , +.Xr pam_rootok 8 , +.Xr pam_securetty 8 , +.Xr pam_self 8 , +.Xr pam_skey 8 , +.Xr pam_ssh 8 , +.Xr pam_unix 8 +.Sh HISTORY +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 +.Pq XSSO +Pluggable Authentication Modules specification. +.Pp +The Pluggable Authentication Module framework first appeared in +.Nx 3.0 . diff --git a/static/netbsd/man8/rc.8 b/static/netbsd/man8/rc.8 new file mode 100644 index 00000000..bcb3415a --- /dev/null +++ b/static/netbsd/man8/rc.8 @@ -0,0 +1,406 @@ +.\" $NetBSD: rc.8,v 1.41 2024/12/31 01:53:59 snj Exp $ +.\" +.\" Copyright (c) 2000-2017 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Luke Mewburn. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd December 7, 2024 +.Dt RC 8 +.Os +.Sh NAME +.Nm rc , +.Nm rc.local , +.Nm rc.shutdown , +.Nm rc.shutdown.final , +.Nm rc.d/ +.Nd startup and shutdown scripts +.Sh SYNOPSIS +.Nm rc +.Nm rc.local +.Nm rc.shutdown +.Nm rc.d/ +.Sh DESCRIPTION +.Nm +is the command script which controls the startup of various services, +and is invoked by +.Xr init 8 +as part of the process of entering the automatic reboot to multi-user startup, +or after the single user mode shell has exited. +If +.Xr init 8 +is starting the automatic reboot process, +.Nm +is invoked with the argument of +.Sq autoboot . +.Pp +.Nm rc.local +is a command script to which local boot-time actions can be added. +It is (nearly) the last thing invoked by +.Nm rc +during a normal boot. +.Pp +.Nm rc.shutdown +is the command script which shuts down various services, and is invoked by +.Xr shutdown 8 +as part of the process of shutting down the system. +.Pp +.Nm rc.d/ +is the directory which contains various +.Xr sh 1 +scripts, one for each service, +which are called by +.Nm +at startup, +.Nm rc.shutdown +at shutdown, +and as necessary during system operation to stop, start, restart, reload, +or otherwise control the service. +.Ss Operation of rc +.Bl -enum +.It +Source +.Pa /etc/rc.subr +to load various +.Xr rc.subr 8 +shell functions to use. +.It +If autobooting, set +.Sy autoboot=yes +and enable a flag +.Sy ( rc_fast=yes ) , +which prevents the +.Nm rc.d +scripts from performing the check for already running processes +(thus speeding up the boot process). +This +.Sy rc_fast=yes +speedup won't occur when +.Nm +is started up after exiting the single-user shell. +.It +Invoke +.Xr rcorder 8 +to order the files in +.Pa /etc/rc.d/ +that do not have a +.Dq nostart +keyword (refer to +.Xr rcorder 8 Ns 's +.Fl s +flag), +and assigns the result to a variable. +.It +Calls each script in turn using +.Fn run_rc_script +(from +.Xr rc.subr 8 ) , +which sets +.Dv $1 +to +.Sq start , +and sources the script in a sub-shell. +If the script has a +.Sq .sh +suffix then it is sourced directly into the current shell. +.It +The output from the above steps is sent to a post-processor. +If +.Sy rc_silent +is false, then the post-processor displays the output. +If +.Sy rc_silent +is true, then the post-processor invokes the command specified in +.Va rc_silent_cmd +once for each line, without otherwise displaying the output. +Useful values for +.Va rc_silent_cmd +include +.Dq \&: +to display nothing at all, and +.Dq twiddle +to display a spinning symbol on the console. +Regardless of the value of +.Sy rc_silent , +the post-processor saves the output in +.Pa /var/run/rc.log . +.El +.Ss Operation of rc.shutdown +.Bl -enum +.It +Source +.Pa /etc/rc.subr +to load various +.Xr rc.subr 8 +shell functions to use. +.It +Invoke +.Xr rcorder 8 +to order the files in +.Pa /etc/rc.d/ +that have a +.Dq shutdown +keyword (refer to +.Xr rcorder 8 Ns 's +.Fl k +flag), +reverses that order, and assigns the result to a variable. +.It +Calls each script in turn using +.Fn run_rc_script +(from +.Xr rc.subr 8 ) , +which sets +.Dv $1 +to +.Sq stop , +and sources the script in a sub-shell. +If the script has a +.Sq .sh +suffix then it is sourced directly into the current shell. +.It +Runs +.Pa /etc/rc.shutdown.final +if it exists, passing the currently ongoing shutdown action, which +will be one of: +.Bl -bullet +.It +shutdown +when going to single user mode. +.It +halt +when halting the machine (but not powering it down). +.It +reboot +when rebooting the machine. +.It +poweroff +when halting the machine and powering it off. +.El +.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). +.El +.Ss Contents of rc.d/ +.Nm rc.d/ +is located in +.Pa /etc/rc.d . +The following file naming conventions are currently used in +.Nm rc.d/ : +.Bl -tag -width ALLUPPERCASExx -offset indent +.It Pa ALLUPPERCASE +Scripts that are +.Sq placeholders +to ensure that certain operations are performed before others. +In order of startup, these are: +.Bl -tag -width NETWORKINGxx +.It Pa NETWORKING +Ensure basic network services are running, including general +network configuration +.Pq Pa network +and +.Pa dhcpcd . +.It Pa SERVERS +Ensure basic services (such as +.Pa NETWORKING , +.Pa ppp , +.Pa syslogd , +and +.Pa kdc ) +exist for services that start early (such as +.Pa named ) , +because they're required by +.Pa DAEMON +below. +.It Pa DAEMON +Before all general purpose daemons such as +.Pa dhcpd , +.Pa lpd , +and +.Pa ntpd . +.It Pa LOGIN +Before user login services +.Pa ( inetd , +.Pa telnetd , +.Pa rshd , +.Pa sshd , +and +.Pa xdm ) , +as well as before services which might run commands as users +.Pa ( cron , +.Pa postfix , +and +.Pa sendmail ) . +.El +.It Pa inline.sh +Scripts that are sourced into the current shell rather than a sub-shell +have a +.Sq Pa .sh +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. +.Pa /etc/rc.d/bootconf.sh +uses this behaviour to allow the user to select a different +configuration (including +.Pa /etc/rc.conf ) +early in the boot. +.It Pa service +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 +.Fn stop_boot +function (from +.Xr rc.subr 8 ) . +.El +.Pp +Each script should contain +.Xr rcorder 8 +keywords, especially an appropriate +.Dq PROVIDE +entry. +.Pp +The scripts are expected to support at least the following arguments: +.Bl -tag -width restart -offset indent +.It Sy start +Start the service. +This should check that the service is to be started as specified by +.Xr rc.conf 5 . +Also checks if the service is already running and refuses to start if +it is. +This latter check is not performed by standard +.Nx +scripts if the system is starting directly to multi-user mode, to +speed up the boot process. +.It Sy stop +If the service is to be started as specified by +.Xr rc.conf 5 , +stop the service. +This should check that the service is running and complain if it's not. +.It Sy restart +Perform a +.Sy stop +then a +.Sy start . +.It Sy status +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). +.It Sy poll +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. +.It Sy rcvar +Display which +.Xr rc.conf 5 +variables are used to control the startup of the service (if any). +.El +.Pp +Other arguments (such as +.Sq reload , +.Sq dumpdb , +etc) can be added if necessary. +.Pp +The argument may have one of the following prefixes to alter its operation: +.Bl -tag -width "force" -offset indent +.It Sy fast +Skip the check for an existing running process. +Sets +.Sy rc_fast=yes . +.It Sy force +Skips the +.Xr rc.conf 5 +check, ignores a failure result from any of the prerequisite checks, +executes the command, and always returns a zero exit status. +Sets +.Sy rc_force=yes . +.It Sy one +Skips the +.Xr rc.conf 5 +check, but performs all other prerequisite tests. +.El +.Pp +In order to simplify scripts, the +.Fn run_rc_command +function from +.Xr rc.subr 8 +may be used. +.Sh FILES +.Bl -tag -width /etc/rc.shutdown -compact +.It Pa /etc/rc +Startup script called by +.Xr init 8 . +.It Pa /etc/rc.d/ +Directory containing control scripts for each service. +.It Pa /etc/rc.local +Local startup script. +.It Pa /etc/rc.shutdown +Shutdown script called by +.Xr shutdown 8 . +.It Pa /etc/rc.subr +Contains +.Xr rc.subr 8 +functions used by various scripts. +.It Pa /etc/rc.conf +System startup configuration file. +.It Pa /var/run/rc.log +Log file created by +.Nm . +.El +.Sh SEE ALSO +.Xr rc.conf 5 , +.Xr init 8 , +.Xr rc.subr 8 , +.Xr rcorder 8 , +.Xr reboot 8 , +.Xr shutdown 8 +.Rs +.%A Luke Mewburn +.%T The Design and Implementation of the NetBSD rc.d system +.%I USENIX Association +.%B Proceedings of the FREENIX Track: 2001 USENIX Annual Technical Conference +.%D June 25-30, 2001 +.%U http://www.usenix.org/publications/library/proceedings/usenix01/freenix01/full_papers/mewburn/mewburn.pdf +.Re +.Sh HISTORY +The +.Nm +command appeared in +.Bx 4.0 . +The +.Pa /etc/rc.d +support was implemented in +.Nx 1.5 +by +.An Luke Mewburn +.Aq lukem@NetBSD.org . +The post-processor, support for +.Va rc_silent , +and saving output to a file, was implemented in +.Nx 6.0 +by +.An Alan Barrett . diff --git a/static/netbsd/man8/rc.subr.8 b/static/netbsd/man8/rc.subr.8 new file mode 100644 index 00000000..93d49d24 --- /dev/null +++ b/static/netbsd/man8/rc.subr.8 @@ -0,0 +1,865 @@ +.\" $NetBSD: rc.subr.8,v 1.32 2021/01/10 19:26:31 riastradh Exp $ +.\" +.\" Copyright (c) 2002-2011 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" This code is derived from software contributed to The NetBSD Foundation +.\" by Luke Mewburn. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd December 17, 2012 +.Dt RC.SUBR 8 +.Os +.Sh NAME +.Nm rc.subr +.Nd functions used by system shell scripts +.Sh SYNOPSIS +.Bl -item +.It +.Li . /etc/rc.subr +.It +.Ic backup_file Ar action Ar file Ar current Ar backup +.It +.Ic basename Ar file Op Ar suffix +.It +.Ic checkyesno Ar var +.It +.Ic check_pidfile Ar pidfile Ar procname Op Ar interpreter +.It +.Ic check_process Ar procname Op Ar interpreter +.It +.Ic collapse_backslash_newline +.It +.Ic dirname Ar file +.It +.Ic err Ar exitval Ar message +.It +.Ic load_rc_config Ar command +.It +.Ic load_rc_config_var Ar command Ar var +.It +.Ic mount_critical_filesystems Ar type +.It +.Ic no_rc_postprocess Ar command Op Ar arguments +.It +.Ic print_rc_metadata Ar string +.It +.Ic print_rc_normal Oo Fl n Oc Ar string +.It +.Ic rc_usage Ar command Op Ar ... +.It +.Ic reverse_list Ar item Op Ar ... +.It +.Ic run_rc_command Ar argument [parameters] +.It +.Ic run_rc_script Ar file Ar argument +.It +.Ic stop_boot +.It +.Ic twiddle +.It +.Ic wait_for_pids Op Ar pid Op Ar ... +.It +.Ic warn Ar message +.It +.Ic yesno_to_truefalse Ar var +.El +.Sh DESCRIPTION +.Nm +contains commonly used shell script functions which are used by +various scripts such as +.Xr rc 8 , +and the periodic system services which are controlled by +.Xr daily.conf 5 , +.Xr monthly.conf 5 , +.Xr security.conf 5 , +and +.Xr weekly.conf 5 . +.Pp +The +.Nm +functions are accessed by sourcing +.Pa /etc/rc.subr +into the current shell. +.Pp +The following shell functions are available: +.Bl -tag -width 4n +.It Ic backup_file Ar action Ar file Ar current Ar backup +Make a backup copy of +.Ar file +into +.Ar current . +If the +.Xr rc.conf 5 +variable +.Sy backup_uses_rcs +is +.Sq YES , +use +.Xr rcs 1 +to archive the previous version of +.Ar current , +otherwise save the previous version of +.Ar current +as +.Ar backup . +.Pp +.Ar action +may be one of the following: +.Bl -tag -width remove +.It Sy add +.Ar file +is now being backed up by or possibly re-entered into this backup mechanism. +.Ar current +is created, and if necessary, the +.Xr rcs 1 +files are created as well. +.It Sy update +.Ar file +has changed and needs to be backed up. +If +.Ar current +exists, it is copied to +.Ar backup +or checked into +.Xr rcs 1 +(if the repository file is old), +and then +.Ar file +is copied to +.Ar current . +.It Sy remove +.Ar file +is no longer being tracked by this backup mechanism. +If +.Xr rcs 1 +is being used, an empty file is checked in and +.Ar current +is removed, +otherwise +.Ar current +is moved to +.Ar backup . +.El +.It Ic basename Ar file Op Ar suffix +Just like +.Xr basename 1 , +except implemented using shell built-in commands, and usable before the +.Pa /usr/bin +direcory is available. +.It Ic checkyesno Ar var +Return 0 if +.Ar var +is defined to +.Sq YES , +.Sq TRUE , +.Sq ON , +or +.Sq 1 . +Return 1 if +.Ar var +is defined to +.Sq NO , +.Sq FALSE , +.Sq OFF , +or +.Sq 0 . +Otherwise, warn that +.Ar var +is not set correctly. +The values are case insensitive. +.Pp +Note that the warning message shown by this function when +.Ar var +is not set references a manual page where the user can find more information. +Its name is picked up from the +.Sy rcvar_manpage +variable. +.It Ic check_pidfile Ar pidfile Ar procname Op Ar interpreter +Parses the first word of the first line of +.Ar pidfile +for a PID, and ensures that the process with that PID +is running and its first argument matches +.Ar procname . +Prints the matching PID if successful, otherwise nothing. +If +.Ar interpreter +is provided, parse the first line of +.Ar procname , +ensure that the line is of the form +.Dl #! interpreter [...] +and use +.Ar interpreter +with its optional arguments and +.Ar procname +appended as the process string to search for. +.It Ic check_process Ar procname Op Ar interpreter +Prints the PIDs of any processes that are running with a first +argument that matches +.Ar procname . +.Ar interpreter +is handled as per +.Ic check_pidfile . +.It Ic collapse_backslash_newline +Copy input to output, collapsing +.Ao backslash Ac Ns Ao newline Ac +to nothing, but leaving other backslashes alone. +.Ic dirname Ar file +Just like +.Xr dirname 1 , +except implemented using shell built-in commands, and usable before the +.Pa /usr/bin +direcory is available. +.It Ic err Ar exitval Ar message +Display an error message to +.Em stderr , +log it to the system log +using +.Xr logger 1 , +and +.Cm exit +with an exit value of +.Ar exitval . +The error message consists of the script name +(from +.Sy $0 ) , +followed by +.Dq ": ERROR: " , +and then +.Ar message . +.It Ic load_rc_config Ar command +Source in the +.Xr rc.conf 5 +configuration files for +.Ar command . +First, +.Pa /etc/rc.conf +is sourced if it has not yet been read in. +Then, +.Pa /etc/rc.conf.d/ Ns Ar command +is sourced if it is an existing file. +The latter may also contain other variable assignments to override +.Ic run_rc_command +arguments defined by the calling script, to provide an easy +mechanism for an administrator to override the behaviour of a given +.Xr rc.d 8 +script without requiring the editing of that script. +.It Ic load_rc_config_var Ar command Ar var +Read the +.Xr rc.conf 5 +variable +.Ar var +for +.Ar command +and set in the current shell, using +.Ic load_rc_config +in a sub-shell to prevent unwanted side effects from other variable +assignments. +.It Ic mount_critical_filesystems Ar type +Go through a list of critical file systems, +as found in the +.Xr rc.conf 5 +variable +.Sy critical_filesystems_ Ns Ar type , +mounting each one that +is not currently mounted. +.It Ic no_rc_postprocess Ar command Op Ar arguments +Execute the specified command with the specified arguments, +in such a way that its output bypasses the post-processor that +.Xr rc 8 +uses for most commands. +This implies that the output will not appear in the +.Pa /var/run/rc.log +file, and will appear on the console regardless of the +value of +.Va rc_silent . +This is expected to be useful for interactive commands, +and this mechanism is automatically used by +.Ic run_rc_command +when a script contains the +.Xr rcorder 8 +keyword +.Dq interactive . +.Pp +If invoked from a context that does not appear to be under the control of +.Xr rc 8 , +then the command is executed without special treatment. +.It Ic print_rc_metadata Ar string +Print the specified +.Ar string +in such a way that it should be handled as meta-data by the +.Xr rc 8 +post-processor. +If invoked from a context that does not appear to be under the control of +.Xr rc 8 , +then the +.Ar string +is discarded. +.Pp +Any +.Xr rc.d 8 +script may invoke this function with an argument that begins with +.Dq note: , +followed by one line of arbitrary text; +the text will be logged by +.Xr rc 8 +but will not be displayed on the console. +.Pp +The use of arguments that do not begin with +.Dq note: +is reserved for internal use by +.Xr rc 8 +and +.Nm . +.It Ic print_rc_normal Oo Fl n Oc Ar string +Print the specified +.Ar string +in such a way that it should be handled as normal output by the +.Xr rc 8 +post-processor. +If invoked from a context that does not appear to be under the control of +.Xr rc 8 , +then the +.Ar string +is printed to standard output. +.Pp +If the +.Fl n +flag is specified, then the string is printed without a newline. +.Pp +Intended use cases include: +.Bl -bullet +.It +An rc.d script can use +.Dq Sy print_rc_normal Fl n +to print a partial line in such a way that it appears +immediately instead of being buffered by +.Xr rc 8 Ap s +post-processor. +.It +An rc.d script that is run via the +.Sy no_rc_postprocess +function (so most of its output is invisible to +.Xr rc 8 Ap s +post-processor) can use +.Sy print_rc_normal +to force some of its output to be seen by the post-processor. +.El +.It Ic rc_usage Ar command Op Ar ... +Print a usage message for +.Sy $0 , +with +.Ar commands +being the list of valid arguments +prefixed by +.Dq "[fast|force|one]" . +.It Ic reverse_list Ar item Op Ar ... +Print the list of +.Ar items +in reverse order. +.It Ic run_rc_command Ar argument Op Ar parameter ... +Run the +.Ar argument +method for the current +.Xr rc.d 8 +script, based on the settings of various shell variables. +.Ic run_rc_command +is extremely flexible, and allows fully functional +.Xr rc.d 8 +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. +.Pp +.Ar argument +is searched for in the list of supported commands, which may be one +of: +.Bl -tag -width restart -offset indent +.It Sy start +Start the service. +This should check that the service is to be started as specified by +.Xr rc.conf 5 . +Also checks if the service is already running and refuses to start if +it is. +This latter check is not performed by standard +.Nx +scripts if the system is starting directly to multi-user mode, to +speed up the boot process. +.It Sy stop +If the service is to be started as specified by +.Xr rc.conf 5 , +stop the service. +This should check that the service is running and complain if it's not. +.It Sy restart +Perform a +.Sy stop +then a +.Sy start . +Defaults to displaying the process ID of the program (if running). +.It Sy rcvar +Display which +.Xr rc.conf 5 +variables are used to control the startup of the service (if any). +.El +.Pp +If +.Sy pidfile +or +.Sy procname +is set, also support: +.Bl -tag -width restart -offset indent +.It Sy poll +Wait for the command to exit. +.It Sy status +Show the status of the process. +.El +.Pp +Other supported commands are listed in the optional variable +.Sy extra_commands . +.Pp +.Ar argument +may have one of the following prefixes which alters its operation: +.Bl -tag -width "Prefix" -offset indent +.It Sy fast +Skip the check for an existing running process, +and sets +.Sy rc_fast=YES . +.It Sy force +Skip the checks for +.Sy rcvar +being set to yes, +and sets +.Sy rc_force=YES . +This ignores +.Ar argument Ns Sy _precmd +returning non-zero, and ignores any of the +.Sy required_* +tests failing, and always returns a zero exit status. +.It Sy one +Skip the checks for +.Sy rcvar +being set to yes, but performs all the other prerequisite tests. +.El +.Pp +.Ic run_rc_command +uses the following shell variables to control its behaviour. +Unless otherwise stated, these are optional. +.Bl -tag -width procname -offset indent +.It Sy name +The name of this script. +This is not optional. +.It Sy rcvar +The value of +.Sy rcvar +is checked with +.Ic checkyesno +to determine if this method should be run. +.It Sy rcvar_manpage +The manual page containing information about +.Sy rcvar . +It will be part of the warning message shown when +.Sy rcvar +is undefined. +Defaults to +.Xr rc.conf 5 . +.It Sy command +Full path to the command. +Not required if +.Ar argument Ns Sy _cmd +is defined for each supported keyword. +.It Sy command_args +Optional arguments and/or shell directives for +.Sy command . +.It Sy command_interpreter +.Sy command +is started with +.Dl #! command_interpreter [...] +which results in its +.Xr ps 1 +command being +.Dl command_interpreter [...] command +so use that string to find the PID(s) of the running command +rather than +.Ql command . +.It Sy extra_commands +Extra commands/keywords/arguments supported. +.It Sy pidfile +Path to pid file. +Used to determine the PID(s) of the running command. +If +.Sy pidfile +is set, use +.Dl check_pidfile $pidfile $procname +to find the PID. +Otherwise, if +.Sy command +is set, use +.Dl check_process $procname +to find the PID. +.It Sy procname +Process name to check for. +Defaults to the value of +.Sy command . +.It Sy required_dirs +Check for the existence of the listed directories +before running the default start method. +.It Sy required_files +Check for the readability of the listed files +before running the default start method. +.It Sy required_vars +Perform +.Ic checkyesno +on each of the list variables +before running the default start method. +.It Sy ${name}_chdir +Directory to +.Ic cd +to before running +.Sy command , +if +.Sy ${name}_chroot +is not provided. +.It Sy ${name}_chroot +Directory to +.Xr chroot 8 +to before running +.Sy command . +Only supported after +.Pa /usr +is mounted. +.It Sy ${name}_env +List of additional or modified environment variables to set +when starting +.Sy command . +.It Sy ${name}_flags +Arguments to call +.Sy command +with. +This is usually set in +.Xr rc.conf 5 , +and not in the +.Xr rc.d 8 +script. +The environment variable +.Sq Ev flags +can be used to override this. +.It Sy ${name}_nice +.Xr nice 1 +level to run +.Sy command +as. +Only supported after +.Pa /usr +is mounted. +.It Sy ${name}_user +User to run +.Sy command +as, using +.Xr chroot 8 . +if +.Sy ${name}_chroot +is set, otherwise +uses +.Xr su 1 . +Only supported after +.Pa /usr +is mounted. +.It Sy ${name}_group +Group to run the chrooted +.Sy command +as. +.It Sy ${name}_groups +Comma separated list of supplementary groups to run the chrooted +.Sy command +with. +.It Ar argument Ns Sy _cmd +Shell commands which override the default method for +.Ar argument . +.It Ar argument Ns Sy _precmd +Shell commands to run just before running +.Ar argument Ns Sy _cmd +or the default method for +.Ar argument . +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 +.Sy required_* +checks and process (non-)existence checks. +.It Ar argument Ns Sy _postcmd +Shell commands to run if running +.Ar argument Ns Sy _cmd +or the default method for +.Ar argument +returned a zero exit code. +.It Sy sig_stop +Signal to send the processes to stop in the default +.Sy stop +method. +Defaults to +.Dv SIGTERM . +.It Sy sig_reload +Signal to send the processes to reload in the default +.Sy reload +method. +Defaults to +.Dv SIGHUP . +.El +.Pp +For a given method +.Ar argument , +if +.Ar argument Ns Sy _cmd +is not defined, then a default method is provided by +.Sy run_rc_command : +.Bl -tag -width "argument" -offset indent +.It Sy Argument +.Sy Default method +.It Sy start +If +.Sy command +is not running and +.Ic checkyesno Sy rcvar +succeeds, start +.Sy command . +.It Sy stop +Determine the PIDs of +.Sy command +with +.Ic check_pidfile +or +.Ic check_process +(as appropriate), +.Ic kill Sy sig_stop +those PIDs, and run +.Ic wait_for_pids +on those PIDs. +.It Sy reload +Similar to +.Sy stop , +except that it uses +.Sy sig_reload +instead, and doesn't run +.Ic wait_for_pids . +.It Sy restart +Runs the +.Sy stop +method, then the +.Sy start +method. +.It Sy status +Show the PID of +.Sy command , +or some other script specific status operation. +.It Sy poll +Wait for +.Sy command +to exit. +.It Sy rcvar +Display which +.Xr rc.conf 5 +variable is used (if any). +This method always works, even if the appropriate +.Xr rc.conf 5 +variable is set to +.Sq NO . +.El +.Pp +The following variables are available to the methods +(such as +.Ar argument Ns Sy _cmd ) +as well as after +.Ic run_rc_command +has completed: +.Bl -tag -width "rc_flags" -offset indent +.It Sy rc_arg +Argument provided to +.Sy run_rc_command , +after fast and force processing has been performed. +.It Sy rc_flags +Flags to start the default command with. +Defaults to +.Sy ${name}_flags , +unless overridden by the environment variable +.Sq Ev flags . +This variable may be changed by the +.Ar argument Ns Sy _precmd +method. +.It Sy rc_pid +PID of +.Sy command +(if appropriate). +.It Sy rc_fast +Not empty if +.Dq fast +prefix was used. +.It Sy rc_force +Not empty if +.Dq force +prefix was used. +.El +.It Ic run_rc_script Ar file Ar argument +Start the script +.Ar file +with an argument of +.Ar argument , +and handle the return value from the script. +.Pp +Various shell variables are unset before +.Ar file +is started: +.Bd -ragged -offset indent +.Sy name , +.Sy command , +.Sy command_args , +.Sy command_interpreter , +.Sy extra_commands , +.Sy pidfile , +.Sy rcvar , +.Sy required_dirs , +.Sy required_files , +.Sy required_vars , +.Ar argument Ns Sy _cmd , +.Ar argument Ns Sy _precmd . +.Ar argument Ns Sy _postcmd . +.Ed +.Pp +The startup behaviour of +.Ar file +depends upon the following checks: +.Bl -enum +.It +If +.Ar file +ends in +.Pa .sh , +it is sourced into the current shell. +.It +If +.Ar file +appears to be a backup or scratch file +(e.g., with a suffix of +.Sq ~ , +.Sq # , +.Sq .OLD , +or +.Sq .orig ) , +ignore it. +.It +If +.Ar file +is not executable, ignore it. +.It +If the +.Xr rc.conf 5 +variable +.Sy rc_fast_and_loose +is empty, +source +.Ar file +in a sub shell, +otherwise source +.Ar file +into the current shell. +.It +If +.Ar file +contains the +.Xr rcorder 8 +keyword +.Dq interactive , +then the command is executed using +.Ic no_rc_postprocess . +.El +.It Ic stop_boot +Prevent booting to multiuser mode. +If the +.Sy autoboot +variable is +.Sq yes , +then a +.Sy SIGTERM +signal is sent to the parent +process (which is assumed to be +.Xr rc 8 ) . +Otherwise, the shell exits with status +.Li 1 . +.It Ic twiddle +Display one of the characters +.Sq \&/ , \&- , \&\e , \&| , +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 +.Pa /dev/tty , +so this function may be useful even inside a script whose output +has been redirected. +.It Ic wait_for_pids Op Ar pid Op Ar ... +Wait until all of the provided +.Ar pids +don't exist any more, printing the list of outstanding +.Ar pids +every two seconds. +.It Ic warn Ar message +Display a warning message to +.Em stderr +and log it to the system log +using +.Xr logger 1 . +The warning message consists of the script name +(from +.Sy $0 ) , +followed by +.Dq ": WARNING: " , +and then +.Ar message . +.It Ic yesno_to_truefalse Ar var +Change the value of the specified variable from any of the +forms acceptable to the +.Ic checkyesno +function, to +.Dq true +or +.Dq false . +.El +.Sh FILES +.Bl -tag -width /etc/rc.subr -compact +.It Pa /etc/rc.subr +The +.Nm +file resides in +.Pa /etc . +.El +.Sh SEE ALSO +.Xr rc.conf 5 , +.Xr rc 8 +.Sh HISTORY +.Nm +appeared in +.Nx 1.3 . +The +.Xr rc.d 8 +support functions appeared in +.Nx 1.5 . +Support for the +.Xr rc 8 +post-processor appeared in +.Nx 6.0 . diff --git a/static/netbsd/man8/rescue.8 b/static/netbsd/man8/rescue.8 new file mode 100644 index 00000000..9dc1759e --- /dev/null +++ b/static/netbsd/man8/rescue.8 @@ -0,0 +1,136 @@ +.\" $NetBSD: rescue.8,v 1.9 2014/03/18 18:20:40 riastradh Exp $ +.\" +.\" Copyright (c) 2003 Tim Kientzle <kientzle@acm.org> +.\" Copyright (c) 2003 Simon L. Nielsen <simon@FreeBSD.org> +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" FreeBSD: src/share/man/man8/rescue.8,v 1.3 2005/11/10 15:42:51 kientzle Exp +.\" +.Dd April 5, 2012 +.Dt RESCUE 8 +.Os +.Sh NAME +.Nm rescue +.Nd rescue utilities in +.Pa /rescue +.Sh DESCRIPTION +The +.Pa /rescue +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 +.Nx 2.0 , +there is a real possibility that the standard tools in +.Pa /bin +and +.Pa /sbin +may become non-functional due to a failed upgrade or a disk error. +The tools in +.Pa /rescue +are statically linked and should therefore be more resistant to +damage. +However, being statically linked, the tools in +.Pa /rescue +are also less functional than the standard utilities. +In particular, they do not have full use of the locale, +.Xr pam 3 , +and nsswitch libraries. +.Pp +If your system fails to boot, and it shows an error message similar to: +.Pp +.Dl "init: not found" +.Pp +try booting the system with the boot flag +.Dq Fl a +and supplying +.Pa /rescue/init , +which is the +.Nm +.Xr init 8 , +as the init path. +.Pp +If your system fails to boot, and it shows a prompt similar to: +.Pp +.Dl "Enter full pathname of shell or RETURN for /bin/sh: " +.Pp +the first thing to try running is the standard shell, +.Pa /bin/sh . +If that fails, try running +.Pa /rescue/sh , +which is the +.Nm +shell. +To repair the system, the root partition must first be remounted +read-write. +This can be done with the following +.Xr mount 8 +command: +.Pp +.Dl "/rescue/mount -uw /" +.Pp +The next step is to double-check the contents of +.Pa /bin , +.Pa /lib , +.Pa /libexec , +and +.Pa /sbin , +possibly mounting a +.Nx +installation CD-ROM +and copying files from there. +Once it is possible to successfully run +.Pa /bin/sh , /bin/ls , +and other standard utilities, try rebooting back into the standard +system. +.Pp +The +.Pa /rescue +tools are compiled using +.Xr crunchgen 1 , +which makes them considerably more compact than the standard +utilities. +.Sh FILES +.Bl -tag -width ".Pa /rescue" -compact +.It Pa /rescue +Root of the +.Nm +hierarchy. +.El +.Sh SEE ALSO +.Xr crunchgen 1 +.Sh HISTORY +The +.Nm +utilities first appeared in +.Nx 2.0 . +.Sh AUTHORS +.An -nosplit +The +.Nm +system was written by +.An Luke Mewburn Aq Mt lukem@NetBSD.org . +This manual page was written by +.An Simon L. Nielsen Aq Mt simon@FreeBSD.org , +based on text by +.An Tim Kientzle Aq Mt kientzle@FreeBSD.org . diff --git a/static/netbsd/man8/veriexec.8 b/static/netbsd/man8/veriexec.8 new file mode 100644 index 00000000..429c3198 --- /dev/null +++ b/static/netbsd/man8/veriexec.8 @@ -0,0 +1,200 @@ +.\" $NetBSD: veriexec.8,v 1.8 2018/01/17 12:49:06 sevan Exp $ +.\" +.\" Copyright (c) 2008 Elad Efrat <elad@NetBSD.org> +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. The name of the author may not be used to endorse or promote products +.\" derived from this software without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd September 13, 2017 +.Dt VERIEXEC 8 +.Os +.Sh NAME +.Nm veriexec +.Nd +file integrity subsystem +.Sh DESCRIPTION +.Em Veriexec +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. +.Sh CONFIGURATION +.Ss Signatures Database +.Em Veriexec +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 +.Xr veriexec 5 . +.Pp +.Nx +provides a tool, +.Xr veriexecgen 8 , +for generating the signatures database. +Example usage: +.Bd -literal -offset indent +# veriexecgen +.Ed +.Pp +Although it should be loaded on system boot (see +.Dq RC Configuration +below), this list can be loaded manually using +.Xr veriexecctl 8 : +.Bd -literal -offset indent +# veriexecctl load +.Ed +.Ss Kernel Configuration +.Em Veriexec +requires a kernel with +.Xr fileassoc 9 +support and a pseudo-device to run: +.Bd -literal -offset indent +options FILEASSOC +pseudo-device veriexec +.Ed +.Pp +Additionally, one or more options for digital fingerprint algorithm support: +.Bd -literal -offset indent +options VERIFIED_EXEC_FP_SHA256 +options VERIFIED_EXEC_FP_SHA384 +options VERIFIED_EXEC_FP_SHA512 +.Ed +.Pp +Some kernels already enable +.Em Veriexec +by default. +See your kernel's config file for more information. +.Ss RC Configuration +.Em Veriexec +also allows loading signatures and setting the strict level (see below) during +the boot process using the following variables set in +.Xr rc.conf 5 : +.Bd -literal -offset indent +veriexec=YES +veriexec_strict=1 # IDS mode +.Ed +.Sh STRICT LEVELS +.Em Veriexec +can operate in four modes, also referred to as strict levels: +.Bl -tag -width flag +.It Learning mode ( strict level 0 ) +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.). +.It IDS mode ( strict level 1 ) +IDS (intrusion detection system) mode provides an adequate level of integrity +for the files it monitors. +Implications: +.Pp +.Bl -hyphen -compact +.It +Monitored files cannot be removed +.It +If raw disk access is granted to a disk with monitored files on it, all +monitored files' fingerprints will be invalidated +.It +Access to files with mismatched fingerprints is denied +.It +Write access to monitored files is allowed +.It +Access type is not enforced +.El +.It IPS mode ( strict level 2 ) +IPS (intrusion prevention system) mode provides a high level of integrity +for the files it monitors. +Implications: +.Pp +.Bl -hyphen -compact +.It +All implications of IDS mode +.It +Write access to monitored files is denied +.It +Access type is enforced +.It +Raw disk access to disk devices with monitored files on them is denied +.It +Execution of non-monitored files is denied +.It +Write access to kernel memory via +.Pa /dev/mem +and +.Pa /dev/kmem +is denied +.El +.It Lockdown mode ( strict level 3 ) +Lockdown mode provides high assurance integrity for the entire system. +Implications: +.Pp +.Bl -hyphen -compact +.It +All implications of IPS mode +.It +Access to non-monitored files is denied +.It +Write access to files is allowed only if the file was opened before the +strict level was raised to this mode +.It +Creation of new files is denied +.It +Raw access to system disks is denied +.El +.El +.Sh RUNTIME INFORMATION +.Em Veriexec +exports runtime information that may be useful for various purposes. +.Pp +It reports the currently supported fingerprinting algorithms, for example: +.Bd -literal -offset indent +# /sbin/sysctl kern.veriexec.algorithms +kern.veriexec.algorithms = SHA256 SHA384 SHA512 +.Ed +.Pp +It reports the current verbosity and strict levels, for example: +.Bd -literal -offset indent +# /sbin/sysctl kern.veriexec.{verbose,strict} +kern.veriexec.verbose = 0 +kern.veriexec.strict = 1 +.Ed +.Pp +It reports a summary of currently loaded files and the mount-points they're on, +for example: +.Bd -literal -offset indent +# /sbin/sysctl kern.veriexec.count +kern.veriexec.count.table0.mntpt = / +kern.veriexec.count.table0.fstype = ffs +kern.veriexec.count.table0.nentries = 33 +.Ed +.Pp +Other information may be retrieved using +.Xr veriexecctl 8 . +.Sh SEE ALSO +.Xr options 4 , +.Xr veriexec 5 , +.Xr sysctl 7 , +.Xr sysctl 8 , +.Xr veriexecctl 8 , +.Xr veriexecgen 8 +.Sh AUTHORS +.An Elad Efrat Aq Mt elad@NetBSD.org diff --git a/static/netbsd/man8/wizd.8 b/static/netbsd/man8/wizd.8 new file mode 100644 index 00000000..dd38157a --- /dev/null +++ b/static/netbsd/man8/wizd.8 @@ -0,0 +1,82 @@ +.\" $NetBSD: wizd.8,v 1.11 2019/06/12 09:03:32 mrg Exp $ +.\" +.\" Copyright (c) 2003, 2014 The NetBSD Foundation, Inc. +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS +.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS +.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +.\" POSSIBILITY OF SUCH DAMAGE. +.\" +.Dd March 30, 2015 +.Dt WIZD 8 +.Os +.Sh NAME +.Nm wizd +.Nd automatically correct typographical errors in man pages +.Sh SYNOPSIS +.Nm +.Sh DESCRIPTION +.Nm +automatically checks and corrects spelling errors, usage problems +with +.Xr mdoc 7 +macros, and other typographical errors in man pages. +.Pp +.Nm +is invoked by any +.Xr cvs 1 +commit to a man page. +.Pp +.Nm +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. +.Sh SIGNALS +.Nm +responds to the following signals: +.Bl -tag -width SIGWIZD +.It Aq Mt wiz@NetBSD.org +Examine a man page for errors. +The man page and particular errors in question may be specified in +standard internet mail format. +.El +.Pp +.Nm +additionally sometimes delivers the following signals to other +committer processes: +.Bl -tag -width SIGWIZD +.It Dv SIGWIZD +An error was detected in a man page. +.El +.Sh SEE ALSO +.Xr cvs 1 , +.Xr intro 1 , +.Xr man 1 , +.Xr mdoc 7 +.Sh HISTORY +.Nm +appeared in +.Nx 1.5 . +.Sh CAVEATS +.Nm +is not only copyrighted, but also registered. +.Sh BUGS +Sleeps sometimes. +Leaves laptop at home sometimes. |