summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Johns <chrisj@rtems.org>2017-03-21 14:21:15 +1100
committerChris Johns <chrisj@rtems.org>2017-03-21 14:22:46 +1100
commitd8795ef2863493509cb34a689e3b6f04b047b416 (patch)
treeb733d65f25e8f21306cadbf5d67fc722d93acc0c
parent10874b0937182b6bbe4a7b2892391fa4bd138c07 (diff)
downloadrtems-docs-d8795ef2863493509cb34a689e3b6f04b047b416.tar.bz2
rsb: Fix the path to the tar for the untar with strip option.
The change is different to the ticket because the example is about coping and deploying the build on a different machine. Closes #2324.
-rw-r--r--rsb/quick-start.rst11
1 files changed, 6 insertions, 5 deletions
diff --git a/rsb/quick-start.rst b/rsb/quick-start.rst
index e3696a5..f39c0a6 100644
--- a/rsb/quick-start.rst
+++ b/rsb/quick-start.rst
@@ -378,14 +378,15 @@ the tar file somewhere and copy the file tree from the level you have write
access from. Embedding the full prefix path in the tar files lets you know what
the prefix is and is recommended. For example if
``/home/chris/development/rtems/4.11`` is the prefix used you cannot change
-directory to the root (``/``) and install because the ``/home`` is root access
-only. To install you would:
+directory to the root (``/``) and untar the file because the ``/home`` is root
+access only. To install a tar file you have downloaded into your new machine's
+``Downloads`` directory in your home directoty you would enter:
.. code-block:: shell
- $ cd
- $ tar --strip-components=3 -xjf rtems-4.11-sparc-rtems4.11-1.tar.bz2
-
+ $ cd /somewhere
+ $ tar --strip-components=3 -xjf \
+ $HOME/Downloads/rtems-4.11-sparc-rtems4.11-1.tar.bz2
A build set tar file is created by adding ``--bset-tar-file`` option to the
``sb-set-builder`` command::