We are still actively working on the spam issue.
Difference between revisions of "DragonflyBSD"
(Created page with "thumb|Mascot of DragonflyBSD {{stub}} '''DragonflyBSD''' is a free, UNIX-like operating system that is part of the BSD family. It is based o...") |
|||
Line 8: | Line 8: | ||
* Virtual kernels providing the ability to run a full-blown kernel as a user process for the purpose of managing resources or for accelerated kernel development and debugging | * Virtual kernels providing the ability to run a full-blown kernel as a user process for the purpose of managing resources or for accelerated kernel development and debugging | ||
* Token-based synchronisation mechanism for it's kernel, in turn allowing for DragonflyBSD to parallelize the system with less effort compared to other kernels, which primarily use hard mutex locks. | * Token-based synchronisation mechanism for it's kernel, in turn allowing for DragonflyBSD to parallelize the system with less effort compared to other kernels, which primarily use hard mutex locks. | ||
− | * Optimised for SSD usage. | + | * Optimised for SSD usage by utilising a swapcache. |
+ | * [https://www.dragonflybsd.org/~labthug/handbook/linuxemu.html Linux binary compatability] |
Revision as of 14:29, 6 October 2016
DragonflyBSD is a free, UNIX-like operating system that is part of the BSD family. It is based on the same UNIX ideals and APIs and shares ancestor code with other BSD operating systems.
It contains a bunch of useful features which sets it apart from other BSD/Linux-based operating systems, one being HAMMER - it's own high-performance filesystem with built-in mirroring and historic access functionality.
Other features include:
- Virtual kernels providing the ability to run a full-blown kernel as a user process for the purpose of managing resources or for accelerated kernel development and debugging
- Token-based synchronisation mechanism for it's kernel, in turn allowing for DragonflyBSD to parallelize the system with less effort compared to other kernels, which primarily use hard mutex locks.
- Optimised for SSD usage by utilising a swapcache.
- Linux binary compatability