On Thu, Mar 14, 2013 at 11:43:32AM +0100, Michal Sekletár wrote: > On Thu, Mar 14, 2013 at 3:33 AM, Zbigniew Jędrzejewski-Szmek > <[email protected]> wrote: > > Hi, > > > > Colin Walters wrote > >>> install-directories-hook: > >>> $(MKDIR_P) $(addprefix $(DESTDIR),$(INSTALL_DIRS)) > >>> + $(MKDIR_P) -m 000 $(addprefix $(DESTDIR),$(INACCESSIBLE_DIR)) > >> Ugh. Can you make this /run/systemd/inaccessible or something, and > >> have systemd do this at runtime? > > > >> Having systemd install a directory with mode 0 is going to screw with > >> a lot of build systems. > > > > Indeed. Even our own 'make distcheck' fails badly with this patch. > > What do you think about the idea of creating /run/systemd/inaccessible > > on first use? > > > > (Note: there's an error there, and the $(addprefix) call is not needed. > > But if this line will be removed this doesn't matter.) > > > > Zbyszek > > Hi Zbyszek, > > It was my intention to do it at runtime, however I couldn't figure out > when it is the right time to do it. I wanted to do it once, and not to > check for this directory everytime we are spawning a new process which > needs it. Do you have any idea, when is the right time to do it, such > that it will work for all scenarios (with dracut, in containers, > etc...) ? Maybe just stick it in mount_setup()?
> > Do you prefer to have it /run or in /tmp? It seems to be without much difference, but I'd go for /run, since this way there'll be less chance that somebody deletes it by mistake. Zbyszek _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
