noovo job

https://sourcecodebrowser.com/libmicrohttpd/0.9.0/files.html https://sourcecodebrowser.com/libmicrohttpd/0.9.0/microhttpd_8h.html#a7d207efa3873993c6d3a72beb9367f75

https://github.com/video-dev/hls.js?files=1 Pull requests are welcome. Here is a quick guide on how to start. First, checkout the repository and install required dependencies git clone https://github.com/video-dev/hls.js.git # setup dev environement cd hls.js npm install => package.json # build dist/hls.js, watch file change for rebuild and launch demo page npm run dev => # lint npm run lint ------------------------------- { "name": "hls.js", "version": "0.7.5", "license": "Apache-2.0", "description": "JavaScript HLS client using MediaSourceExtension", "homepage": "https://github.com/video-dev/hls.js", "authors": "Guillaume du Pontavice <guillaume.dupontavice@dailymotion.com>", "repository": { "type": "git", "url": "https://github.com/video-dev/hls.js" }, ...

https://taozj.org/201604/oversee-of-http-based-on-libmicrohttpd.html

scp ew100_scan root@192.168.0.190:/usr/local/bin/ew100_scan

sudo dd of=/home/john/temp/image.img if=/dev/mmcblk0 bs=1M status=progress sudo dd if=/home/john/temp/image.img of=/dev/mmcblk0 bs=1M status=progress dd 指令參考 https://mini.nidbox.com/diary/read/8640448

http://www.tecmint.com/ifconfig-command-examples/ 1. View All Network Setting 2. Display Information of All Network Interfaces 3. View Network Settings of Specific Interface 4. How to Enable an Network Interface 5. How to Disable an Network Interface 6. How to Assign a IP Address to Network Interface 7. How to Assign a Netmask to Network Interface

使用實例： scp 命令的實際應用概述：   從本端伺服器複製到遠端伺服器 ：   (1)  複製檔案 ：   命令格式：   scp local_file remote_username@remote_ip:remote_folder   或者   scp local_file remote_username@remote_ip:remote_file  

http://linux.vbird.org/linux_basic/redhat6.1/linux_06command.php#df

http://engineering.dailymotion.com/introducing-hls-js/

Press  SHIFT + PRINTSCREEN  for a screenshot of a Region you select with your Mouse.

sudo gtkterm pidof noovo pidof用于找出正在运行的程序的进程PID（find the process ID of a running program.），程序可以是一个二进制执行程序，也可以是一个shell脚本。如果是找出java程序的进程PID，pidof就无能为力了，可以使用ps -ef|grep java或jps -l来查看java进程的信息。通常找出进程PID的目的是确认程序是否在运行、或者为了把它杀掉、或者发送一个信号给它。 ifconfig find eth0 inet addr: ?.?.?.? ssh root@ ?.?.?.? noovo -i tuner curl -H "application/json" -X POST -d '{     "scan_mode": "manual",     "mstore_pid": 728,     "mreceive_pid": 828,     "auto_scan": [{"id": 0, "start_freq":533000, "end_freq":581000, "band":6000}],     "manual_scan":[ {"id":0, "freq": 615000 , "band":8000},{"id":1, "freq":545000, "band":6000}     ]}' localhost:9012/nvp/tuner_setting QCAST.ipts/storage/ ====> received mstore data

https://www.gnu.org/software/make/manual/make.html#Automatic-Variables 10.5.3 Automatic Variables Suppose you are writing a pattern rule to compile a ‘ .c ’ file into a ‘ .o ’ file: how do you write the ‘ cc ’ command so that it operates on the right source file name? You cannot write the name in the recipe, because the name is different each time the implicit rule is applied. What you do is use a special feature of  make , the  automatic variables . These variables have values computed afresh for each rule that is executed, based on the target and prerequisites of the rule. In this example, you would use ‘ $@ ’ for the object file name and ‘ $< ’ for the source file name. It’s very important that you recognize the limited scope in which automatic variable values are available: they only have values within the recipe. In particular, you cannot use them anywhere within the target list of a rule; they have no value there and will expand to the empty string. Also,...

http://stackoverflow.com/questions/11394659/where-does-the-value-of-cxx-in-a-makefile-come-from https://www.gnu.org/software/make/manual/make.html#Implicit-Variables CXX Program for compiling C++ programs; default ‘ g++ ’.

https://www.freebsd.org/cgi/man.cgi?tar(1) -Z , --compress , --uncompress (c mode only) Compress the resulting archive with compress(1) . In extract or list modes, this option is ignored. Note that, unlike other tar implementations, this implementation recognizes compress compression automatically when reading archives. -x Extract to disk from the archive. If a file with the same name appears more than once in the archive, each copy will be extracted, with later copies overwriting (replacing) earlier copies. The long option form is --extract .

https://philipzheng.gitbooks.io/docker_practice/content/introduction/what.html

http://blog.xuite.net/ha126269/94113267/44092194-Ubuntu-%E5%AE%89%E8%A3%9DMeld

0 代表鍵盤輸入 1 代表螢幕輸出 2 代表錯誤輸出 below is ref from:  http://ibookmen.blogspot.tw/2010/11/unix-2.html 這幾天因為研究 L4D2 的專屬伺服器架設，看到  Srcds  網站針對確保 Srcds 服務程序能隨時保持高優先權，在 crontab 底下使用 renice 的方式每五分鐘調整一次程式的優先權，其指令中 renice -20 `cat /home/yoursrcdspath/srcds.pid` >/dev/null 2>&1 最後面的「>/dev/null 2>&1」為 Unix 的重新導向技巧。雖然大約知道是什麼，不過實際上的原理我卻一直不明白，大約查了一下，疑問變更多。於是我決定來搞清楚它的來龍去脈，這篇文章就是這樣來的。 首先，我們先說明一下這段語法的作用，「>/dev/null 2>&1」實際上在這裡會將左邊程式的執行結果丟給「/dev/null」，然後不管程式有什麼錯誤，也會一併丟給 null。熟悉 Unix 的人大概知道，「/dev/null」是 Unix 底下的垃圾筒+黑洞。它不帶任何意義，所有丟進去的東西都會被吃掉然後不見，反正你不想看到的東西丟給 null 就對了。而「>」的意思其實是，將「>」左邊輸出的東西重新導向到右邊去。但不止是這樣而已，系統將標準輸入輸出分成三個：標準輸入 (stdin)、標準輸出 (stdout)、以及標準錯誤輸出 (stderr)，它們的 fd (file descriptor, 檔案描述子) 分別是 0、1、2。當「>」左邊未指定任何東西時，它會讀取左方程式的標準輸出 (也就是 fd=1) 重新導向給右邊的東西，但是你也可以指定要重新導向的 fd (也就是說「>abc.txt」會等於「1>abc.txt」)。所以可以想見 2>&1 的意思應該是把 fd=2，也就是標準錯誤輸出重新導向給 &1。而這邊的 &1 指的其實就是 fd=1。這邊似乎有點混淆視聽的感覺，為什麼「>」前面的 fd 不需要指定 &，後面的 fd 卻又要加 & 呢？我沒...