From: Dan Moulding <dan.moulding@rackwareinc.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Create /dev/null device node when building a cpio rootfs
Date: Tue, 29 Apr 2014 13:18:51 -0600 (MDT) [thread overview]
Message-ID: <1398799131.565731726@apps.rackspace.com> (raw)
In-Reply-To: <535FF178.2090507@mind.be>
On Tuesday, April 29, 2014 12:37pm, "Arnout Vandecappelle" <arnout@mind.be> said:
>
> How is this issue limited to the cpio rootfs? You'll have the same issue
> with any rootfs, right?
Absolutely. But it was only making /dev/console for cpio... so I decided to follow suit, thinking maybe there was a good reason for it.
>
> So perhaps a better solution is to move /dev/console and /dev/null from
> device_table_dev.txt to device_table.txt.
>
Agreed.
> IOW this approach was suggested before but not really picked up.
>
Yes. And in fact, I had stumbled upon these past discussions when Googling about this. I just wasn't sure why it never got picked up.
Cheers,
-- Dan
next prev parent reply other threads:[~2014-04-29 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 15:12 [Buildroot] [PATCH] Create /dev/null along with /dev/console when building cpio rootfs Dan Moulding
2014-04-29 15:12 ` [Buildroot] [PATCH] Create /dev/null device node when building a " Dan Moulding
2014-04-29 18:37 ` Arnout Vandecappelle
2014-04-29 19:18 ` Dan Moulding [this message]
2014-07-16 19:07 ` Thomas Petazzoni
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=1398799131.565731726@apps.rackspace.com \
--to=dan.moulding@rackwareinc.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