This is madness, but since this is a hobby project and not a production server, there is a way:

• Shrink the filesystems on the existing disks to free up as much space as possible, and shrink their partitions.
• Add a new partition to each of the three disks, and make a RAID5 volume from those partitions.
• Move as many files as possible to the new RAID5 volume to free up space in the old filesystems.
• Shrink the old filesystems/partitions again.
• Expand each RAID component partition one at a time by removing it from the array, resizing it into the empty space, and re-adding it to the array, giving plenty of time for the array to rebuild.
• Move files, shrink the old partitions, and expand the new array partitions as many times as needed until all the files are moved.

This could take several days to accomplish, because of the RAID5 rebuild times. The less free space, the more iterations and the longer it will take.

If you can assign a second IP address to the network interface, then just do so, and bind the docker container to one, and Adguard Home to the other. Otherwise, the reverse proxy based on the server name is the way.

This just sounds like a bad idea, a solution in search of a problem. Sure, sudo is a setuid binary, but it’s a fairly simple program, and at some point, you have to trust the code. It’s also a very fundamental piece of the system that you want to always work, even (especially!) when other things get borked. The brief description of run0 already has too many potential points of failure.

100%

Nah, Linux is confusing because it’s software. I have a well-paying job in large part because Windows and macOS are confusing as hell, too.

It always had those dependencies, they’re part of the base desktop system. It’s just that the Chromium package from the unstable branch depends on packages from the unstable branch. The unstable versions got updated so they are no longer the same as the stable packages, and apt has to uninstall the stable versions of them to install the new unstable versions.

According to the ConnectBot issue tracker, it’s not possible to retrieve the private key that it created. You’ll have to make a new key pair, and share the new public key with tildes. The keys are randomly-generated, so the new pair will be different, regardless of whether you use the same password.

Careful, too many packages on one drive becomes unstable, and may collapse into a singularly— technological, astrophysical, or worse, both!

Seriously, though, it’s fine. The trend these days is to isolate network services/apps, each in its own virtual server/container, for security reasons. If that service gets breached by hackers, or the configuration breaks, no other services are affected. A lot of installs, each with only the minimum packages for one service, is bound to bring down the average package count.

A user workstation is bound to have many more packages installed. Install what you need and prosper.

Gotcha. As usual with Linux, there are lots of ways to crack the nut. I would be inclined to go with the built-in option, in this case. Less likely to break.

That’s odd. It does not lock the local user out on Ubuntu, and allows simultaneous use.

I believe that Linux Mint supports RDP, built in. You just enable it in the System Settings. Is that not workable?

I’m not the only one! It doesn’t work with my sound bar, and the developers think that editing 3 (!) obscure config files is an acceptable workaround.

Hey, all you folks ought to get together and publish a guide to writing good FOSS documentation,

There’s a lot of love for it here, so I guess my experience isn’t typical. I updated to Ubuntu Lunar Lobster on my home media machine, which comes with PipeWire by default, and it’s utter shit. The vocals and some instruments in my music tracks only play nearly inaudibly from the center channel of my 5.1 surround system. It’s unlistenable, even with the center volume boosted.

Seriously, what am I missing? How can it do audio that poorly?