Updating software in fedora 7
If you’ve upgraded from past Fedora releases, you may be familiar with the upgrade plugin.
This method is the recommended and supported way to upgrade from Fedora 24 to Fedora 25.
Use yum command to install critical and non-critical security updates as well as binary packages.
Login as the root user to install and update the system. perl-libxml-perl.noarch 0.08-1.2.1 base perl-suidperl.i386 4:5.8.8-10.el5_0.2 updates Installed Groups: Engineering and Scientific My SQL Database Editors System Tools Text-based Internet Legacy Network Server DNS Name Server Dialup Networking Support FTP Server Network Servers Legacy Software Development Legacy Software Support Development Libraries Graphics Web Server Ruby Printing Support Mail Server Server Configuration Tools Postgre SQL Database Available Groups: Office/Productivity Administration Tools Beagle Development Tools GNOME Software Development X Software Development Virtualization GNOME Desktop Environment Authoring and Publishing Mono Games and Entertainment XFCE-4.4 Tomboy Java Java Development Emacs X Window System Windows File Server KDE Software Development KDE (K Desktop Environment) Horde Sound and Video Free NX and NX News Server Yum Utilities Graphical Internet Done Loading "installonlyn" plugin Loading "security" plugin Setting up repositories Reading repository metadata in from local files Extra Packages Deny Hosts.noarch 2.6-python2.4 installed VMware Tools.i386 6532-44356 installed john.i386 18.104.22.168-3.el5installed kernel.i686 2.6.18-8.1.15.el5 installed kernel-devel.i686 2.6.18-8.1.15.el5 installed lighttpd.i386 1.4.18-1.el5installed lighttpd-fastcgi.i386 1.4.18-1.el5installed psad.i386 2.1-1 installed rssh.i386 2.3.2-1.2.el5installed Loading "installonlyn" plugin Loading "security" plugin Setting up repositories Reading repository metadata in from local files setup.noarch 2.5.58-1.el5 base Matched from: /etc/passwd setup.noarch 2.5.58-1.el5 installed Matched from: /etc/passwd The author is the creator of nix Craft and a seasoned sysadmin and a trainer for the Linux operating system/Unix shell scripting.
The side effect of this mechanism is, of course, that if you install any software in your App VM, more specifically in any directory other than then it will disappear after the App VM reboot (as the root filesystem for this App VM will again be “taken” from the Template VM).
This means one normally install software in the Template VM, not in App VMs.
To remove the The removal process leaves user data in place but may remove configuration files in some cases.
In addition to saving on the disk space, and reducing domain creation time, another advantage of such scheme is the possibility for centralized software update.It’s just enough to do the update in the template VM, and then all the App VMs based on this template get updates automatically after they are restarted.