On Sat, 2012-03-24 at 00:11 +0100, Martin Jansa wrote: > On Sat, Mar 24, 2012 at 12:00:04AM +0100, Andreas Oberritter wrote: > > On 23.03.2012 13:56, Martin Jansa wrote: > > > * /etc/modules-load.d/foo.conf is used by systemd like /etc/modutils/foo > > > was with sysvinit > > > > Martin, > > > > the man-page[1] for modules-load.d says that packages should install > > .conf files to /usr/lib/modules-load.d, because /etc/modules-load.d is > > reserved for the system administrator. Did you take this into account > > when you decided to support /etc/modules-load.d? > > You're right, /usr/lib/modules-load.d could be possibly better option. > I've used /etc mostly because I was using it since my first systemd > image (so I was sure it works) and I don't remember seeing /usr/lib in > man page when I was reading it back then (probably overlooked or > forgot). > > Is it worth updating update-modules (maybe teaching update-modules to > look into all possible systemd directories too)?
I think in our case, we'd need to have /lib/modules-load.d and /usr/lib/modules-load.d depending on whether the module was meant to load without /usr being mounted. Using /etc for now seems to make most sense although it probably wouldn't hurt for the script to look at the other locations. Cheers, Richard _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
