diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index ffed3e2728..c59e8e45b7 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -6574,18 +6574,6 @@
or
oe-init-build-env-memres).
- Prepare your local configuration file:
- Toaster needs the
- toaster
- class enabled
- in Bitbake in order to record target image package
- information.
- You can enable it by adding the following line to your
- conf/local.conf file:
-
- INHERIT += "toaster"
-
- Start Toaster:
Start the Toaster service using this
command from within your
@@ -6643,8 +6631,7 @@
tool from the shell and pass it the same URL.
- Either method opens the home page for the Toaster interface,
- which is temporary for this release.
+ Either method opens the home page for the Toaster interface.
Notes
@@ -6678,50 +6665,24 @@
You can click on any build to see related information.
This information includes configuration details, information
about tasks, all recipes and packages built and their
- dependencies, packages installed in your final image,
+ dependencies, packages and their directory structure as
+ installed in your final image,
execution time, CPU usage and disk I/O per task.
- The home page of the interface into the database organizes
- builds into areas:
-
- Recent successful builds, which appear
- in row format in a green area.
- Recent failed builds, which appear
- in row format in a red area.
- Recent builds in progress, which appear
- in row format in a yellow area.
- All builds, which appear in row format at
- the end of the page.
-
+ For details on the interface, see the
+ Toaster Manual.
-
-
- Each entry is linked to more detail on the particular build
- or recipe.
- You can click on the links to learn more information.
-
-
-
- When you click on a failed recipe link, you can find out
- information such as the work directory, the pathname to the
- failing recipe, the exact error message, and precursor tasks.
-
-
-
- Clicking on a successful build provides you with configuration,
- task, and package information along with directory structure,
- build time, CPU usage, and disk I/O information.
-
-
Stopping Toaster
- Stop the Toaster service with the following command:
+ Stop the Toaster service with the following command
+ from with the
+ Build Directory:
$ source toaster stop