Re:Windows 10 to be a recommended update in early 2016
by simoncion on Saturday October 31, 2015 @03:40PM
(#10483889)
> There are tradeoffs for doing things that way. Such as when everything eats shit and you regret updating.
Bad updates are bad updates, regardless of whether you do the configuration after a reboot (rendering the computer useless while you configure), or while the system is still running.
Not that it matters, but I've had far more bad updates on my Windows systems than I have on any of my Linux systems. :)
> ...time-shifting is a legitimate fix to the problem here.
It's not a fix. It's a band-aid that fails to address the root of the problem.
Re:Windows 10 to be a recommended update in early 2016
by tdkl on Saturday October 31, 2015 @09:10AM
(#10482536)
> There are tradeoffs for doing things that way. Such as when everything eats shit and you regret updating.
For example:
pacman -Syu
Knowing that you're on a rolling release distro is one thing, but being used to a "LTS" system (Windows 7,8x) then "upgrading" to a rolling release (Windows 10) is something else.
The trust in MS for being capable and responsible for handling the updates is broken.
The time was the problem in the example, so time-shifting is a legitimate fix to the problem here. "In a rush for work, turn on computer, 30 minutes of updates." was the problem.
>Every Linux distro I use seems to have figured out how to apply and configure updates before you reboot a system, rather than during the next boot cycle.
There are tradeoffs for doing things that way. Such as when everything eats shit and you regret updating.
For example:
Can be a complete nightmare.