How’d you set that up with Opnsense fail over? I have an opnsense VM with input straight from the ISPs FTTP box to the NIC on my server. So I can’t fail over to my second proxmox box without swapping the cable over.

I built my website with

fortune, cowsay, toilet, lolcat and aha

Run your own DNS server on your network, such as Unbound or pihole. Setup the overrides so that domain.example.lan resolves to a local IP. Set your upstream DNS to something like 1.1.1.1 to resolve everything else. Set your DHCP to give out the IP of the DNS server so clients will use it

You don’t need to add block lists if you don’t want.

You can also run a reverse proxy on your lan and configure your DNS so that service1.example.lan and service2.example.lan both point to the same IP. The reverse proxy then redirects the request based on the requested domain name, whether that’s on a separate server or on the same server on a different port.

I imagine they use it in much the same way as any enterprise. Running servers and workstations, mostly.

F16’s run Kubenetes clusters.

Lots of individual bits of hardware on specialized devices will be running embedded operating systems. QNX is big in automotive for the same reasons it’d work on a rocket.

As someone who worked on a pre-systemd linux system with multiple NICs and needed them all configured automatically from an OS image based on where it was in the rack, I can’t stress enough how good deterministic interface names are.

Booting up a system and each time having different names for each NIC was a nightmare.

Frankly 90+% of what systemd has done is tremendously positive and makes linux a better operating system to use, both for sys admins and end users.

I don’t understand it either. On one hand people say don’t remember addresses, use DNS and on the other DNS relies on static addresses but then every device is “supposed” to have random addresses via SLAAC or privacy addresses. It just doesn’t seem to tie together very well, but if you use them like IPv4 addresses you’re apparently doing it wrong.

RAID IS NOT BACKUP RAID IS NOT BACKUP RAID IS NOT BACKUP

Don’t use Red drives for a NAS!! You need the Red Plus (or is it red pro) disks as they’re CMR.

I’d go for Ultrastar drives personally. There’s a few really good videos online analyzing the backblaze stats for different drives that are well worth watching.

EndeavourOS on my desktop and laptop. Works like a charm. By far the happiest I’ve been with a desktop distro.

On my server VMs I’m running Ubuntu Pro because it’s absolutely impeccably stable, Pro is free and I like the idea of having the option of not upgrading them for 10 years.

All running on Proxmox. I have a few appliance type VMs like opnsense and 3CX and they’re nice and stable too.

Or save yourself a character and just yay

I received so much spam and abuse of my network from .xyz domains that they are fully blocked in every conceivable way from being accessed or accessing my network.

A few people need to get off their horses and come up with and agree to IPv4². It’s exactly the same as IPv4 except there’s 2 more octets of address space - 48bits for addresses*. Job done. You’d see wide spread adoption in under 2 years and then we can forget about it all and move on with our lives safe from the clutches of IPv6.

I don’t give a crap that doesn’t neatly fit into 32 or 64 bit architectures. It’s more than doable at plenty fast speed and it keeps everything manageable.

Just because a DE looks sparse doesn’t means it also uses less resources. In imagine KDE would actually run well as it doesn’t need all the bells it offers and is actually a well written performant DE.

Pretty sure my Seagate usb disks I use for backup are SMR and sustained writes are awfully slow. Luckily I’ve discovered restic for backing up which lowered a 1.5tb weekly incremental backup from 9hrs to 1 min.

Same as any OS, yes

It doesn’t tell you up front that it’s going to break

Should you trust something that failed verification? No. That’s the whole point. It’s not what you think it is.

I highly recommend watching this guys videos on his analysis of the backblaze data https://www.youtube.com/watch?v=IgJ6YolLxYE&t=1

And a comparison of the difference WD drive colours, which might not be what you expect https://www.youtube.com/watch?v=QDyqNry_mDo&t=2

Go get help

“It’s never lost data for me. Yet” is what they mean.

I totally agree, the only file system I’ve lost data with as a result of a file system corruption not caused by hardware errors or power problems in 35 years has been btrfs. FAT even served me better.