From owner-freebsd-current@FreeBSD.ORG Tue Sep 25 16:33:33 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46B0416A537 for ; Tue, 25 Sep 2007 16:33:33 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.freebsd.org (Postfix) with ESMTP id EB20213C43E for ; Tue, 25 Sep 2007 16:33:32 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from gotou-daichi-nokonpyuta.local (east61-p181.eaccess.hi-ho.ne.jp [219.105.23.182]) by natial.ongs.co.jp (Postfix) with ESMTP id B6BEB244C3A; Wed, 26 Sep 2007 01:33:31 +0900 (JST) Message-ID: <46F9384E.5010409@freebsd.org> Date: Wed, 26 Sep 2007 01:33:18 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Ivan Voras References: <46F905FD.9060208@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: The safety expansion for FreeBSD rm(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 16:33:33 -0000 Ivan Voras wrote: > Daichi GOTO wrote: >> Hi Guys again >> >> Today is not unionfs. > > How is the unionfs patch progressing through re ? :) I hope it gets > digested soon :) I have sent a aprove request to re@ and been waiting for replay. I have a hope to get aproval mail too :) I beleive in that recent unionfs patches bunch is well viewed and working very good. >> We have created safety expansion for rm(1). If you have any interests, >> please try follow patch. >> >> http://people.freebsd.org/~daichi/safety-rm/ > > This looks useful, but shouldn't this feature be handled more globally, > with a MAC policy or something like that? Yes, that is not depending to MAC or other comprehensive access framework. At the beginning, what's important is that I have anyone needs that feature or not ;-) If someone needs that feature, I will get the work of more comprehensive mechanism.