> -----Original Message----- > From: fedora-devel-list-bounces@xxxxxxxxxx [mailto:fedora-devel-list- > bounces@xxxxxxxxxx] On Behalf Of Colin Walters > Sent: Tuesday, December 15, 2009 11:44 > To: Development discussions related to Fedora > Subject: Re: packages requiring me to reboot... > > On Tue, Dec 15, 2009 at 5:40 PM, Richard Hughes <hughsient@xxxxxxxxx> > wrote: > > 2009/12/15 Seth Vidal <skvidal@xxxxxxxxxxxxxxxxx>: > >> Now, having said that - how would you feel if the updater stopped you > before > >> it ran and said "you're running an app I'm trying to update, please > close > >> the app so I can update it". Would that be a pain or ok? > > > > That's exactly the PackageKit functionality I've added for packages > > like firefox, that explode internally when they get updated. The trick > > it to offer to close them down, and bring them back when done. > > > This exists? Can you point me to the code? > > -- I am not sure what the argument is, factually there are packages that have files open, locks and etc. that need to be shutdown to update, if they are running and you replace the executable, doesn't mean that the memory image is replaced. It is quicker and simpler to just reboot, also the list of the packages that cause you to reboot is probably longer than the ones that are flagged. I think that a reboot should be made whether necessary or not, clears up a lot of grief. > fedora-devel-list mailing list > fedora-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
