Re: Most system update requires system reboot or session restart

On 29 December 2016 at 18:34, Javier Perez wrote: > I remember reading years back about solutions that allowed Kernel upgrade > without reboot. Ksplice and Kpatch comes to mind. Whatever happened to them? > > The facilities arrived in kernel 4.0 with Red Hat and Suse working

Re: Most system update requires system reboot or session restart

I remember reading years back about solutions that allowed Kernel upgrade without reboot. Ksplice and Kpatch comes to mind. Whatever happened to them? On Dec 21, 2016 07:43, "Matthew Miller" wrote: > On Tue, Dec 20, 2016 at 08:06:27PM -0500, Tom Horsley wrote: > > >

Re: Most system update requires system reboot or session restart

On Tue, Dec 20, 2016 at 08:06:27PM -0500, Tom Horsley wrote: > > Neither systemd nor dnf are to blame -- but wayland is a lot more > > fragile in this regard under the current design. > I'm not using wayland, so that isn't it. It can happen in X, too, it's just that there it's more likely that

Re: Most system update requires system reboot or session restart

On Wednesday 21 December 2016 2:37:41 AM IST Rahul Sundaram wrote: > You aren't in a rock and hard place though. Restarting is not strictly > necessary. It is a good idea however. You can also choose to use a more > conservative distribution and apply just security updates. C.f >

Re: Most system update requires system reboot or session restart

On 12/20/2016 10:50 PM, Tim wrote: Programmers like the easiest solution of doing what they want, and let the user put up with the consequences. Users prefer things to be less intrusive. Correction: bad programmers do that and arrogant programmers assume that everybody is going to want to do

Re: Most system update requires system reboot or session restart

Sudhir Khanger: >> On my weekly update I notice that I am almost always required to either >> restart the session or reboot the system. Both of these options are >> unacceptable because they require closing 10-15 apps and restarting >> them. That's unnecessary hassle and loss in productivity.

Re: Most system update requires system reboot or session restart

On 12/21/2016 02:00 AM, Kevin Fenzi wrote: On Tue, 20 Dec 2016 15:39:08 -0800 Joe Zeff wrote: On 12/20/2016 03:27 PM, Matthew Miller wrote: Depends on which part. You can use dnf repoquery to list duplicates, leaf packages (now "unneeded", which I don't think is an improvement

Re: Most system update requires system reboot or session restart

Hi On Tue, Dec 20, 2016 at 7:09 PM Sudhir Khanger > > > I think the bottom line is that you are caught between a rock and a hard > place. Either take the productivity hit by updating and restarting or take > the > security hit by not updating. > You aren't in a rock and hard place though.

Re: Most system update requires system reboot or session restart

On Tue, 20 Dec 2016 18:23:25 -0500 Matthew Miller wrote: > Neither systemd nor dnf are to blame -- but wayland is a lot more > fragile in this regard under the current design. I'm not using wayland, so that isn't it. ___ users mailing list --

Re: Most system update requires system reboot or session restart

On Tue, 20 Dec 2016 15:39:08 -0800 Joe Zeff wrote: > On 12/20/2016 03:27 PM, Matthew Miller wrote: > > Depends on which part. > > > > You can use dnf repoquery to list duplicates, leaf packages (now > > "unneeded", which I don't think is an improvement in clarity, but > >

Re: Most system update requires system reboot or session restart

On Wednesday 21 December 2016 7:02:43 AM IST Ed Greshko wrote: > The bottom line is if someone feels compelled to follow the suggestion that > you *should* reboot or that "should" is equivalent to *must* then just > don't apply updates until ready to take the necessary action to *fully* > apply

Re: Most system update requires system reboot or session restart

On 12/20/2016 03:27 PM, Matthew Miller wrote: Depends on which part. You can use dnf repoquery to list duplicates, leaf packages (now "unneeded", which I don't think is an improvement in clarity, but whatever), orphans ("extras", and ditto), unsatisfied deps (formerly "problems", now

Re: Most system update requires system reboot or session restart

On 12/21/16 06:54, Matthew Miller wrote: > On Tue, Dec 20, 2016 at 02:27:48PM -0800, Joe Zeff wrote: >> The package yum-utils included the program needs-restarting, which >> would tell you what running programs needed to be restarted because >> of an update, although it didn't seem to go so far

Re: Most system update requires system reboot or session restart

On Tue, Dec 20, 2016 at 03:20:43PM -0800, Joe Zeff wrote: > None, actually. Due to hardware issues and other distractions my > desktop is still using F 21, so I still have yum and its utilities > if needed. BTW, is there a dnf equivalent to package-cleanup? I've > had to use it several times

Re: Most system update requires system reboot or session restart

On Tue, Dec 20, 2016 at 06:20:37PM -0500, Tom Horsley wrote: > A far bigger problem that needing to reboot is that > dnf seems to sometimes wack libraries that are in > use and make my X session and/or system crash in the middle of > an update. I never had that happen with yum, but > I've seen it

Re: Most system update requires system reboot or session restart

On 12/20/2016 02:54 PM, Matthew Miller wrote: This thead actually*started* as comments about dnf-plugin-tracer, which does exactly that. What other yum utilities are you, at this point, missing? None, actually. Due to hardware issues and other distractions my desktop is still using F 21,

Re: Most system update requires system reboot or session restart

A far bigger problem that needing to reboot is that dnf seems to sometimes wack libraries that are in use and make my X session and/or system crash in the middle of an update. I never had that happen with yum, but I've seen it a couple of times with dnf (though I suspect it may have more to do

Re: Most system update requires system reboot or session restart

On 12/21/16 06:27, Joe Zeff wrote: > On 12/20/2016 02:14 PM, Rick Stevens wrote: >> After a significant number of updates, it's probably be a good idea to >> reboot just to ensure you are using the latest kernel and that any >> services that were updated have been restarted. How and when that >>

Re: Most system update requires system reboot or session restart

On Tue, Dec 20, 2016 at 02:27:48PM -0800, Joe Zeff wrote: > The package yum-utils included the program needs-restarting, which > would tell you what running programs needed to be restarted because > of an update, although it didn't seem to go so far as to tell you > that you needed to reboot.

Re: Most system update requires system reboot or session restart

On 12/20/2016 02:14 PM, Rick Stevens wrote: After a significant number of updates, it's probably be a good idea to reboot just to ensure you are using the latest kernel and that any services that were updated have been restarted. How and when that reboot cycle happens is completely up to you.

Re: Most system update requires system reboot or session restart

On 12/20/2016 01:07 PM, Joe Zeff wrote: > On 12/20/2016 12:26 PM, Matthew Miller wrote: >> On Tue, Dec 20, 2016 at 11:15:19AM -0800, Joe Zeff wrote: >>> And some of us are using distributed computing, such as BOINC and >>> don't like interrupting the work. >> >> Aren't these things set up to be

Re: Most system update requires system reboot or session restart

On 12/20/2016 12:26 PM, Matthew Miller wrote: On Tue, Dec 20, 2016 at 11:15:19AM -0800, Joe Zeff wrote: And some of us are using distributed computing, such as BOINC and don't like interrupting the work. Aren't these things set up to be resiliant to nodes going in and out? Yes, of course

Re: Most system update requires system reboot or session restart

On Tue, Dec 20, 2016 at 11:15:19AM -0800, Joe Zeff wrote: > And some of us are using distributed computing, such as BOINC and > don't like interrupting the work. Aren't these things set up to be resiliant to nodes going in and out? -- Matthew Miller Fedora Project

Re: Most system update requires system reboot or session restart

On Tue, Dec 20, 2016 at 04:13:45PM +0530, Sudhir Khanger wrote: > On my weekly update I notice that I am almost always required to > either restart the session or reboot the system. Both of these > options are unacceptable because they require closing 10-15 apps and > restarting them. That's

Re: Most system update requires system reboot or session restart

On 12/20/2016 11:02 AM, George N. White III wrote: Yes, some applications have a lengthy setup process and run for days, so are not appropriate for a system that is rebooted frequently. At my work, a window on one day a week is "reserved" for updates and possible reboots, so users can schedule

Re: Most system update requires system reboot or session restart

On 20 December 2016 at 14:40, Samuel Sieb wrote: > On 12/20/2016 02:43 AM, Sudhir Khanger wrote: > >> On my weekly update I notice that I am almost always required to either >> restart the session or reboot the system. Both of these options are >> unacceptable because they

Re: Most system update requires system reboot or session restart

On 12/20/2016 02:43 AM, Sudhir Khanger wrote: On my weekly update I notice that I am almost always required to either restart the session or reboot the system. Both of these options are unacceptable because they require closing 10-15 apps and restarting them. That's unnecessary hassle and loss

Re: Most system update requires system reboot or session restart

On 12/20/2016 05:43 AM, Sudhir Khanger wrote: Hi, I update my Fedora Plasma desktop on a weekly basis. I have dnf tracer plugin installed. On my weekly update I notice that I am almost always required to either restart the session or reboot the system. Both of these options are unacceptable

Most system update requires system reboot or session restart

Hi, I update my Fedora Plasma desktop on a weekly basis. I have dnf tracer plugin installed. On my weekly update I notice that I am almost always required to either restart the session or reboot the system. Both of these options are unacceptable because they require closing 10-15 apps and