On Wed, 30.04.14 14:02, Florian Weimer (fwei...@redhat.com) wrote:
On 04/30/2014 01:08 PM, Lennart Poettering wrote:
On Tue, 29.04.14 20:43, Florian Weimer (fwei...@redhat.com) wrote:
The message at
https://mail.gnome.org/archives/ostree-list/2014-February/msg00010.html
contains two
Move the container wait logic into its own wait_for_container() function
and add two status codes: CONTAINER_TERMINATED or CONTAINER_REBOOTED.
These status codes are used to terminate nspawn or loop again in case of
CONTAINER_REBOOTED.
---
v1 - v2:
Apply Tom Gundersen notes.
src/nspawn/nspawn.c
On Fri, Apr 25, 2014 at 08:12:13PM +0200, Tom Gundersen wrote:
On Fri, Apr 11, 2014 at 2:45 AM, Djalal Harouni tix...@opendz.org wrote:
nspawn and the container child use eventfd to wait and notify each other
that they are ready so the container setup can be completed.
However in its
On 05/02/2014 01:05 PM, Lennart Poettering wrote:
No, /dev/random can (and will) block long after booting.
But that's what you want in this case, no? You want this to block after
booting if there never has been enough entropy in the pool, right?
What I want is no blocking at all. If the
nspawn and the container child use eventfd to wait and notify each other
that they are ready so the container setup can be completed.
However in its current form the wait/notify event ignore errors that
may especially affect the child (container).
On errors the child will jump to the child_fail
On Wed, 30.04.14 14:21, Daniel J Walsh (dwa...@redhat.com) wrote:
http://rhatdan.wordpress.com/2014/04/30/running-systemd-within-a-docker-container/
There are a couple of things in the story that I'd like to correct:
1) udev isn't actually started when systemd detects that /sys is read-only.
On 05/02/2014 11:54 AM, Lennart Poettering wrote:
On Wed, 30.04.14 14:21, Daniel J Walsh (dwa...@redhat.com) wrote:
http://rhatdan.wordpress.com/2014/04/30/running-systemd-within-a-docker-container/
There are a couple of things in the story that I'd like to correct:
1) udev isn't actually
I broke my machine and can not log anymore. When at login prompt, I
can log as user or root, I am rejected.
I have no idea what broke the system (upgrade, wrong behavior, a 100%
full ssd...). The box is clean, up to date, no fancy hacks (I think
so...).
Some info:
Distro : Arch linux
systemd :
On Fri, May 02, 2014 at 12:54:25PM -0400, Daniel J Walsh wrote:
On 05/02/2014 11:54 AM, Lennart Poettering wrote:
On Wed, 30.04.14 14:21, Daniel J Walsh (dwa...@redhat.com) wrote:
http://rhatdan.wordpress.com/2014/04/30/running-systemd-within-a-docker-container/
There are a couple of
