Re: [fuse-devel] How FUSE mount works?

[Paul A. <pau...@gm...>]

You are running a program of your construction. It can do whatever it's
allowed to do -- network communication, file system operations, USB or
serial access. It's up to you to translate the file operation attempted
within the fuse directory to some other activity, including real file
access.

It's a little hard to make that leap of abstraction, but once you get it,
you start to see the power of FUSE.

Paul Alfille

On 12/6/06, Fareha Shafique <fa...@ee...> wrote:
>
> Paul Alfille wrote:
>
> > If I understand your question correctly, Fuse does not necessarily
> > mount an actual source to a destination. Instead, file system requests
> > to a path within the destination (mounted) directory are handled by
> Fuse.
> >
> > This means you can create virtual directories and files. You can also,
> > of course, return actual physical file contents, perhaps parsed or
> > organized differently.
> >
> > If your question is how can you send information to your Fuse program
> > about a "source" or even how to send other parameters, perhaps the
> > easiest way is simply to parse the command line for whatever syntax
> > you wish.
> >
> > Paul Alfille
>
>
> You said, "This means you can create *virtual* directories and files."
> Its not actually possible to create real, physical files and directores
> inside the mounted directory? So all the file systems that use FUSE
> either use another directory in the system to physically create files
> and directories, or just keep track of things in the code to 'emulate' a
> file system?
>
> Thanks,
> Fareha
>
>