#Mac OS X
#!/bin/bash | |
# Paste at Pastebin.com using command line (browsers are slow, right?) | |
# coder : Anil Dewani | |
# date : Novemeber 7, 2010 | |
#help function | |
howto() | |
{ | |
echo "\ | |
Pastebin.com Bash Script \ |
CC0 1.0 Universal | |
Statement of Purpose | |
The laws of most jurisdictions throughout the world automatically confer | |
exclusive Copyright and Related Rights (defined below) upon the creator and | |
subsequent owner(s) (each and all, an "owner") of an original work of | |
authorship and/or a database (each, a "Work"). | |
Certain owners wish to permanently relinquish those rights to a Work for the |
# Read the contents of ~/.path into $PATH, if ~/.path exists. ~/.path should be a file | |
# consisting of one path on each line, such as: | |
# | |
# ~$ cat ~/.path | |
# # vim: ft=sh | |
# ~/usr/bin | |
# /opt/local/bin | |
# ... etc ... | |
# | |
# Note that comments begin with a hash (#). |
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
I wanted to be really able to explain to a fair amount of detail how does the program :command:`ls` actually work right from the moment you type the command name and hit ENTER. What goes on in user space and and in kernel space? This is my attempt and what I have learned so far on Linux (Fedora 19, 3.x kernel).
How does the shell find the location of 'ls' ?
After watching Bryan Cantrill's presentation on [Running Aground: Debugging Docker in Production][aground] I got all excited (and strangely nostalgic) about the possibility of core-dumping server-side Python apps whenever they go awry. This would theoretically allow me to fully inspect the state of the program at the point it exploded, rather than relying solely on the information of a stack trace.
Docker issues are frequently logged for DNS resolution in containers because it doens't inhert or get values for DNS from NetworkManager which leverages a built in dnsmasq to inteligently manage DNS.
sudo bash -c "echo listen-address=$(ip -4 addr show dev docker0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}') > /etc/NetworkManager/dnsmasq.d/docker-bridge"
sudo systemctl reload NetworkManager
sudo bash -c 'echo -e "{\n\t\"dns\": [\"$(ip -4 addr show dev docker0 | grep -oP "(?<=inet\s)\d+(\.\d+){3}")\"]\n}" > /etc/docker/daemon.json'
sudo systemctl restart docker