You are not logged in.

#1 2012-08-29 13:56:07

12eason
Banned
Registered: 2010-07-20
Posts: 103

systemd, pacman and kernel modules

Just a thought, once Arch has transferred to systemd, would it not be pretty easy to get pacman to install a conf file under /etc/modules-conf/ automatically, and remove it on uninstall?

Offline

#2 2012-08-29 15:50:40

hadrons123
Member
From: chennai
Registered: 2011-10-07
Posts: 1,249

Re: systemd, pacman and kernel modules

What are you even asking?
Be specific.

Offline

#3 2012-08-29 19:49:05

12eason
Banned
Registered: 2010-07-20
Posts: 103

Re: systemd, pacman and kernel modules

It's pretty self explanatory.

Offline

#4 2012-08-29 20:34:57

useradded
Member
From: Edinburgh, UK
Registered: 2010-05-15
Posts: 77

Re: systemd, pacman and kernel modules

No it isn't.

Offline

#5 2012-08-29 20:39:02

bohoomil
Banned
Registered: 2010-09-04
Posts: 2,377
Website

Re: systemd, pacman and kernel modules

12eason wrote:

Just a thought, once Arch has transferred to systemd, would it not be pretty easy to get pacman to install a conf file under /etc/modules-conf/ automatically, and remove it on uninstall?

No. It's up to you what extra modules are to be loaded, hence the directory should be empty unless needed.

BTW: You mean /etc/modules-load.d/?

Last edited by bohoomil (2012-08-29 20:40:31)


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

#6 2012-08-29 22:13:37

xduugu
Member
Registered: 2008-10-16
Posts: 292

Re: systemd, pacman and kernel modules

12eason wrote:

Just a thought, once Arch has transferred to systemd, would it not be pretty easy to get pacman to install a conf file under /etc/modules-conf/ automatically, and remove it on uninstall?

That's already the case for several modules, e.g. tp_smapi, and is independent from systemd. Also see Tom's mail.

Offline

#7 2012-08-29 22:14:35

12eason
Banned
Registered: 2010-07-20
Posts: 103

Re: systemd, pacman and kernel modules

bohoomil wrote:
12eason wrote:

Just a thought, once Arch has transferred to systemd, would it not be pretty easy to get pacman to install a conf file under /etc/modules-conf/ automatically, and remove it on uninstall?

No. It's up to you what extra modules are to be loaded, hence the directory should be empty unless needed.

BTW: You mean /etc/modules-load.d/?

Yes. What use case is there for someone installing a kernel module but not needing it loaded at boot? If they didn't want it, surely they would simply uninstall it? It seems to me that it such an unlikely use case that it would be better to install by default and let those few people that don't want it delete the conf themselves.

Offline

#8 2012-08-29 22:17:31

12eason
Banned
Registered: 2010-07-20
Posts: 103

Re: systemd, pacman and kernel modules

xduugu wrote:
12eason wrote:

Just a thought, once Arch has transferred to systemd, would it not be pretty easy to get pacman to install a conf file under /etc/modules-conf/ automatically, and remove it on uninstall?

That's already the case for several modules, e.g. tp_smapi, and is independent from systemd. Also see Tom's mail.

Okay, so why the inconsistency?

Tom's mail
The reasoning being that an admin is almost certainly not going to
want to install a package and then not follow the post-install
instructions. Conversely, on un-install (s)he is likely to want to
revert these changes.

Totally agree.

Last edited by 12eason (2012-08-29 22:20:51)

Offline

#9 2012-08-29 23:42:39

bohoomil
Banned
Registered: 2010-09-04
Posts: 2,377
Website

Re: systemd, pacman and kernel modules

12eason wrote:

What use case is there for someone installing a kernel module but not needing it loaded at boot? If they didn't want it, surely they would simply uninstall it? It seems to me that it such an unlikely use case that it would be better to install by default and let those few people that don't want it delete the conf themselves.

I don't need to load almost anything but vboxdrv: everything else is loaded automatically by udev. That's how it is supposed to work nowadays. Therefore the only file in /etc/modules-load.d/ is vboxdrv.conf.


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

#10 2012-08-30 07:24:08

xduugu
Member
Registered: 2008-10-16
Posts: 292

Re: systemd, pacman and kernel modules

12eason wrote:

Okay, so why the inconsistency?

I guess you mean why some packages include such a file and some not. As far as I know, there is no official policy for this yet and not every developer may be aware of this possibility. If you have a specific package in mind, just open a feature request and ask for the inclusion of a module-load.d configuration file.

Offline

#11 2012-08-30 14:39:14

12eason
Banned
Registered: 2010-07-20
Posts: 103

Re: systemd, pacman and kernel modules

bohoomil wrote:

I don't need to load almost anything but vboxdrv: everything else is loaded automatically by udev. That's how it is supposed to work nowadays. Therefore the only file in /etc/modules-load.d/ is vboxdrv.conf.

Udev only loads in-tree modules. You're right that there are only a very small number of kernel modules that require a conf file. I only have microcode and vboxdrv myself. It just seems to me that the default should be to install them all by default.

Offline

#12 2012-08-30 15:21:42

bohoomil
Banned
Registered: 2010-09-04
Posts: 2,377
Website

Re: systemd, pacman and kernel modules

Now I see what you mean. Well, as it has already been stated, the best you can do is fill a feature request or interrogate a developer in charge on the mailing list (the problem will be sooner examined by a competent person there).


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

Board footer

Powered by FluxBB