4 ms·
The auto partitioning is a bit of a mess for sure. Really no idea why it insists on splitting it into 5 partitions when just a seperate /usr/local mounted with
by jamal-kumar 3y ago
The auto partitioning is a bit of a mess for sure.
Really no idea why it insists on splitting it into 5 partitions when just a seperate /usr/local mounted with the wxallowed flag is mostly fine.
Other than that though it's mostly just hitting enter a bunch of times if you ever want to give it a shot again.
- sillywalk 3y agoI just wish that you could adjust the size of the partitions, rather than having to format and start again.
- daneel_w 3y ago>"Really no idea why it insists on splitting it into 5 partitions when just a seperate /usr/local mounted with the wxallowed flag is mostly fine." Because OpenBSD recommends having nosuid on everything that isn't /, /usr and /usr/local, and nodev on everything that isn't / (where /dev lives).
- detourdog 3y agoEach of the BSD's have their own personality and group of adherents. There is a secondary circle that may love all BSDs. Long ago there was east coast unix and west coast unix. The BSDs represent the West Coast thread. I just like the BSDs because they all maintain a single document that can get you from a single system host install to a supporting network installs DHCP->TFTP install. I always go for either NetBSD "We install on anything" or OpenBSD "We are still just trying to get secure implementation of the 4.4 spec"
- dmvdoug 3y agoI’d love to read more about the differences in “personality” among the BSDs. Any suggestions on material to look at?
- vogon_laureate 3y agoThey explain the reasoning thus[1]: Unlike some other operating systems, OpenBSD encourages users to split their disk into a number of partitions, rather than just one or two large ones. Some of the reasons for doing so are: • *Security: Some of OpenBSD's default security features rely on filesystem mount options such as nosuid, nodev, noexec or wxallowed.* • *Stability: A user or a misbehaved program can fill a filesystem with garbage if they have write permissions for it. Your critical programs, which hopefully run on a different filesystem, do not get interrupted.* • *fsck(8): You can mount partitions that you never or rarely need to write to as readonly most of the time, which will eliminate the need for a filesystem check after a crash or power interruption.* [1]: https://www.openbsd.org/faq/faq4.html#Partitioning