On Fri, Jun 26, 2015 at 03:27:44PM +0200, Eren Yagdiran wrote:
> Similar to the existing mounts.cfg, the mapping between the device and the
> tag is
> passed by a new disks.cfg file. Common-init reads disks.cfg and maps the tags
> to corresponding devices
> ---
> libvirt-sandbox/libvirt-sandbox-i
Similar to the existing mounts.cfg, the mapping between the device and the tag
is
passed by a new disks.cfg file. Common-init reads disks.cfg and maps the tags
to corresponding devices
---
libvirt-sandbox/libvirt-sandbox-init-common.c | 54 ++-
1 file changed, 52 insertion
On Thu, Jun 25, 2015 at 01:27:29PM +0200, Eren Yagdiran wrote:
> Similar to the existing mounts.cfg, the mapping between the device and the
> tag is
> passed by a new disks.cfg file. Common-init reads disks.cfg and maps the tags
> to corresponding devices
> ---
> libvirt-sandbox/libvirt-sandbox-i
Similar to the existing mounts.cfg, the mapping between the device and the tag
is
passed by a new disks.cfg file. Common-init reads disks.cfg and maps the tags
to corresponding devices
---
libvirt-sandbox/libvirt-sandbox-init-common.c | 51 +--
1 file changed, 49 insertion
Similar to the existing mounts.cfg, the mapping between the device and the tag
is
passed by a new disks.cfg file. Common-init reads disks.cfg and maps the tags
to corresponding devices
---
libvirt-sandbox/libvirt-sandbox-init-common.c | 51 +--
1 file changed, 49 insertion