mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Major Hayden <major-rCS72UCksqc@public.gmane.org>,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Adding support for read/write filesystem images
Date: Fri, 15 Aug 2014 12:26:51 +0200	[thread overview]
Message-ID: <53EDE06B.80900@redhat.com> (raw)
In-Reply-To: <53DFAB14.1020201-rCS72UCksqc@public.gmane.org>

On 04.08.2014 17:47, Major Hayden wrote:
> A user can provide a filesystem image (rootfs.img) inside a compressed
> tarball and that filesystem image will be mounted read/write.  This provides
> some benefits over a device mapper snapshot overlay, especially when the
> live system becomes full.  The boot command line simple needs
> "rd.writable.fsimg" added to utilize this feature.
> 
> Signed-off-by: Major Hayden <major-rCS72UCksqc@public.gmane.org>
> ---
>  modules.d/90dmsquash-live/dmsquash-live-root.sh | 16 ++++++++++++++--
>  modules.d/90dmsquash-live/module-setup.sh       |  2 +-
>  2 files changed, 15 insertions(+), 3 deletions(-)
> 

Looks simple enough.

Can you add documentation to the man pages? And if you are really nice add
documentation about the other dmsquash parameters, too. :)

  parent reply	other threads:[~2014-08-15 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 15:47 [PATCH] Adding support for read/write filesystem images Major Hayden
     [not found] ` <53DFAB14.1020201-rCS72UCksqc@public.gmane.org>
2014-08-15 10:26   ` Harald Hoyer [this message]
     [not found]     ` <53EDE06B.80900-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-08-15 13:22       ` Major Hayden
     [not found]         ` <53EE099D.2070402-rCS72UCksqc@public.gmane.org>
2014-08-15 14:07           ` Harald Hoyer

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=53EDE06B.80900@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=major-rCS72UCksqc@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