From 65f66c170e6703cf1b75574e7aabea1302f51c50 Mon Sep 17 00:00:00 2001 From: "Arnout Vandecappelle (Essensium/Mind)" Date: Tue, 27 Nov 2012 11:59:17 +0000 Subject: manual: various fixes Various consistency and correctness improvements. Also removing some sentences that are not or no longer relevant. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Acked-by: Samuel Martin Signed-off-by: Peter Korsgaard --- docs/manual/faq-troubleshooting.txt | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'docs/manual/faq-troubleshooting.txt') diff --git a/docs/manual/faq-troubleshooting.txt b/docs/manual/faq-troubleshooting.txt index fc75d6627..5a227028e 100644 --- a/docs/manual/faq-troubleshooting.txt +++ b/docs/manual/faq-troubleshooting.txt @@ -98,7 +98,7 @@ deal with expressing the dependencies of this package. In the +Config.in+ file, dependencies may be expressed following two semantics. -See xref:depends-on-vs-select[]. +See xref:depends-on-vs-select[choosing between _depends_ and _select_]. [[faq-why-not-visible-package]] Why are some packages not visible in the Buildroot config menu? @@ -131,4 +131,8 @@ one, among these: * device nodes are not created in the target directory. For these reasons, commands run through chroot, using the target -directory as the new root, would fail. +directory as the new root, will most likely fail. + +If you want to run the target filesystem inside a chroot, or as an NFS +root, then use the tarball image generated in +images/+ and extract it +as root. -- cgit v1.2.3