DragonFly BSD 2.2 Released
An anonymous reader writes "DragonFly BSD 2.2 is now available. The second release to feature the HAMMER (versioning, among other things) filesystem — now considered production-ready — it includes 'major stability improvements across the board, new drivers, much better pkgsrc support and integration.' Apart from the CD ISO, this release has a DVD ISO with 'a fully operational X environment,' as well as a bootable USB disk-key image."
First post to say it's NOT dead!
-- I have a private email server in my basement.
...that somebody in BSD land is doing something genuinely different, and making it work.
http://michaelsmith.id.au
Hmmm, 4 posts and it's slashdotted? I hope their server isn't running on BSD, for the sake of its publicity :)
I was able to get in before it was fully slashdotted (it was crawling when there were only two posts here).
Here are some US mirrors:
CA ftp://mirrors.isc.org/pub/DragonFly/
TX ftp://mirror.evilprojects.net/pub/DragonFlyBSD/
VA ftp://ftp.theshell.com/pub/DragonFly/iso-images/
And some EU ones:
UK ftp://ftp.as6911.net/pub/DragonFly/
Germany ftp://chlamydia.fs.ei.tum.de/pub/DragonFly/
Here's the Release Notes:
Release Improvements
* A new DVD ISO release image is now available, in addition to the CD release. /usr. /usr.
* The new DVD release has a full X environment ready-to-go and many packages pre-installed.
* A full pkgsrc tar is now available on the CD/DVD in
* Full sources tar now available on the DVD (kernel sources only on the CD), in
* The nrelease build now trivializes package selection for people creating customized releases.
* The installer is now able to create a HAMMER filesystem setup.
Kernel changes
* First step towards AMD64 support (done by Jordan Gordeev during the Google Summer of Code 2008). /kernel to /boot/kernel and /modules to /boot/modules.
* The system control intr_mpsafe is enabled by default.
* Move
* Add RFC3542 support (done by Dashu Huang during the Google Summer of Code 2008).
* Add HW checksum support to the loopback interface, which doubles performance.
* acpi_cpu(4) update. It's now possible to use higher (lower power usage) C states than C1 in modern (multicore) CPUs.
* First steps to use network threads without the Big Giant Lock (this feature is considered experimental).
* Fixed CVE-2008-2476 IPv6 security issue with modified patches from NetBSD.
* bridge_input works now in parallel.
* Fix bugs in dealing with low-memory situations when the system has run out of swap or has no swap.
* Major rewrite of usched_bsd4 and related support logic, plus additional improvements to the LWKT scheduler.
* Major revamping of the pageout and low-memory handling code.
* suser_* replaced with priv_* implementation from FreeBSD.
HAMMER changes
* HAMMER is now considered production-capable. Many bug fixes and other improvements have been made. /boot. However, for production systems we still recommend a small UFS /boot followed by swap followed by one large HAMMER partition.
* It is now possible to boot from a HAMMER-only disk. No need for a single UFS partition for
* Add HAMMER read support to the boot loader.
* Now uses per-mount kmalloc pools for bulk data structures, particularly for inodes and records.
Hardware changes
* Add ACPI support module for IBM/Lenovo Thinkpad laptops (from FreeBSD).
* Add ACPI support module Asus laptops (from FreeBSD).
* Add acpi_video(4) - a driver for ACPI video extensions (from FreeBSD).
* It is possible to power down PCI devices during
Sadly, PS/2 was yet another victim of USB, which doesn't care what you plug into it, the electrical slut.
OS X (Which I love as a workstation) isn't doing BSD any favors... they still don't have threading right...
OS X is a kludge.
http://michaelsmith.id.au
So what you're saying is that efs2 and ffs/ufs can't touch this.
HAMMER TIME!
Javascript + Nintendo DSi = DSiCade
OS X is a kludge.
Freakin' Word. But it looks pretty.
Similes are like metaphors
OSX benefits from a foundation of Open Source software and a userland developed with a centralized control that holds the developer's paychecks.
The scratch-an-itch method of development works great for the kernel, but can get a little messy in the GUI.
That is one reason I think MS could survive doing the same thing Apple did with OSX.
What version of Perl are you running?
Now wash your hands.