public inbox for initramfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Udvare <audvare-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Minimal initramfs Modification
Date: Thu, 23 Jul 2015 13:42:24 -0700	[thread overview]
Message-ID: <55B151B0.5020100@gmail.com> (raw)
In-Reply-To: <CAAZEOjsyDkv0ai9a96Jg0M7tX5hAKUXMgHW7NiAugf7Sf_xnEw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 23/07/15 12:08, Rick Tillery wrote:
> I need to make a small modification to an existing initramfs image
> file (to add driver and executable that need to run before main system
> drives are mounted), but I want to do so with minimal changes to the
> existing image, in order to avoid incompatibilities with any other
> customization that may have been added to the initramfs before.
> 
> dracut seems to create initramfs from scratch, using the currently
> running environment.  But I would prefer to unarchive the image, make
> my small modification, re-archive the tree, and then replace the
> existing initramfs file (backing up the old one) to be used on the
> next reboot.  The goal is as small a change as possible from what was
> there originally.
> 
> I tried using cpio, but it doesn't handle the device directories when
> unarchiving without generating errors.  And I'm not sure how to use
> this to reconstruct the archive, especially with the compression and
> early CPIO portions restored correctly.

I have had this on bookmark just in case I need it.

http://www.thegeekstuff.com/2009/07/how-to-view-modify-and-recreate-initrd-img/

  parent reply	other threads:[~2015-07-23 20:42 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 [this message]
     [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
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=55B151B0.5020100@gmail.com \
    --to=audvare-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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