I currently use Windows 10 and I’d like to try out Linux. My plan is to set up a dual boot with OpenSUSE tumbleweed and KDE Plasma. I’ve read so many different opinions about choosing a distro, compatibility with gaming and Nvidia drivers, and personal issues with the ethos of different companies like Canonical. I value privacy and I’d rather avoid a Linux distro that’s implementing something like ads or telemetry…if that’s even a thing that’s happening?

As a complete beginner, what sort of advice would you all have for me? Should I avoid OpenSUSE or KDE Plasma for some reason? Are there any ‘10 things to do first when installing Linux for the first time’ recommendations?

Despite all the ‘beginner friendly’ guides and tutorials around, I still feel a little lost and like I’m going into this blind.

EDIT: Thanks to everyone who’s offered advice, I really appreciate all the help and the patience with my dumb questions! There’s a lot to look through and it’s been a busy day for me, but I’ll get back to reading through everything and replying as soon as I can!

  • @[email protected]
    8•1 year ago

    Yeah - the home directory in Linux pre-dates the windows Users directory by a long time. You’ll see the multi-user nature of your OS exposed much more in Linux than you will in Windows.

    Every user will have a /home/username directory on Linux (often referenced by “~” or by the environment variable “$HOME”). By default this is the only directory that user will have any permissions to create things (with some exceptions like /tmp which is used for temporary file creation - but nothing long-term). So all of your configuration, user-created files, etc. will be created there.

    Configurations are often stored in ‘dot-files’ or in directories that begin with a period. These are “hidden” by default with most file-browsing tools (it’s just a tradition - there’s nothing otherwise special about files or directories that begin with a period). So you’ll have a .bashrc which is the script that runs when you start a bash shell for example. Or .local which is where you will find a lot of application configurations these days.

    So if you copy /home/username somewhere you will copy all of your configurations.

    Some applications will install there as well. Steam, for example, will install your programs under $HOME/.steam.

    Things you install “system-wide” will be installed to /usr/bin or /bin. This will typically be things that you use a package manager to install. So the steam application may be /usr/bin/steam but then all of its configurations, installed apps, etc. go in your home dir.

    If you’re curious where a command lives you can use which cmd or type cmd from the command-line and it will show you (something I often wish Windows had).

    NOTE: There are exceptions to everything I’ve said above. But those are the “general” guidelines. In short - if you installed it without needing root permissions it’s likely somewhere in $HOME.

    • @[email protected]OP
      1•1 year ago

      Thanks, that’s a lot of really helpful info.

      What do you mean by this though?

      If you’re curious where a command lives you can use which cmd or type cmd from the command-line and it will show you (something I often wish Windows had).

      A command can ‘live’ in different places? And this might be a dumb question…but what is a command in this context?

      • @[email protected]M
        3•1 year ago

        This is the actually the thing same as Windows - in Linux you’ve got the which command, and it’s equivalent is where in Windows. Both do the same thing - find out where a program lives.

        OP meant a “program” in this context. Both Linux and Windows have specific paths where programs typically lives. For example, in Windows, if you type “notepad” in a command prompt or the ‘Run’ dialog, it’ll search for it in known system paths such as C:\Windows, C:\Windows\system32 etc. These paths are declared in the PATH environment variable - which you may have encountered when certain applications try to (or ask you to) add their program folder to the PATH, such as say Java or Python. If a program is added to the PATH, typing ‘java’ or ‘python’ from anywhere will automatically launch it, so you don’t need to specify the full path or the program.

        Now whilst this is convenient, sometimes it can cause unwanted issues. For example, say you installed some other program that uses a specific version of Java or Python, and it installed that version in your system, and added that folder to the PATH - now when you type java or python in a command prompt, you wouldn’t know which version you’re executing. This is what OP meant by a program living in multiple places. As you can imagine, this can now cause issues, and can even break some scripts expecting a particular version of Java/Python etc and some other version is being picked up. This is where the where command in Windows comes in handy, as it tells you where exactly that program is located. And it’s Linux equivalent is which.

        So at least in this department, the behavior of Windows and Linux is virtually identical. :)