I didn’t realize this community existed and posted my other thread about linux distros in another community, so I’ll try rectifying that here.

I’m trying to learn as much about linux as a desktop system as I can before I dive in to installing a distro on my computer. I do have a tiny bit of familiarity with the terminal from having servers running Debian, but those I get a lot of help with. the distro I’ve chosen is Bazzite, which is based(?) on Fedora if I recall right. I liked the stuff it comes with (I love video games) built in and I like the idea of the atomic desktop setup.

so, what are your tips and tricks for a new linux user? what about outside resources? I’ve been doing as much digging for articles and videos as I can, but I thought asking the community might be a good idea too. I’m trying to compile these resources for myself and my partner, so that we have stuff to learn from and reference.

as a final question, what got you into using linux over windows or mac?

thanks in advance!

  • Korthrun@lemmy.sdf.orgEnglish
    3·
    6 months ago

    You’re absolutely right. For what it’s worth, it’s just the first part that’s important.

    When you pick up a new concept from a “resource” such as a tutorial, take a minute to explore the concept and understand the semantics of what you’re doing. In the name of illustrating a concept tutorials can often be misleading in subtle ways.

    An explanation of my “useless use of cat” example:

    The command line has a concept called “piping”. This lets one command send output to a second command. It’s very handy. There is usually also a “cat” command, which will read a file and send the contents where you tell it. This is often your screen, or through a “pipe” to a second command. There is also a “grep” command that lets you search data for certain words.

    Many “linux newbie” tutorials combine these tools to show how “piping” lets you send data from one command to another. “cat” some text file, then “pipe” the output to “grep” to search for your words. It usually looks something like cat ./my_address_book.txt | grep Giles to find lines in “./my_address_book.txt” that contain the word “Giles”. The thing is that “grep” can take a file name as an argument. You can just do grep Giles ./my_address_book.txt, and cat is for concatenating files into one. If you want to simply read a file there are more appropriate tools such as “less”. This by the way is the “useless use of cat”

    When you’re a newbie though, it may be the first time you’re seeing either “grep” or “cat”. The tutorial is just trying to show you “pipes”. Along the way you’re picking up these “bad habits”. I’ve met professional sysadmins who didn’t know grep took a filename as an argument. It was always “cat blah | grep my_search”. I will see people type “cat /some/file | less” instead of “less /some/file”. It shows a lack of understanding of what these tools actually do, and IMO it just comes down to regurgitating tutorial actions without bothering to understand the semantics of what you’re being shown.

    • Prison Mike@links.hackliberty.org
      2·
      6 months ago

      Not related to your point, but I always felt like piping from cat to grep is crazy inefficient. I’m a programmer so I imagine grep is much more efficient at finding stuff in files (in chunks maybe?) whereas cat likely reads the entire thing into memory (somehow less efficiently) to send it through the pipe.

      …though now I’m wondering if my understanding is off.

      • Laser@feddit.de
        2·
        6 months ago

        I don’t think that’s what’s happening. There’s no hard requirement for cat to read everything straight into memory. It can send data once it’s available, and the receiving process can read it as fast as it wants. There are cases where this might be more clear: Let’s say you have a big video file that you want to convert to something that only supports like y4m input and is not in ffmpeg. A common way is something like ffmpeg -i infile -f yuv4mpegpipe - | encoder --y4m outfile - I’m pretty sure ffmpeg won’t read the whole infile into memory, nor will it store the whole y4m representation in memory. Instead, it will decode infile as necessary and push into the pipe at the speed the encoder can handle.

        But yeah, I remember something about tar using libraries for compression being more efficient that piping its output to a compressor. So it’s still the better route, but probably not as much better as you think.