Dan writes "FreeBSD's Robert Watson says that effective today, newfs(8) and sysinstall(8) will create UFS2 file systems by default, unless explicitly specified. Users wanting to create UFS1 file systems for whatever reason (interoperability with earlier versions, etc) should be sure to employ the -O1 flag to newfs(8), or hit '1' in the label editor in sysinstall(8) to select UFS1."

jschauma writes "The NetBSD Project is pleased to announce that release 1.6.1 of the NetBSD operating system is now available . NetBSD 1.6.1 is a maintenance release for users of NetBSD 1.6 and earlier, with binary releases for 40 ports, and of course also including NetBSD's Packages Collection. A complete list of changes can be found in CHANGES-1.6.1. Please use a mirror close to you."

BSDForums writes "On all but the smallest TCP/IP network, it's handy to configure network information for computers automatically. That's what DHCP does. It's easy to act as a DHCP client, but configuring a server is a little trickier. Dru Lavigne introduces DHCP and explains what you need to know to setup a simple DHCP server."

Starrider writes "It seems the DARPA grant for OpenBSD and for University of Pennsylvania has been cancelled (?) immediately and without warning. See the full story in Theo's email and on deadly.org." Theo is left to only speculate why funding was suddenly pulled. One also has to wonder what this means for the University of Pennsylvania, since they were also in for a piece of the pie.

Dan writes "Julien Bordet announces that Packet Filter (PF) now has "pfsyncd" - the ability to synchronize states across multiple firewalls. Kernel patches and alpha source code to the userland daemon can be found here. This is an alpha release meant for testing and should not be used in production. Testing, patches, and feedback is greatly appreciated."

flynn_nrg writes "Even although version 3.3 is not out yet, users can already enjoy the new 3.3 song: "Puff the Barbarian". Like other Barbarians before him, Puff has had to face some pretty crazy challenges. This song is an allegory of the recent difficulties we went through dealing with Sun, who refused our request for documentation about their UltraSPARC III processors. We want documentation, because these are the fastest processors with a per-page eXecute bit in the MMU, needed to fully support our new W^X security feature. In the meantime, the AMD Hammer has come onto the scene, and this processor supports an eXecute bit in 64-bit mode. And it is going to be faster... Both mp3 and ogg versions available."

A reader writes:"There's a story on ZDNet that describes how Theo de Raadt & co. are hoping to eliminate buffer-overrun exploits for good. On closer inspection, it's a scheme to stop a buffer-overrun leading to executable code. It doesn't stop the buffer-overrun itself."

Dan writes "The first of the GNOME 2.4 development releases is now available. Code named 'Mighty Atom,' this FreeBSD release includes quite a few new proposed modules. Those wanting to test this release should checkout the ``ports'' module per these instructions. Be sure to download the ``marcusmerge'' script from the same page. This script will help you merge the GNOME development ports tree into your main ports tree."

BSDForums writes "Open source never stands still. Even the flexible and mature BSDs are continuing to evolve. In this article, Michael Lucas looks at the NetBSD upgrade process, demonstrating the most common steps to stay abreast of the current source code. This article isn't a comprehensive tutorial that covers every possible situation; rather, it covers the most common situation: updating your source with CVS, building that source code, and installing it on the build machine."

Dan writes "Interesting read on running .NET on FreeBSD. Chip Morton thinks this could be very beneficial to FreeBSD or any OS to have a fully functional .NET CLR (Common Language Runtime) environment. With over 9,000 files, and including some 1300 public classes to pore through, the Shared Source CLI (Common Language Infrastructure) can teach you quite a bit about the internal workings of the CLR. This relevant MSDN article discusses some of the things you can learn from the source code facsimile of the CLR, like how JIT compilation works. One thing that the CLI specification does not mandate is that managed code has to run on Windows. To prove this point, Microsoft built the Shared Source CLI to compile and run on FreeBSD Unix as well as Windows XP."

drdink writes "A few weeks ago, PAE (Physical Address Extension) support was added to FreeBSD 5-CURRENT. This allows memory above 4GB to be used normally by the kernel and userland on the x86 platform. Jake Burkholder, the man behind PAE, is now looking for users to help him test this new feature. In his message to the freebsd-current mailing list, Jake describes the current caveats to PAE and also says 'We'd like this feature to be solid for 5.1-RELEASE, so I'm hoping there are people out there with systems with more than 4G of ram that are willing to test it.' This, along with other features make FreeBSD 5-STABLE look very promising."

craig2787 writes "FreeBSD developer Peter Wemm has successfully booted FreeBSD on a real AMD ClawHammer CPU, in both 64- and 32-bit modes. Original posting to the -current mailing list is here."

An anonymous reader writes "FreeBSD's fast as is, but it appears that folks over there are going the extra mile to make sure that it continues to be the top dog according to this recent announcement. With 5.1 promising to have native threads and 5.1 only a few months out, it is really good to see performance being taken seriously."

Anonymous Coward writes "Onlamp.com publishes the sixth paper of Emmanuel Dreyfus's series on NetBSD's IRIX binary compatibility implementation. This time, this is about reverse engineering IRIX multithreading and the odd virtual memory features involved with it. It's an adventure at kernel and userland boundaries, with a debugger as the sole weapon. A must read!"

An anonymous reader writes "Canada's National Post is reporting today that DARPA is (indirectly) funding $2-million (US) to Theo de Raadt of OpenBSD. The article is available here." Update: 04/07 21:01 GMT by T : As several readers have pointed out, this blurb should credit instead The Globe and Mail rather than the National Post.

BSD Forums writes "OpenBSD recently changed the mode of operation for the Apache webserver from the normal non-chrooted operation to chrooted operation. This enhances the security of the server on which Apache is run but it imposes a few challenges to the system administrator. In this article Marc Balmer discusses selected aspects of running a chrooted HTTP daemon and present strategies on how to set up a chrooted environment for more complex applications like database access or using CGI-scripts."

Dan writes "FreeBSD's Murray Stokely announces the long awaited availability of FreeBSD 4.8, the latest FreeBSD-stable release, which has dealt with known security issues, and added initial support for Firewire, HyperThreading, and other new hardware technologies. Murray says that the new release is also the result of conservative updates to a number of software programs in the FreeBSD base system, see FreeBSD 4.8 release notes for more information."

Gentu writes "The main commercial company behind NetBSD is Wasabi Systems. The company has contributed advances and big chunks of code to the open source project, while they do offer a boxed release of NetBSD. However, their main business for the company is the embedded market and NetBSD is marketed as an embedded OS. OSNews talked to the Vice President of Wasabi Systems, Jay Michaelson. Linux in the embedded market is also discussed."

Dan writes "FreeBSD Release Engineering Team's Bruce Mah provides the latest status of what's holding up the official release of FreeBSD 4.8. We fully support FreeBSD RE's approach to fixing necessary problems before officially releasing the product."

An anonymous reader writes "As seen on this article on the OpenBSDJournal, Henning, one of PF main contribuitors writes: 'After much discussion we made a hard decision: we will change pf syntax from English to German.' So, what are the implications of this? And why the change? Read on."