[Parted-maintainers] parted documentation updates

Sven Luther sven.luther@wanadoo.fr
Sat, 14 May 2005 09:36:06 +0200


On Fri, May 13, 2005 at 10:32:05PM +0200, Nikolaus Schulz wrote:
> Hello all!
> 
> As a result of discussing Debian bug #298020 ("parted: hfs(+) support is
> still poorly documented") [1] with Sven Luther, I have joined the parted
> project at alioth and find myself working on some documentation updates
> for the parted package in Debian. :-)
> 
> Some background for those not following the development closely might be
> in order.  Thanks to Guillaume Knispel, parted supports resizing hfs(+)
> filesystems. (Cool!)  His patch has been merged upstream as of parted
> 1.6.22.  Although Debian Sarge will ship with parted 1.6.21, it includes
> the hfs patch from Guillaume for 1.6.19. Doesn't apply cleanly, but no
> one has complained. :-)  The documentation in Debian yet doesn't reflect
> that, however, which made #298020 spring into life. [2]
> 
> I put the things first that affect upstream. I've packported the
> changes to parted.texi WRT hfs(+) support from 1.6.22 and added a short
> section about hfs, based upon libparted/fs_hfs/DOC from Guillaume.
> Incremental patches (1.hfsdoc-backport 2.hfsdoc) are attached. Note they
> apply cleanly against version 1.6.21, that is cvs revision 1.3 of
> parted.texi.  Patching revision 1.12 with hfsdoc.diff (skipping the
> backport) seems to work, too, with some offsets. 
> 
> Before committing the latter changes, I'd appreciate your opinion, your
> suggestions and your help. For example: Guillaume, you wrote that 
> 2.4. kernels are quite buggy as it comes to hfs resizing. Which
> versions did you test? For now I've put that "as of fall 2004"...
> And can someone confirm that parted _cannot_ create hfs(+) formatted
> volumes? Guillaume?

Nikolaus,

powerpc should no more use 2.4 kernels, which are unsupported upstream since
almost a year and a half now, so simply stating that hfs resizing is buggy on
2.4 kernels should be enough. You can also state that this will most probably
not be fixed, and please upgrade to 2.6.

Friendly,

Sven Luther