tag:blogger.com,1999:blog-7921326074980135918.post6017691210010555926..comments2024-02-06T09:40:10.395+01:00Comments on Karel Zak's blog: libblkidUnknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7921326074980135918.post-52492217527107463652010-02-05T00:24:39.755+01:002010-02-05T00:24:39.755+01:00to eleccham:
that's partially implemented by
...to eleccham: <br />that's partially implemented by<br /><br /> blkid_partition_get_{uuid,type,start, ...}()<br /><br />functions. Things like flags or attributes will be available in the next release.karelzakhttps://www.blogger.com/profile/05231988060539621851noreply@blogger.comtag:blogger.com,1999:blog-7921326074980135918.post-10502824511123944802010-01-28T15:34:50.961+01:002010-01-28T15:34:50.961+01:00I can't say thank you enough times here...
I ...I can't say thank you enough times here...<br /><br />I was tearing my hair out trying to figure out the dual maze of partition/volume identification and the licensing of the components that can do it. I'm working on a project where parts of it are open-source and parts of it aren't, and needed to do the exact kind of low-level discovery that the new low-level API offers.<br /><br />One thought - how about an API for obtaining those pieces of information that are specific to a particular partitioning scheme (i.e., the "active" flag for MBR, or the "attributes" field for GPT)?<br /><br />Lastly, actually, your English isn't any worse than that of many of its native speakers' is... :)Anonymousnoreply@blogger.com