Problem statement :  Further to as explained ...illustrated in
                         opportunityi_innovative_time_stamp_CMOS_clocks.txt

In the context of unix operating sytem ...timestamp is usually the current
cloak cycle of the CPU.

                     Understand systems using multi processors ...specifically
                     those that implement symmetric multi processor ....
                     SMP guarantee that the current clock cycle of any of the
                     CPU is same (viz. the counter yields the same number on
                     all the cpu's at any given point of time) ...ability to
                     increase the number or instructions executed for a unit
                     value (milli or micro seconds) ...with out disturbing 
                     or harming the integrity of the timekeeping.

Opportunity : Innovative timestamp design...

               ....in relation to unix ...what microsoft or alike operating systems
               viz. given the context that it reads or uses a CMOS based clock or
               a seperate timekeeper ...maintain the time ...while precision is lost
               ...the flexibility is that the system can go down (total shutdown)
               and still be brought up ...as the clock powered by battery keeps the
               time.

               gain the precision of timestamp and also ....[benefits as usually
               found in systems using a CMOS clock] ...some use-case modelling to be
               applied.

               ...use a multiple processor's in the CPU ...instead of keeping 
               the processor cloak cycle symmetric  ....choose one of the processors
               as a time-keeper ....vary the cloak cycle of the processor accordingly
               such that when timestamp (nitty gritties of keeping or maintaining the
               counter taken into account ...also any variable precision lost in converting
               or obtaining the timestamp in the desired format) is read from the
               timekeeper-processor (as good as having a CMOS clock) ....by any thread
               context ...being executed on the other processors ...should yield the
               precisive timestamp viz. translating into the cloak cycle of the processors
               executing the instructions.


               either this timekeeper-processor can be battery-powered when the system
               is brought down ...or onthe funnier side ...use a SMP (symmetric multi
               processors) ...and synchronize the processor cloak counter with the 
               time maintained by a CMOS clock ...every time the system is brought-up
               from a shutdown (may be a unix utility on the lines of 'sync' as part
               of the Operating system bootup ....to take care of synchronization of
               the time ...or reading or schronization of the time from timekeeper 
               machine ...usually termed Networkp-time-protocol servers) ...to schronize
               the processor cloak counter would be good proposition.
             
              ...adopted where feasible ....in computing systems (OS, databases),
              exploit the timestamp formats.


              It is clearly being envisioned above that ...terms are as for profit
              basis and absorption of labor ...with work on site (labor being located
              at point of location of systems and devices being maintained) by any one 
              choosing to make or utilize the above opportunity further to as described
              in the document projects.pdf.
              
              
Note: The above problem statement having been encountered in various scenarios
      and detailed in various 'Proof of concepts' as mentioned in 
      'http://uk.geocities.com/ravivenkatus/projects.pdf' ....apply appropriate
      'use-case' modeling, rationalize and arrive at a workable and feasible 
       solution both commercially and techinically viable.