-=> On 08-15-19 20:55, Alexey Vissarionov wrote to Tony Langdon <=-

 TL> Why RPM?

 AV> Besause it is a quality mark.

That could mean anything.  In my world, it's "marketing speak",
and I tend to
ignore that without substantiating evidence.

 TL> dpkg offers similar functionality.

 AV> Have you tried building rpm and deb packages?

Not what I do - irrelevant to me.

 TL> I will use systems that use either.

 AV> Your choice...

That's what Linux is all about. :)

 AV>> 2. SysV init
 TL> Sadly, seems to be a dying breed these days, with systemd taking over
 TL> on a lot of distros.

 AV> We have distributions with both. And even more: some experienced admin
 AV> may switch from one to other and back again.

True.  I haven't yet found documentation that I can follow for systemd.  Other
than that, I have no issue with it.

 TL> I haven't got my head around systemd, but know one of these days I
 TL> really need to get to know it, because like it or not, I will be
 TL> using systems that are based on systemd.

 AV> The old good CentOS 6 will reach EOL this year... and we expect some
 AV> users moving to us :-)

us???

 TL> That said, I quite like SysV init. It's straightforward and orderly.
 TL> Most of my systems still use it.

 AV> Same thing here. The only advantage of systemd is the startup
 AV> dependencies concept, but that's really easy to implement with SysVinit
 AV> - just declare "status" command as mandatory.

 AV> E.g. `service nginx start` may check whether `service network status`
 AV> is "running".

Yes, not hard to do in SysV.


... I used to think I was vague ... but now I'm not so sure!!!!!
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux