mirror of
https://git.yoctoproject.org/poky
synced 2026-06-01 13:09:50 +00:00
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: 22c2f0643975b620fb543b651eae7c510b141770) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
162db35c6b
commit
0caf1dc925
@@ -1648,29 +1648,29 @@
|
|||||||
<filename>devtool deploy-target</filename> command.
|
<filename>devtool deploy-target</filename> command.
|
||||||
Because the <filename>devtool deploy-target</filename> command
|
Because the <filename>devtool deploy-target</filename> command
|
||||||
backs up any files it overwrites, you can use the
|
backs up any files it overwrites, you can use the
|
||||||
<filename>devtool undeploy-target</filename> to restore those files
|
<filename>devtool undeploy-target</filename> command to restore
|
||||||
and remove any other files the recipe deployed.
|
those files and remove any other files the recipe deployed.
|
||||||
Consider the following example:
|
Consider the following example:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ devtool undeploy-target lighttpd root@192.168.7.2
|
$ devtool undeploy-target lighttpd root@192.168.7.2
|
||||||
</literallayout>
|
</literallayout>
|
||||||
If you have deployed multiple applications, you can remove them
|
If you have deployed multiple applications, you can remove them
|
||||||
all at once thus restoring the target device back to its
|
all using the "-a" option thus restoring the target device to its
|
||||||
original state:
|
original state:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ devtool undeploy-target -a root@192.168.7.2
|
$ devtool undeploy-target -a root@192.168.7.2
|
||||||
</literallayout>
|
</literallayout>
|
||||||
Information about files deployed to the target as well as any
|
Information about files deployed to the target as well as any
|
||||||
backed up files are stored on the target itself.
|
backed up files are stored on the target itself.
|
||||||
This storage of course requires some additional space
|
This storage, of course, requires some additional space
|
||||||
on the target machine.
|
on the target machine.
|
||||||
<note>
|
<note>
|
||||||
The <filename>devtool deploy-target</filename> and
|
The <filename>devtool deploy-target</filename> and
|
||||||
<filename>devtool undeploy-target</filename> command do not
|
<filename>devtool undeploy-target</filename> commands do not
|
||||||
currently interact with any package management system on the
|
currently interact with any package management system on the
|
||||||
target device (e.g. RPM or OPKG).
|
target device (e.g. RPM or OPKG).
|
||||||
Consequently, you should not intermingle operations
|
Consequently, you should not intermingle
|
||||||
<filename>devtool deploy-target</filename> and the package
|
<filename>devtool deploy-target</filename> and package
|
||||||
manager operations on the target device.
|
manager operations on the target device.
|
||||||
Doing so could result in a conflicting set of files.
|
Doing so could result in a conflicting set of files.
|
||||||
</note>
|
</note>
|
||||||
|
|||||||
Reference in New Issue
Block a user