Date: Thu, 29 Sep 2016 19:41:39 -0500 From: Bob Willcox <bob@immure.com> To: Pete Wright <pete@nomadlogic.org> Cc: freebsd-x11@freebsd.org Subject: Re: gfx-next update: drm-4.8-rc2 tagged in drm-next Message-ID: <20160930004139.GX845@rancor.immure.com> In-Reply-To: <20160929131751.GW845@rancor.immure.com> References: <20160920212545.GU8480@rancor.immure.com> <d93f0a38-f2c1-ff61-a1db-6efad39c1ffd@nomadlogic.org> <20160920221954.GV8480@rancor.immure.com> <20160921233610.GI845@rancor.immure.com> <9582349b-cf1e-1d75-4784-a1d712aedac4@nomadlogic.org> <1574f2fb8aa.e60df17234511.2445927962639207447@nextbsd.org> <20160923122301.GK845@rancor.immure.com> <20160929014049.GV845@rancor.immure.com> <3d7950a2-0312-0a17-cce5-9eece2430daa@nomadlogic.org> <20160929131751.GW845@rancor.immure.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 29, 2016 at 08:17:52AM -0500, Bob Willcox wrote: > > Since I didn't have an xorg.conf file, I created one (via 'Xorg -configure') > which got me past the problem with the intel driver. However I still couldn't > get X to start. So I then started scrutinizing my .xinitrc file and I > discovered two things that appear to have been causing problems. > > First was that I was setting 'DISPLAY=$HOSTNM:0.0' where $HOSTNM was the first > element of the system's host name and the second was that my old .xinitrc file > didn't have this line at the end: > > exec xterm -geometry 80x66+0+0 -name login > > as the xinitrc file in /usr/local/etc/X11/xinit does. > > I have no problem removing the DISPLAY variable setting (I have no memory of > why I had it there...that was YEARS ago that I did it), but the exec'ing of > the xterm bothers me. I don't understand why it's now required, and I can't > say that I like it (if I exit the xterm X terminates, most annoying). > > Any ideas why this is now needed and if there is a way to get rid of it? > > Thanks, > Bob Ok, I discovered what was causing me to need the exec of the xterm. I was, for some reason (another many year old thing), backgrounding the invocation of the window manager and this was the culprit. Removing the '&' and no longer backgrounding it removed the need for the exec'ing of the xterm. Sorry for the bother...guess my stuff is so old I don't remember why I did it and it is now a bad idea. -- Bob Willcox | In real love you want the other person's good. In bob@immure.com | romantic love you want the other person. Austin, TX | -- Margaret Anderson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160930004139.GX845>