Bug#808997: Processed: Re: Missing /usr path in modules-load.d(5)

Felipe Sateler fsateler at debian.org
Sat Dec 26 19:53:21 GMT 2015


On 26 Dec 2015 04:55, "martin f krafft" <madduck at debian.org> wrote:
>
> also sprach Jörg Frings-Fürst <debian at jff-webhosting.net> [2015-12-26
11:48 +1300]:
> > Care to elaborate why?
>
> Sorry, it's not terribly useful to augment the original bug report
> that I first cloned.
>
> Basically, /usr/lib/modules-load.d is not supported by upstream, and
> eventually we want to converge with upstream. For this to happen,
> packages will need to stop using /usr/lib/modules-load.d and as
> there is no real problem with using /lib/modules-load.d, I filed
> this bug report.

I'm sorry if I gave you this impression, but this is not the case. The
canonical upstream path is indeed /usr. However,  because in debian we use
split-usr, the path is moved to /. Because the /usr path is not documented
when using split-usr, users will become confused (as you did) when a module
is loaded and they can't find who instructed that module to load.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151226/b458ed3c/attachment-0005.html>


More information about the Pkg-systemd-maintainers mailing list