Linked by Thom Holwerda on Wed 15th Jul 2009 16:09 UTC
Linux One of the problem with operating system updates is that you often need to reboot the system. While this is nothing but a minor nuisance for us desktop users, it's a bigger problem when it comes to servers. Ksplice is a technology that allows Linux kernel patches to be applied without actually restarting the kernel.
Thread beginning with comment 373460
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Already in NT.
by bogomipz on Wed 15th Jul 2009 19:50 UTC in reply to "Already in NT."
bogomipz
Member since:
2005-07-11

Except on NT you probably need to reboot to install the new components in the first place because files are in use and are therefore locked (which is a major design flaw in NT compared to *nix systems).

Reply Parent Score: 3

RE[2]: Already in NT.
by kaiwai on Thu 16th Jul 2009 01:12 in reply to "RE: Already in NT."
kaiwai Member since:
2005-07-06

Except on NT you probably need to reboot to install the new components in the first place because files are in use and are therefore locked (which is a major design flaw in NT compared to *nix systems).


That is the one thing I hate about Windows - the stupid idea of locking files; who ever designed such a stupid principle needs to be fired from Microsoft because it lacks all degree of common sense. It not only effects the kernel but try uninstalling applications where the application fails to unload the shared libraries resulting in locked files that results in a whole heap of crap left over when uninstalling.

Reply Parent Score: 2

RE[2]: Already in NT.
by cetp on Thu 16th Jul 2009 09:51 in reply to "RE: Already in NT."
cetp Member since:
2007-12-16
RE[3]: Already in NT.
by bogomipz on Thu 16th Jul 2009 12:33 in reply to "RE[2]: Already in NT."
bogomipz Member since:
2005-07-11

There must be a fundamental difference in how files are handled in Windows and *nix. On a *nix system, when a process reads or writes a file, and this file is deleted, renamed or replaced by another process, the first process will still see the old file until it closes its file handle.

I trust that loading libraries works the same way, although I don't know the details. I guess the trick is that files are considered the same if they are the same inode, regardless of where or when you found them in the file system tree.

Reply Parent Score: 2