Enabling SystemD

Enabling SystemD

[Patrick K.]

Hi there,

I just wanted to ask if it is normal, that when using a example-image 
like "fsl-image-test" with "SystemD" enabled, that I always have 
manually modify the kernel to make it booting properly?

Does anybody has some experience with using "SystemD" as 
startup-manager? I disabled sysvinit completely as stated in the 
yocto-manual.

What I need to add in my kernel configuration to make it work is:

CONFIG_CGROUPS
+
CONFIG_FHANDLE

Any thoughts about this. Could someone add this as patch, so that I 
don't have to add it manually everytime I rebuild an image?

Thanks in advance.

Kind Regards
Patrick

Re: Enabling SystemD

[Otavio Salvador]

Hello Patrick,

On Sat, Feb 8, 2014 at 9:23 AM, Patrick K. <trancefusion@gno.de> wrote:
> I just wanted to ask if it is normal, that when using a example-image like
> "fsl-image-test" with "SystemD" enabled, that I always have manually modify
> the kernel to make it booting properly?
>
> Does anybody has some experience with using "SystemD" as startup-manager? I
> disabled sysvinit completely as stated in the yocto-manual.
>
> What I need to add in my kernel configuration to make it work is:
>
> CONFIG_CGROUPS
> +
> CONFIG_FHANDLE
>
> Any thoughts about this. Could someone add this as patch, so that I don't
> have to add it manually everytime I rebuild an image?

We are certainly open to apply a patch adding it; please send a patch
enabling it and we review.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Enabling SystemD

[Pat Key]

[-- Attachment #1.1: Type: text/plain, Size: 3446 bytes --]

Hi,

attached is a already reviewed patch by Otavio. Please review officially
review it and send it back to Otavio for commit into the tree.

Thank you.

Kind Regards
Patrick


---------- Forwarded message ----------
From: Otavio Salvador <otavio@ossystems.com.br>
Date: 2014-02-12 15:16 GMT+01:00
Subject: Re: [meta-freescale] Enabling SystemD
To: Pat Key <crymeariver33@gmail.com>


Please send this to the mailing list.

On Mon, Feb 10, 2014 at 7:07 PM, Pat Key <crymeariver33@gmail.com> wrote:
> Here we go.
>
> Have a nice evening :-).
>
>
>
>
> 2014-02-10 22:02 GMT+01:00 Pat Key <crymeariver33@gmail.com>:
>
>> Ok thanks.
>>
>> I will try it.
>>
>>
>> 2014-02-10 22:01 GMT+01:00 Otavio Salvador <otavio@ossystems.com.br>:
>>
>>> It is:
>>>
>>> http://git-scm.com/book/en/Customizing-Git-Git-Configuration
>>>
>>> On Mon, Feb 10, 2014 at 7:01 PM, Pat Key <crymeariver33@gmail.com>
wrote:
>>> > But this depends on the name I choosed in Git. He automatically adds
>>> > this to
>>> > the patch.
>>> >
>>> > I don't know if it's possible to change my nickname from Soily to my
>>> > real
>>> > name?
>>> >
>>> >
>>> > 2014-02-10 21:59 GMT+01:00 Otavio Salvador <otavio@ossystems.com.br>:
>>> >
>>> >> 98%.
>>> >>
>>> >> Author:    Patrick Keil <trancefusion@gno.de>
>>> >> Signed-off-by: Soily <trancefusion@gno.de>
>>> >>
>>> >> This is wrong.
>>> >>
>>> >> Signed-off-by: Patrick Keil <trancefusion@gno.de>
>>> >>
>>> >> Is the wished one.
>>> >>
>>> >>
>>> >> On Mon, Feb 10, 2014 at 6:57 PM, Pat Key <crymeariver33@gmail.com>
>>> >> wrote:
>>> >> > Ahh I see, :-)
>>> >> >
>>> >> > thanks for the input.
>>> >> >
>>> >> > I hope now everything is fine.
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > 2014-02-10 21:43 GMT+01:00 Otavio Salvador
>>> >> > <otavio@ossystems.com.br>:
>>> >> >
>>> >> >> Hello Pat,
>>> >> >>
>>> >> >> On Mon, Feb 10, 2014 at 6:34 PM, Pat Key <crymeariver33@gmail.com>
>>> >> >> wrote:
>>> >> >> > Hello Otavio,
>>> >> >> >
>>> >> >> > I don't get it exactly.
>>> >> >> >
>>> >> >> > Why is the name wrong? You mean the filename?
>>> >> >> >
>>> >> >> > I created another one. Is it ok now?
>>> >> >>
>>> >> >> 95% :)
>>> >> >>
>>> >> >> Your name is wrong; check the from line. Please configure your
name
>>> >> >> right in the Git and use:
>>> >> >>
>>> >> >> git commit --amend --author="Your Full Name <your@email.address>"
>>> >> >>
>>> >> >> to fix it.
>>> >> >>
>>> >> >> --
>>> >> >> Otavio Salvador                             O.S. Systems
>>> >> >> http://www.ossystems.com.br        http://code.ossystems.com.br
>>> >> >> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>>> >> >
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Otavio Salvador                             O.S. Systems
>>> >> http://www.ossystems.com.br        http://code.ossystems.com.br
>>> >> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Otavio Salvador                             O.S. Systems
>>> http://www.ossystems.com.br        http://code.ossystems.com.br
>>> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>>
>>
>



--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

[-- Attachment #1.2: Type: text/html, Size: 7446 bytes --]

[-- Attachment #2: 0001-linux-wandboard-3.0.35-Add-kernel-configs-for-System.patch --]
[-- Type: text/x-patch, Size: 1028 bytes --]

From f685ef76950b9911bbd9c09df165344a8abf7398 Mon Sep 17 00:00:00 2001
From: Patrick Keil <trancefusion@gno.de>
Date: Mon, 10 Feb 2014 22:05:46 +0100
Subject: [meta-fsl-arm-extra][PATCH] linux-wandboard-3.0.35: Add kernel
 configs for Systemd

Adding missing kernel configurations for Systemd:
* CONFIG_FHANDLE
* CONFIG_CGROUPS

Signed-off-by: Patrick Keil <trancefusion@gno.de>
---
 .../linux/linux-wandboard-3.0.35/defconfig         |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-kernel/linux/linux-wandboard-3.0.35/defconfig b/recipes-kernel/linux/linux-wandboard-3.0.35/defconfig
index ce3eb77..dae399a 100644
--- a/recipes-kernel/linux/linux-wandboard-3.0.35/defconfig
+++ b/recipes-kernel/linux/linux-wandboard-3.0.35/defconfig
@@ -3,7 +3,9 @@ CONFIG_LOCALVERSION="-wandboard+yocto"
 CONFIG_DEFAULT_HOSTNAME="wandboard"
 # CONFIG_SWAP is not set
 CONFIG_SYSVIPC=y
+CONFIG_FHANDLE=y
 CONFIG_LOG_BUF_SHIFT=14
+CONFIG_CGROUPS=y
 CONFIG_BLK_DEV_INITRD=y
 CONFIG_EMBEDDED=y
 CONFIG_PERF_EVENTS=y
-- 
1.7.9.5

Re: Enabling SystemD

[John Weber]

[-- Attachment #1: Type: text/html, Size: 15417 bytes --]

Re: Enabling SystemD

[Eric Nelson]

Hi Patrick,

On 02/08/2014 04:23 AM, Patrick K. wrote:
> Hi there,
>
> I just wanted to ask if it is normal, that when using a example-image
> like "fsl-image-test" with "SystemD" enabled, that I always have
> manually modify the kernel to make it booting properly?
>
> Does anybody has some experience with using "SystemD" as
> startup-manager? I disabled sysvinit completely as stated in the
> yocto-manual.
>
> What I need to add in my kernel configuration to make it work is:
>
> CONFIG_CGROUPS
> +
> CONFIG_FHANDLE
>
> Any thoughts about this. Could someone add this as patch, so that I
> don't have to add it manually everytime I rebuild an image?
>

Thanks for the ping on this.

If a patch is added, perhaps the remainder of the suggested
kernel configuration items should be added though:
	http://cgit.freedesktop.org/systemd/systemd/tree/README

We're testing a set of patches on our kernel to this end, and
there don't appear to be any regressions:
	https://github.com/boundarydevices/linux-imx6/commit/d6cdf387e5ea0af8181e3f74d6a5d4a69da466b6

Regards,


Eric

Re: Enabling SystemD

[Otavio Salvador]

Hello Eric,

On Sun, Feb 9, 2014 at 11:27 AM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 02/08/2014 04:23 AM, Patrick K. wrote:
>>
>> Hi there,
>>
>> I just wanted to ask if it is normal, that when using a example-image
>> like "fsl-image-test" with "SystemD" enabled, that I always have
>> manually modify the kernel to make it booting properly?
>>
>> Does anybody has some experience with using "SystemD" as
>> startup-manager? I disabled sysvinit completely as stated in the
>> yocto-manual.
>>
>> What I need to add in my kernel configuration to make it work is:
>>
>> CONFIG_CGROUPS
>> +
>> CONFIG_FHANDLE
>>
>> Any thoughts about this. Could someone add this as patch, so that I
>> don't have to add it manually everytime I rebuild an image?
>>
>
> Thanks for the ping on this.
>
> If a patch is added, perhaps the remainder of the suggested
> kernel configuration items should be added though:
>         http://cgit.freedesktop.org/systemd/systemd/tree/README
>
> We're testing a set of patches on our kernel to this end, and
> there don't appear to be any regressions:
>
> https://github.com/boundarydevices/linux-imx6/commit/d6cdf387e5ea0af8181e3f74d6a5d4a69da466b6

From our experience with customers we had no problems with 3.0.35 and
3.10 kernels with systemd. We known problems with 2.6.35.3 (used by
MX28 e MX53) about instability and it fails badly to boot from time to
time (kernel oops). I think this is safe to include.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Enabling SystemD

[Eric Nelson]

On 02/09/2014 06:57 AM, Otavio Salvador wrote:
> Hello Eric,
>
> On Sun, Feb 9, 2014 at 11:27 AM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
 >> ...
 >>
>> If a patch is added, perhaps the remainder of the suggested
>> kernel configuration items should be added though:
>>          http://cgit.freedesktop.org/systemd/systemd/tree/README
>>
>> We're testing a set of patches on our kernel to this end, and
>> there don't appear to be any regressions:
>>
>> https://github.com/boundarydevices/linux-imx6/commit/d6cdf387e5ea0af8181e3f74d6a5d4a69da466b6
>
>  From our experience with customers we had no problems with 3.0.35 and
> 3.10 kernels with systemd. We known problems with 2.6.35.3 (used by
> MX28 e MX53) about instability and it fails badly to boot from time to
> time (kernel oops). I think this is safe to include.
>

Thanks Otavio.