git clone https://github.com/distribution/distribution.git
cd distribution
go run cmd/registry/main.go serve config.yml
| [Interface] | |
| Address = <...> | |
| MTU = 1412 | |
| PrivateKey = <...> | |
| DNS = <...> | |
| PostUp = iptables -t nat -A POSTROUTING -o %i -j MASQUERADE; iptables -A FORWARD -i %i -m state --state RELATED,ESTABLISHED -j ACCEPT; iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu | |
| PostDown = iptables -t nat -D POSTROUTING -o %i -j MASQUERADE; iptables -D FORWARD -i %i -m state --state RELATED,ESTABLISHED -j ACCEPT; iptables -D FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu | |
| [Peer] |
This is the second article in a series of articles around Rusts new async/await
feature. The first article about interfaces can be found
here.
In this part of the series we want to a look at a mechanism which behaves very
different in Rust than in all other languages which feature async/await
support. This mechanism is Cancellation.
| #!/bin/sh | |
| # The script configures simultaneous AP and Managed Mode Wifi on Raspberry Pi Zero W (should also work on Raspberry Pi 3) | |
| # Usage: curl https://gist.githubusercontent.com/lukicdarkoo/6b92d182d37d0a10400060d8344f86e4/raw | sh -s WifiSSID WifiPass APSSID APPass | |
| # Licence: GPLv3 | |
| # Author: Darko Lukic <[email protected]> | |
| # Special thanks to: https://albeec13.github.io/2017/09/26/raspberry-pi-zero-w-simultaneous-ap-and-managed-mode-wifi/ | |
| MAC_ADDRESS="$(cat /sys/class/net/wlan0/address)" | |
| CLIENT_SSID="${1}" | |
| CLIENT_PASSPHRASE="${2}" |
| Enable DCI debugging on Gigabyte-BKi5HA-7200 | |
| -------------------------------------------- | |
| The Gigabyte-BKi5HA-7200 (Kabylake i5-7200 processor) can be debugged with only a USB debug cable, a | |
| special cable that crosses only the data signals and has the power signals | |
| removed. You can buy these cables at i.e. https://www.datapro.net/products/usb-3-0-super-speed-a-a-debugging-cable.html | |
| The hurdle you have to overcome before you can access DCI however is that you | |
| need to set some bits in hardware that first enable DCI and also enable the debug port so that DCI can control the cores. | |
| There are lots of guides in howto patch the BIOS but only these two really describes all the steps using only freely accessible tools: |
cloud-init is absolute cancer. Its code is horrible. It has no documentation at all.
It took me 5 fucking hours to figure out how to properly configure networking on recent
cloud-init (Ubuntu 16.04 cloud image) with local datasource.
It's not mentioned anywhere you need to provide dsmode: local. (but only if you need network-config,
besides that everything is fine; someone below noted that -m flag does the same thing, good to know) Of course nobody needs documentation for network-config format
either. (cloudinit/net/__init__.py is a protip, enjoy the feces dive)
Oh, and by the way - no, it's not possible to provide network-config to uvt-kvm without patching shit.
Instructions how to install Debian using debootstrap. Below instructions were verified to work with debootstrapping Debian 11.
| George Carlin INVOICE | |
| [email protected] | |
| To: Invoice #6 | |
| Stephen Hawking Date: May 13, 2014 | |
| [email protected] | |
| +-----------------------------------------------------------------+ | |
| | Quantity | Description | Unit Price | Total | |