From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Jan 10 21:30:10 2006 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 499D316A41F for ; Tue, 10 Jan 2006 21:30:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1498043D46 for ; Tue, 10 Jan 2006 21:30:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k0ALU9IJ027039 for ; Tue, 10 Jan 2006 21:30:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k0ALU98b027034; Tue, 10 Jan 2006 21:30:09 GMT (envelope-from gnats) Date: Tue, 10 Jan 2006 21:30:09 GMT Message-Id: <200601102130.k0ALU98b027034@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Heiner Cc: Subject: Re: ports/91392: k3b port install causes reboot X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Heiner List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2006 21:30:10 -0000 The following reply was made to PR ports/91392; it has been noted by GNATS. From: Heiner To: Jos Witters Cc: bug-followup@freebsd.org Subject: Re: ports/91392: k3b port install causes reboot Date: Tue, 10 Jan 2006 22:31:04 +0100 On Sunday 08 January 2006 21:24, Jos Witters wrote: > Couldn't it just have been the case that some pieces of software were > located on the unmounted slices causing the panic. This depends on your configuration. With nothing changed, everything is installed below /usr/local. Furthermore, the package db is updated (usually /var/db/pkg). Finally the library cache is updated as well, which *might* affect other directories. Not to forget: the whole build process is done below /usr/ports/sysutils/k3b. Maybe configure&gcc uses /tmp as well, I don't know. In any case: It is usually very hard to see a kernel panic. Unfortunately I can not explain, why it happend only with k3b and not with other applications. I do not see any special things going on during the k3b installation. And I have no further ideas, what is wrong. All I know is, that make install in k3b works fine here and that I have no further reports about that! Sorry Heiner