I've bought new parts and I am awaiting their arrival so I can build my brand new computer. I've decided to go for Arch Linux with KDE plasma or perhaps Gnome as my desktop environment but that's as far as I've come.
One thing I suggest is:
You're trying to get something working but it isn't going anywhere? Try again later.
First, because of the obvious calming down, since stress can affect the person's capacity to solve problems.
Second, I've noticed how many things on Linux have some degree of similarity and/or relation to one another. So trying other things in the meantime can give you the needed insight for solving a previous problem.
And don't skip over reading things! I also run Arch with KDE and honestly with almost all problems I have, if I carefully read through either the Arch Wiki (this will probably be your most valuable tool) or the error message that comes up, the answer is usually in there somewhere, it just needs digging up.
Also: if something with a GUI crashes and doesn't give an error message, try running it in the terminal. So like, if Firefox crashes and doesn't give any info, try opening up a terminal and running firefox from there and the terminal will tell you everything that's going on. (It'll be a different command if you're using a flatpak but that's the general idea.)
A good refinement of this advice is to keep a Q&A sheet in your Dropbox or in Google Sheets or something, because writing down your answers that you discover can help you remember them, and can provide a backup plan in case you forget the answer and need it later, and can remind you to circle back to a question later when your toolkit is bigger.
Edit: also, it helps manage your backlog - you can make a rule like "if the unanswered count ever gets to ten, I'll sit down with an experienced user and try to clear them all"
Boosting this advice. When I started using Linux as my daily driver (14 years ago), I got into the habit of taking notes on everything: troubleshooting solutions, bug fixes, how-tos, configurations, useful software, etc. It's not the Arch Wiki, which is a treasure, but I can solve a lot of my own issues just by looking up what I've done before.
Yes! I have an entire folder in Joplin that's just lists of what broke and how I fixed it so I can refer back to it later. It's saved my ass so many times.
One thing I suggest is:
You're trying to get something working but it isn't going anywhere? Try again later.
First, because of the obvious calming down, since stress can affect the person's capacity to solve problems.
Amazing how many situations in which this can be applied!
Doesn't matter what distro you choose. I'd suggest picking one with a large support base, and not a niche distro.
But ultimately, pick one, don't become a distro hopper, or one of these folks that's always asking "what's the best distro".
As a new user, if you try out a distro for a few months and it's just not "clicking" for you, there's nothing wrong with trying something else out.
More than anything else, once you do find the distro that feels like home, learn to tune out the haters, because they're going to crawl out from under their rocks every bloody time you mention the distro you use, and try and tell you why what they like is better.
You'll notice I haven't mentioned which distro I use. And that's for a reason. I happen to think it's pretty damned fantastic, but there's at least one other person that will read this, and feel its the worst thing ever, of all time.
As far as tips go? Learn to read error messages, learn how to use a websearch, learn how to ask intelligent questions when you need help.
If you're installing Arch, one trick the installation wiki article doesn't tell you:
If you type "archinstall", it has a command line installer there that'll do the install for you, and lets you pick from several desktop environments as well. I've had it crash before more than once, so it's not perfect, but it's less of a pain then doing it all by hand...
My absolute, #1 biggest recommendation is to male separate partitions for / and /home.
What does this mean? In short, you're telling the system to treat different sections of the hard drive / ssd as entirely separate buckets. In this case, you're putting all of the operating system and programs in one bucket ( / ) and keeping all of your files and settings in another (/home).
Why does this matter? As someone learning Linux, you should tinker with things, learn what they do and how they work. Sometimes, that means breaking things, occasionally in spectacular ways. Having your files and your OS separate means that you can completely wreck your OS while you learn without losing your data in the process- you can reinstall from scratch or even distro hop (try out a new version) without having to stress over losing anything. In short, you can learn and play and blunder and explore without risking anything more than a 20 minute reinstall if you can't figure out how to fix it.
I recently switched to Fedora to help get into the Arch based Linux realm. Historically been on Debian based distros. You can’t go wrong with many of the “mainstream” distributions as your first intro to Linux. If you come across any issues ask away and that it a how you’ll learn more about how Linux works, Arch, etc with your hardware too.
Don't start with Arch unless you're looking for a trial by fire. It's a distro intended for advanced users who already know a few things about Linux. I don't even use straight Arch, and I've been using Linux for years. I do use EndeavourOS as my daily driver though, and that's basically a pre-configured Arch with a GUI installer.
Ubuntu, or one of its variants like Kubuntu or Xubuntu, is a better pick for someone who's just starting out. Mint is supposed to be decent for new users too.
You made a wise choice picking a Radeon, btw. Nvidia support on Linux isn't the greatest. AMD, on the other hand, is nearly plug and play since the drivers are built into the kernel. You may or may not need to install extra drivers for proper Vulkan support though.
Another thing I should mention; if you decide to dual boot with Windows, it may seem like a smart idea to share your steamapps folder between OSes, but this doesn't usually work out well because of the way Proton uses symlinks. You're much better off having separate steamapps folders for each OS, even if it uses more disk space that way. (Proton is the compatibility tool Steam uses for running Windows-only games on Linux. It even works better than running Linux-native games in a lot of cases)
I mention the steamapps thing, because it's a common newbie mistake to try sharing a steamapps folder between Windows and Linux.
Linux is a pretty deep rabbit hole to dive into, and it's not for everyone. But don't let this discourage you; it can be rewarding if you're willing to learn how to use it.
I’d say that Ubuntu is a great choice because there is a lot of support out there, in articles/support forums and apt repos for most things that you can just drop in. Even if you want to run the latest bleeding edge kernels the ppa support is excellent. For me it’s a pragmatic choice of distro even if ideologically I’d prefer to run plain Debian.
I’m rooting for OP, though. Starting their Linux journey on hard mode is something to be lauded!
Truthfully, I think the amount of support Ubuntu has is a double-edged sword, because while it is easy to find resources for it, it's also easy to find outdated information that doesn't apply to newer versions. Similarly, with PPAs, they can be quite useful, but you also have to be careful not to hose your system with them.
If OP is willing to stick with Arch, and learn to work with it, then I say kudos to them. The main reason I don't encourage new users to dive right into it is because I don't want them to get discouraged and give up, People learn things different ways though, and for OP, this may just be the ticket for them.
I don't know about this. In my experience with ChatGPT was really bad, at least for programming. Asking about libraries, it started to allucinate and invent some APIs. Also with working with a REST API from GitHub, it started making up endpoints.
So, specially for a begginer, I'd say that better go with the other popular resources (ArchWiki and Server Fault)
And you can expect this to possibly get worse. I remember seeing a post about how AI is now having trouble obtaining good quality image data because the internet has become saturated with AI generated art. I imagine text content is even worse. I've already seen several news articles lambasting a few lawyers for referring to non-existent cases.
The bottom line is that ChatGPT and other AIs don't understand what they are writing. They are just stringing words together by association with keywords. It's writing convincing sounding fiction about the real world. The fact that you can get things like vaguely working code out of it is just a happy accident.
At best, AI it should be seen as an idea generator. It requires that the person be skeptical of whatever is output.
Linux has 'swap'. Pretty much it's a back up to prevent your computer from crashing if it tries to use more ram than it has, so it allocates hard drive space to be used as ram.
Different distributions have different suggestions on how much space to allocate for swap. Depending on how much ram you're putting in your machine and how you plan on using your machine will heavily influence the size of swap you need (ram intensive vs not ram intensive).
You can set up with a 'swap file' on a hard drive after you install your OS.
Or you can set up a 'swap partition' on your harddrive when you're setting up your partitions prior to OS installation
Or you can set up a separate harddrive as a swap drive
Or if you have a lot of ram you can avoid setting up swap entirely. This is not advisable though, it sucks finding out something is ram intensive when what you're doing crashes.
It's good to have an idea of how you want to map out your hard drives before installing your OS.
The world is your oyster.
If you're dual booting windows you need to turn off 'safe boot' in your BIOS.
Ubuntu is a very solid choice and will give you results very fast without hurdles. You can then look under the hood to see in detail how it work if you want to.
It's important to just stick to your package manager at first, don't jump too fast into the flatpak/snap/container wagon. When you know exactly the purpose of a package manager then you can look outside. Your package manager is your best friend, whatever the distro you use, stick to it as much as possible, you won't regret it.
Also, if you are looking for a program under linux but you only know the equivalent in windows/apple, you can use https://alternativeto.net/. Enter the name of the program you are looking for, then search for the alternative for linux.
For example, photoshop -> Gimp or Krita. Then search for it in your package manager.
I'm running KDE on Archlinux. I had used Linux Mint with Cinnamon before, and only Windows other than that. My advice is don't use the arch installer script (it just didn't work for me at all), but follow this guide. It worked perfectly for me.
They also have a guide for installing KDE. If you want a lean system, don't install the kde-applications package, however that will mean a few things like printers won't work without installing the printing service, but kde-applications installs a lot of apps you probably don't want.
[Edit]: I also meant to say put home on a different partition. It makes life a lot easier if you mess up your system or want to reinstall or want to distro hop.
My general advice is to spend some time making your command line look just like you want it to (font, colors, prompt, etc.), and then try to live on the command line. Just about everything you want to achieve can be done through the command line. It's not always the easiest solution, but it will teach you the ins and outs of Linux, and it'll help prepare you to solve whatever challenges you may encounter.
Once you've picked your flavour I'd say choose how you want to partition and manage backups / snapshots. I see you have 2 ssds, so are you planning on raiding them with something like btrfs? Do you want to encrypt your drives?
No, I am not going to use RAID. The only reason I have two SSDs is just for the extra space for games and all my projects I work on. Drive encryption is not something I have thought about, not sure if it's beneficial for me.
Cool. So what I've found useful is to spend a little bit of time upfront to decide how you want to do your partitions, and what file systems. So, for example, I don't care about backing up projects (yay git) and their build artifacts, don't care about .cache, but do want backups of .config and my steam library. I use btrfs for snapshots, and btrfs send that to my NAS, but obviously a lot of stuff can be restored easily so that's bind mounts.
Or use LVM (with or without LUKs) and at least give yourself some wiggle room for later.
Add comment