How do you guys learn linux?

You need a neck beard. Makes it all easier.

3 Likes

Yup. Gotta have something to scratch.

1 Like

I use tldr first. Then go to man if I can’t get what I need out of tldr. Tldr is awesome. Tldr is usually better for reminding you of things you already understand, but for simple tasks it can be all you need.

4 Likes

But so much food gets stuck in it :expressionless:

Really?? I thought that was the job of the moustache…(soup strainer)…

1 Like

For most people learning is frustration. You have to be persistent and use the right approach and you can learn anything. Is it easy? No! Feelings are irrational so if you feel you can’t learn it you won’t! You have to dive right in. Avoid comparisons. Forget about what you know and think. It’s all new! Embrace the frustration. Unlearn old habits. Start from where you are. It takes time. It ain’t Windows! :rofl:

8 Likes

Lolz I still didn’t learn much, but I picked up a lot of solutions along the way.

Some times it was being outnumbered by pig-headed forum members… that helps.

Maybe Linux needs to start using a Registry and working harder to dumb itself down so that in the end nobody really knows what’s going on… For the most part, it’s so much simpler than Windows - things don’t just disappear leaving you wondering if your Defender removed it, or you’re getting false positives from an antivirus.

2 Likes

Use Slackware Linux for a while… :+1:

yeah I think i went through that in my learning process. not using it, but only installing it from floppies. I had no use for a linux server (as linux desktops were kind of unicorns back then), but it was contact with Linux nonetheless. I think in the grand scheme of things that had some contribution to driving me towards Linux.

Linux Learning really started for me with Arch Linux, the Arch-Wiki-Way. Everythings else, beforehand was nada-zero-zip when compared in hindsight.

I am happy that EOS still utilizes that Arch spirit in a great way, and enhances things in a learning way with such a good spirit, even here on the forum.

Thanks, EOS-Peeps!

2 Likes

I was in the shallow lakes of Linux Mint and I dove right into

Two days later Arch Linux was up and running with Enlightenment, Firefox and Virtualbox with minimal RAM usage (around 250 MiB) as I desired.
That is how I gained a significant amount of my knowledge.

wait
I necrobumped :man_facepalming:

1 Like

I know I did, and yet I thought, it could be nice for some people here to pursue this thread.

No offense or nuisance intended.

2 Likes

A topic like this one can be running. We have other topics like this where they continually get bumped over time.

5 Likes

In fact, I started with minix on the Atari Mega ST4 in 1991. With SUSE on an IBM-Clone around 1995, tried Red Hat and also LSF (Linux from Scratch) which helped me most to understand what’s going on. Then I moved to Ubuntu and to Gentoo which was a little more comfortable than LSF - since I still make a re-setup every half year.
Today I am on EndeavourOS because this supports my actual hardware (MS-Surface with touch screen and Pen) best. In between there was Manjaro and KDE-neon.

Around 1998 I switched completely to Linux - windoof only for special proprietary applications for my business. But 98% of my time I work with Linux, and I am satisfied and convinced by the strength of open source. On my MS-Surface I am running MS-Windoof and two Linux instances in parallel, beside my old MS-Surface Pro 4 with 3 Linux instances among QubesOS - for testing and experiments. In my home there are further 4 Raspberry Pis and one BananaPi-R1 to be replaces very soon by the R2 (the R1 will then be used as a firewall).

Today I am also teacher on a High school, using Linux all the way with Microschrott Teams and Office 365 in the web browser on my Linux. However I teach my students Linux on the Raspberry Pi and they know about my preferences for Linux.

1 Like

Same way I learn everything. Play with it. Do something long enough and you’ll learn something usually.

I think the last few comments have proved this.
I learn from my mistakes and asking for help now when unsure of something (used to just try what was suggested from a search)

Well i’ts not really strange, i made a comparison for the path from novice to windows poweruser to the path from novice to linux poweruser.

For windows you start on top of a mountain and descend it gradually (through nice, well sorted gui buttons) till you become a power user.

On linux you start on top of a cliff, there’s a little playground on top of the cliff (your desktop environment which holds basic ass HID, Compositing and Window manager settings among a few others) but if you want to become an actual power user, you have to dive off the cliff, and it’s a learning experience that never ends, or at least doesn’t end till you’re writing your own drivers and contributing to the linux kernel to fix your problems :rofl:

But to get you started, here’s what I propose.

0: Get comfortable with the linux way of package management. On windows you download an exe file and run it, on linux you use either a gui or a cli to install packages. You can do it another way like using appimages or snap, but they should generally be a last resort, and you will want to know why that should be a last resort and what makes the linux way of package management superior to the way it’s done on windows. But also in what ways it’s less convenient.
1: Get comfortable with a terminal, cuz when shit goes really really wrong, you’re gonna need to be comfortable with it. The best tip I can give you to get comfortable with the terminal is to press Tab a lot.
2: Learn the basic linux filesystem structure. On windows you have C:\Windows and C:\Program Files and C:\Users… You know what those things are. On Linux you have /etc and /home and /var and /usr and /usr/lib and /usr/bin and /usr/share and /tmp and /opt and /mnt and some more… Do you know what these are? If you don’t, you should learn that. I can start you off with /etc/ contains a mountain of system-wide config files, but there are also per-user config files in /home/user/.config which can override the /etc/ configs for a specific user when they are logged in. You wanna learn this nuance.

Once you’re comfortable with terminals, you’ll rarely feel entirely out of your depth, and once you know how linux is structured, you’ll know what way is up and what way is down and which general direction you should be looking in when you need to find something specific.

So start with this before anything else.

1 Like

Like how you put this in steps, IMO much easier to start at the bottom though. When you fall from the top you take way more damage.

1 Like

When you divorce yourself from ‘Windows’ you have no other course then to learn ‘Linux’. That’s what I did after Windows ‘ME’ came out. I told myself if others can, I also can learn from my experience. It’s been a long time. I’ve also Distro hopped amongst the top 25 distro’s for many years to see what the differences were and compare who had the upper hand in software apps and distro functionality. It’s been fun and a good learning experience. It’s been a hobby also.

Rich;)

1 Like

Totally relatable hey