On Tue, Oct 28, 2014 at 12:45 PM, Tom Gundersen <teg@xxxxxxx> wrote: > On Tue, Oct 28, 2014 at 2:21 PM, Zbigniew Jędrzejewski-Szmek > <zbyszek@xxxxxxxxx> wrote: >> On Tue, Oct 28, 2014 at 12:23:53PM +0100, Tom Gundersen wrote: >>> On Tue, Oct 28, 2014 at 12:16 PM, Tom Gundersen <teg@xxxxxxx> wrote: >>> > On Tue, Oct 28, 2014 at 3:31 AM, Lucas De Marchi >>> > <lucas.de.marchi@xxxxxxxxx> wrote: >>> >> On Mon, Oct 27, 2014 at 2:55 PM, Tom Gundersen <teg@xxxxxxx> wrote: >>> >>> udev will only manage static nodes that exist at the time udev is started, so >>> >>> creating static nodes later on will likely not behave as expected. In >>> >>> particular, recreating the static nodes at run-time will reset any permissions >>> >>> udev may have applied to the nodes at boot. >>> >>> >>> >>> See <https://bugzilla.redhat.com/show_bug.cgi?id=1147248> and the discussion >>> >>> following <http://permalink.gmane.org/gmane.comp.sysutils.systemd.devel/23795>. >>> >>> >>> >>> Note that this requires (the yet to be released) systemd v217 or a backport >>> >>> of systemd patch 8c94052ee543c3598a3c7b0c46688150aa2c6168. >>> >> >>> >> Is this patch going to systemd-stable? >>> > >>> > I think that makes sense, as the current status is broken in distros. >>> > Not entirely sure though, as the --boot logic is new functionality. >>> > Zbigniew, what do you think? >> Yeah, I'll pull it into -stable. >> >> (But the kmod patch doesn't really depend on your patch 'units: >> tmpfiles-setup-dev - allow unsafe file creation to happen in /dev at >> boot', just on the --boot functionality, which I think was done for F20, >> so can be considered available.) > > It is true that even F20 will parse the new kmod.conf file correctly, > but since --boot is not passed to tmpfiles, the entries will be > ignored. So you really want that patch as well. Yeah, as far as I can see you need that as well. Applied. -- Lucas De Marchi -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
