The DragonFly installer has been modified to produce disk arrangements that will generally match between UFS and Hammer installs, plus directories where you usually don’t want Hammer history or backups (like /tmp or /usr/obj) are now under /build and null-mounted to where you’d expect, since null-mounting works transparently well on DragonFly. Matthew Dillon has a note explaining the whole thing.
2 Replies to “New DragonFly installer disk arrangement”
Comments are closed.
i’d like gpt support in the installer =/ it’s the only thing lacking for me to test dfly on my machine
The explanation sounds right on to me. Consistency is a beautiful thing.
And encrypted root option for UFS without manual intervention now too.
What’s not to like? :)