From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] debugging inittab
Date: Thu, 29 Aug 2013 10:31:26 +0200 [thread overview]
Message-ID: <20130829103126.7bcbf18a@skate> (raw)
In-Reply-To: <521ED985.9050705@mind.be>
Dear Arnout Vandecappelle,
On Thu, 29 Aug 2013 07:17:57 +0200, Arnout Vandecappelle wrote:
> > That was the problem. Thanks!
>
> Right. Maybe we should just rename target/ to
> THIS_IS_NOT_YOUR_ROOT_FILESYSTEM instead of just creating the file. The
> latter is obviously not enough.
>
> What was the reason we didn't do that in the first place?
I personally find it a bit ugly. Moreover, having a file allows to add
contents to explain *why* it is not the root filesystem, while a
directory cannot contain an explanation :)
Since we've added the THIS_IS_NOT_YOUR_ROOT_FILESYSTEM file, this is
the *first* time we have a new report of people using output/target
directly for NFS mounting. At this point, with a file with such a name,
and the contents of the file explaining how to do NFS mounting, I think
there's not much else we can do except pointing users at this file
which documents why what they are doing cannot work.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-29 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 20:11 [Buildroot] debugging inittab Jenkins, Lee
2013-08-22 23:36 ` Arnout Vandecappelle
2013-08-27 22:38 ` Jenkins, Lee
2013-08-29 5:17 ` Arnout Vandecappelle
2013-08-29 7:29 ` Peter Korsgaard
2013-08-29 7:39 ` Arnout Vandecappelle
2013-08-29 8:45 ` Peter Korsgaard
2013-08-29 8:31 ` Thomas Petazzoni [this message]
2013-08-29 10:14 ` 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=20130829103126.7bcbf18a@skate \
--to=thomas.petazzoni@free-electrons.com \
--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