From owner-freebsd-current@FreeBSD.ORG Fri Nov 18 15:45:41 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFFC716A420 for ; Fri, 18 Nov 2005 15:45:41 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B288E43D70 for ; Fri, 18 Nov 2005 15:45:38 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id jAIFjbIh053672; Fri, 18 Nov 2005 09:45:37 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <437DF717.8010207@centtech.com> Date: Fri, 18 Nov 2005 09:45:27 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Candler References: <20051116161540.GB4383@uk.tiscali.com> <20051118091333.GA1058@galgenberg.net> <20051118145051.GA3713@Pandora.MHoerich.de> <20051118153616.GA12210@uk.tiscali.com> In-Reply-To: <20051118153616.GA12210@uk.tiscali.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1178/Thu Nov 17 23:27:25 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' 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: Fri, 18 Nov 2005 15:45:42 -0000 Brian Candler wrote: >>This just adds a -o flag to cp, which preserves order. > > > Hmm, that's another solution that I hadn't thought of. > > Advantages: simple to implement. (Even simpler if you use the ?: operator). > > Disadvantages: it's still strange that the default behaviour is to copy the > files in an arbitary shuffled order. The manpage will need updating to > document the -o flag, and hence will have to explain the strangeness. > Commands arguably have too many flags already. I didn't think cp (or any tool, like tar) did it 'arbitrarily', but in order of mtime. Is that not true? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------