Re: open() fails to update st_mtime when used with O_TRUNC and 0 byte files
Re: open() fails to update st_mtime when used with O_TRUNC and 0 byte files
- Subject: Re: open() fails to update st_mtime when used with O_TRUNC and 0 byte files
- From: Peter O'Gorman <email@hidden>
- Date: Thu, 12 Jul 2007 02:08:53 -0500
On Thu, 2007-07-12 at 00:19 -0500, Mike Frysinger wrote:
> On 7/12/07, Jordan K. Hubbard <email@hidden> wrote:
> > On Jul 11, 2007, at 9:45 PM, Mike Frysinger wrote:
> > > i dont even know what a "DTS representative" ... my guess is you're
> > > punting me to the marketing team or something ? how is it a forward
> > > looking statement if 10.5 has already been certified ?
> >
> > I think Terry's just being cautious. We've already stated publicly
> > that Leopard is UNIX03 compliant and will, of course, ship that way so
> > you can infer from this that it passed the test in question well
> > enough to pass muster with The Open Group.
>
> i guess it isnt possible to ask for a fix for 10.4.x ... especially
> since i dont have any sort of customer $$$ backing the request, just
> some lamer who wants to compile the kernel sanely.
It is entirely within the realm of possibility that Apple ran the UNIX03
conformance tests on a UFS filesystem. So, on Tiger, you'd get the same
results if you also used one. Terry, I think, originally suggested doing
this on a UFS disk image.
If it is the case that Apple did run the complete test suite on UFS, you
could probably make the case to the opengroup that the tests ought to be
run on the system's default filesystem, however, since 10.5 has already
been certified as UNIX, this would not force any change until a later
release.
Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden