At 10:50 AM 11/28/1999 +0000, pippi wrote:
> This is a bread+butter operation for Linux. For TCP/IP
> networks, it takes just two ifconfig commands and
> couple of route commands.
>
> Cheers,
> Steven
> If I do stumble on a
> command to edit something I can't get out of the editor except by manual
> reboot.
Try the Pico editor. It is pretty simple and it explains the commands at
the bottom of the screen.
> Why hasn't someone written a guide that compares linux for M$
> users??
Actually, such a book would be pretty easy to write, since basic
file system commands are quite similar, for instance:
DOS Unix (most shells)
list files and directories dir ls (list)
rename file rename mv
move a file move mv
copy a file copy cp
delete a file del rm (remove)
change directory cd cd
find text in a file find grep (get regular expression)
sort lines of file sort sort
print a file print lpr (line printer)
display file 1 page at a
time more more
display contents of file type cat (contatenate)
I good readable book on Unix, which also applies to Linux is:
Introducing the Unix System, Henry, McGilton and Rachel Morgan,
McGraw-Hill, 1983
> I have study linux in 24 hours but cannot
> carry out basic lessons because -----
> I've seen this in a few
> manuals, neglecting basic instructions such as how to find a directory, how
> to open/close applications and files, how to install/remove applications
> and files, etc. If DOS instructions were this arcane everyone would have
> to use Macs!
I worked for Sun MicroSystems once, updating their Unix on-line ``man''
(help) pages. User documents for Unix have traditionally assumed a
``user'' was some kind of programmer who already knew a lot about the
very operating system being described. And Unix commands often had
undocumented features and obscurely described switches that created
Unix ``gurus'' who were valued experts on a particular command (e.g.,
sed or troff) or aspect of unix. It was historically a ``geek'' OS,
where people took great pride in discovering things that other people
did not know.
All this can be repaired with some easy by documentation targeting an
ordinary, intelligent user, and a little redoing of names, and switches -
etc. to make things more intuitive.
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
