They do. By default the system partition is straight up mounted read-only.

Is that… ICQ? Why?

systemctl disable systemd-critic.service

Systemd-init, the core part of systemd, offersa wide range of features surpassing other init systems. More features lead to more bugs and security vulnerabilities.

This is a bad take. Many of systemd’s features improve security significantly. And having all that code in one cohesive place can’t possibly be inherently less secure than the cornucopia of init scripts we used to use.

They do. Even back in their pre-UEFI days, it was possible to flash BIOS from a properly-formatted USB drive by holding down a magic key combination at power on. But it was not exactly publicized as a supported method.

https://electronics.stackexchange.com/questions/42623/what-is-it-that-strips-vocals-from-audio-when-a-1-8-audio-jack-is-partially-unp

deleted by creator

Bitcoin is deflationary. There is a hard limit on the total number of bitcoins that will ever exist. Every so often, the reward for mining a block is halved. Eventually there will be effectively zero reward for mining at all.

That might have been true a decade ago. But GPUs and FPGAs have long been obsolete for mining Bitcoin.

Mining is happening on custom silicon in large-scale operations. They specifically observed several of those large-scale operations in multiple nations and extrapolated out. I don’t see how that methodology is flawed.

I asked DALLE-2 for a “wide shot of a delivery driver in a Louisiana bayou with bagged food” and it gave me this:

That’s certainly a fascinating way to interpret “bagged food.”

If you’re going to run fiber cables, run two or three. At least two.

You don’t want to do that twice if you don’t have to. And if you need to troubleshoot your layer 1 at some point in the future, it’s a lot less frustrating to have a good spare versus having to run more later just for testing.

I would go with 2 in aggregate (if you have the ports) + 1 spare.

But yes, fiber would definitely be a better option if you have enough clearance to run it without kinking it. Might even be cheaper depending on the cost of copper these days. The real cost is usually in the SFP+ modules.

Definitely do some research on the switches that you have before you buy the modules and cabling. Certain modules can be finicky with certain switches.

Do you have room to keep one quiet switch in the existing closet? Maybe mounted to the ceiling?

Can you run 4 uplink cables from the closet to the basement?

Fanless managed switches with 4x 10G uplink ports and at least 16x 1G access ports are reasonably cheap (minutes transceivers, of course). For example:

https://www.fs.com/products/134655.html?attribute=8032&id=289447

If you can fit the cost into your budget, use CAT8 for your uplinks. That way if you ever do decide to upgrade your access network to 10G, you can bump your 4x uplink up to 25G without having to rewire.

Not that you’ll probably ever need that much bandwidth in a house in the next decade or two.

It can be a big issue. The newest release offers some improvements.

https://devblogs.microsoft.com/commandline/windows-subsystem-for-linux-september-2023-update/

Oh and the aqueducts!

The ones we’re investing tons of money to replace to remove the lead?

You basically just made the case for exactly why.

Programs should be using the system resolver, not parsing that file.

The system resolver should have predictable behavior. But if other programs are doing their own DNS resolution (or otherwise predicating their functionality) based directly on the contents of resolv.conf then their behavior will not always be consistent with the system resolver (or with how the sysadmin intended things to function).

And that can break things in subtle, unpredictable ways, which is always a headache.

Thus, on some modern systems, resolv.conf simply declares the local systemd-resolved instance (i.e. 127.0.0.1) and nothing else.

A single global resolv.conf file also will not let you configure different behavior based on interface or on network namespace. Want to ensure DNS lookups for specific apps occur only through your VPN-specific DNS servers but all other apps only use the normal system resolvers (i.e. no leaking from either side of the divide)? Want to also ensure DNS lookups for those specific apps fail when the VPN is down (again, as opposed to leaking)? systemd-resolved has your back.

And before anyone asks, yes, I am aware there are other, more crude and convoluted ways to do that with e.g. iptables (just like you can use crude, inconsistent init.d spaghetti scripts to manage services). It’s just one single real-world example.

A single global resolv.conf file also will not let you configure different behavior based on interface or on network namespace.

The point is to configure everything using consistent, predictable configuration files and syntax, and to ensure consistent, predictable behavior.

But if you ultimately still want resolv.conf.d back, then your distro of choice undoubtedly provides a way to do so.

Cloud-init is fairly well documented:

https://cloudinit.readthedocs.io/en/latest/reference/network-config-format-v2.html#nameservers-mapping

But if you do not need it (and if you’re configuring DNS by hand, it doesn’t sound like you do), you can disable it entirely:

https://cloudinit.readthedocs.io/en/latest/howto/disable_cloud_init.html

resolv.conf itself should be managed by systemd-resolved on any modern Ubuntu Server release. And that service will use the DNS settings provided by netplan.

With cloud-init disabled, you should have the freedom to create/edit configuration files in /etc/netplan and apply changes with netplan apply.

That’s more of Brother doing things correctly. Mine automatically shows up on all my Windows systems too.

Nobody:

OP: “Please do the needful.”

They don’t sell data. They sell ads. Selling data would directly erode their ability to sell ads.