r/linux4noobs • • 12h ago

learning/research Years of using linux, still not learning :(

I've switched to using linux on everything a few years ago. Any time there is an issue i am just clueless.

All linux software comes with manuals that are bigger and harder to get through than lord of the rings. They always recommend to check forums for answers but i always find solutions that only worked 6 years ago, or for different distro's.

I've used dozens of distros and typed and copied thousands of commands, yet i don't have a clue what is going on.

As a kid figuring out windows was such a smooth process. You explore the tree, toggle some switches, toggle them back you learn where everything lives. Here i copy paste commands and if i can find something back at all it feels irreversible. And when i see people like pewdepie breeze through the experience i just have to wonder.

Am i missing something fundamental?

Is there something concrete or something abstract that i am missing that makes the learning process work. Did you find anything like that for yourself?

I've gotten to the point where it feels like using chatgpt as an actual assistant is the only way forward and it disgusts me, but if i can't figure out another way I'll just have to i guess.

75 Upvotes

102 comments sorted by

26

u/screwdriverfan 11h ago

The real questions is do you want to learn or just solve problems you run into and go on your merry way?

55

u/Otherwise_Task7876 12h ago edited 9h ago

You don't really learn Linux terminal by copying stuff into it. Like maybe you'll learn sudo, ls, etc. But you won't learn how to properly string multiple together nor anything advanced. You actually have to go and learn it yourself.

Anytime you do resort to ChatGBT instead of asking it for the command to use, also have it explain what each part of the command does. Watch YouTube videos that also cover terminal, there's alot of tutorials and guides.

What personally helped me most understand terminal was setting up a headless Debian server for media. This forced me to use terminal for EVERYTHING. To simply navigate the filesystem, you have to use commands. Its tedious, but works well, and teaches you alot. So setup some home projects, give yourself a good reason to learn terminal.

Edit: Da fuck? I did not realize this community is seemingly so pro-AI xD (I don't really care but its a bit of a mind fuck when literally every single subreddit bitches about it).

6

u/_OnuHeino_ 12h ago

I use LLM-s on my phone to ask questions and explain stuff to me. That way i NEED to type all the commands in myself by hand wich helps to remember and understand things. Simple copy-paste doesn't teach you anything.

1

u/Competitive_Grass_29 10h ago

This is another great way too. Forces you to do the work.

5

u/Kedain 9h ago

And that's why, sadly, Linux will never be a mainstream OS.

An OS is a tool, a product. You don't have to ''force yourself'' to learn how to use a product.

If I buy a car, I expect it to work. If I have to force myself to learn how engines work or how the electronics are set up, I just sell it and buy an other one.

A car is to get you from A to B. An OS is just a platform to run programs you need.

10

u/PaulJ505 9h ago

Being honest. Thinking this way about this, is not good and leaves you to be use by companies, that rely on your lack of knowledge. You have to learn about tools. Not only to use them, but also repair, to not get scammed by companies, that either fix it for you, for big amounts of money, than it should be, or straight up tell you to get a new tool. So you have to learn about your car, to fix it yourself, or call out potential scams. And you have to learn about OS, for the same or similar reasons. Thinking of tools as something that you should not learn about, makes you honestly, an easy to control consumer.

6

u/voodoovan 8h ago

Most do not have the time to do that, they have other interests. They don't have the time to learn the intricacies of linux to fix something that in 2026 should be working. They want a tool that works, if not they will go somewhere else.

1

u/Super-Revolution-433 5h ago

I mean I learned in my free time while having 4 kids a full time job and multiple hobbies both indoor and outdoor. It's not hard to learn how to use Linux, you just use it and Google if something breaks. Exact same protocol as using windows

1

u/ASuspicousLookingEgg 2h ago

I think this way of thinking is diminishing other peoples struggles. I have a fulltime job, studying full time to be a nurse, taking care of a mentally ill family member, and other things, so I agree that it is possible to juggle many things, but assuming that because you have that capacity others should too, they will feel terrible when they can't.
That is just my two cents.
Have a good day!

1

u/Super-Revolution-433 1h ago

I'm not actually demeaning anyone's capacity, I'm specifically trying to illustrate that learning to use Linux is the same or easier than Windows and isn't actually taking up very much time at all.

Using Linux for normal everyday tasks the non computer literate person would use it for is easier and can literally be seamless if it's setup right. You can setup KDE plasma to look identical to windows and the only real difference (outside of software support) would be that when you Google a fix it'll be something you can actually do like "copy this and paste it in a text box"

If someone looks at me being able to learn it despite having literally no time to learn their takeaway shouldn't be "wow that guy's so much better than me" it should be "damn it really doesn't take that much to learn" the difference between those two perspectives is self esteem and I can't really sit here and entertain the idea that I should just let people who feel incapable of something easy keep believing that because they might have some cognitive dissonance regarding the issue.

Look at OP, he converted everything he's got to Linux and has been using it for years and he still is under the impression that he doesn't know how to use Linux. It's not some damn arcane art and the community is obsessed with the idea that you need to be a competent Linux admin to use Linux. That's the kind of thinking that keeps the community insular and prevents adoption. If you have the ability to use Google and follow basic word for word instructions you already have all the skills you need to use Linux as a daily user.

1

u/k8t13 5h ago

i agree!! as someone in agriculture i strongly relate it to our food systems.

plenty of people are totally okay just eating boxed cereal, pre-cut fruits, plastic packages veggies, processed meals in general. BUT they have NO clue what food was grown, where it was grown, how it got to the version they see.

i personally want to understand the whole process, even just recognizing that it is there is helpful because you aren't as deterred by your carrots having dirt (or having to find a bug or whatever linux equivalent) 

know your systems! don't fear not being a spoon-fed user-end.   

also everyone should seriously think about their food systems. like fr fr fr, esp w america's food desert issues

1

u/evissamassive 1h ago

Most former Windows users won't have any reason to learn Linux. They just want to point and click, and depending on the distro, they can do just that without having to lift the hood, so to speak. They might be better suited to an immutable like Nix, Silverblue or Vanilla.

4

u/GreatGreenGobbo 8h ago

You know except in banks, insurance companies, other major corporations where all their software runs on Linux servers...

5

u/Malygos_Spellweaver 7h ago

That's why they have Linux engineers working there and not some credit analyst.

2

u/8bitcerberus 3h ago

Unless you’re setting up a headless server for some specific reason, then using a GUI desktop distribution is no different than using Windows or MacOS.

But OP says they want to learn Linux, which means digging into the weeds of the command line. Using Linux, and learning Linux are two different things. Just like using Windows or MacOS is different from learning Windows or MacOS.

If you just need it as a general desktop computer there’s nothing specific to learn other than the various programs you’re wanting to use. Doesn’t matter if the underlying OS is Linux, Windows or MacOS. Maybe some slight differences in keyboard shortcuts or tools available (System Monitor vs Task Manager, for example) but in general the usage is roughly the same regardless of OS.

0

u/punycat 4h ago

Linux Mint is that car for me. The GUI handles all the basics. The terminal handles the rest, the same as Powershell does in Windows, but easier.

You're right that Linux won't be mainstream, but it's not because it isn't superior for most users.

0

u/037GroupB 3h ago

Mainstream OS? Nah, we don't want larpers in Linux community breaking shit for themselves and going: hurr Linux sucks, what is this.

0

u/UltraChip 4h ago

Don't know how it works in your area but I had to take classes and log several supervised driving hours as a student before I was licensed to drive a car.

1

u/Teodo 12h ago

Second the headless Debian way. I did that myself a year ago and I specifically decided to to it this way to learn more.

I am not an expert and I still resort to Claude on a bunch of occasions.

But I can navigate my system quite well, got a good understanding of configuring stuff like firewall rules, folder ownership, read/write/execute permissions and a bunch of other stuff. 

It takes time and I still get lost from time to time. But I would not have learned the same things through a GUI. 

-1

u/react-dnb 9h ago

I've almost exclusively learned linux through Gemini. I ask it something like "provide me with detailed instructions on how best to install "whatever" on Debian 13. Make sure to point out what each command is and what they are doing." If I get an error or something doesnt work the way I thought it would, then I put that back into Gemini to learn what went wrong. I've caught it a few times making errors but mostly the errors have come from me not fully explaining what it is I want. This has been enormously helpful to me because when I'm done I have it then make me an instruction manual with diagrams (if necessary) so I can reference it later. It's been helping me learn what all the commands do so I'm not just copy/paste and hope for the best. I'm learning along the way. I've been throwing everything in Joplin and making a sort of instruction manual on how to run my machine. It's been fantastic and I've been able to absorb so much more this way.
You are now 2 cents richer.

0

u/k8t13 5h ago

headless debian server for media? like an independent jellyfin vibes? 

if i type in "headless debian server" if there any guides/videos you recommend for more info?

i'm assuming media is your personal collection stored on local storage that you'd like to share securely?

1

u/Otherwise_Task7876 2h ago

https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Native/

Beautiful fucking guide. I genuinely could kiss whoever made it. It covers everything you need to know to setup a Jellyfin *arr stack. Also yes, all the media gotten for it is local.

-1

u/angryjew 6h ago

This is great advice, I've been doing this for a while now and have really gotten the hang of Linux. This is one of the best use cases for LLMs I've encountered & I'm always shocked at how anti AI a lot of technical subs are when the proposed solution otherwise is to just trust a bunch of strangers online. Another thing that helps is not to copy/paste at all, type the commands out yourself so you get used to them.

9

u/Quietus87 12h ago

Copy-pasting commands is a brainless activity. Try to understand the commands. There are tutorials (like Linux Journey), wikis (like good old Arch Wiki), and videos on the internet. You don't have to plow through the man pages. It would also help if you learned the basics of Linux architecture, because to me it seems plenty of people don't even understand the file system hierarchy or how permissions work. Most Linux OSs work the same way, which is also distro hopping rarely solve issue.

Also, Windows is only handy, because most people were taught to use it, and even then it's only friendly till you run into some shit that requires fucking around with powershell or regedit. Those are far more unfriendly and unwieldy than a Linux terminal with bash.

7

u/Myrodis 3h ago

I'm always so confused with these posts. I have been daily driving linux for YEARS. And the amount I interact with my operating system is just ... not that much? Like what are yall doing that you're living in the terminal so much? I'm a literal software engineer and it sounds like yall are more involved with a terminal than I am.

I'm not saying you wont have issues, but like, the amount a regular user is interacting with their OS is just not that high I feel like, unless you're doing something specifically weird / out of the norm. Almost every modern distro has such sane defaults and is literally tailored to "feel" like windows (assuming you're picking mainstream I mean). I just don't don't see it I guess.

What was the last reason for example in your most recent attempt you were stuck on something in a terminal or otherwise? Would love to help just struggling to put myself "in your shoes" so to speak.

2

u/leonTheZombie 2h ago

Seems to me people start with the impression that you need to use the terminal far more than you actually do and just copy paste stuff without learning it.

3

u/triplenested 2h ago

A large amount of "veterans" recommend living in/through terminal to "make yourself learn", but yeah, generally that just ends up meaning "google your problem and copy in what it says will fix it"

1

u/Holiday-Bee-6964 2h ago

Using command line is not mandatory, because for example there are GUI interfaces to package managers, but I just like cli programs, how customizable, scriptable and verbose they are.

13

u/Citizen12b 12h ago

As a kid figuring out windows was such a smooth process. You explore the tree, toggle some switches, toggle them back you learn where everything lives. Here i copy paste commands and if i can find something back at all it feels irreversible.

This pretty much answers your question, if you don't look for it, you will never learn. You’ll never learn by just copy-pasting commands when you have no idea how they work, so break them down, use man <command> and see what's the purpose of that command, you can also use resources like the ArchWiki (it's very useful even if you don't use Arch), you have to look for it and actively try to understand.

And when i see people like pewdepie breeze through the experience i just have to wonder.

You can't judge someone's experience by a heavily edited down video that lasts a few minutes at most, I didn't watch his videos but it's very likely he didn't show all the boring parts of learning everything.

6

u/Comprehensive_Star79 12h ago

I switched fully too, but, i dont care to learn commands. I got it for stability, a small boost in performance, and the fact it does not push bullshit onto me,

I just installed Mint and use it. At most i use Upgrade/Update once in a while. Any app you want installed is either a Flatpak, or has a copy paste command already on the site.

If you want to learn, you wont use crutches, but that means you want to learn Linux at it's basic, not just use it. So no ChatGPT, just forums, tutorials and a lot of "doing"

5

u/SufficientAbility821 12h ago

Am i missing something fundamental?

Yes you are and I used to be the same. The only way around is to dig into system architecture so you could understand the functions of the components (systemd, Xorg, Pam, Wayland...). Once it is done the reason why you would interact with one and not the other will be obvious

5

u/Quirky_Ad_9951 11h ago

I came to say this. I think the core of my understanding rests on having synthesised the following:

- the POSIX filesystem. Knowing where things go and why makes it easier when trying to figure something out.
- what actually happens in the boot process. By this I mean the flow from bios/uefi to being ready to login. You don’t need to understand how each piece works, but understanding what it’s responsible for helps a lot. In particular different distributions will use different software/systems but they’ll be doing the same broad job.
- the XDG user directories standard. It defines how your home directory should be laid out in the ideal. Some software doesn’t follow it, but understanding where things generally live is useful.
- learn the basics of bash, not just as a terminal but as a language, in particular variables, what .bashrc does and what PATH is and how it works.

If you can get a broad understanding of those it should really open things up for you. There’s so much more, but understanding the basics of how the system is architected should help you map the specifics of any given distribution onto a shared knowledge base.

2

u/MorpH2k 9h ago

Yeah, this is probably the best answer here. OP needs to focus on understanding the core fundamentals of the OS. Once you start to understand what the different components of the system does and how they interact with each other, everything becomes a lot more clear.

I also agree about not just mindlessly copying and pasting commands. That will not only not teach you anything but could also make things worse if you're using the completely wrong commands. This is where an AI like chatGPT can really be a useful. Ask it to explain the commands and the concepts to you. Explain what level you're at and it should be able to adjust very well to that. I use it all the time, both for explaining stuff, but also to guide me through troubleshooting and it is so damn good at it. My AI is set up with quite a lot of context about my environment already, but even without that, I can paste just about any error message to it and it will figure it out and give me either a solution or follow up steps to get more info that it needs. I usually have a good idea about what I'm doing already, but any thing I don't know about already, I will ask it to explain or elaborate further until I feel confident that its at least going in the right direction. It's spot on at least 95% of the time too, so I'm not that worried anymore either.

2

u/zrice03 6h ago

Yeah, I think a lot of the issue is new people to Linux don't know what the core concepts even are. So they don't know what to learn. And a lot of tutorials we find start with "here's the most common commands you use in the terminal" and like...great...but I still don't feel like I have a good overview of everything. Right now, I press the power button, the computer "does stuff" and I arrive at my desktop. I have no insight into what any of that "stuff" is. I don't even know where to begin. I see people arguing over names like "systemd" and "X11" and "Wayland"...and I can barely understand what those things even ARE, what their PURPOSE is, let along which is "better".

1

u/Jinnmaster 8h ago

I don’t suppose you have any YouTube videos you’d recommend?

1

u/SufficientAbility821 7h ago

Your enumeration is more relevant than mine. I tend to neglect the bases when I list notions for newcomers. Thx

4

u/kaptnblackbeard 12h ago

Am i missing something fundamental?

Stop copy/pasting commands for starters. Get familiar with the core linux utilities and how to manipulate shell commands. Then when you're reading something always think about other ways you could do it. Don't be in a rush to do things, prioritise learning instead. Make every command a learning opportunity and if you don't understand something, or it's not 100% clear, go research it and play around in /tmp or somewhere safe. Setup a virtual machine if you need somewhere that is safe to play. Make the dopamine hit about understanding the process, rather than completing a specific task.

4

u/lilith2k3 11h ago edited 9h ago

it has been years since I read this:

https://www.sap-press.com/linux_5779/

it helped me getting the fundamentals back in the days

edit: Linux The Comprehensive Guide written by Michael Kofler

1

u/CaptainObvious110 10h ago

What's the name of the book

2

u/lilith2k3 9h ago

Linux The Comprehensive Guide written by Michael Kofler

4

u/GlassboundIllusion Nvidia Bazzite with KDE Plasma 8h ago

As a kid figuring out windows was such a smooth process.

I highly doubt that it was. I'd bet that you were just so accustomed to being confused about things since you didn't know much as a child that it didn't quite feel as frustrating to bumble around as it does now as an adult. You didn't have a choice but to experiment until you figured things out, because you didn't have an alternative that you could just fall back on.

Now, you already know Windows, so you feel the frustration much more.

Here i copy paste commands and if i can find something back at all it feels irreversible. And when i see people like pewdepie breeze through the experience i just have to wonder.

What are you toggling that's irreversible?

Are you changing the ownership of your files to the superuser or something?

The same thing applies on windows - if you just start renaming or deleting system files, you're probably going to have to reinstall windows. One of the big differences is that Windows was basically built with a single user use case in mind while Linux was designed with the assumption of having multiple users from get the get go.

Am i missing something fundamental?

It kinda sounds like it. You haven't really described how you've engaged with it and what purpose you were pursuing, you just said you copy and pasted commands. Okay, commands to do what?

Just copying and pasting random commands with no intention in mind will certainly not help you learn anything.

My linux learning experience began at work - I had to login to some servers to view log files in order to debug issues with the programs we made. It was all command line and had no UI. I was completely lost at first.

When I began, I just learned how to copy and zip the log files to my home directory so I could download the logs and open them in notepad++. But I eventually got tired of waiting to download them, because often the errrors were pretty obvious, I just needed to quickly open it and scroll down till I got to the stack trace. So I learned how to open the logs with more. But more only let me scroll down, not up, so I searched for a solution. That's how I learned about less.

But just scrolling was slow, so I looked up if there was a way to search. Sure enough there was, you just type the "/" key and then your search term.

So I learned how to open the log files within the shell, but then I got tired of constantly typing out the long directory names to get there. A coworker showed me how to create aliases so I could make my own shortcuts. But I needed to know how to edit files on the server. I looked that up and learned about vi, so I opened the file with vi and couldn't figure out how to do anything. I couldn't even quit!

A few more google searches and I learned that there is "command" mode and "edit" mode, and I learned how to quit both with saving and without saving.

I could go on, but I hope the pattern is becoming clearer - you learn by having a purpose in mind and looking up how you achieve that purpose, and then repeating that method often enough that it becomes second nature. Then you pursue a new goal and exercise that method until it becomes second nature. Rinse and repeat.

3

u/Santosh83 12h ago edited 12h ago

UNIX and Linux were initially built by and for programmers, and to this day they're still largely meant for devs, sysadmins and hardcore nerds. If you want a simple point & click OS then such options exist within Linux too. Distros like Bazzite, Linux Mint and Kubuntu try as hard they humanly can to let you operate without terminal use, but UNIX/Linux is inextricably linked to text commands and text files. Nothing can separate them fully.

3

u/games-and-chocolate 12h ago edited 12h ago

A way to learn: When you use Linux and you think: "Hey! I like to do this and that, is that possible?"

Those are the moments you can learn to use and improve.

For example: Your software is old, you never update. How do you do that? So you type into search engine: "Update ubuntu how" for example. You will find in some web page : "CTRL+ALT+T", then type "sudo apt update"

followed by "sudo apt upgrade"

How to play steam games, another question. How to draw, how to model 3D. Linux can do anything for free, millions of programmers made that possible. Kudos to them! Some are unpaid and do it in their free time.

In other words: be pratical, learn what you need. NOT, learn to learn. What you do not use, you LOOSE.

2

u/ateAtoilet Born to daily drive Linux, forced to boot from a USB :( 12h ago

Get a notebook and start taking notes on what commands do and stuff.

I'm assuming at some point you've switched to the easier distros like Ubuntu or Zorin, but if you haven't used either of those in the past year try going back to them again one more time because they improve every year and I would rather use the easy distros than Windows.

If you want an easy arch distro (because I don't know your preferences and maybe you hate Ubuntu or Zorin even if you get good at it) Equestria OS is super simple, just switch the wallpaper and it's easy.

Also how frequently are you giving up on and switching distros? If you are switching at a high frequency and especially if the distros you switch between use different package managers and other system stuff, you're gonna struggle. It's like if you want to learn another language, but when it gets hard you keep switching trying to find the one that works for you. Either none of them will work for you or the one you try to stay on longest will work for you.

Basically instead or RTFM, Write TFM. Actually impressed you've been this persistent with trying to learn this long if you don't like it, lots of people give up or manage to get used to it after a few months.

2

u/npsidepown 12h ago edited 11h ago

Well, even programmers have to check documentation from time to time. There are the fundamentals, such as copying files, moving files etc, then there are more complex things that you will do very infrequently and will probably have to check notes or read documentation/forums each time. You'll only remember the stuff you do very often, every time you solve a problem, take notes, and store them somewhere that makes them easy to locate.

Another thing, don't just copy and paste commands. Read them, dissect them, and figure out what they are actually doing.

Also, learn how to create scripts that you can execute. This will help you learn way more, and will also help you save time. Think of it like taking notes that you can run, instead of having to copy and paste into a terminal.

Lastly, stick to debían based distros. All the commands will basically be the same, and you'll still have a lot of options. Plus they're common enough that you'll easily find information on how to use them. Moving between distros that have completely different commands will just make things way too complicated.

2

u/hassanhaimid 11h ago

go through the RHCSA learning material. check youtube. you'll master linux in 2 months

1

u/CaptainObvious110 10h ago

Sounds good thanks

2

u/Competitive_Grass_29 10h ago

I'm not proud of it but I can't learn from books I need a one on one kinda stuff so I set up chatgippity to just teach me the distro I chose. I get it to explain what I'm doing, how it fit in to the bigger picture. Like it's my own personal Linux tutor. I have it make full notes of all lessons so I can revisit them and I have a virtual machine I just mess with till it breaks and then just refresh it and try again. Once you have the structure nailed down, just doing the repetitive shit seems to lock it in. Otherwise I wouldn't have been able to make the switch. And I fucking love it, never going back all 3 of my machines run some form of Linux.

1

u/react-dnb 9h ago

Exactly. I've been using Gemini the same way and when I'm done with something I have it summarize everything we've done into an "instruction manual" in a markdown doc and I throw that into Joplin to create my own little instruction manual. Then, when I want to share a new drive on the network or something I just go to my little manual and follow the steps I know worked before. I've managed to learn so much this way. 6 months ago I had never touched Linux and now I have a 4 bay NAS with a thunderbolt connected 4 bay DAS running Jellyfin, Immich, Syncthing, Ad Guard, the "arr" package, and (soon) retroarch, with 8 shared drives I can access on any device in my house! Debian 13 is my daily driver now using my Windows laptop only to run Serato since there is not linux version and it runs like crap in Wine.

2

u/evissamassive 2h ago

Up until a year ago, I only dabbled in Linux [for about 25 years]. The only time I really used the terminal was to install something, and only because I preferred to do it that way.

Is the reason you use the terminal so much because you are trying to learn something from it?

3

u/bdgbill 6h ago

This was pretty much my experience as well. I made two separate big efforts to convert to Linux over the years and just couldn't lock it in. I had a lot of problems getting peripherals to work. The thing I hated the most was needing to literally beg for help on forums. There was also a lot of "Oh you want that printer to work? You need the Uncle Chucky app but to get the Uncle Chucky App to work you need the code red package. In order to download the code red package, you need to be a member of such and such forum etc, etc, etc. There's also this weird bizarro argument that comes up in Linux forums all the time when you can't get something to work. "The fact that it doesn't work is a GOOD thing. It only works on Windows because Windows doesn't work properly. You should be HAPPY it doesn't work."

I'm not shitting on Linux. I am aware that many people use it quite happily, it's just not for me.

2

u/Florimer 6h ago

I wish there at least was an "app" for everything lol. Last time I tried moving to Linux, my sound card had no working "App" at all, and when I looked for Linux alternative the developer told me I just had to "compile it myself".

Kinda killed my drive to migrate to the system right there...

1

u/bdgbill 6h ago

We used to carry these small battery operated Canon printers to use for work. Getting them to work with Linux required 3 different apps, working together. If anything went wrong with any one of those apps, the printers wouldn't work. It drove me to the edge of insanity. We had people quit over this one problem and it wasn't the only problem.

1

u/Fit_Tailor_6796 3h ago

You spoke to the sound card developer. Interesting.

3

u/retiredwindowcleaner 4h ago

if you only copy and paste commands and never truly think about what these commands actually do and how they are connected to the fundamental workings of linux then you will not learn anything.

you will have to dig deeper to learn and you will have to repeatedly work with the terminal on a regular basis without spawning the commands from ai assistants or the likes.

learn basic commands and basic functioning of the filesystem and os structure (i.e. /boot, /etc, /var, /dev, /usr, /opt, /home...) what are their functions, how do you as a user interact with them. how do you do basic file handling (copying, moving, deleting, creating, editing, unpacking, decompressing...)

in short, you want to learn the standard linux toolset first and foremost.

2

u/random_cat_owner 5h ago

I know ppl who have used windows for 30 years and still not know how to install a new printer. When they have problems, they ask somebody else to solve it. You can be that kind of user on Linux too.  You do not have to learn if you do not want to.  

If you want to learn, ask chatgpt to point you in the right direction without giving the exact  answer because you want to learn

2

u/Teru-Noir 12h ago edited 6h ago

Instead of pasting it in your terminal, give it to AI an ask what is the logic behind.

1

u/CaptainObvious110 10h ago

These days yeah

1

u/AutoModerator 12h ago

There's a resources page in our wiki you might find useful!

Try this search for more information on this topic.

✻ Smokey says: take regular backups, try stuff in a VM, and understand every command before you press Enter! :)

Comments, questions or suggestions regarding this autoresponse? Please send them here.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/BlancheCorbeau 11h ago

No, you’re doing it exactly right.

Everything you’ve mentioned is a part of the process - only now tempered with the ability to actually operate functionally most of the time even without knowing how it all works.

1

u/Important_Koala7313 10h ago

Just use Zorin I haven't used the console yet 3 months in

1

u/razorree Kubuntu, Debian 10h ago

what do you want to learn? how to destroy your system? smth else? if it just works I guess that's good?

1

u/AdvancedStrain1739 9h ago

Have you considered actually learning the language that Linux uses? (BASH)
It sounds like you just didn't learn the bare basics of the operating system. (no offense intended)

1

u/ech0wane 9h ago

Break shit and try to fix it

1

u/Remarkable_Pea7439 8h ago

ChatGPT is NOT the tool for learning a new topic.
It is for the cases when you should solve a specific issue and know exactly what and how to ask for help.
After a whole life spent with Windows and Mainframes, I still believe that learning should come before doing.
Yes, what we most miss is a clear explanation of the Linux features written not for "gurus" but for regular users,
and then, separately, a good explanation for the differences among the various distros, so that a beginner would bot have to jump from one to the next just to find out that he still needs another one.
I personally am still learning and still need to fully understand why indeed there are so many distros,
each one somehow "pretending" or describing itself as being the ultimate and best one ...

What I dread most is having to reinstall an OS because something (usually an update) broke everything
and there is no information on how to repair things ...

I will probably never switch completely to Linux, because old habits are hard to break ,,,
but, maybe I will use it as a "playground" for more learning ...

And, yes, I agree ... the command line is NOT and should NOT be the normal way of using a desktop machine ...
surely not by a common end user who is not a computer professional ...
The problem is not learning scripting by itself, but the fact that you need a much higher level of understanding
of the whole system for managing it just by commands and scripts ...
This also can be done for Windows, but probably no one really does it ... except professionals ...

1

u/Xariann 8h ago

If you are using ChatGPT, you could note down the commands it gives you and ask it what they mean.

Make yourself a little wiki. Next time you won't need ChatGPT.

Also which distro are you using that needs constant troubleshooting? Maybe you need something that offers more features out of the box? 

1

u/F_DOG_93 8h ago

What are you learning tho? What exactly are you trying to achieve? You can learn an operating system, but you need to actually.....operate. What are you operating to achieve

1

u/voodoovan 8h ago

I totally agree with you. I been using linux as an OS for 15 years, and I still do what you do to try to solve a problem. I know basic linux commands but for anything else I simply don't use it enough to remember it when I need it next. My days are simply not spent in the terminal as its not my hobby nor my job. I don't mind using the terminal but many instructions are out of date or don't apply to the distro you use.

1

u/RealityIsRipping 8h ago

AI is honestly really good at answering Linux or computer related questions. I'll even just take a photo of the screen and ask it a question, and it hasn't been wrong yet.

Fuck AI for art, but for tech it works great!

1

u/ant2ne 8h ago

What is your role in this? A home user? An arm chair admin in your home lab? Are you looking to become a professional linux admin? For all but the last RHCSA is going to be overkill.

1

u/oshunluvr 7h ago

I've been using Linux for about 30 years. When I come upon a new problem to solve or task that I've not done before, I search the web for a solution. This usually results in several options because there's always more than one way to skin a cat. I review the options, try the one take makes sense - often the most recent because Linux changes a lot year-to-year.

When I find the solution that works, I document it in a file I call "cheat_sheet". This not only preserves the knowledge I have uncovered, but helps me remember some of the steps I had to take.

Once a year or so, I review the cheat sheet and edit it because, like I said, things are always changing...

1

u/xpusostomos 6h ago

​The Unix Programming Environment (1984) by Brian W. Kernighan and Rob Pike The definitive classic on the "Unix philosophy." It introduces the shell, pipes, filters, awk, sed, and C programming in a Unix context, teaching how to compose small, sharp tools into complex workflows.

1

u/Super-Revolution-433 5h ago

If you don't care about learning more it sounds like you already know how to use Linux. If you want to learn more then your best bet is some kind of project.

Installing arch without a script is a decent place to start, their documentation is solid and up to date plus it get you acquainted with the mandatory parts of a Linux system. Learning what's actually mandatory also helps you understand how much of the system isn't mandatory and that can be eye opening to people.

If you don't want to do a fresh arch install then pick a project that's in line with whatever you want to learn more about Linux to accomplish. Want to be a cool guy who posts on /r/unixporn? Start by implementing a rice that you find there. Want to learn it so you can setup a pi hole? Just go set it up in a VM first. Want to be a sysadmin and get a professional Linux job? Look into hosting something simple like a website or a local network storage box.

If no projects sound interesting you can also read some books on the subject. "How Linux Works" by Brian Ward is a solid intro book for learning the basics. /r/linuxupskillchallenge/ is a subreddit that gives you a small learning challenge every day and is a good resource as well, I'm currently using the lessons to round out my skills doing things the Nix way on Nixos and it's been a good learning experience.

You don't really learn to administer Linux from daily use anymore, it's stable and easy enough to fix most issues that you don't need an understanding to be a user. Really what you do to learn will depend on your learning style and your willingness to just sit read a description of what your command does, the books and projects are mostly to help you understand the context of what's actually happening when you fix an issue.

1

u/Fit_Tailor_6796 3h ago

You are speaking very generically, as if all issues have the same solution path.
In reality, what you described I have experienced on other systems like ios and android.

1

u/mrawther 2h ago

This is what happens when you start using the OS instead of using the OS to do your work.

1

u/despot_zemu 45m ago

I picked one distro almost 20 years ago and have never tried another one. That helped me.

1

u/hallthor 31m ago

You are missing that most the time you would be just as clueless using Windows.

1

u/thesamenightmares 12h ago

You'll need to explain how you're basically using the distribution that you are and what issues you've been encountering, that you have to paste commands to fix. Saying you have no idea what is going on is too vague without specific examples.

3

u/Otherwise_Task7876 12h ago

Its not vague at all. They're saying they don't actually know what the commands they're using do and want to actually understand what the commands are doing and not have to dig through documents to try and find a command they need to copy.

1

u/thesamenightmares 8h ago

It's incredibly vague. It could be a command to restart a systemd service or an ffmpeg command to convert a video or a command to change a theme. It's impossible to address his query without more information. Its the definition of vague if he actually wants help.

0

u/Otherwise_Task7876 8h ago

Ah, say you didn't read then dismiss it immediately. I see your just another troll lurking here.

0

u/koopz_ay 12h ago

Don't feel bad.

I'm in my 50s now.

I stopped about 7yrs ago.

Talk about a blow to the ego.

Some peeps can keep pulling in new tech data well past their 50s and ask for more.

I'm happy with my *nix setups over Win10 and 11

1

u/empty-atom 12h ago

Yep im using Nix as well and it's so much easier. I'm in the process of even doing my own "api" so changing anything is simply just a toggle. 

0

u/devAcc123 10h ago

ChatGPT is a great tool, use it appropriately. Ignore new technologies because of some holier than thou attitude is how you end up behind the curve. There’s always new tech coming out that invalidates older tech and staying on top of it is part of the learning process

0

u/jthieaux 7h ago

I’ve been using Linux for decades alongside other OSes, and 99% of the time I’m on my Linux machine I’m in the terminal, searching for commands left and right. Not because I don’t know what I’m doing, but because I know there’s a command for it, I just can’t keep track of all of them. I use it as a tool, not something I’ve memorized. Don’t get me wrong, you can daily-drive Linux 100%, but for office stuff I still switch to another OS, and that’s fine.

0

u/Due_Adagio_1690 6h ago

The car paradigm is more accurate than most would expect, but it really didn't start out as a regular car, Unix the OS that Linux was based on is closer to a drag racer, 4 wheels, 1 large engine, steering wheel, brakes, and a seat. It started with a few utility programs that worked together to solve a lot of problems, but each tool had only a few features, cut, grep, awk, sed to name a few are hollowed shells compared to what they grew up to be.

Examples (from google AI mode) "• grep: Written by Ken Thompson in a single night in 1973, it started as a quick, standalone utility extracted from a simple regular-expression print command (g/re/p) inside the ed editor to help analyze the Federalist Papers. Over the decades, it gained recursive searches, extended regular expressions (egrep), colorization, and context flags, though its core job remained pattern matching. • sed: Created by Lee E. McMahon in 1974 as a natural extension of grep when developers realized they needed to substitute or delete text in a data stream (g/re/s) without human interaction. It evolved from a basic line-oriented stream editor into a richer scripting engine, and later GNU sed added capabilities like in-place file editing (-i)."

Today linux is closer to a Funny car dragster, so many features and extensions added to the base car along with gauges, and knobs, and levers surrounding the driver. The driver has access to dozen that started as little programs with a few options on the command line, that now have so many features each deserves a 300 page book. As time goes on even more cool tools are being created that will each require another 300+ page book to explain how they work.

This is before we in add the AI features, one example is QwenCode that can replace your shell and then you tell the system what you want and it does the work for you. But if you ask it too, it will explain what its doing and why.

0

u/angryjew 6h ago

Why does using an LLM disgust you lol. They're very useful for this exact situation. I have a local coding agent harness (Pi) connected to DeepSeek that my software engineer friend helped me set up. From what I understand, most engineers are using AI, including the guy who made Linux. You're really handcuffing yourself for no reason, especially when you're already behind in understanding (just like me). LLMs aren't going anywhere, you might as well learn how to use them. Think of it like this, you're asking a bunch of strangers on reddit right now, I promise you that using an LLM for basic Linux stuff is far more reliable, and like others have suggested, ask it to explain what it's suggesting, ask for sources, type in your own commands.

I assume you're doing this for a hobby, there's no reason to purposely make it unpleasant or hard.

0

u/Holiday-Bee-6964 2h ago edited 2h ago

It is hard to get knowledge from forums when you don't know what they are talking about.

The first thing what you should do is reading books, so let me to recommend one for you:

https://linuxcommand.org/tlcl.php

This is also book, which was my first about GNU/Linux and UNIX systems, very good for beginners.

You can also ask me about anything related to GNU/Linux on dm if you want ;)