On Sat, Aug 5, 2023 at 4:32 PM tito via Dng <dng@???> wrote:
>
> On Sat, 5 Aug 2023 15:46:12 +0000
> Manfred Wassmann via Dng <dng@???> wrote:
>
> > On Fri, Aug 4, 2023 at 11:57 AM tito via Dng <dng@???> wrote:
> > >
> > > You can install another init with systemd running and reboot to it.
> > > OTOH you can remove sysvinit with dpkg more easily and end
> > > with a removed pid 1. Tested.
> >
> > Then you should probably go to Ian Jackson's Blog at
> > diziet.dreamwidth.org, which initially spurred this thread[1], and
> > notify him about that. He surely will be delighted if a real insider
>
> I don't think I would like to do this but go on if you feel it is the right thing (TM).

;-)
I suggested that because you were hitting at me while Ian would be the
appropriate target, after all it was him who claimed it wasn't
possible to remove systemd after booting into a system where it is the
active init.

> OTOH maybe I should file a bug report against sysvinit that it can be
> removed while running as PID 1 even if with --force-all.

then "go on if you feel it is the right thing (TM)"