DragonFly users List (threaded) for 2009-01
From: Vincent Stemen <email@example.com>
Subject: Re: fdisk implementation [read this before deciding what to do]
Date: Thu, 8 Jan 2009 20:52:37 -0600
Content-Type: text/plain; charset=us-ascii
References: <firstname.lastname@example.org> <200807081735.m68HZn8e040078@apollo.backplane.com> <email@example.com> <firstname.lastname@example.org> <email@example.com> <48765385$0$848$415eb37d@crater_reader.dragonflybsd.org> <firstname.lastname@example.org> <200812171749.mBHHnLMC092865@apollo.backplane.com> <20090103005704.GA24236@quark.hightek.org> <email@example.com
X-Trace: 1231469935 crater_reader.dragonflybsd.org 881 126.96.36.199
Xref: crater_reader.dragonflybsd.org dragonfly.users:11866
On Wed, Jan 07, 2009 at 11:38:45PM -0800, Matthew Dillon wrote:
> :I could put up a binary if anybody wants to play with it. If you guys
> :are interested in taking it over, making it an official part of
> :Dragonfly, and updating it for the new disk labels, etc, we were
> :considering going ahead and releasing the source. If not, we will
> :probably hold off and release it later on as part of some other projects
> :after we get a chance to finish it ourselves. But that might be
> :a while.
> Well, it sounds quite interesting to me though if it does not yet
> support disklabel64's maybe I could get you guys to add that before
> submitting it. The boot1/boot2 images have recently changed in
> order to support generating different sets for 32 bit disklabels and
> 64 bit disklabels.
> It would have to be open-sourced with a BSD style license if you want
> to submit it. We might cringe a bit if it needs a manual page
> written plus a lot of code cleanup.
> Matthew Dillon
Yes, if you decide you want to make it an official part of DF we were
planning to put it under the BSD license.
I don't think there is much code cleanup needed. Mostly the addition of
the extra features. At the time Chet originally ported partition to DF,
the disklabel64 headers were not finished yet in DF.
He wants to go ahead and separate the fdisk portion out into a separate
tool (Which will be easy - The code is modular) rather than keeping it
as a combined tool that does the job of disklabel and fdisk. He wants
to do that first, then we can give you a copy of the source (and binary
if you want) to the fdisk tool to look over and see what you think.
If you like what you see and want to include the tools, Chet said he
will look into adding disklabel64 support. Also, I will go ahead and
work on the planned command line changes I mentioned first so that I can
write an initial manual.
If you look over fdisk and give me a confirmation that you want to
include the tools in DF and take over maintenance on them, we will bump
the priority up on preparing them for you. Otherwise, we are going to
hold off on doing more work on and officially releasing them until they
are needed as part of some other projects we are working on. So the
evaluation copy of fdisk we give you will not yet be under the BSD