From owner-freebsd-doc@FreeBSD.ORG Sat May 17 05:30:40 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0228EAB2; Sat, 17 May 2014 05:30:40 +0000 (UTC) Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA5672023; Sat, 17 May 2014 05:30:39 +0000 (UTC) Received: by mail-qg0-f47.google.com with SMTP id j107so5668642qga.34 for ; Fri, 16 May 2014 22:30:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=FkO/tiA9kwN3Wn+hJATYh8wzePUYVNKhIy2332qCdXo=; b=xZK2jWVQ82b2QwIvNlhIr62gbdg6Y2h3Gx08/6xDoz0tdE6dxruVCLdiH5vL9alwdA rULyp+UQxBp4OKmN3l6jxK1L0+8Zzge6o4XBQkU5PNNO6IQnQSVn6GVT1JDE0ILJDz/b qETB3JHG1ZHHracX3lj0BHDYvUbEUW0VNda1+EIx2IQX255DXia0HM2LMrQ8ivknEErX fO7NMeB7+A+Wf6ggw7Vv2/jTMRTn6Ct/eg+upjZyTP+NDwda1UCBWn1OYZBT7vyioZC4 kgnWkYxtTWfUgrcNI44CecpsKoHdvu49NfZqf3mBXRgwTpMwhWpHbA2/ncE9fmaEHjJM hixA== X-Received: by 10.224.129.66 with SMTP id n2mr29586287qas.55.1400304638726; Fri, 16 May 2014 22:30:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.92.177 with HTTP; Fri, 16 May 2014 22:30:18 -0700 (PDT) Reply-To: mtk.manpages@gmail.com In-Reply-To: <201405170408.s4H48Xff021996@freefall.freebsd.org> References: <201405170408.s4H48Xff021996@freefall.freebsd.org> From: "Michael Kerrisk (man-pages)" Date: Sat, 17 May 2014 07:30:18 +0200 Message-ID: Subject: Re: docs/188786: Bug in inet(3) man page (inet_aton()) To: bjk@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: freebsd-doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2014 05:30:40 -0000 On Sat, May 17, 2014 at 6:08 AM, wrote: > Synopsis: Bug in inet(3) man page (inet_aton()) > > State-Changed-From-To: open->closed > State-Changed-By: bjk > State-Changed-When: Sat May 17 04:06:45 UTC 2014 > State-Changed-Why: > I do not believe this is a bug. > > The text is just referring to an IP address when it says > "network address", and the class-A addressing scheme is just > taking the three octets from the second component and putting > them as the last three octets of the IPv4 address. > In the nearby portions of this document, "network address" > is also referring to just an IPv4 address. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=188786 Ben, Okay -- I see what you mean--I was focused on that one piece, and didn't note the other uses of "network address". I think that what makes the page a little confusing is that it uses both terms "Internet address" and "network address" without making it clear that they are synonymous (and thus leaving the potential for the reader to think they are not). This might not normally be problematic, but given that the page is also talking about the 'network' and 'host' components of the address, there is scope for confusion. Not a big thing, I guess, but FWIW that's the confusion that I tried to avoid in the Linux man page by using the term "binary address"; see http://man7.org/linux/man-pages/man3/inet.3.html#DESCRIPTION Cheers, Michael