Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site amdahl.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!zehntel!dual!amdahl!gam
From: gam@amdahl.UUCP (Gordon A. Moffett)
Newsgroups: net.bugs.usg,net.lang.c
Subject: Re: utime misusage
Message-ID: <654@amdahl.UUCP>
Date: Sun, 2-Dec-84 16:12:26 EST
Article-I.D.: amdahl.654
Posted: Sun Dec  2 16:12:26 1984
Date-Received: Tue, 4-Dec-84 19:23:14 EST
References: <6114@brl-tgr.ARPA> <613@amdahl.UUCP> <267@rlgvax.UUCP>
Distribution: net
Organization: Amdahl Corp, Sunnyvale CA
Lines: 26
Xref: watmath net.bugs.usg:143 net.lang.c:3394

>   = Guy Harris {seismo,ihnp4,allegra}!rlgvax!guy
> > = me

> > The second argument of utime(2) is expected to be the address of
> > this kind of struct:
> > 
> >         struct utimbuf { time_t actime, modtime; } ubuf;
> > 
> > Using the address of the st_atime field of a stat(2) struct would
> > provide these values correctly, because the word following st_atime in
> > the structure is st_mtime (the mod. time).
> 
> WRONG!  FALSE!  INCORRECT!  Show me where in STAT(2) it states that those
> fields are contiguous.  The V7 manual did, but the S3 and S5 manuals
> *go out of their way* to state that they say *nothing* about what the
> "stat" structure looks like.  They give the fields in a different order
> than they appear in the structure, and say before it "The contents of
> the structure pointed to by 'buf' *include* the following members:".
> Clearly, they did *not* want to commit to the precise shape of the structure
> forever, world without end, amen....

Quite right, sorry, my mistake.  Never mind.
-- 
Gordon A. Moffett		...!{ihnp4,hplabs,amd,sun}!amdahl!gam

37 22'50" N / 122 59'12" W	[ This is just me talking. ]