Shubham K. Sawant shubhamksawant

Content

Basics
Disk and File System Management
- General Disk Manipulation (non-LVM)
LVM

2019 update: this essay has been updated on my personal site, together with a followup on how to get started

2020 update: I'm now writing a book with updated versions of all these essays and 35 other chapters!!!!

1. Learn in public

If there's a golden rule, it's this one, so I put it first. All the other rules are more or less elaborations of this rule #1.

You already know that you will never be done learning. But most people "learn in private", and lurk. They consume content without creating any themselves. Again, that's fine, but we're here to talk about being in the top quintile. What you do here is to have a habit of creating learning exhaust. Write blogs and tutorials and cheatsheets. Speak at meetups and conferences. Ask and answer things on Stackoverflow or Reddit. (Avoid the walled gardens like Slack and Discourse, they're not public). Make Youtube videos

terminal tips && tricks

ctrl + L            - clean terminal  
ctrl + R            - search in bash history  
alt + .             - list of command arguments

basic commands

pwd - acutal workspace path

Typing vagrant from the command line will display a list of all available commands.

Be sure that you are in the same directory as the Vagrantfile when running these commands!

Creating a VM

vagrant init -- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.
vagrant init <boxpath> -- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example, vagrant init ubuntu/trusty64.

Starting a VM

vagrant up -- starts vagrant environment (also provisions only on the FIRST vagrant up)

#Linux Cheat Sheet

##File Commands:

ls – directory listing
ls -al – formatted listing with hidden files
cd dir - change directory to dir
cd – change to home
pwd – show current directory
mkdir dir – create a directory dir
rm file – delete file

	# This file is: ~/.ssh/config

	# You may have other (non-CodeCommit) SSH credentials stored in this
	# config file – in addition to the CodeCommit settings shown below.

	# NOTE: Make sure to run [ chmod 600 ~/.ssh/config ] after creating this file!

	# Credentials for Account1
	Host awscc-account1 # 'awscc-account1' is a name you pick
	Hostname git-codecommit.us-east-1.amazonaws.com # This points to CodeCommit in the 'US East' region