Seconded. Both work great.

FS permissions are the main thing, yes. One can build more systems around it (don’t mount the socket into a Flatpak container, if you don’t want the Flatpak to talk to DBus) or (implement some sort of auth protocol like TLS does).

1. Make a snapshot with LVM2 or BTRFS to ensure consistency, delete the snapshot after backing up.
2. You can back up files as root (I do) or a dedicated user that has perms to all the relevant data via groups.
3. Rsync can preserve users either numerically or by name.
4. Rsync can do incremental backups via hardlinks (you’ll have a complete view of all files in each snapshot, but only pay the storage when files actually change).

What’s an rpc port anyway? Do you mean DBus? Then FS perms of the socket. Perhaps also something in the protocol itself.

If your Windows partition is encrypted with BitLocker (which it probably ought to be, for security), and you disable Secure Boot, Windows will get angry at you.

You can set up Linux to do Secure Boot (I think I saw Fedora do it for you automatically), but it’s extra hassle.

You might be able to decrypt BitLocker in Linux: https://github.com/Aorimn/dislocker/

Tried, but it didn’t support my disk encryption, LUKS2. I intended to stick Guix in a BTRFS subvolume, but didn’t succeed.

192.168.0.00? 'Shopped.

Congrats, you’re now ready for https://en.wikipedia.org/wiki/Lojban

It didn’t, but due to unrelated reasons. The root FS was mounted r/w, so the regular IO eventually overwhelmed the network’s ability to copy stuff.

But no worries, a reboot later, with unmounted FS, I finished the same thing.

Copying the disk of a running system appears to be fine in LVM. Copying is done block-by-block, and the only thing it has to do to make it atomic is: in case of a conflict (writing into a block that’s being copied right now), postpone writing to a block until it’s copied, then finish the write in the new location. Or else, abort the copy, finish the write, then copy again.

BZ2-ing up a terabyte of zeroes (back when a TB was more than people commonly had, then zipping that file up together with another file, to bypass virus scanners in emails that prevent emailing .exe files.

I’ve also seen a self-referential .zip file somewhere that contains itself.

I use rsync with a custom shell script to manage the number of incremental copies. You’ll probably prefer something less janky.

Does your FS support online resizing? EXT4 doesn’t, so you’d have to use an installer stick.

Be super careful about partition sizes. I once tried to shrink my FS to an exact size, then shrink the LV to the same size - it ended up corrupting my FS. After that time, I started undersizing the FS, then resizing LV, finally expanding the FS again.

Have backups.

I’d recommend a Linux installer on a memory stick, instead. It’s bound to have less network lag.

I needed to redo partitions, but didn’t want to reboot.

Mounting a Samba share and moving my LVM pvolumes of / onto a losetup’ed file on it, while running the system. Bass ackwards.

Cool, thanks. Didn’t realize you can use this neat trick :)

What’s the Slackware way of managing package dependencies, then?

Declarative system configuration is the killer feature of NiOS. Atomic rollbacks too. Versioning the whole mess in Git, too.

We’re at Linux@lemmy.ml, hon. The average user uses a package manager. The majority of software is open-source and compiles for ARM just fine. Games excepted, but they won’t run on the low specs anyway.

Yep. I found I don’t have much use for a full-blown VM, whereas there’s plenty of argument for isolating my browser from ~/.ssh/id_*.