<P> In most Unix - like systems, all processes of a pipeline are started at the same time, with their streams appropriately connected, and managed by the scheduler together with all other processes running on the machine . An important aspect of this, setting Unix pipes apart from other pipe implementations, is the concept of buffering: for example a sending program may produce 5000 bytes per second, and a receiving program may only be able to accept 100 bytes per second, but no data is lost . Instead, the output of the sending program is held in the buffer . When the receiving program is ready to read data, then next program in the pipeline reads from the buffer . In Linux, the size of the buffer is 65536 bytes (64KB). An open source third - party filter called bfr is available to provide larger buffers if required . </P> <P> Tools like netcat and socat can connect pipes to TCP / IP sockets . </P> <P> The pipeline concept was invented by Douglas McIlroy and first described in the man pages of Version 3 Unix . McIlroy noticed that much of the time command shells passed the output file from one program as input to another . </P> <P> His ideas were implemented in 1973 when ("in one feverish night", wrote McIlroy) Ken Thompson added the pipe () system call and pipes to the shell and several utilities in Version 3 Unix . "The next day", McIlroy continued, "saw an unforgettable orgy of one - liners as everybody joined in the excitement of plumbing ." McIlroy also credits Thompson with the notation, which greatly simplified the description of pipe syntax in Version 4 . The idea was eventually ported to other operating systems, such as DOS, OS / 2, Microsoft Windows, and BeOS, often with the same notation . </P>

Is it possible to create new file system in unix