On Fri, Jul 12, 2013 at 08:42:31PM +0200, Lennart Poettering wrote: > On Fri, 12.07.13 20:37, Tom Gundersen ([email protected]) wrote: > > > > > On Fri, Jul 12, 2013 at 7:57 PM, Zbigniew Jędrzejewski-Szmek > > <[email protected]> wrote: > > > I see another problem: in a container, this unit fails with: > > > # /usr/bin/kmod static-nodes --format=tmpfiles > > > --output=/run/tmpfiles.d/kmod.conf > > > Error: could not open /lib/modules/3.9.6-301.fc19.x86_64/modules.devname > > > - No such file or directory > > > There was no requirement to have the kernel installation available before, > > > and it'd be stupid to add it just for that. > > > > Except for the failed unit, this doesn't cause any other problems, > > right? It used to be that the missing modules.devname file would be > > silently ignored. I guess we could go back to doing that. Yes, in this case it doesn't matter at all, because udev doesn't do anyting anyway in the container.
> Maybe add a condition check for it? > > Might be hard with the with kernel version in the path, but we could add > a %v or so for this which resolves to the output of "uname -r". Which > could be really useful anyway, wherever things are done with kernels, > initrds, modules? I'm not sure if it is needed in this case, but %v sounds useful. Zbyszek _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
