• 6 Posts
  • 439 Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle
  • Backpacks are how I learned why a lot of purse’s end up as black holes of miscellaneous shit. You think, “oh that like be handy to have just in case”, and next thing you know you’re carrying around half of a house in your backpack.

    Stealth edit: I’m bad at verb conjugation sometimes.






  • The place to start is searching “How to do x in Linux (or the name of the specific distro you’re using)?”. If you are trying to figure out how to do something with a specific program searching for “How to do x in {program} on Linux?”. I’ve been using Linux for years and still need to look up the syntax for commands or a reminder on how to do things. I would also focus on learning things that you actively need so you can apply what you learned immediately. I definitely agree with you that see what is actually installed can be a mess. There’s so many different installation methods that it’s nigh impossible to have a single unified interface. I would try to stick with one installation method as much as possible so most things are able to be listed in one spot.

    For how to apply things it’s common to feel overwhelmed with the complexity of certain tasks. It’s important to try and break that down into smaller parts. An example of something I was recently dealing with was getting SSH access from an external network setup on a server that is running NixOS. There’s so many steps to take to get that setup, but each individual step is easy to do. I broke down the problem like this:

    1. Find the server’s local IP address. Easy to pull up on the machine itself or looking at the devices connected to my router.
    2. Ping that IP address from the computer I want to SSH from.
    3. Enable the SSH daemon on the server.
      1. In my case this was just settings a variable to true, but in most cases it would be installing if via a package manager (varies depending on the distro), but I run Fedora so I would run sudo dnf install openssh openssh-server. I can find those package names by running dnf search ssh or “SSH server on fedora”.
      2. Ensure the SSH daemon is enabled and running by running sudo systemctl enable sshd and sudo systemctl start sshd
    4. Try to SSH into the server from the computer I want to use.
    5. Create some SSH keys so I can do authentication via a private key file instead of a password (much more secure, and good practice).

    I can go on, but each step I feel is simple to execute and doesn’t require knowledge from any subsequent step. As for how I know what the steps are, I am following some tutorials or docs online like this, digging through man pages, and personal experience.


  • First always take notes of the steps you took to do something. If you were throwing shit at the wall then try and do it again using only the correct steps. I have saved my own ass by taking down notes. Include the commands (obviously), what they do, why you’re using them, the expected output, and errors you came across with their solutions.

    Since you said you wanted man pages to be easier to parse, I’ll give you some advice on how to approach these, admittly, intimidating blocks of text. One skill I have learned is how to read those intimidating technical documents and actually get the information I need from them. A good practice is take a tool, a programming language, data format, etc. that you already know and look at the technical specifications. Since you already know how it works you should be able to understand the information in there, and learn how to parse out that data. RFC 2119 also gives some guidance on some of the word usage in those documents (it’s very limited), and is a nice short one to get used to reading stuff like that.

    Another thing is I just try shit out to see what happens. Would probably be a good idea to do this on a machine you don’t care about reimaging, or make a backup of all the data you care about losing. I’m a very learn by doing kind of person and have learned a lot this way

    Finally if you have the time and knowledge looking at source code can really give you an understanding of how a tool works. This is my absolute last resort, so don’t think you have to do this.

    Edit: I wrote this assuming you’re ok with getting into the nitty gritty of Linux. Otherwise I would recommend switching to a more user friendly OS. It looks like you’re trying to set it up for gaming, this is a guess and I could be wrong. I have been using Bazzite for about 6 months now, and the only times I have issues with it is when I try to do power user stuff that isn’t gaming related (e.g. trying to install a build tool to build something from source code).














  • I did some vague streaming stuff for some friends and really enjoyed playing around with OBS to get some overlays and stuff. As long as you’re getting into it cause you find it fun, I see no reason to not try it. Just keep in mind you’ll probably not make it big and this will remain what it starts as: a hobby. Don’t let others deter you from trying atuff out. Even If it’s not your thing you learned some skills and what you like/don’t like.