DragonFly BSD Introduces A 'Stable' CVS Tag

bsdman writes "The DragonFly BSD project have recently introduced a new 'stable' tag in their cvs. If you ever wanted to use DragonFly BSD but was scared of any instability - now is your chance!"

Comments

Re:Which one?

[Draco_es]

It's my impression that OpenBSD is in the perfect balance between NetBSD (privileging portability) and FreeBSD (privileging efficiency and software availability).

I think OpenBSD is the less performant and scalable of the three, has less ports and suffers at high loads much more than the others. But it has better security defaults and pf is great. Don't you agree?

Re:Which one?

[JamesTRexx]

Maybe they don't want to admit they're not as happy with their distro as they say? Or maybe they're just the kind of poeple that want to "oohhh shiny!" kick from installing something new. (and maybe installing stuff is the only thing they do with it because they use their Windows box for games)
And then there might still be people who want to try them all because they can.

Re:Which one?

[m.dillon]

No, the VM subsystem... that is, the concept of using stackable VM Objects, is going to stay in. I do want to implement a copy-on-write mechanism for pages owned by in-progress I/O to avoid stall situations that still exist in FreeBSD (despite Kirk's filesystem bitmap hacks, which only really fixed the worst of the stalls). There are also some kernel memory subsystem interactions with the VM system that need cleaning up to make things more MP friendly, and vm_map's and a few other areas need some algorithmic cleanups... but it's just cleaning up, not a rewrite. Generally I believe the VM Object based VM subsystem used in FreeBSD and DragonFly to be superior to the mechanisms used in other BSDs and in Linux.

-Matt