XPost: comp.os.linux.advocacy   
   From: peter-koehlmann@t-online.de   
      
   Ezekiel wrote:   
      
   >   
   > "Lawrence D'Oliveiro"  wrote in message   
   > news:ik4fpe$8ak$2@lust.ihug.co.nz...   
   >> In message ,   
   >> Justin   
   >> wrote:   
   >>   
   >>> Two god damn hours to install SP1?  Good God, Microsoft is honestly   
   >>> trying to piss off their customers.   
   >>   
   >> And you can't even continue doing work while the update is installing.   
   >> Unlike Unix/Linux systems, Windows won't let you replace files that are   
   >> curently in use by a running process. So you have to stop everything until   
   >> the update is done.   
   >   
   > "You have to stop everything..." is simply a lie.   
      
   No. It is just not completely right. You can continue working. If you ignore   
   the nag-Screens about needing the reboot   
      
   > You can continue doing   
   > whatever and any files that are in-use will get replaced after the next   
   > reboot.   
   >   
   >   
   >> Even Linux updates that require a reboot only need downtime for the actual   
   >> reboot, not for the installation of the update.   
   >   
   > So in both cases you end up rebooting.   
      
   No. You need the reboot only for a kernel change in linux.   
   No point in doing that on linux for non-kernel updates   
      
   > Some files are copied before the   
   > reboot - others after the reboot. It's a distinction without a practical   
   > difference.   
      
   Oh, it *has* a practical difference. On linux, all updated programs will start   
   with the updated version as soon as you launch a new instance.   
   Or, if it is a running daemon, as soon as you initiate a restart of it.   
      
   On windows, as long as you did not reboot, you still get the old ones   
   --   
   The chief cause of problems is solutions   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)