darksun wrote: Tue Oct 29, 2024 8:13 am
for several months still
Hopefully, until Debian 12 reaches its EOL date. I still maintain the Debian 11 based 9.3.x series, as you can see. I think it's the only Puppy with 3 years (?) of updates, and I want 10.0.x to be like this.
darksun wrote: Tue Oct 29, 2024 8:13 am
is there any plan to include/back-port some/all the (applicable) security and privacy and improvements features from 11.0.x ? if feasible and easily implementable.
Check the changelog, I backport some things to 10.0.x but it's a small minority. The way Puppy works prevents me from backporting many of these improvements, and I'm using new technologies like eBPF and erofs, which are not present, not working or too old.
darksun wrote: Tue Oct 29, 2024 8:13 am
b) my understanding is that vanilla dpup uses a custom/modified version of sysVinit , am I right?
No. 10.0.x and below use busybox init, which is somewhat similar to sysvinit. 11.0.x uses a custom init "system" I wrote, see https://github.com/vanilla-dpup/woof-CE ... uilds/init.
darksun wrote: Tue Oct 29, 2024 8:13 amCould you @dimkr explain shortly if systemd as an active role within your system
No, it's there only to satisfy dependencies on it. Debian has packages that depend on either systemd (directly or through logind) or elogind, and they're installable on Debian with either systemd or sysvinit (plus elogind). However, some packages have a hard dependency on systemd but it's not actually a dependency at runtime. Therefore, systemd is installed to have a complete and valid dependency tree, but it doesn't run at all.