sysv init as start process

[Ralf Mardorf]

On Tue, 9 Aug 2016 18:50:22 +1000, Jared Norris wrote:
>On 9 August 2016 at 14:55, Ralf Mardorf <silver.bullet at zoho.com> wrote:
>
>> On Tue, 09 Aug 2016 04:38:07 +0300, Ops Cloud wrote:  
>> >Can we setup the default startup process to sysv init rather than
>> >upstart?
>> >
>> >I really don't like what upstart does. thanks.  
>>
>> Are you kidding?
>>
>> Most distros, including Ubuntu, switched to systemd.
>>
>> If you dislike systemd, a few distros provide alternative new init
>> systems. Soon or later most likely sysvinit will be dropped by
>> those distros, that still provided it in addition to systemd. The
>> distros providing new alternatives unlikely have a huge user base,
>> something that could be a disadvantage.
>>
>> Don't get me wrong, I don't claim that systemd is the best or even a
>> good replacement, I only point out, that it is used by Ubuntu and
>> most other distros.
>
>That being said, a quick google shows there are people who appear to
>have it working okay [1] [2]. Give those a try and let us know if
>there are any specific issues you have.
>
>There is also a bit of a transition guide and help on the wiki [3]
>
>[1]
>http://askubuntu.com/questions/779640/how-to-remove-systemd-from-ubuntu-16-04-and-prevent-its-usage

"I was able to enable upstart and disable systemd with commands that
follows"

This is not SysVinit, it is upstart. The OP still seems to use a release
that by default does use upstart. IOW to get upstart the OP needs
nothing to do.

>[2]
>http://askubuntu.com/questions/760615/ubuntu-16-04lts-does-not-boot-after-package-upstart-sysv-is-installed

This link is also about upstart and not about SysVinit.

>[3] https://wiki.ubuntu.com/SystemdForUpstartUsers

I strongly recommend to learn to live with systemd, resp. to stay with
upstart, when using an older release.

Regards,
Ralf