this post was submitted on 20 Jun 2025
30 points (82.6% liked)

Linux

12380 readers
24 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.

top 21 comments
sorted by: hot top controversial new old
[–] Novocirab@feddit.org 21 points 1 month ago* (last edited 1 month ago) (2 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.)

[–] mhzawadi@lemmy.horwood.cloud 5 points 1 month ago

You don't need to pipe in to grep, use a / to search it.

Man ps

/user enter

Then use n to find the next instance of the search

[–] bridgeenjoyer@sh.itjust.works 2 points 1 month ago (1 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

[–] toynbee@lemmy.world 1 points 1 month ago (1 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/

[–] HayadSont@discuss.online 2 points 1 month 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

[–] toynbee@lemmy.world 2 points 1 month ago (1 children)

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

[–] HayadSont@discuss.online 1 points 1 month 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*.

[–] toynbee@lemmy.world 1 points 1 month 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.

[–] Flamekebab@piefed.social 14 points 1 month ago (1 children)

Sounds like me trying to do stuff in Windows these days.

I don't like man pages though - it's very rare for me to find their content useful as they always seem to be written for a skill level way above mine.

...and I've been using Linux since 2005.

[–] rhadamanth_nemes@lemmy.world 4 points 1 month ago

Man can be a bit arcane, but they generally have the keys to the kingdom.

Admittedly, I have years of experience, but still.

[–] Quazatron@lemmy.world 10 points 1 month ago

I bet that if I switched today from Linux to MacOS I'd feel the same.

In fact, I sometimes feel the same when dealing with Windows, but mostly I just reboot and hope for the best, or bother the IT guys some more.

[–] cronenthal@discuss.tchncs.de 10 points 1 month ago

What I found was that once everything was set up I just started using my software. The system gently faded into the background and things just work. Every so often I need to figure out something new, but that occurs only every few weeks. At that interval I actually enjoy the learning experience.

[–] TonyTonyChopper@mander.xyz 7 points 1 month ago* (last edited 1 month ago)

I've been on Kubuntu daily for 6 months and feel very comfortable using my pc. I think 2 months working with any software is still "beginner" territory, let alone something as complicated as an OS. You need to search for everything since you're still doing things for the first time every day.

In my opinion it isn't a bad thing to search for help, it's actually incredibly efficient. You would spend 10 times as long to figure out how to do anything on your own. Like if you were baking a cake, you don't just go straight to the kitchen and mix stuff together. You open the cookbook.

Deb files are only used for programs that aren't packaged for your distribution. The vast majority of programs are a single command to install. Or you probably don't even need to do that, just open the Software Center, search the program, and install it there.

For most actions there are GUI alternatives to commands. Like copying folders, editing text files, changing settings. You don't need to open the terminal that often.

[–] jlow@discuss.tchncs.de 7 points 1 month ago

Yeah, I feel you but I think that's just learning something new that is pretty complex. I've had decades on Windoge and MacOS (and a lot of software only available on those platforms) and then switching to Linux and FOSS apps is obvioisly a huge learning curve.

[–] ryannathans@aussie.zone 3 points 1 month ago (2 children)

Don't copy and paste, learn each command and argument as you type them. Read the manual

[–] bridgeenjoyer@sh.itjust.works 2 points 1 month ago

This has helped. I've been at least typing them out instead of copying and trying to understand each argument. At worst ill forget it but at least I worked my brain muscle a bit!

[–] mhzawadi@lemmy.horwood.cloud 1 points 1 month ago

Also learn to search man pages, you might get a wall of text. But a search will jump you to what your looking for

man is just less

[–] the_abecedarian@piefed.social 2 points 1 month ago (2 children)

What kinds of beginner guides do you think would have helped you get most things done? (genuine question - trying to help documentation writers understand new user issues)

[–] HayadSont@discuss.online 3 points 1 month ago

Not OP, but when I cold turkey switched to Fedora Silverblue over three years ago, I benefited a lot from this guide.

[–] bridgeenjoyer@sh.itjust.works 2 points 1 month ago (1 children)

A big one I've struggled with and had to keep researching is the file system. It seems insanely complex when you are used to windows file system and where shit is installed. Also the inability to install programs on drives other than your boot drive is a huge downside to me.

One example, I moved a lot of my games over to my linux drive, but some save files didn't move. To find where the save files from linux were, I had to dig and dig through a ton of folders to find it. In windows, it would have simply been in the game folder under saves.

[–] the_abecedarian@piefed.social 3 points 1 month ago

Yeah the way the file system works is of the big differences from windows. That can def be a point of frustration.

There are linux approaches to having your /boot, /root, /usr on another partition or drive. It's been common to separate them for a good while and in fact many or most linux installers ask where you want each of them to live (might be in advanced settings).

It takes time to learn a new system. Keep going!