

Sometimes. And if they’re not, they’ll be replaced or replace themselves.
My point wasn’t that there’s a reason (though, obviously there is), but specifically that their “stable” names can still change easily. So it’s not even that useful
Totally…
The predictable network interface names can change after adding or removing a PCIe device if the system firmware decides to renumber the devices. See systemd issue 33347.
btw
Lesson 1 to 21 from Google: Fascism means profit. Therefore, it’s good.
In other news: 1 + 1 = 2.
I’ve seen a lot of sharks, but that’s a new one to me…


Old small desktop towers. Powerful, very open (so I can run my NS infra and WG server and bridge on there, and easily have them redundant), and very extendable (need a 10G NIC or SFP+? Plug in a PCIe card!), and easily replaceable. I now have some old Cisco APs, which will be for my 2nd Home, so I can use my FritzBox as only a modem. In my 1st Home, I’ll hopefully soon actually have fibre in addition to using my dads FritzBox as uplink. And I could add a Mobile Modem too. There, I don’t need a wireless network, as in contrast to my 2nd Home, that infra is only for servers, to which I can just connect from my dads network/FB.


Home 1’s Routers, Home 2’s Router, public IPv4/v6 VPS. All as the native arch package.


You mean, you’d make Dennis actually implement a string type.
“A toy? A Lego set??”, she asked excitedly, and wagged her tail.
“What God is made of”
“Deleted by (the) creator”
as Google’s L1 Cache
Idiot does not know what a cache is.


Rust:
fn getofmylawn(lawn: Lawn) -> bool {
lawn.remove()
}
C:
bool getofmylawn(Lawn lawn) {
return lawn.remove();
}
With Rust you safe 1 char, and gain needing to skip a whole line to see what type something is.
No, the first step begins before, as the revenue must be as high as possible before the IPO. That’s what happened with Fuckit too.