[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6c5339f0804180743h6f3915c7tf08ed6cb920a152f@mail.gmail.com>
Date: Fri, 18 Apr 2008 10:43:57 -0400
From: "Bob Copeland" <me@...copeland.com>
To: "Miklos Szeredi" <miklos@...redi.hu>
Cc: szaka@...s-3g.org, hch@...radead.org, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 0/7] OMFS filesystem version 3
On Fri, Apr 18, 2008 at 10:23 AM, Miklos Szeredi <miklos@...redi.hu> wrote:
> Fuse has two different APIs. For the "high level", path based one,
> this is true. The "low level" one is very similar to the one provided
> by the VFS.
Ah nice, I do not know how I missed that. Thanks for pointing that out.
> And I think the VFS is great. Undoubtedly kernel programming has it's
> own charm, and I definitely don't want to scare you away from that.
> Merging into mainline is a great reward, which must be erned the hard
> way. The debate is just part of that ;)
>
> I also want to dispel any myths surrounding fuse, because those help
> nobody.
Sure. I'll go on record saying that omfs_fuse was written over a weekend and
can not be considered a good example of anything. I already had a
proto-libomfs that I had made for omfsck and mkomfs, and wanted to see how
easy it would be to wire that stuff up into a FUSE fs. Pretty easily, it
turned out.
--
Bob Copeland %% www.bobcopeland.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists