From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eumx.net ([91.82.101.43]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1U8p5B-0003RL-Jt for openembedded-core@lists.openembedded.org; Fri, 22 Feb 2013 10:38:21 +0100 Message-ID: <512738BF.9000404@communistcode.co.uk> Date: Fri, 22 Feb 2013 09:22:07 +0000 From: Jack Mitchell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130109 Thunderbird/17.0.2 MIME-Version: 1.0 To: Patches and discussions about the oe-core layer References: <510124FE.6040901@intel.com> <51012A68.806@intel.com> <51013136.7040807@intel.com> <5102423C.4010408@intel.com> <511CF540.6090302@communistcode.co.uk> <511D0669.6020903@communistcode.co.uk> <20130221222728.GA1833@sakrah.homelinux.org> In-Reply-To: <20130221222728.GA1833@sakrah.homelinux.org> Subject: Re: systemd: /run directory not created X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: ml@communistcode.co.uk List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2013 09:38:22 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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_INITMAN to systemd. >>> Odd, as I just built and booted a systemd image (core-image-sato, in >>> poky master), and it worked fine. >>> >>> Ross >> I have a custom distro definition that cuts a lot of features out. >> Can you find out which package is supposed to create run and I can >> check if it is pulled in properly on my setup? >> >> I think something must be assumed somewhere and I don't have the >> features enabled to trigger it. > its created by base-files package. If you need hint how it works > with systemd take a look at bbappend that angstrom has for base-files > in meta-angstrom Ah, I see. Thanks Khem. So, the next question is; how come Angstrom requires these files to be appended to base-files in order to get systemd going, when oe-core doesn't? I notice there is: ${localstatedir}/volatile/run \ In the base-files oe-core package, while in Angstrom we have: ${localstatedir}/run \ /run \ I understand oe-core having it as a volatile; but I don't understand why it doesn't create the /run directory. I see some kind of logic regarding it here: volatiles = "run log lock tmp" for d in ${volatiles}; do ln -sf volatile/$d ${D}${localstatedir}/$d done However, if it doesn't create the directory on my target filesystem then something must be wrong... -- Jack Mitchell (jack@embed.me.uk) Embedded Systems Engineer http://www.embed.me.uk --