On Tue, Aug 01, 2017 at 04:03:09PM +0200, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@xxxxxxxxxx>
>
> Detecting UBI superblock may be useful for tools wanting to simplify or
> automate attaching UBI. Please note it's not directly related to the
> ubifs support which is just a filesystem working on top of UBI volume.
How does it co-exists with ufifs? Does it share the same /dev node or
attached UBI uses another device? (I have no UBI to test it.)
Note that by default libblkid does not support scenario where on the
same device is more superblock - in this case extra care is necessary
It seems (according to ubifs prober code) that ubifs is on another
device node.
It would be nice to have lsblk output with mounted ubifs.
> libblkid/src/Makemodule.am | 1 +
> libblkid/src/superblocks/superblocks.c | 1 +
> libblkid/src/superblocks/superblocks.h | 1 +
> libblkid/src/superblocks/ubi.c | 50 ++++++++++++++++++++++++++++++++++
> 4 files changed, 53 insertions(+)
> create mode 100644 libblkid/src/superblocks/ubi.c
Rafał, see also tests/ts/blkid/images-fs/ and tests/expected/blkid/.
It would by nice to have small image with UBI superblock and expected
output from "blkid -p -o udev <device>". It seems dd(1) the begin of
the device would be good enough.
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
