On Fri, Apr 22, 2005 at 02:37:58PM +0200, Corinna Vinschen wrote:
>On Apr 22 07:49, Christopher Faylor wrote:
>> On Fri, Apr 22, 2005 at 10:37:50AM +0200, Corinna Vinschen wrote:
>> >I'm not sure this presumption is correct. The d_ino field is not marked
>> >as optional in SUSv3, it's marked as an
On Apr 22 07:49, Christopher Faylor wrote:
> On Fri, Apr 22, 2005 at 10:37:50AM +0200, Corinna Vinschen wrote:
> >I'm not sure this presumption is correct. The d_ino field is not marked
> >as optional in SUSv3, it's marked as an XSI extension. The crux with
> >XSI extensions is that (quote SuSv3)
On Fri, Apr 22, 2005 at 10:37:50AM +0200, Corinna Vinschen wrote:
>On Apr 21 16:28, Christopher Faylor wrote:
>> On Thu, Apr 21, 2005 at 08:15:33PM +, Eric Blake wrote:
>> I
>> >originally wrote this program to discover that inode reporting in
>> >readdir() is broken (to which you replied tha
Original Message
>From: Christopher Faylor
>Sent: 21 April 2005 19:44
> Nevertheless, Cygwin does try only to set errno when there is an error.
It's certainly a good policy, I don't debate that.
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe inf
On Apr 21 16:28, Christopher Faylor wrote:
> On Thu, Apr 21, 2005 at 08:15:33PM +, Eric Blake wrote:
> I
> >originally wrote this program to discover that inode reporting in
> >readdir() is broken (to which you replied that fixing it would cause
> >too much of a slowdown),
>
> Yes, both Cori
On Thu, Apr 21, 2005 at 08:15:33PM +, Eric Blake wrote:
>> Nevertheless, Cygwin does try only to set errno when there is an error.
>> There are some cases where that isn't true but I didn't see any that
>> referred to EISDIR.
>>
>
>While I didn't find any EISDIR on success (yet), I did find th
> Nevertheless, Cygwin does try only to set errno when there is an error.
> There are some cases where that isn't true but I didn't see any that
> referred to EISDIR.
>
While I didn't find any EISDIR on success (yet), I did find the following in
1.5.15: [l]stat() on /proc/registry/HKEY_CLASSES_R
> Well, that was my next step, but I'm off home for the evening.
>
> [EMAIL PROTECTED] /artimi> cd /proc/registry
> [EMAIL PROTECTED] /proc/registry> cd HKEY_CLASSES_ROOT/
> [EMAIL PROTECTED] /proc/registry/HKEY_CLASSES_ROOT> cd \*
> [EMAIL PROTECTED] /proc/registry/HKEY_CLASSES_ROOT/*> ls
> Alw
On Thu, Apr 21, 2005 at 07:24:00PM +0100, Dave Korn wrote:
>Original Message
>>From: Christopher Faylor
>>Sent: 21 April 2005 19:20
>
>>On Thu, Apr 21, 2005 at 05:39:57PM +, Eric Blake wrote:
>>>Also, I've noticed that some cygwin syscalls are sloppy, and change
>>>errno to EISDIR even
Original Message
>From: Christopher Faylor
>Sent: 21 April 2005 19:23
> On Thu, Apr 21, 2005 at 06:59:11PM +0100, Dave Korn wrote:
>> Original Message
>>> From: Eric Blake
>>> Sent: 21 April 2005 18:40
>>
>>> Contrary to your statement, /proc/registry/HKEY_CLASSES_ROOT/*/ is a
>>>
Original Message
>From: Christopher Faylor
>Sent: 21 April 2005 19:20
> On Thu, Apr 21, 2005 at 05:39:57PM +, Eric Blake wrote:
>> Also, I've noticed that some cygwin syscalls are sloppy, and change
>> errno to EISDIR even when they are successful.
>
> Cygwin does try only to set errn
On Thu, Apr 21, 2005 at 06:59:11PM +0100, Dave Korn wrote:
>Original Message
>>From: Eric Blake
>>Sent: 21 April 2005 18:40
>
>> Contrary to your statement, /proc/registry/HKEY_CLASSES_ROOT/*/ is a
>> valid directory name (but you sure have to be careful with shell quoting
>> to actually ge
On Thu, Apr 21, 2005 at 05:39:57PM +, Eric Blake wrote:
>Also, I've noticed that some cygwin syscalls are sloppy, and change
>errno to EISDIR even when they are successful.
Cygwin does try only to set errno when there is an error. If you have
specific evidence to the contrary please report it
> Dave Korn wrote:
>
> >
> > Presumably the reason that this behaviour is new is that there used to be
> > a bug that stopped it even attempting to recurse those dirs, because nothing
> > with '*' in it could ever be a valid filename.
> >
> >
> > cheers,
> > DaveK
>
>
> So there w
Original Message
>From: Eric Blake
>Sent: 21 April 2005 18:40
> Contrary to your statement, /proc/registry/HKEY_CLASSES_ROOT/*/ is a
> valid directory name (but you sure have to be careful with shell quoting
> to actually get there).
Only on a managed mount. You simply cannot create a
Dave Korn wrote:
>
> Presumably the reason that this behaviour is new is that there used to be
> a bug that stopped it even attempting to recurse those dirs, because nothing
> with '*' in it could ever be a valid filename.
>
>
> cheers,
> DaveK
So there where does the problem lie?
Stupid webmail interface. Why can't it wrap lines, so they don't get truncated
at 1000 characters en route, per the RFCs?
[...]
> changing errno except on error. readdir() is documented as not changing
> errno
> except on error when the return value is NULL, but is allowed to change errno
> w
> Ah. No, you absolutely shouldn't say it "crashes", because it does not
> "crash". Misdescribing a bug is the slowest imaginable way of getting it
> fixed!
>
> Particularly so in this case, because I don't see why find *shouldn't*
> return an exit code of 1 when it's had all those errors.
Original Message
>From: skilover
>Sent: 21 April 2005 16:14
Hi Chuck! Hope you didn't mean to take this off-list deliberately,
because I've added the list back in. Apologies in advance if you feel this
was a deeply personal communication I shouldn't have shared with the world!
> Dave
Dave Korn wrote:
> Original Message
>
>>From: Chuck
>>Sent: 19 April 2005 16:09
>
>
>>Findutils is broken when it comes to using it on the /proc filesystem.
>>The last version that worked is 4.1.7. Newer versions crash if you run
>>"find /proc". Anyone care to tackle this?
>
>
>
> C
Original Message
>From: Chuck
>Sent: 19 April 2005 16:09
> Findutils is broken when it comes to using it on the /proc filesystem.
> The last version that worked is 4.1.7. Newer versions crash if you run
> "find /proc". Anyone care to tackle this?
Cannot reproduce:
[EMAIL PROTECTED] /p
Christopher Faylor wrote:
> On Tue, Apr 19, 2005 at 11:09:27AM -0400, Chuck wrote:
>
>>Findutils is broken when it comes to using it on the /proc filesystem.
>>The last version that worked is 4.1.7. Newer versions crash if you run
>>"find /proc". Anyone care to tackle this?
>
>
> Pass.
>
> cgf
On Tue, Apr 19, 2005 at 11:09:27AM -0400, Chuck wrote:
>Findutils is broken when it comes to using it on the /proc filesystem.
>The last version that worked is 4.1.7. Newer versions crash if you run
>"find /proc". Anyone care to tackle this?
Pass.
cgf
--
Unsubscribe info: http://cygwin.com/
Findutils is broken when it comes to using it on the /proc filesystem.
The last version that worked is 4.1.7. Newer versions crash if you run
"find /proc". Anyone care to tackle this? I posted this here several
months ago and got sent over to a Gnu list. The Gnu folks think it's a
cygwin problem an
24 matches
Mail list logo
