Search Results

Not sure why this got downmodded to oblivion, but anyway. grep "[a-zA-Z]" grep is a search tool, using regular expressions. This specific expression looks for a character range (in brackets) of …

We have two environments here at work, and I access the remote machine over ssh. I can do this: kioexec myeditor fish://me@remotemachine/path/to/file.txt But I'd like to be able to do a diff betwee …

If it is a normal sequence you can do this: in bash: for ITER in {1..50} do cat test${ITER}.xml cat test${ITER}.msg done > test.txt or if you have the utility seq for ITER in $(seq 1 50) …

How did you edit it? I would do: echo 1 > /proc/self/make-it-fail These 'files' in proc are not like files on disks. The 'file' is pure code, using open and read/write as interfaces to the kernel. …

The shell is normalizing the path. … /etc" grep chdir /tmp/strace.out # will give chdir("/etc") The shell does the path normalization before it even tells the system to change the dir …

The command is always fork'ed and exec'ed, but normal shell behavior is to wait on the command until it exits. … If you want this to continue even if you close the shell process, you can use the nohup command to make them ignore this signal and keep running. …

To update an old question.... The best I've done so far is to get around this problem a different way. Namely FUSE + sshfs does what I want, and more.

My first instinct is to isolate the user portion (using grep -o). The good thing about it is that it has some (relatively) unique marking - the brackets. So, the grep below isolates the (two) fields …

In most shells the last parameter you gave on the previous command is in $_ mkdir /some/dir cd $_ # now in /some/dir

The first shell was Bourne shell. It was very cool, but it had some serious limitations. … Dave Korn (nice guy) created a new shell called... Korn shell. It followed the programming model that Bourne shell created (arguably superior to the csh model). …

most unixes have pkill, which kills a process based on name Try: pkill my_program /usr/bin/time my_program sleep 5 pkill -TERM my_program Also, don't kill with -9. It doesn't allow cleanup.

I like Macs, and it does give a good (BSD) UNIX experience but strictly on getting a Linux experience on your PC, I feel there are better alternatives. I personally use Cygwin on any Windows machine …

The du answers above are closer to what you want, but you might also want to try out kdirstat. Its a cool gui tool that shows all your dirs, what's in them, what the content is, and has various tools …

Typing ls -G would work in any shell, though a shell (like bash) that has aliases makes it easier. …

This isn't multiple standard input. This is a bash'ism that called 'Process Substitution' http://tldp.org/LDP/abs/html/process-sub.html It creates a pseudo file (/dev/fd/something) for each substi …