mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] fake-overlayfs
Date: Fri, 9 Oct 2020 15:06:52 +0200	[thread overview]
Message-ID: <20201009130652.GA3084@pengutronix.de> (raw)
In-Reply-To: <20201007223840.GA876287@lenoch>

Hi,

On Thu, Oct 08, 2020 at 12:38:40AM +0200, Ladislav Michl wrote:
> fake-overlayfs help text reads:
>  'fake an overlay filesystem like unionfs by copying the original
>   content to a tmpfs.'
> 
> However it does not seem to do so. Bellow is attempt to fix that.
> 1) /usr/sbin/fake-overlayfs does not seem to mount tmpfs
> 2) with MountFlags=private is tmpfs mount invisible for the rest of system
> 3) perhaps use /run only with systemd?

So I haven't tested this in a while but what is supposed to happen is this:

You add the tmpfs to the fstab for any directory that should be writable.
Then fake-overlayfs will fill that tmpfs with the content that is hidden
by the tmpfs.

Michael


> Comments welcome,
> 	ladis
> 
> diff --git a/projectroot/usr/lib/systemd/system/fake-overlayfs.service b/projectroot/usr/lib/systemd/system/fake-overlayfs.service
> index daa6fd03f..818d624b9 100644
> --- a/projectroot/usr/lib/systemd/system/fake-overlayfs.service
> +++ b/projectroot/usr/lib/systemd/system/fake-overlayfs.service
> @@ -1,11 +1,10 @@
>  [Unit]
>  Description=Fake Overlay Filesystem
>  DefaultDependencies=no
> -After=local-fs.target
> +Before=local-fs.target
>  Requires=local-fs.target
>  
>  [Service]
>  Type=oneshot
> -RemainAfterExit=no
> +RemainAfterExit=yes
>  ExecStart=/usr/sbin/fake-overlayfs
> -MountFlags=private
> diff --git a/projectroot/usr/sbin/fake-overlayfs b/projectroot/usr/sbin/fake-overlayfs
> index b6692c578..de852b520 100644
> --- a/projectroot/usr/sbin/fake-overlayfs
> +++ b/projectroot/usr/sbin/fake-overlayfs
> @@ -2,7 +2,7 @@
>  
>  OVERLAY_DIRS="@OVERLAY_DIRLIST@"
>  
> -bdir=/tmp/.fake-overlay-root
> +bdir=/run/.fake-overlay-root
>  
>  mkdir $bdir
>  mount -o bind,private / $bdir
> @@ -14,10 +14,9 @@ while [ $# -gt 0 ]; do
>  		shift
>  		continue
>  	fi
> -	echo $1
>  	src="$bdir$1"
> -	dst="$1/"
> -	test -e "$dst" || mkdir $dst
> +	dst=$1
> +	mount -t tmpfs tmpfs $dst
>  	cp -a "$src/"* "$src/".[^.]* "$src/"..?* $dst 2> /dev/null
>  	shift
>  done
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

      reply	other threads:[~2020-10-09 13:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 22:38 Ladislav Michl
2020-10-09 13:06 ` Michael Olbrich [this message]

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=20201009130652.GA3084@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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