@ SirDice - I have to agree with some of the others here. While the "fix" is not that complicated, it is nonetheless not good enough.
This issue is going to crop up with every new minor release
...
It's a minor inconvenience during the first three months of a new release, nothing more.
Again, it's not a show-stopper, but it would only be considered a "minor inconvenience" if it was clearly communicated
beforehand, with a "solution" communicated
beforehand.
This seems like something that should be addressed, not accepted.
Even the guys at bugs.freebsd.org think so.
New users may not know how to deal with it but they can easily find out how to fix it
Where exactly? Serious question. Because I read the Release Notes, I read the Errata. Didn't see anything about, and just got blind-sided by it.
Do you mean here, in this thread? Or here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250700
While it is great that these two sources exist, they are really only useful
after the fact.
Desktop users are a minority, and only a small percentage of that minority may have some minor issues.
FreeBSD is marketed as a General Purpose Operating system, is it not?
I actually run my business from a FreeBSD desktop/laptop (dumb?) and I lost a whole day of work (boohoo, I know), and so did my clients. Funny how this is a "minor issue" for me, but not for those running FreeBSD on a server.
FWIW, building from ports worked for me too. Nonetheless, I still feel like this should have been communicated better, or fixed beforehand.
So, for future reference, and for those in the same position as me:
Where could I have read about this problem (and solution) before I upgraded?