Debian 8 のカーネルをアップグレードする方法です。
- Microsoft Windows Server 2012 R2
- Hyper-V
- Debian 8.2 jessie
| #!/bin/bash | |
| # from http://habrahabr.ru/post/108240/ | |
| ncpus=`grep -ciw ^processor /proc/cpuinfo` | |
| test "$ncpus" -gt 1 || exit 1 | |
| n=0 | |
| for irq in `cat /proc/interrupts | grep eth | awk '{print $1}' | sed s/\://g` | |
| do | |
| f="/proc/irq/$irq/smp_affinity" |
Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.
This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.
There is a companion feature matrix of various tools. Comments are welcome in the same manner.
www.iuqerfsodp9ifjaposdfjhgosurijfaewrwergwea.com is up the virus exits instead of infecting the host. (source: malwarebytes). This domain has been sinkholed, stopping the spread of the worm. Will not work if proxied (source).update: A minor variant of the viru
| #!/bin/bash | |
| # parse command line options | |
| while [[ $# -gt 1 ]] | |
| do | |
| key="$1" | |
| case $key in | |
| -u|--url) | |
| target_url="$2" |
This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.
While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.
Concurrency is a domain I have wanted to explore for a long time because the locks and the race conditions have always intimidated me. I recall somebody suggesting concurrency patterns in golang because they said "you share the data and not the variables".
Amused by that, I searched for "concurrency in golang" and bumped into this awesome slide by Rob Pike: https://talks.golang.org/2012/waza.slide#1 which does a great job of explaining channels, concurrency patterns and a mini-architecture of load-balancer (also explains the above one-liner).
Let's dig in:
2018-03-18: Updating of this guide is taking a backseat to the mainnet version at
This guide is specific to btcd, lnd, on testnet, running on an ubuntu 16.04 server host.
It does not address mainnet, or using bitcoind, or neutrino.
Original installation guide is here:
| # -*- mode: ruby -*- | |
| # vi: set ft=ruby : | |
| K8S_DEV_BOX_NAME = "gsengun/k8s-dev-box" | |
| K8S_DEV_BOX_VERSION = "17.12.27" | |
| MASTER_NODE_IP_START="172.27.44.20" | |
| WORKER_NODE_IP_START="172.27.44.10" | |
| JOIN_TOKEN="abcdef.1234567890123456" |
this is a rough draft and may be updated with more examples
GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?
Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to