Re: Removing duplication in /boot - affects kernel development

2012-09-10 Thread Daniel Drake
On Wed, Sep 5, 2012 at 3:46 PM, Daniel Drake d...@laptop.org wrote: Hi, I'd like to renew this thread, since we didn't get a great amount of feedback last time. Also, one of the issues mentioned (but a little downplayed) is the significance of removing the firmware updating code from

Re: Removing duplication in /boot - affects kernel development

2012-09-05 Thread Daniel Drake
Hi, I'd like to renew this thread, since we didn't get a great amount of feedback last time. Also, one of the issues mentioned (but a little downplayed) is the significance of removing the firmware updating code from olpc.fth. Having stale code duplicated from the firmware in olpc.fth bit us

Re: Removing duplication in /boot - affects kernel development

2012-09-05 Thread Mikus Grinbergs
On 09/05/2012 04:46 PM, Daniel Drake wrote: Installing a new kernel RPM to test a new kernel/initramfs before it gets shipped in a build (with rpm -Uvh kernel-foo.rpm). This will continue to install the new kernel as /boot/vmlinuz and the initramfs as/boot/{actrd,initrd}.img. The olpc.fth

Re: Removing duplication in /boot - affects kernel development

2012-03-07 Thread Daniel Drake
On Mon, Mar 5, 2012 at 12:32 PM, Paul Fox p...@laptop.org wrote: and if i don't, the machine will be unbootable, i guess? Yes. is there a way to fall back on the signed zip version of the initrd if there's no plain version? We did try to do this, back in the thread OFW unsecure

Removing duplication in /boot - affects kernel development

2012-03-05 Thread Daniel Drake
Hi, At the moment, /boot in our images looks like this: Development builds - kernel is found at /boot/vmlinuz, initramfs at /boot/initrd.img and /boot/actrd.img. Unsecure boot is always used, meaning that olpc.fth is executed, which loads the kernel and initrd.img from those locations. Release

Re: Removing duplication in /boot - affects kernel development

2012-03-05 Thread Paul Fox
daniel wrote: Hi, At the moment, /boot in our images looks like this: Development builds - kernel is found at /boot/vmlinuz, initramfs at /boot/initrd.img and /boot/actrd.img. Unsecure boot is always used, meaning that olpc.fth is executed, which loads the kernel and initrd.img

Re: Removing duplication in /boot - affects kernel development

2012-03-05 Thread Mikus Grinbergs
Our builds will always ship the kernel and initramfs *only* in their actos/runos/actrd/runrd zip forms. I'm an user who always runs 'yum upgrade kernel' whenever a newer version of the kernel appears in the olpc rpm repositories. I know how to copy the output of 'yum upgrade kernel' to where

Re: Removing duplication in /boot - affects kernel development

2012-03-05 Thread Peter Robinson
On Mon, Mar 5, 2012 at 7:48 PM, Mikus Grinbergs mi...@bga.com wrote: Our builds will always ship the kernel and initramfs *only* in their actos/runos/actrd/runrd zip forms. I'm an user who always runs 'yum upgrade kernel' whenever a newer version of the kernel appears in the olpc rpm