I also would prefer that this split would not had place and that DragonflyBSD would never start ... but yet it happened ... so what?
Recently (as a seasoned FreeBSD user/sysadmin) I tried DragonflyBSD to check how it went ... and it lacks a LOT of things that FreeBSD has - like for example the GEOM framework.
On FreeBSD its quite easy to list block devices like:
FreeBSD # geom disk list
... but on DragonflyBSD its not possible as there is no GEOM ... so the only thing you can do is to:
DFBSD # camcontrol devlist
... but its far from usable and its very limited.
On FreeBSD I was able to write lsblk(8) Linux replacement ... I would not be able to do that on DragonflyBSD.
Yes - its a pity that such a talented person such as Matt Dillon left FreeBSD project - but DragonflyBSD is not a better replacement also ...
I think it's fair to say that DragonFlyBSD has diverged with vastly different goals to FreeBSD. It's a good thing it's able to do what it sets out to do. It's not trying to replace FreeBSD.
Recently (as a seasoned FreeBSD user/sysadmin) I tried DragonflyBSD to check how it went ... and it lacks a LOT of things that FreeBSD has - like for example the GEOM framework.
On FreeBSD its quite easy to list block devices like:
... but on DragonflyBSD its not possible as there is no GEOM ... so the only thing you can do is to: ... but its far from usable and its very limited.On FreeBSD I was able to write lsblk(8) Linux replacement ... I would not be able to do that on DragonflyBSD.
Yes - its a pity that such a talented person such as Matt Dillon left FreeBSD project - but DragonflyBSD is not a better replacement also ...
Regards, vermaden