Hi KP
Just to make it more clear
Am 07.02.2016 um 14:09 schrieb kp kirchdoerfer:
> Hi;
>
..
>
> I don't think we can't make this a valuable decision.
>
> Just adding more code and more options to load modules will increase
> maintenance work and will be confusing in the future.
>
> If we
And they should be accessible at least for some time after daemon start
(for ex., 5-10 seconds) - daemon may not always load modules at start,
it may load modules on demand. And I expect that it shouldn't unload
modules.
Also, now we are freeing unused modules on device plug out. And for new
Am Montag, 8. Februar 2016, 13:20:07 schrieb Erich Titl:
> Hi KP
>
> Just to make it more clear
>
> Am 07.02.2016 um 14:09 schrieb kp kirchdoerfer:
> > Hi;
>
> ..
>
> > I don't think we can't make this a valuable decision.
> >
> > Just adding more code and more options to load modules will
Modules can be loaded by daemon (for ex. accel-ppp loads needed modules).
08.02.2016 19:32, Erich Titl пишет:
> Hi KP
>
> Am 08.02.2016 um 18:26 schrieb kp kirchdoerfer:
> ...
>> You may analyze ppp/pppoe instead, where /var/lib/lrpkg/*.depmod provides the
>> necesssry modules and therefor
Am 08.02.2016 um 18:54 schrieb Andrew:
> Modules can be loaded by daemon (for ex. accel-ppp loads needed modules).
Right, so at daemon start the modules need to be accessible
ET
--
Site24x7 APM Insight: Get Deep
Am Montag, 8. Februar 2016, 18:32:07 schrieb Erich Titl:
> Hi KP
>
> Am 08.02.2016 um 18:26 schrieb kp kirchdoerfer:
> ...
>
> > You may analyze ppp/pppoe instead, where /var/lib/lrpkg/*.depmod provides
> > the necesssry modules and therefor requires no user intervention to load
> > the
Hi;
Am Mittwoch, 3. Februar 2016, 20:03:19 schrieb Andrew:
> Hi.
>
> 03.02.2016 17:44, kp kirchdoerfer пишет:
> > Hi all;
> >
> > I'll try to summarize the current and proposed status of loading modules
> > as
> > this raises questions.
> >
> > Pls correct me whereelse needed if I missed
Hi KP
Am 07.02.2016 um 14:09 schrieb kp kirchdoerfer:
> Hi;
>
..
>
> I don't think we can't make this a valuable decision.
>
> Just adding more code and more options to load modules will increase
> maintenance work and will be confusing in the future.
>
> If we do not copy modules during
04.02.2016 08:49, Erich Titl пишет:
> Hi Andrew
>
> Am 03.02.2016 um 22:56 schrieb Andrew:
>> 03.02.2016 22:47, Erich Titl пишет:
>>> Hi Andrew
>>>
>>> Am 03.02.2016 um 19:03 schrieb Andrew:
Hi.
>>> ...>>
> Erich made the proposal to change the init scripts of such packages to
>
03.02.2016 22:47, Erich Titl пишет:
> Hi Andrew
>
> Am 03.02.2016 um 19:03 schrieb Andrew:
>> Hi.
>>
> ...>>
>>> Erich made the proposal to change the init scripts of such packages to mount
>>> modules.sqfs and load whatever required.
>> Good solution.
>>
>> But IMHO we should leave possibility to
Hi Andrew
Am 03.02.2016 um 19:03 schrieb Andrew:
> Hi.
>
...>>
>> Erich made the proposal to change the init scripts of such packages to mount
>> modules.sqfs and load whatever required.
> Good solution.
>
> But IMHO we should leave possibility to use old behavior on systems.
What behaviour
Hi all;
I'll try to summarize the current and proposed status of loading modules as
this raises questions.
Pls correct me whereelse needed if I missed something or got it wrong.
This summary is based on 5.2.x, master and new-initrd-6x branch
A) The current status
At the time we do have
Hi Andrew
Am 03.02.2016 um 22:56 schrieb Andrew:
> 03.02.2016 22:47, Erich Titl пишет:
>> Hi Andrew
>>
>> Am 03.02.2016 um 19:03 schrieb Andrew:
>>> Hi.
>>>
>> ...>>
Erich made the proposal to change the init scripts of such packages to
mount
modules.sqfs and load whatever
Hi.
03.02.2016 17:44, kp kirchdoerfer пишет:
> Hi all;
>
> I'll try to summarize the current and proposed status of loading modules as
> this raises questions.
>
> Pls correct me whereelse needed if I missed something or got it wrong.
>
> This summary is based on 5.2.x, master and new-initrd-6x
14 matches
Mail list logo
