On Fri, 17 Nov 2017 09:14:38 +0000
KatolaZ <kato...@freaknet.org> wrote:

> On Thu, Nov 16, 2017 at 10:12:51PM +0100, Martin Steigerwald wrote:
> 
> [cut]
> 
> > 
> > I do think that it is wise to replace SysVinit at some point or at
> > least provide an alternative. I even agree with tech-ctte decision
> > regarding replacing SysVinit, that is not the point. Systemd
> > addressed a need. Yet it went to far, it is too many in one,
> > attitude of at least some upstream developers appear to be toxic to
> > me and so on… and it was not the only viable option… we all know
> > the arguments, no need to repeat, … 
> 
> We agree on the necessity of providing (optional) alternatives to
> sysvinit. But this cannot mean just "put the packages in the repos and
> the users will figure it out" [*]. For Devuan, providing alternatives
> (like for instance OpenRC) means *supporting* the alternatives and
> making sure that the users can select the one they like with the least
> effort on their side. Otherwise the users could simply put together
> their own LFS... :)
> 
> My2Cents

I wasn't clear in my last post on this. I have no problem with keeping
sysvinit as PID1 for a long, long time. I have nothing against keeping
the majority of daemons under the care of sysvinit for a long time.

My suggestion was simply to provide a *supervisor*, to be spawned by
sysvinit probably via inclusion in /etc/inittab, to run daemons that
become problematic in sysvinit due to Debian's lack of working sysvinit
init scripts.

My understanding from another Devuan discussion is that the current
Debian runit package **for runit as a supervisor, not as a whole init
system** already works, and does not uninstall sysvinit. So if
Debian's libreswan package has no init script, I could create a run
script, the Devuan libreswan packager could include it, require runit,
and bang, libreswan works on Devuan.

To a certain extent, for early adopters, I *did* suggest something like
"put the packages in the repos and the users will figure it out". A ten
step cookbook document will enable the user to do that, until we figure
out the more Devuan way to do it.

OpenRC isn't part of this discussion: It is not, and cannot function
as, a supervisor. If you want simply to run libreswan and hope it stays
running, you could simply run it in /etc/rc.local. I'm not suggesting
an init system for Devuan, and to me, for the foreseeable future,
sysvinit seems adequate, especially if reenforceable with a
supervisor.  

More in other emails...
 
SteveT

Steve Litt 
November 2017 featured book: Troubleshooting: Just the Facts
http://www.troubleshooters.com/tjust
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to