public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: Josh Saddler <nightmorph@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: shb-services.xml
Date: Thu, 21 Jun 2007 03:31:26 +0000	[thread overview]
Message-ID: <E1I1DOI-0006Ou-AE@stork.gentoo.org> (raw)

nightmorph    07/06/21 03:31:26

  Modified:             shb-services.xml
  Log:
  cleanups for emerge --config and apache

Revision  Changes    Path
1.7                  xml/htdocs/doc/en/security/shb-services.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/security/shb-services.xml?rev=1.7&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/security/shb-services.xml?rev=1.7&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/security/shb-services.xml?r1=1.6&r2=1.7

Index: shb-services.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/security/shb-services.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- shb-services.xml	7 Mar 2007 02:24:17 -0000	1.6
+++ shb-services.xml	21 Jun 2007 03:31:26 -0000	1.7
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/security/shb-services.xml,v 1.6 2007/03/07 02:24:17 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/security/shb-services.xml,v 1.7 2007/06/21 03:31:26 nightmorph Exp $ -->
 <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
 
 <!-- The content of this document is licensed under the CC-BY-SA license -->
@@ -7,17 +7,17 @@
 
 <sections>
 
-<version>1.2</version>
-<date>2006-12-01</date>
+<version>1.3</version>
+<date>2007-06-20</date>
 
 <section>
 <title>Apache</title>
 <body>
 
 <p>
-Apache (1.3.26) comes with a pretty decent configuration file but again, we need
-to improve some things, like binding Apache to one address and preventing it
-from leaking information. Below are the options that you should apply the
+Apache comes with a pretty decent configuration file but again, we need to
+improve some things, like binding Apache to one address and preventing it from
+leaking information. Below are the options that you should apply the
 configuration file.
 </p>
 
@@ -77,10 +77,10 @@
 </p>
 
 <pre caption="Chrooting BIND">
-ebuild /var/db/pkg/net-dns/bind-9.2.2-r2/bind-9.2.2-r2.ebuild config\`"
+# <i>emerge --config bind</i>
 <comment>(Before running the above command you might want to change the chroot
 directory in /etc/conf.d/named. Otherwise /chroot/dns will be used.)</comment>
-<comment>(You might need to substitute the version number with the current version number )</comment>
+
 </pre>
 </body>
 </section>



-- 
gentoo-doc-cvs@gentoo.org mailing list



             reply	other threads:[~2007-06-21  3:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21  3:31 Josh Saddler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-13 20:02 [gentoo-doc-cvs] cvs commit: shb-services.xml Sven Vermeulen
2007-07-08 21:31 Josh Saddler
2007-03-07  2:24 Josh Saddler
2006-12-02  0:36 Josh Saddler
2006-03-11 16:44 swift

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1I1DOI-0006Ou-AE@stork.gentoo.org \
    --to=nightmorph@stork.gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox