From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 122 updates
Date: Fri, 03 Aug 2018 09:14:14 +0100 [thread overview]
Message-ID: <ba3c2ce032538ede86c39d279cba7d1c3b88662b.camel@ipfire.org> (raw)
In-Reply-To: <578BF898-3F94-4ED9-BD24-983245F07D5B@rymes.com>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Thu, 2018-08-02 at 23:41 -0400, Tom Rymes wrote:
>
>
> On Aug 2, 2018, at 2:58 PM, Kienker, Fred <fkienker(a)at4b.com> wrote:
>
> <snip>
>
> > Michael’s posting on the website about maybe it is time for a “clean” reinstall is very much to the point. But this is very hard to do with these older systems. I’m not sure it is possible to install 122 then restore a backup from 120, but I may well be wrong.
>
> Fred,
>
> I’d advise against installing an older backup to a newer system if you can avoid it. Why not install 120 as a clean install, restore the backup, and then upgrade. Will the 120 clean install not have a larger /boot?
Actually, this is a good point.
Configuration wise it doesn't make a difference but certificates that
have been generated with MD5 should be renewed and that is probably
most easy to do with a new installation from scratch.
Best,
-Michael
>
> Tom
next parent reply other threads:[~2018-08-03 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <578BF898-3F94-4ED9-BD24-983245F07D5B@rymes.com>
2018-08-03 8:14 ` Michael Tremer [this message]
2018-08-03 17:17 ` Kienker, Fred
[not found] <H000006e00429396.1533236266.mail.at4b.net@MHS>
2018-08-02 21:46 ` 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=ba3c2ce032538ede86c39d279cba7d1c3b88662b.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