From owner-freebsd-doc@FreeBSD.ORG Thu Sep 4 15:04:26 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AE3A16A4BF for ; Thu, 4 Sep 2003 15:04:26 -0700 (PDT) Received: from shaft.techsupport.co.uk (shaft.techsupport.co.uk [212.250.77.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 749D543F93 for ; Thu, 4 Sep 2003 15:04:25 -0700 (PDT) (envelope-from setantae@submonkey.net) Received: from pc3-cdif2-5-cust222.cdif.cable.ntl.com ([81.101.152.222] helo=shrike.submonkey.net ident=mailnull) by shaft.techsupport.co.uk with esmtp (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.20) id 19v2DH-0005PC-Rq for doc@FreeBSD.org; Thu, 04 Sep 2003 23:04:24 +0100 Received: from setantae by shrike.submonkey.net with local (Exim 4.22) id 19v2DF-0009EF-Si for doc@FreeBSD.org; Thu, 04 Sep 2003 23:04:21 +0100 Date: Thu, 4 Sep 2003 23:04:21 +0100 From: Ceri Davies To: doc@FreeBSD.org Message-ID: <20030904220421.GR25063@submonkey.net> Mail-Followup-To: Ceri Davies , doc@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="35rzUHtxHARXKmYf" Content-Disposition: inline X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.4i Sender: Ceri Davies Subject: 3 line diff creates 700 line whitespace diff problem X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Sep 2003 22:04:26 -0000 --35rzUHtxHARXKmYf Content-Type: multipart/mixed; boundary="McQJJYUzjTUqtsGv" Content-Disposition: inline --McQJJYUzjTUqtsGv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable jon@witchspace.com pointed out to me that the section numbers in the IPsec section of the handbook are slightly off: 10.9.4 and 10.9.5 should really be 10.9.3.1 and 10.9.3.2. My dilemma is that committing the attached patch to correct this will also require that all the intervening lines (~700 of them) will need to be indented to keep the whitespace consistent. Would a whitespace commit of that proportion be excessive, or a necessary evil? Ceri --=20 User: DO YOU ACCEPT JESUS CHRIST AS YOUR PERSONAL LORD AND SAVIOR? Iniaes: Sure, I can accept all forms of payment. -- www.chatterboxchallenge.com --McQJJYUzjTUqtsGv Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ipsec-sections.diff" Content-Transfer-Encoding: quoted-printable Index: chapter.sgml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/security/chapter.sg= ml,v retrieving revision 1.182 diff -u -r1.182 chapter.sgml --- chapter.sgml 1 Sep 2003 23:11:15 -0000 1.182 +++ chapter.sgml 4 Sep 2003 21:58:06 -0000 @@ -3145,9 +3145,8 @@ VPN. - =20 - + Step 1: Creating and testing a <quote>virtual</quote> network link =20 @@ -3379,9 +3378,9 @@ reversing the order of IP addresses. - + =20 - + Step 2: Securing the link =20 To secure the link we will be using IPsec. IPsec provides @@ -3814,6 +3813,7 @@ running. Machines on each network will be able to refer to one another using IP addresses, and all traffic across the link will be automatically and securely encrypted. + =20 =20 =20 --McQJJYUzjTUqtsGv-- --35rzUHtxHARXKmYf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/V7blocfcwTS3JF8RAl2gAJ9xtvF+AubfDU7ZN6euiajEMDaCtACfSTvx +ZeYARO1hi+25WJsWKLDs7M= =mro1 -----END PGP SIGNATURE----- --35rzUHtxHARXKmYf--