From: Sascha Hauer <s.hauer@pengutronix.de>
To: iw3gtf@arcor.de
Cc: barebox@lists.infradead.org
Subject: Re: Re: errors copying UBI volumes
Date: Thu, 15 Sep 2016 13:44:01 +0200 [thread overview]
Message-ID: <20160915114401.z5tdaxcb6eesv3qn@pengutronix.de> (raw)
In-Reply-To: <247915608.359799.1473937994666.JavaMail.ngmail@webmail18.arcor-online.net>
On Thu, Sep 15, 2016 at 01:13:14PM +0200, iw3gtf@arcor.de wrote:
> Hi Sascha,
>
> thanks for the answer,
>
> > Hi Giorgio,
> >
> > On Wed, Sep 14, 2016 at 05:52:32PM +0200, iw3gtf@arcor.de wrote:
> > > Hi,
> > >
> > > I'm working on an embedded board with an iMX25 arm CPU and a nand flash.
> > >
> > > The board runs a linux kernel/userland.
> > >
> > > When the user updates the firmware, the running userland/kernel creates
> > some
> > > new ubi volumes on the nand, let's say 'kernel_next' and 'userland_next'.
> > > On the next system reboot barebox looks if it finds, lets say, the
> > 'kernel_next' volume
> > > and, in this case, it removes the old one ('kernel'), creates a new, empty
> > one ('kernel'),
> > > copies 'kernel_next' to the just created 'kernel' and finally removes the
> > 'kernel_next'
> > > to complete the update.
> >
> > While this should work, why so complicated? Since this commit:
> >
> > | commit 892abde56c1c5a62d49d8b70c73e5d388e74345d
> > | Author: Richard Weinberger <richard@nod.at>
> > | Date: Mon Nov 24 22:30:10 2014 +0100
> > |
> > | UBI: rename_volumes: Use UBI_METAONLY
> > |
> > | By using UBI_METAONLY in rename_volumes() it is now possible to rename
> > | an UBI volume atomically while it is open for writing.
> > | This is useful for firmware upgrades.
> >
> > It should be possible to just remove 'kernel' and rename 'kernel_next' to
> > 'kernel'
> > without bootloader intervention.
>
> This is a very good news for me, I already wanted to ask for a UBI rename feature.
> Could you please elaborate a bit on this point: I looked for a shell command like the
> 'ubirename', present in the 'mtd-utils' package, but could not find it. Maybe we just
> need a new command implemented in '<barebox_root>/commands/ubi.c'.
You can add a ubirename command, patches welcome. Anyway, I suggested to
rename it under Linux since you write your new Kernel/rootfs under Linux
aswell.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-09-15 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 11:13 Aw: " iw3gtf
2016-09-15 11:44 ` Sascha Hauer [this message]
2016-09-15 11:57 ` Aw: " iw3gtf
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=20160915114401.z5tdaxcb6eesv3qn@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=iw3gtf@arcor.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