OpenBSD 5.3

Released May 1, 2013
Copyright 1997-2013, Theo de Raadt.
ISBN 978-0-9881561-1-1
5.3 Song: "Blade Swimmer"

• Order a CDROM from our ordering system.
• See the information on The FTP page for a list of mirror machines.
• Go to the pub/OpenBSD/5.3/ directory on one of the mirror sites.
• Have a look at The 5.3 Errata page for a list of bugs and workarounds.
• See a detailed log of changes between the 5.2 and 5.3 releases.

All applicable copyrights and credits can be found in the applicable file sources found in the files src.tar.gz, sys.tar.gz, xenocara.tar.gz, or in the files fetched via ports.tar.gz. The distribution files used to build packages from the ports.tar.gz file are not included on the CDROM because of lack of space.

What's New

This is a partial list of new features and systems included in OpenBSD 5.3. For a comprehensive list, see the changelog leading to 5.3.

• Improved hardware support, including:
  • New driver oce(4) for Emulex OneConnect 10Gb Ethernet adapters.
  • New driver rtsx(4) for the Realtek RTS5209 card reader.
  • New driver mfii(4) for the LSI Logic MegaRAID SAS Fusion controllers.
  • New driver smsc(4) for SMSC LAN95xx 10/100 USB Ethernet adapters.
  • New drivers for Toradex OAK USB sensors: uoaklux(4) (illuminance), uoakrh(4) (temperature and relative humidity) and uoakv(4) (+/- 10V 8channel ADC).
  • New drivers for virtio(4) devices: vio(4) (network), vioblk(4) (block devices, attaching as SCSI disks) and viomb(4) (memory ballooning).
  • Support for Adaptec 39320LPE added to ahd(4).
  • Broadcom 5718/5719/5720 Gigabit Ethernet devices supported in bge(4).
  • Intel X540-based 10Gb Ethernet devices supported in ix(4).
  • Support for SFP+ hot-plug (82599) and various other improvements in ix(4).
  • TX interrupt mitigation, hardware VLAN tagging and checksum offload reduce CPU use in vr(4).
  • Baby jumbo frames supported in vr(4) and sis(4) useful for e.g. MPLS, vlan(4) tag stacking (QinQ) and RFC4638 pppoe(4).
  • TCP RX Checksum offload in gem(4).
  • Improvements for NICs using 82579/pch2 in em(4).
  • Flow control is now supported on bnx(4) 5708S/5709S adapters, gem(4) and jme(4).
  • Power-saving clients supported in hostap mode with acx(4) and athn(4).
  • A cause of RT2661 ral(4) wedging in hostap mode was fixed.
  • iwn(4) supports additional devices (Centrino Advanced-N 6235 and initial support for Centrino Wireless-N 1030).
  • Improvements to ahci(4).
  • Support for the fixed-function performance counter on newer x86 chips with constant time stamp counters.
  • Elantech touchpads supported in pms(4) and synaptics(4).
  • Support for "physical devices" on skinny mfi(4) controllers.
  • VMware emulated SAS adapters supported by mpi(4).
  • Support for Intel's Supervisor Mode Execution Protection (SMEP) and Supervisor Mode Access Prevention (SMAP) features on i386 and amd64.
  • Support for the RDRAND instruction to read the hardware random number generator on recent Intel processors.
  • amd64 PCI memory extent changed to cover the whole 64-bit memory space; fixes erroneous extent allocation panic on IBM x3100.
  • ulpt(4) can now upload firmware to certain HP LaserJet printers.
  • Added stat clock to Loongson machines, improving accuracy of CPU usage statistics.
  • CPU throttling supported on Loongson 2F.
  • Support for Apple UniNorth and U3 AGP added to agp(4).
  • DRM support for macppc.

• Generic network stack improvements:
  • Restriction on writing to trunk(4) member interfaces relaxed; BPF can now write to interfaces directly (useful for LLDP).
  • UDP support added to sosplice(9) (zero-copy socket splicing).
  • IPv6 autoconfprivacy is enabled by default (can be disabled per-interface with an ifconfig(8) flag).
  • ifconfig(8) hwfeatures displays the maximum MTU supported by the driver (indicating support for jumbo/baby-jumbo frames).
  • Vastly improved IPsec v3 compatibility, including support for Extended Sequence Numbers in the AES-NI driver for AES-GCM and other modes.

• Routing daemons and other userland network improvements:
  • OpenBSD now includes npppd(8), a server-side daemon for L2TP, L2TP/IPsec, PPTP and PPPoE.
  • New standalone tftp-proxy(8) to replace the old inetd(8)-based implementation.
  • SNMPv3 supported in snmpd(8).
  • bgpd(8) is more tolerant of unknown capabilities when bringing up a session (logs a warning rather than fails).
  • bgpd(8) now handles client side of "graceful restart".
  • bgpd(8) can now filter based on the NEXTHOP attribute.
  • A stratum can now be assigned to hardware sensors in ntpd(8).
  • authpf(8) now supports the use of per-group rules files.
  • ftp(1) client now supports basic HTTP authentication as per RFC 2617 and 3986 like "ftp http[s]://user:pass@host/file".
  • ftp(1) client's mput command allows to upload a directory tree recursively using the -r switch.
  • relayd(8) has various improvements including additional scheduling algorithms (least-states, for redirections, and random/source-hash, for relays).
  • The iked(8) IKEv2 daemon supports NAT-T. (The isakmpd daemon for IKEv1 has supported this for a long time).
  • iked(8) blocks IPv6 traffic unless there are v6 VPN flows; this is to prevent leakages as described in draft-gont-opsec-vpn-leakages.

• dhclient(8) improvements:
  • dhclient-script eliminated, all configuration is done with ioctl's and routing sockets.
  • interface configuration is much faster.
  • HUP signals cause dhclient to restart; making it re-read the dhclient.conf(5) and resolv.conf.tail(5) files, and obtain a new lease.
  • INIT, USR1, USR2 signals cause dhclient to exit after attempting to remove routes and addresses it configured.
  • resolv.conf(5) is written only when the in-use default route was inserted by dhclient. Possible changes to the default route are detected and cause dhclient to write out resolv.conf when appropriate.
  • interface hardware address changes are detected and cause dhclient to restart.
  • dhclient.conf directive 'ignore' and command line option '-i' added, allowing the suppression of specific options offered by server.
  • '-L' command line option added, allowing the creation of a complete record of the most recent offer and what we modified it to when binding the lease.
  • rejected offers no longer prevent dhclient from trying recorded leases and going daemon.
  • cleanup of routing tables when starting and exiting is more complete.
  • log messages cleaned up and reduced.
  • dhclient is automatically placed in the routing domain of the interface.
  • incoming and outgoing packet buffers are separate, eliminating possible transmission of inappropriate packets when re-trying DISCOVER and REQUEST.
  • resolv.conf.tail read only once, at startup.
  • both OFFER and ACK packets that lack required options are rejected.
  • file names passed to '-L' and '-l' are constrained to be regular files.
  • bind success reported after binding complete, not when it is started.
  • privileged process daemonizes, eliminating its controlling terminal.
  • STDIN/STDOUT/STDERR no longer redirected to /dev/null when '-d' specified.
  • all existing addresses on the interface are deleted when binding a new lease.
  • leases which would cause routing problems because another interface is already configured with the same subnet are rejected.
  • premature and repeated DISCOVER and/or REQUEST messages at startup are avoided.
  • permanent ARP cache entries are no longer deleted during binding.
  • allow empty lists of option names for 'ignore', 'request', and 'require' dhclient.conf directives, so lists can be reset in interface declarations.
  • dhcpd(8) and dhclient recognize the same list of dhcp options.
  • hand-rolled IMSG implementation replaced with imsg_init(3) and related functions..
  • hand-rolled date string construction replaced with strftime(3) invocations.
  • hand-rolled '%m' option replaced with strerror(3) invocations.
  • many other internal code improvements.

• pf(4) improvements:
  • The divert(4) socket now supports the new IP_DIVERTFL socket option to control whether both inbound and outbound packets are diverted (the default) or only packets travelling in one direction.
  • Sloppy state tracking (a special mode occasionally needed with asymmetric routing) now works correctly with ICMP.
  • PF now restricts the fragment limit to protect against a misconfiguration running the kernel out of mbuf clusters.

• OpenSMTPD 5.3:
  • New features:
    • code is now considered stable and suitable for use in production.
    • smtpctl(8) trace supports runtime tracing of various components, including imsg exchanges, incoming and outgoing sessions, aliases expansion and much more.
    • smtpctl(8) monitor can now be used to monitor in real-time an instance of smtpd(8).
    • smtpctl(8) show queue now supports an "online" mode where the scheduler is queried instead of the disk-based queue to provide more accurate information.
    • virtual domain support has been reworked to simplify and bring support for new features like global catch-alls and shared user mappings.
    • new table API replaces the map API: better handling of transient errors, improved performances and a much better interface.
    • the transfer process may now select the source IP address to use as well as the HELO hostname to advertise from a table.
    • each listener may advertise a different banner hostname.
    • an alternate user database may be provided instead of relying on getpwnam(3).
    • users may now be authenticated using credentials from a table.
    • incoming sessions can be tagged, allowing for rules to only match envelopes that have been reinjected in the daemon after being passed to a proxy tool.
    • intermediate bounces are now sent at configurable rates.
    • rules can now check for a sender email address or domain.
    • experimental (yet functional) support for aldap and sqlite as table backends.
  • Improvements:
    • improved logging format to make it both easier to read and parse.
    • improved memory use by scheduler, smtp, queue and transfer processes.
    • more reliable and efficient disk-based queue.
    • improved scheduler, dns and relaying logic that optimizes transfers.
    • simplified grammar for smtpd.conf(5).
    • initial support for client and server SSL peer certificates validation.
    • SSL certificate tree is now isolated and network-facing processes request SSL information on-demand by imsg.
    • improved and simplified SMTP and MTA engines.
    • much improved performances on both incoming and outgoing code paths.
    • tons of cleanup and assorted minor bug fixes.

• Security improvements:
  • Position-independent executables (PIE) are now used by default on alpha, amd64, hppa, landisk, loongson, sgi and sparc64.
  • gcc(1) stack smashing protector added for Alpha and MIPS (enabled by default).
  • Shared libraries on GCC 4 platforms now each get their own stack protector cookies instead of sharing a single global cookie.

• Performance improvements:
  • Switch default disk I/O sort algorithm to NSCAN for improved fairness and response times.
  • Softdep speedup improvements by the revert of a previously necessary workaround to prevent kva starvation.
  • Large performance and reliability improvements in make(1), especially in parallel mode. make no longer does any busy waiting, it handles concurrent targets correctly, and displays more accurate error messages.
  • Increased stack alignment in constructor functions and new threads on i386 to meet requirements for SSE.
  • Coredumping no longer hogs CPU or I/O and can be aborted by sending the process a SIGKILL signal.

• Threading improvements:
  • Threaded programs and libraries can now be linked with the POSIX-standard -lpthread flag instead of the OpenBSD-specific -pthread flag
  • abort(3) and raise(3) now direct the signal to the calling thread, as specified by POSIX.
  • Whether a thread is currently executing on an alternate signal stack (c.f. sigaltstack(2)) is now determined dynamically, so the stack can be reused if siglongjmp(3) is used to exit the signal handler.
  • libpthread now caches automatically allocated, default size thread stacks.
  • Improvements in the handling of profiling, tracing, and %cpu calculation of threaded processes.

• Assorted improvements:
  • ldomctl(8) was added to manage logical domains on sun4v systems through ldomd(8).
  • Support for WPA Enterprise was added to the wpa_supplicant package.
  • OpenBSD/luna88k and OpenBSD/mvme88k have switched to GCC 3, elf(5) and gained shared library support.
  • OpenBSD/hp300 and OpenBSD/mvme68k have switched to GCC 3 and elf(5).
  • softraid(4) RAID1 and crypto volumes are now bootable on i386 and amd64 (full disk encryption).
  • The mg(1) emacs-like editor now supports diff-buffer-with-file, make-directory and revert-buffer. Column numbers have been made configurable and locale is respected for ctype purposes, like displaying ISO Latin 1 characters.
  • Improved our own pkg-config(1) implementation to make it compatible with freedesktop.org's 0.27.1 release.
  • A number of improvements to the buffer cache and page daemon interactions to avoid issues in low memory/low kva situations.
  • Various bug fixes in uvm to avoid potential races and deadlock issues.
  • Memory filesystem (mfs) switched to bufq, giving us queue limits and FIFO queueing (rather than the current LIFO queueing).
  • Many improvements to the cwm(1) window manager, including tab completion and Xft support for menus, improved Xinerama support, and per-group vertical/horizontal manual tiling support.
  • Added dprintf(3), grantpt(3), posix_openpt(3), ptsname(3), unlockpt(3), and vdprintf(3).
  • Corrected the order of invocation of constructor and destruction functions.
  • Improved compliance and/or cleanliness of header files, particularly <dlfcn.h>, <netdb.h>, <net/if.h>, <netinet/in.h>, <sys/socket.h>, <sys/uio.h>, and <sys/un.h>.

• OpenSSH 6.2:
  • New features:
    • ssh(1) and sshd(8): Added support for AES-GCM authenticated encryption in SSH protocol 2. The new cipher is available as "aes128-gcm@openssh.com" and "aes256-gcm@openssh.com". It uses an identical packet format to the AES-GCM mode specified in RFC 5647, but uses simpler and different selection rules during key exchange.
    • ssh(1) and sshd(8): Added support for encrypt-then-mac (EtM) MAC modes for SSH protocol 2. These modes alter the packet format and compute the MAC over the packet length and encrypted packet rather than over the plaintext data. These modes are considered more secure and are used by default when available.
    • ssh(1) and sshd(8): Added support for the UMAC-128 MAC as "umac-128@openssh.com" and "umac-128-etm@openssh.com". The latter being an encrypt-then-mac mode.
    • sshd(8): Added support for multiple required authentication in SSH protocol 2 via an AuthenticationMethods option. This option lists one or more comma-separated lists of authentication method names. Successful completion of all the methods in any list is required for authentication to complete. This allows, for example, requiring a user having to authenticate via public key or GSSAPI before they are offered password authentication.
    • sshd(8) and ssh-keygen(1): Added support for Key Revocation Lists (KRLs), a compact binary format to represent lists of revoked keys and certificates that take as little as one bit per certificate when revoking by serial number. KRLs may be generated using ssh-keygen(1) and are loaded into sshd(8) via the existing RevokedKeys sshd_config(5) option.
    • ssh(1): IdentitiesOnly now applies to keys obtained from a PKCS11Provider. This allows control of which keys are offered from tokens using IdentityFile.
    • sshd(8): sshd_config(5)'s AllowTcpForwarding now accepts "local" and "remote" in addition to its previous "yes"/"no" keywords to allow the server to specify whether just local or remote TCP forwarding is enabled.
    • sshd(8): Added a sshd_config(5) option AuthorizedKeysCommand to support fetching authorized_keys from a command in addition to (or instead of) from the filesystem. The command is run under an account specified by an AuthorizedKeysCommandUser sshd_config(5) option.
    • sftp-server(8): Now supports a -d option to allow the starting directory to be something other than the user's home directory.
    • ssh-keygen(1): Now allows fingerprinting of keys hosted in PKCS#11 tokens using "ssh-keygen -lD pkcs11_provider".
    • ssh(1): When SSH protocol 2 only is selected (the default), ssh(1) now immediately sends its SSH protocol banner to the server without waiting to receive the server's banner, saving time when connecting.
    • ssh(1) Added ~v and ~V escape sequences to raise and lower the logging level respectively.
    • ssh(1) Made the escape command help (~?) context sensitive so that only commands that will work in the current session are shown.
    • ssh-keygen(1): When deleting host lines from known_hosts using "ssh-keygen -R host", ssh-keygen(1) now prints details of which lines were removed.
  • The following significant bugs have been fixed in this release:
    • ssh(1): Force a clean shutdown of ControlMaster client sessions when the ~. escape sequence is used. This means that ~. should now work in mux clients even if the server is no longer responding.
    • ssh(1): Correctly detect errors during local TCP forward setup in multiplexed clients. (bz#2055)
    • ssh-add(1): Made deleting explicit keys "ssh-add -d" symmetric with adding keys with respect to certificates. It now tries to delete the corresponding certificate and respects the -k option to allow deleting of the key only.
    • sftp(1): Fix a number of parsing and command-editing bugs, including bz#1956.
    • ssh(1): When muxmaster is run with -N, ensure that it shuts down gracefully when a client sends it "-O stop" rather than hanging around. (bz#1985)
    • ssh-keygen(1): When screening moduli candidates, append to the file rather than overwriting to allow resumption. (bz#1957)
    • ssh(1): Record "Received disconnect" messages at ERROR rather than INFO priority. (bz#2057)
    • ssh(1): Loudly warn if explicitly-provided private key is unreadable. (bz#1981)

• Over 7,800 ports, major performance and stability improvements in the package build process
  • The parallel ports builder is more efficient. The main improvement is that dpb consumes much less cpu on busy boxes, but there are lots of small optimizations that amount to a large performance increase: dpb can now build selected large ports using parallel make, and it has a notion of affinity, so that ports failing on a cluster will be preferentially restarted on the same machine.

• Many pre-built packages for each architecture:

  i386: 7670 sparc64: 6756 alpha: 6151

  sh: 1111 amd64: 7632 powerpc: 7215

  sparc: 4635 arm: 4944 hppa: 6401

  vax: 2081 mips64: 6519 mips64el: 6539

• Some highlights:
  • GNOME 3.6.2
  • KDE 3.5.10
  • Xfce 4.10
  • MySQL 5.1.68
  • PostgreSQL 9.2.3
  • Postfix 2.9.6
  • OpenLDAP 2.3.43 and 2.4.33
  • Mozilla Firefox 3.6.28 and 18.0.2
  • Mozilla Thunderbird 17.0.2
  • GHC 7.4.2
  • LibreOffice 3.6.5.2
  • Emacs 21.4 and 24.2
  • Vim 7.3.154
  • PHP 5.2.17 and 5.3.21
  • Python 2.5.4, 2.7.3 and 3.2.3
  • Ruby 1.8.7.370 and 1.9.3.392
  • Tcl/Tk 8.5.13 and 8.6.0
  • Jdk 1.6.0.32 and 1.7.0.11
  • Mono 2.10.9
  • Chromium 24.0.1312.68
  • Groff 1.21
  • Go 1.0.3
  • GCC 4.6.3 and 4.7.2
  • LLVM/Clang 3.2

• As usual, steady improvements in manual pages and other documentation.

• The system includes the following major components from outside suppliers:
  • Xenocara (based on X.Org 7.7 with xserver 1.12.3 + patches, freetype 2.4.11, fontconfig 2.8.0, Mesa 7.11.2, xterm 287, xkeyboard-config 2.7 and more)
  • Gcc 4.2.1 (+patches), 3.3.6 (+ patches) and 2.95.3 (+ patches)
  • Perl 5.12.2 (+ patches)
  • Our improved and secured version of Apache 1.3, with SSL/TLS and DSO support
  • Nginx 1.2.6 (+ patches)
  • OpenSSL 1.0.1c (+ patches)
  • SQLite 3.7.14.1 (+ patches)
  • Sendmail 8.14.6, with libmilter
  • Bind 9.4.2-P2 (+ patches)
  • NSD 3.2.15
  • Lynx 2.8.7rel.2 with HTTPS and IPv6 support (+ patches)
  • Sudo 1.7.2p8
  • Ncurses 5.7
  • Heimdal 0.7.2 (+ patches)
  • Binutils 2.15 (+ patches)
  • Gdb 6.3 (+ patches)
  • Less 444 (+ patches)
  • Awk Aug 10, 2011 version

How to install

Following this are the instructions which you would have on a piece of paper if you had purchased a CDROM set instead of doing an alternate form of install. The instructions for doing an FTP (or other style of) install are very similar; the CDROM instructions are left intact so that you can see how much easier it would have been if you had purchased a CDROM instead.

• CD1:5.3/i386/INSTALL.i386

• CD2:5.3/amd64/INSTALL.amd64

• CD3:5.3/sparc64/INSTALL.sparc64

• FTP:.../OpenBSD/5.3/alpha/INSTALL.alpha
• FTP:.../OpenBSD/5.3/armish/INSTALL.armish
• FTP:.../OpenBSD/5.3/hp300/INSTALL.hp300
• FTP:.../OpenBSD/5.3/hppa/INSTALL.hppa
• FTP:.../OpenBSD/5.3/landisk/INSTALL.landisk
• FTP:.../OpenBSD/5.3/loongson/INSTALL.loongson
• FTP:.../OpenBSD/5.3/luna88k/INSTALL.luna88k
• FTP:.../OpenBSD/5.3/macppc/INSTALL.macppc
• FTP:.../OpenBSD/5.3/mvme68k/INSTALL.mvme68k
• FTP:.../OpenBSD/5.3/mvme88k/INSTALL.mvme88k
• FTP:.../OpenBSD/5.3/sgi/INSTALL.sgi
• FTP:.../OpenBSD/5.3/socppc/INSTALL.socppc
• FTP:.../OpenBSD/5.3/sparc/INSTALL.sparc
• FTP:.../OpenBSD/5.3/vax/INSTALL.vax
• FTP:.../OpenBSD/5.3/zaurus/INSTALL.zaurus

Quick installer information for people familiar with OpenBSD, and the use of the "disklabel -E" command. If you are at all confused when installing OpenBSD, read the relevant INSTALL.* file as listed above!

OpenBSD/i386:

Play with your BIOS options to enable booting from a CD. The OpenBSD/i386 release is on CD1. If your BIOS does not support booting from CD, you will need to create a boot floppy to install from. To create a boot floppy write CD1:5.3/i386/floppy53.fs to a floppy and boot via the floppy drive.

Use CD1:5.3/i386/floppyB53.fs instead for greater SCSI controller support, or CD1:5.3/i386/floppyC53.fs for better laptop support.

If you can't boot from a CD or a floppy disk, you can install across the network using PXE as described in the included INSTALL.i386 document.

If you are planning on dual booting OpenBSD with another OS, you will need to read INSTALL.i386.

To make a boot floppy under MS-DOS, use the "rawrite" utility located at CD1:5.3/tools/rawrite.exe. To make the boot floppy under a Unix OS, use the dd(1) utility. The following is an example usage of dd(1), where the device could be "floppy", "rfd0c", or "rfd0a".

# dd if=<file> of=/dev/<device> bs=32k

Make sure you use properly formatted perfect floppies with NO BAD BLOCKS or your install will most likely fail. For more information on creating a boot floppy and installing OpenBSD/i386 please refer to FAQ 4.3.2.

OpenBSD/amd64:

The 5.3 release of OpenBSD/amd64 is located on CD2. Boot from the CD to begin the install - you may need to adjust your BIOS options first. If you can't boot from the CD, you can create a boot floppy to install from. To do this, write CD2:5.3/amd64/floppy53.fs to a floppy, then boot from the floppy drive.

If you can't boot from a CD or a floppy disk, you can install across the network using PXE as described in the included INSTALL.amd64 document.

If you are planning to dual boot OpenBSD with another OS, you will need to read INSTALL.amd64.

OpenBSD/macppc:

Burn the image from the FTP site to a CDROM, and poweron your machine while holding down the C key until the display turns on and shows OpenBSD/macppc boot.

Alternatively, at the Open Firmware prompt, enter boot cd:,ofwboot /5.3/macppc/bsd.rd

OpenBSD/sparc64:

Put CD3 in your CDROM drive and type boot cdrom.

If this doesn't work, or if you don't have a CDROM drive, you can write CD3:5.3/sparc64/floppy53.fs or CD3:5.3/sparc64/floppyB53.fs (depending on your machine) to a floppy and boot it with boot floppy. Refer to INSTALL.sparc64 for details.

Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail.

You can also write CD3:5.3/sparc64/miniroot53.fs to the swap partition on the disk and boot with boot disk:b.

If nothing works, you can boot over the network as described in INSTALL.sparc64.

OpenBSD/alpha:

Write FTP:5.3/alpha/floppy53.fs or FTP:5.3/alpha/floppyB53.fs (depending on your machine) to a diskette and enter boot dva0. Refer to INSTALL.alpha for more details.

Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail.

OpenBSD/armish:

After connecting a serial port, Thecus can boot directly from the network either tftp or http. Configure the network using fconfig, reset, then load bsd.rd, see INSTALL.armish for specific details. IOData HDL-G can only boot from an EXT-2 partition. Boot into linux and copy 'boot' and bsd.rd into the first partition on wd0 (hda1) then load and run bsd.rd, preserving the wd0i (hda1) ext2fs partition. More details are available in INSTALL.armish.

OpenBSD/hp300:

Boot over the network by following the instructions in INSTALL.hp300.

OpenBSD/hppa:

Boot over the network by following the instructions in INSTALL.hppa or the hppa platform page.

OpenBSD/landisk:

Write miniroot53.fs to the start of the CF or disk, and boot normally.

OpenBSD/loongson:

Write miniroot53.fs to a USB stick and boot bsd.rd from it or boot bsd.rd via tftp. Refer to the instructions in INSTALL.loongson for more details.

OpenBSD/luna88k:

Copy bsd.rd to a Mach or UniOS partition, and boot it from the PROM. Alternatively, you can create a bootable tape and boot from it. Refer to the instructions in INSTALL.luna88k for more details.

OpenBSD/mvme68k:

You can create a bootable installation tape or boot over the network.
The network boot requires a MVME68K BUG version that supports the NIOT and NBO debugger commands. Follow the instructions in INSTALL.mvme68k for more details.

OpenBSD/mvme88k:

You can create a bootable installation tape or boot over the network.
The network boot requires a MVME88K BUG version that supports the NIOT and NBO debugger commands. Follow the instructions in INSTALL.mvme88k for more details.

OpenBSD/sgi:

To install on an O2, burn cd53.iso on a CD-R, put it in the CD drive of your machine and select Install System Software from the System Maintenance menu.

On other systems, or if your machine doesn't have a CD drive, you can setup a DHCP/tftp network server, and boot using "bootp()/bsd.rd.IP##" using the kernel matching your system type. Refer to the instructions in INSTALL.sgi for more details.

OpenBSD/socppc:

After connecting a serial port, boot over the network via DHCP/tftp. Refer to the instructions in INSTALL.socppc for more details.

OpenBSD/sparc:

Boot from one of the provided install ISO images, using one of the two commands listed below, depending on the version of your ROM.

ok boot cdrom 5.3/sparc/bsd.rd
or
> b sd(0,6,0)5.3/sparc/bsd.rd

If your SPARC system does not have a CD drive, you can alternatively boot from floppy. To do so you need to write floppy53.fs to a floppy. For more information see FAQ 4.3.2. To boot from the floppy use one of the two commands listed below, depending on the version of your ROM.

ok boot floppy
or
> b fd()

Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail.

If your SPARC system doesn't have a floppy drive nor a CD drive, you can either setup a bootable tape, or install via network, as told in the INSTALL.sparc file.

OpenBSD/vax:

Boot over the network via mopbooting as described in INSTALL.vax.

OpenBSD/zaurus:

Using the Linux built-in graphical ipkg installer, install the openbsd53_arm.ipk package. Reboot, then run it. Read INSTALL.zaurus for a few important details.

Notes about the source code:

src.tar.gz contains a source archive starting at /usr/src. This file contains everything you need except for the kernel sources, which are in a separate archive. To extract:

# mkdir -p /usr/src
# cd /usr/src
# tar xvfz /tmp/src.tar.gz

sys.tar.gz contains a source archive starting at /usr/src/sys. This file contains all the kernel sources you need to rebuild kernels. To extract:

# mkdir -p /usr/src/sys
# cd /usr/src
# tar xvfz /tmp/sys.tar.gz

Both of these trees are a regular CVS checkout. Using these trees it is possible to get a head-start on using the anoncvs servers as described here. Using these files results in a much faster initial CVS update than you could expect from a fresh checkout of the full OpenBSD source tree.

How to upgrade

If you already have an OpenBSD 5.2 system, and do not want to reinstall, upgrade instructions and advice can be found in the Upgrade Guide.

Ports Tree

A ports tree archive is also provided. To extract:

# cd /usr
# tar xvfz /tmp/ports.tar.gz

The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go read the ports page if you know nothing about ports at this point. This text is not a manual of how to use ports. Rather, it is a set of notes meant to kickstart the user on the OpenBSD ports system.

The ports/ directory represents a CVS (see the manpage for cvs(1) if you aren't familiar with CVS) checkout of our ports. As with our complete source tree, our ports tree is available via AnonCVS. So, in order to keep current with it, you must make the ports/ tree available on a read-write medium and update the tree with a command like:

# cd /usr/ports
# cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_5_3

[Of course, you must replace the server name here with a nearby anoncvs server.]

Note that most ports are available as packages through FTP. Updated packages for the 5.3 release will be made available if problems arise.

If you're interested in seeing a port added, would like to help out, or just would like to know more, the mailing list ports@openbsd.org is a good place to know.

https://darkmail.info/downloads/dark-internet-mailOpenBSD 5.3OpenSMTPDEmail-Statistics-Report-2013-2017-Executive-SummarOpen Source - Sendmail.comThe GNU Privacy GuardTor Browsertorbirdy – Tor Bug Tracker & WikiHaraka SMTP Email Server