Modified the documentation on customizing a rootfs to be less ambiguous
PATCH 1/1 Modified the documentation on customizing a rootfs to be less ambiguous
From: Jeff Stewart <[email protected]>
While reading the documentation I was a little confused over the recommended method for customizing the target file system. After sorting it out in the IRC channel, I modified the documentation to be a little less ambiguous.
--- docs/manual/customize-rootfs.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
docs/manual/customize-rootfs.txt +3 -3
@@ -23,7 +23,7 @@ there are a few ways to customize the resulting target filesystem. over the target filesystem after it has been built. Set +BR2_ROOTFS_OVERLAY+ to the top of the tree. +.git+, +.svn+, +.hg+ directories, +.empty+ files and files ending with +~+ are excluded. - _Among these first 3 methods, this one should be preferred_. + _Among the customization methods, this one should be preferred_. * In the Buildroot configuration, you can specify the paths to one or more *post-build scripts*. These scripts are called in the given order,
@@ -56,8 +56,8 @@ there are a few ways to customize the resulting target filesystem. installation. Note that this method is *not recommended*, as it duplicates the entire skeleton, which prevents from taking advantage of the fixes or improvements brought to the default Buildroot - skeleton. The recommended method is to use the _post-build scripts_ - mechanism described in the previous item. + skeleton. The _post-build scripts_ mechanism described in the previous + item is recommend over this mechanism. Note also that you can use the *post-image scripts* if you want to perform some specific actions 'after' all
Signature · 1 line
1.7.10.4
PATCH 1/1 Modified the documentation on customizing a rootfs to be less ambiguous
Quoted 25 lines · On 02/09/14 22:10, jeffball59 at gmail.com wrote:
From: Jeff Stewart <[email protected]>
While reading the documentation I was a little confused over the recommended method for customizing the target file system. After sorting it out in the IRC channel, I modified the documentation to be a little less ambiguous.
Signed-off-by Jeff Stewart <[email protected]>--- docs/manual/customize-rootfs.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)docs/manual/customize-rootfs.txt +1
-1@@ -23,7 +23,7 @@ there are a few ways to customize the resulting target filesystem. over the target filesystem after it has been built. Set +BR2_ROOTFS_OVERLAY+ to the top of the tree. +.git+, +.svn+, +.hg+ directories, +.empty+ files and files ending with +~+ are excluded. - _Among these first 3 methods, this one should be preferred_. + _Among the customization methods, this one should be preferred_. * In the Buildroot configuration, you can specify the paths to one or more *post-build scripts*. These scripts are called in the given order,
docs/manual/customize-rootfs.txt there are a few ways to customize the resulting target filesystem. · line 59
Quoted 6 lines
docs/manual/customize-rootfs.txt +1
-2@@ -56,8 +56,8 @@ there are a few ways to customize the resulting target filesystem. installation. Note that this method is *not recommended*, as it duplicates the entire skeleton, which prevents from taking advantage of the fixes or improvements brought to the default Buildroot - skeleton. The recommended method is to use the _post-build scripts_ - mechanism described in the previous item. + skeleton. The _post-build scripts_ mechanism described in the previous
Actually it's the ROOTFS_OVERLAY that should be recommended.
Regards,
Arnout
Quoted 5 lines
docs/manual/customize-rootfs.txt +1
-0+ item is recommend over this mechanism. Note also that you can use the *post-image scripts* if you want to perform some specific actions 'after' all
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F