On Tue, Mar 20, 2007 at 11:58:55AM +, Mark McLoughlin wrote:
> On Tue, 2007-03-13 at 23:22 +, Daniel P. Berrange wrote:
>
> > When we build an RPM we also include the default.xml file in the
> > /etc/libvirt/qemu/networks directory, as well as the autostart symlink.
> > So anyone installi
On Tue, 2007-03-13 at 23:22 +, Daniel P. Berrange wrote:
> When we build an RPM we also include the default.xml file in the
> /etc/libvirt/qemu/networks directory, as well as the autostart symlink.
> So anyone installing the libvirt RPM gets the default network, whether
> they're doing an upg
Daniel P. Berrange wrote:
On Tue, Mar 13, 2007 at 07:48:11PM -0700, David Lutterkort wrote:
On Tue, 2007-03-13 at 23:22 +, Daniel P. Berrange wrote:
When we build an RPM we also include the default.xml file in the
/etc/libvirt/qemu/networks directory, as well as the autostart symlink.
So a
On Tue, Mar 13, 2007 at 07:48:11PM -0700, David Lutterkort wrote:
> On Tue, 2007-03-13 at 23:22 +, Daniel P. Berrange wrote:
> > When we build an RPM we also include the default.xml file in the
> > /etc/libvirt/qemu/networks directory, as well as the autostart symlink.
> > So anyone installing
On Tue, 2007-03-13 at 23:22 +, Daniel P. Berrange wrote:
> When we build an RPM we also include the default.xml file in the
> /etc/libvirt/qemu/networks directory, as well as the autostart symlink.
> So anyone installing the libvirt RPM gets the default network, whether
> they're doing an upgr
I've been thinking about the tricky issue of RPM upgrades and how they
interact with the new networking stuff and don't think we've currently
got quite the optimal setup.
The current approach is that 'make install' puts a default.xml file
into /etc/libvirt/qemu/networks and also symlinks that file
