BSDCon '03 Nearly Here (OpenBSD 3.4, Too)
An anonymous reader writes "Pre-orders for the OpenBSD project's latest release, 3.4, are now being taken. This release will ship around November 1st. Significant enhancements have been made in this release, including i386 switch to ELF executable format, further W^X improvements for i386, ld.so on ELF platforms now loads libraries in a random order for greater resistance to attacks, inclusion of a static bounds checker to the compiler for basic checks on functions which accept buffers and sizes, strcpy/strcat function audit to replace with safer strlcpy/strlcat, ProPolice stack protection in the kernel, further manual page cleanups, large number of bug fixes and optimizations to the packet filter (PF) including packet tagging, stateful TCP normalization, passive OS detection, SYN proxy, and adaptive state timeouts, and many other improvements to the rest of the system.
Order a CD from the OpenBSD store. Ordering a CD helps support the project, as a bonus you get cool stickers, artwork, and an audio track!"
The same reader sent links to more information on this release, including new features, and the changelog between 3.3 and 3.4.
The technical sessions start on September 10th, so there's still lots of time to register and book plane tickets.
Speaking of the 10th... I'd better start working on my slides.
Tarsnap: Online backups for the truly paranoid
Theo has said many times before that they will only use GNU tools if there's nothing to replace them with. Infact, the good folks at @openbsd have been looking into replacing gcc with tunDRA (with little success atm) simply because of the GNU licence.
Basically, GNU licenced programs are only there if really necessary.
FreeBSD chose to address this problem by making fsck capable of running in the background. fsck cooperates with the kernel, checking all files/inodes, and when a file is requested that has not yet been checked, the file operation is held while that check is moved to the front of the unique "moustache ride-ordered" queue.
Journaling without sacrificing performance and clean algorithms simply isn't possible, and corruption is still possible on a journaling filesystem with out-of-order writes as done by many kinds of cache-enabled drives and controllers, leading to a false sense of security when fsck is bypassed. FreeBSD's approach catches every situation, and guarantees an intact filesystem on every boot.
I've never quite understood how the BSD people can think they've got freedom when their work may be locked down and stolen by a corporation any time.
You don't understand the BSD license. It's impossible to steal something that's given freely. BSD has been such a seminal influence precisely because the code can be "stolen". That's the intent.
Besides, AT&T did try to steal (in the "you can't use it anymore" sense of the word) BSD's code. They lost.
If he thinks separating from the protection granted by GPL will further the survivability of OpenBSD, he's seriously mistaken.
BSD predates the GPL.
When someone might yell at me, it has to be OpenBSD.