Re: [leaf-devel] BuC 5.x - Raspberry Pi Proof of Concept is Working
On 07/06/2012 03:20 AM, Andrew wrote: 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). Free online course on building a simple Raspberry Pi OS from the University of Cambridge http://www.raspberrypi.org/archives/1913 -- Mike Noyes mike at noyes.name https://plus.google.com/u/0/113364780158082152468 -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- 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
Re: [leaf-devel] BuC 5.x - Raspberry Pi Proof of Concept is Working
On 09/05/2012 09:34 AM, Mike Noyes wrote: On 07/06/2012 03:20 AM, Andrew wrote: 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). Free online course on building a simple Raspberry Pi OS from the University of Cambridge http://www.raspberrypi.org/archives/1913 Upcoming board revision http://www.raspberrypi.org/archives/1929 -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- 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
Re: [leaf-devel] BuC 5.x - Raspberry Pi Proof of Concept is Working
Hi; Am 02.07.2012 20:35, schrieb david M brooke: On Mon, 2012-07-02 at 21:27 +0300, Andrew wrote: 02.07.2012 21:01, KP Kirchdoerfer пишет: Am 01.07.2012 23:43, schrieb david M brooke: Hi all, My Raspberry Pi Model B, on order since April, arrived yesterday. After a few hours of work I have it running BuC 5.x very nicely. Only a Proof of Concept at this stage, but it shows that it can be done. Screen, keyboard and network are all working OK and LRP package loading and saving is the same as for any other platform. Hi David; great news! I'll do a rc1 for 4.3 this week and if no showstoppers show up the final a week later. There are somewhere missed dependencies for package auto-loading mechanism in 5.x that comes from 4.3 (for ex., ppp) For example I have just spotted that webconf now depends on (m)awk. I have to confess, I do not understand. Are there still pb's with dependencies in 4.3? Or in 5.x? Either way pls commit a fix or let me know me know, what package is missing which dependency before I have to guess :) Then we can move next into master - and have a first 5.0 alpha based on your commits, soon after. good work and congrats kp Yes, and split 4.x into new git branch - for legacy fixes and so on. Yes! I think creating a new branch based on 4.3 will be the way to do it. 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 -- 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
Re: [leaf-devel] BuC 5.x - Raspberry Pi Proof of Concept is Working
Am 01.07.2012 23:43, schrieb david M brooke: Hi all, My Raspberry Pi Model B, on order since April, arrived yesterday. After a few hours of work I have it running BuC 5.x very nicely. Only a Proof of Concept at this stage, but it shows that it can be done. Screen, keyboard and network are all working OK and LRP package loading and saving is the same as for any other platform. Hi David; great news! I'll do a rc1 for 4.3 this week and if no showstoppers show up the final a week later. Then we can move next into master - and have a first 5.0 alpha based on your commits, soon after. good work and congrats kp -- 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
Re: [leaf-devel] BuC 5.x - Raspberry Pi Proof of Concept is Working
02.07.2012 21:01, KP Kirchdoerfer пишет: Am 01.07.2012 23:43, schrieb david M brooke: Hi all, My Raspberry Pi Model B, on order since April, arrived yesterday. After a few hours of work I have it running BuC 5.x very nicely. Only a Proof of Concept at this stage, but it shows that it can be done. Screen, keyboard and network are all working OK and LRP package loading and saving is the same as for any other platform. Hi David; great news! I'll do a rc1 for 4.3 this week and if no showstoppers show up the final a week later. There are somewhere missed dependencies for package auto-loading mechanism in 5.x that comes from 4.3 (for ex., ppp) Then we can move next into master - and have a first 5.0 alpha based on your commits, soon after. good work and congrats kp Yes, and split 4.x into new git branch - for legacy fixes and so on. 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. -- 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
Re: [leaf-devel] BuC 5.x - Raspberry Pi Proof of Concept is Working
On Mon, 2012-07-02 at 21:27 +0300, Andrew wrote: 02.07.2012 21:01, KP Kirchdoerfer пишет: Am 01.07.2012 23:43, schrieb david M brooke: Hi all, My Raspberry Pi Model B, on order since April, arrived yesterday. After a few hours of work I have it running BuC 5.x very nicely. Only a Proof of Concept at this stage, but it shows that it can be done. Screen, keyboard and network are all working OK and LRP package loading and saving is the same as for any other platform. Hi David; great news! I'll do a rc1 for 4.3 this week and if no showstoppers show up the final a week later. There are somewhere missed dependencies for package auto-loading mechanism in 5.x that comes from 4.3 (for ex., ppp) For example I have just spotted that webconf now depends on (m)awk. Then we can move next into master - and have a first 5.0 alpha based on your commits, soon after. good work and congrats kp Yes, and split 4.x into new git branch - for legacy fixes and so on. 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. david -- 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
