Patching mkfs.ubifs.c for running under Windows ?

[gutemine <gutemine@oozoon.de>]

Hi!

I'm the author of ubidump, the first real ubifs image extract tool.
ubidump allows to extract ubifs images created by mkfs.ubifs and also ubifs
volumes created by ubinize. 

ubidump works without any nandsim, block2mtd or mtdram modules and doesn't
mount the image at all. Therefore it runs nicely on both Linux and Windows
as it is written in pure C and doesn't use any mtd-utils code or includes.

Live under Linux was easy, but I took the challange to make it run under
Windows too, because there it was not possible to mount and extract an
ubifs image until now.

ubidump under Windows supports Hard and Symlinks by using the native NTFS
functionality. Only device files and pipes are written as simple text files
containing the needed information for a re-pack (eg. char or block device
and major and minor number). 

As users of ubidump under Windows now asked me for getting also the
possibility to re-pack their extracted ubifs images, I'm considering to
patch mkfs.ubifs.c, so that it handles also the Windows hard and softlinks
and my dummy device files correctly. 

My question is now, if it would be OK to add these changes to the standard
mkfs.ubifs.c (off cource nicely wrapped in #ifdef WINDOWS statements so
that these changes don't do any harm when compiled on other plattforms) and
send you the diff, or if I should create an extra open source tool based on
the existing mkfs.ubifs.c code.

BTW I'm ware of the mkfs.ubifs cygwin implementation, but as explained
above I would prefere to make mkfs.ubifs run in native Windows as my
ubidump does.

Please advice on your preferences and in what direction I should proceede
with this project!

Kind regards,
gutemine