Arch has always been rock solid for me and in 10 years or so I have never had to chroot to fix an issue

For me it has usually been boot related things or when I’m doing planned deep surgery on my system. I can recall a few times that I used arch-chroot through the years:

• When the grub package was updated and generated a config file that was incompatible with the earlier grub version that was installed on my EFI partition.
• There was one time a kernel that wouldn’t boot on my hardware, so went back in to install linux-lts
• There was once a bug in netctl that caused it to hang indefinitely on boot, so I had to go in to disable the service so that I could at least boot to troubleshoot it.
• After every BIOS update of my Gigabyte motherboard, I have to re-add grub to the nvram entries by running grub-install from a chroot environment. On my ASUS system I don’t have to do this, don’t ask me why.
• When I moved my installation to a new SSD and made a typo in /etc/fstab
• When I was switching over to a LUKS encrypted root filesystem it was handy that I could boot into the installer to do a clean copy of my root filesystem and make all the grub, mkinitcpio, /etc/fstab changes via arch-chroot. It was also good to know that I could always go back in that way to make additional changes as it can be tricky to get it all right on the first try.

what’s the benefit to doing it with systemd?

You can feel more modern.

The sad part is that I can’t tell if this is a joke or not.

“Let’s go burn down the observatory, so this will never happen again”

The new one has a standby usage closer to 2,5 - 5 watts while having a lot more performance

You can’t just say that without giving the specs of your new server

I trust you on that

Aw man :(

Yeah keep telling yourself that Lennart.

Because through the years I never had problems with plain Alsa on the same hardware, and I don’t have problems with pipewire either on that hardware.

deleted by creator

deleted by creator

Americans: you guys have foreskins?

For me it was Layne Staley, Chris Cornell and Mark Lanegan. The greatest voices of their generation, and unfortunately gone much too soon.

We gave him one of our freestanding paper bag trashcans and problem solved.

Why didn’t you just show him how to flush?

What kind of 19th century style exploitation is this?

This kind of shit is why unions are needed.

Can also see security updates being extended again similar to Win7

I certainly hope so, I have a Windows 10 partition that I occasionally use for gaming. Not looking forward to dealing with Windows 11 bullshit.

As a general rule Ubuntu and Mint don’t really (*) get major package upgrades. They don’t “follow” Debian-Testing but rather fork it at some point in time, apply their modifications and then keep the package versions stable, releasing only security fixes and bug fixes, whereas Debian-Testing keeps incrementing. The process really isn’t all that different from Debian-Stable releases.

This means for example that currently Debian 12 is more up to date than the latest Ubuntu LTS release and only slightly behind Ubuntu 23.04.

(*) There are a few exceptions like the HWE kernel, but the general rule is no major upgrades. The equivalent on Debian-Stable is the backports repository.

deleted by creator

deleted by creator

sharing your home

I wouldn’t recommend that, because your home directory is not just where your files live but your user configuration as well. Arch and Ubuntu will have different versions of the same software, so you may get conflicts and compatiblity issues with the various configuration files in ~/.config, ~/.local and whatnot when you switch from one to the other. Ubuntu also comes with a default ~/.bashrc and ~/.bash_profile for example whereas Arch does not.

It would be like sharing the user registry between Windows 10 and Windows 11.