I’ve seen this one recommended in the past. I think it’s great for beginners yet still full of useful information.

https://linuxjourney.com/

Linux is a tool. And I find that the best way to learn handling a new tool is making a project with it.

A book is (maybe) fine, but a project will help you use your knoweldge while you gain it.

So set up a Lemmy/Minetest/Matrix/Teamspeak server or write a bash script to change your audio output device/volume or program a simple bot in your favorite programming language or mix some music or gather a bunch of PDFs and search through them and concatenate them

And while you do that and create directories, change permissions, move files, create users or “cat” or “grep” or “sed” stuff, find out, what every single line you write in a terminal does. And instead of using a graphical program to move files, shutdown your PC or update all programs, only use the command line.

This will help you in the long run.

https://linuxcommand.org/

I think you need like a project that will give you a goal and things to look up to do specific things. What got me into Linux was running a minecraft realm, then we hit limitations on the service so opted for a server instead which lead down the road to a VPS and had me using Linux and commands

Nice to hear that you have found your way to Linux. What helped me a lot to understand Linux and the command line better was trying to install Arch, following the instructions in the wiki, failing at the first attempt and trying again and finding the error.

My first recommendation is to become familiar with one flavour of Linux. Debian is a solid choice and it will give you a good understanding of how a great many derivatives operate.

The command line is a tool to get things done, it’s not an end to itself. Some things are easier to do with a GUI, many things are easier to do with the command line interface or CLI.

Many Linux tools are tiny things that take an input, process it and produce an output. You can string these commands together to achieve things that are complex with a GUI.

Manipulation of text is a big part of this. Converting things, extracting or filtering data, counting words

For example, how many times do you use the words “just” and “simply” in the articles you write?

grep -oiwE "just|simple" *.txt | sort | uniq -c

That checks all the text files in a directory for the occurrence of either word and shows you how many occurred and what capitalisation they used.

In other words, learning to use the CLI is about solving problems, one by one, until you don’t have to look things up before you understand why or how it works.

I think, as a Linux beginner also (~10 months), the best way to learn the terminal is to figure out what tools are useful to you and then read the manual pages or [application name] --help (if the application supports that command). Learning how to use grep will also be really helpful for troubleshooting, since sifting through logs is such a pain.

Like if you want to download a YouTube video, install yt-dlp and then type man yt-dlp into your terminal to learn about how that tool works. You can do this for basic utilities too, like cp, dd, mv, etc. and other applications you have installed. You can also use yt-dlp --help but that won’t open in the parser, just the terminal. Learn by doing things that are relevant to you and branch out from there.

There are also applications that will let you read the manual pages outside of a terminal, like xman, if you find that useful. After a certain point, you’ll be able to write commands with switches/arguments without needing to check what they mean first.

There’s someone posting a pretty well-crafted intro to Linux series here on Lemmy. Look for that and go to the linked website and dive into the parts that you find interesting. I think they post a course chapter per day in the format of (approximately) “Day 15: Topic for that day.”

I’ve skimmed some of the course material and thought it useful for beginners. I’m really happy that they keep posting each month.

One of the biggest things that helped me was setting up virtual machines and installing different versions of Linux in them and just playing around. I found it super helpful because it makes you learn different things (for example you mentioned reading the Arch wiki which is a good resource, but not all of it will apply to Mint necessarily) and as an added bonus, it doesn’t matter if you break everything. You can just restore a backup, or better yet, reinstall from scratch so you get used to the process or better yet, keep breaking stuff until you come out the other side and get things working again!

I never had an IT background and also “just tried” Linux a few years ago.
Now, I’m still not an Linux expert, but relatively proficient with it.

I tried reading “How Linux works” (free e-book), but didn’t have a great time with it.

It’s just too detailed for someone who just wants to use Linux. It might be an absolutely great resource if you plan to work in IT, but other than that, just it’s too much wasted time.

What helped me a lot was to use Linux as an OS for my homeserver.

You don’t need anything fancy for it. Just use an old spare laptop or something similar you have laying around, or buy an used small form factor PC, like those Mini-PCs many businesses use. Those often cost less than 50 bucks and would otherwise land on the trash.

Then, install your server OS of choice. The most popular one is just plain ol’ Debian, and it’s what I used. It’s a great choice!

Servers run without a display or GUI (DE/ WM). You set it up once, and then connect to it remotely via SSH.
With that, you can either install a web interface like CasaOS or Cockpit, or just use the CLI for everything.

For the start, you can choose just Nextcloud AIO and call it a day. It comes with all things needed for a functioning webserver. But, things said, the learning experience ends here pretty quickly. It’s made to be easy and painless.

If you want to learn more, then consider setting up the stuff for yourself. It’s also really not hard (coming from someone who doesn’t IT stuff professionally!), but takes a bit more time, because you have a lot of choices.

For that, you might consider checking out c/Selfhosted and awesome-selfhosted on GitHub.
Theres a lot of really cool things you can discover!

The main reason I recommend that, and not just “Try LFS, Arch, Void, Gentoo, or whatever” is because I find it pretty much useless. Sure, you learn how it works, but for what price?
When you set up your own homelab, then you have actual useful things running, you also learn a lot, and maybe you can add it to your CV when applying for jobs. I for example work in the chemistry sector, where IT stuff like this is pretty useless on the first glance, but I often got invited for a job interview exactly because of that. It’s just a nice skill to have!

For checking out great CLI tools, check out the according video from TheLinuxExperiment or other YouTube/ PeerTube videos.

Try to learn the basic commands, like cd, ls or cat, then look up for more advanced/ alternative tools, like tree (instead of ls), bat (instead of cat), and so on, and then try to learn shell scripting.

I really like using fish instead of bash, because it’s a very friendly and interactive shell ;)

I hope that my comment was helpful! :)

Another resource https://ryanstutorials.net/linuxtutorial/

There’s a lot of good suggestions here.

As someone who uses Linux but doesn’t love it, be prepared to restart from scratch a lot. Keep the OS on a blank drive and just point the OS to your storage drives once it’s up and running.

Otherwise you are going to be losing data every time you break something in the OS, and that is really no fun.

Using LLM works great since Linux documentation is extensive and was used to train the models.

Just tell it what you want to do and it will write commands and explain how they work.

Even models that can run on mid grade consumer GPU can do this now.

You can set up a docker container for webui and load models in there.

I have a list of learning resources for CLI tools and scripting here: https://learnbyexample.github.io/curated_resources/linux_cli_scripting.html

I’ve also written a few TUI interactive apps to practice text processing commands like grep, sed, awk, coreutils, etc: https://github.com/learnbyexample/TUI-apps

I have been using terminal almost exclusively for about a decade or more. But, when I started I just decided to do it. And that meant that every time I wanted to do something, it would take me forever because I would have to look it up. Eventually, I got faster and faster and now anything I want to do with a gui, I can almost certainly do faster with terminal.