So I'm trying to build my recipe and it continuously fails at the do_populate_lic() phase. I've pasted my recipe file. The Source # Recipe created by recipetool # This is the basis of a recipe and may

#bitbake #systemd #ubuntu #honister

Hi, In 3.1.12, I noticed weston service type was changed to Nofity. This make weston service cannot be restarted by "systemctl restart weston@root" command. The service is then timeout and fail. Inves

#systemd

Hi, I'm looking for advice on https://bugzilla.yoctoproject.org/show_bug.cgi?id=14375 Seems like an easy fix but not sure how I should handle it. I'm willing to put in the effort, just need some point

#systemd

It's fine to inherit both classes and install both files without even checking DISTRO_FEATURES. There's behind the scenes magic that will do the right thing depending on what init manager is chosen in

#sysvinit #systemd

Hello, I have a recipe that installs a simple bash script to run on startup. As you all know, there is systemd and sysvinit. I need to add support for both init managers. I can do : SRC_URI_append = "

#sysvinit #systemd

Hi, Is it possible to set systemd environment variables from a recipe to do the same as 'systemctl set-environment SOME_ENV_VAR'?

#systemd

there is system integration testing that happens on autobuilders which you can check reports for ptests are generic and one can add more to a package but usually you will see that its trying to run th

#systemd #yocto

Hi, I'm aware that yocto picks up packages from respective open source community. For e.g. dbus package is picked from freedesktop.org etc. In this regard, what kind of tests does yocto runs to ensure

#systemd #yocto

you are better off by having two different DISTROs like poky and poky-altcfg is.

#yocto #bitbake #systemd #sysvinit

Hi all, I would like to change the init system (systemd / SysVinit) on a per-image basis. Therefore I added both "systemd" and "sysvinit" to my DISTRO_FEATURES. I set this inside my image-systemd.bb t

#yocto #bitbake #systemd #sysvinit

Thanks... Yesterday I decided to go with ntpq/ntpdate/and a ntpstat script which does some basic stats through ntpd/ntpq/ntpdate and Chrony. We will see how it goes might be enough... Steve

#systemd #yocto #linux

Please, try this: https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-dunfell/local.conf This is the systemd addendum in my BBB Dunfell local.conf : ## Add systemd service DIS

#systemd #yocto #linux

what all functionality are you looking for. E.g. there is date utility and hwclock utility which can help you manipulate system time. you could also look into ntpd and/or chrony for Network time setti

#systemd #yocto #linux

Currently not using system as our default init system (investigating why but this might not be an option). Is there any other utility I might use under Yocto to get similar data as that produced by ti

#systemd #yocto #linux

Is there documentation on how to set this up ?

#systemd #yocto #linux

Hi Steve, It comes with systemd. Use it as your init system and then you'll have the command. Quentin

#systemd #yocto #linux

I currently have "ntpq" building and installing correctly... Can someone tell me what it takes to get the "timedatectl" command utility built into Yocto kernel image ? I see it referenced in both : op

#systemd #yocto #linux

I am trying to build an image with the following command line utilities built in: ntpq, timedatectl, and ntpstat. Note : ntp is builtinto my image and working correctly. I performed a simple test usin

#systemd #yocto #linux

Thanks Matt!! This solved it. And yes, the branch is thud-l4t-r32.3.1.

#yocto #systemd

<eliranl=amazon.com@...> wrote: Which of the meta-tegra branches is it? thud-l4t-r32.3.1? [...] There was an issue with NVIDIA's eqos driver in older BSPs. I know it affected the TX

#yocto #systemd