Re: [OE-core] Systemd Upgradation from 250.5v to 256v in Yocto Kirkstone

You need to first publish the layer and steps to reproduce the problem. Otherwise it’s a guessing game. Alex On Mon 5. Aug 2024 at 10.07, jahnavijha14 via lists.openembedded.org wrote: > Hi, > > I am trying to upgrade systemd package to 256v. I have systemd 256 version > recipe files in my cust

[OE-core] Systemd Upgradation from 250.5v to 256v in Yocto Kirkstone

Hi, I am trying to upgrade systemd package to 256v. I have systemd 256 version recipe files in my custom layer. But while building ( bitbake systemd) it tends to always take the previous version of systemd that is 250.5. I get a warning like this: ---

Re: [OE-core] systemd-firstboot not triggered on read/write /etc folder

Does adding 'stateless-rootfs' to IMAGE_FEATURES work for you? meta/classes-recipe/image.bbclass:IMAGE_PREPROCESS_COMMAND:append = " ${@ 'systemd_preset_all systemd_disable_units' if bb.utils.contains('DISTRO_FEATURES', 'systemd', True, False, d) and not bb.utils.contains('IMAGE_FEATURES', 'st

[OE-core] systemd-firstboot not triggered on read/write /etc folder

Hi! In the systemd-systemctl there is a *systemctl* script used for some configuration/settings for the systemd services (e.g. enabling services). In this script if we call the *preset_all* command, it will create an empty /etc/machine-id file. This is required on read-only /etc folder, otherwi

Re: [OE-core] systemd issue with network commandline config and 6.4 kernel

On Tue, 2023-08-08 at 12:13 -0400, Bruce Ashfield wrote: > On Tue, Aug 8, 2023 at 11:35 AM Chen Qi via lists.openembedded.org > wrote: > > > > I found some clue, but not the root cause yet. > > The eth0 is renamed to enp0s2 by 80-net-setup-link.rules udev rule in > > systemd. And the connman.con

Re: [OE-core] systemd issue with network commandline config and 6.4 kernel

ng I ran into on a build server when upgrading to a "newer" 6.2 kernel, I had to disable interface renaming in order to get a consistent network configuration, and did that via "net.ifnames=0" on the kernel command line. Bruce > > Regards, > Qi > > > -Origin

Re: [OE-core] systemd issue with network commandline config and 6.4 kernel

On 2023-08-08 17:34, Chen Qi via lists.openembedded.org wrote: Maybe some changes in new kernel allows renaming network interface while it's up? Seems correct! https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=bd039b5ea2a91ea707ee8539df26456bd5be80af That was added

Re: [OE-core] systemd issue with network commandline config and 6.4 kernel

rnel allows renaming network interface while it's up? Regards, Qi -Original Message- From: openembedded-core@lists.openembedded.org On Behalf Of Richard Purdie Sent: Tuesday, August 8, 2023 7:51 PM To: openembedded-core Cc: Luca Boccassi ; Alexandre Belloni Subject: [OE-core] systemd issue with

[OE-core] systemd issue with network commandline config and 6.4 kernel

Hi, We'd like to switch to the 6.4 kernel and there are two blockers. One of them is that systemd appears to be breaking the network device config with 6.4 kernels. This happens with core-image-sato but not with core-image-minimal. In the sato image, I can see the kernel gets the ip= commandline

[OE-core] systemd service with @ postinstall bug

Starting from this commit https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=2751472807edc6d2ccc93b6339e6dc57d4abb2da I'm not able to install templated service in my recipes, like SYSTEMD_SERVICE:${PN} = "php-fpm@9000.service" At the rootfs creation state Yocto/OE says, the po

Re: [OE-core] systemd service@ bug

Hi, On 2023/07/19 16:47, Vyacheslav Yurkov wrote: > Hey, > Usually Steve Sakoman cherry-picks patches from master. If it's not the case, > it was probably not applied clearly or simply overlooked. You can submit a > backport with the branch tag. Thank you! I understood. I checked git log and i

Re: [OE-core] systemd service@ bug

Hey, Usually Steve Sakoman cherry-picks patches from master. If it's not the case, it was probably not applied clearly or simply overlooked. You can submit a backport with the branch tag. Vyacheslav On 19.07.2023 03:48, Yuta Hayama wrote: Hi, This issue has been fixed in master. https://git

Re: [OE-core] systemd service@ bug

Hi, This issue has been fixed in master. https://git.openembedded.org/openembedded-core/commit/?id=d18b939fb08b37380ce95934da38e6522392621c But, yes. This patch has not yet been backported to the any stable branch. I don't know about the maintenance process for the stable branch, but I expect t

[OE-core] systemd service@ bug

Hello! (sorry, previously posted as the reply to wrong message) starting from 2aa82324d43467e7c8bfbbb59570ee3306264b75 commit (dunfell and probably other branches) https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=2aa82324d43467e7c8bfbbb59570ee3306264b75 the SYSTEMD_SERVIC

[OE-core] systemd service@ bug

Hello! starting from 2aa82324d43467e7c8bfbbb59570ee3306264b75 commit (dunfell and probably other branches) https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=2aa82324d43467e7c8bfbbb59570ee3306264b75 the SYSTEMD_SERVICE:${PN} = "php-fpm@9000.service" syntax in the recipe bri

Re: [OE-core] systemd-getty-generator present but undesired

Met vriendelijke groet / kind regards, Mike Looijmans System Expert TOPIC Embedded Products B.V. Materiaalweg 4, 5681 RJ Best The Netherlands T: +31 (0) 499 33 69 69 E: mike.looijm...@topicproducts.com W: www.topicproducts.com Please consider the environment before printing this e-mail On 30

Re: [OE-core] systemd-getty-generator present but undesired

On 7/28/20 6:33 AM, Mike Looijmans wrote: I had a hard time getting a serial attached bluetooth device to work, untilI discovered that systemd is running a "getty" on that port (which happens tobe "ttyS0"). The cause is that "systemd-getty-generator" detects that the port comes online (runt

[OE-core] systemd-getty-generator present but undesired

I had a hard time getting a serial attached bluetooth device to work, untilI discovered that systemd is running a "getty" on that port (which happens tobe "ttyS0"). The cause is that "systemd-getty-generator" detects that the port comes online (runtime, it's inside an FGPA) and then dynamicall

[OE-core] systemd 243 update - not happening for 3.0...

On the YP tech call yesterday, I had suggested that someone at WR might work on the systemd-243 update this week. It turns out that other activities have higher priority so it will have to be done by someone else to make the 3.0-M3 cut-off. If that doesn't happen we'll get to it after 3.0, I expec

Re: [OE-core] systemd/busybox fsck fail to run

On Wed, Sep 5, 2018 at 9:25 PM Khem Raj wrote: > > > > On 9/5/18 5:46 AM, Andrej Valek wrote: > > Hi Alex, > > > > There could be multiple options, how to handle this. > > > > My 2cents about this problem: > > 1. Use update-alternatives to handle this > > 2. Rework busybox itself to handle this

Re: [OE-core] systemd/busybox fsck fail to run

On 9/5/18 5:46 AM, Andrej Valek wrote: > Hi Alex, > > There could be multiple options, how to handle this. > > My 2cents about this problem: > 1. Use update-alternatives to handle this > 2. Rework busybox itself to handle this option > 3. Just create a patch to ignore this option > I am no

Re: [OE-core] systemd/busybox fsck fail to run

Hi Alex, There could be multiple options, how to handle this. My 2cents about this problem: 1. Use update-alternatives to handle this 2. Rework busybox itself to handle this option 3. Just create a patch to ignore this option Cheers, Andrej On 09/05/18 10:37, Alex Kiernan wrote: > I've just

[OE-core] systemd/busybox fsck fail to run

I've just come across a box with a corrupt filesystem which wasn't being cleaned (using systemd and busybox): Aug 29 16:03:22 localhost systemd-fsck[143]: read_bad_blocks_file: No such file or directory while trying to open -M Aug 29 16:03:22 localhost systemd-fsck[143]: Warning: fsck.ext4 /dev/mm

Re: [OE-core] systemd PACKAGECONFIG = "lz4" leads to broken init

Hi Marcus, This fix isn't correct, please see Ross' reply to: [OE-core] [PATCH 0/1] systemd: fix PACKAGECONFIG for lz4 // Robert On 12/21/2017 09:26 PM, Marcus Hoffmann wrote: Hey Robert, thanks for the patch. I'd like to understand how this fixes the problem or probably more genrally how th

Re: [OE-core] systemd PACKAGECONFIG = "lz4" leads to broken init

On 12/21/2017 03:26 PM, Marcus Hoffmann wrote: thanks for the patch. I'd like to understand how this fixes the problem or probably more genrally how the PACKAGECONFIG thing works internally. Can someone give me a pointer on where to look? It seems a bit like magic just adding "lz4" twice at the

Re: [OE-core] systemd PACKAGECONFIG = "lz4" leads to broken init

Hey Robert, thanks for the patch. I'd like to understand how this fixes the problem or probably more genrally how the PACKAGECONFIG thing works internally. Can someone give me a pointer on where to look? It seems a bit like magic just adding "lz4" twice at the end :-). Kind regards, Marcus On 2

Re: [OE-core] systemd PACKAGECONFIG = "lz4" leads to broken init

Hi Marcus, I think that the following patch can fix the problem: The following changes since commit 978472c58629d1448399207873bbead96b27102e: image.bbclass: Add additional bb.debug to help track 12304 (2017-12-18 18:02:12 +) are available in the git repository at: git://git.openembe

[OE-core] systemd PACKAGECONFIG = "lz4" leads to broken init

Dear all, when building poky with PACKAGECONFIG_append_pn-systemd = "lz4" in local.conf and DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd" in bblayers.conf, init (=systemd) can't start because of a missing lz4 library: /sbin/init: error while loading shared librari

Re: [OE-core] systemd and /etc/machine-id

On Sun, 2017-03-05 at 10:40 +0100, Nicolas Dechesne wrote: > hi, > > I am trying to understand why the systemd recipe creates an > empty /etc/machine-id file: > > # Create machine-id > > # 20:12 < mezcalero> koen: you have three options: a) run > systemd-machine-id-setup at install ti

[OE-core] systemd and /etc/machine-id

hi, I am trying to understand why the systemd recipe creates an empty /etc/machine-id file: # Create machine-id # 20:12 < mezcalero> koen: you have three options: a) run systemd-machine-id-setup at install time, b) have / read-only and an empty file there (for stateless) and c) boot with / writa

[OE-core] systemd-serial-getty obsolete?

Hello! systemd-serialgetty.bb was introduced in OE-core together with systemd 1.96 and probably goes back even further (copied from meta-systemd). It explicitly instantiates serial-getty@.service for serial ports specified by SERIAL_CONSOLES. I'm wondering whether that is still needed. systemd al

Re: [OE-core] [oe-core][systemd][PATCH] some dependencies in systemd seem not to be taken into account in systemd_229.bb

On Mon, Mar 07, 2016 at 12:47:09PM +0100, Anders Darander wrote: > (Resending as it didn't go to the list). > > Thanks! > > I've just ran into this myself this morning. > > A few comments are inlined. > > * Herve Jourdain [160307 11:51]: > > > # Sign the journal for anti-tampering > > > -PAC

Re: [OE-core] [oe-core][systemd][PATCH] some dependencies in systemd seem not to be taken into account in systemd_229.bb

* Burton, Ross [160307 13:11]: > On 7 March 2016 at 12:01, Herve Jourdain wrote: > > For the gcrypt/resolved patch, I will rework it. > > One thing, though, the idea was to add the --disable-gcrypt in the > > EXTRA_OECONF, if neither gcrypt nor resolved are enabled. > > Hence the removal of "--

Re: [OE-core] [oe-core][systemd][PATCH] some dependencies in systemd seem not to be taken into account in systemd_229.bb

On 7 March 2016 at 12:01, Herve Jourdain wrote: > For the gcrypt/resolved patch, I will rework it. > One thing, though, the idea was to add the --disable-gcrypt in the > EXTRA_OECONF, if neither gcrypt nor resolved are enabled. > Hence the removal of "--disable-gcrypt" in the PACKAGECONFIG[gcrypt

Re: [OE-core] [oe-core][systemd][PATCH] some dependencies in systemd seem not to be taken into account in systemd_229.bb

Message- From: Anders Darander [mailto:and...@chargestorm.se] Sent: lundi 7 mars 2016 12:47 To: Herve Jourdain Cc: openembedded-core@lists.openembedded.org Subject: Re: [OE-core] [oe-core][systemd][PATCH] some dependencies in systemd seem not to be taken into account in systemd_229.bb (Resendi

Re: [OE-core] [oe-core][systemd][PATCH] some dependencies in systemd seem not to be taken into account in systemd_229.bb

(Resending as it didn't go to the list). Thanks! I've just ran into this myself this morning. A few comments are inlined. * Herve Jourdain [160307 11:51]: > # Sign the journal for anti-tampering > -PACKAGECONFIG[gcrypt] = "--enable-gcrypt,--disable-gcrypt,libgcrypt" Please, keep this line a

[OE-core] [oe-core][systemd][PATCH] some dependencies in systemd seem not to be taken into account in systemd_229.bb

Systemd: - RESOLVED depends on GCRYPT, so GCRYPT should be enabled if RESOLVED is enabled - ${PN}-binfmt should be added to SYSTEMD_PACKAGES only if binfmt is enabled Without this patch, build fails when gcrypt is not in PACKAGECONFIG, but resolved is, or when binfmt is not in PA

Re: [OE-core] systemd service vs. update-alternatives (was rsyslog: buggy systemd/ua handling?)

On 20.11.2015 14:42, Steffen Sledz wrote: > PS: What's the better place for this discussion? This mailing list? Or > ? Ping! -- DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, 10319 Berlin, Germany Tel: +49 30 515932-237 mailto:sl

Re: [OE-core] systemd service vs. update-alternatives (was rsyslog: buggy systemd/ua handling?)

On 20.11.2015 10:06, ChenQi wrote: > I sent out a series of patches regarding syslog & systemd some time ago. > The title is "[OE-core] [PATCH V3 0/4] Fixes for systemd services in systemd". > Codes regarding update-alternatives and syslog for 'rsyslog' recipe is > actually part of the whole fix.

Re: [OE-core] systemd service vs. update-alternatives (was rsyslog: buggy systemd/ua handling?)

I sent out a series of patches regarding syslog & systemd some time ago. The title is "[OE-core] [PATCH V3 0/4] Fixes for systemd services in systemd". Codes regarding update-alternatives and syslog for 'rsyslog' recipe is actually part of the whole fix. You could try the patch series to see if

[OE-core] systemd service vs. update-alternatives (was rsyslog: buggy systemd/ua handling?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18.11.2015 17:14, Steffen Sledz wrote: > On 17.11.2015 09:08, Steffen Sledz wrote: >> On 16.11.2015 12:28, Steffen Sledz wrote: >>> I'm not sure but i believe there's a bug in the systemd/ua-handling in >>> meta-oe/recipes-extended/rsyslog/rsyslog_

Re: [OE-core] systemd + run-postinsts.service

On Tue, 2015-03-24 at 09:33 +1100, Jonathan Liu wrote: > I am not sure how well systemd works with executing systemctl to > manipulate services from within a service that is starting... > > What is the definition of foobar.service? Manipulating services within a service works. You were on the rig

Re: [OE-core] systemd + run-postinsts.service

On 24/03/2015 8:57 AM, Patrick Ohly wrote: Hello! I'm using systemd from OE-core master to boot core-image-minimal. I'm seeing a boot failure where "Run pending postinsts" (aka run-postinsts.service) gets stuck during booting under very specific circumstances: 1. The package has a pkg_pos

[OE-core] systemd + run-postinsts.service

Hello! I'm using systemd from OE-core master to boot core-image-minimal. I'm seeing a boot failure where "Run pending postinsts" (aka run-postinsts.service) gets stuck during booting under very specific circumstances: 1. The package has a pkg_postinst_${PN} which (intentionally) fail

[OE-core] systemd getty

Hello, my QT app can't response to key, when tty1 hold by getty. how to disable getty@tty1.service when generating image? -- Nanjing Jilong Yi Qingliang niqingliang2...@gmail.com ___ Openembedded-core mailing list Openembedded-core@list

Re: [OE-core] systemd

On Tuesday, July 02, 2013 09:35:20 AM Yi Qingliang wrote: > Hi, All: > > I want use systemd, add following into my own distro.conf > DISTRO_FEATURES_append = " systemd" > VIRTUAL-RUNTIME_init_manager = "systemd" > DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" > > but when do_roo

Re: [OE-core] systemd

On Tuesday, July 02, 2013 09:35:20 AM Yi Qingliang wrote: > Hi, All: > > I want use systemd, add following into my own distro.conf > DISTRO_FEATURES_append = " systemd" > VIRTUAL-RUNTIME_init_manager = "systemd" > DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" > > but when do_roo

[OE-core] systemd

Hi, All: I want use systemd, add following into my own distro.conf DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" but when do_rootfs for my own image, I got error: error: package update-rc.d is not

[OE-core] systemd depends on util-linux

Hi, I have stumbled upon a build error for systemd a few times, where it fails to build due to missing blkid/blkid.h. | src/udev/udev-builtin-blkid.c:30:25: fatal error: blkid/blkid.h: No such file or directory I think this happens when systemd is built before util-linux and can be fixed with an

Re: [OE-core] systemd: /run directory not created

On 23/02/2013 1:50 AM, Jack Mitchell wrote: On 22/02/13 14:15, Jack Mitchell wrote: On 22/02/13 09:22, Jack Mitchell wrote: On 21/02/13 22:27, Khem Raj wrote: On (14/02/13 15:44), Jack Mitchell wrote: On 14/02/13 15:31, Burton, Ross wrote: On 14 February 2013 14:31, Jack Mitchell wrote: Did

Re: [OE-core] systemd: /run directory not created

On 15/04/2013 11:45 PM, Jack Mitchell wrote: On 15/04/13 14:10, Martin Jansa wrote: On Mon, Apr 15, 2013 at 01:58:52PM +0100, Jack Mitchell wrote: Ok, I have just come back to trying out the new systemd implementation, and this bug still exists. Exactly the same error as before: [2.390730

Re: [OE-core] systemd post-install failure

On 22/04/13 15:56, Burton, Ross wrote: On 22 April 2013 15:44, Jack Mitchell wrote: Ah, ok then, I don't have a /system-update. So square one, any ideas why this would have suddenly flagged up? I was building and booting fine on Wed/Thurs. That was the only useful bit of the debug log I could d

Re: [OE-core] systemd post-install failure

On 22 April 2013 15:44, Jack Mitchell wrote: > Ah, ok then, I don't have a /system-update. So square one, any ideas why > this would have suddenly flagged up? I was building and booting fine on > Wed/Thurs. That was the only useful bit of the debug log I could > determine... That log isn't massiv

Re: [OE-core] systemd post-install failure

On 22/04/13 15:40, Burton, Ross wrote: On 22 April 2013 15:13, Jack Mitchell wrote: Booting master today I had a systemd fault. Enabling debugging I captured the (attached) output. The gist of which is: So, looking into systemd-system-update-generator, it seems this is what takes card of the p

Re: [OE-core] systemd post-install failure

On 22 April 2013 15:13, Jack Mitchell wrote: > Booting master today I had a systemd fault. Enabling debugging I captured > the (attached) output. The gist of which is: > > So, looking into systemd-system-update-generator, it seems this is what > takes card of the post install scripts, which I know

[OE-core] systemd post-install failure

Booting master today I had a systemd fault. Enabling debugging I captured the (attached) output. The gist of which is: . Spawned /lib/systemd/system-generators/systemd-system-update-generator as 81 . Received SIGCHLD from PID 81 (n/a). Got SIGCHLD for process 90 (systemd-sysctl) Child

Re: [OE-core] systemd/sysvinit in the 1.4 release

On Thursday 18 April 2013 17:27:50 Yi Qingliang wrote: > Who need hybrid mode? The most reasonable use-case is for using systemd in the main root filesystem and sysvinit within a rescue/initramfs image (without having to use two separate distro configurations). Cheers, Paul -- Paul Eggleton

Re: [OE-core] systemd/sysvinit in the 1.4 release

Who need hybrid mode? On Thursday, April 18, 2013 08:29:20 AM Richard Purdie wrote: > I just wanted to be clear with people what has gone on with sysvinit and > systemd in the 1.4 release. > > Basically I took some patches recently on a trust that certain things > had been checked and it was foun

[OE-core] systemd/sysvinit in the 1.4 release

I just wanted to be clear with people what has gone on with sysvinit and systemd in the 1.4 release. Basically I took some patches recently on a trust that certain things had been checked and it was found that there were problems with the changes after they went in. At some point I have to trust

Re: [OE-core] systemd: /run directory not created

On 15/04/13 14:10, Martin Jansa wrote: On Mon, Apr 15, 2013 at 01:58:52PM +0100, Jack Mitchell wrote: Ok, I have just come back to trying out the new systemd implementation, and this bug still exists. Exactly the same error as before: [2.390730] systemd[1]: Failed to mount /run: No such fi

Re: [OE-core] systemd: /run directory not created

On Mon, Apr 15, 2013 at 01:58:52PM +0100, Jack Mitchell wrote: > Ok, I have just come back to trying out the new systemd implementation, > and this bug still exists. > > Exactly the same error as before: > > [2.390730] systemd[1]: Failed to mount /run: No such file or directory > > Can we s

Re: [OE-core] systemd: /run directory not created

Ok, I have just come back to trying out the new systemd implementation, and this bug still exists. Exactly the same error as before: [2.390730] systemd[1]: Failed to mount /run: No such file or directory Can we shed any light on why this directory is failing to be created and what can be

[OE-core] systemd postinsts failing when trying to enable masked service

We had crond.service masked to prevent crond sysvinit script being started. Now with crond.service pulled by PN (cronie) it tries to start it and fails: Configuring cronie. Failed to issue method call: Unit crond.service is masked. I guess I can disable it again with SYSTEMD_AUTO_ENABLE or keep

Re: [OE-core] systemd/sysvinit switches (was [meta-systemd][PATCH 1/2] Delete systemd class)

On Fri, Apr 12, 2013 at 11:46:16AM +0100, Burton, Ross wrote: > Hi Andreas, > > On 12 April 2013 09:56, Andreas Müller wrote: > > OK - just in case I have spare cycles to start this: I am afraid I > > lost overview regarding distro features. I found systemd and sysvinit > > which can be set both

Re: [OE-core] systemd/sysvinit switches (was [meta-systemd][PATCH 1/2] Delete systemd class)

Hi Andreas, On 12 April 2013 09:56, Andreas Müller wrote: > OK - just in case I have spare cycles to start this: I am afraid I > lost overview regarding distro features. I found systemd and sysvinit > which can be set both - still correct? > > Ross could you please link me to the information how

[OE-core] systemd/sysvinit switches (was [meta-systemd][PATCH 1/2] Delete systemd class)

On Thu, Apr 11, 2013 at 2:12 AM, Andreas Müller wrote: > On Tue, Apr 9, 2013 at 10:01 PM, Martin Jansa wrote: >> On Tue, Mar 05, 2013 at 11:59:07PM +0100, Martin Jansa wrote: >>> On Tue, Mar 05, 2013 at 11:50:41PM +0100, Andreas Müller wrote: >>> > On Tue, Mar 5, 2013 at 11:18 PM, Martin Jansa

Re: [OE-core] systemd: add python-systemd package

On Thu, Mar 28, 2013 at 03:35:48PM +0200, Yevhen Kyriukha wrote: > Hi! > > It would be great if someone add changes to systemd recipe to generate > python-systemd package ( > http://www.freedesktop.org/software/systemd/python-systemd/). See systemd recipe in meta-systemd before it was removed and

[OE-core] systemd: add python-systemd package

Hi! It would be great if someone add changes to systemd recipe to generate python-systemd package ( http://www.freedesktop.org/software/systemd/python-systemd/). Best regards, Yevhen ___ Openembedded-core mailing list Openembedded-core@lists.openembedde

[OE-core] systemd 197 not mirrored

Had this email sent to p...@yoctoproject.org but maybe this mailing list is the better place to ask. Seems there is an issue downloading systemd 197 from the SRC_URI defined in the recipe. On the other hand, the mirrors don't have version 197 of systemd, but rather only 196. Anybody else gett

Re: [OE-core] systemd-systemctl-native not pulled in when building systemd image

On 1 March 2013 09:25, Erik Botö wrote: > I'm building a small image with systemd as DISTRO_FEATURES_INITMAN and > it's also in DISTRO_FEATURES. But checking the log.do_rootfs I see > that systemctl is missing when running the postinst script of e.g. > systemd-compat-units. That's a bug in system

[OE-core] systemd-systemctl-native not pulled in when building systemd image

Hi, I'm building a small image with systemd as DISTRO_FEATURES_INITMAN and it's also in DISTRO_FEATURES. But checking the log.do_rootfs I see that systemctl is missing when running the postinst script of e.g. systemd-compat-units. If I put in DEPENDS += " systemd-systemctl-native" in my image rec

Re: [OE-core] systemd: /run directory not created

On 22/02/13 14:15, Jack Mitchell wrote: On 22/02/13 09:22, Jack Mitchell wrote: On 21/02/13 22:27, Khem Raj wrote: On (14/02/13 15:44), Jack Mitchell wrote: On 14/02/13 15:31, Burton, Ross wrote: On 14 February 2013 14:31, Jack Mitchell wrote: Did this ever go anywhere? I have just tried aga

Re: [OE-core] systemd: /run directory not created

On 22/02/13 09:22, Jack Mitchell wrote: On 21/02/13 22:27, Khem Raj wrote: On (14/02/13 15:44), Jack Mitchell wrote: On 14/02/13 15:31, Burton, Ross wrote: On 14 February 2013 14:31, Jack Mitchell wrote: Did this ever go anywhere? I have just tried again today with exactly the same result, a

Re: [OE-core] systemd: /run directory not created

On 21/02/13 22:27, Khem Raj wrote: On (14/02/13 15:44), Jack Mitchell wrote: On 14/02/13 15:31, Burton, Ross wrote: On 14 February 2013 14:31, Jack Mitchell wrote: Did this ever go anywhere? I have just tried again today with exactly the same result, all I did was change the DISTRO_FEATURES_I

Re: [OE-core] systemd: /run directory not created

On (14/02/13 15:44), Jack Mitchell wrote: > On 14/02/13 15:31, Burton, Ross wrote: > >On 14 February 2013 14:31, Jack Mitchell wrote: > >>Did this ever go anywhere? I have just tried again today with exactly the > >>same result, all I did was change the DISTRO_FEATURES_INITMAN to systemd. > >Odd,

Re: [OE-core] systemd: /run directory not created

On 02/14/13 15:57, Jack Mitchell wrote: On 14/02/13 15:44, Jack Mitchell wrote: On 14/02/13 15:31, Burton, Ross wrote: On 14 February 2013 14:31, Jack Mitchell wrote: Did this ever go anywhere? I have just tried again today with exactly the same result, all I did was change the DISTRO_FEATURE

Re: [OE-core] systemd: /run directory not created

On 14/02/13 15:44, Jack Mitchell wrote: On 14/02/13 15:31, Burton, Ross wrote: On 14 February 2013 14:31, Jack Mitchell wrote: Did this ever go anywhere? I have just tried again today with exactly the same result, all I did was change the DISTRO_FEATURES_INITMAN to systemd. Odd, as I just bu

Re: [OE-core] systemd: /run directory not created

On 14/02/13 15:31, Burton, Ross wrote: On 14 February 2013 14:31, Jack Mitchell wrote: Did this ever go anywhere? I have just tried again today with exactly the same result, all I did was change the DISTRO_FEATURES_INITMAN to systemd. Odd, as I just built and booted a systemd image (core-image

Re: [OE-core] systemd: /run directory not created

On 14 February 2013 14:31, Jack Mitchell wrote: > Did this ever go anywhere? I have just tried again today with exactly the > same result, all I did was change the DISTRO_FEATURES_INITMAN to systemd. Odd, as I just built and booted a systemd image (core-image-sato, in poky master), and it worked

Re: [OE-core] systemd services in the rootfs

On 14 February 2013 12:32, Florin Sarbu wrote: > So choosing, for example ${PN} to hold the systemd services, and also choose > to use sysvinit as the init manager, then I'd end up with a rootfs > containing useless systemd services. That would be a packaging bug. The systemd class only does wor

Re: [OE-core] systemd: /run directory not created

On 25/01/13 08:28, Radu Moisan wrote: On 01/24/2013 04:52 PM, Burton, Ross wrote: On 24 January 2013 13:03, Radu Moisan wrote: ok, thanks Enrico, this clears the picture for me. Well then it looks like Jack's problems is coming from some other place. No - /run needs to exist for the mount t

Re: [OE-core] systemd services in the rootfs

e files into the relevant package (i.e. $PN, instead of into a separate package of their own. This is different to how meta-systemd worked, because in oe-core systemd is a DISTRO_FEATURE and not something you can decide at image construction time. Ross

Re: [OE-core] systemd services in the rootfs

hem in the rootfs, but > rather to have them added in the do_rootfs stage. Put the service files into the relevant package (i.e. $PN, instead of into a separate package of their own. This is different to how meta-systemd worked, because in oe-core systemd is a DISTRO_FEATURE and not

Re: [OE-core] systemd services in the rootfs

The issue I was referring to was that the individual packages (that contain the systemd service files) generated from various recipes, do not end up in the rootfs solely by having them declared in the SYSTEMD_PACKAGES and having DISTRO_FEATURES_INITMAN ="systemd". You need now to explicitly add

Re: [OE-core] systemd services in the rootfs

On 02/13/2013 05:33 PM, Florin Sarbu wrote: Hi all, following the transition of the systemd.bbclass from meta-openembedded to oe-core, I stumbled upon on what seems to me a missing feature that has not been brought along in the new systemd.bbclass in oe-core. Seems that if one does not explic

[OE-core] systemd services in the rootfs

Hi all, following the transition of the systemd.bbclass from meta-openembedded to oe-core, I stumbled upon on what seems to me a missing feature that has not been brought along in the new systemd.bbclass in oe-core. Seems that if one does not explicitly specify the inclusion of the packages co

Re: [OE-core] systemd: /run directory not created

On 01/24/2013 04:52 PM, Burton, Ross wrote: On 24 January 2013 13:03, Radu Moisan wrote: ok, thanks Enrico, this clears the picture for me. Well then it looks like Jack's problems is coming from some other place. No - /run needs to exist for the mount to happen, and there isn't a /run in the

Re: [OE-core] systemd: /run directory not created

On 24 January 2013 13:03, Radu Moisan wrote: > ok, thanks Enrico, this clears the picture for me. > Well then it looks like Jack's problems is coming from some other place. No - /run needs to exist for the mount to happen, and there isn't a /run in the filesystem. Whatever creates the root files

Re: [OE-core] systemd: /run directory not created

On 01/24/2013 02:53 PM, Enrico Scholz wrote: Radu Moisan writes: /run is part of systemd's api and mounted very early internally by systemd. This mountpoint must exist in the filesystem and it will probably not work when it is symlink into /var/volatile which gets mounted later. Isn't syste

Re: [OE-core] systemd: /run directory not created

Radu Moisan writes: >> /run is part of systemd's api and mounted very early internally by >> systemd. This mountpoint must exist in the filesystem and it will >> probably not work when it is symlink into /var/volatile which gets >> mounted later. > > Isn't systemd looking into fstab.systemd for

Re: [OE-core] systemd: /run directory not created

On 01/24/2013 02:20 PM, Enrico Scholz wrote: Radu Moisan writes: Possibly because /run was a link created by the initscripts which are now disabled when systemd is the init manager. I'll look into this and update 00-create-volatile.conf so that systemd will handle the link creation in stead.

Re: [OE-core] systemd: /run directory not created

Radu Moisan writes: >>> Possibly because /run was a link created by the initscripts which >>> are now disabled when systemd is the init manager. I'll look into >>> this and update 00-create-volatile.conf so that systemd will handle >>> the link creation in stead. >> I wonder how my images booted.

Re: [OE-core] systemd: /run directory not created

On 24 January 2013 12:11, Radu Moisan wrote: > This is exactly what I was looking for. /run shouldn't be there, yet somehow > it is. I was looking into how/where systemd is creating /run but no lead for > now. As far as I'm aware systemd will mount a tmpfs on /run itself on startup, but the direc

Re: [OE-core] systemd: /run directory not created

On 01/24/2013 02:01 PM, Burton, Ross wrote: On 24 January 2013 09:46, Radu Moisan wrote: Possibly because /run was a link created by the initscripts which are now disabled when systemd is the init manager. I'll look into this and update 00-create-volatile.conf so that systemd will handle the l

Re: [OE-core] systemd: /run directory not created

On 24 January 2013 09:46, Radu Moisan wrote: > Possibly because /run was a link created by the initscripts which are now > disabled when systemd is the init manager. I'll look into this and update > 00-create-volatile.conf so that systemd will handle the link creation in > stead. I wonder how my

Re: [OE-core] systemd: /run directory not created

On 01/23/2013 05:19 PM, Jack Mitchell wrote: When I attempt to boot a systemd enabled image I get an error stating that the run directory could not be mounted as it doesn't exist. I checked the target rootfs and there isn't a /run directory. What is responsible for creating this and why is it n

[OE-core] systemd: /run directory not created

When I attempt to boot a systemd enabled image I get an error stating that the run directory could not be mounted as it doesn't exist. I checked the target rootfs and there isn't a /run directory. What is responsible for creating this and why is it not doing it's job? [ 2.631549] systemd[1]: F

Re: [OE-core] systemd

On 14 December 2012 13:12, Yevhen Kyriukha wrote: > Is there any way to use systemd for starting system services in yocto v1.3? Use meta-systemd from meta-openembedded. Ross ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org h

[OE-core] systemd

Hi! Is there any way to use systemd for starting system services in yocto v1.3? -- Best regards, Yevhen ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: [OE-core] Systemd fails

On Mon, Oct 8, 2012 at 7:05 PM, Burton, Ross wrote: > On 8 October 2012 16:45, Andrei Gherzan wrote: > > > tmp-eglibc-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/systemd-git-r7/git/src/journal/journal-verify.c:69: > > undefined reference to `uncompress_blob' > > See [oe] [meta-systemd][PATCH] s

  1   2   >