From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] initramfs disabling
Date: Wed, 8 Sep 2010 09:46:11 +0200 [thread overview]
Message-ID: <20100908094611.4b3bf5ea@surf> (raw)
In-Reply-To: <AANLkTim3kn-otz-=x4DsPWEWgvDk=uqLE-X415W7BK6O@mail.gmail.com>
On Wed, 8 Sep 2010 11:05:58 +0400
Sergey Naumov <sknaumov@gmail.com> wrote:
> I want to ask why disabling the option about initrd integration into
> the kernel image leads to disabling of initrd support in the kernel.
> The description of this option tells nothing about disabling initramfs
> support. What I should do if I want separate hand-made initramfs
> image? Unfortunately, it leads to editing internal makefiles of
> buildroot. Can you introduce "FORCE" option in buildroot that forbid
> buildroot to edit kernel and uclibc configuration?
It's true that there no reason why we should forcefully disable the
initramfs in the kernel configuration when initramfs has not been
selected as the root filesystem: we should keep the kernel
configuration as it is, leaving the possibility for the user to
manually manage his initramfs.
Does the following fix works for you :
http://git.buildroot.net/~tpetazzoni/git/buildroot/commit/?h=for-2010.11/dont-force-no-initramfs&id=350e6d2ca811cb5fedc007f92aa6c17fbbca82d0
?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-09-08 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 7:05 [Buildroot] initramfs disabling Sergey Naumov
2010-09-08 7:46 ` Thomas Petazzoni [this message]
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=20100908094611.4b3bf5ea@surf \
--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