From owner-freebsd-questions Thu Dec 13 13:30:15 2001 Delivered-To: freebsd-questions@freebsd.org Received: from fac13.ds.psu.edu (fac13.ds.psu.edu [146.186.61.98]) by hub.freebsd.org (Postfix) with ESMTP id 7704C37B416 for ; Thu, 13 Dec 2001 13:30:05 -0800 (PST) Received: from fac13.ds.psu.edu (localhost.ds.psu.edu [127.0.0.1]) by fac13.ds.psu.edu (8.11.6/8.11.3) with ESMTP id fBDLTWO84967; Thu, 13 Dec 2001 16:29:32 -0500 (EST) (envelope-from hawk@fac13.ds.psu.edu) Message-Id: <200112132129.fBDLTWO84967@fac13.ds.psu.edu> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Ryan Thompson Cc: freebsd-questions@FreeBSD.ORG Subject: Re: keeping a system in use during a complete rebuild? In-Reply-To: Your message of "Thu, 13 Dec 2001 15:12:10 CST." <20011213150416.K94416-100000@catalyst.sasknow.net> From: dochawk@psu.edu Date: Thu, 13 Dec 2001 16:29:32 -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ryan rambled, > dochawk@psu.edu wrote to Ryan Thompson: > > I'm also getting weird sound results, apparent attempts to load > > the linux module after it's already loaded, and a couple of other > > weird events. > > Hmm... Who knows... Something obviously got corrupted. I'd probably > clean out /usr/src and /usr/obj, run fsck -p (unmount the filesystems > first :-b), restore the GENERIC kernel, re-cvsup the sources, rebuild, > and install. (In that order). Or, to be absolutely sure, you might > still consider remaking the filesystems and reinstalling from fresh > media. Hardware problems can wreak all sorts of lingering havoc on > things. time. no time :) but I do have fresh source, and, as I mention below, portsdb suddently started workign again. I'm rebuilding the entire ports tree. Then I'll do a fresh world, then force the ports again for good measure. > > > You can upgrade most all ports on a running system without any > > > worries. Check out the portupgrade port|package to make life easy. > > That's where this mess started :) Portupgrade no longer works, > > and /usr/ports/INSTALL.db and .rbs are gone and won't come back. > > whoa, hold on. A little dinkin here, and a little there, and > > suddenly, after days of fighting, portsdb -uU is actually doing > > something! I may be home free! Yeehah! > > hawk, who now sees that sacrificing the bunny *did* pay off . . . > :-) If you're not home free yet, you can always just rm -Rf /usr/ports > and re-fetch the ports dist (ports.tar.gz), to start out clean. I've done that a couple of times :) the problem was that I still couldn't force INDEX.db to come back . . . And I really wish I knew why it was working now. Thanks to all. hawk -- What part of "non-negotiable" didn't you understand? /"\ ASCII ribbon campaign dochawk@psu.edu Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of X and postings. Penn State until it pays my retainer. / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message