X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;ds=sidebyside;f=man%2Ffile-hierarchy.xml;h=b0d0e97ee745c66dffbadb18039fb8ab683964e8;hb=9fc25924bef99b3bb522dff785fa56a8e886cb2f;hp=ff2ee3d4bb030e2c7800f1a6ae0a1e97670c3e97;hpb=9546c6ed678bf8fbb93b9be620c9727b0e3d58ae;p=elogind.git
diff --git a/man/file-hierarchy.xml b/man/file-hierarchy.xml
index ff2ee3d4b..b0d0e97ee 100644
--- a/man/file-hierarchy.xml
+++ b/man/file-hierarchy.xml
@@ -130,7 +130,13 @@
network file systems, hence
applications should not assume the
full set of file API is available on
- this directory.
+ this directory. Applications should
+ generally not reference this directory
+ directly, but via the per-user
+ $HOME environment
+ variable, or via the home directory
+ field of the user
+ database.
@@ -165,7 +171,9 @@
usually mounted as
tmpfs instance, and
should hence not be used for larger
- files. Since the directory is
+ files. (Use
+ /var/tmp for
+ larger files.) Since the directory is
accessible to other users of the
system it is essential that this
directory is only written to with the
@@ -175,7 +183,13 @@
usually flushed at boot-up. Also,
files that are not accessed within a
certain time are usually automatically
- deleted.
+ deleted. If applications find the
+ environment variable
+ $TMP set they
+ should prefer using the directory
+ specified in it over directly
+ referencing
+ /tmp.
@@ -278,11 +292,13 @@
Secondary library
directory for placing 64bit versions
of system libraries in, if the primary
- architecture of the system is
- 32bit. This directory should not be
- used for package-specific data, unless
- this data requires 64bit-specific
- versions, too.
+ architecture of the system is 32bit,
+ and /usr/lib64 is
+ defined in the platform ABI. This
+ directory should not be used for
+ package-specific data, unless this
+ data requires 64bit-specific versions,
+ too.
@@ -291,7 +307,11 @@
betwen multiple packages, such as
documentation, man pages, time zone
information, fonts and other
- resources.
+ resources. Usually, the precise
+ location and format of files stored
+ below this directory is subject to
+ specifications that ensure
+ interoperability.
@@ -403,18 +423,26 @@
contrast to /tmp
this directory is usually mounted from
a persistent physical file system and
- can thus accept larger files. This
- directory is generally not flushed at
- boot-up, but time-based cleanup of
- files that have not been accessed for
- a certain time is applied. The same
- security restrictions as with
+ can thus accept larger files. (Use
+ /tmp for smaller
+ files.) This directory is generally
+ not flushed at boot-up, but time-based
+ cleanup of files that have not been
+ accessed for a certain time is
+ applied. The same security
+ restrictions as with
/tmp apply, and
hence only
mkstemp3,
mkdtemp3
or similar calls should be used to
- make use of this directory.
+ make use of this directory. If
+ applications find the environment
+ variable $TMP set
+ they should prefer using the directory
+ specified in it over directly
+ referencing
+ /var/tmp.
@@ -607,7 +635,7 @@
/usr/lib64
- Public shared libraries of the package, compiled for the secondary, 64bit architecture, if this is part of the Operating System ABI.
+ Public shared libraries of the package, compiled for the secondary, 64bit architecture, if this is part of the platform ABI of the architecture.
/usr/lib64/package