• 0 Posts
  • 34 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • There’s a reason you have a home dir. Just copy that forward along with whatever other config files you might’ve customized.

    This is probably the reason why most distros will have the home directory on a separate partition. To easily allow you to keep your most important data when reinstalling or switching to a new distro.








  • Do you have heroic installed through Flatpak? If you do then install flatseal (through Flatpak) and use flatseal to enable permissions for heroic launcher. It should be pretty obvious how to do this once you have flatseal open.

    By default Flatpak does not allow applications to write to directories outside of your home fir (and I think it also blocks access to other partitions).

    Source: I did this on my system last Friday to install return to moria. Also I got zzz to work on my steamdeck out of the box with heroic game launcher.


  • This is true. And it’s also why I always recommend downloading steam through their website. They distribute their own Deb directly, and it auto updates.

    Flatpak version is also okay but if you want to use a secondary disk then you need to know how to use portals (or the Flatpak configuration tool that I can’t remember the name of).






  • This might help in the future in case you setup a remote mount for backups in the future. Look into using systemd’s automount feature. If the mount suddenly fails then it will instead create an unwritable directory in its place. This prevents your rsync from erroneously writing data to your root partition instead.




  • ArchrtoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    2
    ·
    11 months ago

    I also like lutris. But it being “for games” doesn’t do it justice I think. It is basically just a wine environment manager. It advertises as being for games but it should work with just about any windows executable.


  • I did something similar (that my professor still talks about in class as a cautionary tale)

    I ran chown -R user .* (intending to target all hidden files in the folder) and for people that don’t know .* also matches .. (.. was / in this case) which changed the permissions on all files on the system to that user, including sudo.

    We fixed it by mounting the root of the file system in a docker container which effectively gave us root.