25/06/2016 – Johnny Hughes has announced the release of CentOS 6.8, a community distribution which is built using the source code of Red Hat Enterprise Linux. The new release features a number of important changes, including depreciated drivers and packages as well as new features. “CentOS Linux 6.8 is derived from source code released by Red Hat, Inc. for Red Hat Enterprise Linux 6.8. All upstream variants have been placed into one combined repository to make it easier for end users. Workstation, server, and minimal installs can all be done from our combined repository. All of our testing is only done against this combined distribution. There are many fundamental changes in this release, compared with the past CentOS Linux 6 releases, and we highly recommend everyone study the upstream release notes as well as the upstream technical notes about the changes and how they might impact your installation.“
Download CentOS 6.8 i386:
Download CentOS 6.8 x86_64:
CentOS-6.8-x86_64-LiveCD.iso – The disk can also be used to install CentOS 6.8 onto your computer but without offering any package selection options at install time.
CentOS-6.8-x86_64-LiveDVD.iso – The disk can also be used to install CentOS 6.8 onto your computer but without offering any package selection options at install time.
CentOS-6.8-x86_64-bin-DVD1.iso and CentOS-6.8-x86_64-bin-DVD2.iso – These two dvd images contain the entire base distribution. Please burn DVD1 onto a DVD and boot your computer off it. A basic install will not need DVD2. After the installation is complete, please run “yum update” in order to update your system.
CentOS-6.8-x86_64-minimal.iso – The aim of this image is to install a very basic CentOS 6.8 system, with the minimum of packages needed to have a functional system.
CentOS-6.8-x86_64-netinstall.iso – This is the network install and rescue image.
One can do USB key installs by using dd to copy individual ISO files to a USB key using the device name (not the partition name). This will overwrite the entire USB key. Here is an example for the DVD1:
dd if=CentOS-6.8-x86_64-bin-DVD1.iso of=/dev/sdb
Happy CentOS 😀
The OpenBSD project has announced the release of OpenBSD 5.9. 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 W^X (write or execute) security for 32-bit x86 processors, many new and improved hardware drivers and support for installing OpenBSD on GPT partitioned hard drives. This release features a forked version of the “less” command and network stack improvements. 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 😀