All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Brian C. Lane" <bcl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Create a symlink for the live image's base loop device
Date: Fri, 13 Jan 2012 11:41:40 +0100	[thread overview]
Message-ID: <4F100A64.5050607@redhat.com> (raw)
In-Reply-To: <1324419753-14324-1-git-send-email-bcl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 20.12.2011 23:22, Brian C. Lane wrote:
> From: "Brian C. Lane" <bcl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> 
> It is useful to know that loop device that the live image's / is mounted
> from. Make a /dev/live-baseloop symlink that points to it.
> ---
>  modules.d/90dmsquash-live/dmsquash-live-root |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/modules.d/90dmsquash-live/dmsquash-live-root b/modules.d/90dmsquash-live/dmsquash-live-root
> index b704139..cb104e4 100755
> --- a/modules.d/90dmsquash-live/dmsquash-live-root
> +++ b/modules.d/90dmsquash-live/dmsquash-live-root
> @@ -200,6 +200,9 @@ if [ -n "$ROOTFLAGS" ]; then
>      ROOTFLAGS="-o $ROOTFLAGS"
>  fi
>  
> +if [ -b "$BASE_LOOPDEV" ]; then
> +    ln -s $BASE_LOOPDEV /dev/live-baseloop
> +fi
>  ln -s /dev/mapper/live-rw /dev/root
>  printf '/bin/mount %s /dev/mapper/live-rw %s\n' "$ROOTFLAGS" "$NEWROOT" > $hookdir/mount/01-$$-live.sh
>  

changed the symlink to /run/initramfs/live-baseloop, because /dev should be only
be maintained by udev and the kernel

  parent reply	other threads:[~2012-01-13 10:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 22:22 [PATCH] Create a symlink for the live image's base loop device Brian C. Lane
     [not found] ` <1324419753-14324-1-git-send-email-bcl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-13 10:41   ` Harald Hoyer [this message]
     [not found]     ` <4F100A64.5050607-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-13 12:06       ` Brian C. Lane

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=4F100A64.5050607@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=bcl-H+wXaHxf7aLQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.