linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: "Darrick J. Wong" <djwong@kernel.org>, Theodore Ts'o <tytso@mit.edu>
Cc: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>,
	 "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: Tue, 22 Apr 2025 09:21:55 +0200	[thread overview]
Message-ID: <661fb07d164e19e02ae18b4fe24e6cd1613b9a7b.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20250422041655.GN25659@frogsfrogsfrogs>

On Mon, 2025-04-21 at 21:16 -0700, Darrick J. Wong wrote:
> > 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/
> 
> How about hfsprogs, it has mkfs and fsck tools.  Though it /is/ APSL
> licensed...

That's what I use and maintain in Debian. I have been trying to reach out
to Apple to get it relicensed under Apache or MIT but I unfortunately got
a reply.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2025-04-22  7:21 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
2025-04-22  4:16   ` Darrick J. Wong
2025-04-22  7:21     ` John Paul Adrian Glaubitz [this message]
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=661fb07d164e19e02ae18b4fe24e6cd1613b9a7b.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=Slava.Dubeyko@ibm.com \
    --cc=brauner@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=slava@dubeyko.com \
    --cc=tytso@mit.edu \
    /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).