The OpenBSD project has announced the release of OpenBSD 6.0. The OpenBSD project focuses on providing code and documentation that are correct and of high quality. This has lead to OpenBSD being regarded as a highly secure and reliable operating system. The new release features New/extended platforms: for armv7 – EFI bootloader added, kernels are now loaded from FFS instead of FAT or EXT filesystems, without U-Boot headers, a single kernel and ramdisk are now used for all SoCs, Miniroot installer images include U-Boot 2016.07 with support for EFI payloads, vax removed. Many new and improved hardware drivers and support for hardware-reduced ACPI implementations, for ACPI 5.0 implementations, initial support for MSI-X has been added, the xhci(4) driver now performs handoff from an xHCI-capable BIOS correctly, W^X is now strictly enforced by default etc.. Updated versions of LibreSSL and OpenSSH are included as well and feature several security enhancements.
Download and install:
Note: OpenBSD is a project released under the BSD 2-Clause license.
This license is recognized as free license, but is not copyleft.
Creating a bootable USB key using a Un*x-like system:
Some older systems may not be able to boot from USB keys or require
changing boot priority. Check your BIOS settings if you run into
First, you will need to obtain a local copy of the bootable filesystem
image miniroot59.fs or install59.fs as described above.
You should use the signify(1) and sha256(1) commands to verify
the integrity of the images with the SHA256.sig file on the mirror site.
Next, use the dd(1) utility to copy the file to the USB storage device.
The command would likely be, under OpenBSD:
dd if=miniroot59.fs of=/dev/rsdNc bs=1m
where N is the device number. You can find the correct device number
by checking dmesg(8) when inserting the media.
If you are using another operating system, you may have to adapt
this to conform to local naming conventions for the USB key and
options suitable for copying to a "raw" disk image. The key
issue is that the device name used for the USB key *must* be one
that refers to the correct block device, not a partition or
compatibility mode, and the copy command needs to be compatible
with the requirement that writes to a raw device must be in
multiples of 512-byte blocks. The variations are endless and
beyond the scope of this document.
If you're doing this on the system you intend to boot the USB key on,
copying the image back to a file and doing a compare or checksum
is a good way to verify that the USB key is readable and free of
Happy OpenBSD 😀