On 7 May 2017 at 16:30, Gordon Messmer <gordon.messmer@xxxxxxxxx> wrote:
> On 05/07/2017 07:22 AM, ken wrote:
>>
>> "Note that traditional init scripts continue to function on a systemd
>> system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
>> into a service unit foobar.service during system initialization."
>> ...
>> However, what it implies doesn't seem to work out.
>
>
> It does not imply what you infer, because it explicitly says that the file
> in init.d is mapped to a systemd service unit. The files in rc.d are not
> used, because systemd does not boot to runlevel 2, 3, 4, or 5.
>
> If you want "network" to start on boot, you would use "systemctl enable
> network". (You would also want to "systemctl disable NetworkManager")
>
The two do not conflict and there is no need to to disable one to use the other.
In fact you shoudl leave network enabled when using NetworkManager or
you will get some odd behaviours, like missing loopback.
If you do 'nmcli d' to list devices you'll see that loopback is
unmanaged, ie it's handled by the network service.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
