On Sat, 07.12.13 23:56, Colin Guthrie ([email protected]) wrote:
> 'Twas brillig, and Canek Peláez Valdés at 05/12/13 23:26 did gyre and
> gimble:
> > Hi; I've been playing with systemd-nspawn with Gentoo. I'm running
> > systemd 208, and the normal Gentoo stage3 image [1], installing
> > syste
On Thu, 05.12.13 17:26, Canek Peláez Valdés ([email protected]) wrote:
> Hi; I've been playing with systemd-nspawn with Gentoo. I'm running
> systemd 208, and the normal Gentoo stage3 image [1], installing
> systemd 204 inside it. Everything works great, but for some reason
> after powering off the
(Sorry for taking so long to answer, I was away from my test system).
On Sat, Dec 7, 2013 at 5:56 PM, Colin Guthrie wrote:
> 'Twas brillig, and Canek Peláez Valdés at 05/12/13 23:26 did gyre and
> gimble:
>> Hi; I've been playing with systemd-nspawn with Gentoo. I'm running
>> systemd 208, and th
'Twas brillig, and Canek Peláez Valdés at 05/12/13 23:26 did gyre and
gimble:
> Hi; I've been playing with systemd-nspawn with Gentoo. I'm running
> systemd 208, and the normal Gentoo stage3 image [1], installing
> systemd 204 inside it. Everything works great, but for some reason
> after powering
Hi; I've been playing with systemd-nspawn with Gentoo. I'm running
systemd 208, and the normal Gentoo stage3 image [1], installing
systemd 204 inside it. Everything works great, but for some reason
after powering off the container, the file system where it resides
gets remounted read-only. I should
