From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] initramfs: fix boot with dynamic /dev
Date: Wed, 24 Aug 2011 09:53:22 +0200 [thread overview]
Message-ID: <201108240953.23168.arnout@mind.be> (raw)
In-Reply-To: <20110720150418.E95188B391@busybox.osuosl.org>
On Wednesday 20 July 2011 16:30:14, Peter Korsgaard wrote:
> Devtmpfs (which is used by devtmpfs/mdev/udev options) doesn't get
> automounted by the kernel when an initramfs is used, causing boot
> failures when a dynamic /dev is used.
[Reviving an old issue]
I now switched to a cpio that I use as an initrd and of course I encounter
the same issue... So we can do the same thing for cpio archives. Then I have
two issues:
- Are cpio archives used for something else than initrd? In that case, we
shouldn't use this /init. OTOH, /init is never used if it's not an initrd so
it shouldn't really make a difference.
- Clearly this should be refactored so we don't duplicate the same stuff in
initramfs.mk and cpio.mk.
Given that /init is only used in initramfs situations, why don't we create it
unconditionally as part of the .root skeleton? OK, it adds 4K to the ext2fs
but that shouldn't be the issue, right?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110824/7aff7e70/attachment.html>
next prev parent reply other threads:[~2011-08-24 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 14:30 [Buildroot] [git commit] initramfs: fix boot with dynamic /dev Peter Korsgaard
2011-07-20 16:12 ` Michael S. Zick
2011-07-20 17:43 ` Peter Korsgaard
2011-08-24 7:53 ` Arnout Vandecappelle [this message]
2011-09-01 7:18 ` Thomas Petazzoni
2011-09-01 16:18 ` 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=201108240953.23168.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