Ever looked at piece of machinery and seen a counter on the engine to know how many hours of use the machine
has got. They do this for a few reasons..
1. To keep track of how long the fluids need to be changed
2. To determine the value of the equpitment with depreciation.
3. To figure out how much wear and tear the components have had... etc
Now what if an OS were to have a kernel level module that would monitor and store this same information in a
locked location?
What would the advantage be:
1: If the OS is broken in some way, you can figure how many "miles" the OS has on it and determine if a reinstall
is the best option, or if its worth fiddling around in the os to attempt to fix.
2. Determine how much use in general the hardware has if you are looking for hardware problems.
Anyone have any comments or know if there is a solution already for this purpose?
I know that you can usuall tell when Windows was installed by the creation date of C:\Windows
foxkm
has got. They do this for a few reasons..
1. To keep track of how long the fluids need to be changed
2. To determine the value of the equpitment with depreciation.
3. To figure out how much wear and tear the components have had... etc
Now what if an OS were to have a kernel level module that would monitor and store this same information in a
locked location?
What would the advantage be:
1: If the OS is broken in some way, you can figure how many "miles" the OS has on it and determine if a reinstall
is the best option, or if its worth fiddling around in the os to attempt to fix.
2. Determine how much use in general the hardware has if you are looking for hardware problems.
Anyone have any comments or know if there is a solution already for this purpose?
I know that you can usuall tell when Windows was installed by the creation date of C:\Windows
foxkm
