Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH for-2012.11 2/4] manual: more warnings to not use output/target
Date: Tue, 27 Nov 2012 09:30:11 +0100	[thread overview]
Message-ID: <1354005013-28626-2-git-send-email-arnout@mind.be> (raw)
In-Reply-To: <1354005013-28626-1-git-send-email-arnout@mind.be>

From: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
 .topdeps              |    2 +-
 .topmsg               |   16 +---------------
 docs/manual/using.txt |    3 ++-
 3 files changed, 4 insertions(+), 17 deletions(-)

diff --git a/.topdeps b/.topdeps
index 1f7391f..d46ee1c 100644
--- a/.topdeps
+++ b/.topdeps
@@ -1 +1 @@
-master
+t/manual
diff --git a/.topmsg b/.topmsg
index f070122..367c0df 100644
--- a/.topmsg
+++ b/.topmsg
@@ -1,18 +1,4 @@
 From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
-Subject: [PATCH] manual: various fixes
-
-Various minor linguistic fixes and consistency and correctness
-improvements.
-
-Also removing some sentences that are not or no longer relevant.
+Subject: [PATCH] manual: more warnings to not use output/target
 
 Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
----
-Since you need a lot of context to review documentation, I increased the
-context to 5 lines.
-
-I originally planned to include only trivial fixes, but there turn
-out to be a few more invasive changes. If necessary, I can split the
-patch into trivial and potentially-controversial. I haven't done that
-yet because I wanted to get this patch out ASAP for the 2012.11 release.
-Unless I get some ACKs earlier, I'll split the patch tomorrow.
diff --git a/docs/manual/using.txt b/docs/manual/using.txt
index 6e144d0..857aa33 100644
--- a/docs/manual/using.txt
+++ b/docs/manual/using.txt
@@ -86,7 +86,8 @@ This directory contains several subdirectories:
 * +target/+ which contains 'almost' the complete root filesystem for
   the target: everything needed is present except the device files in
   +/dev/+ (Buildroot can't create them because Buildroot doesn't run
-  as root and doesn't want to run as root). Therefore, this directory
+  as root and doesn't want to run as root). Also, it doesn't have the correct
+  permissions (e.g. setuid for the busybox binary). Therefore, this directory
   *should not be used on your target*.  Instead, you should use one of
   the images built in the +images/+ directory. If you need an
   extracted image of the root filesystem for booting over NFS, then
-- 
1.7.10.4

  reply	other threads:[~2012-11-27  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27  8:30 [Buildroot] [PATCH for-2012.11 1/4] manual: various fixes Arnout Vandecappelle
2012-11-27  8:30 ` Arnout Vandecappelle [this message]
2012-11-27  8:30 ` [Buildroot] [PATCH for-2012.11 3/4] manual: give example where _INSTALL_TARGET = NO Arnout Vandecappelle
2012-11-27  8:30 ` [Buildroot] [PATCH for-2012.11 4/4] manual: restructure 'Adding packages' chapter Arnout Vandecappelle
2012-11-27  9:55 ` [Buildroot] [PATCH for-2012.11 1/4] manual: various fixes Thomas Petazzoni
2012-11-27 20:03   ` Arnout Vandecappelle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1354005013-28626-2-git-send-email-arnout@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox