From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 3778EE009D7; Wed, 18 Jan 2017 23:21:44 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [212.227.126.131 listed in list.dnswl.org] * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [212.227.126.131 listed in dnsbl.sorbs.net] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id A8A94E009CF for ; Wed, 18 Jan 2017 23:21:42 -0800 (PST) Received: from LNSYSCH3 ([81.130.69.98]) by mrelayeu.kundenserver.de (mreue003 [212.227.15.163]) with ESMTPSA (Nemesis) id 0LiYwK-1byLex2wiC-00cgFJ; Thu, 19 Jan 2017 08:21:39 +0100 From: To: "'Rick Altherr'" , "'Andre McCurdy'" References: <049201d2719c$fea9e670$fbfdb350$@ln-systems.com> In-Reply-To: Date: Thu, 19 Jan 2017 07:21:38 -0000 Organization: LN Systems Limited Message-ID: <060101d27224$ad344a00$079cde00$@ln-systems.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQHftmx71IEooMCGrNMDnT4mUuYiOAMHaxycAYiQnzWhAFwSYA== X-Provags-ID: V03:K0:07lwYNBR+ZcPA5xvm708g8eTAB+amvRBeb6+SjvtFUjousOkOKs +GdbNFW9S3TvGdxDpKsfDxsbwZrpsWKPVSAbc7Z0XFCau9bBcNefWLwdhlM14jD5pNk4Gvx 5x9QZGRFFAF3HNfOc+AN6r46rBzqsk3sSDStYVqn4HIPDJRdl7nIDoBwzMrO1sRMJPgPNdm ujJCIC3xAJLbmHHgOXFfw== X-UI-Out-Filterresults: notjunk:1;V01:K0:66K0TbHuCX0=:biBNsTYjyORWAL82SektqA PFI/ki2wNaU+IwUhJc1PCIBzEfldMmhFr1gprMp5iUJ5edAE3igbRo+KIZIk4GquxAOPA+lNX wCnICcpyYFHbbSs1FfNx5sdVWoT20xDDQ3+LsEEu7Ts52oymR3unZDfRYYgEqwGPLahkrtJa8 N0RgRN6R49A1wEvCEY4H+IKavC7jLtRPn+YhGaS8Y+fBAylPgE23Yo0bsipn30cR6Nf05jQQQ SmIYPkeTgXxjZKI2ZxlRb0mDL021nS5zWD1pU31f6sp+Xtt0m362t6ZckStNnenmangghfImV aEsuTdEOqDt4U0DNIdNDlgbhINwQca467tFmacPuiGh9aSoLTIfUzuaV936lyJqrStaXL2pfO hH86kzmU/lUOjHcCs4rsjUbnb3FICqrEviPg4Xt3rzwtIb5FlNAPergVfPsTKuLPDdhDtEY1e pMNQchFg5PYeGKOM5mBjqshPDtmKhYx3wnAShzqMSQU9J8LdY9tbuDZPcrg0Gv58KRfSvm8mS u+b85BffthjEZS7CHBgYDQj8C2dP9MZjdVU0VcPsGL9JfBiFCJvk2UQmKVQz3kXsI083Po45c 8aLr4Iud1cdBLAA7INzU5tNaien5R8ACudUt9XH7iT8jAdWhK46tWOD6herZOe9XGCcothpFX +PtQU7DIy2E9RNWgdKElnq+r2LbkR8TDN/Lg9uytbnSNeZHu9hKK64kYL80u9qw2jKPa6xTf0 ZNgDjCIn6z20IS7v Cc: 'Yocto discussion list' Subject: Re: Changing over to systemd (no dhcp) X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: colin.helliwell@ln-systems.com List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2017 07:21:44 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0602_01D27224.AD392C00" Content-Language: en-gb ------=_NextPart_000_0602_01D27224.AD392C00 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Yes, I=E2=80=99d agree with that, Rick. We run automated regression builds from a fresh version control checkout = =E2=80=93 but because local.conf is generated when the build environment = is set up, it isn=E2=80=99t suitable for version control. So any mods to = it found during development have to be (remembered to be) put into = local.conf.sample, so that the same build is assured for anyone = anywhere. I=E2=80=99ve long felt/assumed that local.conf was for truly local mods, = for that user and/or for their temporary try-outs. Similarly =E2=80=93 and this is going even more off-topic so = I=E2=80=99ll save the detail for a separate thread =E2=80=93 = I=E2=80=99ve still not yet got to grips with whether, when I want to add = a particular package, I should be modifying my image recipe or set up a = custom distro) =20 From: Rick Altherr [mailto:raltherr@google.com]=20 Sent: 19 January 2017 00:22 To: Andre McCurdy Cc: colin.helliwell@ln-systems.com; Yocto discussion list = Subject: Re: [yocto] Changing over to systemd (no dhcp) =20 I was wondering about this recently. Why are these snippets put in = local.conf.sample.extended instead of separate, well-named .inc files = that can be shared by multiple distros? The current model seems to = encourage putting lots of configuration in local.conf that probably = should be in the distro or machine conf. =20 Rick =20 On Wed, Jan 18, 2017 at 1:35 PM, Andre McCurdy > wrote: On Wed, Jan 18, 2017 at 7:10 AM, > wrote: > We have a configuration for our embedded system which is working via = SysV, > but we=E2=80=99re investigating moving over to systemd. > > Not sure if this is =E2=80=98wise=E2=80=99 =E2=80=93 if anyone has = technological arguments > for/against then I=E2=80=99d be interested =E2=80=93 but I wanted to = investigate it anyway. > > I=E2=80=99ve modified local.conf (right or wrong) with > > DISTRO_FEATURES_append =3D " systemd" > VIRTUAL-RUNTIME_init_manager =3D "systemd" > DISTRO_FEATURES_BACKFILL_CONSIDERED =3D "sysvinit" > VIRTUAL-RUNTIME_initscripts =3D "" > KERNEL_ENABLE_CGROUPS =3D "1" > > I also found a readme > (https://cgit.freedesktop.org/systemd/systemd/tree/README#n37) about = the > kernel requirements for systemd, and it does at least now boot. > > However although eth0 is coming up (=E2=80=98ifconfig eth0=E2=80=99), = there doesn=E2=80=99t seem to > be any dhcp happening =E2=80=93 no IP etc. > > Previously (under SysV) I had the busybox dhcp client; now it seems = that is > missing. There=E2=80=99s a symlink = /etc/systemd/system/busybox-udhcpc.service to > /dev/null > > I=E2=80=99m using > > Poky Jethro > Kernel 4.4.0 > Busybox 1.23.2 (with =E2=80=98CONFIG_FEATURE_SYSTEMD=3Dy=E2=80=99) > > I wondered if this is just a simple switch I=E2=80=99m missing = somewhere, or is > there a whole load more modifications I need to dig into and = hand-craft? > (Was hoping for something =E2=80=98out of the box=E2=80=99=E2=80=A6.) Try: VIRTUAL-RUNTIME_initscripts =3D "systemd-compat-units" Enabling systemd is somewhat documented by the example in {meta-poky,openembedded-core/meta}/conf/local.conf.sample.extended, which is: # # Use systemd for system initialization # # DISTRO_FEATURES_append =3D " systemd" # DISTRO_FEATURES_BACKFILL_CONSIDERED +=3D "sysvinit" # VIRTUAL-RUNTIME_init_manager =3D "systemd" # VIRTUAL-RUNTIME_initscripts =3D "systemd-compat-units" -- _______________________________________________ yocto mailing list yocto@yoctoproject.org =20 https://lists.yoctoproject.org/listinfo/yocto =20 ------=_NextPart_000_0602_01D27224.AD392C00 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Yes, I=E2=80=99d agree with that, = Rick.

We run automated regression builds from a = fresh version control checkout =E2=80=93 but because local.conf is = generated when the build environment is set up, it isn=E2=80=99t = suitable for version control. So any mods to it found during development = have to be (remembered to be) put into local.conf.sample, so that the = same build is assured for anyone anywhere.

I=E2=80=99ve long felt/assumed that = local.conf was for truly local mods, for that user and/or for their = temporary try-outs.

Similarly =E2=80=93 and this is going even = more off-topic so I=E2=80=99ll save the detail for a separate thread = =E2=80=93 I=E2=80=99ve still not yet got to grips with whether, when I = want to add a particular package, I should be modifying my image recipe = or set up a custom distro)

 

From:<= /b> Rick = Altherr [mailto:raltherr@google.com]
Sent: 19 January 2017 = 00:22
To: Andre McCurdy = <armccurdy@gmail.com>
Cc: = colin.helliwell@ln-systems.com; Yocto discussion list = <yocto@yoctoproject.org>
Subject: Re: [yocto] Changing = over to systemd (no dhcp)

 

I was = wondering about this recently.  Why are these snippets put in = local.conf.sample.extended instead of separate, well-named .inc files = that can be shared by multiple distros?  The current model seems to = encourage putting lots of configuration in local.conf that probably = should be in the distro or machine conf.

 

Rick

 

On Wed, = Jan 18, 2017 at 1:35 PM, Andre McCurdy <armccurdy@gmail.com> = wrote:

On Wed, = Jan 18, 2017 at 7:10 AM,  <colin.helliwell@ln-systems= .com> wrote:

> We have a configuration for our = embedded system which is working via SysV,
> but we=E2=80=99re = investigating moving over to systemd.
>
> Not sure if this = is =E2=80=98wise=E2=80=99 =E2=80=93 if anyone has technological = arguments
> for/against then I=E2=80=99d be interested =E2=80=93 = but I wanted to investigate it anyway.
>
> I=E2=80=99ve = modified local.conf (right or wrong) with
>
>  =  DISTRO_FEATURES_append =3D " systemd"
>  =  VIRTUAL-RUNTIME_init_manager =3D "systemd"
>  =  DISTRO_FEATURES_BACKFILL_CONSIDERED =3D = "sysvinit"
>   VIRTUAL-RUNTIME_initscripts =3D = ""
>   KERNEL_ENABLE_CGROUPS =3D = "1"
>
> I also found a readme
> (https://cgit.freedesktop.org/systemd/systemd/tree/READM= E#n37) about the
> kernel requirements for systemd, and it = does at least now boot.
>
> However although eth0 is coming = up (=E2=80=98ifconfig eth0=E2=80=99), there doesn=E2=80=99t seem = to
> be any dhcp happening =E2=80=93 no IP etc.
>
> = Previously (under SysV) I had the busybox dhcp client; now it seems that = is
> missing. There=E2=80=99s a symlink = /etc/systemd/system/busybox-udhcpc.service to
> = /dev/null
>
> I=E2=80=99m using
>
>  =  Poky Jethro
>   Kernel 4.4.0
>  =  Busybox 1.23.2 (with = =E2=80=98CONFIG_FEATURE_SYSTEMD=3Dy=E2=80=99)
>
> I wondered = if this is just a simple switch I=E2=80=99m missing somewhere, or = is
> there a whole load more modifications I need to dig into and = hand-craft?
> (Was hoping for something =E2=80=98out of the = box=E2=80=99=E2=80=A6.)

Try:

  VIRTUAL-RUNTIME_initscripts =3D = "systemd-compat-units"

Enabling systemd is somewhat = documented by the example = in
{meta-poky,openembedded-core/meta}/conf/local.conf.sample.extended,=
which is:

#
# Use systemd for system = initialization
#
# DISTRO_FEATURES_append =3D " = systemd"
# DISTRO_FEATURES_BACKFILL_CONSIDERED +=3D = "sysvinit"
# VIRTUAL-RUNTIME_init_manager =3D = "systemd"
# VIRTUAL-RUNTIME_initscripts =3D = "systemd-compat-units"

--
_______________________________________________yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto<= /o:p>

 

------=_NextPart_000_0602_01D27224.AD392C00--