Martin Gregorie  writes:
> On Mon, 26 Aug 2019 20:37:53 +0100, druck wrote:
>> On 26/08/2019 17:25, Martin Gregorie wrote:
>>> I thought my recent in-situ upgrade (Stretch -> Buster) went
>>> surprisingly well seeing that it was the first Raspbian attempt at
>>> in-situ upgrades. By and large it 'just worked' even though it took
>>> its time (but then so do Fedora in-situ upgrades and they've been
>>> doing them for the last 10 distro versions). But, you MUST have
>>> Stretch fully updated before attempting it
>>
>> Over the years I've in-situ upgraded from squeeze > wheezy > jessie >
>> stretch > buster, plus upgraded the Pi its running on from B (256M) > B
>> (512MB) > 2B > 3B > 3B+ > 4B. Just make sure its up to date on the
>> current version and fully backed up before you begin.

Ditto. On the x86 side I have had a system which has been in-situ
upgraded repeatedly since 1995 and is still working fine. Most recently
was an i386->amd64 crossgrade, which I don’t recommend in general but I
really didn’t want to capture and reproduce a quarter century of local
configuration (or lose the mtime on /etc/hostname l-)

> Yep, agreed, but the Stretch->Buster upgrade was rather different to
> simply editing a few files and running the standard update again like we
> did previously. Indeed, it has noticeable similarities to the Fedora
> version upgrade.

I don’t recall it being particularly involved...

--
https://www.greenend.org.uk/rjk/

--- SoupGate-Win32 v1.05