Date
1 - 4 of 4
Potential (?) systemd YOCTO problems
Morne
On Tue, Jun 04, 2019 at 11:34:15PM +0200, Zoran Stojsavljevic wrote:
(I did not find it anywhere in the manuals, maybe I missed the paragraph - please, advice where it is?).This is where I found it previously: https://www.yoctoproject.org/docs/2.7/dev-manual/dev-manual.html#using-systemd-exclusively Thank you again,Glad I could help. - Morné
|
|
Zoran
I would have a look at the values ofI would like to thank you for the advice. I tried several combinations without any success, and at the end I came up exactly what you have suggested to me. Local.conf looks something like this: https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/experimental/local.conf_core-tools-profile And the latest changes committed which I have tried following your suggestion are: https://github.com/ZoranStojsavljevic/bbb-yocto/commit/83c22e8ec516020206dc1b34e93276cca8f3f16b I need to do more tests... But seems that initial tests show that all scripts are in place, and systemd is used. This also should be much better documented somewhere in YOCTO documentation. My best guess (I did not find it anywhere in the manuals, maybe I missed the paragraph - please, advice where it is?). Thank you again, Zoran _______ On Mon, Jun 3, 2019 at 9:07 PM Morné Lamprecht <morne@linux.com> wrote:
|
|
Morne
On Mon, Jun 03, 2019 at 07:38:47PM +0200, Zoran Stojsavljevic wrote:
Still. I expected to see the following on the target (my BBB): /etc/init.d/networking script,I would have a look at the values of DISTRO_FEATURES_BACKFILL_CONSIDERED as well as VIRTUAL-RUNTIME_initscripts. My understanding is that if the former is set to "sysvinit", it causes any redundant SysVinit scripts to be removed, and further, that if the latter is set to "", then all initscripts are removed from the image altogether. - Morné
|
|
Zoran
Hello Folks,
I am a bit deeper to the systemd service investigation in YOCTO. I installed systemd service, I also have network manager package. I am using warrior. Here are the snippets of the HOST: [user@fedora29-ssd build]$ bitbake --version BitBake Build Tool Core version 1.42.0 [user@fedora29-ssd build]$ bitbake -s | grep networkmanager networkmanager :1.16.0-r0 networkmanager-openvpn :1.8.10-r0 python-networkmanager :2.1-r0 [user@fedora29-ssd build]$ bitbake -s | grep systemd python-systemd :234-r0 python3-systemd :234-r0 systemd 1:241+AUTOINC+c1f8ff8d0d-r0 systemd-bootchart :233+gitAUTOINC+fe1c5e41e6-r0 systemd-bootconf :1.00-r0 systemd-compat-units :1.0-r29 systemd-conf :241+AUTOINC+c1f8ff8d0d-r0 systemd-machine-units :1.0-r19 systemd-serialgetty :1.0-r5 systemd-systemctl-native :1.0-r6 [user@fedora29-ssd build]$ Still. I expected to see the following on the target (my BBB): /etc/init.d/networking script, but I have the following: root@beaglebone:/etc/init.d# pwd /etc/init.d root@beaglebone:/etc/init.d# ls -al drwxr-xr-x 2 root root 4096 Jun 3 2019 . drwxr-xr-x 27 root root 4096 May 30 23:46 .. -rwxr-xr-x 1 root root 1419 May 31 2019 socketcand root@beaglebone:/etc/init.d# The socketcand recipe is here: https://github.com/ZoranStojsavljevic/meta-socketcan/blob/master/recipes-can/socketcand/socketcand.bb Should I add something to the networkmanager recipe (to add some inheritance)??? To have the component (network script) in play/installed (in /etc/init.d/)? The command: # systemctl restart systemd-networkd does work. root@beaglebone:/etc/systemd# ls coredump.conf logind.conf networkd.conf sleep.conf system.conf user journald.conf network resolved.conf system timesyncd.conf user.conf root@beaglebone:/etc/systemd# cd network root@beaglebone:/etc/systemd/network# ls -al drwxr-xr-x 2 root root 4096 May 31 00:57 . drwxr-xr-x 5 root root 4096 Jun 3 2019 .. root@beaglebone:/etc/systemd/network# What I am doing wrong here? Thank you, Zoran _______
|
|