It doesn't, I have installed many Windows updates that didn't require a reboot. Even ones I expected to need an update, like an update to a graphics driver. Screen just went blank, then came back a second later.
AFAICT it's only updates to things that run at startup time that require a reboot, probably because NTFS doesn't allow you to write to a file that's currently opened (as opposed to nearly every Linux filesystem, which handles that just fine: the process that has the file opened continues to see the "old" file, while any that open it after the write will see the "new" file — but NTFS, probably due to internal architecture, can't handle that and so you have to reboot to change files that background services are using).
It has nothing to so with NTFS, but all with the Win32 API. The Windows kernel supports this file model, proven by WSL1. There is a blog post somewhere (Old New Thing?) stating the engineers would like to e.g. allow deleting a file even if there is still a program with with a file handle to it, but are concerned deviation from current behavior would cause more problems than it solves.
The reason that they want a reboot is that they do not want to support a system using two versions of the same library at the same time, let's say ntdll. So they would have to close any program using that library before programs that use the new version can be started. That is equivalent to a reboot.
And I completely understand the reason. For a long time when Firefox would update on Linux, the browser windows still open were broken; it opened resources meant for the updated Firefox with the processes runnung the non-updated Firefox. The Chrome developers mentioned [2] that the "proper" solution would be to open every file at start and pass that file descriptor to the subprocesses so all of them are using the same version of the file. Needless to say, resource usage would go up.
This isn't an NTFS thing. The I/O Manager implements NtLockFile. Applications can request exclusive byte-range write access to a file. And perhaps it is lazy programmers, or defaults, but they generally do.
I don't think Microsoft sees client machine reboots as an issue, and it used to be much worse when they used to be released weekly. On the server side, Microsoft expects that you'd implement some form of high availability.
NTFS on non-Windows follows the locking semantics of the underlying driver model/kernel, e.g. you can replace an in-use file on Linux. Likewise, using FAT on Windows you cannot replace an in-use file. This is just to demonstrate it isn't a file system-specific "issue" (if you feel it is one). It was a design decision by the original NT OS/2 development group.
Ultimately, the NT byte-range locking is a holdover from NT OS/2, where in OS/2 byte-range locking was mandatory.
There a enough apps that keep old files open, but also (re)open updated files that do not fit to the old, open ones, thus have all kind of issues.
(Subjectively Thunderbird has major issues with not restarting if libs it depends on get upgraded.)
I stopped answering support mails and tickets from users with long uptime with anything else than: reboot first.
And it was >>80% the cause of problems.
And yes, most times a logout would suffice, but with our users having >100d uptime with desktops and laptops, the occasional kernel update is done /en passant/ this way.
(The impatient could kexec and have the advantage of both. Or look at the output of "need restart" or "checkrestart". But I couldn't care less in case of end user devices)
Can‘t replace files that are in-use and that includes running programs or loaded DLLs. Linux can, it keeps the inode and only actually deletes upon termination of last access.
Ive read this many times, so I tried this a few times, giving it the benefit of the doubt, only to find the PC on login screen the following morning every time.
Ugh, I've had this happen over and over. I can't trust my laptop to actually shut down. I have to wait to see the light stay off for a couple seconds before I put it in my bag.
> Are Anthropic currently unable to sell subscriptions because they don’t have capacity?
Absolutely! Im currently paying $170 to google to use Opus in antigravity without limit in full agent mode, because I tried Anthropic $20 subscription and busted my limit within a single prompt. Im not gonna pay them $200 only to find out I hit the limit after 20 or even 50 prompts.
And after 2 more months my price is going to double to over $300, and I still have no intention of even trying the 20x Max plan, if its really just 20x more prompts than Pro.
Im gonna go against the grain here, so hold your pitchforks please, but I think its better than if it were consistent. Let me explain:
The author notices that adding a toolbar changes the radius, and to me it makes sense. If theres a toolbar, I know how much I can cut the corners, because the icons in the toolbar are not gonna be in far corner. At the same time, when I am unsure about what type of content might get cut by the corner, I will reduce the cut slightly to give that content more space.
I couldnt care less that one radius is not the same as another, I guess my OCD levels are not that high (yet?).
And I say all of this as someone who dislikes the glass design, and especially hates the small, slowly fading in volume/brightness indicators in the corner replacing the mid screen beautiful instant indicator.
So… the moment the Interface Designer in XCode can identify the app only has a single button at the center of a window, the window should be a circle? :)
I have Google AI Ultra. Where can I test this? They say its in aistudio, which says its a paid model and I need to setup billing (as if paying for Ultra isnt enough). They say its available in antigravity, but I cant seem to find it there?
Can anybody break my black glasses and offer an anecdote of a high-employee count firm actually involving humans for reading feedback? I suspect its just there for "later", but never actually looked at by anyone...
You know when your game crashes on PS5 and you get a little popup that offers you the opportunity to write feedback/description of the crash?
Yeah, I used to sit and read all of these(at one of the largest video game publishers - does that count?). 95% of them were "your game sucks" but we fixed many bugs thanks to detailed descriptions that people have provided through that box.
reply