From: "Theodore Ts'o" <tytso@mit.edu>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
Cc: "glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"brauner@kernel.org" <brauner@kernel.org>,
"slava@dubeyko.com" <slava@dubeyko.com>
Subject: Re: HFS/HFS+ maintainership action items
Date: Mon, 21 Apr 2025 21:43:33 -0500 [thread overview]
Message-ID: <20250422024333.GD569616@mit.edu> (raw)
In-Reply-To: <f06f324d5e91eb25b42aea188d60def17093c2c7.camel@ibm.com>
On Mon, Apr 21, 2025 at 09:52:14PM +0000, Viacheslav Dubeyko wrote:
> Hi Adrian,
>
> I am trying to elaborate the HFS/HFS+ maintainership action items:
> (1) We need to prepare a Linux kernel tree fork to collect patches.
> (2) I think it needs to prepare the list of current known issues (TODO list).
> (3) Let me prepare environment and start to run xfstests for HFS/HFS+ (to check
One potential problem is that the userspace utilities to format,
check, repair HFS/HFS+ utilities don't really exist. There is the HFS
Utilities[1] which is packaged in Debian as hfsutils, but it only
supports HFS, not HFS+, and it can only format an HFS file system; it
doesn't have a fsck analog. This is going to very limit the ability
to run xfstests for HFS or HFS+.
[1] https://www.mars.org/home/rob/proj/hfs/
- Ted
next prev parent reply other threads:[~2025-04-22 2:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 21:52 HFS/HFS+ maintainership action items Viacheslav Dubeyko
2025-04-22 2:43 ` Theodore Ts'o [this message]
2025-04-22 4:16 ` Darrick J. Wong
2025-04-22 7:21 ` John Paul Adrian Glaubitz
2025-04-22 7:20 ` John Paul Adrian Glaubitz
2025-04-22 12:35 ` John Paul Adrian Glaubitz
2025-04-22 21:12 ` Viacheslav Dubeyko
2025-04-22 21:47 ` John Paul Adrian Glaubitz
2025-04-22 21:48 ` John Paul Adrian Glaubitz
2025-04-25 1:06 ` Viacheslav Dubeyko
2025-04-25 10:17 ` 回复: " 李扬韬
2025-04-25 11:32 ` John Paul Adrian Glaubitz
2025-04-25 11:39 ` 回复: " 李扬韬
2025-04-25 18:25 ` Viacheslav Dubeyko
2025-04-25 19:36 ` 回复: " 李扬韬
2025-04-25 19:44 ` Viacheslav Dubeyko
2025-04-26 6:17 ` 回复: " 李扬韬
2025-04-26 6:59 ` John Paul Adrian Glaubitz
2025-04-27 20:28 ` Viacheslav Dubeyko
2025-05-02 3:01 ` Theodore Ts'o
2025-05-02 19:14 ` Viacheslav Dubeyko
2025-05-03 5:39 ` Theodore Ts'o
2025-05-05 23:08 ` Viacheslav Dubeyko
2025-04-25 20:51 ` John Paul Adrian Glaubitz
2025-04-25 18:02 ` Viacheslav Dubeyko
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=20250422024333.GD569616@mit.edu \
--to=tytso@mit.edu \
--cc=Slava.Dubeyko@ibm.com \
--cc=brauner@kernel.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.