Theologian Dr Corey Stephan has documented his exploration of installing OpenBSD on an old ThinkPad X270. He has posted his rather thorough personal notes which cover the intial setup, such as power management, performance tweaks, Wi-Fi configuration, audio and video, tracking -current, and getting software from the ports tree. He also goes into a bit of his favored tools and workflow.
It is hard not to cherish the partnership of a slightly older ThinkPad and OpenBSD. The ThinkPad X270 and OpenBSD are both minimalist, robust, and customizable. Specifically, the ThinkPad is minimalist with regard to features, robust with regard to physical durability, and customizable with regard to hardware repairability and replaceability. OpenBSD is minimalist with regard to code, robust with regard to security, and customizable with regard to every aspect of the system. Further, since a healthy number of OpenBSD's developers long have used ThinkPads (to the point that I have read some jokes come out of members of their ranks like 'I may use any kind of laptop that I may like, as long as it is a ThinkPad'), the operating system works brilliantly on the laptop — both with their stock settings.
Overall, installing and configuring OpenBSD -current on the ThinkPad X270 was the simplest minimalist installation of any operating system on any hardware that I ever have done, even simpler than Debian GNU/Linux or my beloved FreeBSD (and much simpler than a proprietary, dysfunctional operating system Windows or MacOS). Was the total setup process easier than, say, that of a GNU/Linux distribution that uses the Calamares installer and comes preconfigured with a huge array of GNU/Linux drivers? Well, no, it was not, but that is not the point. OpenBSD is secure, nimble, and customizable in an elegantly simple way that interoperates smoothly with this small ThinkPad for my mobile academic research and writing. Even in this topsy-turvy era in which other popular desktop operating systems are have many design choices for form over function, OpenBSD comes as a serious, professional product that is ready to let me focus on my work.
Previously:
(2021) Recent and Not So Recent Changes in OpenBSD That Make Life Better
(2020) Using OpenBSD Routing Tables to Segment the Home Network for Privacy
(2018) OpenBSD Chief De Raadt Says No Easy Fix For New Intel CPU Bug
and many others.
(Score: 3, Informative) by canopic jug on Sunday April 23, @04:41AM (4 children)
When OpenBSD works, it works well. Their team focuses on quality and correctness. I would not be surprised if the total number of OpenBSD developers over the lifetime of the project was smaller than the current number of active Linux (kernel) developers by at least an order of magnitude so the support is going to be limited pretty much to what the developers themselves need, DRM issues aside. However, between restricted boot [fsf.org] and other DRM gotchas, including legal tangles [copyright.gov], FOSS, including the BSDs and even Linux, will soon be locked out of new hardware forever.
Money is not free speech. Elections should not be auctions.
(Score: 2, Insightful) by Anonymous Coward on Sunday April 23, @07:23AM
Really? Lots of big customers are using Linux. I'm sure AMD and gang will happily sell to Amazon, Google, Cloudflare, etc if Intel and gang don't want to.
Lots of those motherboard manufacturers support "secure boot" but don't require it. Heck some don't even care about enforcing it by default... ;)
(Score: 1, Insightful) by Anonymous Coward on Sunday April 23, @09:31AM (1 child)
I've been reading about this happening "soon" or "in the near future" for over 20 years now.
(Score: 4, Touché) by canopic jug on Sunday April 23, @11:35AM
I've been reading about this happening "soon" or "in the near future" for over 20 years now.
Exactly. And you'll notice that each year, more of the technologies warned about get established in the market. First they are off by default, then on by default but can be disabled, then mandatory.
Money is not free speech. Elections should not be auctions.
(Score: 1, Touché) by Anonymous Coward on Monday April 24, @05:14PM
Secure boot tells a PC "Don't run unsigned code at boot."
IMHO, the bug there isn't that Secure Boot exists and is enabled. The bugs are:
a.) the default keys for secure boot come from Microsoft and not a trusted third party.
b.) there is no standard procedure between hardware manufacturers for creating and deploying a new trusted key.