Skip site navigation (1)Skip section navigation (2)
Date:      22 Aug 2002 16:12:28 +0000
From:      Josh Paetzel <friar_josh@webwarrior.net>
To:        anderson@centtech.com
Cc:        freebsd-doc@freebsd.org
Subject:   Re: docs/41865: [PATCH] XFree86 section should document -nolisten	tcp option in startx
Message-ID:  <1030032756.268.0.camel@markx.vladsempire.net>
In-Reply-To: <3D64F0F2.7080304@centtech.com>
References:  <200208221240.g7MCe7eB007052@freefall.freebsd.org>	<3D64E095.6050001@centtec h.com>	<1030005394.226.23.camel@markx.vladsempire.net> <3D64EBE5.5090501@centtech.com> <1030006504.226.27.camel@markx.vladsempire.net>  <3D64F0F2.7080304@centtech.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2002-08-22 at 14:10, Eric Anderson wrote:
> Josh Paetzel wrote:
> 
> > On Thu, 2002-08-22 at 13:49, Eric Anderson wrote:
> > 
> >>I don't recall ever seeing it in 4.5-RELEASE.  Only with XFree86 4.x have I seen 
> >>it (on FreeBSD).  4.5-RELEASE defaulted to XFree86 3.3.6, and never had the 
> >>problem unless you installed XFree86 4.x over it.
> >>
> >>I missed the documentation on that, my bad.  However, when you do an upgrade 
> >>(binary) of a box, and something like remote X displays stop working, the first 
> >>thing that crosses your mind is "something is broken", not "I should check the 
> >>man pages for XFree86, startx, xinit, [insert your wm here], [insert your 
> >>favorite remote shell program (ie. ssh, rsh, telnet, etc) here], etc".  I hit 
> >>this problem a long time ago putting XFree86 4.2 on a 4.5-RELEASE machine, so it 
> >>seemed like nothing to me.  Only until yesterday when I received a few emails 
> >>from friends (who now use FreeBSD like it's a drug) asking how to fix it, did it 
> >>occur to me that there should be more docs on it - they checked the handbook, 
> >>FAQ, and a few newsgroups - with no good answers.
> >>
> >>Eric
> >>
> > 
> > Top posting makes mail threads hard to follow.
> > 
> > I agree with you completely, but my point still stands.  The issue is
> > with what version of XFree86 you are running.  It's not really tied to
> > what version of FreeBSD you are running very tightly.  If you are going
> > to make a FAQ entry you should include the version numbers of X where
> > the change occured.
> > 
> > Josh
> 
> 
> Right, that is the issue, but since FreeBSD 4.6-RELEASE and newer all come with 
> XFree86 4.x as the default X install now, and an upgrade makes the problem 
> appear, then it is tied to FreeBSD, although not completely.
> 
> If all you're trying to say is "hey, add the versions of XFree86 in the diff", 
> then submit a quick followup to the PR, or I can.
> 
> Eric
> 
That's all I'm trying to say.  You can doctor up the patch the way you
want it.  I think we are completely on the same page.

Josh




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1030032756.268.0.camel>