/tech/ - Technology★

>>1063095 (OP)

First install GNU/Linux and learn the Unix command-line interface, if have the patience to sit through that you can pick your next step. The CLI is the most basic and most useful skill you can pick up. Even if you decide to stop after that you will have something practical in your toolbelt.

A good guide I read is the one from Apple; it's written with macOS in mind, but it applies to all of Unix. There are probably good non-Apple guides out there, but this is the one I used, and the lessons apply to GNU/Linux as well.

https://developer.apple.com/library/archive/documentation/OpenSource/Conceptual/ShellScripting/CommandLInePrimer/CommandLine.html

>>1063110

Opps, I linked to the appendix of the series. Here is the link to the beginning:

https://developer.apple.com/library/archive/documentation/OpenSource/Conceptual/ShellScripting/Introduction/Introduction.html#//apple_ref/doc/uid/TP40004268-TP40003516-SW1

But maybe it would still be better to start with the command-line primer before going into shell scripting. You decide what works better for you.

Fuck off pajeet

>>1063110

>>1063111

> Apple

Fags go in the oven

>>1063132

Nah pretty sure that is some script kiddie from Middle Amerifat

>Moss

Based

>>1063095 (OP)

>what things mean, what they do

Just try to do a thing, and find out how to do that thing. Use duckduckgo or startpage. Laugh at the faggot that argues about which is better.

>what to look for or prioritize when building a computer

http://www.logicalincrements.com/

Shop around. Nearly everything except SSDs can be bought second hand. Leave space for upgrades. Don't cheap out on thermal paste, but don't overspend on your first system.

>be able to talk to other computer people.

Lurk

Handbooks and Manual Pages,

Ubuntu's Manual is amazing, FreeBSDs Handbooks is better, OpenBSDs FAQ is king.