I'm trying to follow this guide to install NixOS
using Btrfs, LUKS and LVM. The main usage of this page for me will be remembering what I did! My laptop is ASUS ROG GL553VD.
Just downloaded Plasma Desktop, 64bit and create a bootable Flash Drive. Then boot up to NixOS Live CD. Using gparted to create two partitions, One 200MB vfat EFI partittion and the rest of SSD drive will be an encrypted partition.
DISK=/dev/nvme0n1
Notes of the key points copied/summarised from Dave Cheney's Practical Go for more concise reading/reference.
It's worth reading the original document as there is more exposition there of the ideas presented.
These are terse notes only; I'm not providing my own commentary, opinion
| Some Jenkinsfile examples |
This is an index of leetcode problems that I find interesting.
You can see many theoretical solutions by hqztrue here.
Likely only people who work in the area knows the current best solution. The best solution is either in some paper, or requires advanced tricks.
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.
| # based on the "patch deployment" strategy in this comment: | |
| # https://github.com/kubernetes/kubernetes/issues/13488#issuecomment-372532659 | |
| # requires jq | |
| # $1 is a valid namespace | |
| function refresh-all-pods() { | |
| echo | |
| DEPLOYMENT_LIST=$(kubectl -n $1 get deployment -o json|jq -r .items[].metadata.name) | |
| echo "Refreshing pods in all Deployments" | |
| for deployment_name in $DEPLOYMENT_LIST ; do |
I'm putting here some of the things Sandro said in his 3-part session on Outside-In TDD (see the github repo here), and highlights some parts that are significant to me.
TDD does not lead to a good design if you don't know what a good design looks like.
The way I code in this video is the way I normally code but not the way I normally teach.
Some of you will notice that I skip the traditional refactoring steps a few times and I do quite a lot of design up-front (or "just in time design" as I prefer to call it) without much feedback from my code.
| go list -f '{{join .Deps "\n"}}' ./... | xargs go list -f '{{if not .Standard}}{{.ImportPath}}{{end}}' | xargs go install -a |
| #!/bin/bash | |
| # bash generate random alphanumeric string | |
| # | |
| # bash generate random 32 character alphanumeric string (upper and lowercase) and | |
| NEW_UUID=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) | |
| # bash generate random 32 character alphanumeric string (lowercase only) | |
| cat /dev/urandom | tr -dc 'a-z0-9' | fold -w 32 | head -n 1 |
