From: Ladislav Michl <ladis@linux-mips.org>
To: rauc@pengutronix.de
Cc: Trent Piepho <tpiepho@impinj.com>
Subject: [RAUC] [RFC 0/3] Fix slots with nodev mounts
Date: Fri, 10 May 2019 11:48:03 +0200 [thread overview]
Message-ID: <20190510094803.GA29451@lenoch> (raw)
Hi there,
this is just an attempt to make rauc work with nodev mounted slots.
It is based on https://github.com/rauc/rauc/pull/406 where first
patch in the serie is meant to be squashed there.
Second patch then implements matching against ubi:<vol_name>
device naming scheme and can be easily extended. Now with
$ cat /proc/mounts
ubi0:rootfs0 / ubifs ro,relatime,assert=read-only,ubi=0,vol=0 0 0
[strip]
It is able to correctly find slot and use it as seed slot for casync:
$ rauc status
Compatible: Foomatic System
Variant:
Booted from: rootfs.0 (system0)
Activated: rootfs.0 (system0)
slot states:
rootfs.1: class=rootfs, device=/dev/ubi0_1, type=ubifs, bootname=system1
state=inactive, description=, parent=(none), mountpoint=(none)
boot status=good
rootfs.0: class=rootfs, device=/dev/ubi0_0, type=ubifs, bootname=system0
state=booted, description=, parent=(none), mountpoint=/
boot status=good
Third patch is again just a preview - r_mount_slot should be fixed
instead. I'm assuming anything having ext_mount_point set is already
mounted there, thus only bind mount makes sense here. Correct?
Please review, I'd like to have patch 1 and (rewritten) patch 3
merged for v1.1 milestone :)
Thank you,
ladis
_______________________________________________
RAUC mailing list
next reply other threads:[~2019-05-10 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 9:48 Ladislav Michl [this message]
2019-05-10 9:48 ` [RAUC] [PATCH 1/3] Normalize device names to find mounted slots (2) Ladislav Michl
2019-05-10 9:49 ` [RAUC] [PATCH 2/3] Try harder to determine slot state (preview) Ladislav Michl
2019-05-10 9:49 ` [RAUC] [PATCH 3/3] Bind mount seed slot Ladislav Michl
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=20190510094803.GA29451@lenoch \
--to=ladis@linux-mips.org \
--cc=rauc@pengutronix.de \
--cc=tpiepho@impinj.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