From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Fwd: Re: Core-upgrade-2.21-121
Date: Fri, 08 Jun 2018 11:01:11 +0100 [thread overview]
Message-ID: <9b10a7a96521f3259c52782d3d1f1680a2970c7f.camel@ipfire.org> (raw)
In-Reply-To: <30de0d30-2b08-5321-22f1-fa8ecba4f09c@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]
On Fri, 2018-06-08 at 11:49 +0200, Matthias Fischer wrote:
> (Forwarding to the 'list' - accidently clicked 'Reply' instead of 'Reply
> all')
>
> -------- Forwarded Message --------
> Subject: Re: Core-upgrade-2.21-121
> Date: Fri, 8 Jun 2018 10:32:34 +0200
> From: Matthias Fischer <matthias.fischer(a)ipfire.org>
> Organization: None
> To: Michael Tremer <michael.tremer(a)ipfire.org>
>
> Hi,
>
> On 07.06.2018 23:09, Michael Tremer wrote:
> > Hey,
> >
> > On Thu, 2018-06-07 at 22:02 +0200, Matthias Fischer wrote:
> > > Hi,
> > >
> > > First ("just for the records"):
> > > I'm taking some days off. Until 24.06.2018 you can find me here (from
> > > time to time): https://www.utersum.de/?page_id=89 ;-)
> >
> > Have a nice holiday.
>
> Thanks! - I hope we will.
>
> >> Second:
> > > I made a clean build from current 'next' today and noticed that
> > > 'ROOTFILES' starts with a blank line. I don't know if this could cause
> > > us any troubles!?
> >
> > It shouldn't have been empty. But as far as I know the builds are fine.
>
> Confirmed. I built current 'next' this night. No errors.
>
> > > 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?
>
> ...
> # 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
> ...
>
> >
> > > Fourth:
> > > "./make.sh gettoolchain" gives me:
> > >
> > > ...
> > > Jun 7 19:57:57: Load toolchain image for i586
> > > Jun 7 19:57:57: error downloading ipfire-2.21-toolchain-20180606-i586
> > > toolchain for i586 machine
> > > ...
> >
> > I will upload that one shortly.
>
> Thanks. :-)
Uploaded.
> Building the complete toolchain from scratch took 12:30h on first run.
> New record...
>
> Best,
> Matthias
next prev parent reply other threads:[~2018-06-08 10:01 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 [this message]
2018-06-08 10:55 ` Matthias Fischer
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=9b10a7a96521f3259c52782d3d1f1680a2970c7f.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