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 it possible to change files without recreating Erofs ? #10

Open
seci20 opened this issue May 9, 2024 · 3 comments
Open

Is it possible to change files without recreating Erofs ? #10

seci20 opened this issue May 9, 2024 · 3 comments

Comments

@seci20
Copy link

seci20 commented May 9, 2024

Can a file be added to an img file of type erofs? Or can it be changed?

@hsiangkao
Copy link
Collaborator

Yes, it sounds a feature to have,
but how appending mode works. If a file is deleted or replaced, do we need to reuse the allocated space?

Also how does it work with reproducible builds? Assuming there is a tree A, and a delta tree B.
You almost cannot get the same image of (appending B to A) and rebuilding a new A+B image.

Anyway, I'd like to say how you define adding: rebuilding or some else.

@seci20
Copy link
Author

seci20 commented May 31, 2024

I reviewed some software that can change the existing file. Is it possible to make a replacement? They just changed the inode addresses and contents, file name etc. they were all the same.

@hsiangkao
Copy link
Collaborator

I reviewed some software that can change the existing file. Is it possible to make a replacement? They just changed the inode addresses and contents, file name etc. they were all the same.

I guess these softwares are quite incomplete since basically you might need some overlayfs-like semantics.
EROFS will have a very preliminary incremental mode in the upcoming erofs-utils, you could try when the new version releases, but it definitely needs more time to make it mature.

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