All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	debian-68k <debian-68k@lists.debian.org>
Cc: linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Status of affs support in the kernel and affstools
Date: Tue, 13 Jun 2023 09:53:31 +0300	[thread overview]
Message-ID: <d062dd7b09006c2d9988d92192952c65e66cf009.camel@gmail.com> (raw)
In-Reply-To: <baa520109ab3a13d1ac8aca1c9b8eaeee070c241.camel@physik.fu-berlin.de>

On Tue, 2023-06-13 at 08:47 +0200, John Paul Adrian Glaubitz wrote:
> Also, I noticed that Roman Zippel actually created an affstools package [1]
> back in the day and I wonder whether anyone has any experience with it. In
> particular, I'm wondering what »different mkfs.affs« Artem Bityutskiy is
> talking about here [2]. Is there an alternative tool for creating and checking
> affs filesystems?

Hi Adrian,

I apologize, that message was sent 10 years ago and I do not remember details
any longer.

What I do remember is that I was doing some cross-filesystem changes and
struggled to test AFFS. At that time it felt that AFFS was abandoned. But I
remember I managed to create an AFFS partition, mount it in Linux, and test my
changes.

Thanks,
Artem.

  reply	other threads:[~2023-06-13  6:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  6:47 Status of affs support in the kernel and affstools John Paul Adrian Glaubitz
2023-06-13  6:53 ` Artem Bityutskiy [this message]
2023-06-13  7:05   ` John Paul Adrian Glaubitz
2023-06-13  7:20 ` Martin Steigerwald
2023-06-13  7:22   ` John Paul Adrian Glaubitz
2023-06-20 21:27     ` Martin Steigerwald
     [not found] ` <CABq5eXGMA=5U_h3ZbfXt_weZNWh5zviFn3rw9oxS=wFc6d1Vsw@mail.gmail.com>
2023-06-13  7:21   ` John Paul Adrian Glaubitz

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=d062dd7b09006c2d9988d92192952c65e66cf009.camel@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=debian-68k@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@lists.linux-m68k.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 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.