On 15/04/2013 11:45 PM, Jack Mitchell wrote:
On 15/04/13 14:10, Martin Jansa wrote:
On Mon, Apr 15, 2013 at 01:58:52PM +0100, Jack Mitchell wrote:
Ok, I have just come back to trying out the new systemd implementation,
and this bug still exists.
Exactly the same error as before:
[
On 23/02/2013 1:50 AM, Jack Mitchell wrote:
On 22/02/13 14:15, Jack Mitchell wrote:
On 22/02/13 09:22, Jack Mitchell wrote:
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
On Mon, Apr 15, 2013 at 01:58:52PM +0100, Jack Mitchell wrote:
Ok, I have just come back to trying out the new systemd implementation,
and this bug still exists.
Exactly the same error as before:
[2.390730] systemd[1]: Failed to mount /run: No such file or directory
Can we shed any
On 15/04/13 14:10, Martin Jansa wrote:
On Mon, Apr 15, 2013 at 01:58:52PM +0100, Jack Mitchell wrote:
Ok, I have just come back to trying out the new systemd implementation,
and this bug still exists.
Exactly the same error as before:
[2.390730] systemd[1]: Failed to mount /run: No such
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 m...@communistcode.co.uk wrote:
Did this ever go anywhere? I have just tried again today with exactly the
same result, all I did was
On 22/02/13 09:22, Jack Mitchell wrote:
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 m...@communistcode.co.uk
wrote:
Did this ever go anywhere? I have just tried again today with
On 22/02/13 14:15, Jack Mitchell wrote:
On 22/02/13 09:22, Jack Mitchell wrote:
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 m...@communistcode.co.uk
wrote:
Did this ever go
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 m...@communistcode.co.uk 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
On 25/01/13 08:28, Radu Moisan wrote:
On 01/24/2013 04:52 PM, Burton, Ross wrote:
On 24 January 2013 13:03, Radu Moisan radu.moi...@intel.com wrote:
ok, thanks Enrico, this clears the picture for me.
Well then it looks like Jack's problems is coming from some other
place.
No - /run needs to
On 14 February 2013 14:31, Jack Mitchell m...@communistcode.co.uk 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
On 14/02/13 15:31, Burton, Ross wrote:
On 14 February 2013 14:31, Jack Mitchell m...@communistcode.co.uk 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
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 m...@communistcode.co.uk 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
On 02/14/13 15:57, Jack Mitchell 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 m...@communistcode.co.uk
wrote:
Did this ever go anywhere? I have just tried again today with
exactly the
same result, all I did was
On 01/23/2013 05:19 PM, Jack Mitchell wrote:
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
On 24 January 2013 09:46, Radu Moisan radu.moi...@intel.com wrote:
Possibly because /run was a link created by the initscripts which are now
disabled when systemd is the init manager. I'll look into this and update
00-create-volatile.conf so that systemd will handle the link creation in
stead.
On 01/24/2013 02:01 PM, Burton, Ross wrote:
On 24 January 2013 09:46, Radu Moisan radu.moi...@intel.com wrote:
Possibly because /run was a link created by the initscripts which are now
disabled when systemd is the init manager. I'll look into this and update
00-create-volatile.conf so that
On 24 January 2013 12:11, Radu Moisan radu.moi...@intel.com wrote:
This is exactly what I was looking for. /run shouldn't be there, yet somehow
it is. I was looking into how/where systemd is creating /run but no lead for
now.
As far as I'm aware systemd will mount a tmpfs on /run itself on
Radu Moisan radu.moisan-ral2jqcrhueavxtiumw...@public.gmane.org
writes:
Possibly because /run was a link created by the initscripts which
are now disabled when systemd is the init manager. I'll look into
this and update 00-create-volatile.conf so that systemd will handle
the link creation in
On 01/24/2013 02:20 PM, Enrico Scholz wrote:
Radu Moisan radu.moisan-ral2jqcrhueavxtiumw...@public.gmane.org
writes:
Possibly because /run was a link created by the initscripts which
are now disabled when systemd is the init manager. I'll look into
this and update 00-create-volatile.conf so
Radu Moisan radu.moisan-ral2jqcrhueavxtiumw...@public.gmane.org
writes:
/run is part of systemd's api and mounted very early internally by
systemd. This mountpoint must exist in the filesystem and it will
probably not work when it is symlink into /var/volatile which gets
mounted later.
On 01/24/2013 02:53 PM, Enrico Scholz wrote:
Radu Moisan radu.moisan-ral2jqcrhueavxtiumw...@public.gmane.org
writes:
/run is part of systemd's api and mounted very early internally by
systemd. This mountpoint must exist in the filesystem and it will
probably not work when it is symlink into
On 24 January 2013 13:03, Radu Moisan radu.moi...@intel.com wrote:
ok, thanks Enrico, this clears the picture for me.
Well then it looks like Jack's problems is coming from some other place.
No - /run needs to exist for the mount to happen, and there isn't a
/run in the filesystem. Whatever
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]:
23 matches
Mail list logo
