From owner-svn-src-head@FreeBSD.ORG  Wed Oct 27 21:26:02 2010
Return-Path: <owner-svn-src-head@FreeBSD.ORG>
Delivered-To: svn-src-head@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1233)
	id 0C5DD1065743; Wed, 27 Oct 2010 21:26:02 +0000 (UTC)
Date: Wed, 27 Oct 2010 21:26:02 +0000
From: Alexander Best <arundel@freebsd.org>
To: Dag-Erling Smorgrav <des@FreeBSD.org>
Message-ID: <20101027212601.GA78062@freebsd.org>
References: <201010271848.o9RImNSR019344@svn.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201010271848.o9RImNSR019344@svn.freebsd.org>
Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org,
	src-committers@freebsd.org
Subject: Re: svn commit: r214431 - head/bin/rm
X-BeenThere: svn-src-head@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SVN commit messages for the src tree for head/-current
	<svn-src-head.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/svn-src-head>,
	<mailto:svn-src-head-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-src-head>
List-Post: <mailto:svn-src-head@freebsd.org>
List-Help: <mailto:svn-src-head-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-src-head>,
	<mailto:svn-src-head-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 21:26:02 -0000

On Wed Oct 27 10, Dag-Erling Smorgrav wrote:
> Author: des
> Date: Wed Oct 27 18:48:23 2010
> New Revision: 214431
> URL: http://svn.freebsd.org/changeset/base/214431
> 
> Log:
>   Language cleanup.
> 
> Modified:
>   head/bin/rm/rm.1
> 
> Modified: head/bin/rm/rm.1
> ==============================================================================
> --- head/bin/rm/rm.1	Wed Oct 27 18:46:56 2010	(r214430)
> +++ head/bin/rm/rm.1	Wed Oct 27 18:48:23 2010	(r214431)
> @@ -231,6 +231,6 @@ The
>  .Fl P
>  option assumes that the underlying file system updates existing blocks
>  in-place and does not store new data in a new location.
> -This is true for UFS but not for ZFS, which is using a Copy-On-Write strategy.
> -In addition, only regular files are overwritten, other types of files
> -are not.
> +This is true for UFS, but not for ZFS or other file systems which use
> +copy-on-write semantics.
> +In addition, only regular files are overwritten.

are in fact COW fs the only exception where the -P flag won't work? before
r213582 LFS was mentioned here and that the block size must be fixed.
also the comment in rm.c says that -P won't work for any logging file systems.
i'm not a fs expert, but i think mentioning that -P won't work for COW fs isn't
enough.

-- 
a13x