start new:
tmux
start new with session name:
tmux new -s myname
# Initialize the scroll | |
page = es.search( | |
index = 'yourIndex', | |
doc_type = 'yourType', | |
scroll = '2m', | |
search_type = 'scan', | |
size = 1000, | |
body = { | |
# Your query's body | |
}) |
#!/bin/sh | |
echo $((`cat /sys/class/thermal/thermal_zone0/temp` / 1000)) |
a4b.amazonaws.com | |
access-analyzer.amazonaws.com | |
account.amazonaws.com | |
acm-pca.amazonaws.com | |
acm.amazonaws.com | |
airflow-env.amazonaws.com | |
airflow.amazonaws.com | |
alexa-appkit.amazon.com | |
alexa-connectedhome.amazon.com | |
amazonmq.amazonaws.com |
#!/usr/bin/python | |
import Crypto.Hash | |
import Crypto.Hash.HMAC | |
import Crypto.Hash.SHA512 | |
import Crypto.Random | |
import Crypto.Cipher | |
import base64 | |
import collections | |
import hashlib |
curl -s https://gist.githubusercontent.com/wongcyrus/a4e726b961260395efa7811cab0b4516/raw/6a045f51acb2338bb2149024a28621db2abfcaab/resize.sh | bash /dev/stdin 60 |
There is current no support for the NanoPi R2S in ArchLinuxArm, but it's possible to run it using the generic aarch64 installation.
dd
(sectors 32 to 32767) everything before the partition, except the partition table)./dev/mmcblk0p1
at offset of 32768 sectors (16384 KiB):Device Boot Start End Sectors Size Id Type
This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.
Let’s begin.
First of all, there are some concepts that one must unlearn from ipv4:
Concept 1