cryptsetup open --type plain -d /dev/urandom /dev/nvme0n1 to-be-wiped
dd if=/dev/zero of=/dev/mapper/to-be-wiped bs=1M status=progress
cryptsetup close to-be-wiped
wipefs -a /dev/nvme0n1
;;; Startup | |
;;; PACKAGE LIST | |
(setq package-archives | |
'(("melpa" . "https://melpa.org/packages/") | |
("elpa" . "https://elpa.gnu.org/packages/"))) | |
;;; BOOTSTRAP USE-PACKAGE | |
(package-initialize) | |
(setq use-package-always-ensure t) | |
(unless (package-installed-p 'use-package) |
#!/usr/bin/env bash | |
# NixOS-only cargo wrapper that: | |
# - always uses mold for linking. | |
# - sets `-C target-cpu=haswell` to avoid generating code for pre-2013 CPUs. | |
# - sets `-C link-arg=-Wl,--compress-debug-sections=zlib-gabi` to compress debug sections. | |
# - sets LIBCLANG_PATH for projects that need clang. | |
# - sets `-Z share-generics` to reduce output binary sizes by ~2MB. | |
# - turns on cargo's sparse-registry feature. | |
# - increases niceness slightly with `nice -n 2` . |
- Original Author: @altercation (And an evolved Arch Wiki version of this, here)
- Contributing Author: @craSH
These are working notes on the installation of Arch Linux. I've just completed this install on a notebook (@altercation: Lenovo P50. @craSH: Dell XPS 13" 9380) but the setup should work for most laptop/desktop configurations.
Some assumptions/notes:
- This isn't a dual boot configuration. I can see some of the appeal and still work in Adobe from time to time, but given the increasing complexity of EFI and the way Windows/MS manhandles the EFI partition during upgrades, I really would recommend steering clear of dual boot. Just my two cents here.
#!/bin/bash | |
# 0 - SSH | |
# This isn't necessary but if you ssh into the computer all the other steps are copy and paste | |
# Set a password for root | |
passwd | |
# Get network access | |
iwctl | |
""" |
This is a collection of the tweaks and modification I've made to my Arch Linux installation over the months. These may be applicable to other distros, but please check first before doing anything. I also included Arch Wiki references for all the procedures I mentioned. My recommendation is not to blindly follow this gist but to always check with the Arch Linux wiki first. Things move fast and by the time you're reading this my gist may be out of date. Lastly, the golden rule: never execute a command you don't understand.
My current DE of choice is KDE's Plasma. I find it just about perfect.
There are various ways to install it on Arch. The most popular one is to install plasma
and plasma-applications
, but I don't like doing that because it comes with too many programs I'll never use. I, instead, install the base plasma
group, remove the few extra packages that come with it, then I finish off by installing a few KDE apps that don't come with th
With the addition of ES modules, there's now no fewer than 24 ways to load your JS code: (inline|not inline) x (defer|no defer) x (async|no async) x (type=text/javascript | type=module | nomodule) -- and each of them is subtly different.
This document is a comparison of various ways the <script>
tags in HTML are processed depending on the attributes set.
If you ever wondered when to use inline <script async type="module">
and when <script nomodule defer src="...">
, you're in the good place!
Note that this article is about <script>
s inserted in the HTML; the behavior of <script>
s inserted at runtime is slightly different - see Deep dive into the murky waters of script loading by Jake Archibald (2013)
Ninj0r admin, [Oct 20, 2017, 9:18:55 AM]: | |
It's a three step process: | |
1) Start listening to the stream and buffering the messages | |
2) Get a depth snapshot | |
3) replay the buffered messages and the live messges. | |
Depth updates have two variables, u and U | |
U is the initial updateId, and u is the final updateId. There can be multiple updates "compressed" into a single update that comes out via the web socket stream. |