From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 7 17:17:23 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 790DD37B401 for ; Mon, 7 Apr 2003 17:17:23 -0700 (PDT) Received: from snark.ratmir.ru (snark.ratmir.ru [213.24.248.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63F5243F3F for ; Mon, 7 Apr 2003 17:17:22 -0700 (PDT) (envelope-from freebsd@snark.ratmir.ru) Received: from snark.ratmir.ru (freebsd@localhost [127.0.0.1]) by snark.ratmir.ru (8.12.9/8.12.9) with ESMTP id h380HLDR018285; Tue, 8 Apr 2003 04:17:21 +0400 (MSD) (envelope-from freebsd@snark.ratmir.ru) Received: (from freebsd@localhost) by snark.ratmir.ru (8.12.9/8.12.9/Submit) id h380HKJf018284; Tue, 8 Apr 2003 04:17:20 +0400 (MSD) Date: Tue, 8 Apr 2003 04:17:20 +0400 From: Alex Semenyaka To: Bill Vermillion Message-ID: <20030408001720.GA18260@snark.ratmir.ru> References: <20030406190054.AA08537B404@hub.freebsd.org> <20030406213453.GB4780@wjv.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030406213453.GB4780@wjv.com> User-Agent: Mutt/1.5.4i cc: freebsd-hackers@freebsd.org Subject: Re: /bin/sh and BIG NUMBERS X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2003 00:17:23 -0000 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