Re: libfs/ FUSE on L4Re

Florian Pester <[email protected]>
Newsgroups gmane.comp.micro-kernel.l4.devel
Message-ID <[email protected]>
Hi,

sorry for the long wait.

On 08.12.2014 23:11, Stark, Josef wrote:
> I think that the client simply needs to be linked with
> "libl4revfs-fs-l4fs" and then do a mount call with "l4fs" as the fs type and
> the same mount path that the server uses (or use libmount accordingly).
yes, that should work.

> But I have no clue about the server. It most probably also needs to be
> linked with the respective library ("libfs-svr") but I think that's not 
> enough. I guess the messages explicitly must be forwarded to the
> target file system.
> If this is right, again I don't know how to do it,
> since the server (which mounts the tmpfs) receives VFS calls
> over IPC but has no direct access to the VFS "interface" of the tmpfs,
> only the standard (POSIX?) functions like fopen(), fclose(), fread() etc.
You still need a FUSE file system on top of tmpfs. During my Beleg I
also ported fuse-exfat (read: adjusted the Makefile to compile it). You
can find that here:
  http://os.inf.tu-dresden.de/~fpester/fuse-exfat-l4re.zip

Inside the zip file you will also find an examples directory, which has
two example clients. These may help to clarify things.

> Also,
>> It exists in the internal tree, it was just never promoted to go public.
> 
> does this mean that at one point there was a version
> of libfs that worked but wasn't continued and thus
> doesn't work on the current snapshot anymore,
> or is libfs still being maintained and just not present in the public tree?
It's just not present in the public tree.

Regards
Florian

_______________________________________________
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
signature.asc (application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUkXw6AAoJEKeWOAFWmFjjLcMP/0gMEyHTQsiUMJnV1wN3x1d5
HckIDJhHcmgBhK4TpmJjOynZVoPeTBDHFt2yBlw2f/j/Ph21w++nJoEwtxzrcok+
Goi0d16GFvW9O+dwb1SR5TBDb+/OK5/kBBeQD59qftHwlNsU2j8vaaH9i9sn9R8/
giwevbcc+pHVGjG0BX/Tzpls3repjK1N5fjNoTwiSwCcoES5OlXjS2Qz0e5G+dc1
qtdQlcJ8PKzsasOHtr+vP12Dgym3F7Cfc1++GOAQTewB+8gkMGo5Z0AeAwlQC1Dm
5P6QQ340TJ2TCFxWRGwVLZ1RvNm8xs0LQrc/BnjkysOCvcBQTWpZcQlsyIokHait
eUm9qUmM5tl5YSltLzxpr1K8uXqPm/90mTXUTCHfwQ9AxtrZWvgWqTFWvG2kZE4n
JFpcXYj071R2ZhB5XS5iaHGC4bJpjS2S/BxqoX5SBes/gRbiGGQqq/E2v6RHchVu
2j1TKTG2wkSeJ8fqhNoRRkAxz6HTljSdmgJxHTdKXvzwUycXxGQ359eADINXWSD2
HzB7kEg2yM6t/QKJ52iJrjUVBKqEBlODyhWH9JtfVanUvawGuwzGAUOt0aohb/0u
pE8Kl41UBFCxa3O0RPpBSBHb1l/tanus9Tto5mKvEfMxIK9AKkxhx0a1E22vddEG
0rkabccroOFHh3IFM5Et
=g+Tl
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.