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 1Ty2Lu-0004QP-6x for openembedded-core@lists.openembedded.org; Wed, 23 Jan 2013 16:35:05 +0100 Message-ID: <50FFFF81.8010203@communistcode.co.uk> Date: Wed, 23 Jan 2013 15:19:29 +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 Subject: 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: Wed, 23 Jan 2013 15:35:05 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit When I attempt to boot a systemd enabled image I get an error stating that the run directory could not be mounted as it doesn't exist. I checked the target rootfs and there isn't a /run directory. What is responsible for creating this and why is it not doing it's job? [ 2.631549] systemd[1]: Failed to mount /run: No such file or directory Possibly of interest is that I am running a custom distro with manually specified DISTRO_FEATURES. -- Jack Mitchell (jack@embed.me.uk) Embedded Systems Engineer http://www.embed.me.uk --