Not very practical, but good for understanding the OS: Everything is a file. Even your filesystem and harddrive is represented by a file (devicenode).

Back in the day, before things such as pulseaudio and equivalents became the norm, there was also such a file (it might still exist, idk) for your soundcard. By shoving the contents of a wav file directly into /dev/dsp, you could hear it as if it was played normally.

Unrelates to the above, in a terminal context it's very handy to learn the concepts of STDIN, STDOUT, and STDERR, and how to manipulate these. I won't go into it here, but whenever you see a bunch of commands strung together with redirects, < > | >>, that's usually for sending the output (STDOUT) of one command somewhere else, such as to the input STDIN to another command.

My big tip is if you haven't already, switch to a local package repository. There are a lot of people mirroring the software packages for mint and you can switch to one that is geographically the closest to you for better speed and to spread out the server load.

I love Linux Mint and it's what I install on all my decom-laptops turned servers. It will do pretty much all you want to do in Windows and then some. The only thing it probably isn't the absolute best for is PC gaming but if you are just using a laptop it probably doesn't make much of a difference either way.

If you like Mint then I also suggest PopOS. They are both based on Ubuntu so a lot of the paths and the package manager are the same. The killer feature there is auto-tiling Windows which is like the window snap feature in windows but happens automatically. It's not for everyone but once I started using it, it changed my entire workflow.

Last thing is, if you haven't already, familiarize yourself with running docker containers. A lot of stuff that's complicated to set up is a breeze with docker and docker-compose.

KDE is your friend in the trenches, Kubuntu > Ubuntu 100%

Regardless of whatever distro, definitely keep all your stuff backed up on an external drive. I had to "restart" my install a few times to get the hang of things. Yet I still keep all my info on an Vegacrypt encrypted external just in case to this day.

I think the two "major tips" that I can give you are simply

1- Package manager is your best friend.

2- Figure out the "know-hows" of Linux (i.e who "is responsible" for the video card, who deals with the cpu, how do i configure my sound card, how do i configure my video card, etc.).

Master those two tips and you can call yourself an average linux user.

My tip would be to try a few distros before you settle on one. Ubuntu was it for me about seven years ago, but I used mint for a few years and am using MX with xfce now.

Also, sudo !! is pretty useful when you forget to sudo the previous command. It means "super user do the last command I just boneheadedly forgot to do that to"

My main recommendation is this - The more techsavvy you are, the harder a switch to Linux will be, because you know how to do some complex things on Windows, and now you'll have to relearn it on Linux.

Take your time, Google lots, and just know the ceiling on Linux is much higher for power users, so getting over the initial hump will reward you greatly

Two tips:

I have not tried running WINE yet but I plan on doing so soon.

Steam "just works" on Linux, you can install it via flatpak (which I use) or from their deb repo. It includes "Proton", which is a fancy bundle of wine and some extra open source valve sauce to make it nice and easy to use. Any game that runs on the steam deck also runs on Linux via proton, and there's no messing around at all. It looks and feels just like steam on Windows, and thousands of games just work with no setup or config beyond clicking the big blue and green buttons to install and run. Not EVERY games works, but tons do. I'd heavily recommend this over raw wine to a beginner.

The second tip is not to ask what you can do on Linux. The answer, to a first approximation, is that you can do everything on Linux that you can do on Windows or OSX. I daily drive all three, and mostly do the same stuff on them. Instead, ask YOURSELF what you WANT to do on Linux. Then Google and ask us HOW to do it... or what the nearest approximation is if the precise thing you want to do doesn't work on Linux.

Switch from bash to zsh and make it look nice – dev.to/abdfnx/oh-my-zsh-powerl…
Also replace ls with exa and cat with batcat. Remember you can set aliases in ~/.bashrc or ~/.zshrc.

If you like customization, I'd recommend KDE.
If you like customizing keyboard stuff, you can customize your keyboard layout here: /usr/share/X11/xkb/symbols. Also look into espanso for text expansion.

If you have an Android phone, get KDE Connect.

If you need new software, check apt search if it's in there.

Oh My Zsh + PowerLevel10k = 😎 terminal

Hi there, The developers always use the terminal, but it is boring and has no colors or shapes. Today...

^{abdfn (DEV Community)}

If you're typing out a long file path in the terminal you don't have to type the whole thing out, you can just press tab and it'll autocomplete for you.

So for example, if your file is called 1234567890.jpg you can just type 123 and hit tab and it'll fill in the rest. And if there's more than one file that begins with 123 it'll list them. Works for folder names too.

I second this. Just going through vimtutor a couple times and then learning how to use the :help pages effectively is all you need to make vim usable.

I'd recommend using neovim over plain vim though, if not for any reason other than it has nicer defaults.

Unless you are looking to work on shared systems/servers as sysadmin or other jobs, explore shells like zsh or fish and customise them rather than stick to bash. A lot more user friendly and accessible advanced features. Helps with learning a lot. Zsh is compatible with bash but fish isn't. So choose based on what your goal with learning shell is.

If you are sticking with debian based distros, try apt and synaptic(GUI) to install your software. At some point you might also need to install tar archives. Don't get worried as most guides should be easy to follow.

Start off with Bottles if Wine is too hard. Wine is a cmd line application while Bottles is Wine with a GUI making it easy to manage Wine.

Also, it is wise to try and have a different wine bottle (aka prefix) for each windows application you install and run.

Also Linux Mint is a distro that comes with Cinnamon pre-installed as long you download the Cinnamon option which is a fork of Ubuntu.

First thing I'd do is ditch the GUI file manager: get comfortable with cd, ls, mv, rm, etc.

After that, maybe start with basic text manipulation, like grep, awk, sort, uniq, etc. This ties in nicely with IO redirection, which is essential for a "CLI based workflow." Get comfortable with pipes and file redirection, it's extremely powerful!

Writing shell scripts is another super useful exercise: any time you find yourself running the same set of commands multiple times, think about making it a shell script. You may end up with some really useful little custom tools that way.

Welcome fellow Linux beginner.

What are some really important basic commands I can use to start branching out into Terminal command structures

Since I refuse to touch the Terminal like my life depends on it, I can't help you with this 😅

And if Cinnamon has shortfalls or weaknesses that I may run into eventually, what are some good alternative distros that I could leapfrog to eventually?

I'm a little biased, so take it with a grain of salt: Cinnamon's biggest flaw is the lack of support for the Wayland protocol. It's still running with x11. As far as I have read about it, X11 has several big security flaws, and it slowly dies a long, quiet death. As far as I know, the Linux Mint devs (makers of Cinnamon) haven't even started on Wayland support. A good alternative would be the KDE Plasma Desktop. It's insanely customizable, and the default look comes very close to classic Windows. As a KDE Distro, I would recommend KDE Neon since it's based on Ubuntu too.

Edit-and-execute is very much worth learning about.

Don't try to install the best X and the best Y. Just start using what you can find, then gradually improve things as you notice becoming annoyed. Within a few years, you'll have a setup you enjoy.

Dotfiles. They let you customize your command line experience. There are loads of examples on GitHub. Reading through the comments on dotfiles that other people share help you learn about all the things that can be done. Customize your shell with aliases, functions, history behavior, syntax highlighting, etc.

I'm a Mac user who tinkers with Linux off and on, but I absolutely love that you're learning about the world of Linux. Welcome to the party!

github.com/topics/dotfiles

Shameless plug of some of my own custom tooling: github.com/fantismo/dotfiles

GitHub

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 330 million projects.

^GitHub

Remember to play. There are multiple terminal emulators, window managers, shells, all the things! Try 'em out. When installing stuff to test via distro package, keep note of which dependencies were dragged in so you can get rid if all of them, not just the thing you wanted to test. Also keep a list of what you tested and later got rid of (and why) so you avoid testing it again.

If you ever ssh into other machines to do stuff, learn the minimum of vi (classic w/no arrow keys, not vim) and bash. Servers "always" have those (though FreeBSD also has tcsh).

Probably already mentioned in other comments, buy it can't be stressed enough: Backups !

Part of learning to use Linux is breaking it. You will make mistakes that will bork your computer. You can either spend hours to try to fix it, or you can wipe everything clean, reinstall, restore from your latest backup, and be done like nothing happend in no time. (Maybe you want to go the hard way for learning, but it's always more relaxing to know you also have the easy option at your disposal)

Ubuntu comes with Timeshift, make use of it. Also plan to make backups to external storage or NAS, in case things go real bad.