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 boot, we have to make shure that for example 
> shorewalls init code calls the helper script  mount_module and load modules 
> from modules.sqfs. This is unneeded if we load the modules during boot.
> If we now want to support both ways to load modules, we will have all the 
> modules right in place, but during shorewall start, it will still mount 
> modules.sqfs and and load modules... and this is true for other packages as 
> well (openvpn, ppp/pppoe and so on).

Just to make it clear for anyone.

Where does openvpn load the tun module?
Where does ppp[oe] load the respective module(s)?

I believe they still rely on /etc/modules.

> 
> Another unsolved problem will be what happens to packages that do not have an 
> init file, but needs modules - like arptable. 

AFAIK arptable like iptable is not an application by itself, just a
collection of utilities. So here the same aplies as in iptables.

Currently we use the <DependsOn>
> section in buildtool.cfg, and this makes shure we do load the modules needed 
> for arptables, with Erichs approach this does not work any more.

>   
> So I see no way to keep both approaches side-by-side.
> 
> Is there a way we can avoid copying modules into /lib/modules, but still 
> using 
> the <DependsOn> mimic?

Sure, just like it is now. With the exception of shorewall no
application I know of can rely solely on DependsOn, because the current
logic _does_not_load_the_modules.

...
> 
> 
> Unfortunately the newinitrd branch mixed also
> 1) get rid of initmod by built the modules needed to noot into the kernel
> 2) change the way we load modules

No, we still use modprobe :-)

> 
> I suggest we seperate those two changes from each other. Therefor we can have 
> the benefit of moving hardware from initmod into kernel and independent from 
> the decision how to work with remaing modules.

We are running in circles here. The new init either works or not. If it
has deficiencies, please show them and then we can try to fix them. If
we can't fix them, then I just failed. Please come up with a use case
for the necessity of the DependsOn logic.

cheers

ET

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to