From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] initramfs
Date: Mon, 18 Jun 2018 11:49:46 +0200 [thread overview]
Message-ID: <20180618094946.evuufmqncbqsol3h@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjxZi-XGegkghexnDxTnrMaCk_WSDemA-kZhJM7H4_O5pQ@mail.gmail.com>
Hi,
On Fri, Jun 15, 2018 at 12:37:11PM -0400, Jon Ringle wrote:
> In 4e8ea1703cad595f3136f0d48ae93de73a180c40 (remove obsolete and
> broken klibc/initramfs), I agree that klibc is broken and should be
> removed. However, I use initramfs. I have in the ptxconfig for
> building my kernel image:
> PTXCONF_INITMETHOD_INITRAMFS=y
> PTXCONF_INITRAMFS_TOOLS=y
> PTXCONF_INITRAMFS_SPEC=y
> PTXCONF_INITRAMFS_SPEC_FILE="${PTXDIST_WORKSPACE}/configs/ec1k-kernel/initramfs_spec"
> PTXCONF_INITRAMFS_TOOLS_SCRIPTS_INIT=y
> PTXCONF_INITRAMFS_TOOLS_SCRIPTS_LOCAL=y
> PTXCONF_INITRAMFS_TOOLS_SCRIPTS_NFS=y
>
> Would you accept a patch that restores this functionality?
Probably not, there should be a better way to do this.
What exactly is in your initramfs?
If it's the whole rootfs, then just use the option you found. See my other
mail.
If not, then you can create a new image for your initramfs and overwrite
the image-kernel rule to use that instead.
Take a look at the documentation section I've just pushed. The use-case is
different, but it should give you some ideas about creating a new image.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-06-18 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 16:37 Jon Ringle
2018-06-18 9:49 ` Michael Olbrich [this message]
2018-06-18 12:11 ` Jon Ringle
2018-06-19 14:31 ` Michael Olbrich
2018-06-29 20:07 ` Jon Ringle
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=20180618094946.evuufmqncbqsol3h@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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