See: microsoft/vscode#229 (comment)
Import Microsoft's repository key:
$ cd /tmp
$ curl -fsSLO https://packages.microsoft.com/keys/microsoft.asc
$ sudo rpm --import microsoft.asc
See: microsoft/vscode#229 (comment)
Import Microsoft's repository key:
$ cd /tmp
$ curl -fsSLO https://packages.microsoft.com/keys/microsoft.asc
$ sudo rpm --import microsoft.asc
On systems with UEFI Secure Boot enabled, recent Linux kernels will only load signed modules, so it's about time DKMS grew the capability to sign modules it's building.
These scripts are extended and scriptified variants of https://computerlinguist.org/make-dkms-sign-kernel-modules-for-secure-boot-on-ubuntu-1604.html and https://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur/768310#768310 and add some error checking, a passphrase around your signing key, and support for compressed modules.
dkms-sign-module
is a wrapper for the more generic sign-modules
which can also be used outside of DKMS.
/root
, say /root/module-signing
, put the three scripts below in there and make them executable: chmod u+x one-time-setup sign-modules dkms-sign-module
#include <stdio.h> | |
#include <stdlib.h> | |
#include <stdint.h> | |
#ifdef _MSC_VER | |
#include <intrin.h> /* for rdtscp and clflush */ | |
#pragma optimize("gt",on) | |
#else | |
#include <x86intrin.h> /* for rdtscp and clflush */ | |
#endif |
This is not an exhaustive list of all interfaces in Go's standard library.
I only list those I think are important.
Interfaces defined in frequently used packages (like io
, fmt
) are included.
Interfaces that have significant importance are also included.
All of the following information is based on go version go1.8.3 darwin/amd64
.
# https://github.com/thibauts/node-castv2-client | |
# https://github.com/thibauts/node-castv2 | |
sudo apt-get install xserver-xorg-core | |
sudo apt-get install xvfb | |
sudo apt-get install scrot | |
sudo apt-get install libav-tools | |
# https://weblog.lkiesow.de/20160215-raspberry-pi-screen-mirroring/ | |
avconv -f x11grab -s 1024x768 -i :0.0 -c:v mpeg4 -f mpegts udp://192.168.0.8:8888 |
This is not intended to be comprehensive or authoritative, just free online resources I've found valuable while learning more about Erlang.
# abort if already under tmux | |
[[ -n $TMUX_PANE ]] && return | |
# zsh-specific includes | |
zmodload -i zsh/datetime | |
zmodload -i zsh/stat | |
# place to store the chart | |
RAINBARF_OUT=~/.rainbarf.out | |
# update period, in seconds |
HTTP is a stateless protocol. Sessions allow us to chain multiple requests together into a conversation between client and server.
Sessions should be an option of last resort. If there's no where else that the data can possibly go to achieve the desired functionality, only then should it be stored in the session. Sessions can be vulnerable to security threats from third parties, malicious users, and can cause scaling problems.
That doesn't mean we can't use sessions, but we should only use them where necessary.