I hereby claim:
- I am blancnoir on github.
- I am blancnoir (https://keybase.io/blancnoir) on keybase.
- I have a public key ASCGyv1ANpd9bAKdVyA1Qc_dasckugHX-4NUbff5Gra2Gwo
To claim this, I am signing this object:
function fish_prompt | |
# $status gets nuked as soon as something else is run, e.g. set_color | |
# so it has to be saved asap. | |
set -l last_status $status | |
# c0 to c4 progress from dark to bright | |
# ce is the error colour | |
set -g c0 (set_color 005284) | |
set -g c1 (set_color 0075cd) | |
set -g c2 (set_color 009eff) |
I hereby claim:
To claim this, I am signing this object:
" ========================================================== | |
" Vundle | |
" ========================================================== | |
set nocompatible | |
filetype off | |
set rtp+=~/.vim/bundle/vundle/ | |
call vundle#rc() | |
" let Vundle manage Vundle |
# | |
# Given the ID of an Amazon public AMI in one region, figure out what the | |
# equivalent AMI IDs are for that same AMI in all other regions known. | |
# If that AMI isn't defined in a region, it prints the region's name, but | |
# comments it out. | |
# | |
from __future__ import print_function | |
import boto3 |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
# Resources | |
https://wiki.archlinux.org/index.php/installation_guide | |
https://wiki.archlinux.org/index.php/Dell_XPS_13_(9360) | |
http://www.rodsbooks.com/gdisk/cgdisk-walkthrough.html | |
# TO-DO | |
# Set up periodic TRIM for SSD | |
# 1 Pre-installation |
#!/bin/bash | |
# Cisco Anyconnect CSD wrapper for OpenConnect | |
# Enter your vpn host here | |
CSD_HOSTNAME= | |
if [[ -z ${CSD_HOSTNAME} ]] | |
then | |
echo "Define CSD_HOSTNAME with vpn-host in script text. Exiting." | |
exit 1 | |
fi |
This guide provides instructions for an Arch Linux installation featuring full-disk encryption via LVM on LUKS and an encrypted boot partition (GRUB) for UEFI systems.
Following the main installation are further instructions to harden against Evil Maid attacks via UEFI Secure Boot custom key enrollment and self-signed kernel and bootloader.
You will find most of this information pulled from the Arch Wiki and other resources linked thereof.
Note: The system was installed on an NVMe SSD, substitute /dev/nvme0nX
with /dev/sdX
or your device as needed.