/etc/sysconfig/modules/

[Antonio Trande]

2012/9/19 Antonio Trande <anto.trande at gmail.com>

> 2012/9/19 Bill Nottingham <notting at redhat.com>
>
>> Sérgio Basto (sergio at serjux.com) said:
>> > Hi,
>> > In my F17 system
>> > rpm -qf  /etc/sysconfig/modules/*
>> > bluez-4.99-2.fc17.x86_64
>> > qemu-system-x86-1.0.1-1.fc17.x86_64
>> >
>> > on this
>> > http://fedora-os.org/2012/09/13/workaround-for-vbox-modules-loading/
>> > Antonio Trande says that modules of vbox ( don't matter what) doesn't
>> > load at boot time .
>> > But if this is true neither should boot bluez or qemu-system.
>> > 1 - Which package is responsibility to load modules
>> > from /etc/sysconfig/modules/ ?
>>
>> systemd *should* load it via the fedora-loadmodules.service.
>>
>> > 2 - Also in article mention that we should put this files
>> > in /etc/modules-load.d/ as part of systemd ,
>> > but
>> > yum provides /etc/modules-load.d/\*
>> > No Matches found
>> > shouldn't bluez, qemu-system-x86 etc etc  move loading modules
>> > to /etc/modules-load.d/  ?
>>
>> It should, but the old should still work for the time being.
>
>
> Hi Bill.
>
> It's right.
> I have just unmasked  'fedora-loadmodules.service' and vbox modules have
> been loaded without 'systemd-modules-load.service'
>
> $ systemctl status  fedora-loadmodules.service systemd-modules-load.service
> fedora-loadmodules.service - Load legacy module configuration
>   Loaded: loaded (/usr/lib/systemd/system/fedora-loadmodules.service;
> static)
>   Active: active (exited) since Wed, 19 Sep 2012 10:26:03 +0200; 3min 6s
> ago
>  Process: 279 ExecStart=/lib/systemd/fedora-loadmodules (code=exited,
> status=0/SUCCESS)
>   CGroup: name=systemd:/system/fedora-loadmodules.service
>
> Warning: Journal has been rotated since unit was started. Log output is
> incomplete or unavailable.
>
> systemd-modules-load.service
>   Loaded: masked (/dev/null)
>   Active: inactive (dead)
>
> Sep 17 12:47:59 local systemd-modules-load[258]: Inserted module
> 'vboxnetflt'
> Sep 17 19:34:57 local systemd-modules-load[2048]: Inserted module 'vboxdrv'
> Sep 17 19:34:57 local systemd-modules-load[2048]: Inserted module
> 'vboxnetflt'
> Sep 17 19:34:57 local systemd-modules-load[2048]: Inserted module
> 'vboxnetadp'
> Sep 18 09:38:06 local systemd-modules-load[284]: Inserted module 'vboxdrv'
> Sep 18 09:38:06 local systemd-modules-load[284]: Inserted module
> 'vboxnetflt'
> Sep 18 10:08:47 local systemd-modules-load[294]: Inserted module 'vboxdrv'
> Sep 18 10:08:47 local systemd-modules-load[294]: Inserted module
> 'vboxnetflt'
> Sep 19 10:12:10 local systemd-modules-load[246]: Inserted module 'vboxdrv'
> Sep 19 10:12:10 local systemd-modules-load[246]: Inserted module
> 'vboxnetflt'
>
> Warning: Unit file changed on disk, 'systemctl --system daemon-reload'
> recommended.
>

As long as another issue: at every reboot I am compelled to restart
 'fedora-loadmodules.service', otherwise the problem with vbox modules
arises again.



-- 
*Antonio Trande
"Fedora Ambassador"*
*"Fedora italian translation group"*
*"Blogger"

**mail*: mailto:sagitter at fedoraproject.org <sagitter at fedoraproject.org>
*Homepage*: http://www.fedora-os.org
*Sip Address* : sip:sagitter AT ekiga.net
*Jabber <http://jabber.org/>* :sagitter AT jabber.org
*GPG Key: 19E6DF27*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120926/4740dd57/attachment.html>