[Lumiera] Work-flow II - Capturing

[Serge GIELKENS]

On Fri, 13 Feb 2009 05:25:23 +0100
Christian Thaeter <ct at pipapo.org> wrote:


> A hardlink is just giving the data another name, but this name does not
> point indirectly to the old name and then to the data. It points
> directly to the data. So if you delete any other (even its original)
> name the hardlink holds still your data. Moreover the 'original' name
> has no special relevance, any other hardlink existing to that data is
> equal. Maybe this is a bit mindbending, but filenames and the data which
> is stored under this name are 2 things for the underlying unix
> filesystem even if you normally don't (need to) notice that as user.
> 
> So for a concrete example:
> 
> a user grabs footage into the project ~/test/ that becomes:
> 
>  ~/test/capture/foobar.dv
> 
> Now what can/will Lumiera do:
> 
> It creates a hash-sum or unique identifier for this file, lets suppose
> this is 12345.dv (in real it will be much longer). Then will link the
> original file into its repository:
> 
>  ln ~/test/capture/foobar.dv ~/.lumiera/repository/12345.dv
> 
> that means that this file (data) is now reachable over 2 names at
> different places on the filesystem. One is the name you gave it, the
> other is lumieras private repository which is hidden (and uninteresting)
> for the user. Lumiera can now use this to do some stunts:
> 

How does Lumiera handle footage that resides on another file system 
than ~/.lumiera?. Hard links cannot be used then.

I am sure this has already been discussed but I have skipped quite some
mails lately. Sorry in advance.

Serge