The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 10.0-RELEASE. This is the first release of the stable/10 branch. Some of the highlights: * GCC is no longer installed by default on architectures where clang(1) is the default compiler. * Unbound has been imported to the base system as the local caching DNS resolver. * BIND has been removed from the base system. * make(1) has been replaced with bmake(1), obtained from the NetBSD Project. * pkg(7) is now the default package management utility. * pkg_add(1), pkg_delete(1), and related tools have been removed. * Major enhancements in virtualization, including the addition of bhyve(8), virtio(4), and native paravirtualized drivers providing support for FreeBSD as a guest operating system on Microsoft Hyper-V. * TRIM support for Solid State Drive has been added to ZFS. * Support for the high-performance LZ4 compression algorithm has been added to ZFS. For a complete list of new features and known problems, please see the online release notes and errata list, available at: http://www.FreeBSD.org/releases/10.0R/relnotes.html http://www.FreeBSD.org/releases/10.0R/errata.html For more information about FreeBSD release engineering activities, please see: http://www.FreeBSD.org/releng/
Ken Thompson had been working on a time-sharing system for Bell Labs when the project was cancelled. Meanwhile, Dennis Ritchie had invented a new programming language called C. While operating systems had previously been written in machine code, these two realized that computers were powerful enough to allow an operating system to be written in C instead. This meant that an operating system could present the same capabilities on any hardware system. Programmers could use the same toolkits on different machines, instead of rewriting the toolkit each time a machine became obsolete. Thompson and Ritchie called this new operating system Unix. (Raymond 8-9)
A recently discovered vulnerability that affects 64-bit FreeBSD systems running on Intel hardware could lead to exploitation of higher privileges by users that already have local system access. Intel adamantly claims that the vulnerability is a result of software implementation issues, rather than their processors.
The FreeBSD security advisory regarding this matter states the following about the impact:
“Successful exploitation of the problem can lead to local kernel privilege escalation, kernel data corruption and/or crash. To exploit this vulnerability, an attacker must be able to run code with user privileges on the target system.”
The FreeBSD Security Team goes on to advise that updating the system is the only resolution that will address the problem. Please note that it is necessary to reboot after this update as it involves patching the kernel.