From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: "Serge E. Hallyn" <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Cc: Jon Zhu <jon.zhu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Does Linux-CR+LXC support FUSE
Date: Sun, 10 Apr 2011 12:18:42 -0400 [thread overview]
Message-ID: <4DA1D862.3010505@cs.columbia.edu> (raw)
In-Reply-To: <20110311182941.GA11570-BtbdaCaBcfOTUehee3IRJA@public.gmane.org>
On 03/11/2011 01:29 PM, Serge E. Hallyn wrote:
> Quoting Jon Zhu (jon.zhu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org):
>> Hi,
>>
>> Just wondering if Linux-CR+LXC support FUSE or not, FUSE(
>> http://fuse.sourceforge.net/) is a pupular file system development platform
>> which is being widely used by lots of distributed file systems.
>>
>> Can anyone shed some light on this?
>
> No. But there's nothing stopping it. Each of the fuse filesystems
> would have to define a fops->checkpoint() method.
In fact, I suspect for many if not most of the FUSE filesystems, the
all-purpose "generic_file_checkpoint()" would be sufficient.
The only problem with doing that by default, is that it break silently
when used with those few that need more; i.e. checkpoint will work but
restart may not succeed later.
Oren.
prev parent reply other threads:[~2011-04-10 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 18:11 Does Linux-CR+LXC support FUSE Jon Zhu
[not found] ` <AANLkTim-bB7c7=sb+g7sC7+MM-Z6uHLYFfFJf=c7Cd2a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-11 18:29 ` Serge E. Hallyn
[not found] ` <20110311182941.GA11570-BtbdaCaBcfOTUehee3IRJA@public.gmane.org>
2011-04-10 16:18 ` Oren Laadan [this message]
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=4DA1D862.3010505@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jon.zhu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.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