On Sun, Feb 04, 2007 at 09:58:30PM +0100, Martin Michlmayr wrote:
> * Rod Whitby <firstname.lastname@example.org> [2007-02-05 07:21]:
> > Assuming this build of apex puts the environment in the same block as
> > apex itself, are the debian scripts padding that block with FFs or
> > zeros? If the latter, that would explain it.
> Ah, thanks. I remember this discussion now. Yes, it's padding with
> Is the APEX environment supposed to be in the same mtd block as APEX
> itself? Wasn't the original idea to hide it in the FIS directory?
> Once I know these details, I can try to integrate this new version
> properly (but that's after etch anyway).
We moved it out of the FIS directory so that it didn't interfere with
kernels that couldn't handle anything in the FIS partition except for
> Doesn't mean having the APEX environment in the APEX block mean that
> we overwrite user changes with each upgrade of APEX (at least if we
> simply wrote the new APEX binary to flash and padded it; I guess we
> could use more trickery and use apex-env to read the environment, then
> write APEX to flash and then set the environment again).
The same thing happens with the FIS block, IIRC. Upgrades rewrite the
partition table, don't they?
> Sorry, I'm aware that you and Marc had quite a bit of discussion about
> this, but I didn't follow the discussion at that time... I suppose
> we in Debian could just wait and then copy whatever nslu2-linux.org
> does. ;-)