Permanodes are the anchors that keep your data alive and visible, so yes, your files should usually be somehow reachable through a permanode. Although it's not always direct; e.g. there could be a permanode only for a directory (static-set), but no permanode for each of the files in that directory (the static-set entries).
A rule of thumb to keep in mind for later: the garbage collector will start enumerating from the known roots and mark everything it can reach from there on. So if one of your files is not reachable through any schema relation (say as the camliContent of a permanode), it would not be marked, and would eventually be collected. Which is fair game since you wouldn't be able to find it back anyway. On 1 June 2016 at 01:51, Alok Parlikar <[email protected]> wrote: > Sorry I'm sending too many questions lately :-) > > I'm not quite sure which files I camput should, or should not be permanodes. > > Should I import all my data with --filenodes and make everything permanodes? > If so, when would I not create permanodes for something I camput? > > Alok > > -- > 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. -- 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.
