init-ifupdown: fix the networking service failure 13/5013/1
authorJackie Huang <jackie.huang@windriver.com>
Thu, 5 Nov 2020 08:22:05 +0000 (16:22 +0800)
committerJackie Huang <jackie.huang@windriver.com>
Thu, 5 Nov 2020 08:31:18 +0000 (16:31 +0800)
commit3536a5570beda4d0980f515a0880870aa7d0066c
treecf053f44dc464dc09dc6fa638489fbc4f460fe13
parent5ec26a6d2dcaf8cbe127eee6a0a3250497c33a7e
init-ifupdown: fix the networking service failure

* Add RDEPENDS on 'ifupdown' because:
    The 'ifup' command provided by 'busybox' and 'ifupdown' behave differently
    when an interface has been configured:

    - The one from busybox
    $ sudo ifup lo; echo $?
    RTNETLINK answers: File exists
    1

    - The one from ifupdown
    $ sudo ifup lo; echo $?
    ifup: interface lo already configured
    0

    The exit code 1 from the busybox one would cause the networking service
    failed, so add RDEPENDS on ifupdown to avoid using the one from busybox.

* Do not auto config eth0 since it may not exist.

Issue-ID: INF-192

Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Change-Id: I5d9478ca163d90da3106ecf6a05ee9459df83502
meta-stx/recipes-core/init-ifupdown/init-ifupdown_%.bbappend [new file with mode: 0644]