Preface

Hey there.

My name is Vega. I know there are plenty of tutorials and ways to learn online be it on YouTube, SkillShare, or online classes provided for free by various universities. The difference here is there is no content you'll never use, no babysitting, and lots of bias as a result of personal experience. My views of things like what programming languages are bad or what hardware you should buy to learn on will be expressed directly and bluntly. This isn't to say I won't explain my reasoning, just that I'm not going to be apologetic when I say Javascript, PHP, Java, Arduino (at least the 328p), and Windows 10 are trash - though I will still likely talk about all of these things.

I by no means expect you to share my same biases, in fact, I hope you do not and that at one point or another we can discuss why you think I am wrong, as that is the only way I can learn.

With that said, what is this exactly?

This is a guide for understanding the power the humble electron has in our lives. Electricity, digital logic, code, computers, embedded systems, these things are all around us every second of everyday. As I type this I'm wearing a smart watch, I have a smart phone in my pocket, and I'm using a desktop computer. Each of these devices contains dozens of smaller computers, power supplies, wireless interfaces, etc. My goal with this is to teach you how all of this works and how to use it from transistors to high level code to useful user applications.

I will be assuming you are of reasonable technical ability already- that is the concept of how to proficiently use most types of generic software like text editors, navigation of a file manager, etc- furthermore, I will avoid going into high level math, chemistry, and physics as much as is practical- mostly because knowing these things is typically not actually useful in the daily life of someone who works on any of this beyond those that are doing cutting edge research or are planning to teach, in which case you should actually go to college instead of reading this. For everyone else, welcome. This is the document which can save you going to college and taking classes full of useless information you will inevitably forget and for which employers don't care about to begin with.

Following along will require a few things. The first of which is dedication and time. If you don't have the desire to put in at least a little bit of work there is simply no way I can help, that said, if you're reading this instead of watching Netflix I believe that's already proof enough you want to learn. Next is hardware and software, namely you'll be needing a few development boards and linux, but I'll get into those with time; however, for convince, everything referenced to be downloaded or physical items to be purchased are all listed in Appendix C

Before we get started there are a few things I recommend reading and watching first. These should give you a bit of an overview of some of the things that will be covered to give you at least a tiny bit of familiarity as each concept comes up.

I recommend this overview of the topics covered in CS: Map of Computer Science by Dominic Walliman

Also by Walliman, a video on How to Read Math and the cheat sheet from it:

How To Read Math, Cheat Sheet

Ⅰ - Community

The only way to be successful in this journey is to make friends along the way. Some of this get's really, really difficult. You will get stuck. Having friends to help makes it possible. Find group chats on telegram, join IRC channels, get on some forums, and ask questions on Reddit. Working with people is a lot more fun and you'll learn so much more.

Beyond that, having inspiration each day can be a huge booster shot to your motivation and creativity. Some sites I use nearly daily to finding good new material are:

https://news.ycombinator.com/

https://www.bleepingcomputer.com/

While much less active, I've found some of these to have great information as well

https://n-o-d-e.net/index.html

https://www.alchemistowl.org/pocorgtfo/

(There are many more links in the 'Other Great Resources' section at the bottom of this document)

Oh, and to mention it now

Yes, there is always a relevant XKCD, and yes, you will always feel like everyone knows more than you. Don't stress about asking stupid questions:

Frequently in chats, whether telegram, IRC, slack, or discord, someone says something like this:

Anyone know rust? Having an issue.

How that question is often read:

Can someone to commit to being able to solve my problem with rust, spending as much time as necessary, without them even knowing what the actual problem is or if it's even a rust problem?

Hopefully it's clear why questions like this rarely result in direct answers.

• There are very few people who could be called experts in every facet of whatever is being asked
• Imposter syndrome is common
• Most people won't write that blank check for time/help commitment

• The goal - "Trying to query for a list of tags on a post" - See The XY Problem
• The problem - "I'm getting back these results"
• The expectation - "but it should be these results"
• Any context or previous research you've done
• If possible, a simplified example. 3v4l for php, jsfiddle for html/js/css, etc. are great, otherwise a paste site.
• What you've already tried

This allows anyone there to try to help. Many skills transfer well to other languages or platforms. At minimum, you might get an idea for something you haven't tried yet. Sometimes you'll even solve your own problem while narrowing down the simplest possible test case.

Oh, and don't snark at well-intentioned answers. It's rude and discourages participation.

The technical community can be ruthless with it comes to expecting people to have 'basic' knowledge sometimes, but don't let it get to you. I do want to provide some general ideas that, while not universally, are generally shared among the engineering and surrounding community:

Ⅰ - Any good solution is fast, easy to understand, and above all elegant.

Ⅱ - Any task which can be automated should be - if a computer can do it faster than you then you shouldn't do it by hand

Ⅲ - Any problem that has been solved in a way that satisfies the above two rules should be looked at for reuse before reinventing the wheel

Ⅳ - Any question which has already been answered should not be left to a human to answer again.

Ⅴ- All knowledge should be free†

† within practicality, trade secrets are obviously a thing, and I'm not crazy. I mean like publicly funded research and what not. While the specifics of this rule vary amongst engineering types it is generally a core belief.

On the note of point Ⅲ...

TLDR: RTFM & STFW http://www.catb.org/esr/faqs/smart-questions.html#rtfm

Finally, and I can't stress this enough, I think balancing your creativity among other interests and looking for ties between them can lead to more good than any of thing mentioned above. I enjoy playing music, reading, and writing, so I find inspiration in these media. There are countless electrical hardware and software tools that use hands on programming when playing music. In books I find ideas for what an author may have thought only futuristic when written. I never know when my mind will strike similar gold when writing for myself. Find a hobby and bend it to this as you go along. Like photography? Lean about the internals of a camera. Like cars? Look up how the ODB2 interface actually works. Nothing is magic and the internet will likely have answers and give you ways to apply this knowledge that you care about.

In general I've found site specific forms and Reddit to be the best platforms for most things, with some others finding their main following in other places though. For example I'm in a large technical chat group with Furries on Telegram and some open source tools still thrive on IRC. Also, if your reaction to that is "Furries? How can that be relevent?" Well, normally it's not. Most of what we talk about is just normal engineering-y topics, but having something else in common helps. That said, there's more cross over in any community than you might think:

No matter what you care about, know there's a wide range of communities that would be thrilled to have you, and you can always combine what you learn here with any of the other interests you have to make the things your passionate about better!

Assholes: A Probing Examination

Ⅱ - Learn how to learn

I'm going to keep this short and sweet: Nobody learns (effectively) by being shown what to do. You can watch hundreds of hours of people playing guitar, even explaining how they do it, but you wont be able to randomly pick one up and play if you never have before. Furthermore, as much as you can learn from direct reading and instruction, it has it's place and limits. This guide, book, whatever you want to call it, was never meant to be followed like instructions. You should go out on your own and poke around, get lost in the weeds as you go. If you find a topic dull, don't read it as in depth. I don't want you wasting your time. Break things. Make mistakes. By the end of this you should know what a burning resistor smells like, what it's like to try to recover from a Linux system that just won't boot, and how it feels when a bug has been eluding you for hours and your code still doesn't work. The only way that happens (unless I made a mistake which is also probable) is if you try ideas when you get them and do more than what's in this book.

This struggle is part of learning and proof that you're doing well. These experiences should teach you things in their own right. The smell of burning electronics may help you diagnose a future circuit, the lesson to not fall into a pit of technical debt may help when a bug has engulfed your code, and the late night of terminal only based work as you try to get your computer working again will teach you more than this book ever can.

To quote someone much smarted than myself:

Finally, there's

Cunningham's Law states "the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer." (source)

but note, you should keep in mind the standard warning that comes when first using sudo if you plan to use Cunningham's law to your advantage:

We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things:

1) Respect the privacy of others. 2) Think before you type. 3) With great power comes great responsibility.

Chapter 1 - The first goal

Every journey needs a place to start, and while many may like to start slow I think a head first approach is best. So that's exactly what we're gonna do. The very first thing we're going to do is install a new operating system (OS) on your computer.

Quote boxes like these will provide notes throughout the guide, often definitional. If you already understand everything prior to each box, you can probably safely ignore it, though it will occasionally be used for actual quotes as seen prior to this

Operating System: According to Wikipedia, "An operating system (OS) is system software that manages computer hardware and software resources and provides common services for computer programs." put simply on your hardware this is probably Windows or Mac OS, and it's what everything else runs on top of

You should really make a full backup of your computer before doing this, as installing an operating system can rather easily lead to lost files when you reformat or reparation your drive or when you change settings in the BIOS/UEFI and swap the bootloader.

Reformat: the bulk storage device in your computer, the hard drive or solid state drive, needs to be formated before use, this sets up a way for the computer and the drive to agree on a base system for how partitions should be setup, speaking of which:

Repartion: To partition a drive means to take all the space on the hard drive and divide it into partitions onto which you can put a file system. Most operating systems like Windows, Mac OsX, or Linux, use multiple partitions for the operating system to function. Usually a filesystem is set up on each of these partitions, in windows this is typically NTFS for Hard Drives and FAT32 for flash drives, these file systems are effectively the index for all the files you'll put on the drive, and as you may have multiple partitions and multiple file systems on one disk each will have an index to match. As complicated as it may seem this means the partition table can be seen as an 'index of inecies' of sorts. Don't worry if that's a lot to understand right now, we'll come back to this topic in depth. BIOS/UEFI: The Binary Input Output System or Unified Extensible Firmware Interface is the thing you see before you computer loads the operating system, usually prompting to press delete or f2 to change settings. This is the system that is used to change the way all the components around the computer talk to one another and at what speed. Bootloader: The bootloader sits at a special place on the hard drive selected for boot in the UEFI or BIOS, and is what the computer uses to load the full operating system, most will let you chose what operating system you want to boot if you have multiple installed on you computer at once

Alright, so why do I want you to install a new OS to begin with? Well, the OS we'll be using is called Linux. Linux is actually what powers both android and ChomeOS, and is a common descendant of the same system as Mac OSX as well as almost all of the servers on the internet from massive website like Facebook and Google to small Minecraft servers you can rent online to play with friends. What's cool about Linux is it lets you get much closer to the hardware and see what's going on, and it just generally makes writing code much easier. Furthermore, it's super easy to set up an amazing development environment in Linux for getting work done with code or electronics, and at the end of the day you can still watch YouTube, play most games that are on steam, or open up an office suite, just like Windows or Mac. Unlike Windows and (to a lesser extent) Mac though the system is laid out in way so that all the moving parts are exposed and able to be tinkered with. No setting or configuration is locked in and you have total control over your computer with Linux. Furthermore, it's not just easier to run and use software and tools for doing hardware and programming development on Linux, but it's also easier to find and install the tools, as you'll see shortly. Finally, Linux has a great track record of stability, as there are many Linux servers that run 24/7/365 to serve web pages, host services like games, and crunch big data in real time. In fact, all of the world's top 500 super computers use Linux.

Beyond that, there's a degree of respect Linux has for the user that Windows, and to a lesser extent OSX, lack. In Windows 10 ads are being baked into the preinstalled programs from Minesweeper to the Email client, the OS pesters you to use Edge and Bing while simulatiously spying on everything you do. If you attempt to do even remotely system level things it's increasingly easy to get the Frowny Face Blue Screen of Death (BSOD)

Add to this the fact that Microsoft basically laid off their entire testing department, and the nightmare that windows 10 updates have cause, forced online accounts, or well, just read this list. You'll see pretty quickly why most 'nerds' have a pretty deep seeded hatred for Microsoft.

I mean, this was a real error message I got when trying to upgrade my system from 8.1 to 10:

Image source

Chapter 2 - Let's do it then, Installing Arch Linux

Unlike Windows or Mac which are primarily differentiated by versions (Windows XP, Vista, 7, 10...), Linux has two important things to look out for: The distribution and the kernel version number. Linux is actually just the name of the underlying 'core' of the system, known as the kernel, as such, there are literally thousands of Linux variations. Some of the well known variants include Ubuntu, Fedora, OpenSuse, and Arch (No disrespect to the other distros out there!). Each of these has a different target audience, with some meant for servers, some meant for casual users as an alternative to Windows, others as work station for hard core computing. They also ship with different software pre-installed to be accessed after the first boot. The other differentiating factor is the version of the Linux Kernel that they use. Some chose to use an older, battle hardened kernel that is known to be very, very stable, others chose a nice middle ground, while yet others continuously release an update to the newest available kernel. There are pros and cons to each model and each has its place; however, the one I'm going to have you install is know as one of the hardest to work with, but also one of the most cutting edge, fun to tinker around in, and best documented: Arch Linux. Arch is what's known as a rolling release distribution, which means it gets the bleeding edge features and the newest kernel pretty much as fast as possible, though really the biggest thing that makes Arch special is how bare bones it is out of the box, shipping with basically no pre-installed software. In fact, when you first start it up the only thing you'll see is a screen to type and run commands, and that's where we're going to start.

For most distros like Ubuntu or OpenSuse (feel free to look these up, this page isn't going anywhere) there's a nice graphical, point and click installer which helps you install the system and somewhat mitigates potential risk of killing your original OS (Mac/Win) or losing data; however, the goal of this guide is to learn. Arch's install process, entirely by typing commands in this terminal is hard, but that difficulty leads to a deeper understanding and respect for the system as a whole

When we're done you'll have a system that has exactly what you need and nothing you don't. You won't find weird forcibly installed software like Win 10's Candy Crush App here, and your system will only do exactly what you tell it. Of course, this implies you know how to speak it's language and tell it what you want. Thankfully with some practice you'll get used to running Arch and you'll wonder why you ever dealt with other systems to begin with.

Install instructions will vary dependent on your hardware, but I'm going to assume you have a desktop or laptop which shipped with Windows 10 and has a UEFI system. Most laptops newer than ~2016 should be in this category. If your system uses a BIOS or Legacy boot instead, or if you have a mac, this won't apply to you, but you should be able to follow some of the resources I used to make this guide which are linked below along with some searching online to figure it out.

Alright, so what exactly are you getting yourself into? Well, I'll be real with you, a lot. Installing Arch sucks. Things can go wrong, it's not user friendly at all, and is generally a pain, and if you screw up you'll need someone who can restore your computer to at least having Windows on it again so I'll say it again- Make a backup of your entire hard drive before proceeding, if you don't know how to do this, search it.

Okay, so, with that said let's dive into it. After you have a backup, you'll need to head on over to https://www.archlinux.org/download/ and if you have a torrent client installed use the provided BitTorrent Downloads, if you have no idea what that is, look at the below box

BitTorrent: Torrenting is type of download that runs over distributed peer to peer connections, this means you're directly downloading the file from multiple people rather than from one large server. Popular clients on Windows include uTorrent, qBittorrent, and Deluge

You may want to go grab a coffee while it downloads depending on your connection, though the image should be rather small. Once that's done downloading your torrent client should automatically confirm the image by checksum, but as this is a good learning opportunity let's do a manual double check as well.

checksum: a mathematical summing of the bits in a file combined with some sort of cypher to produce a 'hash' which can be checked to against one that is known, any modification would result in a different hash. This protects against malicious actors putting bad things in the code as well as from a corrupted download.

certutil -hashfile archlinux-20xx.xx.xx-x86_64.iso sha1


Note, if this spits out "The process cannot access the file because it is being used by another process." you'll need to close your torrent client or stop seeding the file first!

So let's look at this command. The first part, certutil, is a program on your computer, '-hashfile' says the next string of text is the name of the file we want to examine, and the last part sha1 is the checksum as mentioned before. Finally, if you go back to https://www.archlinux.org/download/ and look under 'Checksums' you can compare the output of the command you just ran against the SHA1 sum provided to be sure you didn't have any errors in the file. This is mostly a security check as in theory someone could provide a 'bad' version of the OS containing malware, but such a version would produce an incorrect checksum, in practice this is extraordinarily uncommon. Though this does also serve to ensure the download wasn't corrupted in any way either.

MAC: open up a terminal by going to the Utilities fore in Applications and open 'Terminal'. The mac terminal is very, very similar to what you'll use in Linux actually, and the commands here are actually identical. You should see something like

MacBook:~ username$ waiting for input. That ~ represents that you're in your user or 'home' folder, and assuming you downloaded Arch's install image to your downloads folder you should be able to type MacBook:~ username$ shasum -a 1 Downloads/arch

followed by pressing tab to make that auto complete to something like

MacBook:~ usernameshasum -a 1 Downloads/archlinux-20xx.xx.xx-x86_64.iso upon pressing enter the terminal should print out a long string of text. So let's look at this command. The first part, shasum, is a program on your computer, '-a 1' says to use the sha1 algorithm instead of something like sha256, and the last part is the filename we want to compute the checksum of. Now, if you go back to https://www.archlinux.org/download/ and look under 'Checksums' you can compare the output of the command you just ran against the SHA1 sum provided to be sure you didn't have any errors in the file. This is mostly a security check as in theory someone could provide a 'bad' version of the OS containing malware, but such a version would produce an incorrect checksum, in practice this is extraordinarily uncommon. Though this does also serve to ensure the download wasn't corrupted in any way either. Okay, so we have the OS, how do you install the damn thing? Well, get ready for a fun time. The first thing you'll need is a flash drive with nothing on it you care about, as it's going to be reformated, which will wipe any data on it. To install an OS you have to create 'bootable media' this used to be done with a CD, though mostly it's done with flash drives now. You'll actually be putting the OS on the flash drive and then using that to put it on your hard drive. Let's not get ahead of ourselves though, we need room to put the new operating system in! Thankfully Linux is small- really small. Even 50Gb should be plenty for the OS, all your programs, and tons of room to spare for data, but I typically recommend at least 100GB, and since we'll be installing a lot of development tools, it makes sense to do this right to begin with. Windows: When you got your computer with windows is likely that all of the room on your hard drive was preallocated for windows (as it should be!) so we'll need to shrink this down and make room for Linux to live along side Windows. Open the start menu and type 'disk manag' and hopefully "create or format hard drive partitions" will show up as an option. At the bottom you should see a few bars showing partitions on your disk(s). If you have multiple hard drives there will be multiple rows of bars, otherwise there will be only one row. If you have multiple drives it's likely that one is a larger hard drive (HDD) and the other a smaller solid state drive (SSD), if you have room on your SSD use that, if you don't using the HDD will be fine, but the OS may feel slower than you're accustomed to. If you only have one drive, ignore this. Right click in what is likely the largest box, labeled 'primary partition' and chose 'Shrink Volume'. After it finishes querying available disk space enter 102400 as the amount of room to shrink (This is 100GB as there are 1024MB in a GB) or a lower or higher value as you please, but realize this is data you will not be able to access from windows. If the window shows 0MB of available shrink space first try running disk cleanup and choose cleanup system files, try turning off system restore, and finally disable the page file. In my experince it's usually the pagefile, which kinda sucks. If none of this works, you do have another option: wiping everything and installing linux. This is actually easier, however, it's a bit more extreme, as you won't be able to boot back to windows for anythig. You may instead want to try linux out on an old usused computer first. Either way, you do you, but I'm not liable if things go wrong. https://medium.com/@terajournal/increasing-size-of-available-shrink-space-for-hard-drive-partition-in-windows-8fffa50535d3 Alright, we're getting there I promise. You should now have a gray block next to that blue block of space that shows unused space, that's perfect. Next up we'll need to turn Fast Boot off. In my experience turning this off doesn't effect windows boot time at all, and by having it off we'll be able to access window's file from inside linux later. To do this: go to 'edit power plan', then in the top bar navigate back to 'Power Options', select 'Chose what the buttons do' on the left side, click 'Change settings that are currently unavailable' and then un check 'Turn on Fast Startup'. Okay, now we're finally ready to copy the OS to a flash drive so we can install Arch, to do this, you'll need to download a program called rufus https://rufus.ie/. Download, run, etc. When it opens select the flash drive as your 'device' , press the select button under that and select the archlinux-20xx.xx.xx-x86_64.iso file we downloaded earlier. Everything else should be fine, so click start. This may take a second, in the mean time, open this guide on another computer as the next few steps will require a lot of restarting and doing things outside of windows. MAC: Before we go any further I really want to warn you of two things, one, it's going to be harder to follow this guide on a MAC. More steps are involved, and some work arounds are necessary, and more importantly, I have no experience with it. so I'm mostly regurgitating other things I've read. Pages like https://wiki.archlinux.org/index.php/Mac#Installation may prove helpful later. First, you'll need to open up 'Disk Utility' in Applications/Utilities, then pick your disk and click 'Partition' and click the '+' button to make a new partition. Choose how much space you want to leave on the disk for MacOS and how much you want for Arch. The format of the new partition doesn't matter. Note, if your disk is encrypted, you'll need to decrypt first. Now, you'll need to open a terminal like you did back when checking the checksum. Plug in either an empty flash drive or one which you don't mind erasing, and run diskutil list and you should see something like /dev/diskX (external, physical) which is your flash drive. Now run diskutil unmountDisk /dev/diskX where X is your flash drive disk number from above, then finally run dd if=path/to/arch.iso of=/dev/rdiskX bs=1m. Note that the of part has /rdiskX . The path to your arch iso is probably something like ~/Downloads/archlinux-20xx.xx.xx-x86_64.iso This command won't print anything while it's running, but when it's done you'll see a new line asking for input. Two more notes ripped straight from https://wiki.archlinux.org/index.php/USB_flash_installation_media#In_macOS: To view progress, send SIGINFO by pressing Ctrl+t. Note diskX here should not include the s1 suffix, or else the USB device will only be bootable in UEFI mode and not legacy. After completion, macOS may complain that "The disk you inserted was not readable by this computer". Select 'Ignore'. The USB device will be bootable. Now you should be good to carry on with the guide of note, the following guide will be assuming you're installing Linux on the same drive as Windows or MacOS, making it applicable for most systems right away; however, I strongly recommend getting an extra SSD and giving Linux it's own disk outright instead. This is far easier to do in a desktop, but if you have a laptop with a CD drive you may be able to put a SSD in it's place. SSD prices have been steadily declining over the pas few years, but as of the time of writing a 250Gb ssd should be available for under 50 USD. I'd recommend a larger disk though, with 500Gb being plenty for most people While this guide should lead you though step by step, it may be helpful to follow the offical installation guide as well, which is available at https://wiki.archlinux.org/index.php/installation_guide. Furthermore, while slightly outdated, this flow chat is a nice refrence as well: https://i.imgur.com/Hokk8sK.jpg despite the technically complexity to get to it, the best place for Arch Linux support, even for installation, is in the IRC (Internet Relay Chat) channel #archlinux on Freenode. https://wiki.archlinux.org/index.php/Arch_IRC_channels Obviously if you need this you'll need IRC open on a differnt device than the one you're installing from. There are plenty of IRC clients available for any platform though. ☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠☠ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ Seriously, backup your shit. I've done this countless times and have still managed to accidentally wipe a drive. There's a good chance you're about to completely murder your windows install. This is a necssary evil to learn, and I assure you'll be happy you've done all this, but this next bit is actual hell for people. I'm sorry it gets so bad so early. I promise it's worth it, okay? ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ The next section requires a lot of reboots and has steps where you can't have this guide open on the computer you're working on. Don't be stupid. MAC: Beware, none of the following was writen with a MAC in mind, and as such I strongly recommend you read https://wiki.archlinux.org/index.php/Mac#Installation and look for where my instructions deviate from what's recommended here. Now you'll need to power off your computer. Turn it back on and as you do mash the everliving hell out of both f2 and delete (unless you know what key gets you into the UEFI / BIOS settings). This should bring up a menu that either looks super fancy or looks stright out of the 80's. Either is fine. The setting we're looking for is 'Secure Boot' it's probably under a menu called 'Boot' or 'Security'. You'll need to shut this off. In theory secure boot should protect against a nasty kind of virus called a rootkit, in practice it doesn't and only serves to make installing linux more annoying, don't worry, I'm a security nut and am comfortable leaving it off. Exit and save settings, and as your computer boots again mash F11 or whatever key gets you to a boot menu, and select your USB key. If it shows up twice try the first one first, if that doesn't work try the other one. (If you end up back in Windows just restart and go back into the bios settings, go to 'Boot' and reorder the boot menu entries so your flash drive is the first option) The system should boot first to a screen with a few options, pick Arch Linux if you have to or just wait for it to move on. You should, with any luck, see a list of text flash down the screen that looks roughly like [OK] doing thing [OK] starting thing [OK] did thing  If something comes up as [FAILED] even though you still get to the login prompt, don't worry about it for now Then, you should be greeted by a minimal prompt that looks like root@archiso ~ #  and that's it. Congrats, you've already made massive progress. This is arch, but it's not actually installed yet, right now your entire computer is running off the flash drive. So let's get it installed. You'll need an internet connection to do anything, if you can connect you computer to the network though ethernet directly, that should be much, much easier than doing things though wifi. If you absolutely must do things though wifi, well, first, really don't. I mean, you can, but's a solid pain. I'm going to assume you're not. Cool. If you didn't connect your computer to ethernet before you started arch, the first thing you should type in this prompt is systemctl restart dhcpcd  this manually restarts the service that asks the network for an IP address, which you need to do since currently the system is in such a minimal state it won't do that automatically. Now, try ping archlinux.org  if you see something like '64 bytes from apollo.archlinux.org', congrats! You're online! If not, you may try a different network or wireless if applicable (seriously, it's a pain) From here, you'll need to see the names of the hard drives on your system. run 'lsblk -f'. but what does that even mean? well, let's learn about another command! 'man' for most commands on linux if you type 'man' before the command with no flags (the -x things after the command) it'll open a manual page for the command. Read here to figure and try to figure out what lsblk is and what -f does. lsblk lists information about all or the specified block devices. The lsblk command reads the sysfs filesystem to gather information. The command prints all block devices (except RAM disks) in a tree-like format by default. Use lsblk --help to get a list of all available columns. ... The default output as well as default output from options like --topology and --fs is subject to change, so whenever possible you should avoid using default outputs in your scripts. Always explicitly define expected columns by --output columns in environment where a stable output is required. ... -f, --fs Output info about filesystems. This option is equivalent to "-o NAME,FSTYPE,LABEL,MOUNTPOINT". The authoritative information about filesystems and raids is provided by the blkid(8) command. Okay? Well, that probably doesn't mean much so lets focus on the important bits "lsblk lists information about all or the specified block devices. The lsblk command reads the sysfs filesystem to gather information." Block devices are devices that have 'blocks' of information, like hard drives, flash drives, solid state drives, sd cards, etc. "-f, --fs ... Output info about filesystems." This means we'll be able to see what type of file system is on each block device. So, we can use this command to see information like we saw graphically back when we opened disk management in windows, only now with their linux names. In linux each block device is actually stored as a file, as bizarre as that may seem. This file is actually located in the dev folder which sits on top the root folder. The root folder is simply designated by a single '/' so a normal file structure may look like '/home/USERNAME/Documents/office/' and so on. It's worth noting that '/' is actually a folder in itself, it's just the absolute bottom folder, hence it's called the root folder. So the dev folder is located at /dev. In /dev there's a lot of things, but at the moment what we're really concerned about is the storage devices. so, looking at this example output from lsblk you'll see three storage devices /dev/sda /dev/sdb and /dev/nvme0n1 vega@linux ~ # lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda ├─sda1 ├─sda2 ├─sda3 └─sda4 sdb ├─sdb1 └─sdb2 nvme0n1 ├─nvme0n1p1 ntfs Recovery 36C8A86BC8A82B57 ├─nvme0n1p2 vfat E2AB-10F2 ├─nvme0n1p3 ntfs DE54B4D854B4B51D └─nvme0n1p4  What do these mean? Well, most drives in linux are simply designated by a /dev/sdX where x is just the next available letter in the alphabet, though on some newer systems like mine, you may find some blazing fast SSDs actually use that other odd nvme syntax. Both work exactly the same way for what were doing. looking at that output again you'll see each device has multiple things under it. For example /dev/sda has /dev/sda1 all the way though /dev/sda4. Each of these are the separate partitions. In this particular example, sda is actually the flash drive we're running off of, so you can see that it is currently where our root file is '/' on /dev/sda1 and that it's an ext4 file system (I'll explain this a bit more in a bit) you'll also see there's another partition that's formatted as fat32 for boot, but all of these are on the flash drive because they're on sda. For Simplicity now we're actually going to look at a simpler 'lsblk -f' output with only /dev/sda and sdb. sda is still the boot usb stick you're on, but sdb is now the singular drive in a laptop that has windows installed and available free space in accordance with this guide. root@archiso ~ # lsblk -f sdb ├─sdb1 ntfs Recovery 36C8A86BC8A82B57 ├─sdb2 vfat E2AB-10F2 ├─sdb3 ntfs DE54B4D854B4B51D └─sdb4  alright, so now on sdb we see there's 4 partitions (sdb1,2,3,4) where in this case we have sdb2 as a ~512Mb vfat partition, sdb3 as a 300Gb NTFs partition, and then that blank partition we made on sdb4. That 512Mb partition contains the bootloader for both windows and soon linux. The larger NTFS file system is where Windows and all your programs documents and other things you've done on your computer in the past live. I hope now it's obvious why I urged backups, as we're about to play around with things a bit. We're going to need to make some changes this list tough, as we actually need one more small division in the partition table. run the command root@archiso ~ # cfdisk /dev/sdb  this should bring up a strange command line based almost graphical interface which you can used to edit, add, or remove partitions. With that 100Gb (or whatever you chose free space we made earlier), let's divide it into two partitions, one that's 8GB and the other that's just what's left. We're doing this so we have somewhere to put SWAP in a second, but let's get to that later, for now just use your arrow keys and highlight the large empty block and select new, select primary, then make it 8GB, which is 8*1024Mb or 8192, and then select end. Finally write it, then quit. Whew. Bit stressful even for me. Don't worry, Linux get's much much easier, especially when we get our graphical tools back. now, run lsblk again. You should see something like root@archiso ~ # lsblk sdb ├─sdb1 ntfs Recovery 36C8A86BC8A82B57 ├─sdb2 vfat E2AB-10F2 ├─sdb3 ntfs DE54B4D854B4B51D ├─sdb4 └─sdb5  so now we need to format these partitions with a file system. For the root file system, where we're gonna put all the programs, files, and the OS itself we'll use the ext4 file system. It's by far the most common file system for linux. To do this look at the lsblk output and look for the large empty space we left (not the 8Gb space we just made!) and run root@archiso ~ # mkfs.ext4 /dev/sdxy  where xy is the correct letter and number for your partition, in the above example that's /dev/sdb4, as sdb5 is the 8Gb partition we just made alright, that's actually most of the really hard stuff done. Now we need to mount both the file system we just made and the boot filesystem. run: mount /dev/sdbx /mnt mount /dev/sdby /mnt/boot  where x is the same as the above x and y is the number of the partition with the windows boot manager. sdby should be roughly 500 megabytes and be vfat, it may appear as 'EFI partiton' in cfdisk if you're unsure. Next up we need to install the base of the os to these drives, this is actually pretty easy just run [TODO] Arch linux's install has changed a bit since this was written. Now, more arguments are required at install time as the base Linux kernel is no longer included in base. I've changed this here slightly, but it's very likely still missing some things. pacstrap /mnt base base-devel linux systemd  then, we need something that tells the system the names of our partitions and how to mount them at boot. Thankfully, the system can generate (most) of this for us, just run genfstab -U /mnt > /mnt/etc/fstab  what this command does is looks at the id's of the drives in /mnt (the ones we manually mounted when we ran mount a few commands ago) and redirects those id's and the settings used to mount them (which were default) and writes that output using '>' as a redirect to a file stored in /mnt/etc/fstab. Because /mnt is the location where we mounted the harddrive, it's actually writing a file to the hard drive now, just as pacstrap just did. Alright, next we need to use a command that you'll probably never use again- chroot. This changes your root directly to be higher up the chain, effectively cutting off access to lower files, though we need to do this to install our bootloader, again this is easy root@archiso ~ # arch-chroot /mnt  which will change the above to look like: ' root@archiso ~ # ' to ' root@archiso / # ' as that '~' was actually a shorter representation of being in /home/root (there's actually a user nammed root by default, and the user has it's own home directory. It's easy to confused root the user with root the directory, but you'll get it eventually if you don't now that's okay c: ) now we can install the bootlooder with root@archiso / # bootctl install  Now we need to add a bootloader entry for arch. We're going to use a very simple command line text editor called nano. it's sorta like notepad on windows. root@archiso / # nano /boot/loader/loader.conf  this will bring up a text editor, it says how to operate it at the bottom (ctr+o to write out = save, crt+x to exit, etc) enter, exactly: (Note line 2 says linuZ-linux, that's not a typo, and replace the x with your root partiton) title Arch Linux linux /vmlinuz-linux initrd /initramfs-linux.ing options root=/dev/sdbx rw  and for our last trick before we reboot save and exit nano with ctr+o, ctl+x then, run root@archiso / # nano /boot/loader/loader.conf  and enter timeout 3 default arch  then, we're ready to reboot into the new OS! run consecutively, root@archiso / # exit root@archiso / # reboot  and pull the flash drive out. If all went well your system should boot to Arch. If it didn't, first make sure it's set to boot to arch in the BIOS/UEFI's boot settings, and then if things are still broken try to figure out why, there are plenty of people in the community willing to help, including me. Assuming it booted back up to a similar looking prompt but with no flash drive we have to do some house keeping but you'll have a bad ass system in no time. First things first enter 'root' for the user name, this should let you login. then run 'passwd' this will prompt you to set a password. For the love of god don't forget it. Next you'll need to set a hostname, this is how your computer id's itself on the network, so might help if you make it something sensible like 'usernamelinux' to do this run echo 'mynewawesomehostname' > /etc/hostname  then let's add a user, as using root all the time is very unsafe. To do so run: (I recommend using the same password you used for root) useradd -m -G wheel mycrappyusername followed by, passwd mycrappyusername  I swear to you we're getting there. run EDITOR=nano visudo  then find the line that says # %wheel ALL=(ALL) ALL  and remove the '#' As an explanation, the '#' is turning that line in that file into a comment, in programming it's common practice to use comments to disable sections of code so say we had a program: for i in range(5) #print(i) print(i/2)  the # before print(i) is preventing it from actually executing so the output of this would be {1/2,1,3/2,2,5/2} instead of {1,1/2,2,1,3,3/2,4,2,5/2,5} Anyway, with that out of the way let's find fix up networking so we can get online and run updates run ip link and look for the name of your network interface. If it's a wired adapter it should be enpXsY where X and Y are number, wif is similar but uses wlp instead of enp. To make sure the network brings itself up on each boot let's enable dhcpcd - that service we restarted way back when- on that interface. Just run systemctl enable dhcpcd@enpXsY.service this enable it at each boot however we should start it now because this is the frist time systemctl start hdcpcd@enpXsY.service  next up, we should make sure things know what language we speak. Assuming you want to use US english just run locale-gen followed by, localectl set-locale LANG=en_US.UTF-8  Timezones, run each independently tzselect timedatectl list-timezones timedatectl set-timezone Zone/SubZone hwclock -systohc -utc timedatectl set-ntp true  It's worth noting Linux and Windows use differenent clock standards so every time you reboot between the two windows will messup the clock, to fix it in WINDOWS you can run reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /d 1 /t REG_DWORD /f  in an admin command prompt Alright, we're getting close to graphical stuff now, I swear. Remember that 8Gb partion we made a while ago, time to use it. Now that we're in the full OS the're a good chance the location names of the partitions changed so run lsblk -f again and figure out where that 8Gb portion is lsblk -f mkswap /dev/sdXY swapon /dev/sdxy  then, we need to edit the fstab file we generated earlier. Let's look at what the fstab file looks like right now. We can read a file from the command line without opening it up for editing with cat, so run cat /etc/fstab  and you can see what it looks like. See all those super long UUID's? We need the right one of those for our new swap area. Thankfully there's an easier way to do this than writing it down on a sticky note. if we run lsblk -no UUID /dev/sdxy (obviously substitute x and y) you'll get this UUID, so let's just append it onto the end of the fstab file! Remember how we used the '>' character before to write the output of genfstab to /etc/fstab, well you can also use two of that same character to append an output to a file. However, before we do that let's be safe rather than sorry and make a backup of the fstab file by first moving to the /etc directory then making a copy of the file cd /etc cp fstab fstab.bak lsblk -no UUID /dev/sdxy >> fstab  note we didn't need to type /etc/ before each fstab because that's a file in the folder we're already in. but we're not done yet. use nano to open up the fstab file and edit it so the last line we just appended looks more like: UUID=whateverthisis none swap defaults 0 0  Save and close nano and then to finish up swap all we need to do is edit one more file nano /etc/sysctl.d/99-sysctl.conf and add the single line vm.swappiness=10  Alright, lets run an update and reboot! For now to do updates we'll use pacman (short for package manager) run 'pacman -Syyu' The -S says to Sync, or actually apply the updates, the double y's say to force grab the newest database (usually only use one y) and u means upgrade. If you want more detail run man pacman Once that's done you can run systemctl reboot Finally, we're going to get a graphical environment running. Once the system reboots login with your username, not root. When you type your password you won't see anything, but it is actually typing! then run: sudo pacman -S xf86-video-vesa mesa  This command uses sudo or 'superuser do' because you're now logged in as a user, and as such need admin privileges to install software. This is part of why Linux is so secure. Pacman, again, is just 'package manager' , -S tells pacman to sync the requested packages from the server and the other two things are the two packages we want right now, both are used for video output. To install the correct driver for your graphics hardware you can run these next few commands use 'pipe' the character above enter on most US keyboards lspci | grep -i VGA and if that doesn't turn up anything lspci | grep -i 3D  to find the vendor of your graphics card. If the output contains NVIDIA run sudo pacman -S xf86-video-nouveau  for INTEL run sudo pacman -S xf86-video-intel  and for AMD run sudo pacman -S xf86-video-amdgpu  if you have multiple, it's safe to install both. Alright, now we need to install the desktop environment. Because this guide to this point is probably already melting your brain I'll take it easy for a bit and we can install KDE-Plasma. KDE Plasma is pretty big though, so we're gonna want to be sure we're using fast mirrors before we do anything else sudo pacman -S reflector  then we're going to temporarily switch to the root account using su all you have to do is type su and enter, then type the password now run reflector -c us -n 25 -f 5 > /etc/pacmand.d/mirrorlist  Finally to install Plasma run sudo pacman -S xorg-server xord-utils xorg-xinit xterm plasma kde-applications then sudo systemctl enable ssdm amixer sset Master unmute and finally, lets see the epic payoff of all the effort sudo systemctl start ssdm  Note that KDE Plasma is fairly large to download and a bit resource intensive. As an alternative if on older hardware sudo pacman -S xorg-server xorg-utils xorg-xinit xterm mate mate-extra lightdm then sudo systemctl enebale lightdm amixer sset Master unmute and finally, lets see the epic payoff of all the effort sudo systemctl start lxdm  Alright, now you can take a few minutes to get used to how your new computer works, play with settings, etc. before you wrap up lets do a tiny bit of houskeeping sudo pacman-key --init sudo pacman-key --populate sudo pacman -S git --needed git clone https://aur.archlinux.org/yay.git cd yay makepkg -Acs sudo pacman -U yay -S zsh chsh -s /bin/zsh  from now on you can just open a terminal and type yay followed by your password to run updates. [TODO] Make NTFS drives accesible and auto mount So Why Did I do all of that exactly? Linux makes development of code particularly easy, so, let's write some code! The first language we're going to try out is called python. Python is an interpreted language, meaning each block to be executed can be run one at a time, to show you, let's install it. Because we installed yay earlier you could use either that or pacman, but let's just use yay for simplicity. From here on out I'll be coping directly from what my terminal prompt looks like. Yours, for now, probaly looks similar to: username@root /current/folder : command -to -be executed  However, mine looks like ╭─vega@lyrae /current folder ╰─➤ command -to -be -executed  so, install python just like we've installed other programs with python or yay ╭─vega@lyrae ~ ╰─➤ yay -S python  once that's done you should be able to start the python interpreter by simply typing python and pressing enter. This will give you a new prompt that takes python code as input ╭─vega@lyrae ~ ╰─➤ python Python 3.7.2 (default, Jan 10 2019, 23:51:51) [GCC 8.2.1 20181127] on linux Type "help", "copyright", "credits" or "license" for more information. >>>  the >>> is the prompt asking for input, go ahead and just try 1 + 1 for now >>> 1 + 1 2  Okay, who cares though, right? let's try something a bit cooler. Say you wanted to add up all the odd numbers up to 72? This isn't something that's trivial to do on most calculators and would be a real pain by hand, but it's trivial to do in python. The code to run this in python is #note, this is to 73 becasue the range function include the first number and excludes the last sum = 0 for i in range(1,73): sum = sum + i print(sum)  when you type this in the prompt you'll actually be able to enter multiple lines when you write the for loop. There's no clear way to explain this in text, you'll just have to try it and see how it works, note the way python set up looping is by indentation, so you'll need to press tab when the prompt lets you type the line sum = sum + i so that it's obviously a 'child' of the for loop. after you run the print statment you should see the output ╭─vega@lyrae ~ ╰─➤ python Python 3.7.2 (default, Jan 10 2019, 23:51:51) [GCC 8.2.1 20181127] on linux Type "help", "copyright", "credits" or "license" for more information. >>> sum = 0 >>> for i in range(1,73): ... sum = sum + i ... >>> print(sum) 2628 >>> exit() ╭─vega@lyrae ~ ╰─➤  telling us the answer is 2628. To make you feel like a bad ass, you actually just wrote code that's equivalent to this math $$\sum_{n=1}^{72} n$$ pretty cool right? But that's math? Who cares? Let's do something cool! Python code doesn't have to be written in line by line, you can put it an a file and the computer will run that file as a program, so let's do that! But to do that we're gonna need something better than a terminal editor or an equivalent to notepad. There are actually text editors that make writing code much easier. Let's go grab the 'Visual Studio Code' editor. Hopefully by now you know the command! (The name of the package is just code) super quick detour: while you can open graphical programs though the start menu down in the lower left hand corner just like on Windows, you can actually open a program directly from the terminal. Interestingly, this can make a program that opens in a new window a 'child process' of the terminal, which is why we normally don't do this. What this normally means is that if you start a program from the terminal - the parent- and then close the terminal, the child process, in this case the graphical program you started, will die too. Strangely, VSCode actually separates itself from it's parent process almost immediately, which is why we can start it from a terminal and then close the terminal and it should stay running. so, let's do that. ╭─vega@lyrae ~ ╰─➤ code  and a new window should pop up. It'll probably open with a few tabs welcoming you, asking if you want to install a theme, if you are okay sending VSCode usage info, etc. Uncheck boxes so these don't come up each time and answer questions as you please. Then, we're going to go up to the top and chose file -> new file Then, down at the bottom right of the editor you should see something that says plain text click that and a box will appear asking for the name of the language you're working with. Obviously chose python. alright, now we're ready to code! Let's put a bit more interesting of a program in and then we'll talk about what it does line by line. I stole this code from https://matplotlib.org/2.0.2/examples/animation/animate_decay.html #!/bin/python3 import numpy as np import matplotlib.pyplot as plt import matplotlib.animation as animation def data_gen(t=0): count = 0 while count < 1000: count += 1 t += 0.1 yield t, np.sin(2*np.pi*t) * np.exp(-t/10.) def init(): ax.set_ylim(-1.1, 1.1) ax.set_xlim(0, 10) del xdata[:] del ydata[:] line.set_data(xdata, ydata) return line, fig, ax = plt.subplots() line, = ax.plot([], [], lw=2) ax.grid() xdata, ydata = [], [] def run(data): # update the data t, y = data xdata.append(t) ydata.append(y) xmin, xmax = ax.get_xlim() if t >= xmax: ax.set_xlim(xmin, 2*xmax) ax.figure.canvas.draw() line.set_data(xdata, ydata) return line, ani = animation.FuncAnimation(fig, run, data_gen, blit=False, interval=10, repeat=False, init_func=init) plt.show()  So you can just copy and paste all of this into VSCode, then use ctrl+s to save it, and let's save it in the Documents folder as test.py - the .py extension is for python files. Before we talk about our code, let's see it run! Open up a terminal, and run cd Documents to get to your documents folder, ls to see what's in there, then ./test.py to run the program. ╭─vega@lyrae ~ ╰─➤ cd Documents ╭─vega@lyrae ~/Documents ╰─➤ ls test.py ╭─vega@lyrae ~/Documents ╰─➤ ./test.py  Oops! that probably didn't run. If you look at the errors it will tell you you're missing matplotlib ad numpy, let's go get those ╭─vega@lyrae ~/Documents ╰─➤ yay -S python-matplotlib python-numpy  Now it should work! run ./test.py again, and now you should see a decaying sine wave. Still not exactly something that get's the heart racing, but it does prove the power of programming! The code did all of that in under 50 lines of text! Frankly, the code that makes this work is a bit complicated but we can go over some of the important bits at the very top there are four important lines: #!/bin/python3 import numpy as np import matplotlib.pyplot as plot import matplotlib.animation as animation  the first line uses a shebang #! followed by python's location, this tells Linux to use python (specifically python3) to run the code underneath, actually, that's the location of the python program we installed earlier. In Linux, most of your programs can be found in /bin Next we have a bunch of imports. In most programming lanuges you don't want to reinvent the wheel so you'll use libraries. These are well documented, heavily tested, and optimized blocks of code you can use that you don't really need to understand how work under the hood, only how to use them. Although not used here, the most basic example would be advanced math in the math library, like ╭─vega@lyrae ~ ╰─➤ python Python 3.7.2 (default, Jan 10 2019, 23:51:51) [GCC 8.2.1 20181127] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import math >>> math.sin(1) 0.8414709848078965 >>> math.pow(2,4) 16.0 >>> exit()  on line 6 the math library, which gave us access to sin and exponent functions, was imported. We don't know how math.sin() works, but we know it does, and that's fine. The same is true for numpy and matplotlib above, both of these are libraries, matplot lib is what handled actually putting the data on the screen, and numpy as can be seen on line 12 of the program: yield t, np.sin(2*np.pi*t) * np.exp(-t/10.)  is used for doing some of the math. Numpy is a common python library used for doing more advanced math really fast, we're not going to worry about that right now though. the next thing you should notice is how the code is organized into blocks with def name(): like def data_gen(t=0): or def init(): these blocks of code are called functions and they let programmers break up code into re-usable pieces or just wrap up a lot of complicated things to make code more readable, for example imagine a function that takes two numbers and does hundreds of lines of complicated math with them (eww) def mathyMess(num1, num2) num1 = math.sin(num1) + math.pow(num1,num2) # imagine hundreds more lines here return result  this would make it so latter in your code anytime you needed to do this math again you could just use thing = mathyMess(42, 12) otherThing = mathyMess(0, 2) finalThing = thing + otherThing  this is much, much easier to read than a copy and pasted version without these functions or 'blocks of code' furthermore, if you accidentally made a mistake somewhere in the math in mathyMess you can fix it there rather than in each independent copy individually. For now, we're going to take a bit of a break from code, but we'll be back. Okay, so what? So, yeah, you can develop python just fine in Windows. Installing it is just a matter of going online and fetching an exe installer and checking the right boxes. There's nothing here you can't do in windows. If that's the case why do any of this. Frankly the answer is complicated. The gist of it is that Linux actually exposes things in a way that while might be possible in windows will probably be much more difficult. Even in the above, when we installed python and a few libraries there was no need to open a web browser and each package is maintained and verified in a way that makes installation easy, secure, and reproducible. But more than that, Linux actually exposes the system to the user and doesn't try to hide it's inner workings, rather, for many things Linux implies that you should manually edit the config files, look at how programs use various resources, and peer into how the system actually handles any given task. You'll start to see this more as we move forward though these next few chapters. Speaking of... Chapter 3 - Into the hardware One of the nifty things about Linux is you don't need to install extra software to check out the deeper parts of your hardware. While on windows you might need a tool like CPU-Z to look at information about the CPU on Linux you can do it out of the box. Let's get started on that then! The CPU These are CPUS or Central Processing Units. They're the beating heart of your computer, doing the day-to-day number crunching. The rectangular one of one of the first CPU's in the lineage leading up to CPU's like the ones used in desktop's today, with further sucessors shown in order from top left to the bottom right. The metal-capped one at the bottom right, while old, is visulally quite representative of a moden desktop CPU, though the CPUs in a laptop or smart phone do look quite differnt still. One of the nifty things we do pretty easily in linux is get information about our hardware directly. Just as when we were installing Arch and we used lsblk to see an overview of the disks on the system, we can use some other tools to find out some other information about the system. Let's start off basic and see what CPU you have. Go ahead and run ╭─vega@lyrae ~ ╰─➤ cat /proc/cpuinfo  This is actually just using that same cat command we used before. This time we're using it to read the system generated file that tells us about the processor in this system. I'm going to provide the output from my system for reference: processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 1 model name : AMD Ryzen 7 1700 Eight-Core Processor stepping : 1 microcode : 0x8001137 cpu MHz : 2018.119 cache size : 512 KB physical id : 0 siblings : 16 core id : 0 cpu cores : 8 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca bugs : sysret_ss_attrs null_seg spectre_v1 spectre_v2 spec_store_bypass bogomips : 7688.44 TLB size : 2560 4K pages clflush size : 64 cache_alignment : 64 address sizes : 43 bits physical, 48 bits virtual power management: ts ttp tm hwpstate eff_freq_ro [13] [14]  Alright, that's a whole lot of information, let's break it down. First of all, almost all modern Central Processing Units (CPUs) have multiple cores, and as with most things in computers the're counted from 0, so on a 4 core computer you'll have cores 0, 1, 2, and 3. Multiple cores simply let your computer do things in parallel, running multiple programs or tasks at the same time Next is the vendor ID, family, model, name, and stepping. My processor is an AMD Ryzen 7 1700. There's a pretty good chance your CPU will be made by Intel, and as such the family, model, name, and what not will reflect that. AMD and Intel are practically the only two laptop and desktop CPU providers, though in the feature we'll work with boards that use CPU's made by other manufactures. Really, most of this doesn't matter. Some CPUs are nicer than others, and if you follow the market or care it's easy to get a sense of a CPU's speed just based on it's name, but let's move on for now. Next is microcode : 0x8001137 cpu MHz : 2018.119 cache size : 512 KB  Each of these things is very important, but I'm going to start with cpu MHz as it's probably the easiest to understand, however, to understand this we'll need to get even a bit lower level than this and learn about the electronic component that changed humanity: the transistor. Clock Speed However, to get to that we've gotta go just a bit further down the rabbit hole to the relay. Relays are super simple to understand, they're just a metal switch that is pulled open or closed using another input signal (usually a magnet pulling/pushing the switch closed/open) basically imagine a light switch, where the switch itself is controlled by yet another electrical signal. Relays are slow though, they require a physical metal plate to move to change the connection. Because of this they have limited reliability and worth note they're actually loud. You can hear an audible click of the switch as they change state. Enter the vacuum tube. Though rarely used today outside of high end audio and old radios, for a period of time the logic inside a computer used these tubes. Essentially theres three important parts of the tube, the Cathode, Plate and Grid. Put very simply the Cathode emits electrons and the Plate collects them. Where it gets interesting is the grid in between. By applying a voltage to the grid a signal can be controlled giving us the same ability to turn something on or off by a third wire as in the relay. Worth note but irreverent for digital electronics, tubes and transistors can actually pass only a percentage of the input back out, based proportionally on the input. This actually means that both tubes and transistors can act as an amplifier, using a small input range to control a much larger signal. A single tube or transistor in conjunction with other supporting components can be used to make a functional amplifier. Though the real break though here was the fact that this was no longer a mechanical system. With relays there was a very slow limit on the rate at which they could respond reliably, but with tubes this increased exponentially. Tubes were still expensive, large, and power hungry though. However, with their advent early computers saw a massive boost in speed with a decrease in cost Finally, enter the transistor. The physics here isn't that far removed from the vacuum tube, only now instead of a vacuum the electrons are moving though a semiconductor - typically silicon. Again this brought a massive shrink in physical size and increase in that rate at which it could respond. Pictured above are two discrete transistors, however, this is where things get mind blowing: The Ryzen 1700 CPU in the computer I'm typing this on has 4,800,000,000 transistors in a package that is only 213 mm², and finally, we can refrence the number output by cat /proc/cpuinfo At the moment I got that output the transistors where being turned on and off at a rate of 2018Mhz. or 2Ghz. However, this system can run up to roughly 3.8Ghz. The faster this speed the faster your computer; however, your CPU will also use more power and run hotter. It's for this reason that most systems adjust the speed based on load. Doing simple things like writing this document and as seen with that output my system runs at nearly half speed which is actually the slowest it can run. Because the computer is hardly doing anything right now the majority of that switching is actually just doing nothing but using power running 'no operation instructions' the functional equivalent of just running 0+0 while it it waits for something to do. The OS itself actually tells the processor what speed it should be running at. In Windows, when you change your power plan to 'high performance' one of the major things it does is not allow the processor to run at a slower speed, and in Linux you can similarly control this using some cpu speed commands. We'll get to that later though. Finally it's worth note that on some systems, primarily high end desktops, you can actually run your processor outside of factor specifications by increasing the maximum clock rate of the processor. Doing this can lead to system stability issues and obviously leads to a higher power usage and heat output though. This process is known as 'overclocking' as your taking the internal clock of the processor beyond it's rating. My CPU, a Ryzen 1700, has actually been over clocked in order to get 3.8Ghz at all times on all of the cores. Microcode Modern processors are very, very complicated. So complicated in fact that there is a full very tiny computer in your processor. This computer does multiple things, but the main one we'll talk about is the translation between types of machine code. In order to understand this we'll need to look a basic program written in the language 'C'. int main() { int a; int b; a = 8; b = 16; a = a + b; return 0; }  This code first makes two integers, a and b, gives them values, then adds them together and stores the result back into a. Finally, the program returns a 0 to the operating system in order to say "I ran without errors". Unlike python which get's converted to something the computer can understand as it executes C is compiled before hand. This makes it so programs written in C are much, much faster than those written in python, though obviously C code is more difficult to write. Compilation is the process of turning a program into a file full of instructions the computer actually understands. This happens in two steps, first the program is turned into assembly code, for the above code this results in an output that looks like  push rbp mov rbp, rsp mov DWORD PTR [rbp-4], 8 mov DWORD PTR [rbp-8], 16 mov eax, DWORD PTR [rbp-8] add DWORD PTR [rbp-4], eax mov eax, 0 pop rbp ret  As you can see, this is incredibly difficult to read to a 'normal' person, so even though we're not there yet. This in turn gets turned into binary as can bee seen by this screenshot generated using https://godbolt.org/ See the weird numbers next to each instruction? like 4004b255? That's a base 16 number or hexadecimal usually refered to as 'Hex'. Hex is what is used by most computer guys to represent numbers because computers operate in base 2, or binary- like 01001100, which is very difficult to read and type accurately, however, base 10, the normal numbering system your used to, makes translating between binary and decimal a bit uncomfortable as the common factor is 5, an number that is both odd and in turn not a factor of two, where as 16 is $$2^4$$ so that means we can easily represent binary like this: Binary Hex Decimal 0000 0 0 0001 1 1 0010 2 2 0011 3 3 0100 4 4 0101 5 5 0110 6 6 0111 6 7 1000 8 8 1001 9 9 1010 A 10 1011 B 11 1100 C 12 1101 D 13 1110 E 14 1111 F 15 Okay, so now those 1's and 0's are what your computer actually reads to run instructions. We'll come back to this later, but since we're here I'll drop this link Where you can see how these 1's and 0's are arranged to tell the computer what to do. That is super advanced for where we are now though, so let's get back on track- what the hell is micro code already? Well, it turns out that modern processors are still compatible with some really, really old code. All the way back to the first 8086 processor made by Intel in 1978. It was here that the x86 instruction set - the instructions like 'mov' , 'push', and 'add' above that define the x86 architecture were born. Originally these were 16bit CPUs, that is each instruction only had 16 1's and 0's but soon the i386 came along and used 32bits. Back when 32 bit computers were common this is what this was in reference to. As with all things technology progressed and 64bit cpu's came along. Many attempts were made to make 32bit programs run with backwards comparability at high speeds on these CPU's, though in the end AMD made the method used today, dubbed the x86_64 instruction set. Overtime this instruction set was expanded with various additions. We can actually see the names of these additions that are available on the CPU in the system by looking yet again at the output of cat /proc/cpuinfo and looking at the flags section. While not all of these signify instruction set additions, many do. The most common 'famous' if you will is SSE, of which there have been multiple revision, the first version alone adds 70 instructions, which are used to make math faster Alright, so finally, enter Mircocode. At some point all of this became a lot to manage and processor designs evolved even further, getting exponentially more complicated and faster with more and more instructions, so they added this little computer which has the primary duty of turning the mess of countless possible instructions into yet even smaller instructions that the heavy duty 'real' processor does. Every once in a while a problem will be found in the way this is done, or a security vulnerability in the hardware itself may be found, and your CPU manufacture will release a microcode update. That update version is what you see on that line of cat /proc/cpuinfo Now, at the beginning of this guide I said I wouldn't provide useless information, and I'm sure that all looks pretty useless without more context. In general, this is interesting because you can (and will need to) write some assembly code by hand every now and then. Thankfully, its usually not x86 assembly which is very, very difficult to write but instead assembly on much smaller, micro controllers (basically really tiny computers), where that assembly is necessary because the system is so limited. Cache Okay, next up is cache. Cache, just like in the real world, is a small place to store things. Most people like to think the majority of what a computer does is raw number crunching, doing hard math, but the truth is more often than not it's just moving data around. This follows a path from slowest and cheapest storage up to the fastest but most expensive. Typically this order looks a bit like Hard Drive -> Solid State Drive -> Ram -> Cache -> Registers , where the price for storage on a hard drive can be under \$$0.10Gb, Ram upwards of \$$10Gb, and Cache and registers, which are storage baked directly onto the CPU, cost much, much, more to implement. It's of note that these not only are digitally faster with each jump, but also usually physically close. A hard drive can be 10's of feet of wire from the CPU while the RAM can be a few inches at best, and the cache and registers are physically in the CPU dye. Most of the data above the HDD/SSD level is actually just smaller subsets of each previous pool. In fact, on modern CPU's there are actually usually 3 levels of cache, each with a progressively smaller size but increase in proximity to the executed instruction. Put simply, just as with adding more Random Access Memory (RAM) to your system, having more cache means more information can be within arm's reach of the CPU to do work on at any moment. Let's take a look. install the hwloc package using yay and then run lstopo and you should get an output that looks a bit like this The stuff on the right are connections around the system, you can ignore those for now, but see the various cache layers, designated by L3, L2, L1d and L1i, and you can see how each core has it's own cache. Finally, you can see that each core has two processing units? Hey, wait, what's that all about? Hyper threading, or SMT, or whatever the new term is for it, is a way of adding paths for doing things to keep every part of the CPU active. We'll go into this more later, but for now, suffice it to say it's a way of getting just a bit more performance out of a system. Interrupts While not listed in the /proc/cpuinfo output , it's still relevant to bring up CPU interrupts, which are, fittingly, listed in /proc/interupts Output of cat /proc/interupts on my system Output of information for the first 3 cores on my system displayed graphically using Netdata CPU interrupts are a bit confusing because the term interrupt can refer to the action itself, the code that executes, or the general concept. In general a CPU interrupt is when something needs to poke the CPU to tell it to interrupt what it's doing. This can be when physical pin in the CPU gets a signal, a timer going off, or a program dividing by 0. We'll cover this more in depth later, but from the hardware perspective what's relevant is the CPU is generally so fast compared to other actions that the rest of the system mostly just triggers an interrupt to let the CPU know that a task the CPU asked to be done has completed. The most common example is requesting data from disk (Hard drive or SSD) takes so long, even at just a few milliseconds, that the CPU can get millions of things done while it waits for the request to be fulfilled. So rather than waste that time having the CPU poke the device asking "Are you done yet? Are you done yet?" the disk (or the controller it's hooked up to, like the chipset) issues an interrupt to the CPU to let it know a task has completed. USB works in a similar way, though the really old keyboards with the circular connector (PS2) actually did interrupt the CPU directly on each key press. We'll come back and explore this more later, but if you're really interested you can read ahead by going over these links and reading these man pages: Oreilly on Interupts, Oreilly cont., man trap, man syscall, Power the CPU is one of the most power hungry parts of your computer, and as such it does some interesting things to try to keep it's power usage lower. Namely, it'll turn it's clock speed to do less operations per second as previously mentioned, but theres other things like entering sleep and hibernation states the processor is also capable of. The main thing you might want to concern yourself with from a performance to power consumption stand point is how aggressive this clock speed changing is. You can go as extreme as to tell the system to never let the processor get to full speed or to say 'only run at max speed all the time'. The latter is actually quite useful as often it can take quite a few clock cycles after a heavy load is started for the processor to come up to speed, but if it's always running full steam ahead this is a non issue. This entire topic is particularly relevent to laptops, and on Arch you may want to install a program to manage some of this for you or set sane defaults to save battery. I've had good luck using the tlp package. the cpupower package is helpful for looking at how arch handles cpu scaling and it lets you directly set these min and max frequencies or pick the scaling governor to handle how aggressive the switching is.https://wiki.archlinux.org/index.php/CPU_frequency_scaling#cpupower I very strongly recommend looking into this on any system though, as by default some CPUs will run at the minimum frequency only. We'll talk about delivering power to the CPU in a bit, when we talk about the Voltage Regulation Module (VRM) on the Motherboard. Physically, what and where is this thing? The CPU is on a square or rectangular board that is usually covered by a large heat sink used to keep it cool under load. It connects to the motherboard via hundreds of small, gold plated pins to send and receive signals (which well will discuss in depth later) from all around the system. Even though most modern CPUs are x86_64, generation to generation and cross manufacturer there are changes in the number of pins and the way they are arranged, meaning getting a new processor that's not from the same generation usually won't work. Furthermore, most laptops have soldered on processors that can not be upgraded to begin with. RAM This is RAM or Random Access Memory. The above two sticks are the normal sized used in desktop PCs, this form factor is called a DIM while the bottom two are from laptops and are called SO-DIMS, the placement of the notch is an indicator of the generation of RAM, with neraly all modern ram being a consecutive generation of the DDR standard. At the time of writing (Q2,2019) DDR4 is common in new, medium to high end devices, with many DDR3 devices still being used. Of note many more compact devices solder the ram chips directly to the board, meaning there is no form factor to consider. Just like the CPU, RAM has a speed at which it operates as well, Typically it's listed in MHz still, but speeds range from ~1.8Ghz to ~3.8Ghz at the time of writing, dependent DDR3 or 4. While DDR4 has faster clock speeds, it does typically have a higher overall latency, meaning theres a longer delay between when when data is requested to when it's delivered, albeit at a much higher total throughput. This is a massive topic in of itself, yet is also pretty niche as outside of some pretty specialized applications RAM speed and latency has a relatively minor impact, though faster is typically better. okay, let's move on to ram in Linux. While support for this will vary depending on your motherboard, you should be able to see information about your ram by running sudo dmidecode --type 17 The output will probably repeat multiple times, printing once for each physical stick of ram in your system. I actually have 4 sticks, but I'll just be showing one: You should note that many of the things mentioned above can be seen here, though I do want to look at some things here. First, size. This is an 8Gb or 8192Mb stick of ram. Obviously the more ram the better, but you may find strange ram configurations where there's a mix of ram sizes in a system. This can be bad for performance though, because of memory channels. Most modern systems use 2 or 3 memory channels, to simplify a bit, it makes it so two sticks of ram can have their speed be used in parallel. Think about it like a parking lot, if you have a total of 4 parking lots you could, theoretically, hook them all up in a straight line with one entrance/exit shared among them. This would be pretty stupid though, as it would severely bottleneck traffic going though. Instead you may want to add a separate entrance and exit for each, but that quickly becomes expensive. Instead, most systems use a mix of the two, connecting a pair of sticks together, allowing for added capacity, but allowing for multiple pairs to be inserted independently. A lot of people don't fully fill all the available memory slots on their motherboard though, so instead of having 4 lots with 2 entrances you should be able to have 2 and 2, unless you mistakingly put the sticks in wrong, leaving one 'entrance' closed entirely while the other now has a ton of capacity. On my motherboard these 'lots' are labeled A1, A2, B1, and B2. Looking above you can see the stick we're looking at here is the A1 lot. It's because of this that you should ideally have a multiple of as many sticks of ram as you do memory channels. For example, if you have a two channel motherboard and CPU then you want either 2, 4, or 8 sticks of ram. Most motherboards top out at 4 sticks though, with 2 channel and 2 sticks being the most common configuration. Next, I want to look at the line that says 'Type Detail: Synchronous Unbuffered (Unregistered)' this is referencing another type of ram, which is buffered and error correcting (ECC) memory. This type of ram is almost strictly used in servers and is special because there's actually an extra physical memory die on the card. If you look above you'll notice each stick has sets of 8 black memory dies. ECC memory actually has 9 dies. The reason there are normally 8 dies is simple- there's 8 bits in a byte. Servers don't work on some magic 9-bit in a byte system, instead, this extra bit per byte is used to ensure the data hasn't been corrupted. The math behind this can get complicated and weird, but for now let's just go with it. Buffered memory is basically just adding an extra 'buffer' between the read/write and again, it's a server thing. Finally I want to point out the voltage. Much like a CPU the voltage a Ram module runs at is important, and needs to be kept very stable. However, it may need bumped up if the RAM is running at a particularly high speed or if it's set higher than factory (overclocked). Some RAM actually includes a special memory profile, often called XMPP, which can be applied in the BIOS/UEFI settings to make sure you're getting the absolute best performance out of you RAM before manual overclocking. This may actually overclock your CPU a bit as well as a bit of a side effect. There's a program on your system called free which can be used to see how much RAM you have, how much is in use, etc. Let's run free with the -h flag so we can see the amounts with nice units. ╭─vega@lyrae ~ ╰─➤ free -h total used free shared buff/cache available Mem: 31Gi 4.5Gi 23Gi 488Mi 3.3Gi 26Gi  You can see I have 32Gb of RAM total (it get's truncated to 31 because it's actually like 31.99, units are weird), with ony 4.5Gb used. Most people complain about Chorme eating all their RAM but the truth is unused RAM is wasted RAM. The OS will manage RAM for you, and if you run out start using swap (that partition we made eariler). Let's take a deeper dive, reading the man page for free with man free we can see it uses information from /proc/meminfo, so lets look at that file ourselves using cat /proc/meminfo. One of the most interesting things to point out here is the concept of Dirty memory. 'Dirty' memory is the amount of information that has been modified in memory, but that has not been saved back onto the permanent storage (SSD/HDD). If you were to suddenly lose power this information would be lost. Pagefaults and misses are also important. Because these topics are a bit hard to summarize I'm going to recommend you read the Wikipedia page on Pagefaults and on Cache Misses. It's okay if you don't understand everything you're reading. Hopefully as you read more later and gain more experience the terms you didn't know will 'click' and you'll understand. Going back to when cache was mentioned though, RAM's primary job is to hold bulk information that's in use a bit closer to the CPU. For example if you load a large image file it'll first get copied to ram and then be processed though cache in chunks, this is because there just simply isn't enough cache on the CPU to hold a large image. The Motherboard This is an older motherboard, but still new enough to have modern parts. Let's start by looking at the the most obvious physical features and move to smaller things from there. The most obvious thing to point out is the size of the motherboard. This is a mATX motherboard, which is considered the normal size for most systems. Most gaming or DIY computers will use full size ATX motherboards, which look very similar but are a bit longer vertically, allowing for more expansion slots - those horizonal black bars - among other features. Other formfactors include ITX, a smaller form factor with only a single expansion slot, eATX (extended ATX) which is rarely used now, and SSI and EEB which are both server motheboard sizes. The large, white square is the CPU socket. This is an older board made for an AM3+ processor. The AM3+ processor line, as well as most consumer processors from AMD use a PGA or Pin Grid Array socket. these CPUs have many pins on the bottom which fall into these holes to make contact. Before the CPU is inserted the metal leaver arm, seen at the bottom of the socket if you look carefully, is raised and the CPU should smoothly plop right in, after which the arm can be lowered. Modern Intel CPUs follow a similar-ish mechanism, only instead of having a bunch of pins that go into holes the 'pins' are actually tiny springy pieces of metal on the motherboard which make contact with pads on the CPU, that socket looks a bit like this, albeit this is an old one: If you're looking at a server or high end workstation you may actually run into a single motherboard with multiple CPU sockets. These are becoming less common with time, but even though there are multiple CPUs the system still operates as one larger system. For example, I have access to a system with 4, 8 core, 16 thread cpu's to give for a total of of 64 threads. Giving this beautiful sight: Clearly, a server with that much horsepower will use a lot of electricity though, and there is some overhead for the system when getting information from one physical CPU to another. Above and left of the CPU on you'll see a bunch of copper coils in little boxes and some small metal cylinders, as well as a cluster of these with a large, 4-hole plug a bit further left, directly above the big aluminum heat sink. This all makes up the VRM or Voltage Regulation Module. The connector there is where the CPU power plug from the PC power supply would be plugged in. The power needs to be carefully controlled, filtered, and adjusted based on the needs of the CPU, that's what all of this is for. Generally the beefier and faster a CPU, the larger the VRM. The VRM also needs to dissipate a good amount of heat on higher end systems so many nicer motherboards will cover this up with a large heatsink. Moving on from the CPU you'll see 4 vertical slots next to socket, these are where the RAM sticks are inserted. You'll notice they're color coded as to indicate which slots share the communication channel, so in this case you'd want to put the first memory stick in the blue slot closest to the socket, followed by the black slot closest to the socket, then repeat. While we're looking at this side of the board- next to the RAM slots you'll see two things of note. First, that black circular thing is actually a little buzzer. A lot of even modern systems have these on board to buzz error codes out in morse code if something goes wrong. Below that is a large, 20 or 24 pin connector (most modern systems use the 24pin varient) which is where the power supply is plugged in to provide power to the motherboard (with the exception of the CPU) as well. On the other side of the CPU and down a little you'll see a sizable metal heatsink. This is covering the chipset. We'll come back to what the chipset does in a bit. This motherboard is actually a bit weird, on most motherboards the chipset is found almost directly below the RAM, but in general look for a large heatsink and it's probably under that. Below the chipset here are 4 expansion slots, all of which use the PCI-e standard in this case. We'll come back to these in a bit. In the bottom right of the motherboard there are 6 SATA connectors, here each is a different color (for no apparent reason?). These are for connecting storage like hard drives. Vertically in line but closer to the center of the board you'll also spot a coin cell battery. This is so the system can keep time with use of an on board Real Time Clock (RTC) even when fully powered down and disconnected from wall power. Along the bottom you'll see various connectors with pins sticking out, these are mostly for front panel connections- where the USB, audio, power button, etc. from the front of your case connect. Finally, along the top of the back left edge you'll see the metal tops of the main 'rear i/o' for the computer. These are all the main connections for your system. The bulk of the system's USB ports, networking, and audio ports will be found here. So, how do we get any information from the motherboard? Well, in case it wasn't already obvious, the motherboard isn't really one thing. It's more a common interconnect point and routing system than anything; however, it does have some of it's own responsibilities. To start small let's look at one small, but exceedingly import role of the motherboard: fan and temperature control. To see what your fans are doing on Linux you'll need to grab the package lm_sensors with yay, then you can run run sudo sensors-decect and mash enter until it's done. After this you should be able to run sensors and see an output similar to this one: Of note, depending on your system, there's a small chance nothing will be detected at all or that some information will be wrong. Even in my case this is true as my CPU fan is reporting 0 RPM. Actually entering your motherboard's UEFI or BIOS settings may expose more information, but we'll talk about that more later. Alright, so that's coll and all, but what else can you do? Alright, let's move on to seeing the system buses, namely, the pci bus. The pci bus is where most of the system's add in cards, controllers, and the like connect. Here's a shortened version of the ouput of lspci from my system 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge ... 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 ... 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01) 02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller (rev 02) 02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller (rev 02) 02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port (rev 02) 03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) ... 03:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) 07:00.0 USB controller: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller 08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) 0a:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1470 (rev c3) 0b:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1471 0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] (rev c3) 0c:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64] 0d:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1) 0d:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) 0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function 0e:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor 0e:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller 0f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function 0f:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) 0f:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller  Alright, clearly there's a lot going on here, and on first glance it doesn't even look all that useful. But let's look deeper. From this output we can see some interesting things. Starting from the top you'll see there's a lot of internal AMD things that are just handling routing, really these probably don't matter. the first interesting things to look at is 01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01) which is telling me that my super speedy NVMe solid state drive is at the address 01:00.0 on the pci bus and despite being made by a consumer brand (I think mine's a Silicon Power? though I have another that's made by Samsung) the actual controller on the device is made by Phison, a reputable brand for NVMe controllers. next thing of note is 02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller (rev 02) 02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller (rev 02)  You can see here that I have a separate controller for my USB 3.1 ports and that it's sharing pci lanes with my sata controller. In theory, this means If I'm working one or both of these really hard, the other may be slower. next is: 07:00.0 USB controller: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller 08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)  What's interesting here is I have another 3.1 controller, on an entirely different set of lanes. Really, this is a fault of USB that it's not very clear, this is actually a USB 3.1 gen 2 controller, so each port has a top speed of 10gb/s, compared to the 5gb/s of the other controller. You'll also see that my network interface is being handled by an Intel network controller, despite this system having an AMD CPU. moving on: 0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] (rev c3) 0c:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64] 0d:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1) 0d:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)  Here you'll see some devices can actually use multiple IDs for one physical device. both of the 0c:00.x 'devices' are actually for the 'Vega56' graphics card (Often called GPU for graphics processing unit) made by AMD Radeon, while the 0d:00.x devices are for the GTX1060 card made by Nvida that I have in this system as well. Of note, having both of these in one system is exceedingly uncommon, and my use case is strange; however, It is common to see systems which have a gpu integrated into the CPU (which will still appear in this list) and have a separate larger GPU in the system as well. If you continue down this list you'll see there's yet another USB controller and a audio controller among other things. What's cool is this information relates back to something we saw earlier when looking at the CPU: See all those PCI ids on the right side, those directly correlate with a lot of the above. Finally, if you want a lot more information you can run sudo lspci -v to see even more info about anything, for example, here's the output about my GTX1060 GPU: 0d:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] Flags: bus master, fast devsel, latency 0, IRQ 78 Memory at f6000000 (32-bit, non-prefetchable) [size=16M] Memory at c0000000 (64-bit, prefetchable) [size=256M] Memory at d0000000 (64-bit, prefetchable) [size=32M] I/O ports at c000 [size=128] Expansion ROM at f7000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [128] Power Budgeting <?> Capabilities: [420] Advanced Error Reporting Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] Secondary PCI Express <?> Kernel driver in use: nouveau Kernel modules: nouveau  The most notable thing here is actually at the end: Kernel driver in use: nouveau Kernel modules: nouveau  tells us I'm using the nouveau driver and kernel modules instead of one of the alternatives on the Nvida card in my system If I wanted to I could switch this over to the proprietary Nvidia driver to get a pretty nice speed boost in some applications. I'm not really worried about this because I'm mostly just using the Vega56 card. The nvidia card is there strictly for CUDA support in some workloads. Much like lspci, there's also lsusb, which as you can imagine, tells us information about the USB devices on the system. I have a LOT of usb devices on this system so I'll just paste in a snippet: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6340 Microdia Camera Bus 001 Device 008: ID 28de:1142 Valve Software Wireless Steam Controller Bus 001 Device 006: ID 258a:0013 Bus 001 Device 005: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012  You'll see here that USB hubs, input devices, webcams, etc. all show up. Anything that's hooked up through USB should appear here. The device with ID 258a:0013 isn't really telling us anything though. What we do know is the first part is the USB Vendor ID. This is an ID that vendors of USB devices have to purchase to uniquely id their products. upon looking this id up online, it appears it's used for a generic USB keyboard. For completeness I'll mention, the first part of the id, the x's in xxxx:yyyy is the vendor id, while the y's are the product id. Finally, I'd like to mention dimdecode. according to the manual page: dmidecode is a tool for dumping a computer's DMI (some say SMBIOS) table contents in a human-readable format. This table contains a description of the system's hardwarecomponents, as well as other useful pieces of information such as serial numbers and BIOS revision. Thanks to this table, you can retrieve this information without having to probe for the actual hardware. While this is a good point in terms of report speed and safeness, this also makes the presented information possibly unreliable. we've already used this to get information about the system ram, but other things can be read as well. For example, going back to the pci slots from above running sudo dmidecode --type 9 will tell you what physical slots correspond to what bus address among other information, for a full list of available types simply look at the dmidecode man page with man dmidecode. Chipset The chipset is a chip usually located in the bottom right 1/4 of a motherboard underneath a heatsink. The chipset coordinates the data flow between the processor and most of everything else- excluding the few direct-CPU attached things like the Graphics card. Older systems had both a Northbridge and and a SouthBridge as two separate chips, but everything modern has just the single chip, as the Northbridge, which had memory the memory controller, isn't necessary on modern systems where the memory controller has been integrated into the CPU itself. For the most part, the chipset on a motherboard will match a certain CPU socket, that is each generation of CPU will have it's own chipset and socket; however, this is not always the case as sometimes one chipset may support multiple CPU generations or a CPU generation will work with multiple chipsets. This is the case with AMD's ryzen line where a first generation Ryzen CPU such as the Ryzen 1700 will work in a motherboard with an x370, x470, or x570 chipset, and a third generation Ryzen CPU such as the Ryzen 3700 will work in any motherboard with one of those as well, albeit running a generation mis-match may result in degraded performance or missing features (such as lacking PCIe 4.0). Finally, it's notable that the chipset typically acts as a PCIe lane 'splitter' of sorts, turning (usually) 4 lanes into may more so that more devices may be attached. This can be particularly important when many high bandwidth devices are attached though, as even though these lanes are split, there's still only that original 4 lanes of bandwidth to go around. Source Source Expansion slots Two PCI-e 1x expansion cards, one for USB 3.0 and one for audio. Of note, most motherboards have both functions built in. Most modern expansion cards connect though the PCI Express or PCIe bus. This standard, much like DDR, has gone though multiple generations of bandwidth doubling. Currently consumer devices offer up to PCIe 3.0 but devices with both 4.0 and 5.0 should be on the market shortly. PCIe cards are used for just about anything you could imagine, form adding a more powerful graphics card, more usb ports, a higher end sound card, to some more esoteric things like specific task accelerators (encryption, compression) or even a software defined radio. No matter what the device is you have to keep in mind its physical and electrical requirements. That is, do you have a slot long enough to accommodate the card and can you provide power to it. This may seem odd, but unlike most connections (think USB or Ethernet) which may support varying speeds (usb2 vs 3) but are still physically the same size, the more bandwith hungry a PCIe device, the larger the physical connection. The largest available is a 16x connection, while the smallest is a 1x. The most commonly used lane arrangements are 1x, 4x 8x, and 16x. The motherboard shown above has one 16x connector and three 1x connectors. If you have a card that is electrically wired for 4x it will definitly work in any slot physically designed for 4x or greater, and it will still work in a 1x slot of that slot is open ended- this means the 'back' of the slot is open, allowing the card's connector to go past the actual physical connection. Similarly, many 16x physical slots only have 8x actually wired. If you use a card which elecrically needs more connections it will almost certainly still work, but may have degraded performance. Similarly, if you have a card which expects a PCIe gen 3 16x connection but the best you have available is a PCIe gen 2 connection, it will run at half speed. To be extra clear: PCIe 1 @ 16x == PCIe 2 @ 8x == PCIe 3 @ 4x Similarly, putting a card which only supports PCIe Gen 2 into a Gen 3 slot will not suddenly make the card faster, even if it was to compensate, that is, if the card is made for PCIe Gen 2 @ 16x and you put it in a PCIe Gen 3 @ 8x slot, it will still run at half speed because it's the lowest gen number of the card or the slot that determines how many lanes are actually needed. Unfortunately, PCIe lanes, that is if you add together all the available 16x's and 8x's etc. on a given CPU are usually pretty limited. If the only extra card you plan on adding is a graphics card, you'll be fine, but if you intend to add a graphics card, sound card, network card, etc. all at once you may find that you've either run out of physical slots or that a card is running with less than ideal bandwidth as a 16x slot may 'give up' 8 of it's lanes becoming an 8x slot so that another card can function at all. Of note, the number of physical lanes and slots the mother board has probably greatly exceeds the number of lanes actually going to the CPU, so even if it appears you have plenty of room to add cards you may end up accidentally starving one for bandwidth. Finally, from a power perspective most motherboards will supply up to 75 watts to a card through the motherboard, but power hungry cards like the Nvidia and AMD graphics cards in my system may require external power connections. Also, some server boards cap PCIe power delivery to only 25 watts without an external power supply, so just be careful with compatibility. There are some other standards other than PCIe worth mentioning though. Older standards such as PCI, AGP, and ISA were all used before the widespread adoption of PCIe and while their availability is declining, PCI cards are still often for sale, you need to be very careful to only get PCIe cards and not PCI cards if your system doesn't support them. Both AGP and ISA have been phased out a long time ago, but very old cards may poke up now and then. If you're into vintage computers you may want to look the standards up to learn more. Top: a 16x pci-e graphics card and a 1x pcie networking card Bottom: an ISA networking card and an AGP graphics card, not pictured is the PCI connector ROM/BIOS/UEFI Motherboards have to coordinate the communication of all the peripherals on the system and their own internal buses, furthermore, they have to have some sort of minimal configuration settings for setting things like which drive to boot off of or what speed the CPU or RAM should run at. These configuration settings are stored in some ROM or 'Read Only Memory', which is an independent chip on the motherboard. This configuration is read by the Binary Input Output System (BIOS) or the Unified Extensible Firmware Interface (UEFI). UEFI is essentially just the newer replacement for BIOS, and usually includes a compatibility mode for BIOS based hardware. When you first turn on the system you can typically mash either the delete or F12 key to enter this configuration page. It's typically from this interface that you'd select your boot device, change your CPU or RAM clock speed, and set the system time. On that note, the system also likely has a battery on board which power's the on-board real time clock, which allows the system to maintain the time even when disconnected from power. On some systems the ROM is actually volatile meaning if this battery dies and the system is disconnected from power you may loose the BIOS/UEFI settings. Of note, you may need to update the UEFI or BIOS of a system which is sometimes done via a special admin command within windows but more commonly done by downloading a file to flash drive, putting the drive in a specific usb port, and loading the update file. When this is done it's common to lose all UEFI/BIOS settings as well, as it overwrites the ROM. Finally, it should be noted that it's pretty easy to make your system not boot or boot-loop if you break things here. So, be careful. If you set your fan speeds slower to make the system quieter then everything overheats and dies, well, ヽ（´ー｀）┌ Because this varies per motherboard there's no universal way to describe how it looks or works. Some boards will support a lot more configuration than others, with really the only nearly definite options you'll find at the time of writing being a switch to enable virtualization extensions (for running virtual machines) and a switch to turn of Secure Boot, which you likely had to do to install Arch to begin with. VRM The VRM or 'Voltage Regulation Module' serves a simple but important task of ensuring that the CPU (or processor in question) receives a constant voltage or voltage that makes sense for it's current clock speed. Essentially the VRM may contain multiple stages of current and voltage regulation modules. The more of these stages the more stable the voltage and the more current can be delivered. For most cases, this can be left alone, but it's incredibly important when over clocking, as to overclock a CPU or GPU it's usually necessary to increase the voltage, which is typically done from within the BIOS/UEFI or from a configuration utility inside the OS in the case of the GPU. You can typically tell how strong a particular VRM is by counting the number of 'chokes' on the board. [TODO, add pictures of chokes] Graphics Card (or integrated graphics) A wide array of graphics cards spanning multiple generations. The majority pictured are made by Nvidia Most 'beefier' systems have a graphics card, but (almost) every computer that can output a video signal has dedicated graphics processing of some sort. For many lower end or low power systems (especially laptops) this graphics processing unit, or GPU, is built into the CPU and uses the systems same ram for video. For larger systems there's typically a larger graphics card (often the graphics card is called a GPU as shorthand; however, the GPU is technically just the processor on the board), which is a separate device hooked up though an expansion connection (like PCIe). Typically these cards differ from their integrated into the CPU counterparts in that they're much, much faster and drink much more power. In general the GPU is required because while CPUs are great at very fast consecutive operations like taking '1+1=a, a+1=b, b+1=c' the GPU is really good at parallel operations like '1+1=a, 2+2=b, a+b=c', where both of the first two operations can be done at the same time by different processing units before being manipulated together in the third operation. In reality, this is because the modern GPU really only treats pushing color data to the screen as a secondary operation, instead it's main purpose is to do complex matrix and vector math which is what goes into drawing polygons in a 3D scene, and these matrix operations are massively parallel. So while a CPU has at the high end a dozen cores, a GPU may have multiple thousand. These cores are much more limited in what they can do of coarse, and typically run at a lower clock speed than the CPU, but for their purpose they absolutely shred though large data. This has given rise to GpGPU Computing, or General Purpose Graphics Processing Unit Computing, where in the GPU is used for things other than graphics, like accelerating data base searchers or training AI models. As a brief note, historically graphics cards served primarily to actually draw to the screen, with some only having a fixed number of characters they could draw for rendering a text interface and others having a quite limited color palette that dictated how final images would look. Today, there are three primary manufactures of GPUs: Nvidia, AMD, and Intel. The largest player in the space, Nvidia, makes cards targeted primarily to gamers in their GTX and RTX lineup, and has cards meant for professional/compute tasks in their Tesla and Quadro lines. While the two lines are very similar technically they vary mostly in drivers and compute bit depth, with the professional cards providing the ability to do higher resolution floating point calculations easier. This is primarily done for market segmentation though- to prevent professional from buying the much cheaper (albeit still far to expensive) 'gaming' cards. All of Nvidia's cards support CUDA, a programming framework that makes it easier to take advantage of Nvidia's cards for GpGPU purposes. AMD is currently offering little competition to Nvidia in the high end; however, their more midrange cards have found great success as they perform plenty well for the majority of games and compute work loads at what is often a fraction of the cost. Of note, AMD cards do not support CUDA, though they do support a variety of open standards that serve the same purpose. This is still an issue though, as many programs that can take advantage of GpGPU acceleration depend on CUDA and therefor require an Nvidia card. Nvidia has frequently been quite hostile to the open source community and their drivers significantly lag behind in quality and performance compared to AMD's for Linux. Also of note, AMD makes many 'APU's or Accelerated Processing Units, which is just branding for their take on graphics integrated into the CPU. However, AMD's integrated graphics, at least at the moment, far out do Intel's offerings. Intel, at the moment, only offers integrated graphics that are less than stellar performers. Despite this, laptops with Intel Integrated Graphics are very common due to their low power usage. Intel's Integrated Graphics have very good drive support though, both on Linux and Windows. As of the time of writing, Intel is starting to send prototype graphics cards to vendors in a bid to break out of the integrated graphics only space. Moving into the actual hardware itself let's look at three graphics units, starting with Intel Integrated. Both Intel and Amd offer integrated graphics of various capability that usually pair reasonably well with the CPU they share the die with. Below is an image of the inner workings of a ryzen cpu with integrated graphics, showing the actual CPU cores (I believe this is a 4 core eight thread system?) in CCX0, the memory controller, and the very large Vega series GPU on the right. This looks to be a Vega11 GPU as you can count the 11 stacks of Compute Units in the GPU section. Of note, if you get a CPU with integrated graphics and don't actually use it because you're getting a separate, more powerful card , then you're effectively paying for a large amount of hardware you're not using. As you can see below, if the GPU was not there, there would be a lot more room to add more CPU cores or other features to the CPU to make it more powerful. Unfortunately, due to market segmentation even if the actual cost to add these extra cores would be the same or less as the iGPU's cost, a CPU of the equivalent size would likely be much more expensive. Finally, it should be noted the iGPUs share system memory for graphics memory, which is actually one of their most limiting factors- as system memory (RAM) is optimized for a different kind of access pattern, it is not nearly as fast as GDDR or HMB2, both of which are memory technologies that have been optimized for use with graphics devices. Source Moving on to graphics cards, Looking above at the stacks of graphics cards above, you'll probably notice that a graphics card is basically just a full separate motherboard and processor on a card. Really, this is pretty accurate, as there is a separate compute device (the GPU), ram (GDDR or HBM), and io (fan control, etc.) on the board. Of course, the Graphics card can't really be used as a full separate computer, but thinking about it as such isn't entirely wrong either. In fact, graphics cards really harken back to much older systems where it was common to add a math co-processor chip along side the CPU to make some mathematical operations faster. Storage Pictured here are 3 hard drives, 2 of which are 'full size' at 3.5" and the the other a 'laptop drive' at 2.5", the left most hard drive has been opened up, which has certainly ruined it as dust has gotten in. Below the smaller Hard drive is an NVMe ssd, a micro sd card, and a flash drive. All of which are examples of solid state storage Permanent storage is rapidly evolving, but the old guard: hard drives and tape storage aren't going anywhere either. But why use one over the other? How do you interact with them in Linux? [TODO] mention hdd, ssd, sata, nvme, usb-storage, sd, scsi, u.2, m.2, tape, floppy, zip hdparm HDDs Hard disk drives or 'HDDs' are sometimes called "spinning rust" because unlike other modern storage devices they're fundamentally mechanical. Looking at the delidded hard drive you'll see they're pretty simple in their basic construction: a magnetized needle(s) move across (a) platter(s) and flip bits accordingly. These platters typically spin at 5400 or 7200 RPM, with the faster meaning data can be read and written faster as well. Hard drives generally are not used for speed though, as compared to other alternatives they're extraordinary slow. Instead, they run at 'good enough' speeds for most things- like storing video, music, etc. while being much less expensive than solid state options and with a proven reliability and without suffering from data loss when left without power for long periods of time. That said, just like any storage medium, over time data can be corrupted, so backups are still a must. When a Hard drive is powered off, the head will typically 'park' off the platter (this is part of why the delidded plater above died, as it parked incorrectly) and transportation should be pretty safe, however, when running and spinning quickly they're pretty fragile, and this is why so many older laptops have dead drives: the gyroscopic effects of spinning something that fast make it resistant to a change in orientation, causing things to scrape, scratch, or otherwise go wrong. Thankfully most 2.5" hard drives have been hardened against this now; however, it's still a good idea to store and run hard drives with as much protection from vibration and shock as possible. In fact, yelling at a hard drive has been shown to hurt performance. At the end of the day, for bulk media storage that you still want to be able to access quickly or for backups, hard drives are still one of the best options. Most hard drives connect though either SATA or SAS, with almost all consumer drives being SATA, and enterprise drives using a mix. SAS has some extra features and depending on the drive may be capable of writing an reading at the same time, a nifty trick SATA drives can't do without alternating between the two rapidly. For bulk storage servers you can get insane capacities, and building one yourself isn't all that hard. Here's mine: A modified powervault MD1000 with a hard drive poking out and the computer - being used an archive server - it connects to. It currently is only housing three, 3Tb SAS hard drives. For working with hard drives in Linux you're best friend is hdparm lets use it to look at some disks. First we need to pick a disk to look at, running lsblk you should be able to see all the disks on your system, and I'll be looking at my main data drive which is a 3.7Tb drive on /dev/sdg The first thing we should do is get an idea about the disk usage, to do that I'll go to the mount point of the disk on my system ( it's mounted at /run/media/vega/raid despite the fact it's no longer in a raid array, we'll come back to this) so first I'll run df -h , that -h on most Linux commands means to make the output human readable, printing things in terms of Gigabytes or Terabytes etc instead of just a raw byte count. Filesystem Size Used Avail Use% Mounted on /dev/sdg2 3.7T 2.3T 1.5T 62% /run/media/vega/raid  Alright, so I already have the disk 62% used, let's give that a closer look by firing up ncdu at the mount point. This will take a little while to scan, the more files the longer it will take. After spending a few minutes to analyze the disk I'm greeted with this: From this you should be able to plainly see that the majority of the hard drive is taken up by Archived files, Music, Games, Videos, and Pictures. Pretty Mundane, but I could easily dive into the Archives and see why they're so big and save myself some space None of this is really all that interesting though, so what about speed? How fast or slow is the hard drive? Now is where hdparm comes in. Reading the man page you'll find the the -T and -t flags both perform disk read bench marks, one cached reads, the other raw, so let's run sudo hdparm -Tt /dev/sdg This gives: /dev/sdg: Timing cached reads: 22946 MB in 2.00 seconds = 11492.36 MB/sec Timing buffered disk reads: 556 MB in 3.01 seconds = 184.91 MB/sec  You should immediately notice that cached reads are absolutely insanely high compared to buffered, in reality it's because it was using RAM for cache, and RAM really is that fast. The reads of bulk data on the other hand? A little under 200MB/sec is actually quite fast for a hard drive. Anything between 1-200 is normal. You'll soon see that compared to SSDs though, this is kind of disappointing. But, moving on, another few interesting flags available in hdparm are -g which displays the "geometry" of the drive: cylinders, heads, sectors, etc., -H for tempature. This begs the obvious question: what are cylinders, heads, and sectors [TODO] Another thing of note is S.M.A.R.T tests, while not exclusive to hard drives, they're particularly useful for them as most hard drives give a lot of warning signs before failing out right. In order to get in-depth S.M.A.R.T info on your drive, you'll likely need to run a test first, after which you can view the results. To do this on Linux you can run yay -S smartmontools sudo smartctl -i path/to/disk  Finally, a quick note about Western Digital Green drives: Linux eats them. Thankfully you can use hdparm to fix this. From the man page: -J Get/set the Western Digital (WD) Green Drive's "idle3" timeout value. This timeout controls how often the drive parks its heads and enters a low power consumption state. The factory default is eight (8) seconds, which is a very poor choice for use with Linux. Leaving it at the default will result in hundreds of thousands of head load/un‐ load cycles in a very short period of time. The drive mechanism is only rated for 300,000 to 1,000,000 cycles, so leaving it at the default could result in premature failure not to mention the performance impact of the drive often having to wake-up before doing routine I/O. WD supply a WDIDLE3.EXE DOS utility for tweaking this setting, and you should use that program instead of hdparm if at all possible. The reverse-engineered implementation in hdparm is not as complete as the original official program, even though it does seem to work on at a least a few drives. A full power cycle is required for any change in setting to take effect, regardless of which program is used to tweak things. A setting of 30 seconds is recommended for Linux use. Permitted values are from 8 to 12 seconds, and from 30 to 300 seconds in 30-second increments. Specify a value of zero (0) to disable the WD idle3 timer completely (NOT RECOMMENDED!). Shouting in the Datacenter (YouTube) SSD Solid state drives, like HDDs, come in many capacites, speeds, and form factors; however, SSDs come in many, many more than HDDs. The primary two of note at the moment are SATA SSDs and NVMe SSDs. Sata SSDs are typically the same size and shape (though sometimes a bit thinner) as the normal 2.5" laptop hard drive; however, some other standards are used such as mSATA and m.2. Unfortunately, the m.2 spec is slightly confusing, with some drives being SATA based and some being NVMe based, and the m.2 slot itself supporting any mix (just SATA, just NVMe, or both), so when getting a drive you need to be careful that your motherboard's m.2 slot and the drive are compatible. The main reason you'd want to use NVMe is because it's much, much faster. NVMe drives are often many times faster than their SATA equivilents, and as of the time of writing, only slightly more expensive, albeit not supported on all systems. All SSDs regradless of type consist of 3 main parts: The Controller, the NAND, and some RAM. (okay, technically not all SSDs have ram, but that's sorta misleading) [TODO] Optane, NVMe, Sata, technically all flash, Ram disks, different controllers, MLC, TLC, etc. Cloud Storage (Some one else's drives) This is opinioned guide, so now that's about to show: Dont do it. All cloud storage is is someone else's disks. If you want to use it as a backup sure, but I don't see why- it's much less expensive to just backup the reallly important stuff to a hosted server continually and periodically (weekly, monthly, whatever) backup to some external disks that you keep somewhere else. Not to mention the privacy concerns. Like, really? You want to put allllll your family pictures under the all seeing eyes of Google or Microsoft. Nah. I'll pass. Portable Most fixed disk enclosures suck, albeit they can be less expensive. I'd recommend getting a portable multi-drive enclosure that runs over whatever the fastest connection you have is (Thunderbolt, USB 3.1, etc.). You can even get usb->nvme adapters, albeit they have a nasty amount of bandwidth limiting. Most off-the-shelf flash drives have ass cooling and will over-heat them selves to death when you use them for things like installing operating systems regularly, so I recommend just getting a bulk pack of cheap, low capacity ones to toss when they finally kick the bucket and a few nice USB->SATA or USB->NVME adapter for your main portable storage needs. Failing that, you can always use your phone if you've got a nice high capacity SD card in it or plenty of spare internal storage. The problem with that is MTP or 'Media Transfer Protocol' is a buggy, slow mess, and there's no other clean way to transfer things from a phone. So ¯\(ツ) The Past Floopy, Zip Disks, and Tape? Really? Yes. And yes, they're still used, so you should probably know at least a little about them. [TODO] Floppy, Zip, tape RAID and Disk Pools [TODO] Zfs, hardware raid, software raid, emulated hardware (bios), etc. Network Interfaces Pictured here are three Network Interface cards or a NIC. The three on the left are for WiFi (though some of this form factor may include bluetooth as well) while the one on the right has an ethernet port for wired access. Most computer's will not have a separate card for the wired interface though, as most motherboard's have a wired network interface built in. NICs also include the wireless chipset used for connecting to a cell tower and really any radio communication device in general. Older NICs include those used for Dial-Up connections and some obscure wireless methods that predate WiFi. Ethernet [TODO] rj45, ethernet over infiniband, speed bases WiFi [TODO] Channels 12, 13, 14. 2.4 v 5, wifi 6, weird authentication, etc High Bandwidth [TODO], infiniband, DMA, 10GbE+, Multigig At the end of the day, nothing is faster than a truck filled with drives. The Future [TODO] wifi6, 10gbe rj45 and beyond, cellular, sdr The Past [TODO] coax network, infrared, sneakernet Power Supply The Power Supply Unit or PSU does what you think. It takes power from the wall and turns it into power for the computer. This isn't the chapter on voltage and current, so I'll spare some of the details, but effectively you want a power supply that can deliver plenty of power and that has clean power. A given power supply usually has a rating like '500w' for 500 watts, but this is usually a bad indicator, as they could be refering to multiple things- you see a desktop power supply usually outputs multiple voltages (-12, +12, +5, +3.3) and each one of those lines will have a different maximum power output. Typically, the one that's most relevant is the +12 rail, as both the GPU and CPU will likely run on that and they're what draws the most power. So, you can actually check just this rail by taking the voltage (+12V) times the max current (amperage) on that line (let's use 20A) to see the max power (so 12*20=240 watts) Also note that the power supply itself may be of varrying quality, with the voltage 'ripple' and the efficiency being important as well. Voltage ripple occurs when the supposed-to-be 12V line instead outputs a signal that's varying a little, so let's say you measure the +12V line and it reads 12.2V now, then a minute later reads 11.8V, that's quite a bit of ripple when you expect a constant +12V. Generally you can trust the power supply is decent about this though so long as the power supply is also pretty efficient. Telling efficiency is easy too, as there's a nifty specification that most PC PSU's have called "80 plus" and it's rated by a metal-value system, so an 80+ bronze power supply is already (typically) much better than one without the rating, and an 80+ Gold is even better, going on up to Platinum. Most PC PSU's are in the ATX format, the same specification used to size motherboards, and the majority of desktops use a standard ATX power supply, though smaller systems may opt for one of the smaller standards such as SFX. Servers typically have their own power supplies which look a bit strange as they're basically the shape of an elongated brick, but they're like that so they can be easily swapped in and out. Often server power supplies are redundant so a new one could be put in while the system is still on in many cases. Main takeaway here, if some one is talking about an ATX PSU they're talking about the power supply in a desktop. Often they're (less than safely...) used in other applications as they're cheap and often easy to find used or salvaged from old systems. [TODO] add pictures Cooling Blower, air flow vs static pressure, fan size liquid, heat pipes, pwm vs DC control Peripherals Keyboards HID or Human Interface Device, is the standard over which most mice, keyboards, and game controllers talk to the computer. Unfortunately, it's also a pretty lame standard. You can't just input arbitrary Unicode or send fancy data back to the keyboard to control fancy RGB lights, because of this it's common to need extra drivers per device [TODO] 5pin din, PS2, USB Chapter 3.1 - How to know what to buy [TODO - possibly move] Chapter 3.2 - Legacy Hardware [TODO] Parallel, Serial, Tape, CD, gameport Chapter 4 - Back to the Root of Things We've been using file in /proc and /dev thoughout this, but we never really looked to see what else is in there. Let's do that. We'll actually start with /dev ╭─vega@lyrae ~ ╰─➤ cd /dev ╭─vega@lyrae /dev ╰─➤ ls -la total 4 drwxr-xr-x 22 root root 4600 Feb 8 06:03 . drwxr-xr-x 18 root root 4096 Jan 26 22:05 .. crw-rw-rw- 1 root root 10, 56 Feb 8 06:03 ashmem crw-r--r-- 1 root root 10, 235 Feb 8 06:03 autofs crw-rw-rw- 1 root root 511, 0 Feb 8 06:03 binder drwxr-xr-x 2 root root 520 Feb 8 06:02 block drwxr-xr-x 2 root root 200 Feb 8 06:02 bsg crw------- 1 root root 10, 234 Feb 8 06:03 btrfs-control drwxr-xr-x 3 root root 60 Feb 8 06:02 bus lrwxrwxrwx 1 root root 3 Feb 8 06:03 cdrom -> sr0 drwxr-xr-x 2 root root 5700 Feb 8 06:03 char crw------- 1 root root 5, 1 Feb 8 06:03 console lrwxrwxrwx 1 root root 11 Feb 8 06:02 core -> /proc/kcore drwxr-xr-x 2 root root 60 Feb 8 06:02 cpu crw-rw---- 1 root realtime 10, 60 Feb 8 06:03 cpu_dma_latency crw------- 1 root root 10, 203 Feb 8 06:03 cuse drwxr-xr-x 8 root root 160 Feb 8 06:02 disk crw-rw----+ 1 root audio 14, 73 Feb 8 06:03 dmmidi4 crw-rw----+ 1 root audio 14, 89 Feb 8 06:03 dmmidi5 crw-rw----+ 1 root audio 14, 105 Feb 8 06:03 dmmidi6 crw-rw----+ 1 root audio 14, 121 Feb 8 06:03 dmmidi7 drwxr-xr-x 3 root root 140 Feb 8 06:03 dri crw------- 1 root root 242, 0 Feb 8 06:03 drm_dp_aux0 crw------- 1 root root 242, 1 Feb 8 06:03 drm_dp_aux1 crw------- 1 root root 242, 2 Feb 8 06:03 drm_dp_aux2 crw------- 1 root root 242, 3 Feb 8 06:03 drm_dp_aux3 crw------- 1 root root 242, 4 Feb 8 06:03 drm_dp_aux4 crw-rw---- 1 root video 29, 0 Feb 8 06:03 fb0 lrwxrwxrwx 1 root root 13 Feb 8 06:02 fd -> /proc/self/fd crw-rw-rw- 1 root root 1, 7 Feb 8 06:03 full crw-rw-rw- 1 root root 10, 229 Feb 8 06:03 fuse crw------- 1 root root 254, 0 Feb 8 06:03 gpiochip0 crw------- 1 root root 254, 1 Feb 8 06:03 gpiochip1 crw------- 1 root root 240, 0 Feb 8 06:03 hidraw0 ------------------------------------------------------------------------------------ to make this output shorter I stripped out hidraw 1-5,10-12 ------------------------------------------------------------------------------------ crw-rw----+ 1 root root 240, 6 Feb 8 06:03 hidraw6 ------------------------------------------------------------------------------------ to make this output shorter I stripped out hidraw 7-9 ------------------------------------------------------------------------------------ crw-rw---- 1 root realtime 10, 228 Feb 8 06:03 hpet drwxr-xr-x 3 root root 0 Feb 8 06:03 hugepages crw------- 1 root root 10, 183 Feb 8 06:03 hwrng lrwxrwxrwx 1 root root 12 Feb 8 06:03 initctl -> /run/initctl drwxr-xr-x 4 root root 880 Feb 8 06:03 input crw-rw-rw- 1 root render 241, 0 Feb 8 06:03 kfd crw-r--r-- 1 root root 1, 11 Feb 8 06:03 kmsg crw-rw-rw- 1 root kvm 10, 232 Feb 8 06:03 kvm drwxr-xr-x 2 root root 60 Feb 8 06:02 lightnvm lrwxrwxrwx 1 root root 28 Feb 8 06:03 log -> /run/systemd/journal/dev-log crw-rw---- 1 root disk 10, 237 Feb 8 06:03 loop-control drwxr-xr-x 2 root root 60 Feb 8 06:03 mapper crw-rw---- 1 root video 239, 0 Feb 8 06:03 media0 crw-r----- 1 root kmem 1, 1 Feb 8 06:03 mem crw------- 1 root root 10, 57 Feb 8 06:03 memory_bandwidth crw-rw----+ 1 root audio 14, 66 Feb 8 06:03 midi4 crw-rw----+ 1 root audio 14, 82 Feb 8 06:03 midi5 crw-rw----+ 1 root audio 14, 98 Feb 8 06:03 midi6 crw-rw----+ 1 root audio 14, 114 Feb 8 06:03 midi7 drwxrwxrwt 2 root root 40 Feb 8 06:02 mqueue drwxr-xr-x 2 root root 60 Feb 8 06:03 net crw------- 1 root root 10, 59 Feb 8 06:03 network_latency crw------- 1 root root 10, 58 Feb 8 06:03 network_throughput crw-rw-rw- 1 root root 1, 3 Feb 8 06:03 null crw------- 1 root root 243, 0 Feb 8 06:03 nvme0 brw-rw---- 1 root disk 259, 0 Feb 8 06:03 nvme0n1 brw-rw---- 1 root disk 259, 1 Feb 8 06:03 nvme0n1p1 brw-rw---- 1 root disk 259, 2 Feb 8 06:03 nvme0n1p2 crw-r----- 1 root kmem 1, 4 Feb 8 06:03 port crw------- 1 root root 108, 0 Feb 8 06:03 ppp crw------- 1 root root 248, 0 Feb 8 06:03 pps0 crw------- 1 root root 10, 1 Feb 8 06:03 psaux crw-rw-rw- 1 root tty 5, 2 Feb 8 16:37 ptmx crw------- 1 root root 247, 0 Feb 8 06:03 ptp0 drwxr-xr-x 2 root root 0 Feb 8 06:03 pts crw-rw-rw- 1 root root 1, 8 Feb 8 06:03 random crw-rw-r--+ 1 root rfkill 10, 55 Feb 8 06:03 rfkill lrwxrwxrwx 1 root root 4 Feb 8 06:03 rtc -> rtc0 crw-rw---- 1 root realtime 250, 0 Feb 8 06:03 rtc0 brw-rw---- 1 root disk 8, 0 Feb 8 06:03 sda brw-rw---- 1 root disk 8, 1 Feb 8 06:03 sda1 brw-rw---- 1 root disk 8, 2 Feb 8 06:03 sda2 brw-rw---- 1 root disk 8, 16 Feb 8 06:03 sdb brw-rw---- 1 root disk 8, 17 Feb 8 06:03 sdb1 brw-rw---- 1 root disk 8, 32 Feb 8 06:03 sdc brw-rw---- 1 root disk 8, 33 Feb 8 06:03 sdc1 brw-rw---- 1 root disk 8, 34 Feb 8 06:03 sdc2 brw-rw---- 1 root disk 8, 48 Feb 8 06:03 sdd brw-rw---- 1 root disk 8, 64 Feb 8 06:03 sde brw-rw---- 1 root disk 8, 65 Feb 8 06:03 sde1 brw-rw---- 1 root disk 8, 66 Feb 8 06:03 sde2 brw-rw---- 1 root disk 8, 67 Feb 8 06:03 sde3 brw-rw---- 1 root disk 8, 68 Feb 8 06:03 sde4 brw-rw---- 1 root disk 8, 80 Feb 8 06:03 sdf brw-rw---- 1 root disk 8, 81 Feb 8 06:03 sdf1 brw-rw---- 1 root disk 8, 82 Feb 8 06:03 sdf2 brw-rw---- 1 root disk 8, 96 Feb 8 06:03 sdg brw-rw---- 1 root disk 8, 97 Feb 8 06:03 sdg1 brw-rw---- 1 root disk 8, 98 Feb 8 16:37 sdg2 drwxr-xr-x 4 root root 80 Feb 8 06:03 serial crw-rw----+ 1 root optical 21, 0 Feb 8 06:03 sg0 crw-rw---- 1 root disk 21, 1 Feb 8 06:03 sg1 ------------------------------------------------------------------------------------ to make this output shorter I stripped out sg2-6 ------------------------------------------------------------------------------------ crw-rw---- 1 root disk 21, 7 Feb 8 06:03 sg7 drwxrwxrwt 2 root root 80 Feb 8 16:37 shm crw------- 1 root root 10, 231 Feb 8 06:03 snapshot drwxr-xr-x 4 root root 760 Feb 8 06:03 snd brw-rw----+ 1 root optical 11, 0 Feb 8 06:03 sr0 lrwxrwxrwx 1 root root 15 Feb 8 06:02 stderr -> /proc/self/fd/2 lrwxrwxrwx 1 root root 15 Feb 8 06:02 stdin -> /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Feb 8 06:02 stdout -> /proc/self/fd/1 crw-rw-rw- 1 root tty 5, 0 Feb 8 15:49 tty crw--w---- 1 root tty 4, 0 Feb 8 06:03 tty0 ------------------------------------------------------------------------------------ to make this output shorter I stripped out tty1-62 ------------------------------------------------------------------------------------ crw--w---- 1 root tty 4, 63 Feb 8 06:03 tty63 crw-rw-rw- 1 root uucp 166, 0 Feb 8 06:03 ttyACM0 crw-rw----+ 1 root tty 4, 64 Feb 8 06:03 ttyS0 crw-rw----+ 1 root uucp 4, 65 Feb 8 06:03 ttyS1 crw-rw----+ 1 root uucp 4, 66 Feb 8 06:03 ttyS2 crw-rw----+ 1 root uucp 4, 67 Feb 8 06:03 ttyS3 crw------- 1 root root 10, 61 Feb 8 06:03 udmabuf crw------- 1 root root 10, 239 Feb 8 06:03 uhid crw-rw-rw-+ 1 root root 10, 223 Feb 8 06:03 uinput crw-rw-rw- 1 root root 1, 9 Feb 8 06:03 urandom drwxr-xr-x 2 root root 200 Feb 8 06:03 usb crw------- 1 root root 10, 240 Feb 8 06:03 userio drwxr-xr-x 4 root root 80 Feb 8 06:03 v4l crw-rw---- 1 root tty 7, 0 Feb 8 06:03 vcs crw-rw---- 1 root tty 7, 1 Feb 8 06:03 vcs1 ------------------------------------------------------------------------------------ to make this output shorter I stripped out vcs2-6 ------------------------------------------------------------------------------------ crw-rw---- 1 root tty 7, 7 Feb 8 06:03 vcs7 crw-rw---- 1 root tty 7, 128 Feb 8 06:03 vcsa crw-rw---- 1 root tty 7, 129 Feb 8 06:03 vcsa1 ------------------------------------------------------------------------------------ to make this output shorter I stripped out vcsa2-6 ------------------------------------------------------------------------------------ crw-rw---- 1 root tty 7, 135 Feb 8 06:03 vcsa7 crw-rw---- 1 root tty 7, 64 Feb 8 06:03 vcsu crw-rw---- 1 root tty 7, 65 Feb 8 06:03 vcsu1 ------------------------------------------------------------------------------------ to make this output shorter I stripped out vcsu2-6 ------------------------------------------------------------------------------------ crw-rw---- 1 root tty 7, 71 Feb 8 06:03 vcsu7 drwxr-xr-x 2 root root 60 Feb 8 06:03 vfio crw------- 1 root root 10, 63 Feb 8 06:03 vga_arbiter crw------- 1 root root 10, 137 Feb 8 06:03 vhci crw-rw----+ 1 root kvm 10, 238 Feb 8 06:03 vhost-net crw------- 1 root root 10, 241 Feb 8 06:03 vhost-vsock crw-rw----+ 1 root video 81, 0 Feb 8 06:03 video0 crw-rw----+ 1 root video 81, 1 Feb 8 06:03 video1 crw-rw-rw- 1 root root 1, 5 Feb 8 06:03 zero  Alright, I know what you're thinking. What. The. Actual. Fuck. And honestly, yeah. But first, lets talk about what we just did. Permissions if you run ls it normally shows you the all the folders, shortcuts, and files in a directory, except it excludes any hidden files. In linux you can make a file or folder hidden simply by naming the folder with a '.' at the beginning, so naming a folder .nsfw will mark it has hidden. Hidden doesn't really mean much though as most file managers allow you to view hidden files/folders by checking a box, and in this case, we can see hidden items by using the -a flag for ls. running man ls you'll see the -a flag just stands for 'all' and does exactly what I've said. further down you'll see the '-l' flag gives a "long listing format" which is an almost impressively bad description. This means that on each listing will be displayed like this: Permissions numOfLinks owner group size month date time name example: drwxr-xr-x 2 vega vega 4096 Jul 7 2018 Documents  So let's break that up further. Linux permissions are incredibly powerful, and are set up like this d rwx rwx rwx , the d, or lack there of, species weather a file is a directory (folder) or file. Less commonly you may see 'l', 'c', or 'b', as we do here in the /dev folder. 'l' is the easiest to understand, it's a link or shortcut. That's why you'll see an arrow pointing to where it leads at the end 'c' is a character special file, 'b' is a special block file. There are other possibilities here two, of which you can learn about by running info ls The vast majority of the time you will only see 'd' or '-' designating a file or directory though Moving on to the 'rwx' blocks, these stand for read, write, and execute respectively and each block in order states the permission of the owner of the file, those that are in the same group as the owner, and everyone else, for this reason these permissions will almost exclusively be set such that permissions are lost with each level, for example a file with -rwxr--r-- , is a file (no 'd'), which may be read, written, or if it is a program ran, by the owner, yet by anyone else in the same group as the owner or anyone else on the system may only be read. So if we changed the permissions on that python file we wrote back in Chapter 2 to be this then while anyone else could see the code, they couldn't run it without making a copy. with that let's skip over the number of links, as I've never found it particularly useful and jump to the owner and group fields. The owner of a file is a single user, usually the one who created it. The root user is often the owner of important system files, which is why we have to temporarily use root account when we do many admin actions, such as updating or installing programs using sudo. (note, yay calls sudo automatically and you should NOT run yay with sudo) The group is almost nonsensical on single user systems, though many Linux systems today still have many users, so you may have user groups such as 'students' and 'staff' at a school. Next is size, this is pretty self explanatory, as its just the size of the file. Directories do take some space on the disk as they have to store the bit of their own permissions, name, and so on. On this note, directories are a bit strange in regards to the 'execute' flag that was previously mentioned. On a directory, rather than stating if a user can execute a directory (this wouldn't make any sense!) it says weather or not a user can see what's in the directory at all, almost like a lock on a file cabinet. Next is the file modification time, finally followed by the items name, both of which are self explanatory. To round this off we need to talk about how to change these permissions using chown and chmod chown, as the name implies, changes the owner, note, you need to also have permission to change the owner, so often times this require using sudo as well. For example running ╭─vega@lyrae ~ ╰─➤ sudo chown vega:vega someFile  would change both the owner and group to me, vega (assuming I exist on your system) but what if you want to change every file in a directory? ╭─vega@lyrae ~ ╰─➤ sudo chown -R vega:vega someFolder  the -R flag (Recursive) means to apply the change to every sub folder and directory Using chmod is pretty easy too, though there are two ways to use it. The first, which is easier to understand is with direct flags such as ╭─vega@lyrae ~ ╰─➤ chmod +x on a file to mark it as executable  The other uses the octal system to set flags. Octal has 3 bits: Octal Octal Binary Permission 0 000 --- 1 001 --x 2 010 -w- 3 011 -wx 4 100 r-- 5 101 r-x 6 110 rw- 7 111 rwx Now, you should notice some of those options are nonsenes? being able to write to a file you can't read? being able to execute a file you can't read? In practice this leads to only some of these being used, but I digress to use these in chmod simply run ╭─vega@lyrae ~ ╰─➤ chmod 764 someThing  which would set permissions to -rwxrw-r-- Finally one last oddity. Using ls -la you'll see two more files that are very strange one named '.' and another '..' ; '.' is actually the current folder, as bizzare as this sounds, effectively when you run a command with '.' as an argument it is replaced with the full path to the current folder. In practice this isn't used much, but it means running something like cd . just takes you nowhere. I assure you are practical uses though. More relevant is '..' which is the previous directory. so if you're currently in /a/b/c/d and you run cd .. you'll be taken to /a/b/c To round this conversation off , as previously mentioned, '~' represents your home directory. This usually means it expands out to /home/yourUsername which can be particualy helpful if you are say, in /dev and want to get to your documents folder you can use cd ~/Documents instead of cd /home/user/Documents With all of that out of the way let's finally look at /dev ! /dev, the devices folder Alrighty then, first, a heads up. My /dev folder will have some things yours wont. I'm on a desktop with a lot of hardware, drives, input devices, etc. And I've installed hundreds of programs, some of which interface with the system at a low enough level to necessitate extra files in here. For that reason some are going to be skipped over let's take these in blocks of 10 drwxr-xr-x 22 root root 4600 Feb 8 06:03 . drwxr-xr-x 18 root root 4096 Jan 26 22:05 .. crw-rw-rw- 1 root root 10, 56 Feb 8 06:03 ashmem crw-r--r-- 1 root root 10, 235 Feb 8 06:03 autofs crw-rw-rw- 1 root root 511, 0 Feb 8 06:03 binder drwxr-xr-x 2 root root 520 Feb 8 06:02 block drwxr-xr-x 2 root root 200 Feb 8 06:02 bsg crw------- 1 root root 10, 234 Feb 8 06:03 btrfs-control drwxr-xr-x 3 root root 60 Feb 8 06:02 bus lrwxrwxrwx 1 root root 3 Feb 8 06:03 cdrom -> sr0 drwxr-xr-x 2 root root 5700 Feb 8 06:03 char crw------- 1 root root 5, 1 Feb 8 06:03 console lrwxrwxrwx 1 root root 11 Feb 8 06:02 core -> /proc/kcore  Here I've included . and .. in the output for reference, but we'll immediately move on. 'ashmem' is something that is on my system as a part of a project with the end goal of running android apps natively on linux called 'anbox' it's still in early development, and is very difficult to run on arch 'autofs' is a configurable system for mounting and unmounting storage as it is used 'binder' is another component of 'anbox' 'block' is a directory which contains numbered links to the file system blocks used previously (such as sda) 'bsg' is a directory with files that, again, represent your drives at a hardware level. You can open the bsg folder and run ls followed by lsscsi and compare the outputs to understand. This is practially just an artifact of older systems now. 'btrfs-control' is used when you have drives on the system formated with the btrfs file system, this is a file system that is still in heavy development primarily targeted at storage arrays that are resilient to drive failures 'bus' is a folder which contains a folder 'usb' which contains folders for each usb host controller on the system, and then their devices 'cdrom' is actually a link to the new location of cdroms- sr0 , but, still, it's use it pretty duh 'char' is a folder which contains links to a lot of other things in /dev for use with legacy things 'console' is again a legacy component and is effecively the same as tty, which is always the current terminal. to be explained more when we get to the tty's 'core' a link to /proc/kcore is a direct way to read memory, used mostly for debugging drwxr-xr-x 2 root root 60 Feb 8 06:02 cpu crw-rw---- 1 root realtime 10, 60 Feb 8 06:03 cpu_dma_latency crw------- 1 root root 10, 203 Feb 8 06:03 cuse drwxr-xr-x 8 root root 160 Feb 8 06:02 disk crw-rw----+ 1 root audio 14, 73 Feb 8 06:03 dmmidi4 ... crw-rw----+ 1 root audio 14, 121 Feb 8 06:03 dmmidi7 drwxr-xr-x 3 root root 140 Feb 8 06:03 dri crw------- 1 root root 242, 0 Feb 8 06:03 drm_dp_aux0 ... crw------- 1 root root 242, 4 Feb 8 06:03 drm_dp_aux4  'cpu' is a folder which contains a character file named mircocode. If you enable msr it can also allow you to r/w model specific registers. I don't even know what this means. You'll never work on this directly, moving on. 'cpu_dma_latency' is something to do with making sure changing between power states (sleep) doesn't take to long, otherwise the system will just refuse to do. Not used directly by anyone really 'cuse' is fuse for character devices, ref fuse below 'disk' is the way most modern things access the disk, with separate folders for by id, label, path, or uuid 'dmmidi' is for MIDI or Musical Instrument Digital Interface devices. I have multiple on this system. 'dri' contains links to your graphics cards, this is part of the direct rendering manager for video things (3D, games, etc) 'drm_dp_aux' each represent an output from the GPU, so think of these as the actual cables between the monitor and the computer crw-rw---- 1 root video 29, 0 Feb 8 06:03 fb0 lrwxrwxrwx 1 root root 13 Feb 8 06:02 fd -> /proc/self/fd crw-rw-rw- 1 root root 1, 7 Feb 8 06:03 full crw-rw-rw- 1 root root 10, 229 Feb 8 06:03 fuse crw------- 1 root root 254, 0 Feb 8 06:03 gpiochip0 crw------- 1 root root 254, 1 Feb 8 06:03 gpiochip1 crw------- 1 root root 240, 0 Feb 8 06:03 hidraw0 ------------------------------------------------------------------------------------ to make this output shorter I stripped out hidraw 1-5,10-12 ------------------------------------------------------------------------------------ crw-rw----+ 1 root root 240, 6 Feb 8 06:03 hidraw6 ------------------------------------------------------------------------------------ to make this output shorter I stripped out hidraw 7-9 ------------------------------------------------------------------------------------  'fb0' is your framebuffer - I can't do this justice https://www.kernel.org/doc/Documentation/fb/framebuffer.txt, in practice you're unlikely to ever use this, but it's very good to know 'fd' is for file descriptors, which are now in /proc this is part of how the system internally handles file reads and writes 'full' literally just returns no space left when accessed, used to test how a program responds to a disk full error 'fuse' Filesystems in User Space is a system which allows for interesting virtual drives (think things like GoogleDrive) to be accessible to the native system among other things. This is a very heavily used part of the system and worth a deeper look if you're interested 'gpiochip' is for general purpose input/output like with exposed pins that can be used on development board such as the raspberry pi 'hidraw' is for raw communication with Human Interface Devices (mouse, keyboard, gamepad) and allows for custom drivers, like those necessary for RGB backlit keyboards crw-rw---- 1 root realtime 10, 228 Feb 8 06:03 hpet drwxr-xr-x 3 root root 0 Feb 8 06:03 hugepages crw------- 1 root root 10, 183 Feb 8 06:03 hwrng lrwxrwxrwx 1 root root 12 Feb 8 06:03 initctl -> /run/initctl drwxr-xr-x 4 root root 880 Feb 8 06:03 input crw-rw-rw- 1 root render 241, 0 Feb 8 06:03 kfd crw-r--r-- 1 root root 1, 11 Feb 8 06:03 kmsg crw-rw-rw- 1 root kvm 10, 232 Feb 8 06:03 kvm drwxr-xr-x 2 root root 60 Feb 8 06:02 lightnvm lrwxrwxrwx 1 root root 28 Feb 8 06:03 log -> /run/systemd/journal/dev-log crw-rw---- 1 root disk 10, 237 Feb 8 06:03 loop-control  'hpet' "High Precession Event Timer" is for internal timer-y things 'hugepages' - read this https://wiki.debian.org/Hugepages , these are actually pretty important as they can make a large impact on performance, especially with virtual machines 'hwrng' hardware random number generator, rarely used directly, often not trusted due to known faults, typically used though the soon to be mentioned 'urandom' interface - https://main.lv/writeup/kernel_dev_hwrng.md 'initctl' part of the init system, just dont touch it 'input' is a directory which contains links to all input devices, going to /dev/input/by-id can explicitly tell you how some devices are connected, and can be a way to extract input form devices for input in your own programs 'kfd' has little documentation- appears to be for AMD GPU accelerated compute 'kmsg' is the i/o of dmesg which itself is the main system log 'kvm' is the kernel virtual machine, used for running virtual machines. We'll talk about this more much later. 'lightnvm' use for NVMe drives 'log' no shit, access using sudo journalctl 'loop-contol' - http://man7.org/linux/man-pages/man4/loop.4.html, effectively used to mount images or or other file systems to be read as a separate block device drwxr-xr-x 2 root root 60 Feb 8 06:03 mapper crw-rw---- 1 root video 239, 0 Feb 8 06:03 media0 crw-r----- 1 root kmem 1, 1 Feb 8 06:03 mem crw------- 1 root root 10, 57 Feb 8 06:03 memory_bandwidth crw-rw----+ 1 root audio 14, 66 Feb 8 06:03 midi4 crw-rw----+ 1 root audio 14, 82 Feb 8 06:03 midi5 crw-rw----+ 1 root audio 14, 98 Feb 8 06:03 midi6 crw-rw----+ 1 root audio 14, 114 Feb 8 06:03 midi7 drwxrwxrwt 2 root root 40 Feb 8 06:02 mqueue drwxr-xr-x 2 root root 60 Feb 8 06:03 net crw------- 1 root root 10, 59 Feb 8 06:03 network_latency crw------- 1 root root 10, 58 Feb 8 06:03 network_throughput  'mapper' is primarily used for LVM systems, https://wiki.archlinux.org/index.php/LVM, which is used for more advance disk management but comes with disadvantages in complexity and inter-OS compatibility 'media0' is the i/o file for a webcam 'mem' is direct access to the system's physical memory. This is dangerous. There's almost no reason to do this directly, unless you're writing a low level driver 'memory_bandwidth' - as the name implies. Rarely used 'midi' direct access to midi devices. Documentation on dmmidi vs midi unclear 'mqueue' used for interprocess comunnication 'net' contains virtual network adapters, will likely contain 'tun' by default, used for interprocess communication in weird ways. 'network_latency' and 'network_thoughput' is primary used to specify current minimum necessary requirements for the network, used for power saving on wireless adapters crw-rw-rw- 1 root root 1, 3 Feb 8 06:03 null crw------- 1 root root 243, 0 Feb 8 06:03 nvme0 brw-rw---- 1 root disk 259, 0 Feb 8 06:03 nvme0n1 brw-rw---- 1 root disk 259, 1 Feb 8 06:03 nvme0n1p1 brw-rw---- 1 root disk 259, 2 Feb 8 06:03 nvme0n1p2 crw-r----- 1 root kmem 1, 4 Feb 8 06:03 port crw------- 1 root root 108, 0 Feb 8 06:03 ppp crw------- 1 root root 248, 0 Feb 8 06:03 pps0 crw------- 1 root root 10, 1 Feb 8 06:03 psaux crw-rw-rw- 1 root tty 5, 2 Feb 8 16:37 ptmx crw------- 1 root root 247, 0 Feb 8 06:03 ptp0 drwxr-xr-x 2 root root 0 Feb 8 06:03 pts  'null' literally just discards anything it receives. Useful when a command outputs junk when doing things, and getting rid of the junk. '/dev/null' is referred to regularly in jokes in technical circles 'nvmexxxx' the system NVMe storage device(s), will only exist if you have an NVMe solid sate drive 'port' used for direct access to i/o ports. Dangerous 'ppp' point-to-point protocol. Similar to /net/tun - https://stackoverflow.com/questions/15845087/what-is-difference-between-dev-ppp-and-dev-net-tun 'pps0' pule per second provides a pulse once per second 'psaux' , ps provides a snapshot of currently running system processes, ps aux, where aux: 'a' is all user processes, 'u' is show user/owner, and 'x' processes not attached to a terminal 'ptmx', pseudo terminal master/slave, used for virtual terminals, like the one's you've been opening in KDE 'ptp0' precession time protocol, links to realtime clock 'pts' interval virtual filesystem, used for things like docker. Works closely with 'ptmx' crw-rw-rw- 1 root root 1, 8 Feb 8 06:03 random crw-rw-r--+ 1 root rfkill 10, 55 Feb 8 06:03 rfkill lrwxrwxrwx 1 root root 4 Feb 8 06:03 rtc -> rtc0 crw-rw---- 1 root realtime 250, 0 Feb 8 06:03 rtc0 brw-rw---- 1 root disk 8, 0 Feb 8 06:03 sda brw-rw---- 1 root disk 8, 1 Feb 8 06:03 sda1 ... brw-rw---- 1 root disk 8, 96 Feb 8 06:03 sdg brw-rw---- 1 root disk 8, 97 Feb 8 06:03 sdg1 brw-rw---- 1 root disk 8, 98 Feb 8 16:37 sdg2  'random' waits for true randomness and will block things from finishing until enough entropy is generated 'rfkill' kills all radio transmission on system 'rtc' real time clock, direct access - we'll talk more about real time clocks and time in networking. 'sdxn' the 'normal' representation of block devices like HDDs, SSDs, and flash drives to the system. Each number is a partition drwxr-xr-x 4 root root 80 Feb 8 06:03 serial crw-rw----+ 1 root optical 21, 0 Feb 8 06:03 sg0 crw-rw---- 1 root disk 21, 1 Feb 8 06:03 sg1 ... crw-rw---- 1 root disk 21, 7 Feb 8 06:03 sg7 drwxrwxrwt 2 root root 80 Feb 8 16:37 shm crw------- 1 root root 10, 231 Feb 8 06:03 snapshot drwxr-xr-x 4 root root 760 Feb 8 06:03 snd brw-rw----+ 1 root optical 11, 0 Feb 8 06:03 sr0 lrwxrwxrwx 1 root root 15 Feb 8 06:02 stderr -> /proc/self/fd/2 lrwxrwxrwx 1 root root 15 Feb 8 06:02 stdin -> /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Feb 8 06:02 stdout -> /proc/self/fd/1  'serial' contains references to serial devices by id or path 'sgx' are mostly just remaps of other devices for legacy support 'shm' is for shared memory, to be passed between programs 'snapshot' is used for hirenation 'snd' sound devices raw access, legacy and probably will not work 'sr0' used for optical media 'stderr' is the standard error interface, try echo 1 > /dev/stderr - you should see an error return code depending on your terminal setup 'stdin' is the standard input interface, try echo hello | cp /dev/stdin /dev/stdout 'stdout interface, try echo hello > /dev/stdout crw-rw-rw- 1 root tty 5, 0 Feb 8 15:49 tty crw--w---- 1 root tty 4, 0 Feb 8 06:03 tty0 ... crw--w---- 1 root tty 4, 63 Feb 8 06:03 tty63 crw-rw-rw- 1 root uucp 166, 0 Feb 8 06:03 ttyACM0 crw-rw----+ 1 root tty 4, 64 Feb 8 06:03 ttyS0 crw-rw----+ 1 root uucp 4, 65 Feb 8 06:03 ttyS1 crw-rw----+ 1 root uucp 4, 66 Feb 8 06:03 ttyS2 crw-rw----+ 1 root uucp 4, 67 Feb 8 06:03 ttyS3  TTY's, these are important: 'tty' the currently active terminal, try echo 1 > /dev/tty 'ttyx' are virtual consoles accessible though ctrl+alt+fx, where fx is a function key. You should ben on tty7 by default, go ahead and try it now. Note you may need to hold the 'fn' key as well 'ttyACMx' or 'ttyUSBx' are attached USB devices that can be accessed as a virtual terminal. This is mostly used for development boards, and we'll be using this later 'ttySx' are serial port terminals, rarely used outside of scientific or server gear. The physical connector usually looks similar to VGA cable. Your motherboard may well have a serial port header for adding this even if you don't physically see one available on the outside of the case crw------- 1 root root 10, 61 Feb 8 06:03 udmabuf crw------- 1 root root 10, 239 Feb 8 06:03 uhid crw-rw-rw-+ 1 root root 10, 223 Feb 8 06:03 uinput crw-rw-rw- 1 root root 1, 9 Feb 8 06:03 urandom drwxr-xr-x 2 root root 200 Feb 8 06:03 usb crw------- 1 root root 10, 240 Feb 8 06:03 userio drwxr-xr-x 4 root root 80 Feb 8 06:03 v4l crw-rw---- 1 root tty 7, 0 Feb 8 06:03 vcs crw-rw---- 1 root tty 7, 1 Feb 8 06:03 vcs1 ... crw-rw---- 1 root tty 7, 7 Feb 8 06:03 vcs7 crw-rw---- 1 root tty 7, 128 Feb 8 06:03 vcsa crw-rw---- 1 root tty 7, 129 Feb 8 06:03 vcsa1 ... crw-rw---- 1 root tty 7, 135 Feb 8 06:03 vcsa7 crw-rw---- 1 root tty 7, 64 Feb 8 06:03 vcsu ... crw-rw---- 1 root tty 7, 71 Feb 8 06:03 vcsu7  'udmabuf' Uniform Direct Memory Access Buffer https://github.com/ikwzm/udmabuf, you probably don't care 'uhid' for Human Interface Device stuff on the system side, you shouldn't mess with this 'uinput' https://www.kernel.org/doc/html/v4.12/input/uinput.html, basically you can fake a keyboard or mouse in your program 'urandom', the main source of random numbers. give it a shot but running head -5 /dev/urandom 'usb' folder which contains character devices to the HID inputs, used by the system 'userio' mostly used for laptop touchpad drivers 'v41' part of the video subsystem 'vcsx' virtual console memory, used when running a terminal emulator 'vcax' virtual console stuff 'vcsux' virtual console stuff drwxr-xr-x 2 root root 60 Feb 8 06:03 vfio crw------- 1 root root 10, 63 Feb 8 06:03 vga_arbiter crw------- 1 root root 10, 137 Feb 8 06:03 vhci crw-rw----+ 1 root kvm 10, 238 Feb 8 06:03 vhost-net crw------- 1 root root 10, 241 Feb 8 06:03 vhost-vsock crw-rw----+ 1 root video 81, 0 Feb 8 06:03 video0 crw-rw----+ 1 root video 81, 1 Feb 8 06:03 video1 crw-rw-rw- 1 root root 1, 5 Feb 8 06:03 zero  'vfio' is used for passing hardware directly to virtual machines, often massively improving performanec 'vga_arbiter' if you still have a computer that uses vga I'm sorry. This almost certainly doesn't matter to you even if you do: https://www.kernel.org/doc/html/v4.16/gpu/vgaarbiter.html 'vhci' used for passing though usb devices to virtual machines 'vhost-net' & 'vhost-vsock' used for virtual machine networking 'videox' the graphics adapter in the system. Most systems will have only one, some will have two, very, very rarely you may have more. 'zero' generates an infinite stream of zeros. Used for generating test files of arbitrary size, among other things. And That's it, congrats. Now lets go to /proc /proc, the fake file system /proc doesn't really exist, it's a memory only system used primarily for information about processes, hence the name. https://www.tldp.org/LDP/sag/html/proc-fs.html & https://linux.die.net/man/5/proc Let's dig in by hand a bit though, lets start by opening a terminal and running cd /proc if you run ls you'll see a bunch of numbers followed by some strange things, like uptime let's start with the not-number things. We've already seen cpuinfo and meminfo, but there's other stuff in here too. Running cat uptime will tell us how many seconds the system has been powered on for, for example. A lot of things in here are bit hard to understand, but things like 'uptime' and 'loadavg' can be legitimately useful in our own programs. running cat loadavg you'll see some numbers that represent how much load the system is under. You can use the above links to learn more, but now we're going to dive into the juicy bits! Before we do so though, let's grab a program that will make our lives a bit easier called 'htop', just use yay to install it. once it installs go ahead and open it up you should see something like this: This is a super powerful equivalent to task manager from windows. You can see the load on all 16 of my cpu threads, the memory usage on the system, uptime, loadavg, and number of tasks running here, but best of all we can see a nice tree of all the processes, and how each one of them is impacting the system. (you may need to press f5 to put it in tree mode) From here you can also see the Process's ID known as the PID, these numbers should directly corolate with those visable in /proc Leaving that windows open lets open up two more terminals, in one navigate to /proc and in the other start up python: from here go back to the window running htop and use f3 to search for python if there are multiple processes that come up just keep pressing i3 until you find one that has a tree that looks like: (note your terminal will probably be named either konsole or xterm, not deepin-terminal) and look to the left to find the pid of the running python process, in my case it's 754. Go over to the terminal where you navigated to /proc and now navigate to the folder with the id of your process, in my case i'd run cd 754 then run 'ls' and look at everything in this folder: now, we're gonna run one more thing before we leave, and we'll come back to it later, but I want to show you now, so you can appreciate how cool it is later: go ahead and run sudo cat stack you should see something like: but when we run this in the python terminal: while(1): 1+1  and read the stack again we'll see: Which while may not look overly interesting, I assure you will be something of interest later. One interesting processed to note in here is the process numbered '1' which, if you look back in htop, you'll see is the init process. This means it's actually possible to look at a mountain of deails about the init process, which we'll talk about in a bit. Before we leave /proc, look back up at all the file that each process has and take note, also notice how some of these relate to what we saw in /dev Take a breather, As you can see, Linux gives us a lot of raw access to hardware. There are no training wheels here. While you can use Linux the exact same way you used windows: watch YouTube videos, open a graphical file manager, etc, you can also get down to the nitty gritty of the OS. /bin, /sbin, /lib, /lib64 [TODO] symbolic links to usr explanation /sys echoing to change settings, probabaly focus on device /usr [TODO] Share, man, local, var /boot [TODO] boot loaders, init, initrd fs? /etc ... and etc. Literally. the etc folder contains system configuarion files mostly. Remember back when we installed and you used nano /etc/fstab that was editing the list of file systems that the system loads at boot, a configuration file. When we configure SSH later, it's config files are stored here too. Basically, most of the admin level system config files and default config files (lower priority than the config by the user) files are here. As you learn about your system and tweak things you'll find yourself in this folder rather often. [TODO, add chapter links] Some of the more interesting things in /etc are: /ca-certificates/ -- we'll talk about these more in networking [TODO] /conf.d/ -- various system default config files for system services /cron.d/,/cron.daily/,/cron.hourly/, etc. are all form the cronie package which can be installed then enabled with systemd. Note, systemd timers are a built in way to do the same thing. cron is the 'old' way of doing thing, but is super simple to use /crypttab is the similar to /fstab but for encrypted partitions /cups is a folder used by cups, which is the backend used for printers in linux /dbus-1/ is used by dbus which is a backend for interprocess communication in linux /dconf/ is a folder used by dconf wich is used to store config settings. dconf is a cli tool for changing these settings /gconf/ -- gconf is very similar to dconf but outdated. Still used by somethings though. /dnsmasq.conf is used by dnsmasq, which will be discussed in networking [TODO] /default/ stores default configuration files, typically these get overriden elsewhere by the user /dhcp_fingerprint.conf,/dhcpcd.conf,/dhcpd.conf, and /ducpd6.conf are all part of dhcpcd and dhcp, used for reciveing DHCP information. This is dicussed further in the networking chapter [TODO] /dkms/framework.conf is used to configure dkms or Dynamic Kernel Module Support which is used to load modules for the kernel without building the kernel from source. In practice this means drivers for various hardware can be loaded even if it's not in the linux source tree. Read more here: https://www.linuxjournal.com/article/6896 /envrioment is a configarating file for pam_env files. Basically, enviroment variables that you want to be loaded at boot can be put here. For example to change the defalut editor used by command line programs you can set EDITOR=vim or EDITOR=nano or whatever you like here. /ethertypes is a file listing various ethernet protolcols, we'll come back to this in the networking chapter [TODO] /exports is used to setup NFS shares, again, in networking [TODO] /firewall.d/,/gufw/ are where firewall settings are stored, dependant on the firewall progarm used /fonts/ holds your fonts, go figgure. You'll need to update the font database if you install things manually: https://wiki.archlinux.org/index.php/Fonts#Manual_installation /foremost.conf is used by the foremost package, it contains information about file headers, footers, and data structures for file recovery purposeses. For example, if you have a backup .img file of a failing hdd and need to scan for .jpg file headers to recover images /freeipmi/ contains config files for Intelligent Platform Managment Inferface Modules. We'll talk about this more in servers [TODO], but essentially it's a way to, using server hardware, set BIOS settings, monitor hardware, and turn the system on/off remotely. /freetds/,/mysql/,/sqlmap.conf,/odbc.ini,ODBCDataSources,and odbcinst.ini all have to do with databases and database connectivity. [TODO_Ch17] /fstab/ short for file system table contains a table of file systems to be mounted at startup and options they should have. Settings here can dramatically effect fs performance or cause your system not to boot, so make sure you know what you're doing. Even if your system doesn't boot because of something here, you should land in an emrgancy shell where you can edit /etc/fstab and fix the mistake /fuse.conf is the config file for fuse, which is dicussed below in file systems. /gdb/gdbinit -- you probably want to put the global gdb config file at ~/.gdbinit not here in /etc. gdb is discussed more in debugging [TODO_Ch18] /group is where linux user groups are defined. You probably want to use the groups,groupadd,groupdel,groupmems, and groupmod commands. /grub.d/ contains config files and boot loader entries for the grub bootloader. Not relevent if you're using systemd boot on a UEFI system /gshadow contains encrypted passwords for each group. !! and ! both indicated no password, though !! is no password has been set before /healthd.conf used to notify if hardware has an issue (temp, fan, etc) -- provided by lmsensors /host.conf & /resolv.conf are used for resolver configuration. More in networking [TODO] /hosts local host configuration file. Very useful, in networking again [TODO] /httpd/, and specifically /httpd/conf/httpd.conf is used to conigure a local web server like Apache. Refrenced in Networking [TODO] and Servers [TODO] /home, /mnt, /run [TODO] discuss systemd taking over home soon Users and Groups [TODO] permissions discussed eariler, recap here Drivers [TODO] udev rules File systems [TODO] Inodes, Raid, fuse, ext4, ntfs, zfs, tmpfs, fat/fat32/exfat, ... Processes and Memory [TODO] loading libs, forks, env variables, process ownership lsof, strace, ltrace, nice levels System Calls [TODO] start with a syscall table Kernel Parameters [TODO] SystemD and alternatives [TODO] init system: https://www.lifewire.com/how-to-use-the-init-command-in-linux-4066930 Schedulers [TODO] +real time kernel/preemption Dbus [TODO]reguallarly https://github.com/KnowNo/How-Linux-Works-2nd-Edition/blob/master/How.Linux.Works.What.Every.Superuser.Should.Know.2nd.Edition.PDF.pdf We'll explore more of the OS later, but for now I think the information overload is a bit much anyway, so lets move away from screens and into the world of hardware Chapter 5 - Intro to Angry Pixies A simple guide to electronic components (YouTube) The Tools of the Trade Building, fixing, and analyzing circuitry requires the use of a few tools and appliences. While there are many more than those listed here, these are the most important ones and should be all you need for most even very advanced applications. The Multimeter [TODO] Resistance and the OHM meter resistors do one thing- resist current. Using the ohm meter function of your multimeter you can find out the amount of this resistance measured in ohms (ohms are represented with a capital omega, Ω) using an ohm meter is simple, just poke and prod with at least one component in between the leads. If there's nothing in between - that is the leads are touching one another- there will be no resistance, if there's no way for a DC voltage to get from one point to the other, that will be infinite or 'overload' resistance Voltage, Ground, and the Volt Meter Voltage can be thought of as the 'pressure' in a hose. However, this pressure is relative to another point, the point we usually take reference to is called 'ground', though this doesn't have to be the case- you can measure the voltage across a single resistor or other component too. Just remember measuring the voltage with both probes at point or along the same wire doesn't make sense because a volt meter only tells you the voltage difference between two points. This would be like seeing the pressure difference in hose between two nearby points, obviously the pressure of one point minus the other will be 0. In general there are two primary ways you will work with voltage- AC or DC, these stand for Alternating Current and Direct Current. DC is simply a constant voltage level output. AC on the other hand is any time varying signal, usually periodic (repeating) and most commonly a sine, though many other waves are used like square, triangle, saw, and any mixture of these, including the same signal with a DC offset. Your multimeter will likely have two different settings for measuring voltage, one for DC and one for AC. Of note, most multimeters are not true RMS (Root Mean Square) meters, meaning the reading of AC voltage is not accurate unless it's a clean, no DC offset sine wave. RMS is a topic we'll be covering later, but to wet your apatite, this from wikipedia may help: https://en.wikipedia.org/wiki/Root_mean_square Of note, from a mathematical perspective all time varrying signals can be represented as an infinite number of sine waves added together, this is actually used to do practical computation in many things. https://en.wikipedia.org/wiki/Fourier_series#Examples Current and the Ammeter If current is the pressure in the hose, then current is how much water actually flows. This analogy holds up too, because if we use a resistor to kink the hose and the flow is restircted the current will go down. If you were to stick a wire directly into the wall outlet all the current the wall can give will try to flow though, but it can be restricted. To measure the current though a circuit we can't just probe between two points as before though. Instead the probes need to form the exclusive path that part of the circuit can flow through. In practice this means the wire you want to measure current through would need to be cut and the ammeter's probes hooked up at either end, making the meter part of the circuit. Current, just like voltage, can varry, and in AC circuits usually does. This leads to some more interesting caseses like power factor, but we'll get to that later. Continuity Tester The contiuity tester does exactly what it's name implies, it makes sure two points are connected electrically. If you have a piece of metal and put both probes on it it should beep, but if you put the probes on rubber, they clearly will not be. The continutiy tester isn't really much different from the ohm meter in operation, and many will actually dispaly the resistance if there is any. The main use is that it beeps when the resistance is low enough to be confident two points are electrically connected. [TODO] day to day use, why you want one The Lab Power Supply Power Supply Units or 'PSU's are useful because unlike your phone charger which puts out a singular voltage of 5 volts (ignoring fast charging) they can have their output voltage varried usually between 1 and 35-ish volts. Furthermore, they provide current limiting, useful when you're unsure of how much current your circuit might sink or need it for safety. [TODO] add picture, mention ATX psu, current safety The Frequnecy or Waveform Generator Frequency generators can be used to output a signal that is alternating, unlike the DC signal of the Lab PSU. Usually they'll support a range of wave shapes, frequencies, amplitudes, and DC offsets. Many support far more than this, though the applications for the more advanced modes are few. If you're just starting out you can (with precausions) actually just use the audio output of your computer or buy an inexpensive one for under \20, unlike the expensive example below:

https://en.wikipedia.org/wiki/Arbitrary_waveform_generator

The Oscilloscope

The osciliscope (or OScope or simply Scope) allows you to see an AC signal and how it varies over time as a plot of Voltage on the Y axis and time on the X, Most OScopes will allow you to look at multiple signals at once, with one overlaid on the other. Furthermore, most support X-Y mode, where the plot is actually the voltage of one input as the X axis and the voltage of another as the Y, moving a dot and it's trail around the screen. In fact, this is how the first computer monitors worked:

Modern OScopes look much different than their phosphorescent green ancestors though:

However, a decent 'Digital Storage Oscilloscope' or DSO like the one above run a minimum of \$300 at the time of writing, so many hobbyist opt for older scopes like this one: or a cheap, low resolution, low speed one from Ebay. For most uses, both of these will be perfectly fine. For just starting out though I'd recommend a logic analyzer (I'll talk about that next) and oscilloscope combo tool, like the LHT00SU1 which can be found on Ebay pretty easily. Be aware they can fry your USB port or worse though. But what are these actually used for day to day, and why would you want one? [TODO] Quake on an oscilloscope (YouTube) The Logic Analyzer Logic Analyzers... analyze logic. Who knew? But what does that mean? Well, in reality they are somewhat similar to an oscilloscope in that they show a voltage over time, the difference is they only show either on or off over time based on the set TTL (Transistor–transistor logic) voltage. This lets you eavesdrop on the digital communication going on over a wire. Here's an example output: In this particular encoding, the longer high bumps represent a 1 and the short high bumps a 0, so you're looking at the binary that was sent over a wire. It's actually pretty rare that a wire sends raw high for a 1 and low for 0 so other schemes, like the one above, are used. For most schemes the software can actually be used to decode the received data into raw binary or if it was human readable characters even that. Using a logic analyzer is pretty simple, most today are connected to your computer over USB and then use software like Pulseview as shown above, then you just select the sample rate (how many times per second to check the wire, here 1MHz) and the number of samples to collect and hit start. You may want to setup a trigger too (speaking of, it's worthwhile to look up how triggering works on an OScope [TODO]) Most logic analyzers support 8 or more simultaneous data streams, though in the picture above I'm only using one. [TODO] explain when a logic analyzer is actually used, and look at a quick example decode Software Simulation [TODO] Circuit Simulator Simulide VCV Rack? [TODO- following title needs split up, possibly new chapter?] OHM's law, Nodal & Mesh Analysis, Superposition, Thevanins [TODO] Resistors [TODO] potentiometer read from aduino full range (center tap or max resitor) Capacitors [TODO] True, Reactive, Apparent & Deformed Power Why electrolytic capacitors are actually kinda shitty 💩 (YouTube) Ideal Capacitor's aren't real Inductors [TODO] RGB LED, Inductively Powered, Frequency Controlled (YouTube) Motors Transformers, Variacs [TODO] Buttons, Switches, and Knobs [TODO] SPST DPST etc. Pots V encoders, encoders with buttons, slider pots. (inc motorized) etc. Relays [TODO] solid state vs old school Filters [TODO] Passive V Active Decibels [TODO] How to read logorithmic first Further Reading [TODO] https://learn.sparkfun.com/tutorials/voltage-current-resistance-and-ohms-law/voltage Chapter 6 - Let's work on how we work The Terminal In the world of programming, embedded development, and electrical debugging you will inevitably need to understand how to use a terminal/command line at some point. While the text only interface can look intimidating, it has some clear advantages, namely it's significantly faster to use the cli or 'command line interface' version of many tools. Because of the nature of this book you will be using the terminal frequently, so for convince sake information on using it effectively has been moved to Appendix A, though I highly recommend you read though it now. I highly recommend getting autojump setup early as it makes navigating around the terminal much faster, furthermore, bat makes reading code though cat not suck and tldr will save you time when you forget how to use tar, set these up early if nothing eles. Heads up, With that out of the way, I want to preface this chapter with a big warning: Getting used to everything we're about to do will be a pretty big leap. There's a good chance you've never used a computer that works like we're going to be setting up, but it's what I and many of my friends use daily and for good reason. This is probably where more opinions are going to show than anywhere else. You've been warned. [TODO] pacman -Qi , pacman -R Code editors People get defensive about the way they work, and frequently try to claim theres is the best way. I personally see value in multiple of them, but also understand how setting down with just one and getting very fast with it may have it's appeal. I have three recommendations for code editors, as silly as that may seem. The first two are terminal based nano and vim, nano, is the most simplistic of all the editors I'll list here. It's stupid simple to use and for quick just opening a text file and changing one line, probably the fastest. It clearly prints it's instructions at the bottom of the terminal: where ^ is the ctrl key, and M the alt key. However, you'll quickly find nano rather limiting, so onto vim! Vim, with Spacevim (spacevim.org) ontop is a very powerful tool. Vim can do everything you could ever dream of, and probably a bit more, and with spacevim ontop, it's a powerhouse. Unfortunately, vim is regularly the butt end of a joke becaue of how nutoriously difficult it is to get the hang of. For that reason I'm going to link a mini tutorial here: https://www.openvim.com/, and link https://spacevim.org/documentation Graphically I recommend Visual Studio Code with Platform IO, Bracket Pair Colorizer 2, and GitLens This gives you a pretty kick butt editor on bar with most full Integrated Development Environments or IDEs. I recommend you try out IDEs, especially if for some unholy reason you want to write in Java, but otherwise this will do fine. The Desktop Envrioment This is the biggest change, I'm going to recommend switching from KDE, which we installed when we setup arch, to i3. i3 is a tiling window manager, this means it looks something like this: This is with 3 windows open: Marktext (the program I'm writing this in), a file manager, and an terminal I used to launch the program (scrot) to take the screenshot. What's cool about i3 is how it will always use space as efficiently as possible by tiling the windows, and you can navigate between the windows (or multiple monitors) entirely by keyboard (mouse still works obviously) and open multiple virtual workspaces. When programming and using a computer for advanced things it's not uncommon to have a dozen windows open and having things organized like this can be a life saver. i3, when first installed, is very, very minimal, it will greet you with a plain black bar and clicking with either mouse button anywhere will do nothing. You should, however, be able to open a terminal by using your modkey (probably the windows or alt key) and enter. i3 actually comes in a bunch of separate parts, the most important of which are the window manager itself, the status bar, and the task runner. The window manager is the thing that actually manages the windows, this is the part most people are referring to when talking about i3 (assuming they're not talking about an i3 Intel CPU) and is sometimes refereed to as i3wm. A very popular 'fork' of i3 is i3-gaps which is available in the community repository. On top of the raw window manager you'll probably want a status bar of some kind. While the default i3bar which is included with the i3-gaps package is fine when paired with i3status, it does leave a bit to be desired. Many other options are available. I personally use polybar though I have friends that have used lemonbar ori3blocks. Finally you'll want a runner/application launcher. While i3-demu is included, I find it rather annoying to use, and much prefer rofi -- this is much better explained here than I can briefly: https://github.com/davatorium/rofi To further make i3 reasonable to use you'll want a few more things: compton is a composite manager. This is used to allow application to have some transparency, prevent screen tearing, and do slight effects, like but a shadow behind windows. lxappearance-gtk3 can be used to set the theme used by various graphical applications. I use Sweet but there are nearly endless options For setting the wallpaper (which you probably wont see much) you can use nitrogen or feh if you have multiple monitors before setting the wallpaper though you'll probably want to arrange your monitors correctly, for this you can use xrandr , read the man page for more information. You can add the command you use to set up your displays to your i3 config file to apply them at each reboot if you have a high resolution monitor and things are small, you may want to look here: https://wiki.archlinux.org/index.php/HiDPI , the best thing from this is to add QT_QPA_PLATFORMTHEME=qt5ct QT_AUTO_SCREEN_SCALE_FACTOR=1 GDK_SCALE=2 ELM_SCALE=1.5  to your /etc/enviroment file. You'll be needing quite a few different utilities beyond this. for a terminal I highly recomend deepin-terminal, rxvt-unicode, or Alacritty. For fonts you'll certainly have your own tastes, but I really like Droid Sans Mono, which is in ttf-droid, but ttf-hack and otf-fira-code are pretty cool too. I also recommend installing noto-fonts, noto-fonts-extra, and ttf-font-awesome. The noto packages will provide coverage for weird characters and font awesome is basically icons saved as a font, and many open source projects use it. If you're looking for more ways to make your setup the best it can be or config files you can steal from check out r/unixporn. The Physical Enviroment & Hardware Working on a laptop with a mushy membrane keyboard is totally fine for some people, but when you're deep into some complicated work having the best possible setup can save a lot of time, frustration, and mental overhead. Furthermore, the work environment can change how long you can work for and how productive your work time really is. Be it for comfort or productivity, there are many reasons to take care in making sure you're setup is right for you. If you are on a laptop some of the following is still applicable, but consider how any of what I'm about to mention may be adapted to your own setup. Displays The way you use your monitor is more important the monitor itself. Don't get me wrong, if you have an 11", 4:3 aspect ratio monitor running though VGA there's a limited amount you can do, but there's still some things. First and foremost is positioning. I've helped many a office worker complaining about neck and back pain simply by raising their monitor closer to eye level. Ideally you want your eyes to naturally rest right on the on the top 3rd line of your screen, about the level where the left-most knob is on the wallpaper on my right-most monitor in the picture above. Unfortunately, there is no magic rule for how far away your monitor should be from your face, as this highly depends on your vision, monitor's resolution, and size on this note, you'll often hear monitors described by their dots per inch, this is a measure of the number of pixels in a square inch on the screen, the higher this is the finer the details, but the smaller any given element on screen will be. Apple's Retina displays for example have a high DPI rating, which is a large part of the reason they look so good I personally have my three, 4k (that's 3840x2160, or 4 times the resolution of 1080p) monitors positioned approximately 30 inches from my eyes. Before moving forward though, I think it would make sense to talk about some of this display terminology, if you're already cool with this just skip this massive quote block Aspect ratio is the ratio is the ratio of the width to the height of the screen, most modern screens are 16:9, or have 16 units of width for every 9 units of height. Most older displays, often now called square screens, are actually 4:3. Many people actually still prefer this for the extra vertical room it affords at a given size, and some laptops are actually moving back to a more 'square' aspect ratio. On the other hand more exotic ultra-wide displays are also coming out Sizing of displays is a bit odd. A 27" 16:9 display, is not the same size as a 27" 4:3 display as displays are measured diagonally. Resolution of a display refers to the number of pixels, HD technically starts at 720p, or 720 pixels across, though this is generally rather low by modern standards, with acceptable usually considered 1080p, which is technically 1920x1080. You may also see 1080i, this is a strange concept, not actually related to resolution, and we'll come back to it in a moment The interface on your display matters greatly as well, the most common at the are HDMI, Display Port, DVI, and VGA VGA is the worst option here, as it's an analog signal. This means the signal can do strange things, getting corrupted between your computer and the monitor. Typically this is a blue, screw in connection with many pins DVI is still pretty common and looks like an even larger VGA connection, with a typically white, screw in connector. This signal is normally digital, though there is a varient of DVI that can be adapted into VGA. Of note, DVI can also be adapted to HDMI though you will not have audio, as DVI does not carry sound HDMI, probably the most well known connector, has multiple revisions, the revision determines many things such as the maximum resolution, refresh rate, and weather or not more obscure things such as HDR are supported. HDMI is usually considered the best of these three options Taking the crown however, is Display Port (DP). Like HDMI display port does have multiple revisions which do differentiate similar things; however, Display Port will generally support high resolutions and more features at any given point. Assuming you're running a bog-standard 60hz 1080p display however, you'll find no difference between DVI, HDMI, and DP - unless you need sound. Next, you'll want to note the refresh rate of your monitor. This is how many times per second your monitor refreshes the screen. Typically monitors run at 60hz and TVs at 30 or 60. Because unlike a TV you're causing things on screen to change though, 30hz is generally considered bad and can even cause motion sickness. While 60hz may be standard, going for something even higher, with many displays offering well above 120hz, is something you may want to consider, especially if you plan on gaming. Newer displays may support Freesync or Gsync, and both of these technologies require a supported graphics card in the system as well. These allow the display and computer to adaptively change the refresh rate so the monitor and computer both send and display frames in sync, which can make even a low refresh rate 'feel' much higher. This is a feature typically marketed to gamers and only supported in video games, but this has been changing. Gsync monitors genearlly have a much better implementation of the technology but it requires an Nvidia graphics card. As of the time of writing both Freesync and GSync are supported on linux, but quite rough around the edges. related to refresh rate is latency. In general this can actually mean two things, one is how long it takes for an image sent to the screen to actually be displayed. The lower this time the better, with good screens being sub 10 millisecond. Unfortunately, there's no standard among the industry to measure this and many get it wrong. Also with latency theres grey to grey times, this is a measure of how long it takes a pixel to go from one shade to another. The lower this is the less motion blur the screen will exhibit The color depth of the display determines how precisely a color may be displayed. The higher this is the better, but almost all modern displays will be the same, and unless you're an artist or creative professional you're unlikely to notice a difference On the other hand, you are likely to notice the color gamut or what range of colors the display is actually capable of displaying. For example, two displays may both be capable of displaying 255 levels of red, but if one display's range is only from a dingy red to a dark-ish red, while the other is from a brilliant red to a deep dark red, there's a massive difference in color availability. If this is important to you, notably as a creative professionally in photo or video, you may want to read more at https://en.wikipedia.org/wiki/Gamut The next obvious thing to mention is dynamic range, or how deep the blacks are and how vivid the whites are. Again, this is simple, the higher the better. Many display types (LCD, TN-Panel) will have similar specifications in all these areas, but particularly here. OLED is probably the best when it comes to dynamic range as it can display true black by actually turning the source of the light off, but unfortunately these are quite susceptible to burn in and image persistence. Actually, display technology overall (OLED, LCD, TN, CRT, etc.) will have more of an impact than anything else. But, this is also getting really into the weeds, and I don't want to recomend one technology over the other since depending on many other factors on each display theres no clear winner. There are some newer displays which feature HDR or High Dynamic Range, which allows the panel to selective change the brightness in an area of the screen, giving much better dynamic range in supported applications than a normal display burn in and image persistence are both negative effects on many displays where a pixel either permanently or temporarily resists change in color. This can lead to being able to read previously displayed bright white text on a now black image for example. More commonly you'll find TVs which have a particular station's logo 'burnt in' to one corner of the screen, persisting even after changing channels Brightness is obvious, how bright or dim is the display. The big thing to note here is weather the brightness is PWM or DC controlled. Displays with PWM controlled brightness are much more common, however, it's a bit of a cheat. Instead of actually changing the intensity of the back light directly, they're simply strobing the light on and off to fast for the eye to see. This can cause eye strain over time though, and generally DC control, which actually does change the brightness directly is preferred. If you have a PWM display and don't mind it at full brightness, this should help with eyes strain, as there is no longer a strobe effect as the display's backlight is just constantly on. Finally, if fonts look bad on a screen, it may be due to Sub-pixel rendering. Basically, while most screens pixels go R-G-B in order, not all do. To make text look sharper, most font renders will try to abuse this sub-pixel order to get sharper-than-pixel fonts. clearly there's a lot to be considered here. A no compromise monitor can cost thousands of dollars, but nice 4k 27" monitors like mine can be found for <250 on sale, and I love them. Just figure out what you need and what would be the most beneficial for you and work from there One of the great things about i3 is how powerful it can be with multiple displays, though even if you're not using i3 having a 'multi head' setup can be a god send for productivity. Even if your monitors don't match it's worth it. If you have the budget to get two matching monitors, great, if not just getting a cheapo used monitor from a thrift store will be a massive improvement. I think 2 is the magic number for most people. 3 monitors take up a lot of room and unless you do some very multi-tasked things you won't see much benefit that using something like i3's workspaces wouldn't provide anyways. Another thing to mention is red-light filters. While I dont personally use one many people find that reducing the amount of blue light coming from their displays significant helps with eyestrain. If this interests you give redshift a shot. I use it every now and then if I have a headache. Keyboard Probably the most important thing you can do for your workspace is getting a nice keyboard. If you're rocking a rubber dome or membrane keyboard, moving to a mechanical keyboard will make a massive difference. (source) The membrane/rubber dome keyboard on the left doesn't give much physical feedback to your fingers when you press a key, compared to the mechanical key switch on the right. A decent mechanical keyboard can be found on amazon for <50 USD, though as with anything in life the more you spend the better the product. One thing to keep in mind is the color of the switch used. Above you can see that keyboard has blue switches, blue switches have a noticeable 'bump', that is the switch has a spot of higher resistance before it actually botmoms out, and the key actually presses at this point, furthermore, blue keys are clicky - they are loud and some people find this annoying. Finally, they're also pretty light, not taking too much force to push down. Generally, blues are considered the 'gold standard' among typist, but games on the other hand may prefer a brown, red, or black switch. Linear Bump Bump + Click Light Red Brown Blue Heavy Black Clear Green these are the common colors and how they feel for Cherry MX switches. Most other mechancial switches are 'clones' of MX switches- though sometimes these clones are actually superiour- but these clones don't always follow this chart really it's all a matter of preference, I'm actually using a switch not listed here on my keyboard, but generally finding what you like among the above first is a good place to start. If I'm not using my main keyboard I generally use Blues. If you'd like to try some out before pulling the trigger on a full keyboard you can find switch test boards for sale online. Furthermore, there are other types of switches like IBM's old Model M line which use a buckling spring, which are quite stiff and have a very unique, heavy feeling. If you don't want to use a 20 year old keyboard Unicomp makes clones that are quite nice. You should also consider they layout of your keyboard. Some people absolutely need a number pad while others are happy to omit it and have the shorted hand travel to their mouse. Even still others want an extravagant number of keys or a weird split keyboard like mine: This is a custom built ErgoDone keyboard, The Ergodox-ez can be purchased for ~300 USD, or you can build one like mine for a bit under 200 Beyond the physical layout you may also consider the keymap or software layout. Not only does my keyboard look weird, but the keys aren't arranged as you'd expect either. Instead of typing in QWERTY, I actually use Dvorak. That layout looks a like this on a normal keyboard: though obviously anything is possible. A lot of programmers like to disable their Caps key for example and put something more useful there, or you may just want to move around a letter or two. Using a standard layout like Dovark is a bit easier though as I can easily load my keymap pretty quickly on any computer. Plain old Qwerty is fine, but I personally like my 'weird' keymap. If you're shelling out big bucks on a nice keyboard anyway, you may also want to get a keyboard which supports QMK, a completely open source firmware which gives you total control of your keyboard, allowing you do to cool things like type greek letters ( Ω , α, β) or type parentheses by tapping the shift keys. I find that particularly helpful as my keyboard doesn't actually have enough keys to do have every key nicely available (note how I don't have a function row) for more info check out https://docs.qmk.fm/#/ . You can actually buy an adapter to use a normal keyboard with QMK, but it's a bit hack-y and I really recommend just saving up to get a full keyboard made for it. Back to ergonomics, you'll want to make sure your keyboard is a t a comfortable height for you and that you can type in a way that isn't putting your wrists at any weird angles Finally, one of the nice things about i3 is the ability to navigate everything entirely from the keyboard as well as bind as much as you want to as many keys as you'd like. Want a key combo to launch a file manager? easy. Want a key to navigate to open up a terminal and immediately run a command- no problem. Set things up as you like and enjoy being able to use your system at break neck speed while everyone else drags things around slowly. Mouse and other input Speaking of dragging things around slowly: The mouse Sound Noise isolation both electrical and physical, headphone types (over, on, in), amplifiers, dacs, ASIO/ sound hardware, connection types The Desk and Chair Various Programs: Markdown [TODO] Marktext, Typora, colabrative editing, Github markup, etc Taskwarrior & Timewarrior [TODO] Taskweb File Explorers & Storage Managment [TODO] Ranger, THunar, Nautilius, Baobab, Gparted if you use Nautilius, you may want to run dconf write /org/gnome/nautilus/preferences/always-use-location-entry true  so that the file paths are displayed in full Media (Music, Video, PDF,) [TODO] Office & Creative Software [TODO] Libreoffice Krita Audacity DAW? QJackCTL? OBS KiCad darktable Evince Feh, nomacs Wine Boxes- vm Package managment [TODO] Pamac, Steam, AppImg, itch.io, dpkg, snap. maintaining an aur package, pacman conf stuff Web and network protocols [TODO] Vivaldi, Firefox, Syncthing, Beaker, IPFS, IRC - irssi, Telegram, Etherape, Wireshark, gufw, Shell Scripts [TODO] Chapter 6.1 - Git. [TODO] Show how to setup SSH keys, mention graphical git tools https://dhwthompson.com/2019/my-favourite-git-commit Chapter 7 - Let's write some Code From https://wiki.xxiivv.com/#development: Prototype before polishing. Get it working before optimizing it. Separate policy from mechanism; separate interfaces from engines. Write simple modular parts connected by clean interfaces. Design programs to be connected to other programs. Write programs to write programs when you can. Design for the future, because it will be here sooner than you think. In interface design, always do the least surprising thing. When a program has nothing surprising to say, it should say nothing. When a program must fail, it should fail noisily and as soon as possible. Write big programs only when it is clear by demonstration that nothing else will do. Programming can seem scary at first but the more you exercise, the easier and more exciting it gets. After all, practice makes perfect! :) Python [TODO] Why start with python The building blocks of programming All programming is just chaining logic, for example using treatments like "if a is b, then make c hold the value of a-3" followed by "if c is negitive then say hello" Well, that's actually an easy program a = 1 b = 1 c = 1 if a == b: c = a-3 if c < 0: print('hello')  you should notice a few weird things here though, namely, on line 5 we used two equal signs to check equality. This is the case in most programming languages because a single equal sign, like is used on the first two lines, is used for assignment that is assigning the value of a to 1 and b to 1 or as on line 6 assigning the value of ( a - 3 ) to c, because we've already used a single equal sign for assignment, two equal signs is used for checking equality. If you follow the logic here, a and b are both 1, so line 4 checks that to be true, so line 5 does happen. Now c which previously was equal to 1 is now equal to a-3, where a is 1, so c becomes -2. on line 8 we check if c is less than 0, and it is so we print the word 'hello'. Here, you'll notice 'hello' is in quotes. This is because if it were not, that is if it were print(hello) it would try to print the value of the variable 'hello' which since hello isn't defined, wouldn't work. Let's try this in the Python interpreter. You can find install instructions for your operating system here: https://www.python.org/downloads/. If you're on Linux simply type python into the terminal. With the Python interpreter open try without quotes: >>>print(hello) Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'hello' is not defined  As you can see Python failed to print hello because the variable was not defined. Now lets try assigning a value to the hello variable before printing: >>> hello = "Hello World!" >>> print(hello) Hello World!  Anything you write to the interpreter can also be added to a file and ran that way. Try saving the examples above to a file called test.py, opening a terminal and running it with python test.py. Conditions using if, elif and else You often want code only to be executed, if a certain condition is met. For example, take a look at the following code: a = 13 b = 27 if a > b: print("a is bigger") else: print("b is bigger")  Using the if statement, connected with a logical condition, you can control the program flow. In this case, a is smaller than b, so python will skip the code inside of the if case and only execute what is within the else part. You can also combine multiple if cases like this: a = 3 if a < 0: print("a is negative") elif a == 0: print("a is zero") else: print("a is positive")  Using the elif statement, you can check for another condition if the one in the if statement was false. Loops Some lines of codes have to be repeated very often. Instead of typing the same line over and over again, you can use loops. There are two types of loops: The for and the while loop. While they both basically do the same thing, sometimes it is more intuitive to use one over the other. The for loop The for loop iterates over a list of items and stores the current element in a variable. This is especially useful when working with lists, for example. fruits = ["apple", "banana", "cherry"] for fruit in fruits: print("I am eating a " + fruit)  If you are familiar with loops in other programming languages (such as Java or C), you're probably thinking: "That's not a for loop, that's a for-each!". This is true, in python all for loops are for-each loops. If you want to iterate over a range of numbers, use pythons range() function: for i in range(0, 100): print(i)  The while loop The for loop is very useful, but sometimes, using the while loop is easier and more straightforward. For example, if you want to repeat something until a certain condition is met, using this loop is simple: i = 0 while i < 10: print(i) i += 1  You can also combine the condition after the while keyword with an else statement: i = 11 while i < 10: print(i) i += 1 else: print("i is bigger than 10!")  [TODO] assignment, comparison, combined ops (+=), mod, exponent, floor, in/not in, is/is not, data types, functions libraries Common methods used commenting-out print debugging Recursion, object orientation while(true) try/catch Some simple programs Hello World As seen in the example above, the following will print Hello World!: print('Hello World!') Lets get some input aswell: print('What\'s your name?') # This prints the question. Notice the escape character \ is used to avoid stopping the string. print('Hello ' + input()) # This will pause the program and wait for user input before printing Hello <input>  Even or Odd Below is an example of a Python script which checks if the input number is odd or even. # A number is even if division by 2 give a remainder of 0. # If remainder is 1, it is odd number. num = int(input("Enter a number: ")) if (num % 2) == 0: print("{} is Even".format(num)) else: print("{} is Odd".format(num))  Prime Numbers Prime number is a number greater than 1 whose only factors are 1 and itself. Few instances of prime numbers include 2, 3, 5, 11. Below is an example of python function which defines whether the given input number is prime or not. def is_prime(num): if num > 1: # Iterate from 2 to n / 2 for i in range(2, num // 2): # If num is divisible by any number between # 2 and n / 2, it is not prime if (num % i) == 0: print("{} is not a prime number".format(num)) break else: print("{} is a prime number".format(num)) else: print("{} is not a prime number".format(num))  Calculating sine and pi Sorting a list Palindromes Cypher Making a full project Part 0, Git Before we get started, I want to be sure you took the time to read the section on Git in Chapter 6.1 above. If you need to refer to a cheat sheet you can look in Apendix B. Part 1, Starting easy [TODO] guide to write an OO python program with libraries to read and write entries to a database-like file and a real database the database should have 3 tables, a to-do list, a time-tracker list, and a list of articles To-do: NAME, DUEDATE time-tracker: 2types, either manually enterend with NAME, TSTART, TSTOP or NAME, TTOTAL for the following program articles: NAME, PUBLISHED, TPUB, TEDIT we'll need some way to track what items in the time tracker were started, but never stopped for now, everything should be strictly command line arguments and print statments More advanced topics [TODO] Move this section Lambdas A lambda expression is used to create a a small anonymous function. It can take any number of arguments, but can only have one expression. Below is an example of a lambda expression which can be used to compute cube of any given number. >>> cube = lambda x : x**3 >>> cube(5) 125  And here is the other example of a lambda expression with three arguments. >>> sum = lambda a, b, c : a + b + c >>> sum(1,2,-3) 0  threads/ parrallelization(high level only), interupts (actually, let's save this until embbeded), apis, A little more practice Weird projects https://twitter.com/Foone/status/1245610381600382976 Easing int Graphical Programming with Creative Coding http://feed.grantcuster.com/ Chapter 8 - Low Level Programming Video Link: Program in C (YouTube) the stack, pointers, etc. psuedo code, bitwise opererators, types, unsigned, signed bit, 1's compliment, 2's compliment Some simple programs, in C++ Hello World fully discect each line and call and why each line is used, ASCII table add greating and input Bit Operations Even or Odd, prime, Calculating sine and pi Sorting a list mention efficenecy, analysis later Palindromes Cypher System Calls Interupt & Signal handeling Part 2, Going Deeper [TODO] Interacting with the above, this program should run in the background and update the data, based on window focus events using libxdo This program should actually provide the VAST majority of the source code, with purposeful errors for demonstating the below furthermore, the C code should check to see if there is a new article, and if so it should call a function that first checks a 'meta' entry to see if the python code to change a published time to be newer or the number of entries has changed to optimize: • generates a template markdown file for the article if PUBLISHED is FALSE and no file for it exists, • generates a template markdown file for the article if PUBLISHED is TRUE and no file for it exists, • generates a html file from the markdown if PUBLISHED is TRUE and no html exists then updates TEDIT, TPUB • remove the html file if PUBLISHED is FALSE and an html file for it exists, however, every time this will still need checked to monitor the md for changes, using ionotify • generates a new html from the markdwon if PUBLISHED is TRUE and md has changed then updates TEDIT • if markdown is removed, the html file should be as well What are we going to do? [TODO] Tools to use [TODO] Pseudo code [TODO] Writing it [TODO] using a code editor, header files, libraries, writing and using a Make file, stdout / stderr, Debugging it [TODO] gdb + gef, gdbfrontend, Valgrind, https://cdecl.org/, etc. overflows Analyzing the Assembly [TODO] Cutter, TIS-100, Shenzhen IO, Patching it [TODO] source patching, binary patching C, C++, Rust, Go, ? File formats [TODO] wav is easy, mp3 is hard.. show this. WAV format on 767 of POC||GTFO Where to get more pracice with low level programming [TODO] https://github.com/rby90/Project-Based-Tutorials-in-C Chapter 9 - Finishing up the project Part 3, more advanced high level Modify the original python program to support a pretty cli input in a pretty way to make entries and visulize the data collected, parallelize some things, finally add a config file using yaml Part 4, getting our toes wet with embeded systems Finally, let's go back and add a com port to the C code and send data to an arduino (can be simulated) and a TFT to display the currently active task and time elapsed. Other resources and articles: Good Coders Borrow, Great Coders Steal (StackOverflow Blog) Chapter 9.1 - Other Languages of interest Low Level Rust Rust’s rich type system and ownership model guarantee memory-safety and thread-safety — enabling you to eliminate many classes of bugs at compile-time. Basically, Rust doesn't let you screw up. It enforces writing code that's safe (except when you specify you want to do something unsafe). It has a lot of other really nice features and makes using efficient data structures easy. Another really nifty thing about Rust is that it has a sort of at compile time garbage collection of sorts, for lack of a better way to put it. Read more on that here. I really recommend A half-hour to learn Rust Nannou, is a creative coding framework for Rust that's pretty nifty too. To show the maturity, just check out https://www.redox-os.org/, a full OS written in Rust! Also, it's worth noting Rust can be used to generate Web Assembly (more about that below) Other sources to lean rust: • https://doc.rust-lang.org/book/foreword.html Go Go is an open source programming language that makes it easy to build simple, reliable, and efficient software. The big claim to fame for go is, well go, which let's you do really easy threading. (https://gobyexample.com/goroutines) Other sources to learn Go: • https://tour.golang.org/welcome/1 Zig A general-purpose programming language and toolchain for maintaining robust, optimal, and reusable software. https://ziglang.org/ Zig: A programming language designed for robustness, optimality, and clarity – Andrew Kelley (YouTube) Crystal Crystal's big thing is a Ruby (a very fast to write language) that's compiled and fast. From the home page: # A very basic HTTP server require "http/server" server = HTTP::Server.new do |context| context.response.content_type = "text/plain" context.response.print "Hello world, got #{context.request.path}!" end puts "Listening on http://127.0.0.1:8080" server.listen(8080)  Seriously check it out at https://crystal-lang.org/ D A lesser used competitor to C++ mostly. It's very syntactically similar. Might be worth looking at. https://dlang.org Nim Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. https://nim-lang.org/ Further, Nim allows for easy 'metaprogramming' which basically means you can [TODO] Nim's syntax is python-like-ish Red To be honest, I'm not sure Red belongs in the low level category, as it can be ran as a JIT language. Red is a next-gen programming language, strongly inspired by REBOL. Main features are: • Human-friendly syntax • Homoiconic (Red is its own meta-language and own data-format) • Functional, imperative, reactive and symbolic programming • Prototype-based object support • Gradual and multi-typing • Macros system • Rich set of built-in datatypes (50+) • Both statically and JIT-compiled to native code • Cross-compilation done right • Produces executables of less than 1MB, with no dependencies • Concurrency and parallelism strong support (actors, parallel collections) • Low-level system programming abilities through the built-in Red/System DSL • Powerful PEG parser DSL included • Cross-platform native GUI system, with a UI DSL and drawing DSL • Bridging to the JVM • High-level scripting and REPL console included • Visual Studio Code plugin, with many helpful features • Highly embeddable • Low memory footprint, garbage collected • Single-file (~1MB) contains whole toolchain, full standard library and REPL. • No install, no setup • Fun guaranteed! https://www.red-lang.org/p/about.html If you're interested, check out Red's 'Getting Started' page. Haxe Haxe is an open source high-level strictly-typed programming language with a fast optimizing cross-compiler. https://haxe.org/ Java don't. but, here's why not to use Java: WebAssembly WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable target for compilation of high-level languages like C/C++/Rust, enabling deployment on the web for client and server applications. https://webassembly.org/ While not technically a programming language, I wanted to bring it up and encourage you look into it to be used instead of JavaScript for real projects. Call for Contribution If I missed a language you think I should have mentioned or would like to write a nice guide to your language of choice to be included in this Opinionated Guide please submit a pull request. I'd love to expand the Rust, Go, and Zig sections significantly! High Level [TODO] probably going to need to break this out into it's own chapter JavaScript Fine. I'll talk about JS. But, please. For the love of god do not use this to make an Electron App. Before going to far, I do want to mention that a chunk of my hatred for JS is solved using frameworks and that I totally acknowledge the utility of JS for making quick, often very cool, 'sketches'. The creative coding community is amazing. Further, JS, as much of a total dumpster fire as it is, is responsible for the Internet as it is today weather thats a good thing or not. CoffeeScript https://coffeescript.org/ TypeScript https://www.typescriptlang.org/ Frameworks https://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks Angular React Vue Node PHP don't. but, here's why not to use PHP: If you must, you might want to check out Hack: https://hacklang.org/ Ruby A dynamic, open source programming language with a focus on simplicity and productivity. It has an elegant syntax that is natural to read and easy to write. https://www.ruby-lang.org/en/ For the Skript Kidd3s In programming and hacking cultures, a script kiddie, skiddie, or skid is an unskilled individual who uses scripts or programs developed by others to attack computer systems and networks and deface websites, such as a web shell. It is generally assumed that most script kiddies are juveniles who lack the ability to write sophisticated programs or exploits on their own and that their objective is to try to impress their friends or gain credit in computer-enthusiast communities. However, the term does not relate to the actual age of the participant. The term is considered to be derogatory. from https://en.wikipedia.org/wiki/Script_kiddie But, really, some absolutely incredible code has been written in the following languages. They more than serve their purpose and are generally some of the fastest "I just need a quick and dirty solution" options out there. Not everything needs a blazing fast hand optimized C implementation, and code that's really just for personal use, to acomplish a one-off task, or that runs inside a bigger program (3D modeling software like Blender, Video editing software like Premier, Game development editors, etc.) should probably be easy to read and modify quickly. Rapid prototyping certainly has it's place. Just don't think you should use these to write efficient, safe code. LUA MoonScript AHK Tasker (Android) CMD.exe Bash, ZSH, Fish, Xonsh, wut? Node-Red n8n Is this even Programming anymore? Pure-Data vvvv tooll.io ORCΑ Esolangs, the hole goes deeper https://en.wikipedia.org/wiki/Esoteric_programming_language https://esolangs.org Graphics Programming look to chapter 26 for programming involving graphics, including node based shader editors and more Functional Programming Look at Chapter 27 for Functional Programming Lisp, Haskell, Luna, Database (SQL) Look at Chapter 18 for information on Databases Coding Challanges Obfuscated C programs: Introduction (YouTube) Obvuscated C, https://www.ioccc.org/ Source: https://gist.github.com/munificent/b1bcd969063da3e6c298be070a22b604 Chapter 10 - Networking [TODO] Add follow along making a network stack A typical network [TODO] Default Gateway, Routes & kernel routing table, subnet mask, ping, traceroute, dns - resolv.conf, pihole, caching / squid, localhosts, port forwards, DHCP, private nets, firewalls, chromecast port thing, https vs no s, rsync,scp,samba, cups, databases , pihole, BGP, RIP, OSFI, multi-zone wifi, single ap multi freq wifi, enterprise security, secured ethernet, https://blog.cloudflare.com/how-verizon-and-a-bgp-optimizer-knocked-large-parts-of-the-internet-offline-today/ The OSI model of networking is The physical Layer Coax, Fiber Wireless Hubs, Repeaters Ethernet PPP Switch Bridge Frames Network Packets IPV4, IPV6 MAC ICMP, IGMP Transport TCP UDP Session Authentication Sockets API's Presentation Common Protocols Application HTTP https://www.monkeyuser.com/2017/http-status-codes/ FTP DNS SSH IRC EMail Time Real time clocks, timezones, utc, etc. VPNs Networking Tools Etherape Wireshark Nmap Chapter 10.1 - Weird Networking, because why not! Netsukuku, cjdns + hyperboria, Dat / Beaker, EVE Online internet Software Defined Networking, ActivityPub Chapter 11 - High Level Overview of Math, Physics, and Chemistry (Sorry...) [TODO] Chapter 11.1 - Math some motivation, Klien bottle guy 1 - Algebra Imaginary numbers, systems of equations 2 - Discrete Math http://discrete.openmathbooks.org/dmoi3/ 3 - Trig 4 - Calculus 5 - Differential Equations 6 - Matrix Theory / Linear Algebra https://readhacker.news/s/4aVPz https://readhacker.news/s/4aUb6 7 - Signals An Interactive Introduction to the Fourier Transform https://ocw.mit.edu/resources/res-6-007-signals-and-systems-spring-2011/ https://en.wikibooks.org/wiki/Signals_and_Systems Chapter 11.2 - Physics 1 - Newtonian 2 - Electromagnetism 3 - Relativity and the Quantum Chapter 11.3 - Chem 1 - Atomic Structure, Basics of the Table, Bonding 2 - Acid/base, Electrochem, Thermochem, Photochem 3 - Organic Chemistry Yeast that produce PENICILLIN - Whose Gene is it Anyway (YouTube) Chapter 11.4 - 'The Rest' English [TODO] Because the majority of the Internet and most publications are in English Other sources, interesting videos, etc: • Minute Physics, Thought Emporium, Cody's Lab, 3Blue1Brown Chapter 12 - Circuits Continued [TODO] Show everything in a circuit sim, fix heading levels (this is a mess) Possibly break up this chapter? Transistors, the opamp, etc alone may each justify their own chapters That said, I don't want to get to in the mud of transistor physics. I really want to focus on how/when/why to use what, not how they work as the physics is both pretty hard to grasp and not super useful. Still would like to mention that switching is what uses power and like processe size things, but maybe not the chemistry or electron tunneling effects Chapter 12.1 - Semiconductors Diodes, the one way road [TODO] zeener, normal, bipolar • varistors , sparkgaps • Leds - getting current both ways, LED safety Diode Logic Transistors [TODO] tubes and how they work PNP V NPN IGBT, Mosfets? Integrated Circuits [TODO] https://hackaday.com/2019/05/20/integrated-circuits-can-be-easy-to-understand-with-the-right-teachers/ Uncovering the Silicon: Demystifying How Chips are Built and How They Work (YouTube) Reverse-engineering the TL431 555, OpAmp, 74-Series Logic 555 Timer IC (YouTube) potato semi Chapter 12.2 - Opamps & Filters Optical Electronics [TODO] Crystal Oscilators [TODO] Piezoelectricity - Why hitting crystals makes electricity (YouTube) PWM [TODO] ADC/DAC [TODO] https://en.wikipedia.org/wiki/Fourier_transform Nyquist Active Filters http://sim.okawa-denshi.jp/en/ [TODO] Audio Devices [TODO] speakers, piezos, amps, mics and pickup patters TODO add motors, analog meters, various connection standards, radio, flex/pressure sense, grounding (chasis, digital, analog, ground planes, etc.), solar/photo reactive, Relating AC and Music [TODO] Relate back to things like ADRS, Distortion, Reverb / Echo, Decibels (audio), etc. Use VCV RACK Continued Reading: [TODO] At this point I highly recommend 'Practical Electronics for Inventors' ISBN 978-1259587542, namely chapters 2-12, and 15-16. It's a very large, detailed book that does it's best to keep things, well, practical. https://taleri.files.wordpress.com/2014/02/practical_electronics_for_inventors_-_scherz_paul.pdf Hardware isn't generally copyrightable Chapter 13 - Digital Logic What is digital logic? ignoring the analog world (10%/90%) Truth Tables, K-Maps min/max terms, Don't cares, SOP/POS, multiple out Basic Logic Gates Not Truth table, transistor implementation pmos/nmos, cost, power consumption at switch And, Nand Or, Nor, Exnor Xor, Exor Transmission, Mux, Demux, encoders Basic combinational logic propagation delay, fan in/out, POS/POS 2's Compliment, Floating Pt, Math overflow, carry, ripple, fast, mul, shift-and-add mult, divider, Latches and Flip Flops SR, Dl, edge triggering, Dff, Tff, JKff, Registers Counters More Digital Logic resources We'll come back to look at more complex digital logic in chapter 28 "Let's try out programmable logic" and 29 "Let's make our own SOC" , but if you're hungry for even more, here are some resources Chapter 14 - Embedded Systems [TODO] What is an Embedded System? PWM, SPI, I2C, What's going on?! Making an Embeded System project - 1 - Humidity Sensor Making an Embeded System project - 2 - MIDI Controller (with piezzo) Making an Embeded System project - 3 - Stepper Motor Music adapted from floppy drives, but less expensive Real Time Operating Systems RIOT-OS, MBED, etc Other weird and cool projects: Of Course It Leaks! Chapter 15 - Discrete Math and Algorithms [TODO] Discrete Math Truth tables, binary, logical equlivencies, propositional logic, Sets, functions, relations, recurrence, induction, combonation, graphs, isomorphsm, Sets are a well-defined collection of distinct objects. A set is represented in two ways, Rooster form or Set builder form. Rooster form:- In this form we show all the elements in a set in curly brackets. For example: A set of odd numbers is {1, 3, 5, 7, 9, ...) A set of animals can be {Dog, Cow, Cat, Lion} Set Builder form:- In this form we show all the elements by using a property that all the elements of the set follow. For example: A set of even numbers upto 10 is {x | x is even and x <= 10} which is read as x where x is even and less than or equal to 10. Operations on Sets:- Unions:- A Union of two sets is a set which contains all elements of both the sets. A Union of set A and set B would be represented as, A⋃B. For example: The Union of Set A = {1,3, 5, 6} and Set B = {1, 2, 4, 6} is A ⋃ B = {1, 2, 3, 4, 5, 6} Complexity analsis +recursion analysis, P vs. NP (YouTube) Brute Force Data structures trees, hashtables/maps, stacks Practice Fib, some pracice logical equliv, base conversion algo, overlapping lines, matrix multiplication Chapter 16 - Writing a larger program [TODO] Object Oriented Programming Planning Software Engineering Chapter 17 - Servers! [TODO] What's a homelab? Why build a server DIY Networking: Routing, firewall, etc. Web hosting Before we get to business there's some necessary viewing: http://motherfuckingwebsite.com/ File Storage, Sharing, Backups Remote Access Git, Games, and Glory Virtual Machines Containerization Fault tollerence Chapter 18 - Databases [TODO] Otherwise known as the chapter about sanitizing your inputs. // insert xkcd drop tables Chapter 19 - Debugging, Automated Building and Testing Automated Building Debugging Software Debugging [TODO] GDB with Gef, interpreted languages, embeded systems, non-code isssues (boot problems, glitchy behavior), hardware failures, valgrind, various trace programs, print debugging extended Hardware Dubugging common interfaces, simulation, serial/print debugging (slow), internal data logging, physical indicators of internal state, hardware to facilitate debugging (LED 'byte') Testing Software Testing Hardware Testing Automated Building and Testing [TODO] Fuzzing (sandsifter), make and alts, etc. Continuous Integration Continuous Deployment Chapter 20 - Compilers and Assemblers [TODO] Making a compiler and assembler, DIY language eso-lang style Making an interpreted language Making a compiled language https://medium.freecodecamp.org/the-programming-language-pipeline-91d3f449c919 Continued Reading At this point I highly recommend 'The Art of Exploitation' by Jon Erickson Chapter 21 - Exploitation Often when we think about Exploitation, better known as hacking, we conjur images of a more-punk-than-cyber cyberpunk person clicking away wildly on a keyboard as code flies by, like the 1995 movie, Hackers, and to some extent this isn't wrong, as one look around the floor at DefCon, will show you. And honestly, that's to by accident. While there are strictly professional security experts, those that work at corperations and banks, a large number do it for the lolz, for fun, and to bring a little fun back into computing. Calling exploitation 'hacking' is almost a misnome, as hacking encompases a lot more than exploitation, and exploitation a lot more than hacking. For that reason, before we start, I recomend you watch this video, on speed running Super Mario 64, this is a prime example of exploitation in a non-harmful manner done for fun. [TODO] Types of exploits [TODO] - where to put return oriented programming, super old hardware/software - 'the home router', Otherwise known as hacking, exploitation of software is always alluring, though in reality like many things it is much less glamorous than the news or tv make it out to be. Before I get into it I want to plug 'The Art of Exploitation' by Jon Erickson again, as it truly is a masterpiece that describes exploiting in a way that just makes sense Software Injection - SQL breaking hashes Heap/buffer overflow dangaling pointers code-injection clock attacks Race conditions Path traversel format string pseudo-random Fuzzing Networking DoS/DDoS MitM XXS MAC/IP spoofing sniffing Hardware Intro to Hardware Reversing: Finding a UART and getting a shell (YouTube) Talk about CPU bugs Power side channel Timing attacks pseudo-random (hardware side) Hardware trust (HID injection) replay attacks radio, rfid, etc rowhammer, Heartbleed Social Engineering Phishing spoofing (email, phone) UTF-8 v ASCII click jacking expired certificate default passwords honey pots Physical security Lock picking as a last resort data destruction Malware Section here about not being a dick Viruses polymorphic boot-record trojan logic/comression bomb logic/time bombs ransomware adware/spyware Tools of the trade Many tools in common with debugging (gdb - gef, hex editors, logic analzer) and testing (fuzzing) decompilers, dissassembly, analysis Wireshark Cheatengine dynamic linking Getting some practice CTF-Time PWNie Island Where to learn even more: Live Overflow, Youtube: https://www.youtube.com/channel/UClcE-kVhqyiHCcjYwcpfj9w/playlists Phrack : http://www.phrack.org/ Defcon Media Server : https://media.defcon.org/ As mentioned above in Chapter 17- Compilers and Assemblers At this point I highly recommend 'The Art of Exploitation' by Jon Erickson https://microcorruption.com/ , https://ctftime.org/ , CTF time, https://nagarrosecurity.com/blog/interactive-buffer-overflow-exploitation Some Hacking Community Fun https://www.youtube.com/watch?v=Jwpg-AwJ0Jc https://www.youtube.com/watch?v=UBaVek2oTtc https://www.youtube.com/watch?v=bouYRMItWnI https://www.youtube.com/watch?v=RDZnlcnmPUA https://twitter.com/Foone/status/910217984098017281 Does register selection matter to performance on x86 CPUs? Leap Day Bugs Never claim something is 'unhackable': https://techcrunch.com/2019/05/10/eyedisk-encrypted-flash-drive-unhackable/, DEF CON 18 - Zoz - Pwned By The Owner: What Happens When You Steal A Hacker's Computer (YouTube) Diabetics Are Hacking Their Own Insulin Pumps (YouTube) Big List of Naughty Strings (Github) Chapter 22 - Security [TODO] focus on how to write secure programs, protect hardware, etc. Chapter 23 - Open Source, Licences, and Copyright [TODO] actually contribute on github, make an issue, submit a pull request, make a custom repo, Chapter 24 - Let's make our own PCB [TODO] First things first, we're going to be using Kicad, so you'll want to go grab that from the repos. While that's downloading and installing give this a watch to get the basics down: KiCad Quick Start Tutorial (YouTube) Src: Foalyy @ https://forum.kicad.info/t/cheatsheet-for-kicad/5247 https://llllllll.co/t/pcb-art-artfully-shaped-copper-traces/22027/2 Chapter 24.1 - PCB 'Badges' Source: @AkioOhtori on Twitter https://github.com/badgeek/svg2shenzhen Chapter 25 - We've got cores, let's use em' [TODO] https://lemire.me/blog/2020/01/30/cost-of-a-thread-in-c-under-linux/ Chapter 26 - Graphical Programming Let's start in a way that's incredibly simple, and abstract away all the hard stuff at first by using a tool kit called 'Processing', which is available under that name from the community repo in arch. The default IDE that comes with it is awful to work in though, so go ahead and open up VSCode and grab the Processing Language add on, then in VSCode open up a new workspace folder and make a file called processing.pde, then open VSCode's command pallete (CTRL+Shift+P) and run 'Processing: create task file', after that you'll want to open the tasks.json file and change the command: line to have "command": "/usr/bin/processing-java", after that you can easily try new code just by re-building project the project with CTRL+Shift+B Alright, setup out of the way, let's code! One of my first projects in processing was to make a Topographic Map, looking generator because I just find them quite visually appealing. So, thinking about that problem, we clearly need data. probably an array of sorts with a bunch of values that have a smoothed relationship when viewing them as height map, then we'd want to look at the transition points between ranges of values. Looking up random data generation in python, and you should stumble upon it's noise generation, and see that it uses Perlin Noise, which upon looking at it should be obvious that it generates exactly what we want. So, looking up an example for that in processing we get to this page: https://processing.org/examples/noise2d.html Well, that's already super close, so let's look at that code float increment = 0.02; void setup() { size(640, 360); } void draw() { loadPixels(); float xoff = 0.0; // Start xoff at 0 float detail = map(mouseX, 0, width, 0.1, 0.6); noiseDetail(8, detail); // For every x,y coordinate in a 2D space, calculate a noise value and produce a brightness value for (int x = 0; x < width; x++) { xoff += increment; // Increment xoff float yoff = 0.0; // For every xoff, start yoff at 0 for (int y = 0; y < height; y++) { yoff += increment; // Increment yoff // Calculate noise and scale by 255 float bright = noise(xoff, yoff) * 255; // Try using this line instead //float bright = random(0,255); // Set each pixel onscreen to a grayscale value pixels[x+y*width] = color(bright); } } updatePixels(); }  Alright, so line by line, it seems that line 1 is just defining a constant. Reading the Processing docs you'll find setup() should contain size() which takes two arguments that are the size of the output window in pixels (x and y) and that draw() is an endlessly looping function that updates that window. Before going further let's copy and paste the code into VSCode and run it: [TODO] add picture [TODO] C++ from scratch, JS electron app, Processing creative coding, Python Kivy or similar, Flutter (google lang), shaders (graphical editors), nimp, ronin, Nuklear GP-GPU Chapter 27 - (((())(()((()(())))))) [TODO] Functional Programming, and other paradigms : lisp, haskell, luna-lang.org, ronin Chapter 28 - Let's try out programmable logic [TODO] Finite State Machines, VHDL, Verilog, FPGA & CPLD internals Chapter 29 - Let's make our own SOC Before we start, I'll warn you this isn't easy, but it's also not as bad as it sounds, and it's certainly not as bad as it used to be [TODO] FPGA Linux Kernel drivers An FPGA that only plays Doom Chapter 30 - 3D printing, CNC, and making things [TODO] While this book/guide/thing primarily focuses on the less mechancial-engieering-y side of things, it wouldn't make sense not to include at least a little about 3D printing, molding, materials, gears, springs, and the like. So, here goes: Giant Mechanical Iris! Cut on a CNC Router (YouTube) Chapter 31 - Fine, I'll talk about AI Neural Network Architectures (YouTube) Chapter 32 - Ham Radio '137Mhz' by u/CashewHut LORA 2.4Ghz patch antenna electronically tunable filters https://newhams.info/2017/02/17/rf-connector-types/ Waveguides Explained (YouTube) How a Crystal Radio Works (YouTube) Wrapping up - Where to go from here [TODO] Integrating other interests Projects to work on Contributing to Open Source Appendix A- Using the Linux Shell The Basic Commands Of note, while the majority of these commands should be available on nearly any unix system you may use, many of the alternate recommendations may not be. • man "man [command/topic]", ex, "man ascii", bring up an indepth manual page for a given command/topic. • Alternative recommendation: tldr, actually digestible and much faster when it gives enough info • pwd - Print working directory - literally just a command to tell you the file path to where you are • ls - list - list the files/folders in the current directory, lots of flags available • Alternative recommendation: exa • cd - change directory, if you can't use this may god have mercy • Alternative recommendation: j (for autojump) • mv - move (or rename) a file to a new location (or name) • Alternative recommendation: rsync • rm - remove a file/folder • touch - create an empty file, or change last accessed time of existing file • mkdir & rmdir - make or remove an empty directory (folder) • cat - output the contents of a file • Alternative recommendation: bat, less, more, fltrdr, or an editor like vim or nano • date - output current date and time • chmod & chown - change a file or folders permissions or owner • ln - make a symbolic / hard link (shortcut) • du & df - Disk usage and disk free, df will show you how much room you have left per disk, du serves to help find what's using up your disk • Alternative recommendation: ncdu doesn't suck. • clear - clear the screen of text- (only use in scripts) • Alternative recommendation: ctrl + l , much faster • passwd - change a users password • sudo & su - run a command as another user, typically root • head & tail - print a number of lines from the top or bottom of a file • tee - mostly used with pipes to print output to terminal as well as put it into a file • grep, sed, awk, tr - the 'big four' commands used for text processing in a terminal. grep (and egrep) are used for search, for example running ls | grep myfile to confirm a file is indeed in a folder. sed is used for text/character replacement. awk is a programming language in it's own right, used primarily for selecting text fields by separator, for example only printing the permissions column in the output of ls -l • w - show who is currently logged in and what they're running, epically applicable on shared servers if you need to see if there's an active ssh connection to your system • tar, gzip, bzip, zip - all used for making compressed folders (like .zip files) • ssh , scp, ftp - used for doing remote access, letting you run commands on one system from another • diff - show the differences between two files • sort - sort input by a number of criteria • uniq - remove duplicate entries • fdupes is recommended if the goal is to identify duplicate files • export - used to set environment variables, these for example use export EDITOR=nano to use nano as your terminal text viewer by default. • systemctl - literally system control, wayyy to big to cover quickly, used for everything from setting services to run on boot, shutting down/restarting the system, to viewing logs. Look up Systemd for more information • ip, ping, & dig - ip is used to view as well as modify aspects of network configuration at the more hardware-level, such as turning on/off a networking interface. ping allows you to see if you're able to reach a site/ip address, and dig allows you to check if you're able to turn a domain name to an ip, such as checking the ip address that archlinux.org points to with dig archlinux.org • ps - process management: listing processing, finding the parent of a particular process, etc. • free - display information about system RAM usage • top - a graphical-ish view of the running processes, ram, and CPU usage • Alternative recommendation: htop • kill, murder a process in various ways • whereis - find the location of an executable, ex whereis ls will tell you it's in /usr/bin/ls • wget, curl - retrieve a web page • Alternative recommendation: lynx, w3m Tab Completion and faster navigation Probably the most useful shortcut for using the shell is tab completion. This is used when you need to type a really long command or chain of commands, say I want to run ncmpcpp, a name that is both long and hard to remember, instead of just typing the full name I can type ncm and press tab, and ta-da suddenly the full name is inserted. If you happen to have another package that has multiple possible endings say you want to run lstopo but you have ls, lsusb, lstopo all on your system, most shells will display a menu underneath with all the possible options. This is nice for commands, but the true power comes in file names, say I want to run cat /etc/pacman.d/mirrorlist while that's not too awful to type out, you could easily type cat /e press tab, get cat /etc/ add pac to get cat /etc/pac press tab, get cat /etc/pacman.d/ type mir and tab and get the full command, while that sounds complicated it actually speeds using the command line up rather significantly and prevents spelling mistakes Next up for navigation is directory shortcuts, these can be massive time savers, the most obvious is ~ which is just short hand for the location of the current shell users home directory, so in my case ~ is the exact same as typing out /home/vega. The next two have already been touched on which are . for the current directory and .. for the previous directory. Depending on the shell and arbitrary number of dots may take you back and arbitrary number of directories. Give it a shot! If nothing else you can always use ../../.. to navigate back as necessary. Finally, - represents the last directory you were in so if your in ~/Downloads and then cd /etc/pacman.d/, running cd - will bring you back to downloads. The most advanced form of built in linux navigation comes in the form of pushd and popd, which as their names imply push and pop directories to a stack (a special kind of list) of directories. Like a stack of any item you can put or 'push' an item on top, and take or 'pop' an item off. Running dirs -v will show you a numbered list of the stack, you can navigate to the top item with popd or and abitrary item with cd ~# where # is the number as shown by dirs -v. Finally, there's one more super handy way to get around your file system but it's a non-standard tool so most systems or servers you use other than your own will not have it installed, and that's autojump. Put simply it takes a good guess about where you want to go by only typing part of the name of a folder you've navigated to before, so say you have a long file path /mnt/data/archived/january2000/pictures/family/vacation/ you can get back to it again by simply running j vac which is obviously much simpler. It works the vast majority of the time in practice, only having issues if you don't include enough letters leading to ambiguity. I/O redirection for the hard core, you can read good documentation here: https://www.tldp.org/LDP/abs/html/io-redirection.html • stdin (<) (<<) [TODO] • stdout (>) (>>) [TODO] • stderr (2>) (2>>) [TODO] Note, &> redirects both stderr and stdout • pipes ( | ) Finally, the weirdest and rarely used <> operator can be used to directly attch file descriptions and read/write files dirctly, this is rearely used as it's kind of a pita, but if you need to script something advanced it's available. Stollen from the above advanced link: [j]<>filename Open file "filename" for reading and writing, and assign file descriptor "j" to it. If "filename" does not exist, create it. If file descriptor "j" is not specified, default to fd 0, stdin. An application of this is writing at a specified place in a file. echo 1234567890 > File # Write string to "File". exec 3<> File # Open "File" and assign fd 3 to it. read -n 4 <&3 # Read only 4 characters. echo -n . >&3 # Write a decimal point there. exec 3>&- # Close fd 3. cat File # ==> 1234.67890 Random access, by golly. Wild Cards & Regex Regular Expressions or 'Regex' are an incredibly powerful tool used to match strings in a logical way. For example, say you wanted to find all the phone numbers on page that started with the area code 555, the next three digits were any number, and the last four digits could be represented as either numbers or letters, and '-' separating each group. With regex that's easy, the regular expression for this looks like: 5{3}-[0-9]{3}-[a-zA-Z0-9]{4} Which while I could explain, I think just staring at that a little while should make it obvious and ideally the mental effort will lead to a better understanding. Regex can do a lot more than this though. Go ahead and checkout https://regex101.com and give it a shot. regex can be used with a bunch of common tools like awk, sed, and grep. This means you can do fancy things like chain ls and grep together with a pipe to find any file matching a pattern or chain commands to rename any file containing characters which may be invalid in NTFS ( The file system used by Windows) to be valid before doing a transfer. Job Control [TODO] • fg • bg • jobs • & operator • Ctrl+z • Ctrl+c / +d Shortcuts • ctrl-z to bg process, fg to resume • jobs -l or ps -a to see jobs • reptyr to move • pushd/popd & dirs to use path stack • cd - to last dir • history, and !№ to run that cmd • ctrl-c/d to kill • ctrl-l to clearscrn • ctrl-u to clrline • ctrl-r to search hist • ctrl-left/right to nav args • expansion with mv /path/meh.{md,txt} Aliases and customization [TODO] Shell Scripting [TODO] xargs, sed, awk, fzf, grep, https://shellmagic.xyz/ https://wiki.bash-hackers.org/ Alternative Shells When we installed arch we actually changed the default shell from bash to zsh, but there are other options such as fish, csh, and xonsh among others [TODO] Alternative commands • bat • alternative to cat, capable of syntax highlighting and line numbering • exa, lsd • alternatives to ls, eaiser on the eyes • You could also use ranger or nnn two fully featured terminal file browsers • fd • altertnative to find, doesn't suck • htop, gtop • alternatives to top, doesn't suck • prettyping • alternative to ping, pretty • diff-so-fancy, icdiff, Delta • alternative to diff, but better • ncdu • while much slower than du it's great for finding out what's eating storage space • choose • user friendly, simple alternative to awk/cut Useful Non-Stock CLI Tools • tldr • tldr, 'for too long didn't read' provides a quick, easy to read version of the man page for many common linux commands. Forget how to use tar ? just run tldr tar • autojump • refrence above description in faster navigation • mpd + ncmpcpp • 'music player daemon' and 'ncurses music player client plus plus' are two cli tools that work in tandem to provide an experiance that I presonally find superiour to any graphical music player • irssi • full featured IRC client, chat right from your terminal • screenfetch • get some nift stats about your terminal, add to your shell's RC file to be one of the cool kids • moreutils • "moreutils is a growing collection of the unix tools that nobody thought to write long ago when unix was young." • hr • Need some way to visually seperate things, this literally just makes a horizontal line in the terminal • fltrdr • Wanna read at 1000wpm, this is the tool for you. • crex • test regular expressions in the terminal • lynx, w3m, browsh • Browse the web from a terminal (not a joke and actually useful) • entr • monitor file system for changes • noti • send a graphical system notification when a command finishes • progress • start a command and have no way to see what its doing (rsync, cp, etc)? This is your tool • figlet, toilet, banner • makes big text, run figlet Your Text Here and see your text in big, ascii letters • no more secrets • reveal text in a martix effect.. I'm streching the meaning of useful here • stress-ng • stresstest your system in pretty much any super specific way you can think of, or hammer your cpu to test an overclock • pandoc • convert between damn near any text format to any other format • taskwarrior • keep track of To-Do's and tasks, can also be paired with timewarrior for timetracking • waifu2x (many forks available) • Upscale and de-noise images zoom-and-enhance style but for real- this ones' a bit GPU intensive because it uses AI • youtube-dl • despite the name this tool can download videos or audio from almost any page on the internet, even supporting playlists in many cases too. • rat • "Compose shell commands to build terminal applications" • magic-wormhole • tool for getting a file between two systems easily and secure, just run wormhole send and wormhole recive on the respective systems • Ix, Gist • Paste tools, like pastebin • DMIDecode • get info from BIOS • hexyl • pretty terminal based hex viewer • UXY • "UXY tool also wraps some common UNIX tools and exports their output in UXY format." "UXY is a tool to manipulate UXY format, which is a basically a two-dimenstional table that's both human- and machine-readable." This gives a nice format for manipulation of commands though pipes for super complex shell scripting • lsof • list what files a runnig process has open While some of these may be included, they're some of the OG addons or tools to make included things better: • tmux • multiplex your termianal, open multiple terminals in your terminal, usefull in non-graphicas ttys espically • vim + extensions (neovim, spacevim, etc) • the old school text editor meets new school • GDB + gef • GDB, the original debugger, has it's faults. GEF, a config file for GDB on steroids, fixes many of them. While originally made for exploit developers, many people use it for everyday debugging • resh • replacement for ctrl+r history seach Common Graphical Linux Utils [TODO] Mostly taken from https://wiki.archlinux.org/index.php/List_of_applications and https://github.com/Kickball/awesome-selfhosted Graphical Enviroments++ Gnome, KDE, Pantheon, Rofi, Polybar, j4, Compton Nitrogen, pywal, (feh), Free Graphical Utilities Office & Daily Libreoffice, Xournal++, thunar + bulk rename, nautilus, Filezilla, Deluge, qBitTorrent, Firefox, Min, Vivalidi, Marktext, Typora, Notable Geogebra Evolution Evince A/V Feh, Nomacs Rawtherepee, Krita, Gimp, Darktable Inkscape, Blender, Pencil2D, OpenToonz Goxel, Pithos, Gnome-Music, Cadence (jack2) Audacity, Ardour, LMMS, non, Radium Giada VCV Rack Guitarix PureData, SonicPi, ORCA Processing, VVVV, VLC DaVinci Resolve Cheese, Motion, OBS Social Thunderbird LBRY Discord, Telegram, qTox, HexChat, SRain, Riot/Fractal , Programming Okteta Gitkraken Code, Atom, Sublime, Code::Blocks, Eclipse, Netbeans, IntelliJ, Sublime PyCharm, Spyder Cutter, Node-Red Etherape/cap, Wireshark Engineering FreeCAD, LibreCAD, KiCad, CircuitSim, Fritzing PulseView, Arduino, PlatformIO System Alacritty, urxvt, Deepin-Terminal, Hyper, Baobab, Filelight, GParted, VeraCrypt Syncthing Etcher lsusb, lshw, lstopo, usbview, Firewall frontend? ClamAV deepin-screesshot, scrot IRL Gnome-Maps Gnome-Weather Celestia Stellarium Other GnuRadio, SDRAngel Renoise, Bitwig Self hosted / Services Netdata VPN (Wiregaurd) Snort, Suritica Gitea, Gitlab Mathics LAMP stack Couchpotato, headphones mpd, ampache Owncloud, NextClound Samba DAT, IPFS Convos.by Ix , 0bin (pastebin) Mathics TaskWeb (TaskWarrior) Appendix B - Cheat Sheets and quick info Electrical Part Tables [TODO] • package types • reading specs • datasheets * Git Markdown # heading1 ## heading2 ### heading3 --- on it's own line will give you a diveder line * for a bulleted list * alternatively, - works too - ~~The world is flat.~~ for a strike though, **to bold** *to itilicize* 1. for a numbered list 2. ​python ​ for a code box, where 'python' can be whatever language you want syntax highlighting for single backticks (note, these aren't apostrophes) for in line code too > lets you make a block quote markdown also lets you use inline HTML, so, depending on the intent to render out to a pdf or webpage, you may be able to embed YouTube Videos or Tweets or whatever like I have through out this guide. [title](https://www.example.com) for links ![alt text](image.jpg) for images | Tables | Can | | ------ | ------- | | Be | Made | | Like | This | Here's a sentence with a footnote. [^1] [^1]: This is the footnote. - [x] This is a task list - [ ] As we go down this page - [ ] Some of this syntax may not be supported$ may let you type inline math in \LaTeX $, and$ for blocks, same as the code syntax

1^2 or 1~2 may let you write super and sub-script text as well.


Appendix C - BOM

[TODO - FINAL REVSION]

Item Price/item (approx) Quantity
Backup Hard Drive 40/Tb optional
Thumb Drive 8 1
Arduino nano 5/board 2
ESP8266 5/board 2
STM32F103C8T6 w/ programmer 8 Optional
ICE-Breaker FPGA 80 Optional
74-series logic IC's 25 Optional
Assorted Resistors 10
Assorted Potentiometers 5
Assorted Capacitors (Ceramic) 10
Assorted Capacitors (Electrolytic) 10
Assorted Inductors 5
Assorted transistors 8
Assorted Diodes 10
Op-Amps (UA741) 5/10
Assorted LEDs 5
Assorted Crystal osc
555 Timers 4/10
Hook up wire
jumper wire
Solid Core wire Optional
Proto PCB
Buttons
DIP Switches
7-segment display
OLED display 6
Accelerometer Optional
Servo
Relay board 5
Lab Power Supply 35 1, 2 optional
Soldering Iron (TS100) 75 (full kit)
Solder 9/spool
Flux 10/4oz
Osciliscope 30 for a shit, \350 for a good one Optional-ish
Multimeter 35
Logic Analyzer 10
Software Defined Radio 150 optional
Proxmark3
TOTAL BASE ;OPTINONAL

Also we're going to be building a little server, for this you'll want

Item Price Quantity
ASRock J3455-ITX 75 1
ITX, SFX case (APEX MI Series MI-008, with power supply) 50
DD3L 40/8Gb 1
1Tb 2.5" hard drive (Redundant Storage) 55/dive 2
120Gb SSD (OS) 20
Extra Network interface card 25 Optional
Total (Barebones)
Total (Optional)

OR

You can find a used Dell Poweredge r610 or poweredge 1950. Many of these will come with out drives, but this option is probably cheaper than the above for better specs. However; these servers are LOUD, loud enough to not be comfortable in the same room and absolutely drink power. As mentioned in the server section, the hardware you use really doesn't matter, you'll just want at least two hard drives, an OS drive, and multiple network interfaces are encouraged. These things can all be added to just about any desktop though, so going to electronics thrift stores or auctions and finding a desktop works too.

Getting things for cheap

salvage, auctions

Appendix D - Politics and Ethics

Img credit, Kokofox @ https://kokoscript.com/

Don't feed the Trolls

Because you're now somebody in the know about topics relating to technology and have a deeper understanding about issues that may effect the public, such as The FBI V Apple encryption case, Issues regrading internet speed and infrastructure, or The Government/NSA spying on people. There are plenty of issues that weather you like it or not you're one of the few with enough information to truly understand and inform your peers. A well known digital writes and freedom advocacy group you may consider supporting is the Electronic Frontier Foundation or EFF, as they do some absolutely incredible work making sure we maintain our digital rights both in the role of consumers as well as hackers, tinkerers, security researchers and nerds. You may consider checking out Free press as well, though above all else educating yourself and others about issues to end ignorance and fear when it comes to these issues is more valuable than anything else.

Furthermore, there's a general view in the technical community that we should help push adoption of superior platforms. This is usually either for a push for decentralized services like Mastodon or Dat, or a push for FOSS (Free and Open Source) software like Linux or LibreOffice.

Most in the technical community believe that you should have full control over the devices you own. This is a major factor in why so many technical people host their own servers and build a lot of the crazy things they do. As a result you'll hear a lot about rooting or getting superuser or root on various devices as well as Right to Repair.

Many in the tech community are on the heartbeat of issues surrounding copyright, fair use, and the Digital Millennium Copyright Act or DMCA as without exceptions, a lot of security research would not be legal and it's of direct importance to issues like software piracy and issues surrounding YouTube's automated ContentID [TODO: add links]

Moving on from that though, there is increasingly a concern about energy consumption and environmental consequences of technology use. Data centers alone are already consuming over 2% of the worlds electricity and that number is set to grow exponentially in the coming years. Because of this having a light, fast, http://motherfuckingwebsite.com/ instead of a bloated, JavaScript heavy page actually matters. http://gauthierroussilhe.com/en/posts/convert-low-tech as well as https://solar.lowtechmagazine.com/2016/05/how-to-go-off-grid-in-your-apartment.html are good sites that go more in depth on this issue. Now, at the same time, I'm not going to act all high and mighty, my desktop and monitors use in excess of 300w, but it is still something to be mindful of.

From https://wiki.xxiivv.com/#development:

The Four Essential Freedoms The freedom to run the program as you wish, for any purpose. The freedom to study how the program works, and change it. The freedom to redistribute copies so you can help others. The freedom to distribute copies of your modified versions to others.

The hacker and information freedom community has multiple 'sacred texts' if you will, which I think do a good job of outlining some of the ideologies of the communities. Probably the most famous is the Guerrilla Open Access Manifesto written by Aaron Swartz, an amazing man that, according to Wikipedia "was involved in the development of the web feed format RSS and the Markdown publishing format, the organization Creative Commons, and the website framework web.py, and was a co-founder of the social news site Reddit". Due to his extensive work in online politics his Wikipedia page almost acts like a hub of sorts for relevant information: https://en.wikipedia.org/wiki/Aaron_Swartz. The full text of the Guerrilla Open Access Manifesto is below:

Information is power. But like all power, there are those who want to keep it for themselves. The world's entire scientific and cultural heritage, published over centuries in books and journals, is increasingly being digitized and locked up by a handful of private corporations. Want to read the papers featuring the most famous results of the sciences? You'll need to send enormous amounts to publishers like Reed Elsevier.

There are those struggling to change this. The Open Access Movement has fought valiantly to ensure that scientists do not sign their copyrights away but instead ensure their work is published on the Internet, under terms that allow anyone to access it. But even under the best scenarios, their work will only apply to things published in the future. Everything up until now will have been lost.

That is too high a price to pay. Forcing academics to pay money to read the work of their colleagues? Scanning entire libraries but only allowing the folks at Google to read them? Providing scientific articles to those at elite universities in the First World, but not to children in the Global South? It's outrageous and unacceptable.

"I agree," many say, "but what can we do? The companies hold the copyrights, they make enormous amounts of money by charging for access, and it's perfectly legal — there's nothing we can do to stop them." But there is something we can, something that's already being done: we can fight back.

Those with access to these resources — students, librarians, scientists — you have been given a privilege. You get to feed at this banquet of knowledge while the rest of the world is locked out. But you need not — indeed, morally, you cannot — keep this privilege for yourselves. You have a duty to share it with the world. And you have: trading passwords with colleagues, filling download requests for friends.

Meanwhile, those who have been locked out are not standing idly by. You have been sneaking through holes and climbing over fences, liberating the information locked up by publishers and sharing them with your friends.

But all of this action goes on in the dark, hidden underground. It's called stealing or piracy, as if sharing a wealth of knowledge were the moral equivalent of plundering a ship and murdering its crew. But sharing isn't immoral — it's a moral imperative. Only those blinded by greed would refuse to let a friend make a copy.

Large corporations, of course, are blinded by greed. The laws under which they operate require it — their shareholders would revolt at anything less. And the politicians they have bought off back them, passing laws giving them the exclusive power to decide who can make copies.

There is no justice in following unjust laws. It's time to come into the light and, in the grand tradition of civil disobedience, declare our opposition to this private theft of public culture.

We need to take information, wherever it is stored, make our copies and share them with the world. We need to take stuff that's out of copyright and add it to the archive. We need to buy secret databases and put them on the Web. We need to download scientific journals and upload them to file sharing networks. We need to fight for Guerilla Open Access.

With enough of us, around the world, we'll not just send a strong message opposing the privatization of knowledge — we'll make it a thing of the past. Will you join us?

Aaron Swartz

July 2008, Eremo, Italy

If you'd like more information on Swartz's infulence you can watch a documentry on him here

Another important document is "The Conscience of a Hacker" written by "The Mentor" in '86

Another one got caught today, It's all over the papers. "Teenager Arrested in Computer Crime Scandal", "Hacker arrested after Bank Tampering"...

Damn kids. They're all alike.

But did you, in your three-piece psychology and 1950's technobrain, ever take a look behind the eyes of a hacker? did you ever wonder what made him tick, what forces shaped him, what may have molded him?

I am a hacker. Enter my world.

Mine is a world that begins with school... I'm smarter than most of the other kids, this crap they teach us bores me... Come on... Ain't Got All Day!! Damn underachiever. They're all alike.

I'm in junior high or high school. I've listened to the teachers explain for the fifteenth time how to reduce a fraction. I understand it. "No Ms. Smith, I didn't show my work. I did it in my head..."

Damn kid. Probably copied it. They're all alike.

I made a discovery today. I found a computer. Wait a xecond, this is cool. It does what I want it to. if it makes a mistake, it's because I screwed it up. Not Because it doesn't like me... Or feels threatend by me... Or thinks I'm a smart ass... Or doesn't like teaching and shouldn't be here...

Damn kid. All he does is play games. They're all alike.

And then it happened... a door opened to a world... rushing through the phone line like junk through an addict's veins, an electronic impulse is sent out, a refuge from the day-to-day incompetencies is sought... a board is found.

"this is it... this is wwhere I belong..."

I know everyone herre... even if I've never met them, never talked to them, may never hear from them again... I know you all...

Damn kid. tying up the phone line again. They're all alike... Come on... Ain't Got All Day!! You bet your ass we're all alike... we've been spoon-fed baby food at school when we hungered for steak... the bits of meat that you did let slip through were prechewed and tasteless. We've been dominated by sadist, or ignored by the apathetic. The few that had something to teach us found us willing pupils, but those few are like drops of water in the desert.

This is our world now... the world of the electron and the switch, the beauty of the baud. We make use of a service already existing without paying for what could be dirt-cheap if it wasn't run by profiteering gluttons, and you call us criminals. we explore... and you call us criminals. We seek after knoledge... and you call us criminals. We exist without skin color, without nationality, without religous bias... and you call us criminals. You build atomic bombs, you wage wars, you murder, cheat, and lie to us and try to make us believe it's for our own good, yet we're the criminals.

Yes, I am a criminal. My crime is that of curiosity. My crime is that of judging people by what they say and think, not what they look like. My crime is that of outsmarting you, something that you will never forgive me for.

Come on... Ain't Got All Day!!

I am a hacker, and this is my manifesto. You may stop this individual, but you can't stop us all... after all, we're all alike.

+++The Mentor+++ Racketeers

Finally, I'd like to make a few notes about online communities, trolling, hate speech, and the like. Clearly the tech industry leans significantly on the liberal/libertarian side; however, most of us also strongly support your right to say whatever you like even if we don't support it. This is particularly frustrating when it comes to large, non-grouped online communities like Twitter or Tumblr where except by blocking, everyone is in the same public sphere instead of isolated. While the isolation can have negative effects too, like echo chambers where false information and hate breed, the smaller communities are also beneficial as they allow for a better sense of community and for individual moderation policies decided by the users instead of awkward rules like Tumblr's NSFW ban and the chaos that ensued. Clearly the lines between hate speech and trolling and free speech are a problem online, and frankly the internet is young. We haven't really figured out the right way to handle it yet. Should Twitter have the right to remove the Alt-Right or are they to important of a political forum to deny freedom of speech despite being a public company? Is it ethically okay to use services like Tor for privacy when by doing so you're indirectly helping people get away with things like child ... abuse (I don't want this document getting flagged by something, ironically). Or because the tools are going to exist regardless and criminals will always find another way is it okay? The truth is, it's not black and white, and it's well worth your time to sit down and consider what you are personally okay with and what you think, as a society, we need to change and how we might go about doing that. Personally, I think services like Mastodon which offer security and privacy while keeping individual communities free to handle themselves are the best option, but they're also more complicated. Just know that decision you make online can have real world consequences, and that at the end of the day, there's a human on the other side of that screen.

Localization

https://shinesolutions.com/2018/01/08/falsehoods-programmers-believe-about-names-with-examples/ https://www.youtube.com/watch?v=-5wpm-gesOY https://www.youtube.com/watch?v=q9ZMub2UrKU&feature=youtu.be Names, Timezones, unicode, maps (Tiwan v china)

Religion

The engineering community is strangely divided, the 'old guard' is actually relatively conservative and professional, but as time has moved forward it's quite the opposite. Unsurprisingly, this correlates with religion as well. The main way this plays into politics is a general hard stance for the separation of church and state. This is in part due to a past of religiously motivated legislation negatively impacting copyright law, but also just generally an understood ideal that is beneficial to democracy. Furthermore, it would probably be worth your time to look into basics of most world religions, as engineering is increasingly a global field where you will have no choice but to work with people from diverse backgrounds across the globe.

An NSFW Note

The 'Hacking' community in particular is usually very clear on sexual liberation/freedoms and given that technically minded people tend to have statistically significantly higher amounts of LGBTQIA+ people, it's relevant to mention. I don't want to go in depth or be your source of sex education, but I do think skipping over this would be doing the community some injustice. As such I'd also like to link to some videos providing sexual education, The truth about unwanted arousal | Emily Nagoski , YouTube

TypeError:
no implicit conversion of Gender into Boolean


Finally, a little less NSFW, the Maker and engineering communities also tend to overlap rather heavily with more artistically minded and sub-culture heavy groups, ranging from those obsessed with comics to anime nerds or furries. I really recommend you do at least a little research into various sub cultures and geek culture to better understand some of the people you'll probably interact with. You might just find something new you enjoy while you're at it.

Also, because this got a bit heavy for a bit, let's touch on Rule 34. We all know it, but where does it come from? 4Chan of course. Here's the full set:

Thank you

If you've made it this far I just want to say thank you. We need more people to really consider the ethics of technology as we design it and proceed with it. DeepFakes, Automated driving, and even more mass online censorship are issues we're only going to face more with time and it's people like you who are going to help make sure we take the best path we can. So, from the bottom of my heart, thank you.

Political or social commentary ramblings from hackers solarpunks and engineers

Please Consider My Application to Give You Labor So I Can Stay Alive

The Great Asshole Fallacy

Ameyama's Values Update

How to Dropout

A Sick Giant

Metaphors We Believe By

TODO

Education, college, prices, highschool homework and personal time, Drugs,

Should I block ads?

[TODO]

Other Great Resources

https://news.ycombinator.com/

https://slashdot.org/

https://lobste.rs/

https://snapzu.com/

https://serializer.io/

https://stackoverflow.com/

http://textfiles.com/

https://www.alchemistowl.org/pocorgtfo/

https://n-o-d-e.news/

https://glitch.com/

https://media.ccc.de/

https://media.ccc.de/

Crash Course: Comptuer Science, from PBS

Learning Linux

https://linuxjourney.com

ElectroBoom

CNLohr

N-O-D-E

LiveOverflow

Tom Scott

bigclive

3Blue1Brown

Bryan Lunduke

Level1Techs

Podcasts

https://theamphour.com/

Github info pages

https://github.com/dwmkerr/hacker-laws

https://github.com/lorin/resilience-engineering

https://github.com/alex/what-happens-when

https://github.com/Awesome-Windows/Awesome

https://github.com/dwmkerr/hacker-laws

https://github.com/cirosantilli/x86-assembly-cheat

https://github.com/kozross/awesome-c

https://github.com/rby90/Project-Based-Tutorials-in-C

https://github.com/trimstray/the-book-of-secret-knowledge

https://github.com/terkelg/awesome-creative-coding

https://github.com/toplap/awesome-livecoding

https://github.com/sindresorhus/awesome

https://github.com/netspooky/Simple-Virtual-CPU

Blogs

http://blog.cleancoder.com/

DIY Pages

https://www.instructables.com/circuits/

Non-Technical

https://longform.org/ https://www.metafilter.com/ https://relevant.community/relevant/top

History

[TODO] Move this elsewhere

Other odd things:

// Potentially move these elsewhere

Polygot Files

elf hacking, POC||GTFO

Strange thought

Main not fn

order of variable declaration (paged out 001 pg 33)

generic midi use (paged out 002 pg 24)

rop