DragonFly BSD Releases Version 2.0
An anonymous reader writes "DragonFly BSD 2.0 has been released!
It includes HAMMER, DragonFly's brand-new file system supporting advanced features like history, snapshots and various other cool things. Will it become the new ZFS?
Since it is BSD licensed it could also be integrated into various other operating systems."
HAMMER-time!
Knowledge is power. Knowledge shared is power lost.
Oh why? Don't we already have enough of them?
You can be twitter too!
Did anyone manage to get the live cd work on VirtualBox? On my Ubuntu box it seems to hang once I get to the screen with various options of booting DragonFly. :|
this can't be!
BSD was dying just the other day.
And it was true, I read it on slashdot!
The Hammer is my...filesystem
Hey baby, wanna take a ride on the dragon*coughflycough*?
which is totally what she said
Many good things came from BSD in tha past. Seems this trend continues!
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
If you want to know more about the hammer file system, check http://bsdtalk.blogspot.com/2008/07/bsdtalk154-matthew-dillon.html
But will it run AmigaOS?
Seriously, I'm glad to see this. Matt Dillon is a brilliant programmer with much broader OS experience than most of the folks driving OS development these days, so I have no doubt that he's doing amazing things.
That's the small problem. The bigger problem is nobody can make their own ZFS-compatible implementation on Linux because unless you're using the CDDL code, you don't get patent rights. And ZFS has several dozen patents on it. You have to use the CDDL code (or negotiate a separate patent license agreement with Sun, I suppose).
Yeah, I know GRUB has rudimentary ZFS support under GPL, but that's not what people are interested in.
I'm not sure why nobody is taking the FreeBSD route and making Solaris-compatibility API's for Linux such that end users could use the CDDL code.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
Matt has posted a very in-depth PDF whitepaper describing the Hammer filesystem. A very interesting read!
My other account has a 3-digit UID.
1. Thus it takes two flush cycles to fully commit an operation to the media, since a crash which occurs just after the first flush cycle returns cannot guarantee that the META buffers had all gotten to the media, and upon remounting the UNDO
buffers will be run to undo those changes.
What does this mean for fsync() and databases?
2. As seems to be standard for new file systems, there seems to be no fsck.
I mislike this.