Re: Disk Device Manager quo vadis?

Axel Dörfler wrote:
> Hi Jan, Tomas, and ?,
>
> it's almost been 2 months since we last heard from you - I just wanted 
> to ask if you are still working on it or not. Have you made any 
> progress?
>
> Bye,
>    Axel.
>   
Hello,
i was just going to write.
Status is this: we turned in our project about a month and a half ago,
and it was accepted. However, i don't really think it is finished,
especially cosidering documentation, and the partitioning client. So i
decided to work on it a little more. Then more important things got in
the way.

What is done:
- the intel partitioning addon is functionally complete and rather well
documented and tested
- KJobs are finished, but not really well tested.
- DiskDeviceManager call paths are cleared for most calls, but still
broken for some.
- "overview" docs are written and i thing they are quite good

What isn't:
- documentation, apart from the addon, is rather sketchy
- the client is ... really bad. It can list partitions and it can create
children, but it looks worse than fdisk and the implementation is quite
weird.

Which reminds me, we've run into a strange problem : kernel won't
automatically unlock the partitioning tree when the client exits. I
don't have any idea how to solve this.

I will send you what we have, as a patch against some current revision
... once i find out where it is stored (did i say that i "accidentally"
did rm -rf /usr on my favorite OS in the course of events, and then had
much fun reconstructing one of the other OSes?)

In other news, i am now sick and in bed, so i have about a week's worth
of free time. I could try and find out if i can build a gui partitioning
client in that time.

regards
m.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/