SoloCDM wrote:
> I recognize the following documentation from man bash, but it's not
> clear just how high you can numerically climb, exactly how the
> ampersand qualifies, or how does one determine what numeral level is
> placed in the given position based on the given qualifiers. Do you
> understand what direction and approach I'm taking?
I do now.
think that you have
1) stdout
2) stderr
and how can you combine them
I think there's no such thing as 5&>
basically you can
redirect stdout to a file: echo Hi > file
redirect stderr to a file: grep * 2> file
redirect stdout to a stderr grep * 1>&2
redirect stderr to a stdout grep * 2>&1
redirect stderr and stdout to a file: echo hi > file 2>&1 or grep * &> file
redirect stderr and stdout to stdout see stderr 2 stdout
redirect stderr and stdout to stderr see stdout 2 stderr
1 'represents' stdout and 2 stderr
>
> *********************************************************************
> Signed,
> SoloCDM
>
> ___________________________Reply_Separator___________________________
>
> Mike G wrote:
> >
> > REDIRECTION
> > Before a command is executed, its input and output may be
> > redirected using a special notation
> > interpreted by the shell. Redirection may also be used to open and
> > close files for the current
> > shell execution environment. The following redirection operators may
> > precede or appear anywhere
> > within a simple command or may follow a command. Redirections are
> > processed in the order they
> > appear, from left to right.
> >
> > In the following descriptions, if the file descriptor number is
> > omitted, and the first character
> > of the redirection operator is <, the redirection refers to the
> > standard input (file descriptor
> > 0). If the first character of the redirection operator is >, the
> > redirection refers to the
> > standard output (file descriptor 1).
> >
> > The word that follows the redirection operator in the following
> > descriptions is subjected to
> > brace expansion, tilde expansion, parameter expansion, command
> > substitution, arithmetic expan
> > sion, quote removal, and pathname expansion. If it expands to more
> > than one word, bash reports
> > an error.
> >
> > Note that the order of redirections is significant. For example, the
> > command
> >
> > ls > dirlist 2>&1
> >
> > directs both standard output and standard error to the file dirlist,
> > while the command
> >
> > ls 2>&1 > dirlist
> >
> > from man bash
> >
> > SoloCDM wrote:
> >
> > > Mike G wrote:
> > > >
> > > > SoloCDM wrote:
> > > >
> > > > > Mike G wrote:
> > > > > >
> > > > > > SoloCDM wrote:
> > > > > >
> > > > > > > Is there a more definitive explanation for redirecting in bash?
> > > > > >
> > > > > > more than ... ?
> > > > > > more than man bash?
> > > > >
> > > > > More than Linux documentation.
> > > >
> > > > there's learning bash from O'reilly,
> > > > but I'm curious, is there any thing you want to do with redirection that
> > > > is not covered in std doc?
> > >
> > > I'm not clear on anything associated with the numbers and ampersand
> > > used with the left and right arrows "<>".
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
