* Fwd: Re: Core-upgrade-2.21-121
[not found] <51be2faa-4bf0-beb3-7b8e-647e9ad6cc4a@ipfire.org>
@ 2018-06-08 9:49 ` Matthias Fischer
2018-06-08 10:01 ` Michael Tremer
0 siblings, 1 reply; 4+ messages in thread
From: Matthias Fischer @ 2018-06-08 9:49 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 2147 bytes --]
(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?
...
# 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. :-)
Building the complete toolchain from scratch took 12:30h on first run.
New record...
Best,
Matthias
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Fwd: Re: Core-upgrade-2.21-121
2018-06-08 9:49 ` Fwd: Re: Core-upgrade-2.21-121 Matthias Fischer
@ 2018-06-08 10:01 ` Michael Tremer
2018-06-08 10:55 ` Matthias Fischer
0 siblings, 1 reply; 4+ messages in thread
From: Michael Tremer @ 2018-06-08 10:01 UTC (permalink / raw)
To: development
[-- 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Fwd: Re: Core-upgrade-2.21-121
2018-06-08 10:01 ` Michael Tremer
@ 2018-06-08 10:55 ` Matthias Fischer
2018-06-11 8:50 ` Michael Tremer
0 siblings, 1 reply; 4+ messages in thread
From: Matthias Fischer @ 2018-06-08 10:55 UTC (permalink / raw)
To: development
[-- 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Fwd: Re: Core-upgrade-2.21-121
2018-06-08 10:55 ` Matthias Fischer
@ 2018-06-11 8:50 ` Michael Tremer
0 siblings, 0 replies; 4+ messages in thread
From: Michael Tremer @ 2018-06-11 8:50 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
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,
>
> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-06-11 8:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <51be2faa-4bf0-beb3-7b8e-647e9ad6cc4a@ipfire.org>
2018-06-08 9:49 ` Fwd: Re: Core-upgrade-2.21-121 Matthias Fischer
2018-06-08 10:01 ` Michael Tremer
2018-06-08 10:55 ` Matthias Fischer
2018-06-11 8:50 ` Michael Tremer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox