From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <775b8d190602111910w5adb0046q796ef800e92d2aea@mail.gmail.com> Date: Sun, 12 Feb 2006 14:10:46 +1100 From: Bruce Ellis To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] Strange date/time on some created files In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <92e9851ad8fe77a526c62bbb5c9121a8@collyer.net> Topicbox-Message-UUID: fd861bbe-ead0-11e9-9d60-3106f5b1d025 it would work if stat on PATH/. returned the server's idea. this is only feasible for a REPLACE, i think union directroies should return the 'M'. brucee On 2/12/06, Russ Cox wrote: > > At least in Ken fs, you want the access time of the root (to get the > > current fs time): > > > > ; date; ls -ldu /n/boot / > > Sat Feb 11 17:45:13 PST 2006 > > d-r-xr-xr-x / 0 bootes bootes 0 Feb 11 17:45 / > > d-rwxrwxr-x M 251502 adm sys 0 Feb 11 17:45 /n/boot > > ls -ld /n /n/boot and you will see they have the same mount number. > > > It's done here, 9p1.c:1300,1301: > > > > if(d->qid.path =3D=3D QPROOT) /* stat of root gives time = */ > > d->atime =3D time(); > > > > and here, 9p2.c:1431,1432: > > > > if(d->qid.path =3D=3D QPROOT) /* stat of root giv= es time */ > > d->atime =3D time(); > > > > I haven't looked to see if fossil does it. > > It does, if only because accessing the root updates atime anyway. > > But that's not what I was getting at. If you dial the file server > yourself and read/write 9P messages, yes, you can get at the > stat info for a file server root. But via the usual system calls, > the stat info for any mounted file server root is invisible. You > always see the mount point, never the mounted root. > > Russ >