🚀 go-pugleaf

In article <1h7lrmINNpde@aludra.usc.edu> aliu@aludra.usc.edu (Alex Liu) writes:
>Hi,
>  I think what some people are missing is what is the idea of pipes.
>Under Unix, the concept of Pipes comes from the idea of linking small
>prewritten utilities to get something done as opposed to writing a
>entirely new application.
>
.... explanation of KISS re: unix tools deleted

I missed the beginning of the thread, but I haven't seen anyone mention
daemons, named pipe services, sockets, and other IPC type applications
of multiprocessing. DOS/Windows does limited IPC, NT will probably do
it robustly (Dave Cutler knows how to design robust OS's even if
Bill Gates is clueless).

Unix allows several different flavors of multitasking, multiple processes
launched from a single command line is one flavor, and is probably the
most visible to the user. Multiple command lines is another user-oriented
flavor, whether the additional commands are put into background or are
running in a different console window. 

Then there are the programs that run essentially in background doing
nothing but waiting for input, these are database servers, network
daemons, cron, etc. These programs do essentially what TSR's do for DOS,
but take advantage of the multitasking features of Unix to continue
processing while other work is being done on the same system.

All of this is common knowledge for most of the readers here. For those
folks that haven't used a true multitasking system long enough to find
it's usefulnes, it's difficult to envision just how convenient multitasking
is. Like any tool more complex than a hammer, tho, it does take time to
learn to use efficiently.

Alan Davis                      aur : davis@aurfs1
Alcatel Network Systems         BIX : adavis
adavis@rockdal.aud.alcatel.com  CIS : 72317,3661