Just start using it. Set up a dual boot if you really need access to Windows still, but try not to use it as much as possible. You learn by running into problems or holes in your knowledge, and solving those issues will fill in other gaps.

There are plenty of video series if you want to listen to advice before diving in, but there’s no teacher like experience.

Install using the debian net installer. Only add a GUI/Desktop Environment through command line and apt. Don’t use tasksel.

https://www.debian.org/CD/netinst/

Do this on a laptop that’s not mission critical. Barring that, use Tails on a USB drive

https://tails.net/about/index.en.html

For learning about the filesystem layout, you can type man hier into a Linux terminal.

Or read the same online: https://www.man7.org/linux/man-pages/man7/hier.7.html

[email protected] [email protected]

I dabbled for a few years before I made the switch.

You learn after you switch. Not before. Because then it’s easier to search for a Linux solution than it is to reinstall windows and get it done in the way you’re familiar.

If you can dual boot and do your daily needs you are good enough to make the switch.

My personal journey:

Install random Linux distro as virtual machine or dual boot, use it until you run into something you can’t fix. Look for an alternative.

Do this a couple of times, my path was: Ubuntu, Manjaro, PopOS, Zorin, Debian, Mint. I ended up replacing windows completely with Mint. It’s nice, easy, customizable, and I can play my games on it when I need to 👍

Learning the terminal is easily done on linuxjourney.com!

Before I swapped to linux full-time, I used virtualbox to create test environments from various distros to see which one I liked best.

After testing: EndeavorOS, Manjaro, PopOS, Nobara, Ubuntu, and openSuse
I settled on Endeavor as my main driver and have been running it for over a year now. openSuse came close second for me, and Nobara was a distant last, I really did not like it. The important thing for me was to try several of them in a safe way that would let me experiment on if this was really something I wanted at all.

The first thing to bring to the process is curiosity. Linux is not Windows and doesn’t operate in the same way.

What you think of a normal Windows behaviour, is unlikely to work in the same way under Linux.

In Linux everything is represented within the filesystem. This means that you’ll find USB ports, soundcards, hard drive devices, mouse, as well as running processes, open files, memory and even the CPU as well as everything else to run a modern computer represented inside the filesystem directory structure you’re presented with.

The Linux kernel is the heart of every system. Each flavour or distribution (distro) of Linux package up their ideas for the best way to use the kernel, offering different ways to install applications, drivers, user interface, etc. The variety is endless.

Note that within each distro are multiple versions. Each distro is distinct and unlikely to do things in the same way, so instructions found online for one might not apply to another.

The vast majority of software available is packaged from source by a distro and made available to you as a package.

You can compile anything from source, but that is a very deep rabbit hole, something you’d want to shy away from for the first year at least.

Packages have dependencies which most package managers attempt to deal with. This works fine if you use the same distro, but has a very high chance of breaking things if you start pulling packages from other distros or versions.

Much can be achieved with a GUI, but the real magic happens on the command line.

To get started, set aside an old machine, or build a virtual machine on your Windows PC and start learning.

I’ve been using Linux daily since 1999, and I’d recommend that you start with Debian. It’s stable, highly compatible, has a massive package collection and is properly documented.

Other distros like Ubuntu are (loosely) based on it.

Whatever you do, take it slow, make regular backups of your data and ask questions.

https://linuxjourney.com/

https://linuxcommand.org/lc3_learning_the_shell.php

One of the more interesting things for me was learning how in depth some of the commands are. For example I wanted to use wget to back up a website that was having issues at the time. I built an advanced command after going through every option and learning what it did.

Install arch the old fashioned way using the installation guide and then maintain it for a year or so. It’s not hard but it’ll take you some hours to get going if you are just used to buttons which tell you what they do.

there isn’t actually that much to read, at the user level. Nowadays, on a “user friendly distribution” you should be able to launch firefox to browse lemmy, and open a pdf without much difficulties. Even printer aren’t anymore a nightmare to install.

Main stuff to know IMO.

• Linux distribution came with app store long before it was cool, for 99% of the case should just use-them, no need to worry (at first) about how to install an app which doesn’t come from an official repository

• While you can choose among many Desktop environment, just take the one coming with the distro you choose and get used to it.

• Terminal is a pretty neat tool once you know-it, but so is a Torque-wrench for your car. You do not have to know how to use-it to use a PC.

you really want to learn linux?

https://www.linuxfromscratch.org/

I don’t know if it still exists, but following along with the Gentoo Linux install guide where you build everything from the ground up. I definitely wouldn’t daily drive something like that now (I had a lotore free time (and no money) back then), but learning what the commands did was great for learning not just about commands but a number of Linux concepts.

I had a tiny bit of very basic previous experience, mostly with common command line tools like CD, ls, etc.

It really depends on your approach to learning things. If you’re looking for a systematic approach, I really like No Starch Press books for that sort of thing: How Linux Works or Your Linux Toolbox (for a more playful approach).

But in the end there’s really no substitute for installing Debian on bare metal and tinkering with it. I would really recommend Debian, because it’s the archetype of how Linux systems have been working for the last 30 years or so. Arguably, this is currently changing, but come to grips with Debian before you dabble in more modern approaches to system management.

Find an easy distro (my recc is mint if you’re coming from windows, elementary if you’re coming from Mac) and just do it. Follow the install guides and just start trying to use your computer. Look up things when things aren’t working. If you get frustrated or justconsistently don’t like your distro, find a different one. Most people don’t know the exact distro they like with their first attempt. It’s very common to bounce around to different ones for a while or even have multiple.

Some will allow you to do a live environment off a USB stick, but I don’t know. I never found that really told me whether not it was going to be a good daily driver. But it does give you an easy way to check out the “vibes” of one without having to actually commit to it