Hello All,

On Thu, 28 Nov 2019 16:30:41 -0500
Steve Litt <slitt@???> wrote:

> 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
>
> I have good news, bad news, and better news.
>
> Good news. The latest script at http://www.trek.eu.org/devel/sysd2v/
> appears to make good sysvinit init scripts from a unit file.
>
> Bad news: That script is just for sysvinit, and in my 1/2 hour look at
> it I couldn't find an easy way to pick off info necessary to make
> facilities for s6, runit or Epoch.
>
> Better news: Systemd Unit Files are a pretty good specification of what
> any process supervisor should do with a daemon, so converters for s6,
> runit and Epoch should be pretty easy to make. Because declaratory Unit
> Files are by necessity a superset of script based systems, some human
> intervention will be necessary, but not a whole lot.
>
> Better news: There's an already made collection of runit run scripts,
> for the usual suspects, at http://smarden.org/runit/runscripts.html .
> I've put out a query for a similar collection of s6 scripts.
>
> SteveT

We have a problem that is already a hipotsis of been solved converting the Service Units, to SysVinit daemons..
Since the Unit Files in SystemD, are "unit...", could we theoretically implement the Stub Interface for the Unit Files in SysVInit, and them threat the cases has we want to???

Because the problem with inits, in Unix Like Systems is that is there NO Standars today..
freedesktop.org, should adress the situation, like they have done in the past with other things..
Nowadays Desktop is more or less standardized.. filesystem more or less...

For Init Systems.. theres is no public Standard...
So or freedesktop.org adress the case or it will be like a jungle( it is now.. )..

We can also have 2 fronts...
1) Convert the unit.files from SystemD to SysVInit daemons
2) Adapt an API like, only for the unit. files that describe the Services, like a stub, an adaptor, and add it to sysVInit

In the 2nd case we parse the unit.files and work the meaning as we want to( but without creating SysVinit files, since we already have what is needed to launch the service.. , **The problem is to control this pseudo service after is running**.. ) ofcourse its a lot easier to talk than do it.. but that would give us plenty of time to recreate the SysVInit script we want to, after that..

But that also means that the Unit.Files language used to describe SystemD services will be "more closer to a standard"..

Could be a situation were SysVInit can support the traditional SysVInit daemons, usual runlevels, and such, and interprete the unit files of SystemD, but atribute them to this runlevels??
What do you think?

I just want to add my 2 cents,. because I think that any one of this 2 cases is a valid case..

--
tux <tuxd3v@???>