On Di, 23.07.19 10:56, Adam Jackson (ajax@xxxxxxxxxx) wrote: > On Tue, 2019-07-23 at 11:01 +0200, Miroslav Suchý wrote: > > Hi, > > directories /proc/ and /sys/ are owned by filesystem package. This worked in past where we needed those directories to > > exist so we can mount the procfs and sysfs. > > > > However this cause issues in containers: > > https://bugzilla.redhat.com/show_bug.cgi?id=1548403 > > and during building where hacks are needed: > > https://github.com/rpm-software-management/mock/pull/234/commits/d7e0b413c83bec00fd1ed75ee15122a9cc6db62e > > > > 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. It does, if they are missing. In fact, it's totally supported to boot up with an empty / (for example: tmpfs, which is what systemd.volatile=yes on the kernel cmdline will do) with the one exception of a populated /usr and systemd will create all the basic mount points and symlinks needed to make the system boot. That said, that only works if / is writable. Which is not a given. Lennart -- Lennart Poettering, Berlin _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
