Module: xenomai-jki
Branch: for-forge
Commit: 90dfc3fa9bc324b587832247a82d02412391e95a
URL:    
http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=90dfc3fa9bc324b587832247a82d02412391e95a

Author: Jan Kiszka <jan.kis...@siemens.com>
Date:   Thu Nov 27 16:47:13 2014 +0100

copperplate/registry: Switch to /var/run as default mountpoint root

Creating directories in a user/admin-owned and typically persistent
filesystem for the purpose of mounting volatile filesystems on top is
a suboptimal default. Today /run should be used for such purposes, but
older distros may only expose the current FHS standard /var/run. So use
that instead.

This comes with the advantage that we will now typically work against
tmpfs, thus won't stumble if / is read-only.

Signed-off-by: Jan Kiszka <jan.kis...@siemens.com>

---

 configure.ac                          |    2 +-
 doc/asciidoc/MIGRATION.adoc           |    2 +-
 doc/asciidoc/README.APPLICATIONS.adoc |    6 +++---
 doc/asciidoc/README.INSTALL.adoc      |    4 ++--
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/configure.ac b/configure.ac
index 6077960..05c4241 100644
--- a/configure.ac
+++ b/configure.ac
@@ -295,7 +295,7 @@ AC_MSG_CHECKING(whether the registry should be enabled)
 AC_ARG_ENABLE(registry,
        AS_HELP_STRING([--enable-registry], [Export real-time objects to a 
registry]),
        [case "$enableval" in
-       y | yes) use_registry=yes; registry_root=/mnt/xenomai ;;
+       y | yes) use_registry=yes; registry_root=/var/run/xenomai ;;
        /*) use_registry=yes; registry_root=$enableval ;;
        *) unset use_registry ;;
        esac])
diff --git a/doc/asciidoc/MIGRATION.adoc b/doc/asciidoc/MIGRATION.adoc
index c837925..72206bf 100644
--- a/doc/asciidoc/MIGRATION.adoc
+++ b/doc/asciidoc/MIGRATION.adoc
@@ -104,7 +104,7 @@ filesystem.  The hierarchy of the Xenomai registry is 
organized as
 follows:
 
 ----------------------------------------------------------------------------   
 
-    /mount-point            /* registry fs root, defaults to /mnt/xenomai */
+    /mount-point            /* registry fs root, defaults to /var/run/xenomai*/
         /session            /* shared session name or "anon" */
             /pid            /* application (main) pid */
                /skin        /* API name: alchemy/vxworks/psos/... */
diff --git a/doc/asciidoc/README.APPLICATIONS.adoc 
b/doc/asciidoc/README.APPLICATIONS.adoc
index 6cf353a..f775918 100644
--- a/doc/asciidoc/README.APPLICATIONS.adoc
+++ b/doc/asciidoc/README.APPLICATIONS.adoc
@@ -72,7 +72,7 @@ link:installing-xenomai-3-x[configuration switch]).
 *--registry-root=<path>*::
 
        Tells Xenomai to root the object registry at the given path,
-       instead of +/mnt/xenomai+ by default (see the
+       instead of +/var/run/xenomai+ by default (see the
        +--enable-registry+ switch from the configuration options).
 
 *--shared-registry*::
@@ -85,7 +85,7 @@ link:installing-xenomai-3-x[configuration switch]).
 *--no-registry*::
 
        This switch disables registry support at runtime. No real-time
-       objects will be exported to +/mnt/xenomai/<session>/<pid>+,
+       objects will be exported to +/var/run/xenomai/<session>/<pid>+,
        despite the registry code was compiled in.
 
 *--no-sanity*::
@@ -118,7 +118,7 @@ link:installing-xenomai-3-x[configuration switch]).
 
 [normal]
        This label is also used to form the registry mount point for
-       each process, e.g. +/mnt/xenomai/<session>/<pid>+. See
+       each process, e.g. +/var/run/xenomai/<session>/<pid>+. See
        +--enable-registry+ from the build options.
 
 [normal]
diff --git a/doc/asciidoc/README.INSTALL.adoc b/doc/asciidoc/README.INSTALL.adoc
index 07cae06..445b0d9 100644
--- a/doc/asciidoc/README.INSTALL.adoc
+++ b/doc/asciidoc/README.INSTALL.adoc
@@ -413,14 +413,14 @@ Generic configuration options (both cores)
 
 [normal]
        When this option is enabled, the system creates a file
-       hierachy under `/mnt/xenomai/<session>/<pid>` (by default),
+       hierachy under `/var/run/xenomai/<session>/<pid>` (by default),
        where you can access the internal state of the active
        real-time objects. The session label is obtained from the
        --session runtime switch. E.g. looking at the properties of a
        VxWorks task could be done as follows:
 
 --------------------------------------------------------------------
-               $ cat /mnt/xenomai/anon/12656/vxworks/tasks/windTask 
+               $ cat /var/run/xenomai/anon/12656/vxworks/tasks/windTask
                name       = windTask
                errno      = 0
                status     = ready


_______________________________________________
Xenomai-git mailing list
Xenomai-git@xenomai.org
http://www.xenomai.org/mailman/listinfo/xenomai-git

Reply via email to