Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Vaclav Haisman
> UNIX has a method for producing sparse files. If this is desired functionality, > Cygwin should mimic that not invent a new way of doing things. > > cgf Hi, I have prepared another patch that implements parse files for Cygwin. It is smaller and, I think, even better than the previous. No new CY

Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Christopher Faylor
On Mon, Feb 17, 2003 at 05:37:20PM +0100, Vaclav Haisman wrote: >> UNIX has a method for producing sparse files. If this is desired functionality, >> Cygwin should mimic that not invent a new way of doing things. >> >> cgf > >Hi, >I have prepared another patch that implements parse files for Cygwi

Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Vaclav Haisman
> This looks pretty good but the cygwin convention is to use wincap > settings for this kind of thing rather than using is_winnt. So, please > add a wincap capability to accomplish this. > > cgf Modified as suggested. Vaclav Haisman 2003-02-17 Vaclav Haisman <[EMAIL PROTECTED]> * win

Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Max Bowsher
> On Mon, Feb 17, 2003 at 05:37:20PM +0100, Vaclav Haisman wrote: >> I have prepared another patch that implements sparse files for >> Cygwin. It is smaller and, I think, even better than the previous. >> No new CYGWIN options. >> 2003-02-17 Vaclav Haisman <[EMAIL PROTECTED]> >> >> * include/win

Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Vaclav Haisman
> Is it wise to set *all* new files to sparse? Surely if this was actually > advantageous, Windows would do it anyway? From MSDN: "Note It is up to the > application to maintain sparseness by writing zeros with > FSCTL_SET_ZERO_DATA." I.e., this will gain nothing unless the application > knows ab

Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Max Bowsher
Vaclav Haisman wrote: >> Is it wise to set *all* new files to sparse? Surely if this was >> actually advantageous, Windows would do it anyway? From MSDN: "Note >> It is up to the application to maintain sparseness by writing zeros >> with FSCTL_SET_ZERO_DATA." I.e., this will gain nothing unless th

Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Vaclav Haisman
> That's nice. Did you read the bit above where I quoted MSDN? Merely setting > the file as sparse will NOT SAVE SPACE on Windows. So, no space gain, and a > performance penalty of untested magnitude. I see only disadvantages. > > > Max. Oh yes, it will. Some applications do lseek() on rather lon

Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Christopher Faylor
On Mon, Feb 17, 2003 at 07:20:42PM +0100, Vaclav Haisman wrote: >>That's nice. Did you read the bit above where I quoted MSDN? Merely >>setting the file as sparse will NOT SAVE SPACE on Windows. So, no >>space gain, and a performance penalty of untested magnitude. I see >>only disadvantages. >

Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Vaclav Haisman
> Btw, now that I've said that it occurred to me to check > GetVolumeInformation. There is apparently a FILE_SUPPORTS_SPARSE_FILES > flag available. That's the ultimate way to deal with this rather than > adding a wincap, I believe. Check (pc->fs.flags & > FILE_SUPPORTS_SPARSE_FILES) in fhandler

Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Christopher Faylor
On Mon, Feb 17, 2003 at 07:48:57PM +0100, Vaclav Haisman wrote: >>Btw, now that I've said that it occurred to me to check >>GetVolumeInformation. There is apparently a FILE_SUPPORTS_SPARSE_FILES >>flag available. That's the ultimate way to deal with this rather than >>adding a wincap, I believe.

Re: Create new files as sparse on NT systems. (2nd try)

2003-02-17 Thread Vaclav Haisman
> This is consistent with the way the rest of cygwin works, however. The > same argument could be applied to testing for ntsec. If this was an issue > then we should be changing the fs information to reflect reparse points. > > cgf I am not sure what is the conclusion here. Should I make it chec

grp.cc

2003-02-17 Thread Pierre A. Humblet
Corinna, I believe this will take care of Re: uh oh [[EMAIL PROTECTED]: Re: bash broken with cygwin 1.3.20? - now working with 1.3.20] Pierre 2003-02-17 Pierre Humblet <[EMAIL PROTECTED]> * grp.cc (internal_getgroups): Handle properly tokens with no groups. Fix bug introduced