From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] m.2 nvme stick not what I was expecting at all.
Date: Tue, 25 Feb 2025 12:05:12 -0500 [thread overview]
Message-ID: <CAGfcS_mQQPr6r9z4WDf1_24=XwPU=qs_WggjedhusT2e2mSang@mail.gmail.com> (raw)
In-Reply-To: <353bd04b-3cd7-1da9-25f8-92497e59b9f8@gmail.com>
On Tue, Feb 25, 2025 at 10:57 AM Dale <rdalek1967@gmail.com> wrote:
>
> Still, is FUSE the best way to handle this or should it be done the same way as EXT4? I don't recall enabling FUSE so I figure it is enabled by default or something.
ext4 is a filesystem. FUSE is a kernel API that can be used to
implement any filesystem.
I'm pretty sure there is a kernel setting to enable FUSE, and it is
pretty typical for it to be enabled. Lots of stuff uses it.
In many operating systems (with a microkernel architecture) the
equivalent of FUSE is the only way filesystems are implemented.
Usually people prefer to use built-in kernel drivers if they are
available. There isn't really anything wrong with FUSE, but in many
cases the in-kernel drivers are just better maintained.
It isn't unusual to see less conventional "filesystems" implemented as
FUSE first, since this is more maintainable if you never intend to get
your work integrated into the kernel. FUSE uses the stable system
call interface, while an actual kernel module has no stable interface
and is therefore more painful to maintain outside of the mainline
kernel. For example, see sshfs, gzipfs, restic, etc. I know a guy
who created a novelty "filesystem" that just creates files dynamically
using the filename as GPT prompts. Stuff like that would never be
accepted into the mainline kernel, but they can be implemented
reliably using FUSE.
--
Rich
next prev parent reply other threads:[~2025-02-25 17:06 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 18:58 [gentoo-user] m.2 nvme stick not what I was expecting at all Dale
2025-02-24 19:20 ` Jack
2025-02-24 19:49 ` Dale
2025-02-24 19:40 ` Mark Knecht
2025-02-24 19:41 ` Rich Freeman
2025-02-24 19:53 ` Dale
2025-02-24 20:00 ` Rich Freeman
2025-02-24 20:34 ` Dale
2025-02-24 20:02 ` eric
2025-02-24 20:11 ` Mark Knecht
2025-02-24 20:44 ` Dale
2025-02-24 22:48 ` Frank Steinmetzger
2025-02-25 3:56 ` Dale
2025-02-25 10:08 ` Michael
2025-02-25 11:00 ` Dale
2025-02-25 11:16 ` Michael
2025-02-25 15:57 ` Dale
2025-02-25 17:05 ` Rich Freeman [this message]
2025-02-25 19:00 ` Michael
2025-02-25 19:18 ` Rich Freeman
2025-02-25 20:39 ` Michael
2025-02-25 22:16 ` Frank Steinmetzger
2025-02-25 14:48 ` Peter Humphrey
2025-02-25 17:00 ` Michael
2025-02-24 22:13 ` Frank Steinmetzger
2025-02-25 4:20 ` Dale
2025-02-25 8:18 ` Wols Lists
2025-02-25 14:07 ` [gentoo-user] " Grant Edwards
2025-02-25 8:20 ` [gentoo-user] " Wols Lists
2025-02-25 11:09 ` Dale
2025-02-25 12:26 ` Dale
2025-02-25 15:04 ` Rich Freeman
2025-02-25 15:32 ` Dale
2025-02-25 16:29 ` Rich Freeman
2025-02-25 17:26 ` Dale
2025-02-25 17:41 ` Rich Freeman
2025-02-26 14:43 ` Dale
2025-02-26 16:38 ` Michael
2025-02-26 20:34 ` Dale
2025-02-26 20:48 ` Mark Knecht
2025-02-25 20:19 ` Wol
2025-02-25 20:21 ` Michael
2025-02-25 21:34 ` Frank Steinmetzger
2025-02-26 7:52 ` Wols Lists
2025-02-26 16:44 ` Michael
2025-02-26 18:03 ` Wol
2025-02-26 18:05 ` Rich Freeman
2025-02-26 18:42 ` Wol
2025-02-26 19:26 ` Rich Freeman
2025-02-26 19:47 ` Wols Lists
2025-02-26 19:56 ` Rich Freeman
2025-02-26 21:25 ` Wol
2025-02-26 22:37 ` Michael
2025-02-26 16:41 ` Michael
2025-02-28 5:43 ` Dale
2025-02-28 16:40 ` [gentoo-user] " Grant Edwards
2025-03-02 16:01 ` Dale
2025-03-02 22:06 ` Frank Steinmetzger
2025-03-02 22:39 ` Dale
2025-03-03 3:01 ` Grant Edwards
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='CAGfcS_mQQPr6r9z4WDf1_24=XwPU=qs_WggjedhusT2e2mSang@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.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