[Tux3] Tux3 fuse port

[Daniel Phillips]

On Sunday 07 September 2008 04:27, Tero Roponen wrote:
> 
> On Sat, 6 Sep 2008, Daniel Phillips wrote:
> 
> > Conrad, I would like to hand this back to you and go back to working
> > on the guts of tux3.  The biggest issue is, you can't just use the
> > path that fuse hands you as a filename.  At least it has to be broken
> > into a directory path and a filename.  But that is not the way we
> > should do it here, notice that fuse has fuse_file_info->fh where we
> > can store the tux3 inode in the fuse open, then ignore the filename
> > in all other operations except for debug traces.  Exceptions to this
> > are unlink and rename, where the only choice I can see is to split
> > the fuse name into path and file.  I am not sure why fuse does not do
> > that for us.
> 
> Hi,
> 
> this is my attempt to port the tux3 fuse implementation to lowlevel ops.
> I can't guarantee that it works, because this is just a quick weekend hack
> to get familiar with tux3. I hope somebody finds this useful, but
> unfortunately I don't have time to maintain this myself.

A most excellent weekend project, thankyou!  And the weekend isn't even
over yet, is it?  I see code in there I wrote yesterday... very fast
turnaround.  I compiled it, it works as far as I tried it.  I am not sure
whether we should discard the high level version at this point.  I kind
of doubt it will ever work properly but we shall see.  I think I will
check this one in as tux3fuse, the other will remain tux3fs.

Would you care to comment on what you think needs doing to the readdir?

Regards,

Daniel

_______________________________________________
Tux3 mailing list
Tux3 at tux3.org
http://tux3.org/cgi-bin/mailman/listinfo/tux3