It was <2013-11-18 pon 17:04>, when Schaufler, Casey wrote: >> -----Original Message----- >> From: Łukasz Stelmach [mailto:[email protected]] >> Sent: Monday, November 18, 2013 12:38 AM >> To: Schaufler, Casey >> >> It was <2013-11-15 pią 22:56>, when Schaufler, Casey wrote: >>> The User domain: >>> >>> The user experience is provided by the display manager and the >>> application launcher. They have been set to run in the User domain. >>> The appropriate manifest files will be updated as part of the merge. >>> Because these services are managed by systemd the User domain is >>> granted access to the System::Run label and hence the /run directory. >> >> What about $XDG_RUNTIME_DIR (/run/usr/$UID)? Shouldn't these >> directories be labeled with something like User::Run? > > That will depend on what talks to the user bus.
What does user bus have to do it? /run/user/$UID is a place where user processes can put their "non-essential runtime files and other file objects"[1]. These can be for example API sockets. > At this point all user processes are running with the label User. When > we start dividing the User domain into peer domains you're probably > right. We'll grill that fish when we've caught it. OK. >>> The /run directory is a resource managed by systemd and must not be >>> used as a repository for other data. >> >> <nitpicking> >> This isn't exactly true. UDisks2 for example mounts removable media under >> /run/media. >> </nitpicking> > > That puts them on separate filesystems, with their own smack > configuration. It would probably have been better to say "/run > filesystem" than "/run directory". I mean that systemd isn't the only process that manages content (creates directories) on the "/run filesystem". [1] http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html [2] http://cgit.freedesktop.org/udisks/tree/src/udiskslinuxfilesystem.c?id=bc5e358e4ad686a00e8df29a42aabb6332000d98#n890 -- Łukasz Stelmach Samsung R&D Institute Poland Samsung Electronics
pgpigLoFOKReH.pgp
Description: PGP signature
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
