diff options
| -rw-r--r-- | doc/ChangeLog | 5 | ||||
| -rw-r--r-- | doc/hurd.texi | 26 |
2 files changed, 16 insertions, 15 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog index 3746d021..bc17463d 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,8 @@ +2009-02-16 Thomas Schwinge <tschwinge@gnu.org> + + * hurd.texi: Instead of `st_?time' and `st_?time_usec', talk about + `st_?tim'. + 2008-06-10 Samuel Thibault <samuel.thibault@ens-lyon.org> * hurd.texi (Diskfs Callbacks): Add const qualifier to parameter diff --git a/doc/hurd.texi b/doc/hurd.texi index edac88c4..098bebf2 100644 --- a/doc/hurd.texi +++ b/doc/hurd.texi @@ -102,7 +102,7 @@ This file documents the GNU Hurd kernel component. This edition of the documentation was last updated for version @value{VERSION} of the Hurd. Copyright @copyright{} 1994, 1996, 1998, 1999, 2000, 2001, 2002, 2003, -2004, 2005, 2007, 2008 Free Software Foundation, Inc. +2004, 2005, 2007, 2008, 2009 Free Software Foundation, Inc. @quotation Permission is granted to make and distribute verbatim copies of @@ -1806,27 +1806,23 @@ this by calling @code{io_get_icky_async_id}. Users may call @code{io_stat} to find out information about the I/O object. Most of the fields of a @code{struct stat} are meaningful only for files. All objects, however, must support the fields -@var{st_fstype}, @var{st_fsid}, @var{st_ino}, @var{st_atime}, -@var{st_atime_usec}, @var{st_mtime_user}, @var{st_ctime}, -@var{st_ctime_usec}, and @var{st_blksize}. +@var{st_fstype}, @var{st_fsid}, @var{st_ino}, @var{st_atim}, +@var{st_mtim}, @var{st_ctim}, and @var{st_blksize}. @var{st_fstype}, @var{st_fsid}, and @var{st_ino} must be unique for the underlying object across the entire system. -@var{st_atime} and @var{st_atime_usec} hold the seconds and -microseconds, respectively, of the system clock at the last time the +@var{st_atim} holds the timestamp of the system clock at the last time the object was read with @code{io_read}. -@var{st_mtime} and @var{st_mtime_usec} hold the seconds and microseconds, -respectively, of the system clock at the last time the object was -written with @code{io_write}. +@var{st_mtim} holds the timestamp of the system clock at the last time the +object was written with @code{io_write}. -Other appropriate operations may update the @var{atime} and the -@var{mtime} as well; both the file and socket interfaces specify such +Other appropriate operations may update the @var{atim} and the +@var{mtim} as well; both the file and socket interfaces specify such operations. -@var{st_ctime} and @var{st_ctime_usec} hold the seconds and -microseconds, respectively, of the system clock at the last time +@var{st_ctim} holds the timestamp of the system clock at the last time permanent meta-data associated with the object was changed. The exact operations which cause such an update are server-dependent, but must include the creation of the object. @@ -3932,8 +3928,8 @@ If disk is not readonly and the noatime option is not enabled, set @deftypefun void diskfs_set_node_times (@w{struct node *@var{np}}) If @code{@var{np}->dn_set_ctime} is set, then modify -@code{@var{np}->dn_stat.st_ctime} appropriately; do the analogous -operations for atime and mtime as well. +@code{@var{np}->dn_stat.st_ctim} appropriately; do the analogous +operations for @code{st_atim} and @code{st_mtim} as well. @end deftypefun @deftypefun {struct node *} diskfs_check_lookup_cache (@w{struct node *@var{dir}}, @w{char *@var{name}}) |