diff options
-rw-r--r-- | documentation/sdk-manual/sdk-extensible.xml | 14 |
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> |