Windows command mode looks a lot like:
Linux and Unix...
- Yes, but it also looks like MS-DOS.
- Many Linux/Unix commands work directly: mkdir, rmdir, cd, at, kill, more
- TCP/IP commands work exactly the same: ftp, telnet, finger, ping
- Pipes ( | ) and redirects (<, <<, >, >>) do just what they do in
Unix
But at times, Windows is just different enough from
Linux/Unix to be annoying.
In the arbitrary category:
- \path instead of /path
- /flag instead of -flag
- nmake 1> mlog
2> errorlog instead of
make >& mlog
- doskey listdir = dir
/OD instead of
alias listdir ls -lt
- & instead
of ;
In the matter-of-taste category:
- dir instead of ls
- erase or
del instead of rm
- wordpad
or notepad instead of vi
or emacs (both of these are available)
- TAB key* instead of
ESC key (command completion)
*The systems group has set up the TAB key as the way to complete commands on the
login nodes. See Microsoft's Windows Server 2003 Resource Kit Registry Reference
for directions on setting up your own Windows machine.
In the spell-it-out category:
- copy instead of cp
- move instead
of mv
In the more-sensible category:
- type instead of cat
- find instead
of grep
In the more-complicated category is "history":
- right click the title bar on command prompt window >
properties > options instead of
set history =
NN
- F7 function key
instead of history
- up and down arrows* instead of
!!
- F7 > use arrows to highlight desired command > "enter"
instead of !N
*using the up and down arrows moves the current command history to the command last
repeated. Using F7 to pop up the history list does not change the list.
Most of the Linux/Unix commands listed above will work on the login nodes, if you uncomment
the line
-
REM call setup_cygwin.bat
in your userlogin.bat located at H:\users\your_userid. This will add the Cygwin
directory containing many Unix type commands to the head of your path (but will
not put you in the Cygwin environment.)
