From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 568A2E00952; Mon, 20 Apr 2015 14:51:26 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [147.11.146.13 listed in list.dnswl.org] Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id EB495E0079F for ; Mon, 20 Apr 2015 14:51:21 -0700 (PDT) Received: from ALA-HCB.corp.ad.wrs.com (ala-hcb.corp.ad.wrs.com [147.11.189.41]) by mail1.windriver.com (8.14.9/8.14.9) with ESMTP id t3KLpED1024563 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 20 Apr 2015 14:51:15 -0700 (PDT) Received: from [128.224.22.111] (128.224.22.111) by ALA-HCB.corp.ad.wrs.com (147.11.189.41) with Microsoft SMTP Server id 14.3.224.2; Mon, 20 Apr 2015 14:51:06 -0700 Message-ID: <553574AD.7030404@windriver.com> Date: Mon, 20 Apr 2015 17:50:37 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Matt Schuckmann , Yocto Project References: <4B07ADD556F70043925DA2E9C5D4346D2FDCA585B2@MSXBEBVT12.planar.net> <20150420084300.GC11779@ad.chargestorm.se> <5535128C.6010701@windriver.com> <4B07ADD556F70043925DA2E9C5D4346D2FDCA586B4@MSXBEBVT12.planar.net> In-Reply-To: <4B07ADD556F70043925DA2E9C5D4346D2FDCA586B4@MSXBEBVT12.planar.net> Subject: Re: Problems enabling systemd X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2015 21:51:26 -0000 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit On 04/20/2015 02:06 PM, Matt Schuckmann wrote: > > >> -----Original Message----- >> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] >> Sent: Monday, April 20, 2015 7:52 AM >> To: Matt Schuckmann; Yocto Project >> Subject: Re: [yocto] Problems enabling systemd >> >> On 04/20/2015 04:43 AM, Anders Darander wrote: >>> * Matt Schuckmann [150417 23:27]: >>>> I've got an image for a AM3352 system based on Dylan and Arago and >>>> I'm trying to switch to systemd for init. >>> >>>> So far I haven't had much luck. >>>> First off I'm getting different results depending on where I turn it >> on. >>>> I'm turning it on via the following 2 lines: >>> >>>> DISTRO_FEATURES_append = " systemd" >>>> VIRTUAL-RUNTIME_init_manager = "systemd" >>> >>> These two lines looks correct, though, if you're building a >>> systemd-only distro & image, you migth want to add: >>> >>> DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" >>> >>>> If I place these lines in my_image.bb file I seem to get a partial >>>> install of systemd, systemd_udev is there and seems to run but >> that's >>>> about it, there is no systemctrl journalctl and the sysvinit init >>>> scripts still seem to be called. >> >> >> And also on this point, make sure to check your PACKAGECONFIG values >> for systemd. The optional utilities like networkd are not enabled by >> default, and a bbapend of the systemd recipe is needed to enable them >> via PACKAGECONFIG. >> >> Cheers, >> >> Bruce > > Thanks for the info, Bruce I'll try a take a look. Are there any good examples for what to do with PACKAGECONFIG? the Yocto manual doesn't mention this at all for systemd. > I can share my configuration in a day or so, I'm in need of a refresh to github, and that'll work for one reference (and one that I know works). Otherwise, I recall that Angstrom has some systemd usecases, so cloning and having a look at those layers would also be a good reference. Bruce >> >>> >>> DISTRO_FEATURES is a distro (policy) configuration, and thus, can't >> be >>> modfied in a recipe. The correct way would be to add this in your own >>> my_distro.conf. >>> >>>> If I place these lines in either local.conf or my_distrobution.conf >>>> all of the systemd utility seem to get installed and systemd >> startups >>>> up but it's clearly not configured correctly. >>> >>> Good that it seems to be installed OK. >>> >>>> For starters the systemd dbus isn't getting created and that seems >> to >>>> lead to a whole host of other problems, including journald constant >>>> spewing the following error messages: >>> >>>> [ 55.926223] systemd-journald[715]: Failed to write entry, >> ignoring: Argument list too long >>>> [ 55.936931] systemd-journald[715]: Failed to rotate >> /run/log/journal/c37feca280b74ec583564afcc2a93f0a/system.journal: No >> such file or directory >>>> [ 55.950911] systemd-journald[715]: Failed to write entry, >> ignoring: Argument list too long >>>> [ 55.961580] systemd-journald[715]: Failed to rotate >> /run/log/journal/c37feca280b74ec583564afcc2a93f0a/system.journal: No >> such file or directory >>>> [ 55.975568] systemd-journald[715]: Failed to write entry, >> ignoring: Argument list too long >>>> [ 55.986329] systemd-journald[715]: Failed to rotate >> /run/log/journal/c37feca280b74ec583564afcc2a93f0a/system.journal: No >> such file or directory >>> >>>> I don't know if it matters but this system has no display at all, >>>> it's a strictly embedded installation. >>> >>> That shouldn't really matter, I'm running systemd in headless setups. >>> >>> I'd guess that you're getting some errors earlier than this in the >>> bootlog? Could you paste them? >>> >>> Cheers, >>> Anders >>> >>> > > > >