“Anyway, here are terminal commands you don’t understand.” and after asking for clarification on said terminal commands, you are quite rudely told to read The Manual - which seems to be some kind of a holy book for these bizarre creatures - without explaining in any way whatsoever which part of which manual you should be “reading”. Thankfully, only every command ever created by anyone since the very conception of these systems - which was some 50 years ago in the seventies, in a university of a country you don’t live in, written in a language you don’t possibly even understand all that well, possibly by someone who also didn’t know the language all that well - is discussed at length and in an impenetrably obtuse manner by many different parts of many different manuals, with helpful references to other commands and concepts you also don’t understand, but which are all varying levels of essential knowledge for understanding some of these commands, while different levels for others. Also if you do not grasp the essential knowledge, you might completely fuck up your system. It seems that the philosophy in playing Dwarf Fortress is found in trying to use certain types of Linux distros, mostly frequented by massive nerds with hugely inflated egos: losing is fun! Because why else would I still be using Arch (btw)?
But in any case: Read the Fucking Manual (rtfm to you as well, brother)
There is a manual pre-installed on your machine for most commands available. You just type man and the name of the thing you want the manual for. Many commands also have a --help option that will give you a list of basic options.
I should point out this isn’t Linux specific either. Many of these commands come from Unix or from other systems entirely. macOS has a similar command line system actually. It’s more that Linux users tend to use and recommend the command line more. Normally because it’s the way of doing things that works across the largest number of distributions and setups, but also because lots of technical users prefer command line anyway. Hence why people complain about Windows command lines being annoying. I say command lines because they actually have two of them for some odd reason. Anyway I hope this helped explain why things are the way they are.
Indeed, well explained. Though I think I should mention that I’ve been using Linux in general for some 12-13 years, since from somewhere around Ubuntu 12.04 to 13.10. I did make the error of overestimating my own skills and abilities regarding “figuring it out” when I dove headfirst into Arch, so basically I was a self-proclaimed massive nerd, but I didn’t even realize how inflated my own ego was. I don’t think the archinstall script/library even existed back then, and I also had no clue about the man-pages, or how anything really worked.
So my comment here was more along the lines of embellished musings on my own past experiences trying to learn things while I was doing them. Through these experiences what I have learned though is that the Arch Wiki is an invaluable source for most Linux users.
“Anyway, here are terminal commands you don’t understand.” and after asking for clarification on said terminal commands, you are quite rudely told to read The Manual - which seems to be some kind of a holy book for these bizarre creatures - without explaining in any way whatsoever which part of which manual you should be “reading”. Thankfully, only every command ever created by anyone since the very conception of these systems - which was some 50 years ago in the seventies, in a university of a country you don’t live in, written in a language you don’t possibly even understand all that well, possibly by someone who also didn’t know the language all that well - is discussed at length and in an impenetrably obtuse manner by many different parts of many different manuals, with helpful references to other commands and concepts you also don’t understand, but which are all varying levels of essential knowledge for understanding some of these commands, while different levels for others. Also if you do not grasp the essential knowledge, you might completely fuck up your system. It seems that the philosophy in playing Dwarf Fortress is found in trying to use certain types of Linux distros, mostly frequented by massive nerds with hugely inflated egos: losing is fun! Because why else would I still be using Arch (btw)? But in any case: Read the Fucking Manual (rtfm to you as well, brother)
There is a manual pre-installed on your machine for most commands available. You just type man and the name of the thing you want the manual for. Many commands also have a --help option that will give you a list of basic options.
I should point out this isn’t Linux specific either. Many of these commands come from Unix or from other systems entirely. macOS has a similar command line system actually. It’s more that Linux users tend to use and recommend the command line more. Normally because it’s the way of doing things that works across the largest number of distributions and setups, but also because lots of technical users prefer command line anyway. Hence why people complain about Windows command lines being annoying. I say command lines because they actually have two of them for some odd reason. Anyway I hope this helped explain why things are the way they are.
I’ve been using linux for ~17 years or so and I just realized the other day that there can be multiple “pages” in a manual
No, I don’t want to talk about it
Indeed, well explained. Though I think I should mention that I’ve been using Linux in general for some 12-13 years, since from somewhere around Ubuntu 12.04 to 13.10. I did make the error of overestimating my own skills and abilities regarding “figuring it out” when I dove headfirst into Arch, so basically I was a self-proclaimed massive nerd, but I didn’t even realize how inflated my own ego was. I don’t think the archinstall script/library even existed back then, and I also had no clue about the man-pages, or how anything really worked.
So my comment here was more along the lines of embellished musings on my own past experiences trying to learn things while I was doing them. Through these experiences what I have learned though is that the Arch Wiki is an invaluable source for most Linux users.