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?
Linux has had real-time threads (round-robin and, more recently, deadline scheduling) and kernel preemption for a _long_ time. But the kernel isn't fully preemptible all the time, and latencies are not strictly bounded in all such situations (e.g. if you are trying to grab a contested spinlock). PREEMPT_RT is the final icing on the cake, and as far as I know, it makes Linux the first general-purpose OS that has full realtime guarantees.
But I haven't been able to figure out anything that would indicate FreeBSD is better (or is better than what Linux was in 2016). The information is sparse, but it seems to me that it has a scheduler with _some_ support for realtime threads (when the timeslice is up, RT threads take priority in the scheduling algorithm), but not really preemption of non-RT threads by RT threads (ie., when a RT thread is ready to wake up, non-RT threads get kicked out even if the timeslice isn't up), and I cannot find anything at all about the kernel being preemptable by userspace threads, RT or not.
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.
> 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?
>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.
I blocked their entire IP range from my network. Cloudflare WAF shows the amount of nonsense coming from their network. Bots and a lot of hits in the fail2ban logs.
I don't think moderates favor rational discussion so much as they disdain conflict.
In my experience, a moderate is a conservative in all things that effect them, and a liberal for anything else.
Most moderates I know revile anything that might effect change, until it effects change. And once the change is implemented, they bristle at anything that might change that.
No political block gets to claim the province of rationality in a world where political disputes are as much about values as they are about coherent policies.
There’s research showing (at least in the US) that the “archetype” moderate, who believes all things in moderation, is basically nonexistent. Moderates instead are made up of people who have perhaps a few “moderate” views, but mostly have a roughly even mixture of left-wing and right-wing views, with no particular combinations being particularly common.
A hypothetical moderate might believe all of the following:
* Gay marriage should be illegal
* Abortion should be legal
* Firearm rights are important
* Taxes on large businesses and wealthy people should be much higher
* NATO should be scrapped
* The USA should bomb Iran and Syria
* Free markets are good
* Free trade is bad
This person has too many strong and politically diverse viewpoints to consistently back either major US party, and ends up voting based on whichever candidate most effectively signals alignment with the small number of policies the “moderate” voter currently feels most strongly committed to.
It’s easy for someone to come across as a “moderate” if they have a different primary motive for policy preference. A devout catholic might believe that both abortion and firearm ownership should be strictly forbidden, which is hard to fit into either party platform. Someone with a commitment to individual liberty might support gay marriage, unrestricted abortion access, drug legalization, free markets, free trade, and low taxes; very hard to reconcile with a party platform.
Moderate center prefers status quo and dislikes confrontation. But, it does not actually prefer rational discussion, rational discussion only sometimes favors statis quo.
Which is why center is loosing alot. Except in presidential elections, IMO both Biden and Obama are center by any reasonable definition. Even Clintons were center, but she lost, so.
This has very much become the case, and what a wide centre it has become - I’d have said I was left wing until the poles pushed so far apart I fell into the central void.
Yeah, that's potentially compelling; if you've got UEFI enabled boards for those platforms. A quick search says maybe raspberry pi 4 supports uefi booting, which would be interesting.
I don't believe there are any POWER machines using UEFI. The standard POWER boot process uses OPAL (Open Power Abstraction Layer) instead. But POWER does use GPT disk partitioning, which is from the UEFI standard.
Someone has ported TianoCore to powerNV, but I've never looked into it. You could replace the hostboot payload with any binary, it's basically just an ELF file with a payload delivered, an initramfs in the case of skiboot/petitboot.
Not a lot of advantages in UEFI over petitboot, though.
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.
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?