On Mon, 10 Nov 2014 18:52:09 +0000 (UTC), James wrote:

> > I'd have thought you needed to emerge -e world if you really want to
> > be protected.  
> 
> Yea, maybe. I read the man page on emptytree. I get it actually replaces
> by a "reinstall".   Does this do more than if I just reboot after
> 
> emerge @system @world and then reboot?  
> 
> I'd be curious to know exactly what reinstall does that is not
> covered by just starting up a given code again? 
> 
> Is it that it forces a reinstall and stop/starts the binary without
> rebooting?   
> 
> Rebooting catches *everything* even better than --emptytree ?

--emptytree has nothing to do with rebooting. It simply forces emerge to
rebuild everything in @world and their dependencies. Once you have done
that, you will have daemons still running the old code, which you could
fix with a reboot, or you could run checkrestart and restart only the
affected programs.

After an emerge -e @world, a reboot is probably best, another reason to
avoid the unnecessary step of emerge -e @world in the first place.


-- 
Neil Bothwick

Top Oxymorons Number 20: Synthetic natural gas