I run -current these days on most desktops. What I can say is that since 7.9, I have experienced smoother audio playback and system load overall on my decade-old laptop. So, it is likely that others will experience similar things when moving to 8.0.
> OpenBSD works well with relatively recent versions of Chromium and Firefox. That being said, they are on a six month release cycle. The Chromium port can fall behind if you stick to -stable or releases.
Just to clarify here, security patches are backported to -stable. So it is not like you stick to the same browser release for six months.
Personally, I run www/firefox-esr. In part because the ESR moves more slowly in general and in part because it is maintained by someone working for Mozilla.
"Still uses CVS", I mean, CVS worked twenty years ago and it still works today for all the platforms OpenBSD supports. If you prefer something else, that is all right, but here is emulators/wine on CVSWeb:
Plenty of issues that have been patched recently found using such tools as well. OpenBSD's policy remains largely the same as always: You need to understand the patch you propose and it needs to be maintainable. The link elsewhere in this thread is mainly discussing large patches where it is unclear if the LLM drew too heavily on code elsewhere.
OpenBSD's errata list has recently started growing rapidly, and the scale is a real departure from the past. I have taken to running syspatch much more regularly than in the past. Anyway, it's clear that the project's stance on AI is "as long as reports are detailed and high-quality (and probably from a person with a record of such work) the project will act on it." See slide 17 here: https://events.eurobsdcon.org/media/2026/submissions/ZGDXQR/...
Talked to bluhm@ after that talk in Brussels and the general feeling (from what I can remember from the conversation) so far is that there is a large increase in overall reports (good and bad), but that the severity of what is reported has not really increased. This also mirrors my own experience from reading source-changes@. In essence, it seems like we have known how to build secure software for the last thirty or so years, just that most do not seem to have bothered to do so.
"Can't even match GNU's coreutils"? Care to elaborate? Last time I checked OpenBSD is pretty much in line with Posix and there are plenty of us that consider many of the GNU extensions to be anti-features.
I use a Mac, so the CLIs are the BSD versions. I don't have any opinion on which is better, but it's just annoying that it's different from GNU, so a lot of my work ends up being on a Linux VM or server instead. POSIX compliance doesn't seem to buy me anything. I like the BSD license though.
That's a brand new excuse, Apple refused to distribute GPLv3 when GPLv3 was first published, 20ish years ago. How is GPLv3 incompatible with their system volume, yet GPLv2 is still fine?
GPLv3 added language which specifically requires that GPLv3 software embedded in products be distributed with "Installation Information" explaining how modified versions of that software can be installed. It is not at all clear how this would apply to software in an immutable, signed system volume. This language was not present in GPLv2.
You're entitled to your opinion, but that doesn't change the fact that the situation is "Apple can't distribute them", not "Apple doesn't want to distribute them".
Continuing to "correct" "want" to "can't" doesn't make sense, even under your interpretation of the situation. Even assuming the GPLv3 requires all software on the machine to ship under a compatible license (it doesn't), they can do that. They don't want to.
Of course, but any script meant for Mac is going to assume Mac core utils, even assume zsh instead of bash. You don't want to be the one person on the team with a non-stock setup.
> The GNU versions work fine in macOS. Apple doesn’t want to distribute them, but that’s mean you can’t use them.
We also test GNU coreutils on macOS. It is a bit tricky since the other maintainers and I don't own any macOS machines for testing. But we seem to do well enough with a shared system that Adélie Linux kindly allows the compile farm [1] to use, along with some additional CI machines.
I don't know how compatible my Mac will really be with a Free/OpenBSD machine. Last time I tested this theory, some C code I was building on Mac clang didn't build on FreeBSD clang cause I was unknowingly using some extension enabled by default. But that was about 12 years ago.
I'm not trying to. And it's not even like GNU/Linux/whatever is a superset of POSIX and I'm using the extensions. There are mutual differences in basic functionality.
"[Doesn't] get the job done"? Well, it gets my job done. You are welcome to use whatever you subjectively prefer (I use GNU's date(1) for a few scripts, but would prefer the English date grammar parsing as a tool of its own), but if you are unable to talk about anything in concrete terms there is not point in trying to discuss in good faith and I will just roll my eyes and move on.
I am not the parent commenter, but I have the same sense that the GNU ones are better.
But the only concrete example I can think of is that `cat -n a b`, if `a` doesn't end in a newline, produces something that is obviously not what the user wanted. GNU cat does it right.
I didn't report it to the openbsd people because I didn't want them to yell at me that `-n` is nonstandard anyway with no "right" behavior, so I should STFU. Which would be what I'd expect from having reported problems in the past.
I think the behavior in the GNU clone is more consistent with "we added line numbers to the concatenation tool" while whoever added it to OpenBSD's ancestry was probably more concerned with generating listings for printing.
Personally, I'd remove even the POSIX [-u] flag from all cat versions because all of them are un-UNIX-like.
Some GNU tools are particularly ridiculous with the Easter egg features I only know about because LLMs use them all the time —and I have been using Linux for 30 years.
Because you don't like the design(I don't either) but it carries information.
Someone could have thought it was a good idea and no one was willing to audit all of UCB's scripts to fix the "bug" even if it had been the result of a lazy implementation because ed(1) on a terminal.
My choice of wording is from my assumption that nobody, at any point, actually wanted that behaviour. And I stand by that being a pretty safe bet.
So I wouldn't refer to it as "the design". It's not that the methods are unsound, it's that I don't see any method at all.
As for not wanting to break existing scripts, OpenBSD is not even remotely as concerned about backwards compatibility as Linux is. I don't mean that in a derogatory way. It's a perfectly cromulent choice.
How is that ironic? If you know how to do this, ensure that the license of the code is compatible [1], and maintain the code, then send the patch to tech@ for review and maybe it gets in.
I think the security argument for carrying an alternative set of Posix-like utilities to Gnu Core Utilities is rather weak. These would mostly have been used to build other ports, or are you suggesting that this would harden the systems the ports build systems? If so, I would take the lower maintenance burden any day and just wait for the Linux ecosystem to make up their mind as to whether Uutils becomes the new standard or not.
What is this rubbish? We have "media" coverage trying to stir up drama about what happens on mailing lists now?
Go and read the thread yourself [1] and you will see that the reason it was rejected was that no one saw a reason to take on the maintenance burden when you already need to have Gnu Core Utils in ports to be able to build a heap of other ports. Focusing on theo@ calling out the submitter for having their judgement clouded by "Because Rust" misses the point.
Besides, Rust already has a solid presence in ports and I know several experienced OpenBSD developers dabbling in it. But the language will never make it into base in its current form as OpenBSD expects self hosting. I think everything in base is Posix(-like), apart from Perl.
You still see interesting efforts today. Here is a dmesg from a Tadpole SPARCbook 6500 booting 7.9 (released in May this year) that appeared on bugs@ just a few weeks ago (also, note who the person is that responds to that message):
You of course also have the absolutely insane luna88k support [1] and I have myself been looking into getting my hands on a landisk [2] box as the Hitachi SuperH CPU is fascinating (I only knew of it from old arcade boards and the Sega Dreamcast).
In my experience, groups like this have a fairly hostile relationship to State Communism as well. The Kronstadt rebellion for example is frequently cited [1]. But then you have groupings like Anarchist communists [2], which you would then risk lumping together with the anti-Communism part (not to mention that anti-Communism as a term is usually associated with forces staunchly opposed to people like this). Plus, if you are "only" anti-authoritarian, how do you suggest avoiding getting lumped together with Anarcho-capitalism?
Furthermore, these organisations operate in what they perceive to be Fascist and/or Capitalist societies, so why state opposition to something that is not "there" and has been pretty much gone from the global scene for nearly forty years?
In conclusion, yes, you have a point. But given the reasons above I find it really hard to get worked up over it and Anarchists do not generally get along with Leninists, Stalinists, or Maoists anyway.