sfk ftpserv -rw

… and enjoy your zero-install, ultra-portable ftp server!

dir | clip – copies the output of the dir command to the clipboard
clip < example.txt – copy the contents of the file example.txt to the clipboard

RESTORE DATABASE MyDatabase
FROM DISK = 'd:\backup\MyDatabase.bak'

It’s that simple.
Thanks to Michael Otey @ SQL Server Magazine.

• are free/open source,
• create checksums for multiple files,
• export checksums to a file,
• and verify md5 sums from a list of files.

In short: if you need a very good tool, then use the Swiss File Knife (sfk).

For creating checksums for all your files in the current directory and storing the individual checksums in checksum.md5, execute this:

sfk md5gento checksum.md5 .

And for validating the checksums of all files in the current directory, execute this:

sfk md5check checksum.md5

That’s it

Whether you are looking for a handy summary to carry around, or a help to get started quickly – this is what you are looking for.

*snip*

Command Chaining:

TO run a -> b -> c

ls -lF /etc; pwd;who;ps

Logical ANDing:

Program b will execute only if program a was executed
a&&b&&c

Programs run mutually inclusive
Returns a exit status 0 and then run b exit status 0 and then run C

Logical ANDing – runs subsequent based on exit status of 0

ls -l /etc/resolv.conf && grep name /etc/resolv.conf

Logical ORing:

Run subsequent program based on failure of previous

ls -l /etc/resolve.conf || grep name /etc/resolv.conf

Example:

If the file text.txt doesnt exist you can create with ORing

ls -l test.txt || touch test.txt

Combining ANDing ORing

-bash-3.00$ ls -l text.txt || touch test.txt && ls -ltr test.txt
text.txt: No such file or directory
-rw-r--r-- 1 carlosap other 0 Aug 22 00:13 test.txt


BASH for LOOPS

text.txt
1
2
3

LOOPS SYNTAX:
for variable in list; do command variable; done


-bash-3.00$ for i in `cat test.txt`; do echo $i; done
1
2
3
-bash-3.00$ for i in `cat test.txt`; do echo test$i; done
test1
test2
test3

*snap*

However, I found these default settings with quite useful:

Window -> Appearance -> Font: Courier New or Lucida Console
Window -> Translation -> Character Set: UTF-8
Window ->Translation -> Line Drawing: Use Unicode Line drawing code points

There are quite a few file managers out there that allow you to work with remote file systems over SSH. My favourite is Midnight Commander, which is included in most Linux distributions out there. Just start it on your local machine (type mc in your terminal), select the menu “Left”, and click on “Shell link…”. Dialog will come up, enter your login details here, just as you would when using ssh (e.g. “user...@example.com”). You will be asked for your password, and voila – there you are!

Now you can browse the remote server on the left, and your local server on the right. Copying files back and forth should be no problem.

If you are looking for a better visual experience you might want to try muCommander.

Currently I am using vi most of the time, but that’s just because I am playing with equipment that is running BusyBox now and then. I guess you are not surprised that I am telling you that using vi is not  very hard.

Enough chatting, let’s get our hands dirty!
There are hundreds of vi cheat sheets and tutorials out there. But let’s keep this one simple

You might know that vi is all about modes. In other words, you can either view the text or edit it – no further magic.
These are the most basic commands you need to know when using vi:
vi somefile.txt – start vi and open the file somefile.txt
i – enter the edit mode (“Insert”)
<ESC> – pressing the escape key ends the editing mode and sends you back to read-only
u – revert your last changes (“Undo”)
:w – save the file (“Write”)
:q – exit vi (“Quit”)

So you can open, edit and save files. This might not look like much, but these 5 basic commands are nearly all you need.


#!/usr/bin/ksh
#
# PCP (PID con Port)
# v1.07 20/05/2008 s...@unix.ms
#
# If you have a Solaris 8, 9 or 10 box and you can't
# install lsof, try this. It maps PIDS to ports and vice versa.
# It also shows you which peers are connected on which port.
# Wildcards are accepted for -p and -P options.
#
# The script borrows from Eric Steed's excellent "getport.sh" script.
#
#
if [ $# -lt 1 ]
then
echo >&2 "usage: $0 [-p PORT] [-P PID] [-a ALL ] (Wildcards OK)"
exit 1
fi
while getopts :p:P:a opt
do
case "${opt}" in
p ) port=${OPTARG};;
P ) pid=${OPTARG};;
a ) all=all;;
[?]) # unknown flag
echo >&2 "usage: $0 [-p PORT] [-P PID] [-a ALL ] (Wildcards OK) "
exit 1;;
esac
done
shift `expr $OPTIND - 1`
if [ $port ]
then
# Enter the port number, get the PID
#
port=${OPTARG}
echo "PID\tProcess Name and Port"
echo "_________________________________________________________"
for proc in `ptree -a | grep -v ptree | awk '{print $1};'`
do
result=`pfiles $proc 2> /dev/null| grep "port: $port"`
if [ ! -z "$result" ]
then
program=`ps -fo comm -p $proc | tail -1`
echo "$proc\t$program\t$port\n$result"
echo "_________________________________________________________"
fi
done
elif [ $pid ]
then
# Enter the PID, get the port
#
pid=$OPTARG
# Print out the information
echo "PID\tProcess Name and Port"
echo "_________________________________________________________"
for proc in `ptree -a | grep -v ptree | grep $pid| awk '{print $1};'`
do
result=`pfiles $proc 2> /dev/null| grep port:`
if [ ! -z "$result" ]
then
program=`ps -fo comm -p $pid | tail -1`
echo "$proc\t$program\n$result"
echo "_________________________________________________________"
fi
done
elif [ $all ]
then
# Show all PIDs, Ports and Peers
#
echo "PID\tProcess Name and Port"
echo "_________________________________________________________"
for pid in `ptree -a | grep -v ptree |sort -n | awk '{print $1};'`
do
out=`pfiles $pid 2>/dev/null| grep "port:"`
if [ ! -z "$out" ]
then
name=`ps -fo comm -p $pid | tail -1`
echo "$pid\t$name\n$out"
echo "_________________________________________________________"
fi
done
fi
exit 0

Found at unix.ms.