I've been watching this with interest. Back around 1980 I designed a Unix equivalent to SysV init at Raytheon data systems because system v was not available at the time. While systemd has its issues, using SysV init to schedule start up dependencies is difficult. Any it's slow because it is based on shell scripts. But, systemd does handle dependencies well and significantly speeds up the initialization process. I would prefer systemd to be less of an everything package, but having struggled with initd dependent issues in a complex environment made me appreciate systemd.
-- Jerry Feldman <gaf.li...@gmail.com> Boston Linux and Unix http://www.blu.org On Tue, Jun 4, 2024, 1:18 PM Kent Borg <kentb...@borg.org> wrote: > On 6/4/24 09:59, Kent Borg wrote: > > -kb, the Kent who doesn't know what a good solution would have been. > > Maybe the right approach was to not touch the init system at all, and > instead finish all that D-Bus work to rationalize dynamic dependencies. > Would that work? > > And maybe that means submitting a few patches to various important > packages to implement some key D-Bus-something-something calls. That way > those other packages (such as OpenSSH) could vet any changes to their code. > > Donno. > > -kb > > _______________________________________________ > Discuss mailing list > Discuss@driftwood.blu.org > https://driftwood.blu.org/mailman/listinfo/discuss > _______________________________________________ Discuss mailing list Discuss@driftwood.blu.org https://driftwood.blu.org/mailman/listinfo/discuss
