TIL: github publishes your public keys for you
today i learned, github publishes everyone’s public keys at https://github.com/username.keys. handy for bootstrapping a machine. mine
today i learned, github publishes everyone’s public keys at https://github.com/username.keys. handy for bootstrapping a machine. mine
overview to build a virtualized network topology from the most base elements it’s as simple as starting a virtual machine with the necessary number of virtualized interfaces and interconnecting these virtual interfaces to other virtual machines or physical interfaces. while there are tools1 which will nicely automate the creation of topologies and handle the lifecycle of VMs. all of these are effectively placing a nice wrapper around the following process....
this bloomberg article re: microsoft under nadella is totally worth the read. it’s really difficult to recognize the microsoft from the ballmer era vs. what we see today. the products and the stuff coming out of microsoft is actualy pretty exciting. their hardware is decent, their cloud presence and developer support (hello, github.) is first rate and they’re consistently chipping away at AWS in the cloud space. 20 years ago, if you would have told me that they’d be sticking a linux layer into their OS and you’d have something approximating a useful unix userspace environment in your PC, i would have thought you were quite high....
you can have multiple pythons enabled at the same time so that those applications which you run which make assumptions about python2 being available work. (i’m looking at you gsutil and gcloud) elmo(~)% pyenv global 3.7.1 2.7.15 elmo(~)% pyenv versions system * 2.7.15 (set by /Users/sulrich/.pyenv/version) 2.7.15/envs/foo 2.7.5 * 3.7.1 (set by /Users/sulrich/.pyenv/version) 3.7.2 foo elmo(~)% which python2 /Users/sulrich/.pyenv/shims/python2 elmo(~)% which python3 /Users/sulrich/.pyenv/shims/python3 elmo(~)% which python /Users/sulrich/.pyenv/shims/python elmo(~)% python --version Python 3....
because i have to google these sysctl settings every … time.. /etc/sysctl.conf # disable IPv6 on the wlan0 interface net.ipv6.conf.wlan0.disable_ipv6=1 # insufficient on its lonesome net.ipv6.conf.wlan0.autoconf=0 # don't forget this .. it’s important to disable autoconf because it will still pick up the RAs for learning the default and this may not deterministically let you do what you want. replace wlan0 with the interface you want to starve.