| %!TEX TS-program = xelatex | |
| \documentclass[12pt]{scrartcl} | |
| % The declaration of the document class: | |
| % The second line here, i.e. | |
| % \documentclass[12pt]{scrartcl} | |
| % is a standard LaTeX document class declaration: | |
| % we say what kind of document we are making in curly brackets, | |
| % and specify any options in square brackets. |
| local string = string | |
| --local print = print | |
| local tostring = tostring | |
| local io = io | |
| local table = table | |
| local pairs = pairs | |
| local capi = { | |
| mouse = mouse, | |
| screen = screen | |
| } |
| #include <assert.h> | |
| #include <stdint.h> | |
| #include <stdio.h> | |
| #include <string.h> | |
| #include <windows.h> // 各种位图数据结构 | |
| class Converter | |
| { | |
| public: | |
| Converter() : pixels_(NULL), width_(0), height_(0) {} |
| /* | |
| * I add this to html files generated with pandoc. | |
| */ | |
| html { | |
| font-size: 100%; | |
| overflow-y: scroll; | |
| -webkit-text-size-adjust: 100%; | |
| -ms-text-size-adjust: 100%; | |
| } |
| #include <algorithm> | |
| #include <iostream> | |
| #include <map> | |
| #include <unordered_map> | |
| // MapTraits<MapType, KeyType1, KeyType2, KeyType3...> | |
| // --------------------------------------------------- | |
| // 连续使用 KeyType1, KeyType2, KeyType3... 对 MapType 进行取 Value 操作后的信息 | |
| template <typename MapType, typename KeyType, typename... KeyTypes> |
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' ?
| #include <array> | |
| #include <iostream> | |
| #include <stdexcept> | |
| #include <string> | |
| #include <cstdint> | |
| /// An UTF-8 encoded character. | |
| class utf8_char { | |
| private: |
When hosting our web applications, we often have one public IP
address (i.e., an IP address visible to the outside world)
using which we want to host multiple web apps. For example, one
may wants to host three different web apps respectively for
example1.com, example2.com, and example1.com/images on
the same machine using a single IP address.
How can we do that? Well, the good news is Internet browsers
This is an opinionated guide to learning about computer security (independently of a university or training program), starting with the absolute basics (suitable for someone without any exposure to or knowledge of computer security) and moving into progressively more difficult subject matter.
It seems that most people don't realize how much information is actually available on the internet. People love to share (especially geeks) and everything you need to become well versed in computer security is already available to you (and mostly for free). However, sometimes knowing where to start is the hardest part - which is the problem that this guide is intended to address. Therefore, this guide can accuratley be described as a 'guide to guides', with additional recommendations on effective learning and execises, based on my own experiences.
Many of the free resources are the best resources and this guide focuses on them. It is intended to provided a comprehensive
| # In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env | |
| # variable pointing GPG to the gpg-agent socket. This little script, which must be sourced | |
| # in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start | |
| # gpg-agent or set up the GPG_AGENT_INFO variable if it's already running. | |
| # Add the following to your shell init to set up gpg-agent automatically for every shell | |
| if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then | |
| source ~/.gnupg/.gpg-agent-info | |
| export GPG_AGENT_INFO | |
| else |
