> Sent: Saturday, November 30, 2024 at 11:54 AM
> From: "Andy Smith" <a...@strugglers.net>
> To: debian-user@lists.debian.org
> Subject: Re: where is mail.log
>
> Hi,
>
> On Sat, Nov 30, 2024 at 01:31:12PM +0100, poc...@homemail.com wrote:
> > You did not comprehend what I posted.
>
> I think it is you who are having problems reading.
>
Again You can not comprehend
> > I am on the systemd mail list.
> > They have dropped all sysV support.
> > The only way you'll have init script support is if you rip out systemd.
>
> Yes, that is what is being said: it is still possible to run Debian
> without systemd. People are doing it. There are package maintainers that
> wish to let people do it. Surprise! It's a funny old world.
Well I didn't say you couldn't
>
> > Since debian is using systemd for their init system debian will have
> > to come into the here and now.
And debian is light years away from properly using systemd.
>
> Have you been living under a rock for ten years? The only reason why
> systemd is able to drop their svsv init script support is *because*
> Debian has been ready to also do so for a long time! Nothing operates in
> a vacuum. There are multiple Debian developers who are also systemd
> developers. They have been working on the goal to make everything in
> Debian have a native systemd service unit for a *long* time and we've
> been at that stage for some time already. There is no "coming into the
> here and now". We are here already because of work done in part by
> Debian.
>
> However it is also separately true that many packages still have a sysv
> init script that their maintainers support for the purposes of having it
> work without systemd. Though I have no interest in doing that personally.
OS
>
> What you seem to not understand is that it has been Debian policy for
> *years* for packages to have systemd unit files, but it has not been
> policy for packages to get rid of any existing or contributed sysv init
> scripts. That is optional.
Yet you miss the point
>
> There's plenty of users who do need to "get into the here and now" (as
> evidenced by this thread), but Debian itself has been there for a full
> release cycle at least.
LOL No, just No
[alarm@alarm ~]$ pacman -Q|grep systemd
systemd 256.8-2
systemd-libs 256.8-2
[alarm@alarm ~]$ cat /etc/hosts
# Static table lookup for hostnames.
# See hosts(5) for details.
dpkg -l|grep systemd
libnss-resolve 252.31-1~deb12u1
libpam-systemd 252.31-1~deb12u1
libsystemd-shared 252.31-1~deb12u1
libsystemd0 252.31-1~deb12u1
systemd 252.31-1~deb12u1
systemd-container 252.31-1~deb12u1
systemd-resolved 252.31-1~deb12u1
systemd-sysv 252.31-1~deb12u1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Gone not longer supported
debian will need to see the lite or change to sysV init
systemd-timesyncd 252.31-1~deb12u1
