From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: PFire 2.21
Date: Wed, 27 Jun 2018 23:07:06 +0200 [thread overview]
Message-ID: <b19d92af-cf23-2508-4a5f-c9785dfc6891@link38.eu> (raw)
In-Reply-To: <012c01d40e59$94d51de0$be7f59a0$@ministc.com>
[-- Attachment #1: Type: text/plain, Size: 2462 bytes --]
Hello Paul,
this is the right place. Testing reports are always welcome. :-)
A crashing grub does not sound so good - especially if a firewall
machine is physical unreachable and no remote KVM console or similar
is available.
The 2.12 release was split up in two parts (one includes the new
kernel, firmware files are in the second) and as far as I am aware,
both should installed before rebooting.
> This may be my machine as I had used a live parted in the past to make a
> properly useful size var partition.
I did not get this.
@Core developers: Are we changing partition layout on existing
installations (enlarge /boot, drop /var)?
Yes, restoring too old backup files causes trouble. IPFire creates
a new backup before running a core upgrade, but if this fails, it
is hard to recover it. So better create a fresh backup before updating
to 2.21. Should we include this in the release notes?
Any observations after running on 2.21 (faster/slower/unstable/...)?
Thanks, and best regards,
Peter Müller
> Dear all,
>
>
>
> Hopefully I am in the right place to report on 2.21
>
> Just in case not - a quick summary
>
> Moved to testing from stable 120.
>
> Pakfire upgraded first to 121 - no reboot suggested.
>
> Pakfire upgraded next to 2.21 - This time reboot required.
>
>
>
> Reboot failed with a broken grub. I could not fix this with the manual grub
> commands to get ipfire running at all so could not rewrite grub from a
> running system.
>
> This may be my machine as I had used a live parted in the past to make a
> properly useful size var partition.
>
>
>
> Bit the bullet and downloaded nightly build of 2.21 and reinstalled a clean
> ipfire.
>
> So far so good.
>
>
>
> Only one comment about restoring previous settings from a backup.
>
> My backup was old and from a time when php was supported. After restoring
> the backup a surprise was in store the next time apache web interface was
> restarted. Apache failed as there is a reference in the conf files from
> backup to load php so extension.
>
> Commenting out the line fixes it of course. Just thought I would mention
> that restoring backups from a version prior to the latest may have issues as
> features start to get expired.
>
>
>
> By the way I really admire the stuff you do and a donation is en-route.
>
>
>
> Regards,
>
> Paul
>
>
>
>
>
>
>
>
>
>
--
"We don't care. We don't have to. We're the Phone Company."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2018-06-27 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <012c01d40e59$94d51de0$be7f59a0$@ministc.com>
2018-06-27 21:07 ` Peter Müller [this message]
2018-06-28 10:41 ` Michael Tremer
2018-06-28 20:51 ` Paul Titjen
2018-06-29 17:26 ` IPFire 2.21 test report Peter Müller
2018-06-29 20:55 ` Peter Müller
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=b19d92af-cf23-2508-4a5f-c9785dfc6891@link38.eu \
--to=peter.mueller@link38.eu \
--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