docs: OpenBSD Man Pages Added

3 files changed, 512 insertions, 0 deletions

diff --git a/static/openbsd/man8/man8.amd64/MAKEDEV.8 b/static/openbsd/man8/man8.amd64/MAKEDEV.8
new file mode 100644
index 00000000..1a32b0c4
--- /dev/null
+++ b/static/openbsd/man8/man8.amd64/MAKEDEV.8
@@ -0,0 +1,317 @@
+.\" $OpenBSD: MAKEDEV.8,v 1.99 2025/09/29 01:02:58 deraadt Exp $
+.\"
+.\" THIS FILE AUTOMATICALLY GENERATED.  DO NOT EDIT.
+.\" generated from:
+.\"
+.\"	OpenBSD: etc.amd64/MAKEDEV.md,v 1.85 2025/09/29 01:00:14 deraadt Exp 
+.\"	OpenBSD: MAKEDEV.common,v 1.122 2025/01/08 23:09:25 kirill Exp 
+.\"	OpenBSD: MAKEDEV.man,v 1.10 2025/09/29 01:00:14 deraadt Exp 
+.\"	OpenBSD: MAKEDEV.mansub,v 1.2 2004/02/20 19:13:01 miod Exp 
+.\"
+.\" Copyright (c) 2004, Miodrag Vallat
+.\" Copyright (c) 2001-2004 Todd T. Fries <todd@OpenBSD.org>
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.Dd $Mdocdate: September 29 2025 $
+.Dt MAKEDEV 8 amd64
+.Os
+.Sh NAME
+.Nm MAKEDEV
+.Nd create system and device special files
+.Sh SYNOPSIS
+.Nm MAKEDEV
+.Op Ar name ...
+.Sh DESCRIPTION
+The shell script
+.Nm ,
+found in the
+.Pa /dev
+directory, is used to create various special files.
+See
+.Xr intro 4
+for a more complete discussion of special files.
+.Pp
+.Nm
+takes any number of device names as arguments, where the names are
+the common abbreviation for the device or group of devices.
+Files are created in the current working directory.
+.Pp
+Where a device name is followed by a star
+.Sq * ,
+the star must be replaced by a unit number.
+If units are expected for a device but not provided,
+.Nm
+will supply the standard numbers in most cases.
+.Pp
+The amd64 supports the following devices:
+.Pp
+.Sy Special device names
+.Bl -tag -width tenletters -compact
+.It Ar all
+Creates special files for all devices on amd64.
+.It Ar ramdisk
+Ramdisk kernel devices.
+.It Ar std
+Creates the
+.Sq standard
+devices (console, klog, kmem, ksyms, mem, null,
+stderr, stdin, stdout, tty, zero)
+which are absolutely necessary for the system to function properly.
+.It Ar local
+Creates configuration-specific devices, by invoking the shell file
+.Pa MAKEDEV.local .
+.It Ar redodisks
+Recreates all partitions for disks found in
+.Pa /etc .
+.El
+.Pp
+.Sy Disks
+.Bl -tag -width tenletters -compact
+.It Ar cd*
+ATAPI and SCSI CD-ROM drives, see
+.Xr cd 4 .
+.It Ar fd*
+Floppy disk drives (3 1/2", 5 1/4"), see
+.Xr fd 4 .
+.It Ar rd*
+.Dq rd
+pseudo-disks, see
+.Xr rd 4 .
+.It Ar sd*
+SCSI disks, including flopticals, see
+.Xr sd 4 .
+.It Ar vnd*
+.Dq file
+pseudo-disk devices, see
+.Xr vnd 4 .
+.It Ar wd*
+.Dq winchester
+disk drives (ST506, IDE, ESDI, RLL, ...), see
+.Xr wd 4 .
+.El
+.Pp
+.Sy Tapes
+.Bl -tag -width tenletters -compact
+.It Ar ch*
+SCSI media changers, see
+.Xr ch 4 .
+.It Ar st*
+SCSI tape drives, see
+.Xr st 4 .
+.El
+.Pp
+.Sy Terminal ports
+.Bl -tag -width tenletters -compact
+.It Ar tty[0-7][0-9a-f]
+NS16x50 serial ports, see
+.Xr com 4 .
+.It Ar ttyc*
+Cyclades serial ports, see
+.Xr cy 4 .
+.It Ar ttyVI*
+Virtio serial ports, see
+.Xr viocon 4 .
+.El
+.Pp
+.Sy Pseudo terminals
+.Bl -tag -width tenletters -compact
+.It Ar ptm
+pty master device, see
+.Xr ptm 4 .
+.It Ar pty*
+Set of 62 master pseudo terminals, see
+.Xr pty 4 .
+.It Ar tty*
+Set of 62 slave pseudo terminals, see
+.Xr tty 4 .
+.El
+.Pp
+.Sy Console ports
+.Bl -tag -width tenletters -compact
+.It Ar ttyC-J*
+wscons display devices, see
+.Xr wsdisplay 4 .
+.It Ar wscons
+Minimal wscons devices, see
+.Xr wscons 4 .
+.It Ar wskbd*
+wscons keyboards, see
+.Xr wskbd 4 .
+.It Ar wsmux
+wscons keyboard/mouse mux devices, see
+.Xr wsmux 4 .
+.El
+.Pp
+.Sy Pointing devices
+.Bl -tag -width tenletters -compact
+.It Ar wsmouse*
+wscons mice, see
+.Xr wsmouse 4 .
+.El
+.Pp
+.Sy Printers
+.Bl -tag -width tenletters -compact
+.It Ar lpa*
+Polled printer port, see
+.Xr lpt 4 .
+.It Ar lpt*
+IEEE 1284 centronics printer, see
+.Xr lpt 4 .
+.El
+.Pp
+.Sy USB devices
+.Bl -tag -width tenletters -compact
+.It Ar ttyU*
+USB serial ports, see
+.Xr ucom 4 .
+.It Ar uall
+All USB devices, see
+.Xr usb 4 .
+.It Ar ugen*
+Generic USB devices, see
+.Xr ugen 4 .
+.It Ar uhid*
+Generic HID devices, see
+.Xr uhid 4 .
+.It Ar fido
+fido/* nodes, see
+.Xr fido 4 .
+.It Ar ujoy
+ujoy/* nodes, see
+.Xr ujoy 4 .
+.It Ar ulpt*
+Printer devices, see
+.Xr ulpt 4 .
+.It Ar usb*
+Bus control devices used by usbd for attach/detach, see
+.Xr usb 4 .
+.El
+.Pp
+.Sy Special purpose devices
+.Bl -tag -width tenletters -compact
+.It Ar apm
+Power Management Interface, see
+.Xr apm 4 .
+.It Ar audio*
+Audio devices, see
+.Xr audio 4 .
+.It Ar bio
+ioctl tunnel pseudo-device, see
+.Xr bio 4 .
+.It Ar bktr*
+Video frame grabbers, see
+.Xr bktr 4 .
+.It Ar bpf
+Berkeley Packet Filter, see
+.Xr bpf 4 .
+.It Ar dt
+Dynamic Tracer, see
+.Xr dt 4 .
+.It Ar diskmap
+Disk mapper, see
+.Xr diskmap 4 .
+.It Ar dri
+Direct Rendering Infrastructure, see
+.Xr drm 4 .
+.It Ar efi
+EFI runtime services, see
+.Xr efi 4 .
+.It Ar fd
+fd/* nodes, see
+.Xr fd 4 .
+.It Ar fuse
+Userland Filesystem, see
+.Xr fuse 4 .
+.It Ar gpio*
+General Purpose Input/Output, see
+.Xr gpio 4 .
+.It Ar hotplug
+devices hot plugging, see
+.Xr hotplug 4 .
+.It Ar ipmi*
+IPMI BMC access, see
+.Xr ipmi 4 .
+.It Ar nvram
+NVRAM access, see
+.Xr nvram 4 .
+.It Ar kcov
+Kernel code coverage tracing, see
+.Xr kcov 4 .
+.It Ar pci*
+PCI bus devices, see
+.Xr pci 4 .
+.It Ar pctr*
+PC Performance Tuning Register access device, see
+.Xr pctr 4 .
+.It Ar pf
+Packet Filter, see
+.Xr pf 4 .
+.It Ar pppx*
+PPP Multiplexer, see
+.Xr pppx 4 .
+.It Ar pppac*
+PPP Access Concentrator, see
+.Xr pppac 4 .
+.It Ar radio*
+FM tuner devices, see
+.Xr radio 4 .
+.It Ar *random
+In-kernel random data source, see
+.Xr random 4 .
+.It Ar rmidi*
+Raw MIDI devices, see
+.Xr midi 4 .
+.It Ar speaker
+PC speaker, see
+.Xr spkr 4 .
+.It Ar tun*
+Network tunnel driver, see
+.Xr tun 4 .
+.It Ar tap*
+Ethernet tunnel driver, see
+.Xr tap 4 .
+.It Ar tuner*
+Tuner devices, see
+.Xr bktr 4 .
+.It Ar uk*
+Unknown SCSI devices, see
+.Xr uk 4 .
+.It Ar video*
+Video V4L2 devices, see
+.Xr video 4 .
+.It Ar vmm
+Virtual Machine Monitor, see
+.Xr vmm 4 .
+.It Ar vscsi*
+Virtual SCSI controller, see
+.Xr vscsi 4 .
+.It Ar pvbus*
+paravirtual device tree root, see
+.Xr pvbus 4 .
+.It Ar kstat
+Kernel Statistics, see
+.Xr kstat 4 .
+.It Ar psp
+Platform Security Processor, see
+.Xr psp 4 .
+.El
+.Sh FILES
+.Bl -tag -width /dev -compact
+.It Pa /dev
+The special file directory.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr config 8 ,
+.Xr mknod 8
diff --git a/static/openbsd/man8/man8.amd64/Makefile b/static/openbsd/man8/man8.amd64/Makefile
new file mode 100644
index 00000000..e8fe087c
--- /dev/null
+++ b/static/openbsd/man8/man8.amd64/Makefile
@@ -0,0 +1,4 @@
+MAN = boot_amd64.8 \
+      MAKEDEV.8
+
+include ../../../mandoc.mk
diff --git a/static/openbsd/man8/man8.amd64/boot_amd64.8 b/static/openbsd/man8/man8.amd64/boot_amd64.8
new file mode 100644
index 00000000..6c6926a2
--- /dev/null
+++ b/static/openbsd/man8/man8.amd64/boot_amd64.8
@@ -0,0 +1,191 @@
+.\"	$OpenBSD: boot_amd64.8,v 1.9 2016/02/25 09:43:52 tb Exp $
+.\"
+.\" Copyright (c) 1997 Tobias Weingartner
+.\"
+.\" 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 $Mdocdate: February 25 2016 $
+.Dt BOOT_AMD64 8 amd64
+.Os
+.Sh NAME
+.Nm boot_amd64
+.Nd amd64 system bootstrapping procedures
+.Sh DESCRIPTION
+.Ss Cold starts
+The
+.Tn Athlon64
+computers and clones will perform a POST (Power On Self Test) upon
+being booted cold.
+This test will find and initialize memory, keyboard, and other devices.
+It will search for and initialize any extension ROMs that are present,
+and then attempt to boot the operating system from an available boot
+drive.
+.Pp
+The boot drive is usually specified in the BIOS setup.
+.Ss Warm starts
+The BIOS loads the first block (at physical location: track 0, head 0,
+sector 1) off the boot device into memory, and if the last two bytes in the
+block match the signature 0xAA55, the BIOS considers the block a valid
+bootable drive.
+The BIOS then proceeds to call the machine code program in this block.
+If the BIOS is current, it will also pass the boot drive
+to the boot block in register %dl.
+.Pp
+There are two different types of boot blocks on devices.
+There is the
+MBR (master boot record) and the PBR (partition boot record).
+A digression
+into a little piece of history will quickly give light as to why this is so.
+In the beginning, the PC
+.Dq architecture
+came with single or dual floppy
+drives, and no hard drives.
+The only type of bootable sectors on any device were the PBRs.
+They were responsible for loading the rest of the operating
+system from the correct device.
+When hard disks came out, it was felt that
+such a huge space should be able to be partitioned into separate drives,
+and this is when the MBR was invented.
+.Pp
+The MBR relocates itself upon being loaded and invoked by the BIOS.
+Embedded within the MBR is a partition table, with four partition table
+entries.
+The MBR code traverses this table (which was loaded with the
+MBR by the BIOS), looking for an active entry, and then loads the MBR or
+PBR from the disk location specified by the partition table entry.
+So in reality, the MBR is nothing more than a fancy chaining PBR.
+.Pp
+Note: The MBR could load another MBR, which is the case when you are booting
+off an extended partition.
+In other words, the first block of an extended
+partition is really an MBR, which will then load the corresponding MBR or PBR
+out of its extended partition's partition table.
+.Ss Geometry translation
+.Em WARNING :
+This portion of the
+.Dq PC BIOS Architecture
+is a mess, and a compatibility nightmare.
+.Pp
+The PC BIOS has an API to manipulate any disk that the BIOS happens to
+support.
+This interface uses 10 bits to address the cylinder, 8 bits to
+address the head, and 6 bits to address the sector of a drive.
+This restricts any application using the BIOS to being able to address only
+1024 cylinders, 256 heads, and 63 (since the sectors are 1 based) sectors
+on a disk.
+These limitations proved to be fine for roughly 3 years after
+the debut of hard disks on PC computers.
+.Pp
+Many (if not all) newer drives have many more cylinders than the BIOS API
+can support, and likely more sectors per track as well.
+To allow the BIOS the ability of accessing these large drives, the BIOS would
+.Dq re-map
+the
+cylinder/head/sector of the real drive geometry into something that would
+allow the applications using the BIOS to access a larger portion of the
+drive, still using the restricted BIOS API.
+.Pp
+The reason this has become a problem is that any modern OS will use its own
+drivers to access the disk drive, bypassing the BIOS completely.
+However,
+the MBR, PBR, and partition tables are all still written using the original
+BIOS access methods.
+This is for backwards compatibility to the original IBM PC!
+.Pp
+So the gist of it is, the MBR, PBR, and partition table need to have BIOS
+geometry offsets and cylinder/head/sector values for them to be able to
+load any type of operating system.
+This geometry can, and likely will,
+change whenever you move a disk from machine to machine, or from controller
+to controller.
+.Em They are controller and machine specific .
+.Ss Boot process options
+On most
+.Ox
+systems, booting
+.Ox
+from the BIOS will load the
+.Ox Ns -specific
+first-stage bootstrap,
+.Xr biosboot 8 ,
+which in turn will locate and load the second-stage bootstrap,
+.Xr boot 8 .
+Other bootstrapping software may be used, and can chain-load the
+.Ox
+bootstrapping code, or directly load the kernel.
+In the latter case, refer to your bootloader documentation to know which
+options are available.
+.Ss Abnormal system termination
+In case of system crashes, the kernel will usually enter the kernel
+debugger,
+.Xr ddb 4 ,
+unless it is not present in the kernel, or it is disabled via the
+.Em ddb.panic
+sysctl.
+Upon leaving ddb, or if ddb was not entered, the kernel will halt the system
+if it was still in device configuration phase, or attempt a dump to the
+configured dump device, if possible.
+The crash dump will then be recovered by
+.Xr savecore 8
+during the next multi-user boot cycle.
+It is also possible to force other behaviours from ddb.
+.Sh FILES
+.Bl -tag -width /usr/mdec/biosboot -compact
+.It Pa /bsd
+default system kernel
+.It Pa /bsd.sp
+single processor capable kernel
+.It Pa /bsd.mp
+multiprocessor capable kernel
+.It Pa /bsd.rd
+standalone installation kernel, suitable for disaster recovery
+.It Pa /usr/mdec/mbr
+system MBR image
+.It Pa /usr/mdec/biosboot
+system primary stage bootstrap (PBR)
+.It Pa /usr/mdec/boot
+system second stage bootstrap (usually also installed as
+.Pa /boot )
+.It Pa /usr/mdec/pxeboot
+PXE bootstrap
+.El
+.Sh SEE ALSO
+.Xr ddb 4 ,
+.Xr biosboot 8 ,
+.Xr boot 8 ,
+.Xr halt 8 ,
+.Xr init 8 ,
+.Xr installboot 8 ,
+.Xr pxeboot 8 ,
+.Xr reboot 8 ,
+.Xr savecore 8 ,
+.Xr shutdown 8
+.Sh BUGS
+The
+.Dq PC BIOS Architecture
+makes this process very prone to weird and
+wonderful interactions between different operating systems.
+.Pp
+There is no published standard to the MBR and PBR,
+which makes coding these a nightmare.