Date: Tue, 8 Apr 2003 04:17:20 +0400 From: Alex Semenyaka <alexs@ratmir.ru> To: Bill Vermillion <bv@wjv.com> Cc: freebsd-hackers@freebsd.org Subject: Re: /bin/sh and BIG NUMBERS Message-ID: <20030408001720.GA18260@snark.ratmir.ru> In-Reply-To: <20030406213453.GB4780@wjv.com> References: <20030406190054.AA08537B404@hub.freebsd.org> <20030406213453.GB4780@wjv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 06, 2003 at 05:34:53PM -0400, Bill Vermillion wrote: > >> alexs@snark> /bin/sh -c 'echo $((10000000000-1))' > Not all shells have that problem. I'm using the real KSH from AT&T > via the ports. It's returns 999999999 quite nicely :-) Thanks, and sure I know it. I've check different shells before patching /bin/sh. That's not enough that there are shells which do not suffer from the problem described above. The REAL problem is that NOW we have 64-bit counters in ipfw, we have lots-of-gigs harddrives and so on. And some people continue to use OWN OLD scripts (i.e. for system maintenance) which will NOW silently produce just wrong results. That's why I suggest to fix /bin/sh. SY, Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030408001720.GA18260>