From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 122
Date: Mon, 23 Jul 2018 23:15:32 +0100 [thread overview]
Message-ID: <463d69aefdae325b8f0eb41c9a97b95027965c37.camel@ipfire.org> (raw)
In-Reply-To: <H000006e00422959.1532367572.mail.at4b.net@MHS>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
Hello Fred,
thank you for getting in touch.
On Mon, 2018-07-23 at 13:39 -0400, Kienker, Fred wrote:
> Core 122 has been in the testing phase for almost a month now. Is there
> anything outsiders can do to help accelerate the release?
Yes, provide us feedback just like you are doing now.
Even if there are no (new) bugs, we would like to know. So far, it has been
really quiet, but I guess that has a lot to do with the hot weather, a world cup
and now people being on holiday.
So, we have not been feeling very confident to roll out the update, but we made
the decision that it will be coming next week.
> Things we have tried on Core 122 with success:
> Updating copies of existing systems including those with VPN’s
> Installing from scratch on bare metal machines
> Transferring settings backups from existing machines to bare metal setups
>
> No surprises with any of these. Machines were left running with the various
> test setups for up to a week with no issues. All showed significant
> performance boosts with the new kernel.
Cool. Did you benchmark that? How has performance improved and on what hardware
are you running IPFire?
> One thing we have noticed – to get the maximum benefit does require a bare
> metal install and a restore from backup.
> Best regards,
> Fred Kienker
>
Best,
-Michael
parent reply other threads:[~2018-07-23 22:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <H000006e00422959.1532367572.mail.at4b.net@MHS>]
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=463d69aefdae325b8f0eb41c9a97b95027965c37.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