110 ms·

Unix Tricks

361 points by dedalus 12y ago

INTPenis 12y ago
I call this one sshping. while sleep 0.1; do nc -w 1 -z host 22; done Useful when waiting for systems to boot.
- lloeki 12y ago
  Add this line to (vixie) cron: @reboot /bin/date | /usr/bin/mail -s "$(/bin/hostname) booted" root@example.com If you don't want to configure postfix as a smarthost (which is not that hard and recommended if only to have mail queued for retry), use ssmtp.
- stevekemp 12y ago
  $ until-success ssh ... If you have my sysadmin-utils installed: https://github.com/skx/sysadmin-util https://github.com/skx/sysadmin-util
voltagex_ 12y ago
I wonder if I can convince the author of this to put it up in a Git repo so everyone can contribute. It probably needs the tiny URLs removed (IME, they're more likely to break than the original site)
samsaga2 12y ago
It's amazing how many years I've been using bash and I still have things to discover. Ctrl-x Ctrl-e nice tip!
- tomsthumb 12y ago
  `man readline` and `man bash` alike blow my mind every time I pop them open.
- pling 12y ago
  I still prefer "sh" on BSD (particularly OpenBSD). It doesn't have as many knobs to turn nor as many surprises.
  - currysausage 12y ago
    sh, the Bourne shell mode of pdksh? Isn't that a little too limited? pdksh (/bin/ksh) though is great, yes. I'm in general a big fan of the OpenBSD userland: straightforward and very, very well-documented. Real manpages, no religious "The full documentation for xyz is maintained as a TeXinfo manual" crap. A well-conceived featureset and good docs are key to properly learning a platform. OpenBSD taught me a lot about Unix. If you later realize that Bash has some feature that you actually need, you can still install it.
    - Zenst 12y ago
      Also worth noting that native borne shell was always slightly slower than korn shell. Though been a long time since I checked that one out, though did on few systems and found it to be so. But there again csh was also about then, distant memory in for many that one. Also anything that will run script wise on bourne will run as is under korn. Though you may well find that it is historical, which one a user picks shell wise. People who started or worked a lot with Sun systems will be csh fans. Old vets more inclided to bourne, though very few. As for korn shell, that would be mostly down to AIX systems as that is the default upon them as with the other systems mentions, default wise. Then for Linux you will find a bias towards bash. Least that is what I have observed. Though history does give us some intersting trends and the awk, perl, python transition and preference will also mostly be down to when somebody got into unix as a whole. Again old school, awk. Old, perl and not so long ago the python brigade. But that is just a rule in thumb and more helpful in explaining why there is a solo perl script when everything else done in xyzzy type encounters. As for OpenBSD, good choice, I prefer it due to the file system layout and more akin to old school unix unlike Linux which is `creative` more than not in choices, so feels less at home. Still back in the early days we had AT&T and Berkly BSD flavours and with that the ps command, oh the fun and games. But least thinks a little bit more common across flavours than before and yet still each has there own quirks.
- raju 12y ago
  In bash fc will open your $EDITOR with the last command you just typed. Just like Ctrl-x Ctrl-e but you don't need a command in place to edit.
atoponce 12y ago
http://www.commandlinefu.com/commands/browse/sort-by-votes http://www.commandlinefu.com/commands/browse/sort-by-votes
rzimmerman 12y ago
Ctrl-R is by far the most useful one for me.
- cmatteri 12y ago
  The article doesn't say, so it's worth mentioning that you can type ctrl-R multiple times to search further back into command history.
  - aatos 12y ago
    It doesn't mention either that you can search to the other direction by pressing ctrl-s (usually it also sends the stop signal which should be removed by "stty -ixon"). Very useful if you go past the entry you are looking for.
  - danielweber 12y ago
    I use C-r constantly. But sometimes I need to find a command, and then edit it before running it. What is the proper way to exit "search mode" and go into the normal "edit" mode?
    - morsch 12y ago
      Any movement key will do the trick. I usually use cursor-right or the end key. It's so ingrained I had to actually do it in a shell to know what it was I did.
      - danielweber 12y ago
        ISTR pressing one of those keys would obliterate the part of my line where I was writing, putting in ^B characters. I can't replicate it now on my test box; it works exactly the way you say it should. It may be a terminal issue; I'm currently on Windows using cygwin to ssh to Linux.
    - aatos 12y ago
      C-g (as in quit https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html https://www.gnu.org/software/emacs/manual/html_node/emacs/Qu...) is the 'proper' way but yeah, not the only one.
cellover 12y ago
Very interesting resource! It's amazing to see how after 10 years of using command line that you can learn new tricks. Every single day!
nemasu 12y ago
One to add: Unfreezing terminal after pressing Ctrl+S by accident. Press Ctrl-Q.
- derefr 12y ago
  Or drop a `stty -ixon` into your .bash_profile to never have that problem again.
- danielweber 12y ago
  One that I needed to use a lot in the old days, and still occasionally need: If your font is all messed up, echo C-v C-o. C-v puts you into a literal mode, and C-o gets you back into the normal character set. (You probably got there by emitting a C-p at some point.)
  - mkesper 12y ago
    I always used 'reset' for that.
ing33k 12y ago
one more resource http://www.thegeekstuff.com/2010/11/50-linux-commands/ http://www.thegeekstuff.com/2010/11/50-linux-commands/
sigsergv 12y ago
And for python3: python3 -m http.server 8080
TimWolla 12y ago
You might want to try out the more modern fish shell as well: http://fishshell.com/ http://fishshell.com/ It makes history searching even easier.
- bshimmin 12y ago
  I love fish and have happily been using it for years. Every time it comes up here, though, someone inevitably will complain about compatibility - and I will admit that RVM, for instance, has definitely caused me problems with fish in the past. I guess it depends quite a lot on your particular usage and requirements.
  - robin_reala 12y ago
    I never got RVM working with fish; unsurprising, seeing as it’s 20k lines of bash. rbenv works well though (with one additional conf line), and chruby was working on support last time I checked.
    - bshimmin 12y ago
      There's a wrapper to get RVM working with fish, in case it matters to you now; details here: https://rvm.io/integration/fish https://rvm.io/integration/fish
      - robin_reala 12y ago
        Doesn’t matter now :) rbenv does everything I need in a lighter package.
    - platz 12y ago
      RVM is pretty heavyweight. Why not something like chruby?
      - robin_reala 12y ago
        I started using RVM when it was the only (possibly well-known?) game in town, and never switched until I started using fish and found that it didn’t work.
nemasu 12y ago
I actually bookmarked a similar page a little while ago, super useful: http://www.reddit.com/r/linux/comments/21rm3o/what_is_a_useful_linux_tool_that_you_use_that http://www.reddit.com/r/linux/comments/21rm3o/what_is_a_usef...
curiousHacker 12y ago
You know what I hate? My history isn't aggregated in real time across all my Mac OS X terminal windows. You know what else I hate? Typing in long commands in the Mac OS X terminal and then them wrapping weirdly. Especially when I hit the up arrow to go back in my terminal history.
- ibotty 12y ago
  > My history isn't aggregated in real time across all my Mac OS X terminal windows. zsh has `setopt inc_append_history` and `setopt share_history`. i am sure bash has something similar.
- Tiksi 12y ago
  Here you go, just throw it in your .bashrc: shopt -s histappend export HISTSIZE=100000 export HISTFILESIZE=100000 export HISTCONTROL=ignoredups:erasedups export PROMPT_COMMAND="history -a;history -c;history -r;$PROMPT_COMMAND" I wish I could give credit to where I originally found this but it was ages ago.
  - mtford 12y ago
    Many thanks for this! This has been a thorn in my side for a while but never got round to doing anything about it...
  - grimgrin 12y ago
    Don't you want HISTCONTROL=ignoreboth ?
  - gknoy 12y ago
    I've been using `history -a`, but what do `history -c` and `history -r` do? It looks like it clears your shell's history, and then re-populates it from the .bash_history file?
    - Flenser 12y ago
      history -a # append history lines from this session to the history file. #History file may contain history from other terminals not in this one so: history -c # clear [in-memory] history list deleting all of the entries. history -r # read the history file and append the contents to the history list instead. I've heard that -n can be problematic which is why -c then -r is used.
chanux 12y ago
Pipe to clipboard with following alias alias clip='xsel -i --clipboard' Get tree view of directories alias lst='tree -L 2 $1' Also I use za to go up in directory tree bash https://gist.github.com/chanux/1119556 https://gist.github.com/chanux/1119556 fish https://gist.github.com/chanux/9411092 https://gist.github.com/chanux/9411092
wombit 12y ago
http://explainshell.com/ http://explainshell.com/
3rd3 12y ago
man hier is pretty cool. It explains the root directory structure of the system.
- robert_tweed 12y ago
  TIL. As a long-time DOS user that often gets a bit lost on Unix systems I cannot stress how awesome it is to have found out about this!
  - jordigh 12y ago
    Wow, DOS users still exist? Which one? FreeDOS? Back in the late 90s when I first moved to Debian from Windows, growing up with a DOS CLI made the transition far easier to me (and having some FTP exposure didn't hurt either).
    - robert_tweed 12y ago
      There's no good way to refer to the entire DOS/Windows command shell lineage without confusion, but that's what I meant. I don't technically use DOS at all anymore. I think "that system" is easier to understand in it's entirety and find your way around than Unix, although it has been getting progressively more complex for years. I actually use OS X most of the time now (plus Linux on servers and Windows for 3D stuff).
      - thinkpad20 12y ago
        > I think [DOS] is easier to understand in it's entirety and find your way around than Unix Yikes, I recently had to do a bit of development on a windows box and I found the command-line tools (not to mention CMD itself, which seems to have stopped development in 1993) to be absolutely awful. I could barely survive without Cygwin, git bash, etc giving me some semblance of a functional shell setup. I guess it's different strokes for different folks.
        robert_tweed 12y ago
jalanb 12y ago
I notice j.py in that list. I forked that a wee while back, and have been enhancing it ever since: http://www.al-got-rhythm.net/kd/ http://www.al-got-rhythm.net/kd/
- grimgrin 12y ago
  https://github.com/rupa/z https://github.com/rupa/z is really nice, too. Pure bash.
fauria 12y ago
I would add: TOOLS ... * 'tree' instead of 'ls -R' ...
- voltagex_ 12y ago
  Which package would that be in?
  - chanux 12y ago
    tree on ubuntu
  - ejstronge 12y ago
    On Debian/Ubuntu, you can use the `apt-file` package to determine what package a file resides in. For example: apt-file search /bin/tree
  - WickyNilliams 12y ago
    `brew install tree` on OSX Also this bash function from Mathias Bynen's famous dotfiles is a fantastic shortcut for colorised (and more) output from tree. https://github.com/mathiasbynens/dotfiles/blob/master/.functions#L240-L246 https://github.com/mathiasbynens/dotfiles/blob/master/.funct...
danielweber 12y ago
> - 'sort | uniq' to check for duplicate lines sort -u
xr09 12y ago
j.py? The original is autojump: https://github.com/joelthelion/autojump/ https://github.com/joelthelion/autojump/
- grimgrin 12y ago
  z is a nice replacement that is purely written in bash. https://github.com/rupa/z https://github.com/rupa/z
k4rthik 12y ago
I have for cmd in $(compgen -c); do if [[ $cmd =~ ^[0-9a-zA-Z]+$ ]]; then eval "alias $cmd?='man $cmd'"; fi; done in my .bashrc to alias command?=man command, saves some typing to get to man pages ( which I do very often )
- grkvlt 12y ago
  Wow. I never knew about the `compgen -c` command to show bash command completions. Also from this reference [1] I found these: % compgen -b # built-ins % compgen -k # keywords % compgen -A function # functions % compgen -abckA function # everything [1] http://www.cyberciti.biz/open-source/command-line-hacks/compgen-linux-command/ http://www.cyberciti.biz/open-source/command-line-hacks/comp...
- vram22 12y ago
  Speaking of man pages, in earlier versions of Unix and Linux, I used to want to redirect the output of many man commands to files for later reading, e.g. if working on C, say I wanted to read 'man ioctl', 'man stdio', 'man signal', etc. But the man output had {n|t}roff formatting characters in it, for print output, which used to mess up vi. So I used to use this script I wrote, called m: # Put this script in a directory in your PATH. # m: pipe man output through col and save to file(s). mkdir -p ~/man # Only creates the dir first time, including all dirs in the path. for name: # in $* is implied man $name | col -bx > ~/man/$name.m done Do a "chmod u+x m" to be able to run it. Then run it like this: m ioctl stdio signal # or any other commands Then: pushd ~/man; view ioctl.m stdio.m signal.m; popd to read those pages, now stripped of formatting characters.
- bubblesorting 12y ago
  For zsh: for cmd in $(compgen -c); do if [[ $cmd =~ ^[0-9a-zA-Z]+$ ]]; then eval "alias $cmd\?='man $cmd'" ; fi; done # had to escape the ? in the alias name Cool trick :)
AssertFailure 12y ago
Instead of using netcat when tunneling SSH through another machine like this: ProxyCommand ssh -T host1 'nc %h %p' one should use this instead: ProxyCommand ssh -W %h:%p host1
- aseidl 12y ago
  The only problem with -W is that it is not available everywhere yet: RHEL6 defaults to OpenSSH 5.3, while -W was introduced in 5.4. Thankfully EL7 comes with OpenSSH 6.4 (and a kernel newer than 2.6.32!).
lloeki 12y ago
Instead of ssh -R 12345:localhost:22 server.com "sleep 1000; exit" use ssh -R 12345:localhost:22 -n server.com The -n flag tells ssh to only make a connection, without ever running a shell. This means it even works when you don't have shell access (say, with a command= entry in .authorized_keys). Also, I cannot recommend envoy enough in lieu of ssh-agent, if you're not using a GUI ssh agent already (e.g OSX keychain or GNOME keyring) Last, I guarantee you don't want "$@" in those aliases, but either "$*" or $@ (certainly the latter).
- zipperhead 12y ago
  I usually visit these threads knowing that I will pick up something useful to add to the toolbox... thank you for 'envoy' - I think it will streamline my ssh key management.
- ciupicri 12y ago
  I think you meant -N, not -n. From the man page[1]: -N Do not execute a remote command. This is useful for just for‐ warding ports (protocol version 2 only). -n Redirects stdin from /dev/null (actually, prevents reading from stdin). This must be used when ssh is run in the background. [1]: http://www.openbsd.org/cgi-bin/man.cgi?query=ssh&sektion=1 http://www.openbsd.org/cgi-bin/man.cgi?query=ssh&sektion=1
valarauca1 12y ago
Its implied on the list but not mentioned specifically. !! will be substituted with the last command you typed. So if your somebody like me who frequently types $ apt-get update Could not lock yada yada are you root? $ sudo apt-get update instead you can type $ apt-get update $ sudo !!
- cheepin 12y ago
  What I love about this is that if you up-arrow through your past commands, the "sudo !!" shows up as "sudo apt-get update"
  - valarauca1 12y ago
    Bash substitutions are done prior to execution so your history stays intact. Older open source projects are just amazing for how complete their feature set is.
    - pokpokpok 12y ago
      is this how people feel about religious texts?
      - valarauca1 12y ago
        Originally I was gonna write: >Religious texts don't change over time due to community suggested changes. Then I caught myself.
      - carlisle_ 12y ago
        You mean my bash fanaticism isn't religious?
- vehementi 12y ago
  I named my cat sudo bangbang
- a3_nm 12y ago
  It always feels more logical to me to just type "Ctrl-P Ctrl-A sudo" (previous history line, beginning of line, add missing sudo) than typing "sudo !!" or "sudo !!<tab>" if you need to edit the substitution. Same thing for the last argument, it's easily edited if you know the right shortcuts: Ctrl-P Alt-B Ctrl-U. (Works for bash, for zsh you need http://stackoverflow.com/q/3483604/414272 http://stackoverflow.com/q/3483604/414272). That said, I didn't know about Alt-.
Tepix 12y ago
Missing trick: In bash, "ESC" then "." fetches the last parameter of the previous command. It's invaluable (same as typing "!$" but you get to see and edit it)
- akirk 12y ago
  You can get any parameter of the previous command by using "Esc, <number>, Esc, .". If you repeat pressing "Esc, ." you get the n-th parameter from the command before the previous one, etc. More details in this Stackoverflow answer: http://stackoverflow.com/a/4010170/578588 http://stackoverflow.com/a/4010170/578588
- lloeki 12y ago
  It's actually Meta, emulated by an ESC character by the terminal. OSX tip: check "use Option as Meta" in Terminal's preferences, and you can keep Option pressed while you mash ".".
  - akirk 12y ago
    Which is fine if you never need to generate characters using the Option key. For example on a German keyboard you need the Option key to write { or }.
    - lloeki 12y ago
      I'm on a french layout so I know :-) It also has the side effect of "resurrecting" dead keys (which are unrelated to Option), making input of 'ê'and 'ï' impossible. An alternative is using iTerm2 which has a similar setting, liberally applyable to either Option key.
- Alupis 12y ago
  There are some great tips/tricks in this document. Too bad it's not in Markdown or something easier on the eyes!
  - grmarcil 12y ago
scarygliders 12y ago
Another one: Use dcfldd instead of dd if you want to see how far your dd operation is progressing... dcfldd if=[infile] of=[outfile] sizeprobe=if So. Much. Better. dcfldd also has many other useful options - read the man pages - and note that you'll have to install it from your linux distro's package repo beforehand.
- sushimako 12y ago
  You can also send SIGUSR1 to dd for progress info. From the manpage: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying. $ dd if=/dev/zero of=/dev/null& pid=$! $ kill -USR1 $pid; sleep 1; kill $pid 18335302+0 records in 18335302+0 records out 9387674624 bytes (9.4 GB) copied, 34.6279 seconds, 271 MB/s
  - scarygliders 12y ago
    Indeed you can :) But I prefer not to have to manually keep sending that ;)
    - staticshock 12y ago
      while ; do kill -s USR1 $(pgrep '^dd$'); sleep 5; done
  - carlisle_ 12y ago
    On OSX it's SIGINFO (29) in case anybody wondered
    - jamesog 12y ago
      Which you can also get by hitting Ctrl-T. This works for FreeBSD too. (Not sure about the other BSDs.)
      - carlisle_ 12y ago
        neato
o_____________o 12y ago
I was going to write a shell package/snippet manager until I discovered this: https://github.com/ziyaddin/jean https://github.com/ziyaddin/jean It would be nice to get all of these .bash_profile enhancements in as packages. I suppose it could be improved to prompt for a brew/apt install if needed.
wazoox 12y ago
Ctrl+r is fine when you're looking for something recent, but this one is useful when you're looking through a long list of similar commands. alias hist='history | grep' Use it like this: $ hist git 9543 git add toto 9544 git commit 9545 git log 9546 git log 9548 git add -A 9549 git commit 9550 git log 9633 git pull 9955 cd dev/git 9957 git grep copyof 9958 git grep copyof 9959 git pull By the way, do you know you can call back the 9633rd command in the history with "!9633"?
- hrrsn 12y ago
  Wow, this is great. All too commonly I do cat ~/.bash_history|grep, but this is way easier. Thanks!
- WickyNilliams 12y ago
  I use this all the time. In fact it was one of the first aliases i made when i switched to a UNIX system. Though I named mine `greph` (for grep history). Absolutely invaluable
jlas 12y ago
Along with the !! function you can reference the last call of a specific command like so: !<cmd> e.g. sometimes I forget the "ln -s" order of arguments (to which it gives me an error), so I follow it up with: ln -s !ln:3 !ln:2
kneth 12y ago
Now and then I reread a chapter of "Classic Shell Scripting" (http://shop.oreilly.com/product/9780596005955.do http://shop.oreilly.com/product/9780596005955.do) - probably the best book on shell script I know.
dorfsmay 12y ago
> In bash, 'ctrl-r' searches your command history No! In emacs ctrl-r searches your command history. It happens that bash use emacs mode by default. All other emacs basic commands work too: ctrl-p, ctrl-n, ctrl-f etc... If you are a vim user, and especially if you love venting how much you hate emacs, then please add this to your bashrc: set -o vi and now you can use vim command instead of emacs.
- dllthomas 12y ago
  'ctrl-r' is reverse-i-search in vi mode as well.
  - dventimi 12y ago
    'ctrl-r' is bound to isearch-backward in my Emacs. 'meta-r' is bound to comint-history-isearch-backward-regexp
dorfsmay 12y ago
> 'htop' instead of 'top' meh, I don't like htop. "atop" on the other hand!!!
marcosscriven 12y ago
A really handy one a colleague showed me yesterday was the /dev/fd/0|1|2 files, which are stdin/out/err respectively. Means you can use that file for utils that expect a file only. E.g echo "This would be contents of file" | someCommand /dev/fd/0
- LukeShu 12y ago
  These are also available as /dev/std{in,out,err}; the names of which are a little more self documenting :) $ ls -l /dev/fd /dev/std* | column -t lrwxrwxrwx 1 root root 13 Jun 27 16:32 /dev/fd -> /proc/self/fd lrwxrwxrwx 1 root root 15 Jun 27 16:32 /dev/stderr -> /proc/self/fd/2 lrwxrwxrwx 1 root root 15 Jun 27 16:32 /dev/stdin -> /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Jun 27 16:32 /dev/stdout -> /proc/self/fd/1 You can even access the file descriptors of other processes with /proc/${pid}/fd/; which is handy for (say) un-deleting a file that a process still has open. Another handy one is "process substitution" which lets you do the same thing with multiple streams by creating new file descriptors, and automatically turning them into /dev/fd/* paths: someCommand <(echo "contents of file 1") <(echo "contents of file 2") which is somewhat explained by: $ echo someCommand <(echo "contents of file 1") <(echo "contents of file 2") someCommand /dev/fd/63 /dev/fd/62
  - toddkaufmann 12y ago
    "process substitution" is one of the new useful things I learned this year (switched to bash from csh over 20 years ago). /proc/${pid}/fd/ is very useful for forensic purposes when you find some malware running that deleted itself and/or config files but still has a handle open to them.
meapix 12y ago
!.
joereggan190 12y ago
http://steamcommunity.com/profiles/76561198143338254 http://steamcommunity.com/profiles/76561198143338254
biftek 12y ago
zsh has a simple builtin `r` (which is just an alias for `fc -e -`). It lets you edit the previous command with search and replace. I use it for brew and git a lot. $ brew info rust $ r fo=stal
Zenst 12y ago
stty - sane Very handy if you do something silly like cat a binary file without piping it into strings -a This restores the terminal settings and sanity restored. Note you will often find yourself typing without seeing anything, least until you enter and execute the sane. Also asvise the following usage ctrl+c a couple of times to clear anything out of the input buffer queued up. stty -sane all good from here onwards and good time to play with od and remember the strings -a pipe next time.
currysausage 12y ago
I found Ctrl-O (execute current command from history and edit the next one) to be invaluable. Ctrl-V: type next input literally (e.g. Ctrl-V [Tab] if you don't want [Tab] to autocomplete). Alt-#: Prefix current line with "#" (don't execute it) and put it into history for later use. I'm sometimes surprised how many people don't know these: Ctrl-U/K: kill line before/after cursor.
agumonkey 12y ago
I used to be excited about this, now I found it shallow. Better unix tip => http://www.confreaks.com/videos/615-cascadiaruby2011-the-unix-chainsaw http://www.confreaks.com/videos/615-cascadiaruby2011-the-uni...
WickyNilliams 12y ago
A personal favourite of mine is aliasing common cd operations. alias ..="cd .." alias ...="cd ../.." # etc and of course `cd -` to jump to previous directory
andrey-p 12y ago
I love these, there's too much to process but I always get to learn at least one ridiculously useful thing. Today's was vim's `:set spell`.
gowan 12y ago
Send a command to display 1. `xterm -display :1 -e <command>` This is useful when running automated tests on top of vnc.
pmontra 12y ago
I suggest bashmarks http://www.huyng.com/projects/bashmarks/ http://www.huyng.com/projects/bashmarks/ to bookmark directories and jump there with a quick command. I also like to alias ..="cd .." and alias ...="cd ../.." to quickly navigate up.
thln666 12y ago
"- Compile your own version of 'screen' from the git sources. Most versions have a slow scrolling on a vertical split or even no vertical split at all" Or you could just use tmux which afaict is superior to screen in almost every way. http://tmux.sourceforge.net/ http://tmux.sourceforge.net/
joereggan190 12y ago
http://learn.hightail.com/t5/Ideas/UFC-175-Live-Stream-Watch-UFC-175-Weidman-vs-Machida-Live-Stream/idi-p/74016 http://learn.hightail.com/t5/Ideas/UFC-175-Live-Stream-Watch...
joereggan190 12y ago
UFC 175 Weidman vs Machida Live Stream http://learn.hightail.com/t5/Ideas/UFC-175-Live-Stream-Watch-UFC-175-Weidman-vs-Machida-Live-Stream/idi-p/74016 http://learn.hightail.com/t5/Ideas/UFC-175-Live-Stream-Watch...
aceperry 12y ago
>Don't know where to start? SMB is usually better than NFS for most cases. Not sure why he feels SMB is better, because in my experience, NFS usually works more smoothly and is easier to setup than SMB. But then, I don't usually use windows.

Unix Tricks

361 points by dedalus 12y ago

INTPenis 12y ago

I call this one sshping. while sleep 0.1; do nc -w 1 -z host 22; done Useful when waiting for systems to boot.

lloeki 12y ago
Add this line to (vixie) cron: @reboot /bin/date | /usr/bin/mail -s "$(/bin/hostname) booted" root@example.com If you don't want to configure postfix as a smarthost (which is not that hard and recommended if only to have mail queued for retry), use ssmtp.
stevekemp 12y ago
$ until-success ssh ... If you have my sysadmin-utils installed: https://github.com/skx/sysadmin-util https://github.com/skx/sysadmin-util

voltagex_ 12y ago

I wonder if I can convince the author of this to put it up in a Git repo so everyone can contribute. It probably needs the tiny URLs removed (IME, they're more likely to break than the original site)

samsaga2 12y ago

It's amazing how many years I've been using bash and I still have things to discover. Ctrl-x Ctrl-e nice tip!

tomsthumb 12y ago
`man readline` and `man bash` alike blow my mind every time I pop them open.
pling 12y ago
I still prefer "sh" on BSD (particularly OpenBSD). It doesn't have as many knobs to turn nor as many surprises.
- currysausage 12y ago
  sh, the Bourne shell mode of pdksh? Isn't that a little too limited? pdksh (/bin/ksh) though is great, yes. I'm in general a big fan of the OpenBSD userland: straightforward and very, very well-documented. Real manpages, no religious "The full documentation for xyz is maintained as a TeXinfo manual" crap. A well-conceived featureset and good docs are key to properly learning a platform. OpenBSD taught me a lot about Unix. If you later realize that Bash has some feature that you actually need, you can still install it.
  - Zenst 12y ago
    Also worth noting that native borne shell was always slightly slower than korn shell. Though been a long time since I checked that one out, though did on few systems and found it to be so. But there again csh was also about then, distant memory in for many that one. Also anything that will run script wise on bourne will run as is under korn. Though you may well find that it is historical, which one a user picks shell wise. People who started or worked a lot with Sun systems will be csh fans. Old vets more inclided to bourne, though very few. As for korn shell, that would be mostly down to AIX systems as that is the default upon them as with the other systems mentions, default wise. Then for Linux you will find a bias towards bash. Least that is what I have observed. Though history does give us some intersting trends and the awk, perl, python transition and preference will also mostly be down to when somebody got into unix as a whole. Again old school, awk. Old, perl and not so long ago the python brigade. But that is just a rule in thumb and more helpful in explaining why there is a solo perl script when everything else done in xyzzy type encounters. As for OpenBSD, good choice, I prefer it due to the file system layout and more akin to old school unix unlike Linux which is `creative` more than not in choices, so feels less at home. Still back in the early days we had AT&T and Berkly BSD flavours and with that the ps command, oh the fun and games. But least thinks a little bit more common across flavours than before and yet still each has there own quirks.
raju 12y ago
In bash fc will open your $EDITOR with the last command you just typed. Just like Ctrl-x Ctrl-e but you don't need a command in place to edit.

atoponce 12y ago

http://www.commandlinefu.com/commands/browse/sort-by-votes http://www.commandlinefu.com/commands/browse/sort-by-votes

rzimmerman 12y ago

Ctrl-R is by far the most useful one for me.

cmatteri 12y ago
The article doesn't say, so it's worth mentioning that you can type ctrl-R multiple times to search further back into command history.
- aatos 12y ago
  It doesn't mention either that you can search to the other direction by pressing ctrl-s (usually it also sends the stop signal which should be removed by "stty -ixon"). Very useful if you go past the entry you are looking for.
- danielweber 12y ago
  I use C-r constantly. But sometimes I need to find a command, and then edit it before running it. What is the proper way to exit "search mode" and go into the normal "edit" mode?
  - morsch 12y ago
    Any movement key will do the trick. I usually use cursor-right or the end key. It's so ingrained I had to actually do it in a shell to know what it was I did.
    - danielweber 12y ago
      ISTR pressing one of those keys would obliterate the part of my line where I was writing, putting in ^B characters. I can't replicate it now on my test box; it works exactly the way you say it should. It may be a terminal issue; I'm currently on Windows using cygwin to ssh to Linux.
  - aatos 12y ago
    C-g (as in quit https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html https://www.gnu.org/software/emacs/manual/html_node/emacs/Qu...) is the 'proper' way but yeah, not the only one.

cellover 12y ago

Very interesting resource! It's amazing to see how after 10 years of using command line that you can learn new tricks. Every single day!

nemasu 12y ago

One to add: Unfreezing terminal after pressing Ctrl+S by accident. Press Ctrl-Q.

derefr 12y ago
Or drop a `stty -ixon` into your .bash_profile to never have that problem again.
danielweber 12y ago
One that I needed to use a lot in the old days, and still occasionally need: If your font is all messed up, echo C-v C-o. C-v puts you into a literal mode, and C-o gets you back into the normal character set. (You probably got there by emitting a C-p at some point.)
- mkesper 12y ago
  I always used 'reset' for that.

ing33k 12y ago

one more resource http://www.thegeekstuff.com/2010/11/50-linux-commands/ http://www.thegeekstuff.com/2010/11/50-linux-commands/

sigsergv 12y ago

And for python3: python3 -m http.server 8080

TimWolla 12y ago

You might want to try out the more modern fish shell as well: http://fishshell.com/ http://fishshell.com/ It makes history searching even easier.

bshimmin 12y ago
I love fish and have happily been using it for years. Every time it comes up here, though, someone inevitably will complain about compatibility - and I will admit that RVM, for instance, has definitely caused me problems with fish in the past. I guess it depends quite a lot on your particular usage and requirements.
- robin_reala 12y ago
  I never got RVM working with fish; unsurprising, seeing as it’s 20k lines of bash. rbenv works well though (with one additional conf line), and chruby was working on support last time I checked.
  - bshimmin 12y ago
    There's a wrapper to get RVM working with fish, in case it matters to you now; details here: https://rvm.io/integration/fish https://rvm.io/integration/fish
    - robin_reala 12y ago
      Doesn’t matter now :) rbenv does everything I need in a lighter package.
  - platz 12y ago
    RVM is pretty heavyweight. Why not something like chruby?
    - robin_reala 12y ago
      I started using RVM when it was the only (possibly well-known?) game in town, and never switched until I started using fish and found that it didn’t work.

nemasu 12y ago

I actually bookmarked a similar page a little while ago, super useful: http://www.reddit.com/r/linux/comments/21rm3o/what_is_a_useful_linux_tool_that_you_use_that http://www.reddit.com/r/linux/comments/21rm3o/what_is_a_usef...

curiousHacker 12y ago

You know what I hate? My history isn't aggregated in real time across all my Mac OS X terminal windows. You know what else I hate? Typing in long commands in the Mac OS X terminal and then them wrapping weirdly. Especially when I hit the up arrow to go back in my terminal history.

ibotty 12y ago
> My history isn't aggregated in real time across all my Mac OS X terminal windows. zsh has `setopt inc_append_history` and `setopt share_history`. i am sure bash has something similar.
Tiksi 12y ago
Here you go, just throw it in your .bashrc: shopt -s histappend export HISTSIZE=100000 export HISTFILESIZE=100000 export HISTCONTROL=ignoredups:erasedups export PROMPT_COMMAND="history -a;history -c;history -r;$PROMPT_COMMAND" I wish I could give credit to where I originally found this but it was ages ago.
- mtford 12y ago
  Many thanks for this! This has been a thorn in my side for a while but never got round to doing anything about it...
- grimgrin 12y ago
  Don't you want HISTCONTROL=ignoreboth ?
- gknoy 12y ago
  I've been using `history -a`, but what do `history -c` and `history -r` do? It looks like it clears your shell's history, and then re-populates it from the .bash_history file?
  - Flenser 12y ago
    history -a # append history lines from this session to the history file. #History file may contain history from other terminals not in this one so: history -c # clear [in-memory] history list deleting all of the entries. history -r # read the history file and append the contents to the history list instead. I've heard that -n can be problematic which is why -c then -r is used.

chanux 12y ago

Pipe to clipboard with following alias alias clip='xsel -i --clipboard' Get tree view of directories alias lst='tree -L 2 $1' Also I use za to go up in directory tree bash https://gist.github.com/chanux/1119556 https://gist.github.com/chanux/1119556 fish https://gist.github.com/chanux/9411092 https://gist.github.com/chanux/9411092

wombit 12y ago

http://explainshell.com/ http://explainshell.com/

3rd3 12y ago

man hier is pretty cool. It explains the root directory structure of the system.

robert_tweed 12y ago
TIL. As a long-time DOS user that often gets a bit lost on Unix systems I cannot stress how awesome it is to have found out about this!
- jordigh 12y ago
  Wow, DOS users still exist? Which one? FreeDOS? Back in the late 90s when I first moved to Debian from Windows, growing up with a DOS CLI made the transition far easier to me (and having some FTP exposure didn't hurt either).
  - robert_tweed 12y ago
    There's no good way to refer to the entire DOS/Windows command shell lineage without confusion, but that's what I meant. I don't technically use DOS at all anymore. I think "that system" is easier to understand in it's entirety and find your way around than Unix, although it has been getting progressively more complex for years. I actually use OS X most of the time now (plus Linux on servers and Windows for 3D stuff).
    - thinkpad20 12y ago
      > I think [DOS] is easier to understand in it's entirety and find your way around than Unix Yikes, I recently had to do a bit of development on a windows box and I found the command-line tools (not to mention CMD itself, which seems to have stopped development in 1993) to be absolutely awful. I could barely survive without Cygwin, git bash, etc giving me some semblance of a functional shell setup. I guess it's different strokes for different folks.
      - robert_tweed 12y ago

jalanb 12y ago

I notice j.py in that list. I forked that a wee while back, and have been enhancing it ever since: http://www.al-got-rhythm.net/kd/ http://www.al-got-rhythm.net/kd/

grimgrin 12y ago
https://github.com/rupa/z https://github.com/rupa/z is really nice, too. Pure bash.

fauria 12y ago

I would add: TOOLS ... * 'tree' instead of 'ls -R' ...

voltagex_ 12y ago
Which package would that be in?
- chanux 12y ago
  tree on ubuntu
- ejstronge 12y ago
  On Debian/Ubuntu, you can use the `apt-file` package to determine what package a file resides in. For example: apt-file search /bin/tree
- WickyNilliams 12y ago
  `brew install tree` on OSX Also this bash function from Mathias Bynen's famous dotfiles is a fantastic shortcut for colorised (and more) output from tree. https://github.com/mathiasbynens/dotfiles/blob/master/.functions#L240-L246 https://github.com/mathiasbynens/dotfiles/blob/master/.funct...

danielweber 12y ago

> - 'sort | uniq' to check for duplicate lines sort -u

xr09 12y ago

j.py? The original is autojump: https://github.com/joelthelion/autojump/ https://github.com/joelthelion/autojump/

grimgrin 12y ago
z is a nice replacement that is purely written in bash. https://github.com/rupa/z https://github.com/rupa/z

k4rthik 12y ago

I have for cmd in $(compgen -c); do if [[ $cmd =~ ^[0-9a-zA-Z]+$ ]]; then eval "alias $cmd?='man $cmd'"; fi; done in my .bashrc to alias command?=man command, saves some typing to get to man pages ( which I do very often )

grkvlt 12y ago
Wow. I never knew about the `compgen -c` command to show bash command completions. Also from this reference [1] I found these: % compgen -b # built-ins % compgen -k # keywords % compgen -A function # functions % compgen -abckA function # everything [1] http://www.cyberciti.biz/open-source/command-line-hacks/compgen-linux-command/ http://www.cyberciti.biz/open-source/command-line-hacks/comp...
vram22 12y ago
Speaking of man pages, in earlier versions of Unix and Linux, I used to want to redirect the output of many man commands to files for later reading, e.g. if working on C, say I wanted to read 'man ioctl', 'man stdio', 'man signal', etc. But the man output had {n|t}roff formatting characters in it, for print output, which used to mess up vi. So I used to use this script I wrote, called m: # Put this script in a directory in your PATH. # m: pipe man output through col and save to file(s). mkdir -p ~/man # Only creates the dir first time, including all dirs in the path. for name: # in $* is implied man $name | col -bx > ~/man/$name.m done Do a "chmod u+x m" to be able to run it. Then run it like this: m ioctl stdio signal # or any other commands Then: pushd ~/man; view ioctl.m stdio.m signal.m; popd to read those pages, now stripped of formatting characters.
bubblesorting 12y ago
For zsh: for cmd in $(compgen -c); do if [[ $cmd =~ ^[0-9a-zA-Z]+$ ]]; then eval "alias $cmd\?='man $cmd'" ; fi; done # had to escape the ? in the alias name Cool trick :)

AssertFailure 12y ago

Instead of using netcat when tunneling SSH through another machine like this: ProxyCommand ssh -T host1 'nc %h %p' one should use this instead: ProxyCommand ssh -W %h:%p host1

aseidl 12y ago
The only problem with -W is that it is not available everywhere yet: RHEL6 defaults to OpenSSH 5.3, while -W was introduced in 5.4. Thankfully EL7 comes with OpenSSH 6.4 (and a kernel newer than 2.6.32!).

lloeki 12y ago

Instead of ssh -R 12345:localhost:22 server.com "sleep 1000; exit" use ssh -R 12345:localhost:22 -n server.com The -n flag tells ssh to only make a connection, without ever running a shell. This means it even works when you don't have shell access (say, with a command= entry in .authorized_keys). Also, I cannot recommend envoy enough in lieu of ssh-agent, if you're not using a GUI ssh agent already (e.g OSX keychain or GNOME keyring) Last, I guarantee you don't want "$@" in those aliases, but either "$*" or $@ (certainly the latter).

zipperhead 12y ago
I usually visit these threads knowing that I will pick up something useful to add to the toolbox... thank you for 'envoy' - I think it will streamline my ssh key management.
ciupicri 12y ago
I think you meant -N, not -n. From the man page[1]: -N Do not execute a remote command. This is useful for just for‐ warding ports (protocol version 2 only). -n Redirects stdin from /dev/null (actually, prevents reading from stdin). This must be used when ssh is run in the background. [1]: http://www.openbsd.org/cgi-bin/man.cgi?query=ssh&sektion=1 http://www.openbsd.org/cgi-bin/man.cgi?query=ssh&sektion=1

valarauca1 12y ago

Its implied on the list but not mentioned specifically. !! will be substituted with the last command you typed. So if your somebody like me who frequently types $ apt-get update Could not lock yada yada are you root? $ sudo apt-get update instead you can type $ apt-get update $ sudo !!

cheepin 12y ago
What I love about this is that if you up-arrow through your past commands, the "sudo !!" shows up as "sudo apt-get update"
- valarauca1 12y ago
  Bash substitutions are done prior to execution so your history stays intact. Older open source projects are just amazing for how complete their feature set is.
  - pokpokpok 12y ago
    is this how people feel about religious texts?
    - valarauca1 12y ago
      Originally I was gonna write: >Religious texts don't change over time due to community suggested changes. Then I caught myself.
    - carlisle_ 12y ago
      You mean my bash fanaticism isn't religious?
vehementi 12y ago
I named my cat sudo bangbang
a3_nm 12y ago
It always feels more logical to me to just type "Ctrl-P Ctrl-A sudo" (previous history line, beginning of line, add missing sudo) than typing "sudo !!" or "sudo !!<tab>" if you need to edit the substitution. Same thing for the last argument, it's easily edited if you know the right shortcuts: Ctrl-P Alt-B Ctrl-U. (Works for bash, for zsh you need http://stackoverflow.com/q/3483604/414272 http://stackoverflow.com/q/3483604/414272). That said, I didn't know about Alt-.

Tepix 12y ago

Missing trick: In bash, "ESC" then "." fetches the last parameter of the previous command. It's invaluable (same as typing "!$" but you get to see and edit it)

akirk 12y ago
You can get any parameter of the previous command by using "Esc, <number>, Esc, .". If you repeat pressing "Esc, ." you get the n-th parameter from the command before the previous one, etc. More details in this Stackoverflow answer: http://stackoverflow.com/a/4010170/578588 http://stackoverflow.com/a/4010170/578588
lloeki 12y ago
It's actually Meta, emulated by an ESC character by the terminal. OSX tip: check "use Option as Meta" in Terminal's preferences, and you can keep Option pressed while you mash ".".
- akirk 12y ago
  Which is fine if you never need to generate characters using the Option key. For example on a German keyboard you need the Option key to write { or }.
  - lloeki 12y ago
    I'm on a french layout so I know :-) It also has the side effect of "resurrecting" dead keys (which are unrelated to Option), making input of 'ê'and 'ï' impossible. An alternative is using iTerm2 which has a similar setting, liberally applyable to either Option key.
Alupis 12y ago
There are some great tips/tricks in this document. Too bad it's not in Markdown or something easier on the eyes!
- grmarcil 12y ago

scarygliders 12y ago

Another one: Use dcfldd instead of dd if you want to see how far your dd operation is progressing... dcfldd if=[infile] of=[outfile] sizeprobe=if So. Much. Better. dcfldd also has many other useful options - read the man pages - and note that you'll have to install it from your linux distro's package repo beforehand.

sushimako 12y ago
You can also send SIGUSR1 to dd for progress info. From the manpage: Sending a USR1 signal to a running 'dd' process makes it print I/O statistics to standard error and then resume copying. $ dd if=/dev/zero of=/dev/null& pid=$! $ kill -USR1 $pid; sleep 1; kill $pid 18335302+0 records in 18335302+0 records out 9387674624 bytes (9.4 GB) copied, 34.6279 seconds, 271 MB/s
- scarygliders 12y ago
  Indeed you can :) But I prefer not to have to manually keep sending that ;)
  - staticshock 12y ago
    while ; do kill -s USR1 $(pgrep '^dd$'); sleep 5; done
- carlisle_ 12y ago
  On OSX it's SIGINFO (29) in case anybody wondered
  - jamesog 12y ago
    Which you can also get by hitting Ctrl-T. This works for FreeBSD too. (Not sure about the other BSDs.)
    - carlisle_ 12y ago
      neato

o_____________o 12y ago

I was going to write a shell package/snippet manager until I discovered this: https://github.com/ziyaddin/jean https://github.com/ziyaddin/jean It would be nice to get all of these .bash_profile enhancements in as packages. I suppose it could be improved to prompt for a brew/apt install if needed.

wazoox 12y ago

Ctrl+r is fine when you're looking for something recent, but this one is useful when you're looking through a long list of similar commands. alias hist='history | grep' Use it like this: $ hist git 9543 git add toto 9544 git commit 9545 git log 9546 git log 9548 git add -A 9549 git commit 9550 git log 9633 git pull 9955 cd dev/git 9957 git grep copyof 9958 git grep copyof 9959 git pull By the way, do you know you can call back the 9633rd command in the history with "!9633"?

hrrsn 12y ago
Wow, this is great. All too commonly I do cat ~/.bash_history|grep, but this is way easier. Thanks!
WickyNilliams 12y ago
I use this all the time. In fact it was one of the first aliases i made when i switched to a UNIX system. Though I named mine `greph` (for grep history). Absolutely invaluable

jlas 12y ago

Along with the !! function you can reference the last call of a specific command like so: !<cmd> e.g. sometimes I forget the "ln -s" order of arguments (to which it gives me an error), so I follow it up with: ln -s !ln:3 !ln:2

kneth 12y ago

Now and then I reread a chapter of "Classic Shell Scripting" (http://shop.oreilly.com/product/9780596005955.do http://shop.oreilly.com/product/9780596005955.do) - probably the best book on shell script I know.

dorfsmay 12y ago

> In bash, 'ctrl-r' searches your command history No! In emacs ctrl-r searches your command history. It happens that bash use emacs mode by default. All other emacs basic commands work too: ctrl-p, ctrl-n, ctrl-f etc... If you are a vim user, and especially if you love venting how much you hate emacs, then please add this to your bashrc: set -o vi and now you can use vim command instead of emacs.

dllthomas 12y ago
'ctrl-r' is reverse-i-search in vi mode as well.
- dventimi 12y ago
  'ctrl-r' is bound to isearch-backward in my Emacs. 'meta-r' is bound to comint-history-isearch-backward-regexp

dorfsmay 12y ago

> 'htop' instead of 'top' meh, I don't like htop. "atop" on the other hand!!!

marcosscriven 12y ago

A really handy one a colleague showed me yesterday was the /dev/fd/0|1|2 files, which are stdin/out/err respectively. Means you can use that file for utils that expect a file only. E.g echo "This would be contents of file" | someCommand /dev/fd/0

LukeShu 12y ago
These are also available as /dev/std{in,out,err}; the names of which are a little more self documenting :) $ ls -l /dev/fd /dev/std* | column -t lrwxrwxrwx 1 root root 13 Jun 27 16:32 /dev/fd -> /proc/self/fd lrwxrwxrwx 1 root root 15 Jun 27 16:32 /dev/stderr -> /proc/self/fd/2 lrwxrwxrwx 1 root root 15 Jun 27 16:32 /dev/stdin -> /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Jun 27 16:32 /dev/stdout -> /proc/self/fd/1 You can even access the file descriptors of other processes with /proc/${pid}/fd/; which is handy for (say) un-deleting a file that a process still has open. Another handy one is "process substitution" which lets you do the same thing with multiple streams by creating new file descriptors, and automatically turning them into /dev/fd/* paths: someCommand <(echo "contents of file 1") <(echo "contents of file 2") which is somewhat explained by: $ echo someCommand <(echo "contents of file 1") <(echo "contents of file 2") someCommand /dev/fd/63 /dev/fd/62
- toddkaufmann 12y ago
  "process substitution" is one of the new useful things I learned this year (switched to bash from csh over 20 years ago). /proc/${pid}/fd/ is very useful for forensic purposes when you find some malware running that deleted itself and/or config files but still has a handle open to them.

meapix 12y ago

joereggan190 12y ago

http://steamcommunity.com/profiles/76561198143338254 http://steamcommunity.com/profiles/76561198143338254

biftek 12y ago

zsh has a simple builtin `r` (which is just an alias for `fc -e -`). It lets you edit the previous command with search and replace. I use it for brew and git a lot. $ brew info rust $ r fo=stal

Zenst 12y ago

stty - sane Very handy if you do something silly like cat a binary file without piping it into strings -a This restores the terminal settings and sanity restored. Note you will often find yourself typing without seeing anything, least until you enter and execute the sane. Also asvise the following usage ctrl+c a couple of times to clear anything out of the input buffer queued up. stty -sane all good from here onwards and good time to play with od and remember the strings -a pipe next time.

currysausage 12y ago

I found Ctrl-O (execute current command from history and edit the next one) to be invaluable. Ctrl-V: type next input literally (e.g. Ctrl-V [Tab] if you don't want [Tab] to autocomplete). Alt-#: Prefix current line with "#" (don't execute it) and put it into history for later use. I'm sometimes surprised how many people don't know these: Ctrl-U/K: kill line before/after cursor.

agumonkey 12y ago

I used to be excited about this, now I found it shallow. Better unix tip => http://www.confreaks.com/videos/615-cascadiaruby2011-the-unix-chainsaw http://www.confreaks.com/videos/615-cascadiaruby2011-the-uni...

WickyNilliams 12y ago

A personal favourite of mine is aliasing common cd operations. alias ..="cd .." alias ...="cd ../.." # etc and of course `cd -` to jump to previous directory

andrey-p 12y ago

I love these, there's too much to process but I always get to learn at least one ridiculously useful thing. Today's was vim's `:set spell`.

gowan 12y ago

Send a command to display 1. `xterm -display :1 -e <command>` This is useful when running automated tests on top of vnc.

pmontra 12y ago

I suggest bashmarks http://www.huyng.com/projects/bashmarks/ http://www.huyng.com/projects/bashmarks/ to bookmark directories and jump there with a quick command. I also like to alias ..="cd .." and alias ...="cd ../.." to quickly navigate up.

thln666 12y ago

"- Compile your own version of 'screen' from the git sources. Most versions have a slow scrolling on a vertical split or even no vertical split at all" Or you could just use tmux which afaict is superior to screen in almost every way. http://tmux.sourceforge.net/ http://tmux.sourceforge.net/

joereggan190 12y ago

http://learn.hightail.com/t5/Ideas/UFC-175-Live-Stream-Watch-UFC-175-Weidman-vs-Machida-Live-Stream/idi-p/74016 http://learn.hightail.com/t5/Ideas/UFC-175-Live-Stream-Watch...

joereggan190 12y ago

UFC 175 Weidman vs Machida Live Stream http://learn.hightail.com/t5/Ideas/UFC-175-Live-Stream-Watch-UFC-175-Weidman-vs-Machida-Live-Stream/idi-p/74016 http://learn.hightail.com/t5/Ideas/UFC-175-Live-Stream-Watch...

aceperry 12y ago

>Don't know where to start? SMB is usually better than NFS for most cases. Not sure why he feels SMB is better, because in my experience, NFS usually works more smoothly and is easier to setup than SMB. But then, I don't usually use windows.