> > So for the first case, we could have something like
> >
> >
> >
> >
> >
> >
> >
> > Where target attributes would match /domain/devices/*/tar...@dev
>
> I'm not a huge fan of using */tar...@dev as the identifier for the
> device though, since that isn't an attribute that
On Tue, Jan 11, 2011 at 03:17:26PM +0100, Jiri Denemark wrote:
> Hi,
>
> I'm working on $SUBJ and I can't decide on XML representation of that. The
> goal is to let users specify an ordered list of devices to boot from, e.g.,
> 2nd NIC, 1st NIC, 1st CD-ROM, 2nd IDE disk. We already have boot eleme
On Tue, Jan 11, 2011 at 03:17:26PM +0100, Jiri Denemark wrote:
> Hi,
>
> I'm working on $SUBJ and I can't decide on XML representation of that. The
> goal is to let users specify an ordered list of devices to boot from, e.g.,
> 2nd NIC, 1st NIC, 1st CD-ROM, 2nd IDE disk. We already have boot eleme
Hi,
I'm working on $SUBJ and I can't decide on XML representation of that. The
goal is to let users specify an ordered list of devices to boot from, e.g.,
2nd NIC, 1st NIC, 1st CD-ROM, 2nd IDE disk. We already have boot elements in
/domain/os so we could make use of them or we could add a boot ele
