From owner-freebsd-questions Mon Mar 4 22:16:32 2002 Delivered-To: freebsd-questions@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 5B10F37B400; Mon, 4 Mar 2002 22:16:27 -0800 (PST) Received: from dialup-166.90.70.85.dial1.chicago1.level3.net ([166.90.70.85] helo=there) by albatross.prod.itd.earthlink.net with smtp (Exim 3.33 #1) id 16i8FN-0005yK-00; Mon, 04 Mar 2002 22:16:25 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Bob Giesen To: Peter Ulrich Kruppa , Greg Lehey Subject: Re: Cannot change X screen resolution Date: Tue, 5 Mar 2002 00:15:51 -0600 X-Mailer: KMail [version 1.3] Cc: References: <20020305061845.E203-100000@pukruppa.de> In-Reply-To: <20020305061845.E203-100000@pukruppa.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday 05 March 2002 12:27 am, Peter Ulrich Kruppa wrote: > On Tue, 5 Mar 2002, Greg Lehey wrote: > > On Monday, 4 March 2002 at 20:06:55 +0000, Peter Ulrich Kruppa wrote: > > > Hi, > > > > > > I just installed the latest XFree86-4 port on my -STABLE > > > machine. Now I can't change the screen resolution by typing > > > + + ( or ) > > > anymore - which was quite a helpful feature, because I am > > > little bit short-sighted. > > > > > > I am using the same XF86Config as before. > > > > There has been a format change since 3.3.6. Are you sure it's > > really using the same config file? > > Actually I did not upgrade from 3.3.6 but from some Xfree86-4 > (perhaps 3 or 4 months old - Zoom worked with that one). > So indeed I use the same config file. > > > > Any idea how I can restore this "zoom" feature? > > > > 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." Still, this command will not log error output. See my earlier message for details. Bob -- "I never think of the future. It comes soon enough." -- Albert Einstein (1879-1955) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message