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

thoughts on chown/acl support #41

Open
jxsl13 opened this issue Dec 20, 2023 · 2 comments
Open

thoughts on chown/acl support #41

jxsl13 opened this issue Dec 20, 2023 · 2 comments

Comments

@jxsl13
Copy link

jxsl13 commented Dec 20, 2023

Just wondering if there are any thoughts about adding an abstraction for os.Chown (which for windows does work pretty badly as you need string SSIDs and the semantics differ from Linux in the regard that you don't change user (uid) and group (gid) at the same time like os.Chown does.

Seemingly ACLs are common on those platforms or changing file owner and file owner group independently of each other might be an approach.

Also getting the current owner and owner group or a list of all ACLs of a file might be another interesting feature which would be necessary for like copying files and applying the same ownership permissions as the source file had.

@pjbgf
Copy link
Member

pjbgf commented Dec 20, 2023

Hey @jxsl13, is there a specific use case you are trying to resolve?

@jxsl13
Copy link
Author

jxsl13 commented Dec 20, 2023

I'm trying to move my backupfs (backup on write fs abstraction layer with rollback mechanisms) from the afero interface to one that supports windows better and is more actively maintained.

This one: https://github.com/jxsl13/backupfs

(When running with elevated/root permissions, Chown becomes interesting.)

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