On Mon, 2018-06-11 at 12:11 +0200, fischerm42@t-online.de wrote:
Hi,
-----Original-Nachricht----- Betreff: Re: Fwd: Re: Core-upgrade-2.21-121 Datum: 2018-06-11T10:50:17+0200 Von: "Michael Tremer" michael.tremer@ipfire.org An: "Matthias Fischer" matthias.fischer@ipfire.org, "IPFire: Development- List" development@lists.ipfire.org
Yes, good idea. Did you try to extract the update and check how large it is?
If I remember correctly, extracted size was about 350MB ...
But we're on Föhr now and my 'Devel' is far, far away...
Until ~27.6.18 I have no chance to look at his. Family says I'm on vacation now... ;-)
Absolutely. I forgot.
I just checked and the extracted image is ~477MB.
@Arne: is this an acceptable size for the update?
Best, Matthias
-Michael
On Fri, 2018-06-08 at 12:55 +0200, Matthias Fischer wrote:
Hi,
On 08.06.2018 12:01, Michael Tremer wrote:
...
...
Third: It's BIG. 'core-upgrade-2.21-121.ipfire' has now ~103 MB. I'm hoping that this won't cause any troubles, too.
Yes, it is huuuuuge. And that *will* cause problems. I have no idea why though. The kernel and firmware themselves shouldn't be that large and there is barely anything else in it. Unless I have added something that> shouldn't be in there.
As far as I can see its the 'firmware'. Just an idea: perhaps we should adjust "$ROOTSPACE" from 'update.sh' accordingly?
What would that be?
I don't know how much space we will need for this update - I thought of something like this:
... if [ $ROOTSPACE -lt [HERE_SOME_BIGGER_VALUE_INSTEAD_OF_100000] ]; then ...
Jm2c!
... # Check diskspace on root ROOTSPACE=`df / -Pk | sed "s| * | |g" | cut -d" " -f4 | tail -n 1`
if [ $ROOTSPACE -lt 100000 ]; then exit_with_error "ERROR cannot update because not enough free space on root." 2 exit 2 fi ...
Best, Matthias