diff options
| author |   Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-03-19 07:01:37 -0600 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-03-25 12:29:43 +0000 |
| commit | 128cdcf85d9f5d719bae8d641fe91f1db37dd8c9 (patch) | |
| tree | 8cf3c974572b6ead2034a193c963a679175749ab /documentation/dev-manual | |
| parent | 46a4fb250e12d9afaac7d6b4c1ac799f26971845 (diff) | |
| download | openembedded-core-contrib-128cdcf85d9f5d719bae8d641fe91f1db37dd8c9.tar.gz | |
dev-manual: Read-thru edits to "Creating a Read-Only Root Filesystem"
I changed the way I referenced the read-only-rootfs feature. Since
it is something on the right side of a variable equation, I decided
to not render it in a Courier font. I have quoted it.
(From yocto-docs rev: 90804e71e43cddd3ac7c194a677acaab0c866ed6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 23ea2df38e..5223aba158 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -5458,7 +5458,7 @@ <para> To create the read-only root filesystem, simply add the - <filename>read-only-rootfs</filename> feature to your image. + "read-only-rootfs" feature to your image. Using either of the following statements in your image recipe or from within the <filename>local.conf</filename> file found in the @@ -5494,13 +5494,13 @@ build on the host system. These scripts cannot attempt to run during first-boot on the target device. - With the <filename>read-only-rootfs</filename> feature enabled, + With the "read-only-rootfs" feature enabled, the build system checks during root filesystem creation to make sure all post-installation scripts succeed. If any of these scripts still need to be run after the root filesystem is created, the build immediately fails. These build-time checks ensure that the build fails - rather than the target device failing later during its + rather than the target device fails later during its initial boot operation. </para> @@ -5552,7 +5552,7 @@ <title>Areas With Write Access</title> <para> - With the <filename>read-only-rootfs</filename> feature enabled, + With the "read-only-rootfs" feature enabled, any attempt by the target to write to the root filesystem at runtime fails. Consequently, you must make sure that you configure processes |