Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Warn the user about the usage of output/target as the root filesystem
Date: Sat, 17 Nov 2012 10:59:41 -0300	[thread overview]
Message-ID: <50A7984D.2050602@zacarias.com.ar> (raw)
In-Reply-To: <1353160334-30174-1-git-send-email-thomas.petazzoni@free-electrons.com>

On 11/17/2012 10:52 AM, Thomas Petazzoni wrote:

> A very common mistake done by our users is that they use
> output/target/ directory as their root filesystem. Even though this is
> loudly documented in our Buildroot manual, people don't read
> documentation, so it is not sufficient.
> 
> This patch adds a text file named
> output/target/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM which explains why
> output/target isn't appropriate to use as the root filesystem. The
> process is:
> 
>  * At the beginning of the build, right after the skeleton has been
>    copied, support/misc/target-dir-warning.txt is copied to
>    output/target/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM
> 
>  * In the filesystem images creation code, this file is removed before
>    launching fakeroot, and restored right after that, so that this
>    file is not present in the generated root filesystem images.
> 
> Note that the file has not been added to the default skeleton for two
> reasons:
> 
>  * It would have annoying to have in our source tree a file named in
>    capital letters inside system/skeleton/
> 
>  * The proposed way works even if the user uses a custom skeleton.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Juha Lumme <juha.lumme@gmail.com>

Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar>

  reply	other threads:[~2012-11-17 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17 13:52 [Buildroot] [PATCH] Warn the user about the usage of output/target as the root filesystem Thomas Petazzoni
2012-11-17 13:59 ` Gustavo Zacarias [this message]
2012-11-17 14:03 ` Richard Braun
2012-11-17 16:13 ` Peter Korsgaard

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=50A7984D.2050602@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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