On 23 Jun 2023 16:41, mick.crane wrote:
On 2023-06-23 11:58, Nicolas George wrote:
Andy Smith (12023-06-23):
It seemed fine the way it was. The only reason why I didn't answer
is that I don't know anything about removing systemd!
Me I know just a little about it, enough to know that discussion with
people who want to remove it but are not already capable of doing it by
themselves is a waste of time.
It's a subjective thing.
It is what it is but I do feel warmth towards those try to make it work
without systemd.
it's not particularly logical.
mick
Yes, init freedom is subjective, it's like using Firefox or Chrome.
It's not a matter of logic ; )
I have some Debians with sysvinit, some with systemd, both work.
Switching from systemd to sysv following the Debian wiki page was
painless, although I mostly did it on "small hosts", with not much
packages installed.
Maybe installs with many packages are harder to manage ?
Because you have to be careful during package management, some commands
would propose to remove sysv and install systemd instead !
I guess not all packages are "sysv aware" (or rather non-systemd aware).
I suggest non-systemd init users (sysv, rc,...) to use --dry-run and
--no-install-recommends during package management, it can help.
But for the OP, who iirc asked if he should switch to sysv -before- or
-after- the bookworm update, I have no idea.
I updated sysv- and systemd-based Debians from bullseye to bookworm
without problems, but didn't try the switch since, from a bookworm host.
YMMV !
