Re: gluebi vs. ubi-volume mapping

[Richard Weinberger <richard@xxxxxx>]

Am Freitag, 11. Januar 2019, 13:54:22 CET schrieb Shibin George:
> On Fri, Jan 11, 2019 at 6:14 PM Richard Weinberger <richard@xxxxxx> wrote:
> >
> > > ubiblock, being read-only, didn't satisfy my requirement.
> > > The device I am working on needs to have block-level software upgrade
> > > capability.
> > > So gluebi was the best solution that I could find that can run block-based
> > > filesystem.
> >
> > Usually you don't want such a deep stacking on an embedded system.
> > But you are aware of ubiupdatevol?
> 
> Yes, ubiupdatevol was one of the candidates. However, I needed the capability
> to upgrade software incrementally instead of packing the entire ubifs image
> (This is because I can't afford to reserve storage for large software-upgrade
> packages).
> I had posted this query about ubiupdatevol @
> https://stackoverflow.com/questions/50699945/apply-incremental-patches-on-ubifs-volume
> and finally had to discard ubifs for my purpose for the same reason.
> That and the fact the current software-upgrade solution that I have works well
> with block-based filesystems.

I have no idea what this has to do with squashfs.

Instead of updating the squashfs via mtdblock->glubi->ubivolume->ubi,
just use ubiupdatevol to update the ubivolume.

Thanks,
//richard



______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/