From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 081A4E00A08; Wed, 18 Jan 2017 07:10:30 -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.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [212.227.126.133 listed in dnsbl.sorbs.net] * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [212.227.126.133 listed in list.dnswl.org] * -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.133]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 238E1E00A03 for ; Wed, 18 Jan 2017 07:10:26 -0800 (PST) Received: from LNSYSCH3 ([81.130.69.98]) by mrelayeu.kundenserver.de (mreue005 [212.227.15.163]) with ESMTPSA (Nemesis) id 0M6heq-1cfuaa3CBI-00wVew for ; Wed, 18 Jan 2017 16:10:24 +0100 From: To: Date: Wed, 18 Jan 2017 15:10:23 -0000 Organization: LN Systems Limited Message-ID: <049201d2719c$fea9e670$fbfdb350$@ln-systems.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdJxm76r42G/wrCZRhaTKOOUulQQTA== X-Provags-ID: V03:K0:wIkGo3QE6g/NYr8HRZ2m8qKpAnw4HwU3LNzmmt8LkZ6qVHvd14v cdOCu4bL7imygKiZ0/BJFlA2ckZzwoPwU+GJWpxMsWJ1/KXGRxa1YPGnGKSjr8EGc0i/hnJ vub9+sb44CwfsEHj/uI2Pt9olQdhCkD6n7zdEeqT0LeD5gvtuoWbrqws+zVnk6nEbU39lrc B6gEOo3Uy3SJMJ6ScVweQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:tqwyGhVYTqY=:5dnaiotQw76sFrxVVGErhs TAzrqL2mEzl2C1T281hXv074fQSPNYmN66UbZ5NSmmHIiUas46mhE5oKjUT7NHgzi9YSs2iE/ nxZGYYcLt3K+4kzbn3AI31mUfxuuV40OjK3nVq+jhPA0LoenPBOfo5iTzWwiPY/C8/dV77QOM H0zEOXmLMEGYjOMe3yJ5OmD35fxvmGqhvMhwLRKpoObTEX5erl1M8N47kAg7VBBkTJViaagaa vbQTHNTSFqCo2jMm/QXU6tHba5pxHhJVzoxEcYmGe3ciQc8UdCCwhZlvGZ7w8qPGZfdrb2yMC PcIBZ306T7iQ9HCvTNCOl/ngpcQ+72gxmcOTyCE5NAsu4QhNrziq3TpeUIV1eth+U2fWtOtXc KJZwwSc92+UiP2NjMog/vJf3UgTorRG3m2neQuR4sBTEt3+Y8gBI8aa9NoVPffnVdTBaKaEvM nmuwcIQ8IRIVVQEhChh1y1/J76rMxuQHMDkxy0Mq28/CpDwazCq7rH/8xJDyKvl9bSzxEMxl1 1xPMeM0SFeopuIOTMVOSjkfbAidSZ2mIimXoIlK3ha1/9Q/TGefYN0KdFE4x1YmEaxZG/Sofi O+n0EPBUnsm4RwXcGkgESuitGDzKaqwuX3xqJisRwaU8de5F7F+rYkxJ4+uSMqweidJ5Lu3/z Zr7Imw1/MqL4ydoS2F/h/wzxIop4KLTHEyUYRFSiCDMYppoczoSs4idKO+Y0AJfe3bw6Z5Txf 9Umy0lJIlEPfH5xI Subject: 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: Wed, 18 Jan 2017 15:10:30 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0493_01D2719C.FEAC3060" Content-Language: en-gb ------=_NextPart_000_0493_01D2719C.FEAC3060 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit We have a configuration for our embedded system which is working via SysV, but we're investigating moving over to systemd. Not sure if this is 'wise' - if anyone has technological arguments for/against then I'd be interested - but I wanted to investigate it anyway. I've modified local.conf (right or wrong) with DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" VIRTUAL-RUNTIME_initscripts = "" KERNEL_ENABLE_CGROUPS = "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 ('ifconfig eth0'), there doesn't seem to be any dhcp happening - no IP etc. Previously (under SysV) I had the busybox dhcp client; now it seems that is missing. There's a symlink /etc/systemd/system/busybox-udhcpc.service to /dev/null I'm using Poky Jethro Kernel 4.4.0 Busybox 1.23.2 (with 'CONFIG_FEATURE_SYSTEMD=y') I wondered if this is just a simple switch I'm missing somewhere, or is there a whole load more modifications I need to dig into and hand-craft? (Was hoping for something 'out of the box'..) Thanks ------=_NextPart_000_0493_01D2719C.FEAC3060 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

We have a configuration for our embedded system which = is working via SysV, but we’re investigating moving over to = systemd.

Not sure if this is = ‘wise’ – if anyone has technological arguments = for/against then I’d be interested – but I wanted to = investigate it anyway.

 

I’ve = 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 (‘ifconfig eth0’), there doesn’t seem to be any = dhcp happening – no IP etc.

Previously (under SysV) I had the busybox dhcp client; = now it seems that is missing. There’s a symlink = /etc/systemd/system/busybox-udhcpc.service to /dev/null

I’m using

  Poky Jethro

  Kernel 4.4.0

  Busybox 1.23.2 (with = ‘CONFIG_FEATURE_SYSTEMD=3Dy’)

 

I wondered = if this is just a simple switch I’m missing somewhere, or is there = a whole load more modifications I need to dig into and hand-craft? (Was = hoping for something ‘out of the = box’….)

 

Thanks

 

------=_NextPart_000_0493_01D2719C.FEAC3060--