Linux

48878 readers

1232 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

160

Tips for getting better at Linux. (lemmy.ml)

submitted 1 week ago* (last edited 1 week ago) by pineapple@lemmy.ml to c/linux@lemmy.ml

115 comments fedilink hide all child comments

I am a Linux beginner/amateur and I have sort of had enough of copy and pasting commands I find on the internet without having a good understanding of how they actually work.

I guess my end goal is to be able to comfortably install and use arch Linux with my own customization's and be able to fix it when things go wrong.

What tips/ideas do you have for getting better at navigating the terminal, and getting a better understanding of how the os works. What is a good roadmap to follow? And how did you, advanced Linux user, get to the stage your at now?

Edit: my current distro is bazzite just in case you were interested and thanks for all the replies you are all really helpful.

you are viewing a single comment's thread
view the rest of the comments

[–] boredsquirrel@slrpnk.net 1 points 1 week ago (1 children)

As I said. Fish can just be a shell. I only write bash scripts. All bash scripts have #!/bin/bash at the beginning so it doesnt matter.

I dont know about fish errors. If something doesnt work, I enter bash and then run it again. I enter exit when I am done.

That does happen but the workaround is easy

Apart from that, instant suggestions, history, arguments and available commands already help a lot.

[–] thingsiplay@beehaw.org 1 points 1 week ago (1 children)

Fish can just be a shell. I only write bash scripts.

That's the exact problem. You deal with two languages. I did that too BTW. Now for someone who is experienced, its fine. But for someone who just started learning about Linux and scripting, its not ideal, as it adds unnecessary complications and friction for a learning process that is already complicated. Because learning Bash is a must do in my opinion. Regardless what custom shell you use.

After that learning process and getting familiar, one still can decide to use Fish as the interactive shell. But that's AFTER the initial learning process of the basics of Linux.

[–] boredsquirrel@slrpnk.net 1 points 1 week ago

I dont get why you shouldnt use fish to run your daily commands, and bash for the scripts. I rarely do anything fancy in the terminal that would be bash specific.