From owner-freebsd-current@FreeBSD.ORG Sat Apr 16 18:56:04 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF9A516A4CE for ; Sat, 16 Apr 2005 18:56:04 +0000 (GMT) Received: from fast.dnswatch.com (fast.dnswatch.com [216.177.243.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4CA043D3F for ; Sat, 16 Apr 2005 18:56:03 +0000 (GMT) (envelope-from null@dnswatch.com) Received: from fast.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.12.6/8.12.6) with ESMTP id j3GIu0sm096385 for ; Sat, 16 Apr 2005 11:56:03 -0700 (PDT) (envelope-from null@dnswatch.com) Received: (from www@localhost) by fast.dnswatch.com (8.12.6/8.12.6/Submit) id j3GItxOq096384; Sat, 16 Apr 2005 11:55:59 -0700 (PDT) (envelope-from null@dnswatch.com) X-Authentication-Warning: fast.dnswatch.com: www set sender to null@dnswatch.com using -f Received: from mail.1command.com ([216.177.243.35]) (DNSwatch.com_WebMail authenticated user null) by webmail.dnswatch.com with HTTP; Sat, 16 Apr 2005 11:55:58 -0700 (PDT) Message-ID: <50589.216.177.243.35.1113677758.localmail@webmail.dnswatch.com> In-Reply-To: <13591.1113660644@bizet.nethelp.no> References: <4261185D.1060202@gamersimpact.com> <13591.1113660644@bizet.nethelp.no> Date: Sat, 16 Apr 2005 11:55:58 -0700 (PDT) From: "/dev/null" To: freebsd-current@freebsd.org User-Agent: DNSwatch.com_WebMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Re: strtonum(3) in FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2005 18:56:04 -0000 >> > K may so be 1024, but M may not, because M must be 1000000, >> > always. SI prefices are the same among all units. >> >> When talking about digital data storage K means times 2^10, M means >> times 2^20, G means 2^30 and T means 2^40. >> >> 1K = 1 * 2^10 bytes = 1024 bytes >> 1M = 1 * 2^20 bytes = 1048576 bytes >> 1G = 1 * 2^30 bytes = 1073741824 bytes > > The disk drive manufacturers seem to disagree with you. For instance > Seagate: > > http://www.seagate.com/products/discselect/glossary/index.html#cap > > "Most disc drive companies, including Seagate, calculate disc capacity > based on the assumption that 1 megabyte = 1000 kilobytes and 1 > gigabyte=1000 megabytes." > I don't know about you. But have you ever noticed how the capacity of your drive as reported by the manufacturers suddenly shrank after formatting it? Point being, they have always used the one which reported the *larger* capacity. ;) In short; the standard is... there is no standard. :) -Chris > My own conclusion is simply that there is no universal agreement which > says that kilo, mega, giga and tera mean something different (using > powers of 2) when applied to data storage. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > //////////////////////////////////////////////////// If only Western Electric had found a way to offer binary licenses for the UNIX system back in 1974, the UNIX system would be running on all PC's today rather than DOS/Windows. ////////////////////////////////////////////////////