Jim Meyering wrote:
Curtis Gedak wrote:
...
I think it is a good idea to keep the resize FAT16/32 file system code
in parted for at least a while longer (perhaps even up to a year or
more). That way it will provide some overlap time between when the
fatresize project contains the updated code from parted, and when
dosfstools might include the fatresize command. This will also
provide various distributions time to include such code in the
respective updated packages.
I am now considering taking a less invasive approach for
the upcoming beta release: merely warn about any use
of file-system-related operations.
Removing FS support entirely would take more time than I have
now, and would significantly complicate testing.
In addition, hfs/hfs+ resizing support must stay,
since there appears to be no free alternative.
That sounds like a wise approach in light of the realization that there
appears to be no free alternatives for resizing FAT16/32 or even HFS/HFS+.
If I hear from the fatresize team regarding taking over the FAT16/32
resize capability I will be sure to post here about it.
_______________________________________________
parted-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/parted-devel
