> The point isn't to make it work *now*, but getting it to *stay* work. Since the only thing that can change to affect the outcome of the script or program is the value of CONFIG_HZ, isn't knowing that it works within a range of any reasonable values to set CONFIG_HZ to enough to know that it will stay working? I just tested again using the bc script and my C program, and this time I tested every possible value up to 100000, and they both still matched output. It doesn't seem like there's something that would cause the C program to stop working in the future due to precision issues.
