DragonFly BSD Releases Version 2.0 43
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."
Stop! (Score:5, Funny)
HAMMER-time!
Re:Stop! (Score:5, Funny)
HAMMER-time!
Yes, but which HAMMER-time? HAMMER-atime, HAMMER-ctime, or HAMMER-mtime?
Re: (Score:2)
What? Get with the times man!
What about HAMMER-relatime?
Re: (Score:2, Funny)
sounds like this BSD is to legit to quit!
Another filesystem? (Score:1)
Re: (Score:3, Insightful)
Re:Another filesystem? (Score:5, Informative)
No, because a bunch of douchebags keep making them all under licences which do not allow for proper intergration into other operating systems and because HAMMER is designed for distributed filesystem work, a field where there are limited existing systems.
Re:Another filesystem? (Score:5, Informative)
So whose fault is that? ZFS has been and continues to be adopted by other operating systems. The GPL is a manifestation of a polical agenda and the inability to incorporate ZFS is a consequence. That is Linux's problem, not the folks that release their open-source filesystems under the licenses of their choosing.
Just because somebody doesn't buy into Stallman's agenda doesn't mean they are a douchebag.
Re: (Score:1, Insightful)
The other AC might be talking about filesystems which are licensed under the GPL which makes those developers douchebags.
However, don't let that stop you from defending your pet project.
It's the patents, Rufus. (Score:2)
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-compatibi
Re: (Score:1)
Re: (Score:3, Insightful)
No, he's probably talking about GPL licensed filesystems which can't work kind of anywhere.
The guy above was probably pro-BSD license, so his point was probably that others can use hammer but they can't for instance get XFS.
Re: (Score:2)
That means CDDL doesn't give BSD-licensed systems any problems. Obviously ZFS also works on OpenSolaris which is fully open source as well.
Re:Another filesystem? (Score:4, Informative)
Ignoring the license for the moment, ZFS has a lot of desirable features. But it also tries to throw in the kitchen sink, far more then I personally believe a file-system should deal with. I haven't tried it myself so I don't know how well it performs.
HAMMER takes a different approach to redundancy. HAMMER is eventually intended to operate in a replicated multi-master clustered environment. The first release only has the beginnings of that work (aka single-master/multi-slave replication), but the basic principle that HAMMER follows is that no single copy of a file-system can ever be considered safe, no matter how much redundancy you throw into it. Software bugs are far more likely to corrupt a file-system then hardware issues.
Up until now snapshots have always been fairly expensive affairs. They run the gauntlet from outright dangerous in UFS to fairly quick in ZFS, but of all the OSS offerings only HAMMER gives you a fine-grained (~30-60 second interval if you don't lift a finger) historical access to the entire filesystem. All you need is a transaction id and you cd directory@@transaction_id and, poof, you are looking at a file or the entire filesystem as of some point in the past. You have full administrative control over what historical data is kept and what is thrown away, independent for each of your mirrors, backup systems, whatever.
After all, we need to justify getting those cheap, terrabyte+ drives coming out now!
-Matt
Re: (Score:2)
Bringing up Bitkeeper doesn't make any sense here. What if Bitkeeper was CDDL, BSD, or Mozilla licensed? There would have been no problem using it to track the Linux configuration. Stallman correctly predicted the final consequence of using Bitkeeper, but that had nothing to do with the GPL or his agency of 100% open source code. That's just keeping yourself outside the mercy of others which applies in al
Re: (Score:2)
No.
VirtualBox? (Score:3, Informative)
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. :|
Re:VirtualBox? (Score:5, Informative)
VirtualBox has some issues [virtualbox.org] with FreeBSD.
I tried to install a recent release of FreeBSD which ended up in frequent hangs related to the network adapter.
Changing the network adapter type seems to fix the problem.
Re: (Score:2)
Well, in my case even disabling the network adapter altogether didn't change a thing. Hangs with a different network adapter type, hangs with no network adapter.
Just to verify, the same virtual machine (with the same configuration) has DesktopBSD (another FreeBSD variant) already installed, and that boots up just fine. Even though the network in DesktopBSD doesn't work, it at least boots up without hanging. No such luck with DragonFly.
Re: (Score:2)
VirtualBox in general has a lot of issues with most BSD projects.
MidnightBSD (which was forked from FreeBSD 6.1) worked with earlier versions of VirtualBox, but can't work with later versions.
Re: (Score:3, Informative)
As far as we can tell VirtualBox does not properly emulate the 8254, which we use for timer interrupts. We run it in a different mode then linux does and my guess is that VB doesn't emulate that mode.
People have told me that DFly does run under VMWare and MS virtualization and QEmu. And natively, of course.
-Matt
But... (Score:1, Funny)
this can't be!
BSD was dying just the other day.
And it was true, I read it on slashdot!
Re: (Score:2)
And it was true, I read it on slashdot!
There's your problem: you didn't assess truth based on Netcraft confirmation.
Re: (Score:2)
You know, just to counter that old joke they totally should have named this PhoenixBSD instead. BSD dieing? Been there, done that. Now I'se back.
Of course, ZombieBSD has a nice ring too . . .
Captain Hammer says (Score:4, Funny)
The Hammer is my...filesystem
Bilbo says.. (Score:2)
Hey baby, wanna take a ride on the dragon*coughflycough*?
Re: (Score:2)
Only if I can put on my robe and wizard hat.
Cool! (Score:2, Insightful)
Many good things came from BSD in tha past. Seems this trend continues!
bsdtalk interview with Matthew Dillon (Score:5, Informative)
But will it run... (Score:2)
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.
Re: (Score:2)
Seems like the 2.0 packages aren't built yet, and not all sources seemed to be on the mirror google showed first, anyway there is a UAE package for DragonFly 1.12 so there probably is one for 2.0 as well.
Not that you thought there wasn't one :)
Description of Hammer (Score:3, Informative)
Matt has posted a very in-depth PDF whitepaper describing the Hammer filesystem [backplane.com]. A very interesting read!
A couple of concerns about Hammer (Score:2)
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.