From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: Fwd: Re: Core-upgrade-2.21-121 Date: Fri, 08 Jun 2018 12:55:27 +0200 Message-ID: <46e8c892-4219-025c-137f-2ce8b0c9913c@ipfire.org> In-Reply-To: <9b10a7a96521f3259c52782d3d1f1680a2970c7f.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4211872955120845273==" List-Id: --===============4211872955120845273== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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. >> >=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? I don't know how much space we will need for this update - I thought of somet= hing like this: ... if [ $ROOTSPACE -lt [HERE_SOME_BIGGER_VALUE_INSTEAD_OF_100000] ]; then ... Jm2c! >=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 >> ... Best, Matthias --===============4211872955120845273==--