From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] initramfs: fix boot with dynamic /dev
Date: Thu, 1 Sep 2011 09:18:42 +0200 [thread overview]
Message-ID: <20110901091842.784dbcf3@skate> (raw)
In-Reply-To: <201108240953.23168.arnout@mind.be>
Hello,
Le Wed, 24 Aug 2011 09:53:22 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> I now switched to a cpio that I use as an initrd and of course I
> encounter the same issue...
Ah, yes, of course.
> So we can do the same thing for cpio archives. Then I have two
> issues:
>
> - Are cpio archives used for something else than initrd?
I don't think so. I would say that we can assume that cpio archives are
always used for initramfs.
> - Clearly this should be refactored so we don't duplicate the same
> stuff in initramfs.mk and cpio.mk.
In fact I think the initramfs.mk and cpio.mk should be merged. Instead
of having initramfs.mk generating the "initramfs file list", we could
just have cpio.mk generate the cpio archive and then have the kernel
configuration tuned to include this cpio archive as an initramfs. I
haven't thought too much about the details of this but I remember we
already discussed this in the past and it's probably doable.
> 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?
Well, I'd prefer to keep it for the initramfs situation only. Not
because of the size, just for the sake of cleanliness and clarity.
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:[~2011-09-01 7:18 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
2011-09-01 7:18 ` Thomas Petazzoni [this message]
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=20110901091842.784dbcf3@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