[PATCH 1/1] ubi: Introduce block devices for UBI volumes
Willy Tarreau
w at 1wt.eu
Mon Feb 10 03:51:02 EST 2014
Hi Thomas,
On Mon, Feb 10, 2014 at 09:42:46AM +0100, Thomas Petazzoni wrote:
> Dear Willy Tarreau,
>
> On Sat, 8 Feb 2014 23:51:49 +0100, Willy Tarreau wrote:
>
> > > I really vote for dropping write support at all.
> >
> > Why ? When you put a read-only filesystem there such as squashfs, the
> > only writes you'll have will be updates, and write support will be the
> > only way to update the filesystem. So removing write support seriously
> > impacts the usefulness of the feature itself.
>
> Why can't you use ubi_updatevol to do the update of the squashfs image?
> I.e instead of updating through the block layer, you update at the UBI
> layer level. No?
It only solves one part of the problem with needless extra complexity.
I really fail to see why we would punish MTD users asking them to use
significantly different block device management interfaces than what
they can have on top of eMMC, SD, etc..., allowing to unify the FS
management methods.
Also, ubiupdatevol will offers no possibility to have a small R/W FS
to save a configuration from time to time.
Thanks,
Willy
More information about the linux-mtd
mailing list