From owner-freebsd-ports@FreeBSD.ORG Sat Aug 27 13:16:32 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61393106566C for ; Sat, 27 Aug 2011 13:16:32 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 1B3A98FC0A for ; Sat, 27 Aug 2011 13:16:31 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 27 Aug 2011 09:16:30 -0400 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr17.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id BAX25476; Sat, 27 Aug 2011 09:16:30 -0400 Received: from 209-6-41-114.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.41.114]) by smtp04.lnh.mail.rcn.net with ESMTP; 27 Aug 2011 09:16:30 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20056.60974.346785.592721@jerusalem.litteratus.org> Date: Sat, 27 Aug 2011 09:16:30 -0400 To: freebsd-ports@freebsd.org In-Reply-To: References: <20110826172328.67f707d7@cox.net> <1314402348.13483.6.camel@xenon> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr17.lnh.mail.rcn.net) Subject: Re: Problem with nvidia-driver and "X" after upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Aug 2011 13:16:32 -0000 Michal Varga articulated: >> This is a known phenomena with everything when having your OS sources >> and your live OS out of sync. > > Define "everything" Obviously, not everything suffers from this > problem. In fact, lacking proof otherwise, I would tend to > believe that this is a niche problem. This would be the second case I know of; the other is "lsof". Other ports determine what the OS looks like by consulting /inter alia/ /usr/include/ and /usr/local/include/, which are by definition expected to match the running kernel+world. I have never understood why anyone would use anything else. Respectfully, Robert Huff