Date: Wed, 6 Mar 2002 19:58:22 -0500 From: parv <parv_@yahoo.com> To: Peter Leftwich <Hostmaster@Video2Video.Com> Cc: FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Cannot change X screen resolution [tcsh?] Message-ID: <20020307005822.GA11742@moo.holy.cow> In-Reply-To: <20020306173122.G97469-100000@earl-grey.cloud9.net> References: <E16i8FN-0005yK-00@albatross.prod.itd.earthlink.net> <20020306173122.G97469-100000@earl-grey.cloud9.net>
next in thread | previous in thread | raw e-mail | index | archive | help
in message <20020306173122.G97469-100000@earl-grey.cloud9.net>,
wrote Peter Leftwich thusly...
>
> On Tue, 5 Mar 2002, Bob Giesen wrote:
> > > > Capture the output of the X startup and check the messages.
> > > I tried
> > > # startx 2 > & 1 > /var/tmp/startuplog
> > > and get
> > > Ambiguous output redirect.
>
> > It's ambiguous because of the space you have after the ampersand
> > ("&"). The shell is trying to run the command "startx 2 >" in
> > the background. (It is ambiguous in that you're beginning to
> > redirect the stderr output without telling the shell where you
> > want it to go...) You must not have a space between the
> > ampersand and the "1."
>
> Isn't this discussion about 2> and &1 etc. shell-dependent (tcsh)?
why, yes. apparently tcsh(1) loathes "2>&1" redirection, prefers
instead ">&". in addition, it also doesn't care about the spaces
between ">" and "&". even when "l s >& p " is entered, histrory
shows the command to be "l s > & p".
so, if you haven't already figured it out, try this (in tcsh)...
# startx >& log
...no wonder that you got the "ambiguous output redirect" message if
you were using tcsh.
- parv
--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020307005822.GA11742>