From owner-cvs-doc@FreeBSD.ORG Tue Dec 5 16:14:47 2006 Return-Path: X-Original-To: cvs-doc@freebsd.org Delivered-To: cvs-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2AAB416A5BD; Tue, 5 Dec 2006 16:14:47 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA56C43E30; Tue, 5 Dec 2006 16:12:17 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.8/8.13.8/Debian-2) with ESMTP id kB5GCPDZ005143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Dec 2006 18:12:36 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.13.8/8.13.8) with ESMTP id kB5GCGoG003798; Tue, 5 Dec 2006 18:12:17 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.13.8/8.13.8/Submit) id kB5GCEOg003797; Tue, 5 Dec 2006 18:12:15 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Tue, 5 Dec 2006 18:12:14 +0200 From: Giorgos Keramidas To: Dmitry Morozovsky Message-ID: <20061205161214.GB3357@kobe.laptop> References: <200612041443.kB4EhpBG035838@repoman.freebsd.org> <4574A587.3050903@FreeBSD.org> <20061205135214.K72517@woozle.rinet.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VrqPEDrXMn8OVzN4" Content-Disposition: inline In-Reply-To: <20061205135214.K72517@woozle.rinet.ru> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.675, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.72, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: Doug Barton , doc-committers@freebsd.org, cvs-all@freebsd.org, cvs-doc@freebsd.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/install chapter.sgml X-BeenThere: cvs-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the doc and www trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 16:14:47 -0000 --VrqPEDrXMn8OVzN4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 2006-12-05 13:53, Dmitry Morozovsky wrote: > On Mon, 4 Dec 2006, Doug Barton wrote: > DB> > Log: > DB> > A class C network for 192.168.0.0/24 includes the address > DB> > range 192.168.0.0-192.168.0.255, not 192.168.0.0-192.168.255.255 > DB> > > DB> > Submitted by: Tom Van Looy > DB> > DB> In an ideal world, all references to Class [ABC] networks would > DB> disappear from our docs, and be replaced by their CIDR equivalents. > > There are suprisingly small number of such places. What do you think about the > patch attached? I'm not sure I like the appearance of "/24" in flowing text, but the patch builds fine. > Index: books/handbook/ppp-and-slip/chapter.sgml > =================================================================== > RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v > retrieving revision 1.173 > diff -u -r1.173 chapter.sgml > --- books/handbook/ppp-and-slip/chapter.sgml 30 May 2006 23:08:24 -0000 1.173 > +++ books/handbook/ppp-and-slip/chapter.sgml 5 Dec 2006 10:53:35 -0000 > @@ -760,7 +760,7 @@ > > For example, if you have three dialup customers, > fred, sam, and > - mary, that you route class C networks > + mary, that you route /24 CIDR networks > for, you would type the following: > > &prompt.root; ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-fred > @@ -827,7 +827,7 @@ > should also contain routing information for each static > IP user if required. The line below would add a route > for the 203.14.101.0 > - class C via the client's ppp link. > + /24 CIDR network via the client's ppp link. > > fred: > add 203.14.101.0 netmask 255.255.255.0 HISADDR Is there any way we can rephrase this to avoid having to use /24 in the middle of a sentence. How do the documentation texts of Cisco and other networking-related companies, which have a lot of texts about CIDR address ranges, deal with this? --VrqPEDrXMn8OVzN4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFdZpe1g+UGjGGA7YRAv/QAKCdNnjFAet/8RKJwta0LabG1k6FOACdEaX2 jem1ruFiztrR46V8c+39zXY= =mWDL -----END PGP SIGNATURE----- --VrqPEDrXMn8OVzN4--