> But I am chaging my mind again, and thinking about another new option
> "nocheck".
>
> - without "nocheck" (default), aufs checks the consistency even if the
> src/dst are specified.
> - specifying "nocheck" explicitly, aufs skips the check. this option is
> just for the users who know what
"V.Krishn":
> alternatives:
> "rm" has option " prompt before every removal"
> and "mv" has --interactive
> maybe something similar
> or other option could be
> --safe-mode (opposite of default nocheck)
Thans for comment.
I believe it is worth to implement the --interactive option.
J. R. Okajim
Feature sounds interesting.
> I see.
> That was very similar to what I was thinking.
> - by default, without specifying source/target branches, src is the
> first branch where the file exist and dst is the next lower writable
> branch. in this case, of course, the consistency is checked.
> - w
Tomas M:
> I think user should be able to specify source and target branches, and
> I see no problem in that, if there is no file with the same name in
> the middle (in a branch between the source and target branches).
>
> I would suggest to check existence of the same file on all branches
> betwe
I think user should be able to specify source and target branches, and
I see no problem in that, if there is no file with the same name in
the middle (in a branch between the source and target branches).
I would suggest to check existence of the same file on all branches
between source and target,
Tomas,
Thank you for the comment.
Tomas M:
> 1: /rw/file.txt (most recently updated, copied-up here, some time ago already)
> 2: /ro/file.txt (readonly original)
> 3: /rw/ (empty writable branch)
:::
> 1: /rw/
> 2: /ro/file.txt (readonly original)
> 3: /rw/file.txt (most recently updated)
Imagine a file /union/file.txt in these branches:
1: /rw/file.txt (most recently updated, copied-up here, some time ago already)
2: /ro/file.txt (readonly original)
3: /rw/ (empty writable branch)
Consider 1 is the first writable branch.
User can edit file.txt in /union and changes are stored in
Hello all,
I am considering a new feature "move-down", which will be a first step
of "file-based hierarchy storage management."
Here is a simple document for it. And I want you to try reading it and
post a comment.
Thanks in advance.
J. R. Okajima
Move-down
---
