Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #257540 > unrolled thread
| Started by | Michel Verdier <mv524@free.fr> |
|---|---|
| First post | 2023-04-24 19:10 +0200 |
| Last post | 2023-04-24 23:10 +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.
Re: Looking for inspiration/advice/best practices on system upgrade Michel Verdier <mv524@free.fr> - 2023-04-24 19:10 +0200
Re: Looking for inspiration/advice/best practices on system upgrade Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-04-24 23:10 +0200
| From | Michel Verdier <mv524@free.fr> |
|---|---|
| Date | 2023-04-24 19:10 +0200 |
| Subject | Re: Looking for inspiration/advice/best practices on system upgrade |
| Message-ID | <Go7Rn-4eq8-1@gated-at.bofh.it> |
Le 24 avril 2023 DdB a écrit : > 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. Usually this is the safest way. But why don't you upgrade sooner to bullseye ? Do you have some problematic packages ? > 2. Install a fresh bullseye and try to manually make it as similar as > can be to my current workhorse The more you customized your system the harder it will be > 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 need to you should only change manually your userid/groupid and don't change system ids. Replacing entire passwd is usually a bad idea. Also you should check your user/group are conforming to the minumum defined in /etc/login.defs
[toc] | [next] | [standalone]
| From | Timothy M Butterworth <timothy.m.butterworth@gmail.com> |
|---|---|
| Date | 2023-04-24 23:10 +0200 |
| Message-ID | <GobBD-4gFx-5@gated-at.bofh.it> |
| In reply to | #257540 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Apr 24, 2023 at 1:06 PM Michel Verdier <mv524@free.fr> wrote: > Le 24 avril 2023 DdB a écrit : > > > 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. > https://www.cyberciti.biz/faq/update-upgrade-debian-10-to-debian-11-bullseye/ Usually this is the safest way. But why don't you upgrade sooner to > bullseye ? Do you have some problematic packages ? > > > 2. Install a fresh bullseye and try to manually make it as similar as > > can be to my current workhorse > > The more you customized your system the harder it will be > > > 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 need to you should only change manually your userid/groupid and > don't change system ids. Replacing entire passwd is usually a bad idea. > Also you should check your user/group are conforming to the minumum > defined in /etc/login.defs > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web