On Tue, Oct 4, 2016 at 12:18 PM, Pommier, Rex <rpomm...@sfgmembers.com> wrote:
> Charles, > > I hear where you're coming from, but this sword cuts both ways. If I have > an install on the mainframe go south, I have the diagnostic tools to figure > out what went wrong and correct the problem. Comparing that to my Windows > install on my home PC, it says I have 75 critical updates that I need to > install, but when I click the next-next-go it just sits there claiming it > is downloading the updates but nothing happens. I get no errors, no > nothing indicating what's wrong. I try to run the "updater fix it tool" > and the extent of errors I get back consists of "something went wrong". I > shudder to think what mess we'll be in if the mainframe installation ever > gets to that level. > > Rex > > IMO, the way my Linux distro (Redhat Fedora) does things is much nicer that Windows. I have a CLI tool, "dnf", which can be used to upgrade one package (the Linux kernel is a package), a list of packages, or all packages. Assuming the vendor does the work correctly (and Redhat has so far), dnf will resolve inter-package dependencies by either adding more packages to the list or by telling me that a listed package cannot be upgraded to a missing co-requisite. It will then give me a list of what it intends to download & upgrade, which shows the version/patch level. I then approve that list. It then downloads _all_ the packages to a staging area on disk. It then starts upgrading packages. It is really quite easy. Debian based distributions have something similar. -- Heisenberg may have been here. Unicode: http://xkcd.com/1726/ Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
