Hi Andrew Am 30.11.2015 um 14:16 schrieb Andrew:
30.11.2015 13:41, Erich Titl пишет:Am 30.11.2015 um 10:44 schrieb Andrew:30.11.2015 11:11, Erich Titl пишет:Hi AndrewAm 22.09.2015 um 20:02 schrieb Andrew:Hi. Another important target IMHO - merge all important stuff (root.lrp/etc.lrp/config.lrp/other packages that are 100% present in LEAF box) into initrd.Don't do that, initrd is overloaded as it is now,Why you think that using separate packages for that files are better than placing them into initrd? Or you know LEAF usecases when, for ex., root.lrp with all it's dependencies wasn't loaded?
That is fine, if you load it from a single .lrp, initrd is IMHO the wrong place.
I am just afraid of overloading initrd, I need to package it with initmod, because grub does not support multple initrd files. ..I think that 850kb instead of 550kb isn't a big difference.cheers ETYes, I know that. And this is one of reasons why I want to make solid initrd that will contain all basic stuff that is currently placed in root.lrp
What do you consider moving from root.lrp to initd? Why not make a big root.lrp which contains everything for a basic system and leave initrd tiny?
and it's deps. Because on embedded platforms with small amount
of RAM and available MTD device (that is always connected to SoC) it'll be preferrable to use squashfs initrd that is always mounted (+ mount overlayfs on top of it) rather than copy all stuff from it to valuable RAM.
Yes, but unless you can access the medium containing the squashfs that won't work.
If we can place initrd on squashfs this is certainly better. The question is here, can we low_level load the squashfs initrd, so we can load the storage and network drivers from there? cheers ETFor embedded platforms, kernel should contain all boot-required modules compiled in.
Totally agreed, this may mean we have a number of kernels for various platforms.
And SoC network drivers also may be compiled in kernel, not
as modules to save some space. Rest of modules (like additional USB network adapters, iptables modules and so on) will be compiled as modules.
I suggest to build a new modules.sqfs with the kernel directory level removed and permanently mounted to /lib/modules/kernel. This way we can avoid to have to copy the modules to /lib/modules completely. We just need to run depmod once the squashfs is mounted, then module loading can be done from the squashfs directly and if user specific modules are needed they can either be on an OverlayFS or be written to a subdirectory of /lib/modules.
This is an easy change which will make init more simple than it is now.We just need to compile the kernel with the necessary storage drivers compiled in, after mounting the new modules FS to /usr/lib/kernel, normal module loading can be done. This way there is no need for initmod anymore.
We also should let shorewall load all the modules it requires, this will remove some of the complexity in module management.
cheers ET
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
