From: Andrew Ruder <andy@aeruder.net>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH] fs/common.mk: Add support for fakeroot script
Date: Fri, 18 Oct 2013 16:35:04 -0500 [thread overview]
Message-ID: <20131018213504.GA23840@gmail.com> (raw)
In-Reply-To: <20131018204920.GA4019@free.fr>
On Fri, Oct 18, 2013 at 10:49:20PM +0200, Yann E. MORIN wrote:
> Or you could have had a look at the manual:
> http://buildroot.net/downloads/manual/manual.html#makedev-syntax
>
> The first sentence in this section reads:
Yes, taken out of context it looks perfect, but put the whole sentence
in there and it sounds like it is specifically for device node creation.
> The makedev syntax is used in several places in Buildroot to define
> changes to be made for permissions, or which device files to create
> and how to create them, ***in order to avoid calls to mknod.***
Emphasis mine, of course.
- Andy
next prev parent reply other threads:[~2013-10-18 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 13:21 [Buildroot] [RFC PATCH] fs/common.mk: Add support for fakeroot script Andrew Ruder
2013-10-15 14:19 ` Thomas Petazzoni
2013-10-18 20:23 ` Andrew Ruder
2013-10-18 20:49 ` Yann E. MORIN
2013-10-18 21:35 ` Andrew Ruder [this message]
2013-10-18 22:07 ` Yann E. MORIN
2013-10-27 9:30 ` 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=20131018213504.GA23840@gmail.com \
--to=andy@aeruder.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.