From: Henrik.Carlqvist@deadspam.com   
      
   On Sat, 04 May 2024 13:34:13 -0400, Sam wrote:   
   > I am, though, quite shocked to see that do-release-upgrade just plows   
   > through, just like that, on a live system, even with an X session going.   
   > But it does apparently work. At least, I don't see huge crowds   
   > complaining about the whole thing crashing down halfway through, because   
   > half the system is upgraded, live.   
      
   The same thing kind of applies also to Slackware when it comes to   
   security updates. I do   
   "upgradepkg --install-new --reinstall"   
   in a cron job on all new security updates from the patches directory and   
   it mostly worsk fine including when X packages are being updated. When   
   firefox has been updated firefox might say that firefox needs to be   
   restarted and of course the entire machine has to be restarted if the   
   kernel has been updated. However, I have customized my kernel packages to   
   also update the boot loader.   
      
   But yes, the recomended way to upgrade from a previous release is to do a   
   full reinstall from scratch. For me, this has never been a big problem. I   
   have multiple machines in networks running different versions of   
   Slackware. Some of those networks share home directories on NFS servers,   
   some setups have local home directories on separate partitions.   
      
   All those people out there out there finding it hard to to a total   
   reinstall from scratch probably lack a plan for doing a bare metal   
   recovery. One day such a plan might be needed in case of a disk crash,   
   fire or other disaster. It is better to have such a plan in place before   
   that happens.   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)