From owner-cvs-all@FreeBSD.ORG Mon Mar 17 15:19:10 2008 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8565106566C; Mon, 17 Mar 2008 15:19:10 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id AD8658FC2B; Mon, 17 Mar 2008 15:19:10 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.128] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id m2HFJApb021809; Mon, 17 Mar 2008 08:19:10 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <47DE8BEE.7040405@freebsd.org> Date: Mon, 17 Mar 2008 08:19:10 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <200712180849.lBI8nmEi088947@repoman.freebsd.org> <20071218100355.GR16982@elvis.mu.org> <20080314223652.GA20470@garage.freebsd.pl> In-Reply-To: <20080314223652.GA20470@garage.freebsd.pl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-src@freebsd.org, Alfred Perlstein , src-committers@freebsd.org, Diomidis Spinellis , cvs-all@freebsd.org Subject: Re: cvs commit: src/tools/regression/bin/mv regress.sh X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Mar 2008 15:19:11 -0000 >>> FreeBSD src repository >>> >>> Modified files: >>> tools/regression/bin/mv regress.sh >>> Log: >>> Add more tests. All rename(2)-based tests now succeed. >>> The performance of the cross-device equivalents is under investigation. > > I was thinking about adding two options to cp(1) (-1 and -2) to give > cp(1) a hint if the copy is done inside one disk or between separate > disks. Will anyone ever use such a flag? I'm skeptical. If there were a way to determine this programmatically, it would be a big win. You'd need to look at the first file copied to determine if the destination was on the same (physical) disk or not. Tim