From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Fwd: Re: Core-upgrade-2.21-121
Date: Mon, 11 Jun 2018 09:50:02 +0100
Message-ID: <2b2517237059188da4ab732997916732b92e94d3.camel@ipfire.org>
In-Reply-To: <46e8c892-4219-025c-137f-2ce8b0c9913c@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1534869717128257398=="
List-Id: <development.lists.ipfire.org>

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

Yes, good idea. Did you try to extract the update and check how large it is?

-Michael

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 hoping
> > > > > that this won't cause any troubles, too.
> > > >=20
> > > > Yes, it is huuuuuge. And that *will* cause problems. I have no idea w=
hy
> > > > though. The kernel and firmware themselves shouldn't be that large and
> > > > there is barely anything else in it. Unless I have added something th=
at>
> > > > 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

--===============1534869717128257398==--