From owner-freebsd-questions@freebsd.org Thu Apr 7 14:08:22 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D792B0784A for ; Thu, 7 Apr 2016 14:08:22 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2F302000 for ; Thu, 7 Apr 2016 14:08:21 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (user-24-214-48-39.knology.net [24.214.48.39]) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id u37DmttG014739 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 7 Apr 2016 08:48:56 -0500 Subject: Re: Recovering from X "upgrade" disaster - now what? References: Cc: freebsd-questions@freebsd.org From: "William A. Mahaffey III" Message-ID: <57066547.60405@hiwaay.net> Date: Thu, 7 Apr 2016 08:54:25 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 14:08:22 -0000 On 04/06/16 22:58, Warren Block wrote: > On Wed, 6 Apr 2016, Will Parsons wrote: > >> Thank you for the suggestions, even if they failed to solve the >> problem. >> >> Happily, I have now got X working again, but to do so I had to restore >> the entire contents of /usr/local from a backup I had made about 6 >> months ago. I think what this means is that my pkg database is out of >> sync with the actual contents of /usr/local. What does this mean as >> far as further updating? I'd just as soon try to resolve the real >> problem, but am understandably reluctant to leave my system crippled >> again. > > First, make a full backup of the system as it is. > > The easy way to fix the package database is the same thing that might > resolve the problem. Reinstall all the packages, either as binaries > or from ports. There is a procedure for ports at the end of the > portmaster man page. For packages, I want to say it would be 'pkg > install -af', but I have not tested it. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > If he blindly reinstalls *all* pkg's, he will replicate the problem he just got done fixing. Might want to lock X11, maybe other stuff as well, before restoring pkg's .... $0.02, no more, no less .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.