Even though I agree that we should never have been forced to reinvent a
wheel that wasn't broken, I have no problem with co-existence. But the
systemd cabal might not want to share. Will be interesting to see if at
some point those unit files are locked down in a way that prevents the
conversion. Then back to the creative drawing board. One possible
scenario . . . if init freedom can survive long enough, systemd might
just trip over its own feet and go poof. Hey, I can dream . . . :D

golinux


On 2019-11-27 19:23, Ralph Ronnquist via Dng wrote:
> Hmm, I understood
>

>     http://www.trek.eu.org/devel/sysd2v/sysd2v-0.2.sh

>
> to be the code, and that it's about to be included in the sysvinit
> package.
>
> If it works well enough, it'll be a handy tool for init script
> writers, even though it implicitly validates the existence of
> something the world could have been without to start with.
>
> Ralph.
>
> Steve Litt wrote on 28/11/19 11:53 am:
>> On Wed, 27 Nov 2019 12:18:55 -0600
>> golinux@??? wrote:
>>
>>> More fiddling while Rome burns . . . sigh . . .
>>>
>>> I'm in a bit of a mood because I thought that a script to convert
>>> systemd units to init style shell scripts would be worthy of at least
>>> some discussion.
>>>
>>> golinux
>>
>> Well holy cow, give us a chance!
>>
>> That conversion is pretty technical, and I haven't yet seen the source
>> code: Its location isn't obvious. I can't discuss something I have
>> little knowledge of. After all, we're not systemd fanboiz. The URL you
>> supplied raises more questions than answers.
>>
>> For instance, how the script decides whether to execute something in a
>> function or straightaway is a bit of a mystery to me. Another mystery
>> is which init system the output is intended to control. It doesn't
>> look
>> like any sysvinit scripts I've seen, and it's for sure not runit, s6
>> or
>> Epoch.
>>
>> If anyone finds the URL of the *actual code* of the converter, please
>> post it.
>>
>> You're right about one thing: This is great news. Whether we end up
>> using the script and adapting to other inits by parsing the output, or
>> whether we end up using part of the script to work with each init,
>> this
>> should make life easier.
>>
>> SteveT
>>