From: Robert Karszniewicz <r.karszniewicz@phytec.de>
To: barebox@lists.infradead.org
Subject: Re: [RFC PATCH 0/4] Introduce global.bootm.root env var for booting via PARTUUID
Date: Tue, 30 Jun 2020 16:20:17 +0200 [thread overview]
Message-ID: <1a2cb925-dccd-8de7-08da-c4abe76d473c@phytec.de> (raw)
In-Reply-To: <1593524914-228154-1-git-send-email-r.karszniewicz@phytec.de>
The problem is that we want to be able to have the rootfs and kernel on
separate partitions. We've looked into the Boot Loader Specification,
but from what we saw, it makes A-B systems difficult (according to the
spec, there can only be one "$BOOT" filesystem on a device).
For reference: https://systemd.io/BOOT_LOADER_SPECIFICATION/
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-06-30 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 13:48 Robert Karszniewicz
2020-06-30 13:48 ` [RFC PATCH 1/4] bootm: add env var root_dev Robert Karszniewicz
2020-06-30 13:48 ` [RFC PATCH 2/4] globalvar: add bootm.root Robert Karszniewicz
2020-06-30 13:48 ` [RFC PATCH 3/4] bootm: handle global.bootm.root Robert Karszniewicz
2020-06-30 13:48 ` [RFC PATCH 4/4] bootm: mount root device before accessing linux_rootarg Robert Karszniewicz
2020-06-30 14:20 ` Robert Karszniewicz [this message]
2020-07-01 5:58 ` [RFC PATCH 0/4] Introduce global.bootm.root env var for booting via PARTUUID Sascha Hauer
2020-07-08 6:55 ` Stefan Riedmüller
2020-07-09 14:14 ` Sascha Hauer
2020-07-13 11:18 ` Robert Karszniewicz
2020-07-14 18:37 ` Sascha Hauer
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=1a2cb925-dccd-8de7-08da-c4abe76d473c@phytec.de \
--to=r.karszniewicz@phytec.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox