From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Haris Papadopoulos <haris@amberbox.com>
Cc: barebox@lists.infradead.org
Subject: Re: Multiple root file systems
Date: Fri, 10 Feb 2017 09:12:10 +0100 [thread overview]
Message-ID: <20170210081210.anhoasldrlhqtork@pengutronix.de> (raw)
In-Reply-To: <CACmkAZEcG-VJCJt6va7fBamCV7BexSrQn3S8hBudyasyk97npA@mail.gmail.com>
Hello,
On Fri, Feb 03, 2017 at 01:44:43PM +0000, Haris Papadopoulos wrote:
> I am trying to create a system with one bootloader, one kernel and
> multiple filesystems. I am going to use barebox bootchooser
> (http://www.barebox.org/doc/latest/user/bootchooser.html)
>
> My current /boot/nand file is as follows:
>
>
> #!/bin/sh
>
> [ -e /env/config-expansions ] && /env/config-expansions
>
> [ ! -e /dev/nand0.root.ubi ] && ubiattach /dev/nand0.root
>
> global.bootm.image="/dev/nand0.root.ubi.kernel"
> global.bootm.oftree="/dev/nand0.root.ubi.oftree"
>
> global.linux.bootargs.dyn.root="root=ubi0:root ubi.mtd=root
> rootfstype=ubifs rw"
>
> I would like to use two filesysyems with names root1 and root2. How
> should I modify the above?
What is the reason to stick to one kernel for both root filesystems?
If you drop that, you can put the kernel into the rootfses and use
blspec for booting. This way you get rid of the bootscript and just
mount the rootfs and then call
boot /mnt/rootfs1
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-02-10 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 13:44 Haris Papadopoulos
2017-02-10 8:12 ` Uwe Kleine-König [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=20170210081210.anhoasldrlhqtork@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=haris@amberbox.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