From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: AW: Fwd: Re: Core-upgrade-2.21-121
Date: Mon, 11 Jun 2018 12:03:09 +0100
Message-ID: <ac9fdc197251db63a86ee2d4f776565646c14481.camel@ipfire.org>
In-Reply-To: =?utf-8?q?=3C1528711896083=2E6520907=2Eab3c400eb713b7d98e37cf2f?=
 =?utf-8?q?990a567fbb3c3f13=40spica=2Etelekom=2Ede=3E?=
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1481397291345708965=="
List-Id: <development.lists.ipfire.org>

--===============1481397291345708965==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Mon, 2018-06-11 at 12:11 +0200, fischerm42(a)t-online.de wrote:
> Hi,
>=20
> -----Original-Nachricht-----
> Betreff: Re: Fwd: Re: Core-upgrade-2.21-121
> Datum: 2018-06-11T10:50:17+0200
> Von: "Michael Tremer" <michael.tremer(a)ipfire.org>
> An: "Matthias Fischer" <matthias.fischer(a)ipfire.org>, "IPFire: Developmen=
t-
> List" <development(a)lists.ipfire.org>
>=20
> > Yes, good idea. Did you try to extract the update and check how large it =
is?
>=20
> If I remember correctly, extracted size was about 350MB ...
>=20
> But we're on F=C3=B6hr now and my 'Devel' is far, far away...
>=20
> 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
>=20
>=20
> > -Michael
>=20
> On Fri, 2018-06-08 at 12:55 +0200, Matthias Fischer wrote:
> > Hi,
> >=20
> > 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 hop=
ing
> > > > > > that this won't cause any troubles, too.
> > > > >=20
> > > > > 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.
> > > >=20
> > > > As far as I can see its the 'firmware'.
> > > > Just an idea: perhaps we should adjust "$ROOTSPACE" from 'update.sh'
> > > > accordingly?
> > >=20
> > > What would that be?
> >=20
> > I don't know how much space we will need for this update - I thought of
> > something like this:
> >=20
> > ...
> > if [ $ROOTSPACE -lt [HERE_SOME_BIGGER_VALUE_INSTEAD_OF_100000] ]; then
> > ...
> >=20
> > Jm2c!
> >=20
> > >=20
> > > >=20
> > > > ...
> > > > # Check diskspace on root
> > > > ROOTSPACE=3D`df / -Pk | sed "s| * | |g" | cut -d" " -f4 | tail -n 1`
> > > >=20
> > > > if [ $ROOTSPACE -lt 100000 ]; then
> > > > 	exit_with_error "ERROR cannot update because not enough free
> > > > space on
> > > > root." 2
> > > > 	exit 2
> > > > fi
> > > > ...
> >=20
> > Best,
> > Matthias
>=20
> =EF=BB=BF

--===============1481397291345708965==--