public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Fwd: Re: Core-upgrade-2.21-121
Date: Fri, 08 Jun 2018 12:55:27 +0200	[thread overview]
Message-ID: <46e8c892-4219-025c-137f-2ce8b0c9913c@ipfire.org> (raw)
In-Reply-To: <9b10a7a96521f3259c52782d3d1f1680a2970c7f.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]

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-08 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51be2faa-4bf0-beb3-7b8e-647e9ad6cc4a@ipfire.org>
2018-06-08  9:49 ` Matthias Fischer
2018-06-08 10:01   ` Michael Tremer
2018-06-08 10:55     ` Matthias Fischer [this message]
2018-06-11  8:50       ` Michael Tremer

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=46e8c892-4219-025c-137f-2ce8b0c9913c@ipfire.org \
    --to=matthias.fischer@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