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"? Thanks, Jon -- Jon H. LaBadie jon at jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
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"? > > Thanks, Jon >It is certainly better to upgrade with less things running as a general practice. One should never update from a Remote X type connection via VNC or NX, etc. The absolute safest way to upgrade would be to do so via the console and a keyboard on the actual machine if there is some issue with sshd, etc. But generally, this upgrade should be OK via ssh, etc. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20170127/8d7ce0e7/attachment-0001.sig>
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"? > > It is certainly better to upgrade with less things running as a general > practice. > > One should never update from a Remote X type connection via VNC or NX, > etc. > > The absolute safest way to upgrade would be to do so via the console and > a keyboard on the actual machine if there is some issue with sshd, etc. > > But generally, this upgrade should be OK via ssh, etc. >On our about 200 workstations and servers, we just ssh in and run the yum update. Workstations... we co-ordinate with the user, and yes, it's better if they log off. Still, ssh in has always been fine (unless you have to worry about the video, such as NVidia or AMD proprietary video drivers). mark
On Fri, 2017-01-27 at 10:02 -0600, Johnny Hughes wrote:> But generally, this upgrade should be OK via ssh, etc.Just make sure you invoke screen right after you log in in case you accidentally lose the connection. Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research