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 [thread overview]
Message-ID: <ac9fdc197251db63a86ee2d4f776565646c14481.camel@ipfire.org> (raw)
In-Reply-To: =?utf-8?q?=3C1528711896083=2E6520907=2Eab3c400eb713b7d98e37cf2f?= =?utf-8?q?990a567fbb3c3f13=40spica=2Etelekom=2Ede=3E?=
[-- Attachment #1: Type: text/plain, Size: 2301 bytes --]
On Mon, 2018-06-11 at 12:11 +0200, fischerm42(a)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(a)ipfire.org>
> An: "Matthias Fischer" <matthias.fischer(a)ipfire.org>, "IPFire: Development-
> List" <development(a)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
>
>
reply other threads:[~2018-06-11 11:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac9fdc197251db63a86ee2d4f776565646c14481.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox