i'm aware of the disadvantages but i'd like to have the choice to do so anyway if/when i see fit.
On Mon, 8 Jan 2024 10:22:43 +0200, Toomas Soome via openindiana-discuss wrote: > reboot is needed to verify your setup is still working as supposed after an > update. You can have > different kind of potential issues; if file is overwritten, then your > currently running app will most > likely crash, if the file is replaced, then running apps will continue to use > old content till the > apps are restarted and you can have mixture of old and new setup, which can > give interesting results > sometimes (you think your system has security patch installed, but actually > old code is running and > you are still vulnerable for example). > > Of course, the context can be different, getting your vi or gnu tar updated > most likely will not > affect your system, but there are different scenarios. > > Having BE concept actually does imply that you get used to have those BE’s > created, so that you can > actually rely on actually having the option to roll back in case of failure > from update, or recovery > from other kind of corruption. And yes, the cost of having those BE’s is > needing to actually create > those BE’s and leave old one functional. > > I have seen plenty of cases where people have done those “small changes” on > live systems over long > period of time and ending up unbootable or broken systems once they actually > reboot the system. > Therefore I really encourage to have habit to reboot the system, to make sure > that everything is still > behaving as you do expect to. > _______________________________________________ openindiana-discuss mailing list [email protected] https://openindiana.org/mailman/listinfo/openindiana-discuss
