From owner-freebsd-x11@FreeBSD.ORG Tue Dec 29 23:29:49 2009 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D013C106566B for ; Tue, 29 Dec 2009 23:29:49 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id A7F2B8FC18 for ; Tue, 29 Dec 2009 23:29:49 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 37F80BDC43; Tue, 29 Dec 2009 15:29:49 -0800 (PST) To: Robert Noland In-Reply-To: <1262092734.2314.15.camel@balrog.2hip.net> Date: Tue, 29 Dec 2009 15:29:49 -0800 Message-ID: <29760.1262129389@tristatelogic.com> From: "Ronald F. Guilmette" Cc: freebsd-x11@freebsd.org Subject: Re: Default configuration for xorg-drivers (WTF?) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Dec 2009 23:29:49 -0000 Robert, Thanks for your quick response. In message <1262092734.2314.15.camel@balrog.2hip.net>, you wrote: >> Call me dense, but hope somebody can explain to me how this makes sense. > >run "make rmconfig && make config" in the xorg-drivers port. Your >config is likely stale. Hummm... OK. I learned something today. So, ah, basically you're telling me that "portsnap fetch update" DOES NOT flush out old/crusty/outdated port config files, yes? I confess, that I didn't know that. (I was under the naive impression that "portsnap fetch update" made everything lovely, beautiful, and, most importantly, current. I guess not. Oh well. Forewarned is forearmed. Thanks for the info.) As to my other question, I'm still looking for some reassurance: >> But ummm...... Why is it that in the current up-to-date files relating to >> the xorg-drivers port, the openchrome driver is, by default, *de-selected*? >> >> Should I be worried? >> >> Is there something broken about the current openchrome driver? Is the current openchrome driver safe for mere mortals like me (e.g. when used with K8M890) ?