You are not logged in.
Another workaround may be to use bindfs and set it to ignore chown (let it succeed, but do nothing):
https://aur.archlinux.org/packages/bindfs
Last edited by progandy (2024-10-29 13:14:19)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Or, if this is NFS (I thik for CIFS you're fucked) just user proper posix permissions (at least for the relevant export, you can still squash the permissions for your por… media shares)
CIFS is discouraged anyway, because it doesn't support file names with colon (among other perfectly-acceptable-on-Linux characters); what's worse it will either:
write a file with no error, but after listing the directory the file will present itself as something like S4Y9SG~X.XZ.
write a file and present it via CIFS with correct name, but on the server colons will be substituted with U+F022.
To all those unaware - package names do contain colons sometimes, please use NFS or SSHFS or whatever that's Linux-file-names compliant.
I still wonder though - why was this change (i.e. chowning downloaded packages to root) introduced? Couldn't those downloaded files be kept owned by alpm?...
Last edited by madman_xxx (2024-11-09 23:16:14)
Offline
I still wonder though - why was this change (i.e. chowning downloaded packages to root) introduced?
Probably to secure teh cache against manipulations, notably since the database isn't signed.
W/ https://gitlab.archlinux.org/pacman/pac … ote_169363 it might "just" be to have the change being transparent.
Offline
It is supposed to limit possibility of the downloader making modification to the package cache. A remote possibility - and impossible with landlock support with modern linux kernels - but security is about the layers...
Offline