Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcsun!hp4nl!star.cs.vu.nl!ast From: ast@cs.vu.nl (Andy Tanenbaum) Newsgroups: comp.os.minix Subject: Re: Large Disks Keywords: POSIX stat inode Message-ID: <3479@ast.cs.vu.nl> Date: 3 Oct 89 22:26:36 GMT References: <233@vsserv.scri.fsu.edu> <3463@ast.cs.vu.nl> <275@nikhefh.nikhef.nl> Reply-To: ast@cs.vu.nl (Andy Tanenbaum) Organization: VU Informatica, Amsterdam Lines: 18 In article <275@nikhefh.nikhef.nl> Schutte@nikhefh.nikhef.nl (Klamer Schutte) writes: >In article <3463@ast.cs.vu.nl> ast@cs.vu.nl (Andy Tanenbaum) writes: >#>one must >#>have three times in the i-node, since the standard tells exactly when each >#>time is updated, and test suites can easily verify this. > where can i find this? Start with Table 5-1. Then read Sec. 2-4, page 36: "Each file has three associated time values ..." All over the standard are requirements like 5.6.6.2" "Upon successful completion, the utime() function shall mark for update the st_ctime field of the file." It is easy enough for a test suite to stat a file, do a utime on it and stat it again to see if st_ctime was changed. The standard is full of requirements like this. Andy Tanenbaum (ast@cs.vu.nl)