From owner-freebsd-questions@FreeBSD.ORG Wed Nov 12 10:56:53 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 998B616A4CF for ; Wed, 12 Nov 2003 10:56:53 -0800 (PST) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.156.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FAA443FA3 for ; Wed, 12 Nov 2003 10:56:52 -0800 (PST) (envelope-from forrie@forrie.com) Received: from dell.forrie.com (wks.forrie.net. [192.168.1.21]) by forrie.com with ESMTP id hACIuj3p001449 for ; Wed, 12 Nov 2003 13:56:46 -0500 (EST) (envelope-from forrie@forrie.com) Message-Id: <6.0.0.22.2.20031112135218.01d0b928@192.168.1.1> X-Sender: forrie@192.168.1.1 X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Wed, 12 Nov 2003 13:56:44 -0500 To: freebsd-questions@freebsd.org From: Forrest Aldrich Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean Subject: Mysterious manpage & *roff problems solved (SOLUTION) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2003 18:56:53 -0000 I had posted recently regarding a mysterious problem I had with my manpage subsystem not working properly. This has been a problem for quite some time. After analyzing ktrace/kdump outputs, removing any conflicting *roff files in /usr/local/bin and /usr/local/share, we still couldn't get it working. Interestingly, there are no indications of *roff in /var/db/pkg, so I have no idea how it ended up under /usr/local to begin with. The solution, thanks to Larry Rosenman , was to backup my /usr/src/sys/i386/conf file and "rm -rf" the entire /usr/src and /usr/obj trees, then re-CVSup (putting back my kernel config) and rebuild/reinstall the system. It was a pickle - as the problem just didn't seem obvious. So, somewhere along the line something got munged up in the /usr/src directory. I hope this solution helps someone out there that may get bitten by this. And again thanks to Larry. Forrest