Re: Errors in Classifying Updates

2020-05-15 Thread Patrick O'Callaghan
On Fri, 2020-05-15 at 17:38 +0800, Ed Greshko wrote: > On 2020-05-15 16:56, Patrick O'Callaghan wrote: > > On Fri, 2020-05-15 at 06:32 +0800, Ed Greshko wrote: > > > On 2020-05-15 02:51, Samuel Sieb wrote: > > > > But this discussion is rather irrelevant anyway. You're not going to > > > > get wh

Re: Errors in Classifying Updates

2020-05-15 Thread Ed Greshko
On 2020-05-15 16:56, Patrick O'Callaghan wrote: > On Fri, 2020-05-15 at 06:32 +0800, Ed Greshko wrote: >> On 2020-05-15 02:51, Samuel Sieb wrote: >>> But this discussion is rather irrelevant anyway. You're not going to get >>> what you want. Online updates are not "supported". You can do them i

Re: Errors in Classifying Updates

2020-05-15 Thread Patrick O'Callaghan
On Fri, 2020-05-15 at 06:32 +0800, Ed Greshko wrote: > On 2020-05-15 02:51, Samuel Sieb wrote: > > But this discussion is rather irrelevant anyway. You're not going to get > > what you want. Online updates are not "supported". You can do them if you > > want, but you are on your own. I do onl

Re: Errors in Classifying Updates

2020-05-14 Thread Ed Greshko
On 2020-05-15 02:51, Samuel Sieb wrote: > But this discussion is rather irrelevant anyway.  You're not going to get > what you want.  Online updates are not "supported".  You can do them if you > want, but you are on your own.  I do online upgrades (not system upgrades), > but I also generally r

Re: Errors in Classifying Updates

2020-05-14 Thread Joe Zeff
On 05/14/2020 12:51 PM, Samuel Sieb wrote: I'm saying that if one executable has a shared library open and then that library is deleted, the inode still exists.  However, the same path could now point to a different inode with a new version of the library and any executables getting started aft

Re: Errors in Classifying Updates

2020-05-14 Thread Kevin Fenzi
On Thu, May 14, 2020 at 11:51:11AM -0700, Samuel Sieb wrote: > On 5/14/20 11:34 AM, Joe Zeff wrote: > > On 05/14/2020 12:20 PM, Samuel Sieb wrote: > > > > > > Besides, you say the file doesn't vanish until the last program > > > closes it.  While technically true, it's not practically true.  > > >

Re: Errors in Classifying Updates

2020-05-14 Thread Samuel Sieb
On 5/14/20 11:34 AM, Joe Zeff wrote: On 05/14/2020 12:20 PM, Samuel Sieb wrote: Besides, you say the file doesn't vanish until the last program closes it.  While technically true, it's not practically true.  Sure, the inode still exists in the file system, but the name is gone or points to a

Re: Errors in Classifying Updates

2020-05-14 Thread Joe Zeff
On 05/14/2020 12:20 PM, Samuel Sieb wrote: Besides, you say the file doesn't vanish until the last program closes it.  While technically true, it's not practically true.  Sure, the inode still exists in the file system, but the name is gone or points to a different file.  So even if one appli

Re: Errors in Classifying Updates

2020-05-14 Thread Samuel Sieb
On 5/14/20 10:12 AM, Joe Zeff wrote: On 05/14/2020 09:26 AM, Richard Hughes wrote: It's impossible. Desktop applications do not expect files to just disappear when running. This is Linux we're talking about, so they don't.  When you delete a file, it doesn't vanish until the last program usin

Re: Errors in Classifying Updates

2020-05-14 Thread Joe Zeff
On 05/14/2020 09:26 AM, Richard Hughes wrote: It's impossible. Desktop applications do not expect files to just disappear when running. This is Linux we're talking about, so they don't. When you delete a file, it doesn't vanish until the last program using it closes the file. HTH, HAND. __

Re: Errors in Classifying Updates

2020-05-14 Thread Richard Hughes
On Thu, 14 May 2020 at 13:45, John Mellor wrote: > > All package updates are scheduled for offline installation. There's no > > safe way to update packages at runtime, and I've written a lot about > > this in the past. > That is untrue. I have observed a few packages installing without a > requir

Re: Errors in Classifying Updates

2020-05-14 Thread John Mellor
On 2020-05-14 8:08 a.m., Richard Hughes wrote: On Wed, 13 May 2020 at 13:28, John Mellor wrote: That just stumps me. How can Vim possibly be an update requiring a system reboot? All package updates are scheduled for offline installation. There's no safe way to update packages at runtime, and

Re: Errors in Classifying Updates

2020-05-14 Thread Richard Hughes
On Wed, 13 May 2020 at 13:28, John Mellor wrote: > That just stumps me. How can Vim possibly be an update requiring a > system reboot? All package updates are scheduled for offline installation. There's no safe way to update packages at runtime, and I've written a lot about this in the past. >

Errors in Classifying Updates

2020-05-13 Thread John Mellor
The Gnome update tool classifies updates as things that can be immediately installed, and things that require a reboot to install.  I have never seen an update requiring users to login again, but that should obviously be a state transition that the Gnome updater should occasionally need as well