From: The Mariocrafter <kayvonkamyar@gmail.com>
To: linux-m68k@vger.kernel.org
Subject: MFS Filesystem support
Date: Sun, 14 Apr 2024 16:07:47 -0700 [thread overview]
Message-ID: <CAEgzAWxZOMZYSzsiJJxOAy5otCGBvOZe9STGdjkkzWZa5p3dvg@mail.gmail.com> (raw)
Macintosh File System (MFS) is a filesystem used in early Macintosh
models up to those running System 3, when the original HFS (which is
supported within Linux) supported it. Although no Mac model that
shipped or can run with an MFS-only macOS can run Linux, floppy disks
formatted with an MFS system may still exist and the user never
bothered to reformat it to HFS or HFS+, and the main use case I can
think of is using MFS to transfer files from a modern device to a Mac
that does not support HFS. It would be nice supporting the MFS
filesystem natively within Linux, which could be read-only or
read-write.
MFS is a very limited filesystem, meaning it's simple to implement,
albeit being less efficient than its successors. MFS stored files in a
single flat structure without subdirectories; the illusion of
"folders" was created by including a "directory handle" in each file
entry so that the single directory could be scanned to find files that
belong to a particular virtual folder. File names could be up to 255
characters, though Finder didn't support more than 63 or 31 characters
(depending on the version). Resource Forks were introduced in MFS. An
MFS volume consists of a boot block, a master directory block, some
file directory blocks, and some allocation blocks. It may also have a
backup master directory block, but this is optional. These blocks are
each defined in terms of 512-byte sectors. Unless otherwise specified,
all values are big-endian (MSB first). Information about the
filesystem is relatively easy to find.
next reply other threads:[~2024-04-14 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 23:07 The Mariocrafter [this message]
2024-04-15 1:25 ` MFS Filesystem support Josh Juran
2024-04-15 1:39 ` Michael Schmitz
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=CAEgzAWxZOMZYSzsiJJxOAy5otCGBvOZe9STGdjkkzWZa5p3dvg@mail.gmail.com \
--to=kayvonkamyar@gmail.com \
--cc=linux-m68k@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 read-only IMAP folder(s) and NNTP newsgroup(s).