This gist shows a quick overview of calling Rust in a Swift project, with Swift Package Manager configured.
Let's go ahead and create a folder containing all our sources:
mkdir swift-rs && cd $_
#!/usr/bin/env bash | |
set -o errexit | |
MUSL_VERSION=1.2.5 | |
LIBEVENT_VERSION=2.1.12 | |
NCURSES_VERSION=6.5 | |
TMUX_VERSION=3.5a | |
TARGETDIR=$1 |
Instructions on how to install the CMake tool on macOS.
First step should be to unsinstall any previous CMake installation. This step can be skipped if no CMake version was previously installed.
To uninstall any previous CMake installations use the following commands:
" ~/.vim/after/syntax/python.vim or ~/.config/nvim/after/syntax/python.vim | |
syn match pythonEscape +{{+ contained containedin=pythonfString,pythonfDocstring | |
syn match pythonEscape +}}+ contained containedin=pythonfString,pythonfDocstring | |
syn region pythonfString matchgroup=pythonQuotes | |
\ start=+[fF]\@1<=\z(['"]\)+ end="\z1" | |
\ contains=@Spell,pythonEscape,pythonInterpolation | |
syn region pythonfDocstring matchgroup=pythonQuotes | |
\ start=+[fF]\@1<=\z('''\|"""\)+ end="\z1" keepend | |
\ contains=@Spell,pythonEscape,pythonSpaceError,pythonInterpolation,pythonDoctest |
Note - this article assumes you have reasonable familiarity with systemd
, networkd
and nspawn/machinectl
There seem to be a lot of references on the internet for nspawn networking with a bridge - but not on simply using the stock veth
networking with static addresses. The default behaviour of nspawn
(as of 24/03/20 and systemd:245
on Arch) is to:
/lib/systemd/network/80-container-ve.network
)/lib/systemd/network/80-container-host0.network
)AddOn:
chrome/userChrome.css
in your profile directory: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.
# Instructions for installing Pi-hole 4.2 on UniFi CloudKey Gen 1 (UC-CK) running firmware 0.13.6 | |
# Pi-hole will need to be completely re-installed after every FW update or if CloudKey is reset to defaults. | |
# Verify UC-CK is running firmware v0.13.6 (or later) before installing Pi-hole. If not, do: | |
ubnt-systool fwupdate https://dl.ubnt.com/unifi/stage/cloudkey/firmware/UCK/UCK.mtk7623.v0.13.6.7ad551e.190225.0939.bin | |
# UC-CK firmware v0.13.6 downgrades UniFi Controller to 5.10.17. Upgrade to 5.10.19 with: | |
cd /tmp | |
wget https://dl.ubnt.com/unifi/5.10.19/unifi_sysvinit_all.deb | |
dpkg -i unifi_sysvinit_all.deb |
[ | |
{ | |
"ProviderGUID": "72d164bf-fd64-4b2b-87a0-62dbcec9ae2a", | |
"ProviderName": "AccEventTool", | |
"ProviderGroupGUID": "4f50731a-89cf-4782-b3e0-dce8c90476ba", | |
"AssociatedFilenames": [ | |
"accevent.exe", | |
"inspect.exe", | |
"narrator.exe", | |
"srh.dll" |