Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #257547 > unrolled thread

Re: Looking for inspiration/advice/best practices on system upgrade

Started byDan Ritter <dsr@randomstring.org>
First post2023-04-24 20:10 +0200
Last post2023-04-25 09:20 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Looking for inspiration/advice/best practices on system upgrade Dan Ritter <dsr@randomstring.org> - 2023-04-24 20:10 +0200
    Re: Looking for inspiration/advice/best practices on system upgrade "Andrew M.A. Cater" <amacater@einval.com> - 2023-04-25 09:20 +0200

#257547 — Re: Looking for inspiration/advice/best practices on system upgrade

FromDan Ritter <dsr@randomstring.org>
Date2023-04-24 20:10 +0200
SubjectRe: Looking for inspiration/advice/best practices on system upgrade
Message-ID<Go8Nr-4eYT-7@gated-at.bofh.it>
DdB wrote: 
> while still on debian buster (old-old-stable soon), i am approaching the
> point, where i will be ready to upgrade. I do have backup(s) from
> different points in time, and can carry out restore to a VM, that is
> almost identical to my main system, that i can use as a playground for
> playing through the whole process.
> 
> But i could not yet decide upon the right way to progress, 3
> alternatives coming to mind:
> 1. Upgrade from current configuration using upgrade path tools (apt) and
> plan only one step (going to bullseye) at a time, eventually having to
> upgrade a second time later.

Upgrade buster to bullseye, reboot, upgrade to bookworm.

Solve the final set of problems, not all the intermediates which
may have been fixed.


> >From my past experiences, i recall one problem, that i am still
> suffering from: the file group and user owners, that reside on a
> different disk set (on a ZFS pool, to be more precise). In order to
> alleviate the problem, i did at one point fetch an older /etc/group and
> passwd file from a backup and created a mess. I'd love to straigthen
> this out now.

If you have owner/group problems now, solve them before any of the
upgrades.

-dsr-

[toc] | [next] | [standalone]


#257563

From"Andrew M.A. Cater" <amacater@einval.com>
Date2023-04-25 09:20 +0200
Message-ID<Gol7Y-4mYf-1@gated-at.bofh.it>
In reply to#257547
On Tue, Apr 25, 2023 at 12:16:54AM +0200, DdB wrote:
> Thank you for providing your take on this.
> 
> Am 24.04.2023 um 19:46 schrieb Dan Ritter:
> > Upgrade buster to bullseye, reboot, upgrade to bookworm.
> > 

Read the release notes for bullseye.

Change /etc/apt/sources.list to suit.

Upgrade buster to bullseye - reboot.

Check with apt as to anything that you should autoremove.

Read the release notes for bookworm

Change /etc/apt/sources.list to suit

Upgrade bullseye to bookworm

Reboot and check for autoremovals

[There's two sets of changes to /etc/apt/sources.list necessary to 
accommodate changes to bullseye security and bookworm non-free-firmware
but you won't know that unless you read the release notes]

> > Solve the final set of problems, not all the intermediates which
> > may have been fixed.
> interesting consideration there. :-)
> > (...) If you have owner/group problems now, solve them before any of the
> > upgrades.
> That is, what i was thinking too. Unfortunately, i am afraid of this
> step. That is why i had been builing a kind of playground first.
> > 

That depends on owner and group problem extent. If you're not sure,
then the wise thing is to spin up a virtual machine or some such and
check what the groups are on the new system *first* then match your
old modified system to the new model? It's probably not worth trying
to upgrade and still being unsure.

Andy

> > -dsr-
> > 
> > 
> 

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web