Re: Support for the new OpenBSD disklabel format

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Karel,

On Tue 10 Dec 2013 12:32:08 PM EET, Karel Zak wrote:
> On Mon, Dec 02, 2013 at 07:21:50PM +0200, Nikos Skalkotos wrote:
>> Besides the python tool I've written, for a more permanent solution, I'm
>> considering patching libfdisk to support the OpenBSD disklabel. I wanted
>> to know if you are interested for those patches. I think the best way to
>> do it is to split the disklabel parts that have changed into different
>> structs and use unions to create a disklabel struct that will work both
>> for NetBSD and OpenBSD. What do you think?
>
> I'm just doing some invasive changes to the library -- it would be
> probably better to wait to January to avoid some collisions and extra
> work.
>
> We also have some very simple partitions table parser in libblkid
> (see libblkid/src/partitions/, mostly dos.c for nested partition tables). It
> would be nice to extend this partition table parser too.
>
> Don't forget to send some test image with the new BSD disklabel! :-)

No problem, I can wait till January. I'll keep an eye on the changes 
made in
libfdisk. I'll also examine the code under libblkid/src/partitions.

>
>> If this works out, I'd be happy to create python bindings for libfdisk
>> (like the ones you have for libmount) as a later step. I know that the
>> API is not currently stable, but most parts seem OK.
>
> It's probably too early, the API is not stable at all, maybe later in
> next year.
>
> Anyway, python binding is wanted -- we already have binding for
> libmount, Ondrej promised binding for libblkid, so binding for
> libfdisk would be excellent thing!
>
> Now the library is good enough for dialogs driven interfaces (like
> fdisk), but it's necessary to improve it for programs like cfdisk and
> sfdisk. Now I'm working on new cfdisk.

Actually I wanted to ask you about this. I've seen the fdisk_ask struct
and how the client can registers an ask_callback function, but it's not
clear to me how you are planning to allow programs to use the
library in an unattended way. Are you going to provide new methods
for this or are you going to document the data each method will ask
for to allow the user to provide the answers in advance?

If you rewrite sfdisk to use the library, I'll get all the answers I 
need. :-)

>
>     Karel
>
--
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




[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux