Re: [Xen-users] Upgrade Proceedure
Petersson, Mats wrote:
The spec files don't usually change much between different software
versions, although I use hte xensource src.rpm files for that: The RHEL
5 and Fedora Core SRPM's do a lot of...... extra stuff with
virt-manager that I don't feel a need for and in fact find inappropriate
for most use. (This may be due to libvirt for RedHat releases being way
behind the leading edge for the software!)
[snip a ton of old stuff]
The INSTALL script you mention works without the build directory in
place? That's a bit.... odd.
Not at all. It just takes the files in the "dist" directory (which is a
copy of what's been produced in the individual build directories, e.g.
xen.gz, qemu-dm, vmlinuz, kernel modules, hvmloader, etc, etc), and
copies it out to wherever it goes. Have a look at "dist/install.sh".
It's not complicated, it essentially just copies the files from
"dist/install" to whatever destination you specify (defualt is "/").
If you're not familiar with it, I'd like to point out that
there is a
I use Makefiles and RPM's to support full-blown package management,
version management, conflict reports, etc., etc., etc. Writing all of
that into an installer or uniinstaller script is quite a lot of work.
INSTALL script in the distribution directory which can be used to
install the resulting product of the make (which is what I described
earlier in this thread).
I recognize that not every OS has this kind of package
prefer to build on the fly.
Great if you have the environment to build the RPM, but if you take the
xen-unstable.hg repo, it doesn't come with spec-files to make RPM's
For Xen kernels, and other kernels under RHEL, one normally does an "rpm
-i", not an "rpm -U". this installs the new kernel as well as the old
one: Post-install scripts may change some of the symlinks in /boot, and
edit the grub or lilo appropriately: that takes knowledge and software
control of the grub or lilo commands, and some expertise to do carefully.
Xen-users mailing list