From owner-freebsd-questions Fri Nov 30 16:52:12 2001 Delivered-To: freebsd-questions@freebsd.org Received: from teak.adhesivemedia.com (teak.adhesivemedia.com [207.202.159.79]) by hub.freebsd.org (Postfix) with ESMTP id 254DB37B417 for ; Fri, 30 Nov 2001 16:52:09 -0800 (PST) Received: from localhost (philip@localhost) by teak.adhesivemedia.com (8.11.6/8.11.6) with ESMTP id fB10oD104110; Fri, 30 Nov 2001 16:50:13 -0800 (PST) (envelope-from philip@adhesivemedia.com) Date: Fri, 30 Nov 2001 16:50:13 -0800 (PST) From: Philip Hallstrom To: Ryan Thompson Cc: Maciek , Subject: Re: percent progress In-Reply-To: Message-ID: <20011130164903.G2924-100000@teak.adhesivemedia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Actually mv could take a really long time if you move across filesystems because then it is really doing a cp and then a delete... It's not really an estimate and someone might have already suggested this (didn't see the whole thread) but you can always add the "-v" option to either mv or cp and watch the files go by... -philip On Fri, 30 Nov 2001, Ryan Thompson wrote: > Maciek wrote to questions@FreeBSD.ORG: > > > Hi, > > > > can I have percent progress in mv or cp? > > Here's a more academic answer: > > You shouldn't really need one for mv, unless you are mv'ing thousands > of files. (Note that if you mv a directory, even if it contains > thousands (or millions) of files, that it completes with only one > actual move operation... so it returns almost immediately). > > cp, on the other hand, could potentially support something like this. > Someone already suggested using an existing file manager for > this, which is a fine idea. > > One trouble with copying files, though, is one doesn't always know how > much progress has been made. (i.e., cp from a special file), so it > wouldn't be perfect. For most applications, though, it would be OK. > > It would be fairly trivial to extend cp(1) to include something like > this, but it would cause funny results in a lot of scripts that don't > expect any output from cp(1). You'd want to make a copy of the cp(1) > source under a different name, and make your modifications there. > > Hope this helps, > - Ryan > > > > > > Rodion > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > -- > Ryan Thompson > Network Administrator, Accounts > > SaskNow Technologies - http://www.sasknow.com > #106-380 3120 8th St E - Saskatoon, SK - S7H 0W2 > > Tel: 306-664-3600 Fax: 306-664-1161 Saskatoon > Toll-Free: 877-727-5669 (877-SASKNOW) North America > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message