johnr2

> Presumably not on mainline kernel.

At first it was necessary to compile the realtime-lsm module to allow user programs to make use of realtime scheduling. In late 2006 or so (IIRC) rlimits-aware PAM became available which made realtime-lsm redundant.

I've used CONFIG_PREEMPT=y (along with CONFIG_HZ=1000) when compiling mainline kernels all along. My current distro of choice (Void) enables these by default in their 5.4 series kernels. I've never needed PREEMPT_RT for my particular use case.

AFAIK FreeBSD still doesn't allow users to run programs with realtime scheduling privileges (SCHED_FIFO or SCHED_RR), only root.

From the article: "I started using FreeBSD in 2016 as a dual-boot with Linux. The reason was that at the time Linux provided no support for real-time threads and preemptive scheduling"

I've been using real time threads and preemptive scheduling on my Linux audio workstations since 2005. Am I missing something here, or is that date in the article a typo?

> How many developers that could evolve into great developers have been stunted because someone denied them the opportunity to become competent?

Nobody is denying anyone. The code is there to read as an example. If an aspiring developer hasn't got the initiative to develop at least a basic level of competence on their own, that's their problem. What happened to self-reliance?

> I believe that is anti-community in spirit and non-conductive to solving the issue you claim exists.

You presumably haven't encountered this issue with your own open-source projects, but that doesn't mean the problem doesn't exist.

>Computers should work for us. We shouldn't work for computers. Dump .txt for .text.

If my computer expects me to type an extra letter every time I name a file it isn't working for me. The short extensions make for more efficient typing.

> I wish Digital Ocean would do something about the amount of abuse from their network.

Yes. After blocking the usual suspects, the great majority of SSH brute force attempts I see in my server logs now come from Digital Ocean IP addresses.

> the Left's common enemy is the Right, and vice versa

The common enemy of both is the moderate in the middle who prefers rational discussion to confrontation.

> Why are you using legacy BIOS? It has been obsolete for a long time

It's simpler. That's sufficient reason for me.

For those of us who still prefer to use legacy BIOS on current hardware when possible, the article is not obsolete.

I suspect the downvotes were because your comment comes across as unreasonably negative.

I switched to OpenBSD on my desktop and remote server after many years of Linux use. It's now my goto OS for network connected stuff.

One caveat: A power cut during the relinking process that occurs during and after boot can wreck the filesystem. A UPS is advisable. Once the relinking finishes the filesystem is quite robust.

> HTTPS-only is about forcing all traffic to be encrypted by banning clear-text traffic

Banning clear text might work for browsers but it would disable ACME clients that rely on plain http to initiate a certificate request from Let's Encrypt.

> tripe-filled posts

I enjoyed the article and found it thought provoking. Maybe I have tripe for brains.

> Ah, the foundation trilogy. Prepper culture apocalypse fairy tales – but for academians.

It was written in the early 1950's. Did prepper culture exist then to the same extent as it does today?