You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
CLIs are a fantastic way to build products. Unlike web applications, they take a small fraction of the time to build and are much more powerful. With the web, you can do whatever the developer programmed. With CLIs, you can easily mash-up multiple tools together yourself to perform advanced tasks. They require more technical expertise to use, but still work well for admin tasks, power-user tasks,
The Recurity Lablog Posts computer security, research, reverse engineering and high level considerations First Round: Git LFS In mid May 2017, I was about to go on my two month parental leave, when I stumbled across a nifty vulnerability in Git LFS, which is developed by the fine people at GitHub. The actual vulnerability was shockingly simple: Git LFS can be configured (partially) by a .lfsconfig
egzactã¨ããã³ãã³ãã®è©°ãåããã»ãããä½ã£ã¦ã¿ã¾ããã â Github ãã£ãã zipã§å¤éå§ç¸®ããã®ã«ã$ zip ãã¡ã¤ã« | zip | tee zip1 | zip | tee zip2 | zip | tee zip3 ããã¿ãããªã®åºæ¥ãªãï¼ #ã·ã§ã«è¸ #usptomo â ã±ã´ãã (@papiron) 2016å¹´3æ25æ¥ ããã¯ããã·ã§ã«è¸çé1ã®æ¹ã®çºè¨ã§ããã¢ã³ãã¦ã¤ã«ã¹ã½ããã®åä½ç¢ºèªã§ãå¤éZIPããããã¹ãã¦ã¤ã«ã¹ãã¡ã¤ã«ãå¿ è¦ã ã£ãã¨ã®ãã¨ã§ããä½äººãã®æ¹ããã¢ããã¤ã¹ãé ãã¦ããããã§ãããæ®å¿µãªããã·ã§ã«ã§ãµã¯ãã£ã¨ã¯çµå±ã§ããªãã£ããæ§åã§ãã2ã ãã®äºä¾ã¯ãã·ã§ã«ä¸ã§ã®ã¯ã³ã©ã¤ãã¼ï¼a.k.a ã·ã§ã«è¸3ï¼ã®å¼±ç¹ã®ä¸ã¤ãå¦å®ã«è¡¨ãã¦ãã¾ããæååãåãåºããããå¤æãããã¨ãããã£ã«ã¿ãªã³ã°ã®å¦çã¯å¾æã§ããããã¿ã¼ã³çæãæ¯è¼çè¦æã§
package main import ( "flag" "fmt" "net/http" "os" "os/exec" "runtime" "strconv" "strings" ) var ( port int user string pass string com string ) func main() { //parse args flag.IntVar(&port, "p", 8080, "port /default:8080") flag.StringVar(&user, "user", "", "user (BASIC AUTH)") flag.StringVar(&pass, "pass", "", "pass (BASIC AUTH)") flag.Parse() com = strings.Join(flag.Args(), " ") //start server f
Stop using tail -f (mostly) 12 Mar 2015 I still see a lot of people using tail -f to monitor files that are changing, mostly log files. If you are one of them, let me show you a better alternative: less +F The less documentation explains well what this +F is all about: Scroll forward, and keep trying to read when the end of file is reached. Normally this command would be used when already at the e
> groovy mvnfind -q "commons lang" com.btmatthews.jaxb2_commons:jaxb2-commons-lang3:1.0.0 com.cedarsoft.commons:lang:6.0.1 com.mysema.commons:mysema-commons-lang:0.2.4 commons-lang:commons-lang:20030203.000129 fm.last.commons:lastcommons-lang:3.1.1 net.bramp.jackson:jackson-datatype-commons-lang3:0.1 net.dongliu.commons:commons-lang:1.0.3 net.sf.staccatocommons:commons-lang:1.2 org.andromda.thirdp
Linuxã®æ¨æºã³ãã³ãã¯å¼·åãªãã®ã§ã¯ããããå®éã«äººéã使ãéã«ããããããããã¨ããã¨ååã§ã¯ãªãã ããã§ãä»åã¯Linuxã®æ¨æºã³ãã³ãããä¹ãæããäºãå¯è½ãªã³ãã³ãã©ã¤ã³ã¦ã¼ãã£ãªãã£ã¼ã調æ»ãæ´çãã¦ã¾ã¨ãã¦ã¿ããã¨ã«ããã 1.df â dfc ã¾ãã¯ããã以åã«ãã¡ãã§ãè¨è¿°ãã¦ããã dfã³ãã³ããããåãããããããã³ãã³ãã§ããã¼ã§å©ç¨çãèªèãããã¨ãåºæ¥ãã ã¤ã³ã¹ãã¼ã«ã¯ä»¥ä¸ã®ã³ãã³ãã§è¡ããã sudo apt-get install dfc (Debian or Ubuntu) 2.vmstat â dstat ããã©ã¼ãã³ã¹ã®ã¢ãã¿ãªã³ã°ã§ããç¨ããããvmstatããæ´ã«æ¡å¼µããã³ãã³ãã§ããdstatã«ããã dstatã«ã¯ãvmstatã«ã¯ãªããããã¯ã¼ã¯ã«é¢ããããã©ã¼ãã³ã¹ã追å ããã¦ãããè¦ãç®ãè¦ããããªã£ã¦ããã ã¤ã³ã¹ãã¼ã«ã¯ä»¥ä¸ã®ã³
ã§ããã°ã·ã§ã«ã¹ã¯ãªãããªãã¦æ¸ããããªããã ãã©ï¼ã¾ã ã¾ã æ¸ãæ©ä¼ã¯å¤ãï¼ã·ã§ã«è¸ãã¯ã³ã©ã¤ãã¼ã®ãããªåã£ããã¨ã§ã¯ãªãï¼ä»ã®ã²ã¨ã使ããããã·ã§ã«ã¹ã¯ãªãããæ¸ãããã«èªåãå®è·µãã¦ãããã¨ãã¾ã¨ãã¦ããï¼ ãã«ãã¡ãã»ã¼ã¸ æ¸ãã¦ãã·ã§ã«ã¹ã¯ãªããã使ãæ¨ã¦ã§ã¯ãªãä½åº¦ã使ããã®ã§ããå ´åã¯ï¼æ¬ä½ãæ¸ãå§ããåã«ï¼ãã®ã¹ã¯ãªããã®ä½¿ãæ¹ã表示ããusageé¢æ°ãæ¸ãã¦ãã¾ãï¼ ãããæ¸ãã¦ããã¨ï¼å¾ã ãã¼ã ã¸å ±æããããããªãï¼ã¨ããããusageè¦ã¦ãã ããã¨è¨ããï¼ã¾ãï¼ãããããæ¸ããã¨ã§ï¼åãªãã·ã§ã«ã¹ã¯ãªããã§ãã£ã¦ãèªåã®ä¸ã§åä½ãæ´çãã¦ããæ¸ãå§ãããã¨ãã§ããï¼é¢æ°ã¨ãã¦æ¸ãã®ã¯ï¼usageã表示ãã¦ãããã¨ããå ´é¢ãããã¤ãããï¼ä½¿ãåããã¨ãã§ããããï¼ ä»¥ä¸ã®ããã«æ¸ãï¼ function usage { cat <<EOF $(basename ${0})
naoya_itoã®ç«ãå´ããã·ã§ã«tips - Togetter ãããèªãã§ãµã¨æ¸ããããªã£ãã®ã§ãã¡ãªã¿ã«åã¯bash使ã£ã¦ãã¾ãã CTRLã使ã£ã便å©ç³» ã¾ããUNIXãªæä½ãããã ãã¼ãã¤ã³ã æå³ CTRL + s ãã¼å ¥åãåãä»ããªããã ç»é¢åºåæãã CTRL + q ä¸è¨è§£é¤ CTRL + z ããã¯ã°ã©ã¦ã³ãã«. fgã§æ»ã CTRL + l ç»é¢ãã¯ãªã¢ãclearã¨åç CTRL + c ç¾å¨ã®å¦çãåæ¢ CTRL + d exitã¨åç CTRL + r historyããã³ãã³ãæ¤ç´¢ emacsã£ã½ãã㤠ã©ã£ã¡ãã¨ããã¨ãã¼æä½ã«è¿ããåºæ¬ã¯emacsãmetaã¯åã¯optionã«å²ãå½ã¦ã¦ããã¨ãããã触ããã人ã¯ESCã§OKã ãã¼ãã¤ã³ã æå³ CTRL + a è¡é CTRL + e è¡æ« CTRL + f â CTRL + b â CTRL
Interested in the Go programming language? This tutorial will show you how to write a simple command-line task tracker using Go. It is assumed you have completed the tour and have a working Go environment already installed. Our program will work similarly to todo.txt. When done, we will be able to add, list, and complete tasks from the command line using the command âtodoâ: $ todo ls [1] [2014-3-2
Being sick of myself occasionally wiping off the changes made to files by running wrong commands, I have started writing a program called "Unco" (pronunciation: an-ko) - a command that records the changes to the file system, and let the users undo the changes afterwards if necessary. Unlike existing command-level solutions like aliasing rm to trash-cli, Unco is designed to be capable of undoing ch
ã¾ã¨ã $ git diff --no-prefix HEAD~ > thisis.patch $ patch --dry-run -p0 < thisis.patch $ patch -p0 < thisis.patch git diffã«--no-prefixãã¤ããäºã§ãæ®éã®patchã§å½ã¦ãããããããã¡ã¤ã«ãåºåã§ãã¾ãããã®ä¾ã§ã¯HEADã®1åå*1ããHEAD*2ã¾ã§ã®ãããã§ãã æ®éã®patchã³ãã³ãã®ã»ãã®ç¥èããã¾ãç¡ãã¦-p0ããã¾ãã¡ããåãããªããã§ãããgit diff --no-prefixã§ä½æããããããã¡ã¤ã«ãå½ã¦ãã«ã¯å¿ è¦ã¿ããã§ãã--dry-runã¯ãå®éã«ã¯å½ã¦ãªããã©å½ã¦ãå ´åã®çµæãåºåãã¾ãããªã®ã§ãã¾ãã¯--dry-runã§ç¢ºèªãã¦ãåé¡ãç¡ããã°å®éã«ããããå½ã¦ã¾ãã ã¨ã³ããªã¼æ¸ããå¾ã«æãã¦ããã£ãè£è¶³ patch -p1ã®
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}