From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rewriting paths [was: mv vs cp]
Date: Wed, 10 Oct 2001 09:05:25 +0000 [thread overview]
Message-ID: <3BC3CBF2.539DA51@null.net> (raw)
In-Reply-To: <27591.1002609695@apnic.net>
George Michaelson wrote:
> Something maybe not covered so far is what mv etc do with sparce files,
> if memory serves me right some operations are 'safe' and some have a habit
> of filling the empty extent with data, having unforseen consequences for
> the real size of used disk.
> Of course, if 9 doesn't have them, it doesn't have the problem either.
It wouldn't much matter, since it's just an optimization issue and
could be "fixed".
next prev parent reply other threads:[~2001-10-10 9:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <nemo@gsyc.escet.urjc.es>
2001-10-09 6:25 ` Fco.J.Ballesteros
2001-10-09 6:41 ` George Michaelson
2001-10-10 9:05 ` Douglas A. Gwyn [this message]
2001-10-09 14:19 ` Richard
2002-07-16 16:08 [9fans] useful language extension, or no? rob pike, esq.
2002-07-16 15:31 ` Sam
2002-07-16 17:24 ` [9fans] more extensions FJ Ballesteros
2002-07-16 16:26 ` Sam
2002-07-16 17:28 ` Howard Trickey
2002-07-16 17:09 ` [9fans] New language? Sam
2002-07-17 5:45 ` GBA
2002-07-17 6:23 ` Lucio De Re
2002-07-16 18:23 ` [9fans] more extensions Scott Schwartz
2002-07-16 18:47 ` Dan Cross
2002-07-16 19:05 ` Jon Snader
2002-07-17 8:58 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2001-10-07 16:23 [9fans] mv vs cp jmk
2001-10-08 17:43 ` [9fans] rewriting paths [was: mv vs cp] Richard Uhtenwoldt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BC3CBF2.539DA51@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).