| #!/usr/bin/env sh | |
| # | |
| # CONFIG | |
| # ====== | |
| # | |
| # ONT_IF Interface connected to the ONT | |
| # | |
| # RG_ETHER_ADDR MAC address of your assigned Residential Gateway | |
| # | |
| # EAP_SUPPLICANT_IDENTITY Required only with supplicant mode. MAC address associated |
| #!/usr/bin/env python | |
| r""" | |
| This script can be used to fix the "exec format error" seen with tools like gzip in | |
| WSL with Ubuntu 22.04 in Q1/Q2 2022 | |
| A hacky fix for broken executables in WSL/Ubuntu 22.0 | |
| see https://github.com/microsoft/WSL/issues/8219 | |
a quick converter to convert Xresources format color definitions (from terminal.sexy) to Kitty's color configuration format.
usage:
./xres_to_kitty.py < xres_colors.txt >> ~/.config/kitty/kitty.conf
ideally, you would clear the existing previously generated colors from the kitty conf file before running.
| --- | |
| source: https://www.google.com/maps/d/viewer?mid=1Z1dI8hoBZSJNWFx2xr_MMxSxSxY&&ll=54.784654126394415%2C-8.91870626273581&z=3 | |
| last_update: Jul 23, 2019 | |
| contribute: http://bit.ly/2d13csJ | |
| ios: http://apple.co/2b7BatI | |
| android: http://bit.ly/2dDeaaN | |
| how_to_update: 1. open the source in a browser | |
| 2. open browser console and type in `_pageData` to print the content of the variable | |
| 3. copy-paste all the content in a file | |
| 4. keep interesting lines with: `grep -e "name" -e "description" > new_file` |
| ### | |
| # https://gcits.com/knowledge-base/check-it-glue-passwords-against-have-i-been-pwned-breaches/ | |
| ### | |
| [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 | |
| $key = "ENTERAPIKEYHERE" | |
| $ITGbaseURI = "https://api.itglue.com" | |
| $headers = @{ |
The initial goal of this project is to use the raspberry pi in place of my Wireless Range Extender and then going from 3 wireless networks (2.4ghz, 2.4ghz extended, 5ghz) at home to only one (5ghz). This way I'm reducing the exposition to radio waves for the whole familly at home.
Ok, enough drama for now, let's go technical. 😁
DNS queries on home network suddenly resolving hosts to 104.239.207.44.
You will see SPORADIC mis-resolutions of EVERYTHING to that 104.239.207.44 address if their crappy router happens to hear your PC's DHCP request - EVEN IF ANOTHER DHCP SERVER ON THE NETWORK assigns the ultimate address.
https://www.reddit.com/r/JDM_WAAAT/comments/8zgkfj/server_build_nas_killer_v_20_the_terminator_dual/ 2x X5650 from this thread Aside from that build guide, a generic USB3 card and an AMD R9-200
Modify /etc/default/grub and add vfio-pci.ids=dead:beef video=efifb:off to GRUB_CMDLINE_LINUX_DEFAULT (use the PCI vid/pid of your primary GPU, not dead:beef)
I owe my very rapid learning journey in the world of ConfigFs to several key sources which aren't necessarily relevant to this result, but I feel deserve a mention anyway.
