“Somebody shit in my pants.”

I bought a refurbished SFF PC and put a PCIe NIC in it. Installed opnSense.

Cheap as chips. Supremely powerful.

Nice analogy.

TYVM!

Yeah, I went and checked after posting.

My hunch is that if the moon was closer it would ‘drag’ the barycentre closer to the moon.

Which, given the moon is slowly receeding, means it was probably a binary early on in the formation of the solar system.

That’s because you’ve only named one end of the tunnel. It’s the Mouth-Butt Tunnel.

I believe the rule of thumb is binary planets’ barycentre is external to either body. This is the case with Pluto/Charon, I think it’s also the case with Earth/Moon.

February isn’t in summer.

Yeah, it is.

I still double-check my CIDR’s/netmasks and expected ranges with a tool (some online one or other). Easier to avoid silly mistakes or typo’s

TL;DR: it depends entirely on the DHCP server software.

Generally the safe/reliable policy is to assign a smaller DHCP range (or ranges) and allocate static assignments outside of the DHCP range(s).

Assume your network is 192.168.1.0/24.

Specify 192.168.1.128/25 for DHCP, which means all DHCP addresses will be above 192.168.1.128.

This leaves you everything below 192.168.1.127 for static assignments.

But then they can’t force you to watch claim that you watched the ad at the start of the video for that sweet advertiser revenue.

There’s also a draw.io (diagrams.net) plugin for intellij and probably eclipse.

I’ve used coreos happily on homelab bare metal.

PXE booting it with cloudinit/ignition automation for provisioning.

It’s make for an excellent VPS.

Those “select tiles with a bicycle” are us training image recognition programs.

Intel’s way ahead of you.

They do!

See their Era, Mood, Ridge, Terra cases.

But the OS crashing as a result of that systemic failure may actually be the most reasonable desirable outcome compared to any other possible outcome.

In which case this should’ve been documented behaviour and probably configurable.

Hmmmm.

More like standing there and loudly shitting your pants and spreading it around the stage.

Except “freak out” could have various manifestations.

In this case it was “burn down the venue”.

It should have been “I’m sorry, there’s been an issue, let’s move on to the next speaker”

Poorly written code can’t.

In this case:

1. Load config data
2. If data is valid:
   1. Use config data
3. If data is invalid:
   1. Crash entire OS

Is just poor code.

Having the data exposed to userspace via an API would avoid having to have a kernel module at all… Which when malformed wouldn’t compromise the kernel.