echo r"0xX4H" | rev mbledkowski

Requirements

Download NixOS minimal iso and copy to USB stick. For example on Mac OSX

$ diskutil list
$ diskutil unmountDisk /dev/disk1 # Make sure you got right device

jq — https://jqlang.github.io/jq/ — "like sed for JSON data"

There are several options available for installing jq. I prefer to use Homebrew: brew install jq

Created 17 Aug 2018

This is a simple installation that I did on my Raspberry Pi. Of course, this is only one of the many reasons to do it.

Here are my requirements:

For getting rid of the horizontal tab bar to save vertical space and reduce confusion, edit userChrome.css to add this:

/* Hide tab bar in FF Quantum */
@-moz-document url("chrome://browser/content/browser.xul") {

Search for the following keywords in "advanced settings" and disable (uncheck) the options which appear.

premium alert
oboom
Special Deals
Donate
Banner

	Difference between spawn and exec functions of child_process

	The Node.js Child Processes module (child_process) has two functions spawn and exec, using which we can start a child process to execute other programs on the system. Those new to child_process may wonder why there are two functions to do the same thing, and which one they should use. I'll explain the differences between spawn and exec to help you decide when to use what.

	The most significant difference between child_process.spawn and child_process.exec is in what they return - spawn returns a stream and exec returns a buffer.

	child_process.spawn returns an object with stdout and stderr streams. You can tap on the stdout stream to read data that the child process sends back to Node. stdout being a stream has the "data", "end", and other events that streams have. spawn is best used to when you want the child process to return a large amount of data to Node - image processing, reading binary data etc.

	child_process.spawn is "asynchronously asynchr

	#You probably want to do this in root to reduce the amount of sudos required
	su -

	#Install iptables if you haven't already
	#Alternatively use packet manager of your choice
	apt-get install iptables

	#Allow all incoming traffic to begin with
	iptables -P INPUT ACCEPT
	#Clean out any existing input rules. You may also remove the "INPUT" argument and run only "iptables -F" to clear all chains. When doing so, make sure there are no rules in other chains that you still need (list via "iptables -L"), for example Oracle cloud servers will have preset rules, which should not be removed.

	----------POSSIBLE OPTIONS----------------------------------------------
	--account : [optional] account name to login with
	--key : [optional] connection key for the server (defaults to 1 in debug)
	--automationRoutine : [optional] automation routine to run after login
	--startAutomationGraph : [optional] start up and execute automation global graph using provided guid
	--gatherEffectStats : [optional] enables effect stat gathering
	--noautoconnect : [optional] Do not automatically connect to a server
	--fastQuit
	--dumpAssetNames : Write to <file> a JSON map of GUID (String "0xabc...") to asset name for all soft assets
	--startPosition : [optional] start position when joining a map

	# Default config for sway
	#
	# Copy this to ~/.config/sway/config and edit it to your liking.
	#
	# Read `man 5 sway` for a complete reference.

	### Variables
	#
	# Logo key. Use Mod1 for Alt.
	set $mod Mod4

	More recent resolution:

	1. cd ~/../../etc (go to etc folder in WSL).
	2. echo "[network]" \| sudo tee wsl.conf (Create wsl.conf file and add the first line).
	3. echo "generateResolvConf = false" \| sudo tee -a wsl.conf (Append wsl.conf the next line).
	4. wsl --terminate Debian (Terminate WSL in Windows cmd, in case is Ubuntu not Debian).
	5. cd ~/../../etc (go to etc folder in WSL).
	6. sudo rm -Rf resolv.conf (Delete the resolv.conf file).
	7. In windows cmd, ps or terminal with the vpn connected do: Get-NetIPInterface or ipconfig /all for get the dns primary and
	secondary.