On Tue, Mar 31, 2015 at 07:14:26PM +0200, Lennart Poettering wrote:
> On Tue, 31.03.15 11:35, Dave Reisner (d...@falconindy.com) wrote:
>
> > > +/* Some systems abusively restrict mknod
> > > but
> > > + * allow bind mounts. */
> > >
On Tue, 31.03.15 11:35, Dave Reisner (d...@falconindy.com) wrote:
> > +/* Some systems abusively restrict mknod
> > but
> > + * allow bind mounts. */
> > +r = touch(to);
> > +
On Tue, Mar 31, 2015 at 5:35 PM, Dave Reisner wrote:
> On Tue, Mar 31, 2015 at 05:14:48PM +0200, Alban Crequy wrote:
>> From: Alban Crequy
>>
>> Some systems abusively restrict mknod, even when the device node already
>> exists in /dev. This is unfortunate because it prevents systemd-nspawn
>> fr
On Tue, Mar 31, 2015 at 05:14:48PM +0200, Alban Crequy wrote:
> From: Alban Crequy
>
> Some systems abusively restrict mknod, even when the device node already
> exists in /dev. This is unfortunate because it prevents systemd-nspawn
> from creating the basic devices in /dev in the container.
>
>
On Tue, 31.03.15 17:14, Alban Crequy (alban.cre...@gmail.com) wrote:
> From: Alban Crequy
>
> Some systems abusively restrict mknod, even when the device node already
> exists in /dev. This is unfortunate because it prevents systemd-nspawn
> from creating the basic devices in /dev in the contain
From: Alban Crequy
Some systems abusively restrict mknod, even when the device node already
exists in /dev. This is unfortunate because it prevents systemd-nspawn
from creating the basic devices in /dev in the container.
This patch implements a workaround: when mknod fails, fallback on bind
moun
