On Mi, 24.07.19 13:24, Jun Aruga (jar...@redhat.com) wrote: > Sorry I posted my previous email wrongly. > > > > I have bunch of ideas, but all of them ugly (e.g., not own that file and > > > create that directories in scriptlet). Do you > > > have any ideas about this situation? > > > > Make systemd create them? It has to manage them anyway. > > I see this situation to think about the ownership of /proc happens > when qemu-user-static RPM creates new > /proc/sys/fs/binfmt_misc/qemu-$cpu files by "dnf install > qemu-user-static" through running systemd. [1] > Who is the owner of the /proc/sys/fs/binfmt_misc/qemu-$cpu files? > The possible solution I am considering is "(e.g., not own that file > and create that directories in scriptlet)".
These directories are runtime objects, i.e. kernel API exposed as a file system. RPM should not own files below /proc. Something should own/create /proc itself, since it needs to exist to be overmounted with procfs, but beyond that stuff below /proc should be off limits for any package manager I figure. Lennart -- Lennart Poettering, Berlin _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
