Re: Please...
> and moans that Windows need a reboot after patching,
While Windows does need a reboot after an update that replaces or patches the kernel, it also needs a reboot because Windows cannot delete or replace a file that is open due to the way the file system is designed. As many library files are open on a running system then it almost always needs a reboot so that files can be deleted and replaced during start up and before they are opened.
Unix like systems using an inode file system can delete and replace files that are open because the file name is not directly linked to the data blocks but is done through the inode. An open file can continue to use the original inode while the update creates a new inode with its own set of data blocks and the file name is linked to the new inode. The old inode and its data is deleted when all processes have closed the old inode.
This means that the vast majority of updates do not require a reboot. Some systems will do in-flight kernel patching that also does not require a reboot.
Biting the hand that feeds IT
