summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2018-05-31 13:57:16 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-06-15 11:26:46 +0100
commit73d00d17fb910c621b9574994293777edc212dbc (patch)
tree7fc7dd48e64e242ce444fcab1d9fca174144dcc5 /documentation
parentd527a5f7ab1fe120cb1bb1cca8b74f12dd5ed0d8 (diff)
downloadpoky-73d00d17fb910c621b9574994293777edc212dbc.tar.gz
sdk-manual: Edits to "Restoring the Target Device to its Original State"
Fixed a grammar error and made a few other corrections. (From yocto-docs rev: 369a22ffe3780fd00514344f1b3b8a944305e320) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/sdk-manual/sdk-extensible.xml14
1 files changed, 7 insertions, 7 deletions
diff --git a/documentation/sdk-manual/sdk-extensible.xml b/documentation/sdk-manual/sdk-extensible.xml
index 5df700bee8..bc77bed86c 100644
--- a/documentation/sdk-manual/sdk-extensible.xml
+++ b/documentation/sdk-manual/sdk-extensible.xml
@@ -1648,29 +1648,29 @@
1648 <filename>devtool deploy-target</filename> command. 1648 <filename>devtool deploy-target</filename> command.
1649 Because the <filename>devtool deploy-target</filename> command 1649 Because the <filename>devtool deploy-target</filename> command
1650 backs up any files it overwrites, you can use the 1650 backs up any files it overwrites, you can use the
1651 <filename>devtool undeploy-target</filename> to restore those files 1651 <filename>devtool undeploy-target</filename> command to restore
1652 and remove any other files the recipe deployed. 1652 those files and remove any other files the recipe deployed.
1653 Consider the following example: 1653 Consider the following example:
1654 <literallayout class='monospaced'> 1654 <literallayout class='monospaced'>
1655 $ devtool undeploy-target lighttpd root@192.168.7.2 1655 $ devtool undeploy-target lighttpd root@192.168.7.2
1656 </literallayout> 1656 </literallayout>
1657 If you have deployed multiple applications, you can remove them 1657 If you have deployed multiple applications, you can remove them
1658 all at once thus restoring the target device back to its 1658 all using the "-a" option thus restoring the target device to its
1659 original state: 1659 original state:
1660 <literallayout class='monospaced'> 1660 <literallayout class='monospaced'>
1661 $ devtool undeploy-target -a root@192.168.7.2 1661 $ devtool undeploy-target -a root@192.168.7.2
1662 </literallayout> 1662 </literallayout>
1663 Information about files deployed to the target as well as any 1663 Information about files deployed to the target as well as any
1664 backed up files are stored on the target itself. 1664 backed up files are stored on the target itself.
1665 This storage of course requires some additional space 1665 This storage, of course, requires some additional space
1666 on the target machine. 1666 on the target machine.
1667 <note> 1667 <note>
1668 The <filename>devtool deploy-target</filename> and 1668 The <filename>devtool deploy-target</filename> and
1669 <filename>devtool undeploy-target</filename> command do not 1669 <filename>devtool undeploy-target</filename> commands do not
1670 currently interact with any package management system on the 1670 currently interact with any package management system on the
1671 target device (e.g. RPM or OPKG). 1671 target device (e.g. RPM or OPKG).
1672 Consequently, you should not intermingle operations 1672 Consequently, you should not intermingle
1673 <filename>devtool deploy-target</filename> and the package 1673 <filename>devtool deploy-target</filename> and package
1674 manager operations on the target device. 1674 manager operations on the target device.
1675 Doing so could result in a conflicting set of files. 1675 Doing so could result in a conflicting set of files.
1676 </note> 1676 </note>