• 0 Posts
  • 172 Comments
Joined 2 年前
cake
Cake day: 2024年2月4日

help-circle

    1. Linux is intentionally made to be modular and using the terminal is pretty much the only standard way to do things across many distributions.

    I highly suggest you stop avoiding it because it will most likely be faster and easier to do something (i.e. system-level changes) with it than not.

    1. If you want a hard-to-fuck-up distro, I think Atomic (at least that’s what Fedora calls them) distros are the best.

    Similar to smartphones or MacOS, entire OS is a singular image that is also updated all at once. Core parts of the filesystem is also read-only, meaning it is pretty much impossible to mess things up if you don’t mean to do so deliberately.

    The best in this regard are from uBlue project: Bazzite (most popular), Bluefin, Aurora, etc. While Bazzite is intended for gaming (things like Steam are pre-installed), the other are for general use. Bluefin uses GNOME desktop, while Aurora has KDE Plasma desktop environment. Look up their visuals and choose whichever one you like. I prefer Aurora because KDE Plasma is often much more familiar to Windows users.

    1. uBlue distros don’t require a password for system updates (they happen automatically in the background) and so do installing/updating programs.




  • pogodem0n@lemmy.worldtoLinux@lemmy.mlInstall Issue
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    3 天前

    First, you should learn about Wine prefixes. Arch Wiki has a good write-up about it.

    After the game is installed, you need to edit that setup.exe you added as a non-Steam game and point it to the game’s actual executable.

    Steam’s Wine prefixes are usually located in ~/.local/share/Steam/steamapps/compatdata. This directory should have some text config files that you can read to find out what ID Steam has assigned to it.

    Also, you might have more luck with Bottles (available through flatpak) which is more suited for such tasks.















  • Unfortunately, no. My assertion came from sheer popularity of their GitHub repositories and personal observation among my tech-savvy friend groups.

    You can start checking out their code yourself, though. There are a lot of open-source software out there and it would be unfeasible for anyone to audit their code themselves. At some point, you’ll have to put some trust into others. Be it software audit companies, or the Signal developers.