From: Andrei Borzenkov <arvidjaar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Rick Tillery <rtillerywork-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Andrew Udvare <audvare-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Minimal initramfs Modification
Date: Mon, 27 Jul 2015 07:10:58 +0300 [thread overview]
Message-ID: <20150727071058.52eedf20@opensuse.site> (raw)
In-Reply-To: <CAAZEOjsavzT1GsBMENe9AbHYDUhrhbS5OWaZ4tpuqe7383GO3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
В Fri, 24 Jul 2015 10:26:10 -0500
Rick Tillery <rtillerywork-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> пишет:
>
> It's at that point that I looked closer at dracut. It appears to be
> able to successfully construct the initrd from the existing
> environment. Additionally, dracut recognizes the entire image,
> including the early_cpio portion (which likewise must be recognized by
> grub (2?) as well), when used to examine the initrd/initramfs file.
>
Bootloaders do not care about content of initrd, they just load it in
memory and pass pointer to kernel.
> So back to my original question, can dracut build the image from an
> existing image (possibly unarchived as above), with changes, and
> including the early_cpio portion?
It is not implemented.
> And if not, before I go trying to
> create my own scripts, are there are there any tools that can do this?
>
Not that I'm aware of. I have the same issue every now and then and it
would be good to have dracut support it. Something like "lsinitrd -x"
to extract archives and dracut options to use existing directories for
early cpio and main initrd.
next prev parent reply other threads:[~2015-07-27 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 19:08 Minimal initramfs Modification Rick Tillery
[not found] ` <CAAZEOjsyDkv0ai9a96Jg0M7tX5hAKUXMgHW7NiAugf7Sf_xnEw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-23 20:42 ` Andrew Udvare
[not found] ` <55B151B0.5020100-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-07-24 15:26 ` Rick Tillery
[not found] ` <CAAZEOjsavzT1GsBMENe9AbHYDUhrhbS5OWaZ4tpuqe7383GO3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-27 4:10 ` Andrei Borzenkov [this message]
2015-10-01 10:56 ` Akos Ovari
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=20150727071058.52eedf20@opensuse.site \
--to=arvidjaar-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=audvare-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rtillerywork-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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