Linux
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:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
2 things: Experience Repetition
First of all, continue to look up how to fix things, there's no problem with that. HOWEVER, make sure you understand what the commands you are entering do. Same thing applies to Windows as well, I've seen plenty of troubleshooting posts that and with "paste these 3 lines into power shell"
The more you do this, you'll get a feel for how everything is organized. You might not know HOW to fix your issue at this point, but you will at least know where to look for logs and where to find the config files relevant to your issue. Once you've fixed enough problems, you'll start to be able to figure it out on your own. You can also help out with bug reports better now too.
You also need to do this often enough that you remember these things. I've got a bunch of Linux installations (3 desktops, 1 laptop, 4 small servers) so I get plenty of practice changing things. When I only had the 1 computer running Linux, it was a lot harder to remember everything.