Hello Michael Biebl! On Sun, Aug 03, 2014 at 05:57:03PM +0200, Michael Biebl wrote: [...] > The uuid sysv init script creates /run/uuid as uuid:uuid. > Under systemd afaics that directory is created as a side-effect of > uuid.socket, the resulting permissions/owner being 755 root:root. > > Is there a reason why under sysvinit the directory has a different > owner/group? >
The reason is probably historic (and no longer needed). Not that I've been around for this, but I think the history lesson reads something like this: Once upon a time libuuid used to have a home-brew "socket activation" feature where the library would spawn uuidd on request. This was quite hacky and included the uuidd being setuid uuid and the directory where it put the socket had to be writable by the uuid user. Once systemd came along and solved the socket activation problem in a much better way, util-linux added real socket-activation to handle uuidd and the old home-brew solution was dropped (so socket activation is now only available when using systemd). Since then the suid uuid etc. is no longer needed. Unfortunately by this time everyone stopped caring about the sysvinit script and noone cared to clean it up for the changes that had happened elsewhere..... I sent a patch upstream to drop some of the in my opinion most misleading bits of the sysvinit script: https://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/misc-utils/uuidd.rc.in?id=928601e6307479de6929ac8e1f1c90750111f0b4 If anyone wants to work on improving/cleanup the sysvinit script further please feel free (also please send your patches upstream).... I'm not very interested myself (so in my mind this bug report is a wontfix).... Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
