I found some mystery visitors in nginx’s access log. I tried to figure out the location of those visitors and what they did. IP collection First copy nginx’s access log to a folder and save all logs into a single file. $ mkdir mysteryIPs && cd $_ $ sudo cp /var/log/nginx/access.log.* . $ zcat access.log.* > access-gz.log $ cat access.log.1 >> access-gz.log $ cat access.log >> access-gz.log Remove LAN accesses from log file, for example my subnet IP rang is 192.168.x.x ...

This problem appered when I was checking out older tag from the Chromium project. Working with Release Branches ~/chromium_build/src$ git fetch --tags ~/chromium_build/src$ git checkout -b tag_35.0.1849.0 35.0.1849.0 ~/chromium_build/src$ gclient sync --with_branch_heads --jobs 16 Error log: Syncing projects: 100% ( 1/ 1) src src (ERROR) ---------------------------------------- [0:00:00] Started. ________ running 'git reset --hard HEAD' in '/home/sam.chen/chromium_source/src' [0:00:00] HEAD is now at 77bd011 Publish DEPS for Chromium 35.0.1849.0 [0:00:00] _____ src : Attempting rebase onto 77bd011602b1799f715591e697806c55e7ef8b7f... [0:00:00] Current branch tag_35.0.1849.0 is up to date. [0:00:00] ---------------------------------------- Error: 1> Dependency src specified more than once: 1> src(https://chromium.googlesource.com/chromium/src.git) [https://chromium.googlesource.com/chromium/src.git] 1> vs 1> src(https://chromium.googlesource.com/chromium/src.git) -> src(https://chromium.googlesource.com/chromium/src.git@ae69ae7642 35ccaac55fc44a3b5f3276ff34cb58) [https://chromium.googlesource.com/chromium/src.git@ae69ae764235ccaac55fc44a3b5f3276ff34cb58] You need to edit the .DEPS.git file, remove the entry ‘src’ and then gcient sync --with_branch_heads. ...

First, check out and install the depot_tools package. $ git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $ export PATH=$PATH:/path/to/depot_tools Checkout source code $ mkdir ~/chromium_build && cd $_ ~/chromium_build$ fetch --nohooks android //Configure GYP ~/chromium_build$ echo "{ 'GYP_DEFINES': 'OS=android', }" > chromium.gyp_env //Update projects from gyp files. //You may need to run this again when you have added new files, updated gyp files, or sync'ed your repository. ~/chromium_build$ gclient runhooks Environment setup ~/chromium_build$ sudo apt-get install openjdk-7-jdk //config default JDK ~/chromium_build$ sudo update-alternatives --config javac ~/chromium_build$ sudo update-alternatives --config java ~/chromium_build$ sudo update-alternatives --config javaws ~/chromium_build$ sudo update-alternatives --config javap ~/chromium_build$ sudo update-alternatives --config jar ~/chromium_build$ sudo update-alternatives --config jarsigner //install build dependencies ~/chromium_build$ src/build/install-build-deps-android.sh // Install Google Play Services ~/chromium_build$ src/third_party/android_tools/sdk/tools/android update sdk --no-ui --filter 57 Build ~/chromium_build$ cd ~/chromium_build/src //Full browser ~/chromium_build/src$ ninja -C out/Debug chrome_public_apk //WebView ~/chromium_build/src$ ninja -C out/Debug android_webview_apk //sync source ~/chromium_build/src$ gclient sync Android APK location: ~/chromium_source/src/out/Debug/apks/ ...

This is a How-To article that include installation and compile LaTeX file to PDF using Texmaker, Sublime Text 3, and Vim. Install TeX Live Install texlive-latex-extra instead of texlive-latex-base. $sudo apt-get install texlive-latex-extra -y Initial user tree in home directory Before using tlmgr in user mode, you have to set up the user tree with the init-usertree action. tlmgr is TeX Live package manager, you can run tlmgr --help for more detail. The full documentation for tlmgr ...

Real-Time Monitor for rpi-monitor: Update system status every 5 seconds. Two HTML layouts: change different layout via click Real-Time on navigation bar. Project on github: rpi-monitor Layout 1(default): Layout 2:

Core Hollow Body Hold Plank Variation L Sit Upper Chest/Push up Exercises & Variations Pull-up Dips Lower Lower Back Leg workout Other resources Full Body workout Core beginner to advanced Push beginner to advanced Push beginner to advanced Comprehensive handstand tutorial

I recently switched my blog from Google Blogger to GitHub Pages, here is how I built my blog. I’ll go through the following: Install Jekyll on Raspberry Pi Setup Jekyll Theme Post a new article Images minimization Commit to GitHub Using Jekyll and Minimal Mistake build a blog and host on GitHub and Raspberry Pi(or Ubuntu). Requirements: Raspberry Pi(or Ubuntu) GitHub account Jekyll 2.2+ Minimal Mistake Grunt If you have no idea with these things, here are useful resources: How Jekyll Works Jekyll Installation Minimal Mistake Theme Setup GitHub Pages Getting started - Grunt ...