Re: [systemd-devel] [PATCH] nspawn: fallback on bind mount when mknod fails

2015-03-29 Thread Alban Crequy
On Sun, Mar 29, 2015 at 5:24 PM, Tom Gundersen wrote: > > On Mar 29, 2015 5:18 PM, "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 creat

Re: [systemd-devel] [PATCH] nspawn: fallback on bind mount when mknod fails

2015-03-29 Thread Tom Gundersen
On Mar 29, 2015 5:18 PM, "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. > > This patch im

[systemd-devel] [PATCH] nspawn: fallback on bind mount when mknod fails

2015-03-29 Thread Alban Crequy
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