https://bugzilla.suse.com/show_bug.cgi?id=1204929 https://bugzilla.suse.com/show_bug.cgi?id=1204929#c13 --- Comment #13 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Antonio Feijoo from comment #12)
(In reply to Thomas Blume from comment #11)
So, most probably the chown shouldn't be necessary.
I case of:
https://bugzilla.suse.com/show_bug.cgi?id=1177461#c39
it seems that /run/rpcbind was already present with wrong permissions. So, I guess an "rm -rf /run/rpcbind" instead of a chown in the initrd would do.
Thanks Thomas. The /run/rpcbind directory is created by root in the initrd (see comment #6 - https://github.com/dracutdevs/dracut/blob/master/modules.d/95nfs/nfs-start- rpc.sh#L10-L14), that's why the chown is done after. Then, IIUC we can avoid the mkdir and the chown, because rpcbind will create /run/rpcbind if it does not exist, right?
Yes, the change came in 2016: --> commit 2e78e6fb51292fea798355e5cb749dbc1de26ca6 Author: NeilBrown <neilb@suse.com> Date: Wed Nov 16 10:53:07 2016 -0500 Move default state-dir to a subdirectory of /var/run --< that should cover all dracut versions we maintain.
And, does the same apply to the /var/lib/rpcbind directory (see https://github.com/dracutdevs/dracut/blob/master/modules.d/95nfs/parse- nfsroot.sh#L126-L128), could we skip that mkdir & chown?
At least for SUSE that directory is obsolete: --> ------------------------------------------------------------------- Sat Nov 12 21:19:10 CET 2016 - kukuk@suse.de - Move /var/lib/rpcbind to /run/rpcbind, data should not survive reboot and this makes read-only root filesystem easier. --< and there is no code in rpcbind to create it. Still, it might be present on other distros. -- You are receiving this mail because: You are on the CC list for the bug.