>>1049185
>I'll create a warning in the .pdf
Htop is a shitty piece of code, don't add anything beyond that. People use shitty code all the time, and GNU/Linux development stack is full of shit in general, but it's not like people are going to stop wanting some specific software.
> To create a location to install and store downloaded programs in, find the manual that's specific to your distribution.
This isn't what I had in mind, dude.
a) You don't strictly need to "install" programs unless you actually need to
b) You can usually dump your own stuff into /usr/local, if it is the ./configure prefix what you are looking for
Package manager, and, consequentially, custom/local repositories are distro-specific though, that's what I was saying.
> If the drivers for 3rd party hardware (Fancy keyboard or mouse's with LED programs such as Roccat) are not already supported by the linux kernel, then you must obtain the source-code and compile it for linux. This is done by applying the bash command on the configure file, which should be within the programs (source-code) directory. Then enter the make command while still being in the directory??
Dude, don't write anything THAT specific until you have actually compiled the kernel yourself at least once, OK? It's misleading and plain out wrong.
>something which the man-pages lack
Man-pages are usually just about perfect at describing what program does. Don't hesitate to use search with "/" on them.
If you don't understand some specific technological term, look it up.
If you don't understand the technology you are about to manipulate (and you need to understand), look up the technology docs, rfcs, whatever.
You can look up usage examples online, too.
It's really easy with online search LOL.
>The problem is that I don't know how much I need to learn before I can consider myself proficient with Linux
Just don't think about it dude. Keep bashing your head against the wall until you can solve all your problems LMAO. If the problem is unsolvable at current Leenooks development stage, it will be pretty obvious.
>I still don't know how to use wine
<wine - run Windows programs on Unix
<wine program [arguments ... ]
Just type "wine path/to/program.exe" LMAO
Like, did you even try to read the manual dude?