From owner-freebsd-stable@FreeBSD.ORG Fri Jul 4 21:13:25 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5BC8B3EE for ; Fri, 4 Jul 2014 21:13:25 +0000 (UTC) Received: from mta1.riverwillow.net.au (mta1.riverwillow.net.au [IPv6:2001:8000:1000:1801::36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mta1.riverwillow.net.au", Issuer "Riverwillow Root Certificate 2010-04-12" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A5895232A for ; Fri, 4 Jul 2014 21:13:24 +0000 (UTC) Received: from mail1.riverwillow.net.au (mail1.riverwillow.net.au [IPv6:2001:8000:1000:1801::46]) by mta1.riverwillow.net.au (8.14.9/8.14.9) with ESMTP id s64LDIu5066937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 5 Jul 2014 07:13:19 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=mta1002; t=1404508399; bh=Ko7NgJdtKAfmrYL4ssRfLQZkn3YKnZRPpjMNHahCyRw=; h=Date:From:To:Subject:References:In-Reply-To; b=KTsuXXOzeke/R2vb7QhPz5t1N9bccctUs6y1msCzbOoodTiQ+qllJX6il32dNAMhO 78ZI2bC+1Y7uvHVWkkuxmWSLNtPDVJPsiTDgKKH2jmBh8MQxeP+9/CxW/S+70LJgLz 1cLBEXnMHb7C+7zasWVSfXnEYlFQp4AbuQWvZ5/4= Received: from rwpc15.gfn.riverwillow.net.au (rwpc15.gfn.riverwillow.net.au [IPv6:2001:8000:1000:18e1:20c:76ff:fe0a:2117]) (authenticated bits=56) by mail1.riverwillow.net.au (8.14.9/8.14.9) with ESMTP id s64LDFM9066936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 5 Jul 2014 07:13:17 +1000 (AEST) Date: Sat, 5 Jul 2014 07:13:12 +1000 From: John Marshall To: freebsd-stable@freebsd.org Subject: Re: Should 9.3 carry a warning about NEW_XORG Message-ID: <20140704211311.GA7680@rwpc15.gfn.riverwillow.net.au> Mail-Followup-To: freebsd-stable@freebsd.org References: <53B69B88.4060803@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline In-Reply-To: <53B69B88.4060803@gmail.com> OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2014 21:13:25 -0000 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 04 Jul 2014, 14:18 +0200, Piotr Kubaj wrote: > On 07/04/2014 14:00, freebsd-stable-request@freebsd.org wrote: > There's not POLA as vt(4) has been merged to stable/9 and stable/10 to > make it possible to use tty. To use new Xorg with tty, recompile kernel > using VT config. Right, it cannot be construed as POLA violation for stable/9 or stable/10; but we're talking about a -RELEASE branch. Is it appropriate for a -RELEASE branch user doing a point release upgrade within a major version to have NEW_XORG build without warning (and not work) following the OS upgrade? The intention of ports r351411 appears to be to make NEW_XORG the default on stable/9 and stable/10 while leaving old XORG the default on the 9 and 10 -RELEASE branches. We have just branched releng/9.3 from stable/9, so it has picked up the "opt out" behaviour from stable - opposite to the "opt in" behaviour of the releng branches. Although the conditional processing happens in the ports infrastructure it impacts user experience of this release FOR USERS OF X. vt(4) is not even mentioned in GENERIC or NOTES but a VT config file is lurking in the release. sc(4) and vga(4) are still in GENERIC and GENERIC states that syscons(4) is the default console driver. I didn't come across anything that warned me that a ports upgrade following the OS upgrade would break X. --=20 John Marshall --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlO3GOcACgkQw/tAaKKahKLYuQCgsXvpbxct4mELpagLGR8z7jL7 Q1sAnRTZHrkndyWphvdu+7hTVZjGwRfu =mUlc -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy--