> > That seemed counter-productive. Do we really want to have to privately > > mimick that functionality? > > No, but warp_clock() will change the time, so it would be a bad > side-effect for a module to recreate. Right - it changes the meaning of the value passed into the function, so a module would have to privately consider whether it also needs to change that value. > It's only called, typically, > during boot when setting the timezone. But it is called from user space, presumably after compiled-in modules are initialized. So by leaving the hook there, we are in effect saying "erroneous values can be passed in exactly once, but we're ok with that." Right?
This archive was generated by hypermail 2b30 : Mon Dec 01 2003 - 12:01:13 PST