Very helpful thread. Thanks, all :-) 

On Wednesday, May 11, 2016 at 5:20:16 AM UTC+5:30, mpl wrote:
>
> On 10 May 2016 at 18:42, Eric Drechsel <[email protected] <javascript:>> 
> wrote: 
> > On Tue, May 10, 2016, 5:22 AM Mathieu Lonjaret <[email protected] 
> <javascript:>> 
> > wrote: 
> >> 
> >> On 10 May 2016 at 07:15, Eric Drechsel <[email protected] <javascript:>> 
> wrote: 
> >> > On Sat, May 7, 2016 at 7:05 PM, Alok Parlikar <[email protected] 
> <javascript:>> 
> >> > wrote: 
> >> 
> >> >> (4) I think my $HOME should still be on disk, and not use the fuse 
> >> >> mount; 
> >> >> in that case, how easy is it to keep it in sync with camlistore? 
> >> > 
> >> > 
> >> > There are a couple of ways to map a directory structure into 
> Camlistore. 
> >> > 
> >> >  (a) camput file $PATH creates a static (deduplicated) snapshot of 
> the 
> >> > path. 
> >> > It's great for backups, and is the foundation on which the other mode 
> is 
> >> > built. You can restore with camget -o $OUTDIR $REF. 
> >> >  (b) camput file -filenodes $PATH creates a mutable "permanode" for 
> each 
> >> > file/directory under the path. This mode is appropriate when you plan 
> to 
> >> > treat Camlistore as the source of truth going forward.  Unlike (a), 
> the 
> >> > command isn't idempotent; each run creates a new set of permanodes. 
> You 
> >> > can 
> >> > also create permanodes by creating/copying directories under "roots/" 
> in 
> >> > the 
> >> > FUSE mount. 
> >> > 
> >> > If you are talking about bidirectional sync between the local 
> filesystem 
> >> > and 
> >> > permanodes, it's possible but requires some care. Always test first 
> on a 
> >> > throwaway instance (devcam server -wipe is your friend). The main 
> thing 
> >> > to 
> >> > be aware of: lots of user space programs spam temp files, and 
> cammount 
> >> > doesn't filter them out (yet). Also, depending on how a sync program 
> >> > operates, it may remove the original file and create a new one. I'd 
> like 
> >> > to 
> >> > document which sync software works, and flags are needed. As Mathieu 
> >> > said, 
> >> > you may want to wait. Help wanted :) 
> >> 
> >> Sorry, what? Where did I say to wait? Wait for what? 
> > 
> > 
> > I was referencing your reply to Alok's (4). 
>
> Oh, ok. that was meant as a "wait a minute" figure of speech, sorry 
> about the confusion. I don't think he needs to wait (for any of the 
> FUSE mount features) for achieving what he wants. 
>
> >> Wait. Camlistore is not really meant to replace your whole day to day 
> >> work filesystem, at least not right now. So yeah, you definitely still 
> >> want a traditional filesystem with a $HOME and everything on your 
> >> laptop. 
> > 
> > 
> > Where you advised not to try to use the FUSE mount as your home dir, I 
> was 
> > advising 
> > caution using it to _sync_ with your home dir, because there are a few 
> > limitations/issues 
> > to be aware of: 
> > 
> >  - Files deleted in FUSE aren't marked as deleted for the indexer. #711 
> >  - Ephemeral files are stored as permanodes (and with #711, aren't 
> actually 
> > deleted). #549, #419 
> >  - Some robustness issues. #554 #729 
> > 
> > Generally I think the FUSE subsystem is close to sound, but needs some 
> bug 
> > fix work and a QA cycle. 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Camlistore" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to [email protected] <javascript:>. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Camlistore" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to