From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Oct 30 00:00:02 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2A40D86E for ; Wed, 30 Oct 2013 00:00:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1860121DF for ; Wed, 30 Oct 2013 00:00:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9U001uC002045 for ; Wed, 30 Oct 2013 00:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9U0010j002044; Wed, 30 Oct 2013 00:00:01 GMT (envelope-from gnats) Date: Wed, 30 Oct 2013 00:00:01 GMT Message-Id: <201310300000.r9U0010j002044@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Henry Hu Subject: Re: ports/169165: sysutils/fusefs-kmod: calling fchown(2) on sshfs filesystem causes panic X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Henry Hu List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2013 00:00:02 -0000 The following reply was made to PR ports/169165; it has been noted by GNATS. From: Henry Hu To: "bug-followup@freebsd.org" , dh@bsd.ee Cc: Subject: Re: ports/169165: sysutils/fusefs-kmod: calling fchown(2) on sshfs filesystem causes panic Date: Tue, 29 Oct 2013 19:59:09 -0400 --089e0102f84ad9df9d04e9ea016a Content-Type: text/plain; charset=ISO-8859-1 Finally we've got fuse in the base system, and this problem no longer exists... -- Cheers, Henry --089e0102f84ad9df9d04e9ea016a Content-Type: text/html; charset=ISO-8859-1
Finally we've got fuse in the base system, and this problem no longer exists...

--
Cheers,
Henry
--089e0102f84ad9df9d04e9ea016a--