/etc/sysconfig/modules/

[Sérgio Basto]

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/ ? 

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/  ? 

Thanks,
-- 
Sérgio M. B.

[Bill Nottingham]

Sérgio Basto (sergio(a)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.

Bill

[Antonio Trande]

2012/9/19 Bill Nottingham <notting(a)redhat.com&gt;

>  Sérgio Basto (sergio(a)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.



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

**mail*: mailto:[e-mail] <sagitter(a)fedoraproject.org&gt;
*Homepage*: http://www.fedora-os.org
*Sip Address* : sip:sagitter AT ekiga.net
*Jabber <http://jabber.org/>* :sagitter AT jabber.org
*GPG Key: 19E6DF27*

[Antonio Trande]

2012/9/19 Antonio Trande <anto.trande(a)gmail.com&gt;

>  2012/9/19 Bill Nottingham <notting(a)redhat.com&gt;
>
> > Sérgio Basto (sergio(a)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:[e-mail] <sagitter(a)fedoraproject.org&gt;
*Homepage*: http://www.fedora-os.org
*Sip Address* : sip:sagitter AT ekiga.net
*Jabber <http://jabber.org/>* :sagitter AT jabber.org
*GPG Key: 19E6DF27*

[Sérgio Basto]

On Qua, 2012-09-26 at 17:04 +0200, Antonio Trande wrote:
>  As long as another issue: at every reboot I am compelled to restart
>  'fedora-loadmodules.service', otherwise the problem with vbox modules
>  arises again.  
No , fedora-loadmodules.service run at startup by default . 

-- 
Sérgio M. B.

[Antonio Trande]

2012/9/26 Sérgio Basto <sergio(a)serjux.com&gt;

>  On Qua, 2012-09-26 at 17:04 +0200, Antonio Trande wrote:
>  > As long as another issue: at every reboot I am compelled to restart
>  > 'fedora-loadmodules.service', otherwise the problem with vbox modules
>  > arises again.
>
>  No , fedora-loadmodules.service run at startup by default . 

I know.
I must restart it however.


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

**mail*: mailto:[e-mail] <sagitter(a)fedoraproject.org&gt;
*Homepage*: http://www.fedora-os.org
*Sip Address* : sip:sagitter AT ekiga.net
*Jabber <http://jabber.org/>* :sagitter AT jabber.org
*GPG Key: 19E6DF27*

[Sérgio Basto]

On Qua, 2012-09-26 at 19:23 +0200, Antonio Trande wrote: 
>  2012/9/26 Sérgio Basto <sergio(a)serjux.com&gt;
>          On Qua, 2012-09-26 at 17:04 +0200, Antonio Trande wrote:
>          > As long as another issue: at every reboot I am compelled to
>          restart
>          > 'fedora-loadmodules.service', otherwise the problem with
>          vbox modules
>          > arises again.
>          
>          
>          No , fedora-loadmodules.service run at startup by default . 
>  
>  
>  I know. 
>  I must restart it however. 
>   
No, you don't need to restart fedora-loadmodules.service. 
After boot without restart fedora-loadmodules.service
lsmod  | grep vbox
vboxnetadp             25670  0 
vboxnetflt             23442  0 
vboxdrv               300366  2 vboxnetadp,vboxnetflt

You only need restart when you update Virtualbox, to remove old modules
and load new ones .


Regards, 
-- 
Sérgio M. B.

[Antonio Trande]

2012/9/26 Sérgio Basto <sergio(a)serjux.com&gt;

>  On Qua, 2012-09-26 at 19:23 +0200, Antonio Trande wrote:
>  > 2012/9/26 Sérgio Basto <sergio(a)serjux.com&gt;
>  >         On Qua, 2012-09-26 at 17:04 +0200, Antonio Trande wrote:
>  >         > As long as another issue: at every reboot I am compelled to
>  >         restart
>  >         > 'fedora-loadmodules.service', otherwise the problem with
>  >         vbox modules
>  >         > arises again.
>  >
>  >
>  >         No , fedora-loadmodules.service run at startup by default .
>  >
>  >
>  > I know.
>  > I must restart it however.
>  >
>  No, you don't need to restart fedora-loadmodules.service.
>  After boot without restart fedora-loadmodules.service
>  lsmod  | grep vbox
>  vboxnetadp             25670  0
>  vboxnetflt             23442  0
>  vboxdrv               300366  2 vboxnetadp,vboxnetflt
>
>  You only need restart when you update Virtualbox, to remove old modules
>  and load new ones . 

I have just tried again (and Virtualbox is already updated). I confirm you
that I must restart 'fedora-loadmodules.service' otherwise vbox* modules
are not loaded .
I must understand the cause.



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

**mail*: mailto:[e-mail] <sagitter(a)fedoraproject.org&gt;
*Homepage*: http://www.fedora-os.org
*Sip Address* : sip:sagitter AT ekiga.net
*Jabber <http://jabber.org/>* :sagitter AT jabber.org
*GPG Key: 19E6DF27*