Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this case use correct, or is it a risky way of doing things? #87

Open
cesss opened this issue Jan 20, 2019 · 1 comment
Open

Is this case use correct, or is it a risky way of doing things? #87

cesss opened this issue Jan 20, 2019 · 1 comment

Comments

@cesss
Copy link

cesss commented Jan 20, 2019

I have several read-only branches, and each of them has /bin and /lib subdirectories. Then I have a read-write branch which is completely empty (ie: it has no /bin nor /lib subdirs inside).

Then I create the union mount as 'unionfs -o cow branches/store=RW:branches/1=RO:branches/2=RO:branches/3=RO:branches/4=RO myunion'

And then I create a new file myunion/bin/newcommand

I verified that a new /bin subdirectory is then created in branches/store (the only RW branch, which was initially empty), and the 'newcommand' file is put in branches/store/bin/newcommand

This is behaviour I desire, but should I have created the /bin directory inside branches/store before mounting the union, or is it perfectly OK to leave to unionfs-fuse the task of creating the /bin directory?

Thanks!!

@mrvn
Copy link

mrvn commented May 14, 2021

That's perfectly OK.

This issue should be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants