>>978247
Ignore the slackbook, just play by ear.
Basic concepts that are done on LINUX:
Files with a dot at the beginning are handled by file-viewing programs as invisible. You even need to use the -a option with the "ls" program to view these which I deem pretty harmful, but there's GNU software for you.
In the vast, vast majority of distributions, the first user interface to load is a command-line program called "tty" (TeleTYpe) which basically emulates a teletype interface because yes, UNIX really is that old and traditional. Running a program mentioned later called "X" is basically analogous to running Windows on DOS, though theoretically, like Windows NT, you could skip this phase and cut tty entirely out of the picture but that's fucking stupid.
Package managers will give you pre-configured, pre-compiled programs. How do they tell that a binary package is safe? They all build it with BIG GNU's compiler and compare the hashes to make sure they're all exactly the same.
When you're compiling programs yourself, you'll usually run this local script usually called "configure" in the directory with the command "./configure" (you have to explicitly specify that it's in the current directory as adding . to your PATH is a big security hazard when you're working with a text-oriented operating system) which firstly tells you whether you actually have the requirements to install and run the program, and next basically generates another file that tells a program called "make" how to compile the program and where to put it. Run "make" next to do something I'm not actually all that clear on, and then either "make build" to put a copy of the program in the current directory to be moved manually, or "make install" if you want to run the risk of everything being put in the wrong location, according to your preference.
stdout; "Standard Output", which is the text put out by a program.
stdin; "Standard Input", the text which goes into programs, normally handed by your shell when you "pipe" the output of another program. Basically examples are:
ls . > aaaabuaaaaa.txt which puts the output of "ls ." into a (new) text file called aaaabuaaaaa.txt
echo "aaaabuaaaaa"|cowsay which, if you install the program, makes a silly cow say "aaaabuaaaaa" through the output of "echo "aaaabuaaaaa"" which is "aaaabuaaaaa".
Environment variables, which makes programs behave in different ways when they think they're simply just too clever to do something so pedestrian as read from a text file or accept options. View your current variable with "export", and add new ones with "export VARIABLEKEYINBIGCAPITALLETTERS="variable, with quotes around if there's blank spaces"".
Important programs are:
man; "Manual" which explains to you what the hell programs are and how to use them. You access pages with the numbers after them with the silly syntax "man (number) (topic)".
ls; "List", view the files in a directory.
cat; "Cocatenate" which prints the contents of a file directly into your output.
"more"/"less", a set of default "paging" programs made for the more convenient viewing of text in files, and because LINUX programs don't tend to have any extensions like ".exe", and catting just any binary file will lock your terminal until it's done and could very well start fucking things up, you're going to want to use this rather than getting into the habit of catting files to figure out what they say.
pwd; "Present Working Directory", which you can use in conjunction with other scripts or programs, or just in normal navigation because you shouldn't get into the silly habit of using ls to figure out where you are.
cd, to change your directory fucking obviously.
vim; "VIsual editor IMproved" which is basically inspired by the "visual editor" vi, which itself was an alternative to the earlier UNIX text editor ed (I don't know if Slackware has this by default, but I do know that the default configuration is absolute ass, so you'll want to mess with that later).
su; "Super User" which opens a kind of login shell for the account "root" who has unlimited privileges, which you'll need to maybe install sudo if you really feel like it. By default, root is the only account that can access important programs in the /sbin directory.
stat, which lets you view several properties of a file or directory, but most importantly the owner and privileges.