Eric Blake <[EMAIL PROTECTED]> wrote:
> According to James Youngman on 2/1/2005 3:17 AM:
>>
>> Unix systems automatically generate sparse files when programs seek
>> forwards on their output file. There is no need to have a "sparse"
>> attribute. This is what coreutils' "cp" does.
>
> Right now,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to James Youngman on 2/1/2005 3:17 AM:
>
> Unix systems automatically generate sparse files when programs seek
> forwards on their output file. There is no need to have a "sparse"
> attribute. This is what coreutils' "cp" does.
Right no
Jim Meyering <[EMAIL PROTECTED]> writes:
> Is this just theoretical, or do you know of a file system type
> that'd cause trouble (that doesn't support sparse files, yet for
> which meta data can take up extra space)?
It's just a guess, I don't know of any example. It might well be that
going fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to RE on 2/2/2005 3:11 AM:
> Hi Eric,
>
> Maybe you can answer my question or help me with my "sparse problem" which I
> am quoting in the following once again. [BTW I don't know if the patch you
> sent me will be needed, but if yes, I woul
and regards,
Rolf
-Ursprüngliche Nachricht-
Von: Eric Blake [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 2. Februar 2005 04:17
An: James Youngman
Cc: RE; bug-coreutils@gnu.org
Betreff: Re: cp command - problem with sparse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jame
Andreas Schwab <[EMAIL PROTECTED]> wrote:
if test "$2" = 64; then
>>> ^^
>>> Doesn't that need to be changed to 128 as well?
>>
>> Yes. Thanks. Fixed.
>
> Actually it should check for >= 128 to account for possible meta data.
Ok. I've made it do that, too.
Is this just t
Jim Meyering <[EMAIL PROTECTED]> writes:
> Andreas Schwab <[EMAIL PROTECTED]> wrote:
>> Eric Blake <[EMAIL PROTECTED]> writes:
>>
>>> if test "$2" = 64; then
>> ^^
>> Doesn't that need to be changed to 128 as well?
>
> Yes. Thanks. Fixed.
Actually it should check for >= 128 t
Andreas Schwab <[EMAIL PROTECTED]> wrote:
> Eric Blake <[EMAIL PROTECTED]> writes:
>
>> Index: tests/du/8gb
>> ===
>> RCS file: /cvsroot/coreutils/coreutils/tests/du/8gb,v
>> retrieving revision 1.6
>> diff -u -p -r1.6 8gb
>> --- tests
Eric Blake <[EMAIL PROTECTED]> writes:
> Index: tests/du/8gb
> ===
> RCS file: /cvsroot/coreutils/coreutils/tests/du/8gb,v
> retrieving revision 1.6
> diff -u -p -r1.6 8gb
> --- tests/du/8gb 3 May 2003 14:24:37 - 1.6
>
Eric Blake <[EMAIL PROTECTED]> wrote:
...
> According to the cygwin mailing list,
> http://sources.redhat.com/ml/cygwin/2005-02/msg00013.html, cygwin already
> supports sparse files when you do lseek beyond EOF during writes. The
> trick, however, is that NTFS on Windows XP does not create a hole
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to James Youngman on 2/1/2005 3:17 AM:
>
> Unix systems automatically generate sparse files when programs seek
> forwards on their output file. There is no need to have a "sparse"
> attribute. This is what coreutils' "cp" does.
>
> Wind
On Mon, Jan 31, 2005 at 05:30:22PM +0100, RE wrote:
> "cp --sparse=always c:\test.cfg c:\test2.cfg"
>
> Everything works fine with that cp command, except the
> fact that I do not get a sparse file. Even when I copy
> a sparse file, the sparse attribute is no longer
> present in the copy an t
Hi there,
I have files on my HD that contain large amounts of
zeroes and I want to convert them into sparse files. I
already tried the GNU fileutils with their cp command.
They say that it converts standard files into sparse
files by using the command
"cp --sparse=always c:\test.cfg c:\test
13 matches
Mail list logo
