On Wed, May 13, 2009 at 11:30:37AM +0200, Kay Sievers wrote:
> On Wed, May 13, 2009 at 11:18, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
> > Last but not least partition table reading is very little code, and
> > showing that into a shared library of it's own is a bit revolting.
> > Either we have a libfdisk or whatever doing both reading and writing,
> > or we have the partition table detection (and reading is not much more
> > than detecting and reading out a few fields) into the library we use
> > for all the other detection.
>
> Yeah, if it fits in any way in the libblkid API, I like to see the
> partition probing code there. We need the partition table information
> in many cases along with the filesystem type, to see things like the
> raid flag, the hidden marker, ...
OK, let's use libblkid.
> The writing and mangling of partition tables can probably go into its
> own library, it's a very different task from probing.
Yes, definitely.
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
