Hi,
I've recently changed l-m-c to take an hwpack, which is installed before the image is built. To keep that change simple I had to unpack the binary tarball into a tmp directory, install the hwpack, repack the tarball and then continue with the image generation. This extra unpacking/repacking of the binary tarball is obviously not ideal, so I'm now refactoring l-m-c to make it possible to avoid it when installing an hwpack.
The one thing I'm not sure about is whether I should
a) unpack the binary tarball to a tmp dir, install the hwpack (which may cause lots of data to be written) and then move that to the SD card or b) unpack the tarball straight into the sd card (as is done currently) and then install the hwpack
I'm leaning towards a) because of the poor write speed of SD cards, but if anybody knows of any reasons why I should go with b) now's the time to tell me. :)
Cheers,
On Thu, 23 Sep 2010 15:42:34 -0300, Guilherme Salgado salgado@canonical.com wrote:
Hi,
I've recently changed l-m-c to take an hwpack, which is installed before the image is built. To keep that change simple I had to unpack the binary tarball into a tmp directory, install the hwpack, repack the tarball and then continue with the image generation. This extra unpacking/repacking of the binary tarball is obviously not ideal, so I'm now refactoring l-m-c to make it possible to avoid it when installing an hwpack.
The one thing I'm not sure about is whether I should
a) unpack the binary tarball to a tmp dir, install the hwpack (which may cause lots of data to be written) and then move that to the SD card or b) unpack the tarball straight into the sd card (as is done currently) and then install the hwpack
I'm leaning towards a) because of the poor write speed of SD cards, but if anybody knows of any reasons why I should go with b) now's the time to tell me. :)
I realise it's a bit late now, but I agree with you, so I'm glad that's what you implemented :-)
James
On Thu, Sep 23, 2010 at 8:42 PM, Guilherme Salgado salgado@canonical.com wrote:
a) unpack the binary tarball to a tmp dir, install the hwpack (which may cause lots of data to be written) and then move that to the SD card or b) unpack the tarball straight into the sd card (as is done currently) and then install the hwpack
I'm leaning towards a) because of the poor write speed of SD cards, but if anybody knows of any reasons why I should go with b) now's the time to tell me. :)
Would the refactoring allow to try out whether a) or b) is better without guessing?
On Mon, 2010-09-27 at 09:44 +0200, Alexander Sack wrote:
On Thu, Sep 23, 2010 at 8:42 PM, Guilherme Salgado salgado@canonical.com wrote:
a) unpack the binary tarball to a tmp dir, install the hwpack (which may cause lots of data to be written) and then move that to the SD card or b) unpack the tarball straight into the sd card (as is done currently) and then install the hwpack
I'm leaning towards a) because of the poor write speed of SD cards, but if anybody knows of any reasons why I should go with b) now's the time to tell me. :)
Would the refactoring allow to try out whether a) or b) is better without guessing?
Not without some more work. And even if I did that, the results would be specific to my hardware (5400rpm disk and a couple different SD cards), so I don't think it'd be of much use.