gfx-next update: drm-4.8-rc2 tagged in drm-next

[Bob Willcox]

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 at immure.com | romantic love you want the other person.
Austin, TX     |     -- Margaret Anderson