04.07.2012 20:38, KP Kirchdoerfer пишет: > Hi; > > Am 02.07.2012 20:35, schrieb david M brooke: >>> Also I plan to split initrd for separate files (one common for one arch >>> with binaries and some additional with kernel modules for each subarch >>> and even subarch variants like CD boot, USB boot and so on if this will >>> be useful)? possible I'll do this on this or next week. >> YES PLEASE! I have been thinking the same - multiple initrd per subarch >> so we can have a PXE initrd separate from a "basic" initrd and so on. >> Would let us have a small & simple initrd for some users and a large & >> generic initrd for others. > Sounds good! > > kp Today I've done this, I committed changes into git, and ran rebuilding from scratch. Test image on VM seems to work OK. Now there are 2 initramfs files - initrd.lrp with binaries and initmod.lrp with kernel modules that are required on boot before filesystem is mounted. And, due to automated generation of 2nd file for each subarch, it'll take not much time to add generation of multiple variants of boot module packs for each subarch when it'll be needed (for ex., for pxe implementation). Also that concept is compatible with building embedded images (kernel + initramfs that are glued by some tool into single file - like image file for uboot looader); it's needed just to link critical drivers into kernel statically (w/o initmod.lrp).
Also I think that there is other good target for cross-compiling - one of Ralink-based (or Atheros-based - they'll be even better) MIPS routers with USB. They'll require some kernel patches (may be taken from OpenWRT for ex.), and some userland stuff like switch configure tools; also they'll require image builder tool to glue kernel and initrd into boot image, that should initialize USB and load config and packages from USB stick. One pb - they have 32M RAM typically in cheap models (or even lesser), this is enough for basic install (NAT/DHCP/DNS/tunnels/tor/etc) but small for something greater than SOHO small box. But in any case, it should be interesting for experiments. And IMHO there'll be good to add non-required option 'arch' for packages described in 'sources.cfg' - to ensure that arch-dependent packages will not be built for other arch (they'll be useless or even they'll fail to built), and also add arch checking for apkg/initrd package loader (to warn that package is built for other arch). ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
