> Input redirection is symbolized by the < character. Output is the >
> character, and output with append uses the >> characters.
That's like DOS (except that MORE < FILE doesn't seem to work).
> $ echo this | thisfile
> -ksh: thisfile: cannot execute [Permission denied]
KSH? Korn Shell?
> This is a redundant operation. It would win the "useless use of cat" award
How about ls | cat | cat ? That's even worse!
> $ echo this that other > wc -w
> $ cat wc
> this that other -w
> $
>
> Our words were not counted, they were redirected into a file which has
> the filename wc.
>
> But how did that -w get in there? Ahhh, but that is the subject of a later
> lesson!
Weird... I want to know!
> Errata: it IS possible to pipe to a file. How? Because (as we saw in the
> last lesson) a file can become a command.
And what about piping STDERR?
> But piping to a user-created command is an advanced technique, and we
> aren't going to explore that right away.
I wrote a DOS program that would accept piped input (STDIN, I
believe...) and display it to a graphics mode using a custom font. It
locked up since I didn't know when to stop taking input! There is some
character to flag the end, but I am unsure....
But that was DOS. We're talking UNIX here.
