Re:Introducing PackageManagement in Windows 10
by level on Wednesday April 29, 2015 @01:42PM
(#9460121)
I don't even mind the multiple restarts, the part that bothers me is that I have to babysit Windows Update as soon as my machine finishes restarting, tell it to get updates, tell it to install now, and then have it restart again. If Windows Update could collect all the update packages, and I could leave it alone for 20 minutes and come back to a fully updated system, that would be fantastic.
Re:Introducing PackageManagement in Windows 10
by glesica on Wednesday April 29, 2015 @02:01PM
(#9460320)
Yeah, this seems like it should be pretty straightforward (I'm sure it is harder than it seems, but still). Set a flag that persists through multiple reboots that says "after Windows loads, if there are updates, apply them and reboot, repeat, otherwise unset the flag".
Re:Introducing PackageManagement in Windows 10
by tomswartz07 on Wednesday April 29, 2015 @02:28PM
(#9460577)
Fun fact: I helped tweak up a Powershell script that does this exact thing:
https://github.com/tomswartz07/packer-windows/blob/master/sc...
Re:Introducing PackageManagement in Windows 10
by tacticus on Wednesday April 29, 2015 @09:34PM
(#9462846)
I owe you a reasonable beverage of your choosing. Please redeem anytime you're in melbourne.au :)
Re:Introducing PackageManagement in Windows 10
by seanp2k2 on Wednesday April 29, 2015 @02:08PM
(#9460388)
If only it had a place to register a setting or store a file containing information like "update until you reach the latest version". It'd also need to be able to get through all the updates without crashing even once (otherwise we'd need to check the disks and repair start-up files, and that can't be automated), so maybe this is just impossible.
Re:Introducing PackageManagement in Windows 10
by derefr on Wednesday April 29, 2015 @09:42PM
(#9462863)
Even in Linux you've got to restart once, if you update the kernel or somesuch. The problem with Windows is the restarts before the final one, where you need to finish upgrading to version N+1 before the updates taking you to N+2 will even download.
If the updater software could just plan out a patch-graph ("once I do X, then Y will be available, so I'll do Y, and that means Z will be available"), then apply all the updates it had recursively discovered and only restart at the very end, everyone would be happy.
Even though the resulting mechanism wouldn't be very similar at all to Linux's idempotent "just install the latest version of the package, you don't have to take the steps in-between" system, it's the UX that matters.
Re:Introducing PackageManagement in Windows 10
by Latty on Thursday April 30, 2015 @04:48AM
(#9463953)
Actually the 4.0 release has added support for no-reboot kernel patching, IIRC.
Re:Introducing PackageManagement in Windows 10
by tomswartz07 on Wednesday April 29, 2015 @01:55PM
(#9460249)
Heck, I'd be okay with booting into a Windows PE drive, if it meant that after 1 reboot I'd have a fully upgraded OS.
This isn't going to happen. MS is tied deeply into restarting due to how it loads libraries and other issues. Unless they write a new OS from scratch and give up on legacy compatibility, well, don't hold your breath.