On Sun, 2015-01-25 at 08:25 -0600, Johnny Hughes wrote: > On 01/23/2015 05:50 AM, Bill Maltby (C4B) wrote: > <snip> > > Even windows doesn't make me repeatedly click cancel if I'm not ready to > > update (I have one Windows box for one application I do and my wife has > > a couple) - it raise a little ... "flag" saying updates are available (I > > have "check with me" set rather than allowing auto updates). > > > > Yesterday on this 6.6 box I had to click cancel many times - most on one > > switch of users as apparently they queue up. > > > > AFAIK, tools are provided (sudo, "su -", ...) for non-root users to > > invoke and accomplish these functions on *their* schedule, rather than > > that set by some anonymous "one who knows better". > > Then turn off the service that does/offers auto updates in GUI mode. That is my intent. But until one encounters the new behavior and realizes that the facility behaves that way (and it never did in the past - I guess I didn't have it enabled or it wasn't part of the standard install?), it is aggravating. I only had the little star in the panel before, and it's still there. That's good enough for me. Being a non-admin type, I've tried to keep all the underlying stuff pretty much "stock" and I have no idea how deep I can go without compromising what I value - the reliable, stable behavior that has fit my M.O. for so many years prior to 6.6. E.g. I now boot into run level 5 since the transition from 3->5->3->5 ... is broken now. I could fix it it I suppose if I was willing to dedicate the hours and effort to it instead of doing what I need and prefer to do now. But avoiding that sort of onus is why I chose CentOS. I'm one of those "you broke you fix it" believers that tries to avoid placing myself in that position now that the computers are just a tool for me. > <snip> Bill