From owner-freebsd-doc Thu Mar 7 16:10: 8 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DE28637B41A for ; Thu, 7 Mar 2002 16:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g280A1P38626; Thu, 7 Mar 2002 16:10:01 -0800 (PST) (envelope-from gnats) Date: Thu, 7 Mar 2002 16:10:01 -0800 (PST) Message-Id: <200203080010.g280A1P38626@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Giorgos Keramidas Subject: Re: docs/35646: cp(1) page needs a "Bugs" section. Reply-To: Giorgos Keramidas Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35646; it has been noted by GNATS. From: Giorgos Keramidas To: "Gary W. Swearingen" Cc: bug-followup@freebsd.org Subject: Re: docs/35646: cp(1) page needs a "Bugs" section. Date: Fri, 8 Mar 2002 02:07:24 +0200 (EET) Gary W. Swearingen wrote: > The cp(1) program has a feature that should be documented in a "Bugs" > section. (Or can there be a "Warnings" section?) Are you sure this should be documented in the manual page of cp(1) ? Any program that copies data and doesn't take special care of 'holes' will show similar behavior. Should we modify their manual pages too? [ See what dd(1) does instead of cp(1) below. ] hades:~> cd /tmp hades:/tmp> df . Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 194548 65916 113069 37% / hades:/tmp> dd if=/dev/zero of=zeros-sparse oseek=1000 count=2 2+0 records in 2+0 records out 1024 bytes transferred in 0.000685 secs (1494682 bytes/sec) hades:/tmp> df . Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 194548 65932 113053 37% / hades:/tmp> dd if=zeros-sparse of=zeros-dd 1002+0 records in 1002+0 records out 513024 bytes transferred in 0.286582 secs (1790147 bytes/sec) ^^^ Many blocks copied. hades:/tmp> df . Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 194548 66444 112541 37% / hades:/tmp> ls -l zeros-* -rw-r--r-- 1 charon wheel - 513024 Mar 8 02:03 zeros-dd -rw-r--r-- 1 charon wheel - 513024 Mar 8 02:03 zeros-sparse Note that I'm not opposing the change. I'm only asking for ideas about all the possible programs that will behave exactly like cp(1) and dd(1) do, when they find files with 'holes'. Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message