Hi Brian,

Thank you for working to improve the resize tests in addition to many other areas of parted.

> Is anyone still shipping a mkfs.hfs?

Both mkfs.hfs and mkfs.hfsplus are included with the hfsprogs package in recent Debian [1] and Ubuntu [2].

[1] https://packages.debian.org/sid/i386/hfsprogs/filelist
[2] https://packages.ubuntu.com/impish/amd64/hfsprogs/filelist

There is also the older hfsutils package in both Debian [3] and Ubuntu [4].

[3] https://packages.debian.org/sid/i386/hfsutils/filelist
[4] https://packages.ubuntu.com/impish/amd64/hfsutils/filelist

It appears that openSUSE also ships hfsprogs [5] and hfsutils [6].

[5] https://build.opensuse.org/search?search_text=hfsprogs
[6] https://build.opensuse.org/search?search_text=hfsutils

> Is anyone not shipping mkfs.hfsplus?

For Fedora I found the package hfsutils but not hfsprogs.

[7] https://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=hfsutils [8] https://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=hfsprogs

In summary it appears that at least Debian, Ubuntu, and openSUSE are shipping both mkfs.hfs and mkfs.hfsplus file system utilities. Fedora seems to only have the older hfsutils package.

Regards,
Curtis

On 2021-07-15 11:11 a.m., Brian C. Lane wrote:
While looking more closely at the t3000 tests I realized that on Fedora
we haven't had a mkfs.hfs for a long time... So the t3000 test hasn't
actually been running.

It still seems to pass (whew!) but I've just sent a patch to make it run
with the available filesystems so that if there is no mkfs.hfs it will
still run the vfat test if mkfs.vfat is installed in the environment.

The other thing is this: Is anyone still shipping a mkfs.hfs? Is anyone
not shipping mkfs.hfsplus?

Should we switch to using mkfs.hfsplus and fsck.hfsplus (on Fedora
fsck.hfs is a symlink to fsck.hfsplus)?

Plain hfs is ancient at this point, and if I'm reading the comments in
the hfs resize code it is supposed to work fine with hfs+ so I think
it's probably time to switch.

Thanks,

Brian


Reply via email to