Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: Vyacheslav Yurkov <uvv.mail@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: overlayfs-etc compatibility with volatile-bind
Date: Wed, 07 Feb 2024 11:28:34 +0200	[thread overview]
Message-ID: <87sf24vcxu.fsf@tarshish> (raw)

Hi Vyacheslav Yurkov,

overlayfs-etc generates a 'preinit' script that unconditionally remounts
root to make it writable. Later systemd-fstab-generator generates a
mount unit (-.mount) that restores read-only as set in /etc/fstab.

I added an entry to VOLATILE_BINDS for the /home directory. The volatile-binds
recipe creates a systemd mount unit with the condition

  ConditionPathIsReadWrite=!/home

The trouble is that there is no dependency between the rootfs mount unit and
the /home unit. When the /home unit runs first, the condition is false, and
the unit fails. If I later start the /home unit manually, it succeeds, because
rootfs is read-only now.

What is the purpose of mounting root rw in 'preinit'?

Is there any other alternative to make volatile-binds do the right thing?

Thanks,
baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -


             reply	other threads:[~2024-02-07  9:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  9:28 Baruch Siach [this message]
2024-02-07 10:53 ` overlayfs-etc compatibility with volatile-bind Vyacheslav Yurkov

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=87sf24vcxu.fsf@tarshish \
    --to=baruch@tkos.co.il \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=uvv.mail@gmail.com \
    /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