From 128cdcf85d9f5d719bae8d641fe91f1db37dd8c9 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 19 Mar 2014 07:01:37 -0600 Subject: 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 Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 8 ++++---- 1 file 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 @@ To create the read-only root filesystem, simply add the - read-only-rootfs 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 local.conf 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 read-only-rootfs 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. @@ -5552,7 +5552,7 @@ Areas With Write Access - With the read-only-rootfs 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 -- cgit v1.2.3-54-g00ecf