mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] systemd: Install configuration files for systemd-modules-load.service
Date: Wed, 7 Aug 2019 12:47:58 +0200	[thread overview]
Message-ID: <20190807104758.kfxmrjxtvns4s4j2@pengutronix.de> (raw)
In-Reply-To: <20190723135311.21924-1-lapeddk@gmail.com>

On Tue, Jul 23, 2019 at 03:53:11PM +0200, Lars Pedersen wrote:
> Signed-off-by: Lars Pedersen <lapeddk@gmail.com>

No. This is very similar to SYSTEMD_UDEV_CUST_RULES and that turned out to
be a bad idea.
The problem with stuff like this is, that as soon as BSPs get a little bit
more complex, options like this start to conflict with packages that want
to install individual files from these directories.

And in most cases, there are other files that are installed anyways to use
the functionality provided by the modules that are loaded, so the config
file should be installed together with those anyways.

Michael

> ---
> v2: Added systemd prefix to title
>  rules/systemd.in   | 5 +++++
>  rules/systemd.make | 4 ++++
>  2 files changed, 9 insertions(+)
> 
> diff --git a/rules/systemd.in b/rules/systemd.in
> index 5ce43b99c..c7f410cf7 100644
> --- a/rules/systemd.in
> +++ b/rules/systemd.in
> @@ -169,6 +169,11 @@ config SYSTEMD_UDEV_CUST_RULES
>  	  This will install the customized udev rules files from
>  	  'projectroot/usr/lib/udev/rules.d' into '/usr/lib/udev/rules.d'
>  
> +config SYSTEMD_MODULES_LOAD_D
> +	bool
> +	default n
> +		prompt "install kernel modules to load at boot"
> +
>  endmenu
>  
>  menu "persistent device node links  "
> diff --git a/rules/systemd.make b/rules/systemd.make
> index da375fd89..4bed33be5 100644
> --- a/rules/systemd.make
> +++ b/rules/systemd.make
> @@ -452,6 +452,10 @@ ifdef PTXCONF_SYSTEMD_UDEV_CUST_RULES
>  	@$(call install_alternative_tree, systemd, 0, 0, /usr/lib/udev/rules.d)
>  endif
>  
> +ifdef PTXCONF_SYSTEMD_MODULES_LOAD_D
> +	@$(call install_alternative_tree, systemd, 0, 0, /usr/lib/modules-load.d)
> +endif
> +
>  	@$(call install_finish, systemd)
>  
>  	@$(call touch)
> -- 
> 2.21.0
> 
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2019-08-07 10:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 13:35 [ptxdist] [PATCH] " Lars Pedersen
2019-07-23 13:53 ` [ptxdist] [PATCH v2] systemd: " Lars Pedersen
2019-08-07 10:47   ` Michael Olbrich [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190807104758.kfxmrjxtvns4s4j2@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox