Date: Mon, 7 Jul 2014 21:49:15 +0100 From: Ben Morrow <ben@morrow.me.uk> To: freebsd-stable@freebsd.org Subject: Re: Should 9.3 carry a warning about NEW_XORG Message-ID: <20140707204912.GA11191@anubis.morrow.me.uk> In-Reply-To: <alpine.BSF.2.11.1407071357340.87353@wonkity.com> References: <53B69B88.4060803@gmail.com> <E1X32XF-000PnU-QG@dilbert.ingresso.co.uk> <CAPyFy2BhARs%2BwxhOuP-09tcPgzerU00_ARy=o4OyKec9azTOkQ@mail.gmail.com> <20140705103235.GB7680@rwpc15.gfn.riverwillow.net.au> <alpine.BSF.2.11.1407050455010.5138@wonkity.com> <20140706220006.K50382@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoth Warren Block <wblock@wonkity.com>: > On Sun, 6 Jul 2014, Ian Smith wrote: > > > Seeing that a perhaps not miniscule proportion of 9.x X users will need > > to do some manual configuration on upgrading to 9.3, a relevant WARNING > > in http://www.freebsd.org/releases/9.3R/relnotes.html should be helpful. > > I can agree with the idea of a note, just have no clear idea what it > should say. If people are shown how to stick with the old xorg, they > will be marooned and ports that require the newer version will not work. > People that upgrade may find their hardware no longer supported. That's > sort of the price of progress with technology. (No, it's the price of depending on a CADT upstream. It's a shame FreeBSD doesn't have the manpower to maintain a fork, since that would really be the only reliable option at this point.) The note should say exactly what you just said: there are no good options. Many configurations will either break now or break soon, unless you're willing to fall back to VESA-only (is that likely to remain a viable option in all cases?). While this is a deplorable situation, there is nothing the FreeBSD project can do about it. Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140707204912.GA11191>