public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Weekly Report: Fusebox - FUSE Porwered sandbox project
Date: Sun, 21 Jun 2020 20:21:39 +0200	[thread overview]
Message-ID: <2985923d2fecef8fa048048f77ef95fd27ea1516.camel@gentoo.org> (raw)
In-Reply-To: <CAHuS14MB1_RBJJPac_+VyvUCk_nxwTf8+-A4R7phxeh8iXQYEQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

On Sun, 2020-06-21 at 20:17 +0900, Kaoru Esashika wrote:
> Hi,
> This week, I implemented some FUSE interface.
> Therefore, the emerge program can work well on my Fusebox filesystem.
> However, I ran into a few problems when we tried to implement it.
> I've written about the problem and explanation about FUSE on my blog.
> If you interested, please check
> https://blog.pluser.net/en/posts/2020/gsoc-milestone-1/
> Now I need to integrate Fusebox to the emerge program. But I don't
> familiar with the emerge program well, I need to read the code...
> 

The questions I'd like to see answered are:

1. From our talking you indicated that FUSE has both high-level and low-
level API.  However, the post only hints at it.  Could you explain both
shortly and why you've chosen the one you've chosen?

2. How are you planning to deal with the essential problem that
the underlying directory tree may consist of multiple filesystems with
different files having colliding inode numbers?

3. How do other passthrough filesystems deal with the same problem?
 What are the advantages/disadvantages of different approaches you've
considered, and why did you chose this solution?


-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2020-06-21 18:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21 11:17 [gentoo-soc] Weekly Report: Fusebox - FUSE Porwered sandbox project Kaoru Esashika
2020-06-21 18:21 ` Michał Górny [this message]
2020-06-22 16:17   ` Kaoru Esashika
2020-06-22 18:02     ` Michał Górny
  -- strict thread matches above, loose matches on Subject: below --
2020-08-24  9:55 Kaoru Esashika
2020-08-17  8:27 Kaoru Esashika
2020-08-09 23:00 Kaoru Esashika
2020-08-02 23:00 Kaoru Esashika
2020-07-26 23:00 Kaoru Esashika
2020-07-27  4:48 ` EBo
2020-07-28 20:08   ` Kaoru Esashika
2020-07-28 20:24     ` EBo
2020-07-19 23:00 Kaoru Esashika
2020-07-12 23:00 Kaoru Esashika
2020-07-06  2:10 Kaoru Esashika
2020-06-28 18:47 Kaoru Esashika
2020-06-14 11:41 Kaoru Esashika

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=2985923d2fecef8fa048048f77ef95fd27ea1516.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-soc@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