All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Will Woods <wwoods-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH liveupdates] apply-live-updates.sh: handle updates for /run
Date: Thu, 06 Sep 2012 12:17:45 +0200	[thread overview]
Message-ID: <50487849.5010803@redhat.com> (raw)
In-Reply-To: <1346281095-16549-1-git-send-email-wwoods-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Am 30.08.2012 00:58, schrieb Will Woods:
> /run will get mounted at $NEWROOT/run after switch_root, but it's not
> there yet. bind-mount it in place so updates for /run actually land in
> /run.
> 
> (also: remove a redundant check for existing directories. mkdir -p
> doesn't do anything if the directory already exists.)
> ---
>  modules.d/90dmsquash-live/apply-live-updates.sh | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/modules.d/90dmsquash-live/apply-live-updates.sh b/modules.d/90dmsquash-live/apply-live-updates.sh
> index 61da4bf..d620f2c 100755
> --- a/modules.d/90dmsquash-live/apply-live-updates.sh
> +++ b/modules.d/90dmsquash-live/apply-live-updates.sh
> @@ -2,14 +2,16 @@
>  
>  if [ -b /dev/mapper/live-rw ] && [ -d /updates ]; then
>      info "Applying updates to live image..."
> +    mount -o bind /run $NEWROOT/run
>      # avoid overwriting symlinks (e.g. /lib -> /usr/lib) with directories
>      (
>          cd /updates
>          find . -depth -type d | while read dir; do
> -            [ -d "$NEWROOT/$dir" ] || mkdir -p "$NEWROOT/$dir"
> +            mkdir -p "$NEWROOT/$dir"
>          done
>          find . -depth \! -type d | while read file; do
>              cp -a "$file" "$NEWROOT/$file"
>          done
>      )
> +    umount $NEWROOT/run
>  fi
> 

Huh? Why do you want updates in /run ?????

  parent reply	other threads:[~2012-09-06 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 22:58 [PATCH liveupdates] apply-live-updates.sh: handle updates for /run Will Woods
     [not found] ` <1346281095-16549-1-git-send-email-wwoods-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-09-06 10:17   ` Harald Hoyer [this message]
     [not found]     ` <50487849.5010803-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-09-06 17:26       ` Will Woods
2012-09-07 12:09         ` 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=50487849.5010803@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wwoods-H+wXaHxf7aLQT0dZR+AlfA@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.