Erik Price wrote:
> Does the code that tells the reader or writer to block have to be
> written into the application, or is that somehow built into the shell?
It's probably best to think of this behavior as built in, provided by the OS.
The shell just provides a convenient and easy-to-use synt
On Wed, Dec 11, 2002 at 10:41:52PM -0500, Erik Price <[EMAIL PROTECTED]> wrote:
> Does the code that tells the reader or writer to block have to be
> written into the application, or is that somehow built into the shell?
> If it needs to be built into the application, well then say for
> instan
On Wednesday, December 11, 2002, at 07:00 PM, [EMAIL PROTECTED]
wrote:
An ordinary redirection opens a file descriptor with regular file
semantics.
Some shells implement "process" redirection which is similar to a pipe.
The main difference between pipe file descriptors and "file" file
descri
> Is there a difference between piping something into another
> utility and using the "<" redirection operator to send data
> to it?
An ordinary redirection opens a file descriptor with regular file semantics.
Some shells implement "process" redirection which is similar to a pipe.
The main diffe
On Wed, 11 Dec 2002, Price, Erik wrote:
> Is there a difference between piping something into another utility and
> using the "<" redirection operator to send data to it?
As I understand it, piping ("|") redirects the standard output of one app
into the standard input of another app; the "<" oper
Is there a difference between piping something into another
utility and using the "<" redirection operator to send data
to it?
Erik
___
gnhlug-discuss mailing list
[EMAIL PROTECTED]
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss