There are definitely situations where you can't ask for help and you can't turn your back on the bug.
I worked on a project that depended on an open source but deprecated/unmaintained Linux kernel module that we used for customers running RHEL[1]. There were a number of serious bugs causing panics that we encountered, but only for certain customers with high VFS workloads. I spent days to a week+ on each one, reading kernel code, writing userland utilities to repro the problem, and finally committing fixes to the module. I was the only one on the team up to the task.
We couldn't tell the customers to upgrade, we couldn't write an alternative module in a reasonable timeframe, and they paid us a lot of money, so I did what I had to do.
I'm sure there are lots of other examples like this out there.
[1] Known for its use of ancient kernels with 10000 patches hand-picked by Red Hat. At least at the time (5-10 years ago).
I heard about them a few times before finally deciding to listen to an album. I can't remember if it was Reddit or Instagram. In each case they were just mentioned offhand in a comment, like I should already know about them.
Ultimately, I kind of hate the guy's voice. Sort of reminds me of... Parquet Courts? Who I don't really love, either.
I think it's partly because "sit" is one of the first commands they learn so if they're not sure what to do, they'll default to sit as that often gets the treat.
That's also why you teach "sit" first before, "bite the face of the person in front of me" (talking German Shepherds again)
In this case it's more like it's replacing management or executives. There is still a person, with an ownership stake, putting up the capital, and taking the profits (if any).
Except it doesn't work with links, which is usually how I find news stories. I have Apple One (which includes News), but If I click on a link to the WSJ, I get the paywall. To read the article, I have to copy the article title or headline (if I can find it!), and paste it into the News app to read it.
> The ACE 1000 also had a built-in power supply and 64k of RAM while Apple’s machine did not.
The Apple II series (except for the later //c) all had quality switching power supplies built-in. That was already something Apple was doing to set it apart from Commodore, Atari and Tandy.
Does anyone know how the blocking functionality works? I worked on some eBPF code a few years ago (when BTF/CO-RE was new), and while it was powerful, you couldn't just write to memory, or make function calls in the kernel.
Is there a userland component that's using something like iptables? (Can iptables block traffic originating from/destined to a specific process nowadays?)
eBPF is extended in every kernel version. There is a layer where you get network packets and return a verdict. Little Snitch uses this type of eBPF function. You can look at the sources on Github.
I worked on a project that depended on an open source but deprecated/unmaintained Linux kernel module that we used for customers running RHEL[1]. There were a number of serious bugs causing panics that we encountered, but only for certain customers with high VFS workloads. I spent days to a week+ on each one, reading kernel code, writing userland utilities to repro the problem, and finally committing fixes to the module. I was the only one on the team up to the task.
We couldn't tell the customers to upgrade, we couldn't write an alternative module in a reasonable timeframe, and they paid us a lot of money, so I did what I had to do.
I'm sure there are lots of other examples like this out there.
[1] Known for its use of ancient kernels with 10000 patches hand-picked by Red Hat. At least at the time (5-10 years ago).
reply