![]() There are reasons people use Windows or Apple (perceived convenience), and reasons not to (long-term cost/benefit decisions for known uses). (I also recommend setting default umask to 0077 for the same reason, except while using pkg_add - I have a wrapper script that undoes it temporarily for that due to issues encountered.) To me, it seems worthwhile to have fewer 0-day bugs to worry about, and more reliable separation between user accounts (fewer privilege escalation bugs, etc etc). You can still use search engines, but once you learn your way around the documentation, you might find it is more reliable and quicker. But pristine is important when you care about security, and maintenance burden is a huge component of security, as are simplicity and transparency. I'm not one of those people who wants pristine for the sake of pristine. Follow the upgrade guide and delete outdated files (much easier since sysclean(8)), and a 10-year-old OpenBSD box can have a filesystem as pristine as a freshly installed system. While I've fortunately only rarely encountered significant problems with any of them, OpenBSD upgrades are the only ones where I can have any confidence in understanding and tracking how the system evolves across upgrades. The above have the same basic format and content as this one from 2004: I've been doing remote upgrades of OpenBSD and Linux (mostly Debian, but also occasionally Red Hat derivatives) for over 20 years. Notice how succinct and consistent (across decades!) are the upgrade guides. ![]() The upgrade guide for 6.9 gives a better flavor for how OpenBSD handles and documents subsystem and configuration changes: This release only includes changes related to SNMP, which I imagine are irrelevant to most people, though probably exciting for a subset of OpenBSD users. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |