From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>,
"frank.li@vivo.com" <frank.li@vivo.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [HFS] generic/740 failure details
Date: Tue, 10 Jun 2025 07:43:22 +0200 [thread overview]
Message-ID: <27fffebd97c65f20291bfe54ba5e824bcbf579a0.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <7c676b6fe21c84033d34a09f4a02f2eb8746bce8.camel@ibm.com>
Hi,
On Mon, 2025-06-09 at 19:41 +0000, Viacheslav Dubeyko wrote:
> Frankly speaking, I don't see the point to re-write the hfs-progs in Rust for
> multiple reasons:
> (1) mostly, the main use-case that HFS/HFS+ partition is created under Mac OS
> and somebody tries to mount it under Linux to access data;
> (2) Apple is the owner of the code on Mac OS side and it's not good to
> significantly deviate from the Apple's state of the code;
> (3) I believe that Apple considers hfs-progs as obsolete code and they don't
> want any significant changes in it;
> (4) the hfs-progs is user-space tool, it is not frequently used, and even it
> fails, then there is no much harm.
Writing hfsprogs from scratch for Linux would mean though that a proper license
could be chosen that is not APSL which some distributions consider non-free.
On the other hands, the current hfsprogs utility is based on Apple's original
HFS/HFS+ code which is battle-tested and known to be reliable and robust. I'm
not sure whether we would be able to reach this level of stability within a
reasonable amount of time.
I do have to resume my work on my Linux patches again so that we can synchronize
hfsprogs with the latest upstream version.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2025-06-10 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 22:41 [HFS] generic/740 failure details Viacheslav Dubeyko
2025-06-06 6:31 ` John Paul Adrian Glaubitz
2025-06-06 17:52 ` Viacheslav Dubeyko
2025-06-09 10:52 ` Yangtao Li
2025-06-09 19:41 ` Viacheslav Dubeyko
2025-06-10 5:43 ` John Paul Adrian Glaubitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27fffebd97c65f20291bfe54ba5e824bcbf579a0.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=Slava.Dubeyko@ibm.com \
--cc=frank.li@vivo.com \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).