My theory for why it created copies: The files you listed look like they are all subdirectories from /dev, which is (usually) a separate filesystem. When you try to move a file or directory across filesystems, the OS can’t just change the link, it has to actually copy the files and then remove the original. As a directory is a set of links to files, and the copies are different files, directories are just newly created with the same name in the new location instead of copying the directory filesystem entry. It looks like mv creates these target directories, before it checks if it actually has permission to remove the source, but checks file permissions, before it copies them

Regarding snapshots, I use a setup, where at the root of the btrfs partition I have the subvolumes “rootfs”, “home”, and a directory “snapshots”. I can boot into a snapshot by changing the mount options for the rootfs in the kernel command line, e.g.setting subvol=snapshots/rootfs-yyyy-mm-dd.

The only difference between a snapshot and a regular subvolume is that snapshots are readonly by default, you can keep a writable copy of a snapshot beside it for recovery purposes, if you need it. As long as nothing is written in it, it shouldn’t use any significant extra space.

I know that, but that does not give apps root access. Unless you mean something else by root access than being run with root privileges

But Shift+insert currently pastes the primary selection, not the copy-paste clipboard. So it doesn’t do the same as Ctrl+V.

Well, the article proposes to use dedicated copy and paste keys. If you don’t have an insert key, you probably don’t have those either.

And best of all, you get an OS that is secure, which traditional Linux distros aren’t due to every app having root access by default.

What? Which distro runs everything as root by default?

Try eject /dev/sr0, that should be your disk drive if it is attached via SATA or USB. /dev/cdrom is usually just a symlink.

but had the genes

I’d say that falls under “birth lottery” as much as wealth inheritance.

on my gaming PC, it never used the GPU.

In my experience, that is usually a problem with the GPU OpenCL drivers. Sadly, the Mesa OpenCL implementation didn’t include image support when I last checked (you can check with clinfo | grep "Image support"). For AMD cards you need to have either the “pro” driver or ROCM installed, both aren’t packaged by all distros. Similar with Intel, don’t know about Nvidia, but I’m sure if it works, it’s only with the proprietary driver.

I ended up installing darktable in an arch distrobox container, as arch has ROCM packages (in AUR) and ever since GPU acceleration is working fine.

This is mostly what I use too. Additionally, on images with high ISO I usually add the profiled denoise module, often without changing the default values. If the image has a lot of noise, I sometimes use the preset that only reduces chroma noise (so the image stays grainy, but without the color mismatches)

I don’t think working overtime has much to do with WFH vs office for most people. We have a lot more WFH here since covid, and the only people I know that work a lot of overtime already did that before WFH was introduced.

For me, WFH means an hour more of free time, as I don’t have to spend it in traffic on my way from and to work.

…and all I hear is: “this stuff isn’t ready yet” and “I’m going to be starring at Unicode glyphs the next time I have to tinker outside of my GUI”.

This really isn’t a zsh problem, but a “people putting too much stuff in a ‘getting started’ config”.

I used zsh for 15 years before looking at any plug-in manager, you can get a lot of the good stuff like the completion by just going through the first-run wizard included in zsh. A lot of stuff is included directly with zsh, including various prompt themes (which is what that tutorial wants extra fonts for, because they use a fancy prompt with custom glyphs; I don’t think any of the built-in ones need that)

Things like fuzzy history search with fzf is usually included with fzf’s distro package and the additional zsh-completions package for less used or newer commands is also packaged by most distros. In my experience, a lot of the other plugins are stuff that could be a standalone script instead of a plug-in anyway.