here are some quick commands, play with them (careful with
umount, and mount)
# cp - copy files (like DOS copy)
# ls - list files (like DOS dir)
# rm - delete files (like DOS del)
# rmdir - delete directory/folder (like DOS rd/rmdir)
# mkdir - create a directory/folder (like DOS md/mkdir)
# cd - change directory
# mount - add a disk device to the system
# umount - remove a disk device
# pico - a cute text editor
# emacs - a more advanced text editor
# pine - a mail program
# lynx - a text based browser
# ping - used to test connections
# gcc - built in c compiler!!!!
and for a really nice shell type
# bash (you can use [backspace]! no ^H, and you can type [tab] to auto-complete
filenames)
if you need more information about a command type # man [commandname] type the
command name and add -? to it, like # cp -? this is by NO MEANS a complete
list. Most people that use UNIX have to keep a command book by thier side
(like me). I'm sure there are 1,000,000 web sites with unix commands, just do a
search.
UNIX is all about editing script files. Everything in UNIX (luckily for editing
purposes) is in a text files. You just have to know what files to edit to get
the system to do what you want.
DONT USE SPACES IN UNIX FILENAMES! The system will allow it, but it will be a
hassle to read it again. Remeber the UNIX token parser (like most parsers) is a
space between tokens. eg. # cp filename \bin\newfile will copy filename to the
directory \bin under the name newfile. If you type the following: # cp file name
\bin\file name, it will confuse the parser and it will give an error (it thinks
that "file" is being copied to "name", and there are two extra, erorrnus
parameters: "\bin\file" and "name". You can get around it by using quotes on
newer systems (# cp "file name" "\bin\file name"), but some older systems don't
support it, so don't do it! Use "_" (underscore) instead
