this post was submitted on 20 Jun 2025
34 points (85.4% liked)

Linux

11385 readers
106 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
 

Not that I don't still love using linux daily, but it is getting a little old having to search for how to do anything even just install a simple program (recently, had a. Deb file to install unifi software that wouldn't install and had to find a custom script to do it).

I feel like there's no way I'd ever learn all the random commands I've been copying and pasting (and keeping in a text file for later) and can't help but feel it's kind of clunky. And I don't feel like I really know anything of what Im doing. Even man pages baffle me. I've been into computing for 20 years but only used linux a little like 8 years ago, but now it's been my main os on my desktops for probably 2 months. I know, maybe that's just not long enough. I just don't like the fact that if I couldn't search, I'd be completely stuck on a lot of tasks.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 21 points 3 days ago* (last edited 22 hours ago) (8 children)

A good start is to install tldr. You use it like man, but it gives you shorter explanations – or rather, a short list of illustrative examples.

As for man pages themselves (which I often find overwhelming, too), if you're not doing that already, you can pipe it into grep to extract just those lines that contain your search string:

man ps | grep user

# or for two lines of context above and below each match:
man ps | grep user -C 2 

Going further, check out Fish instead of Bash. I haven't use Fish yet, but it's said to be much better for learning Linux commands as a beginner. Later on, you may switch to Zsh. In any case, hitting Tab once or twice will often give you a list of possible completions to the command you are typing.

PS: I see no good reason why anyone should downvote this question.

Edit (June 23): As it so happens, just today I've stumbled into the O'Reilly book "Classic Shell Scripting" by Robbins and Beebe (ISBN 9780596005955). What can I say – its age notwithstanding, it's apparently an extremely good book for understanding things and learning how to solve real problems. (It presupposes some familiarity with Unix-like systems and with the shell, so if one's just starting out, the book "Learning the Unix Operating System" may be better.)

[–] [email protected] 2 points 3 days ago (5 children)

I do have tldr and fish and love it ! Although I get a little annoyed that my aliases from bash didn't carry over into fish because I sometimes forget to launch fish since I almost always use the ctrl alt t shortcut to launch term

[–] [email protected] 1 points 2 days ago (4 children)

You can change your default shell in a few ways. I've never used fish, but vipw should open your passwd file, in which you can change /bin/bash to the appropriate path for fish (which you can find via which fish). It's probably best to only change this for your user.

A possibly simpler option (and one that I don't believe requires root access) is the chsh command. I've never used it myself, so I'll let this site provide instructions for it: https://www.howtogeek.com/669835/how-to-change-your-default-shell-on-linux-with-chsh/

[–] [email protected] 2 points 2 days ago (1 children)

Article by a Red Hat engineer that also makes a ton of contributions to FOSS in their free time: Don't change your login shell, use a modern terminal emulator

[–] [email protected] 2 points 2 days ago (1 children)

Interesting, I hadn't heard that take. I'll give it a read. Thanks!

[–] [email protected] 1 points 2 days ago (1 children)

My pleasure fam! Btw, I'm in no place to dictate what's right or wrong (or whatsoever). I just wanted to add their perspective on the matter*.

[–] [email protected] 1 points 1 day ago

I don't know that I agree with the take represented in your linked article. If I'm reading it correctly, the primary reason not to switch shells is that those shells might not exist universally. That is a valid concern, but running which fish (as referenced in my original comment) should help to mitigate that risk factor. Scripts should always use a hashbang to specify their desired environment so, unless you're overriding that, it shouldn't be a concern.

I agree that you shouldn't use shells that are not available to you. I don't think that means you shouldn't try to change shells if you are unsatisfied with your current one.

load more comments (2 replies)
load more comments (2 replies)
load more comments (4 replies)