• 0 Posts
  • 222 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle
  • I forget the exact terminology but I tried putting it into the most permissive mode available. Is still could not work with external hard drives. This was several years ago so I can’t say what might have changed since then, but I did spend some time troubleshooting and at the time that functionality did not work. I’d read that it was possible in the previous version (maybe 18.04?)

    Edit: Come to think of it, it might not have been as simple as “couldn’t access external drives”. It might have had something to do with how my disks were mounted and their permissions and mount points. I remember that I hit a wall at some point and further troubleshooting would have required more surgery on my system than I was willing to attempt.


  • GenderNeutralBro@lemmy.sdf.orgtoLinux@lemmy.mlThe Dislike to Ubuntu
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    1
    ·
    3 days ago

    Yeah, this kind of things drove me batty on Ubuntu. So many things were delivered as Snaps when they just don’t work that way. The funniest one to me was Filebot. It’s a media file naming/organizing tool…that doesn’t have disk access. Are you kidding me, Canonical?

    Flatpak is easier to work with, but has similar issues. Great for simple things, but I’m always worried that at some point I’m going to need some features that just won’t work, and then it’s going to be a hassle to migrate to a native installation. And it has no CLI support.

    And yeah, the bloat is wild. Deduplication on btrfs (or similar) helps but there’s no getting past the bandwidth bloat.











  • Probably ~15TB through file-level syncing tools (rsync or similar; I forget exactly what I used), just copying up my internal RAID array to an external HDD. I’ve done this a few times, either for backup purposes or to prepare to reformat my array. I originally used ZFS on the array, but converted it to something with built-in kernel support a while back because it got troublesome when switching distros. Might switch it to bcachefs at some point.

    With dd specifically, maybe 1TB? I’ve used it to temporarily back up my boot drive on occasion, on the assumption that restoring my entire system that way would be simpler in case whatever I was planning blew up in my face. Fortunately never needed to restore it that way.





  • YES.

    And not just the cloud, but internet connectivity and automatic updates on local machines, too. There are basically a hundred “arbitrary code execution” mechanisms built into every production machine.

    If it doesn’t truly need to be online, it probably shouldn’t be. Figure out another way to install security patches. If it’s offline, you won’t need to worry about them half as much anyway.




  • Ah, that makes sense! I probably should have split my /home off to its own subvolume. I’ll add that my list of things to think about next time I hop distros or rebuild (which I’m considering once again, because I have Plasma envy).

    And yes, snapshots should NOT be treated as backups. A real backup saves your butt if your drive dies, while a snapshot goes down with that ship. I should really set up a better backup system, but for now I just periodically use Borg to back up to an external HD, and then copy that into an encrypted cloud drive.


  • I love btrfs+snapper. I have automatic snapshots taken before and after every apt install, so if anything ever goes belly-up, no problem, I just roll back.

    It’s a little weird sometimes when I’m running out of disk space, so I delete some big downloads and…I get no disk space back, because those files still exist in old snapshots! I suspect there’s some way to finetune it to ignore certain directories (like ~/Downloads) in snapshots but I haven’t taken the time to dig into it. Anyway, it’s not a huge problem because the automatic snapshots are limited to a certain number, so they eventually get bumped out (or I can delete them manually if needed).

    I haven’t tried bcachefs yet. Perhaps on my next build.