On Fri, Jan 27, 2017 at 06:05:54PM +0100, Leon Fauster wrote: > > Am 27.01.2017 um 17:27 schrieb m.roth at 5-cent.us: > > > > Johnny Hughes wrote: > >> On 01/27/2017 09:19 AM, Jon LaBadie wrote: > >>> With a large update to be made, eg. the 900 package > >>> one I questioned yesterday, are there any suggestions > >>> to avoid possible complications? > >>> > >>> Two examples, I'd like to know of others too: > >>> > >>> I'm not running the most recently installed kernel, > >>> I assume I should reboot to that. > >>> > >>> I normally have a graphical environment running. > >>> Would it be better to: a) shutdown X and update > >>> from a straight CLI environment b) logout from > >>> the GUI and update from a vt CLI c) update from > >>> a GUI login as root or d) doesn't matter, do as > >>> normal -- from an ssh login, "sudo yum update"? > >> ... > > In such scenario (xxx packages to update) I normally split the update command into > > # yum clean all > # yum update glibc* rpm* yum* > # yum update > # reboot The update to glibc*, wouldn't that replace the current versions on disk? If so, wouldn't there be a problem if one had to reboot before the yum update could run or complete. Or do applications not need specific glibc versions but only version X or newer. Jon -- Jon H. LaBadie jon at jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)