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!
My big question would be why are you starting with a dual boot? I would recommend trying each one with a liveUSB or in a virtual machine and simply do a single boot with the one you like better. There’s likely little need for you to actually maintain two distros unless you have a very niche use case that one distro can’t solve.
My advice would be to just relax and realize that the underlying OS is 90% the same regardless of what distro you choose. All the discussion you see on different distros, package managers, snaps, wayland, etc. are all the other 10%. It really doesn’t matter what distro you start on as long as it’s a general purpose distro (both of the ones in your OP are): once you learn the first 90% of linux, you’ll develop your own tastes, and then you’ll be able to decide on the remaining 10%.
I think he wants to dual boot tumbleweed and windows, not two linux distros.
That’s an even worse idea imo. If you’re not very familiar with bcd and grub you will find it hard to boot into Linux once windows decides to “fix the boot issue”.
Better to have a separate drive so you can select by picking boot device on startup.
I know it’s possible to dual boot, but it will be some issues at some point
This is the sensible thing to do. Try a bunch of distros using either USB or as Virtual Machines.
It’ll save you a lot of heartache when you eventually kill the bootloader, the display driver or both (and you will, it is part or the learning process).
I don’t understand the issue here. Does that mean I can kill my BIOS bootloader somehow? Or the display driver? And how would screwing up drivers on one SSD with Linux affect my other SSD with Windows? Sorry if these are dumb questions, I’m just trying to get my head around as much of this as I can.
Windows likes to pretend it’s the only OS in the world so it can overwrite the bootloader and you lose access to the Linux install.
But if you use separate disks for each there’s a simple solution if your BIOS has a quick boot selection: install each bootloader on its respective disk and use the BIOS selector at boot.
Alternatively, install the Linux bootloader on the Linux disk; it will autodetect Windows and offer it as a boot option, but Windows won’t be aware of Linux. In BIOS you set Linux as permanent boot disk in this case.
I want to maintain my Windows 10 install for now as a sort of fallback. I have a lot of random software installed for my university classes, and I don’t know about all the compatibility issues I might face with those. And letting it sit there in the background in case I need it for something feels safer than jumping head first into a new OS.
Trying out liveUSB or VM stuff seemed like it would be an extra hurdle in transitioning to Linux. Like, I want to get settled in and actually use it as a daily thing, not just browse the internet a bit here and there. If I don’t like the distro I choose, I can always just install another one, right?
You can indeed always install another distro. You can also run many distros in “live cd” mode, just boot from the install media and choose the live option without installing. It’s actually a great way to see if a distro will play nice with your hardware and LAN and peripherals out of the box.
Oh, my misunderstanding, I thought you wanted to dual boot OpenSuse and KDE Plasma. Dual booting Windows 10 and one of those makes way more sense, especially if you have niche university software that was probably written 20 years ago for Windows XP service pack 2, is already barely compatible with Windows 10, and almost certainly never had a linux version. You definitely don’t want to gamble on abandoning Windows completely until after you graduate.
And yes, once you get comfortable installing a distro, it gets pretty easy to just install a new one.
Plasma is the desktop environment he wants on Tumbleweed. Neon is the KDE distro. I thought it was pretty clear he wanted to dual boot Windows tbh
A live USB would let you play around in a desktop environment for a bit to see if you like it before jumping in the deep end with it. But if you’ve already tried out KDE plasma and know you’ll like it, then you’re probably fine. I agree that you won’t become familiar with a full distro without data persistence and repeated use.
Maybe at least live boot gnome if you haven’t tried that one yet. Gnome and KDE are the most fully featured desktop environments, so they’re natural choices for users coming from win/mac.
Yeah, you can always install another, but if you are going to do that every day or two before settling on one, maybe consider installing virtual box and trying out the distros like that first. Of course, if you’re in a VM, it can be a challenge to get proper hardware acceleration if you’re going to try out gaming.
At the end of the day, I think dual booting is a good idea, as long as you only use windows when it’s your only option. That’s what I do. It’s easy enough to reboot if I need to play a game or use a windows specific app. More consistent than dealing with QEMU or something.
Can you easily switch drives in your system? I’ll often do that on my computer because little m.2 SSDs are so darn cheap now. It’s easier and cheaper to pick up a little 64GB drive for one off projects than it is to do a proper backup and restore.
Also, I’d just go with Tumbleweed. I don’t distro hop like I used to, but that’s because as everyone else is saying, most of the distros have gotten really good. Most of the time, my little projects are trying out specific features of a different distros. So I’ll just pop a new drive in, test drive it, then either switch back or not.
Mooby gives good advice! I tried out different distros in vm’s for 6 months after which I found myself very familiar and living in one more than my base os. At that point I nuked macos and installed Kubuntu no regrets. Kubuntu is a great start due to the popular Ubuntu base. Kinoite would be a good choice for its immutability. If set on Opensuse then choose Gecko as a more friendly way to install it.
It’s a bit of an unpopular opinion, but if you pick a mainstream distro there isn’t a lot of difference between them. Especially to somebody who is new to linux.
With most any distro you can use KDE, gnome and other desktop environments. You can pick which one you want to use when you login. So don’t think you’re tying yourself to KDE if you install kubuntu or something.
If you want an easy way to switch to a new distro make sure you create a separate partition for /home. Then if/when you want to install something new you can have it overwrite everything except your home directory. So all your steam configs and games will be left untouched (for example). Alternatively just backup /home somewhere and restore as you need.
Is a home directory similar to the users folder in windows, or like the program files folder? Is it ‘everything but the OS’? I’m still trying to get a grasp on how the OS operates conceptually.
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.
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 cmdortype cmdfrom 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?
Essentially, yeah. Most programs will install to your root directory, but all your personal configs and personal files will be in your home directory.
What I’d personally recommend is using Timeshift to automatically keep backups if your home directory on a separate partition, then if you want to switch distros or if you need to reinstall for whatever reason you can use Timeshift to restore your home directory pretty easily, as long as your new install uses the same file system.
For Nvidia I would recommend Pop!_OS since it makes things really easy. Either that or Debian with KDE. More mainstream = more users = better support.
OpenSUSE Tumbleweed is an awesome distro with up to date packages. KDE is also a great choice, especially with Plasma 6.0 around the corner.
I wouldn’t worry too much about Nvidia drivers, just follow OpenSUSE’s guide [1]. The remaining issues of Nvidia with KDE Wayland are getting fixed over the coming months.
Edit: OpenSUSE can’t ship some codecs by default for legal reasons (like RedHat, Fedora), but makes it simple to enable them (optionally through graphical YaST) [2].
[1] https://en.opensuse.org/SDB:NVIDIA_drivers
[2] https://en.opensuse.org/SDB:Installing_codecs_from_Packman_repositories
Keep notes on what you do including outcomes. You can always reinstall, skip all of the extra crap you didn’t need to mess around with and have a good clean system without having to back track.
From https://wiki.debian.org/DontBreakDebian#Take_notes
Take notes.
It’s easy to forget the steps you took to do something on your computer, especially several months later when you’re trying to upgrade. Sometimes when you try several different ways of solving a problem, it’s easy to forget which method was successful the next day!
It’s a very good idea to take notes about the software you’ve installed and configuration changes you’ve made. When editing configuration files, it’s also a very good idea to include comments in the file explaining the reason for the changes and the date they were made.
This has saved me so much grief. If ever I mess up a system so badly that I want to re-install or when I want to set up a new machine, having a clear set of notes makes it a breeze.
It’s easy to forget the steps you took to do something on your computer, especially several months later when you’re trying to upgrade. Sometimes when you try several different ways of solving a problem, it’s easy to forget which method was successful the next day!
History with Fish makes this easy
