maccam94

I've wanted this as my business-hours pager sound for a very long time...

People can generally only output their max power for short durations. The output level they can sustain is generally much lower. I bet you could try to model higher limits for short distances, but what those should be could vary greatly depending on personal fitness.

DNS cache poisoning?

Dang, they aren't catching the booster this time, but I guess V3 is practically a new vehicle and validating the next Starship launch is probably too critical to risk damage to the launch site for now.

In Zulip, if a thread meanders with messages about a tangent, the authors/mods can choose to move those messages to a new thread (and IIRC messages with links between the two threads are created so it's easy to jump back and forth for any missing context)

If you're laying a communications cable, you should just do fiber. It can carry any type of traffic at high data rates, and you can upgrade the speed over time by just replacing the optics at the ends rather than having to replace the whole cable. Fiber plans are only expensive if your service level is expensive, or if you have to pay to get the line run to your building

Yeah, as far as I know the only way to be sure is by putting the parent process into a cgroup. Then to kill all of the child processes you have to freeze the cgroup, enumerate the pids, send sigterm/sigkill to all of them, before unfreezing again.

very slowly, with the radio at maximum power, and no obstructions

It uses a different transceiver on the satellite which is broadcasting a ~standard LTE signal, at a miniscule data rate

The Linux kernel doesn't have a stable ABI. Thus, if a kernel function signature changes, or a subsystem gets refactored, etc, drivers get updated as part of the process. If the drivers lived outside the kernel tree, they would have to be updated separately by their own maintainers. That's less efficient and prone to breakage, so generally driver modules are merged into the kernel tree. Often they can even share code with other hardware devices!

Not sure what you mean by "userland" drivers here, but support for kernel modules written in rust is actively being developed. It's already being used for kernel drivers like the Asahi Linux GPU driver for M1 Macs.

Wait, Commonwealth Fusion Systems is already building 20T REBCO magnets, can't those meet the requirements for MRIs?

Why would you use LVM with ZFS? ZFS should handle all of the features LVM has (as far as I can think of, at least).

I would have taken a full screenshot but I had my company's Gitlab open behind it.