public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Francisco Blas Izquierdo Riera" <klondike@xiscosoft.es>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-docs:master commit in: html/, xml/
Date: Fri, 18 Feb 2011 07:10:06 +0000 (UTC)	[thread overview]
Message-ID: <41a5e07255359938c67683a5bbf0bbf98b7376ea.klondike@gentoo> (raw)

commit:     41a5e07255359938c67683a5bbf0bbf98b7376ea
Author:     klondike <klondike <AT> xiscosoft <DOT> es>
AuthorDate: Fri Feb 18 07:10:06 2011 +0000
Commit:     Francisco Blas Izquierdo Riera <klondike <AT> xiscosoft <DOT> es>
CommitDate: Fri Feb 18 07:10:06 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-docs.git;a=commit;h=41a5e072

Forgot to add some input marks.

---
 html/hardenedfaq.html |   14 +++++++-------
 xml/hardenedfaq.xml   |   14 +++++++-------
 2 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/html/hardenedfaq.html b/html/hardenedfaq.html
index 3ecd556..381fafc 100644
--- a/html/hardenedfaq.html
+++ b/html/hardenedfaq.html
@@ -135,7 +135,7 @@ You can use <span class="code" dir="ltr">gcc-config</span> to accomplish this:
 <a name="doc_chap2_pre1"></a><table class="ntable" width="100%" cellspacing="0" cellpadding="0" border="0">
 <tr><td bgcolor="#7a5ada"><p class="codetitle">Code Listing2.1: Example gcc-config output</p></td></tr>
 <tr><td bgcolor="#eeeeff" align="left" dir="ltr"><pre>
-# gcc-config -l 
+# <span class="code-input">gcc-config -l</span>
  [1] x86_64-pc-linux-gnu-4.4.4 *
  [2] x86_64-pc-linux-gnu-4.4.4-hardenednopie
  [3] x86_64-pc-linux-gnu-4.4.4-hardenednopiessp
@@ -143,13 +143,13 @@ You can use <span class="code" dir="ltr">gcc-config</span> to accomplish this:
  [5] x86_64-pc-linux-gnu-4.4.4-vanilla
  
 <span class="code-comment">To turn off PIE building switch to the hardenednopie profile:</span>
-# gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednopie
+# <span class="code-input">gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednopie</span>
 <span class="code-comment">To turn off SSP building switch to the hardenednossp profile:</span>
-# gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednossp
+# <span class="code-input">gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednossp</span>
 <span class="code-comment">To turn off SSP and PIE building switch to the hardenednopiessp profile:</span>
-# gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednopiessp
+# <span class="code-input">gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednopiessp</span>
 <span class="code-comment">To turn off all hardened building switch to the vanilla profile:</span>
-# gcc-config x86_64-pc-linux-gnu-4.4.4-vanilla
+# <span class="code-input">gcc-config x86_64-pc-linux-gnu-4.4.4-vanilla</span>
 </pre></td></tr>
 </table>
 <table class="ncontent" width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td bgcolor="#bbffbb"><p class="note"><b>Note: </b>
@@ -262,14 +262,14 @@ toolchain so that you have a consistent base:
 <tr><td bgcolor="#eeeeff" align="left" dir="ltr"><pre>
 # <span class="code-input">emerge --oneshot binutils gcc virtual/libc</span>
 <span class="code-comment">Make sure the hardened toolchain is being used (gcc version may vary):</span>
-# gcc-config -l 
+# <span class="code-input">gcc-config -l</span>
  [1] x86_64-pc-linux-gnu-4.4.4 *
  [2] x86_64-pc-linux-gnu-4.4.4-hardenednopie
  [3] x86_64-pc-linux-gnu-4.4.4-hardenednopiessp
  [4] x86_64-pc-linux-gnu-4.4.4-hardenednossp
  [5] x86_64-pc-linux-gnu-4.4.4-vanilla
 <span class="code-comment">If the hardened version isn't chosen select it</span>
-# gcc-config x86_64-pc-linux-gnu-4.4.4
+# <span class="code-input">gcc-config x86_64-pc-linux-gnu-4.4.4</span>
 <span class="code-comment">Keep emerging the system</span>
 # <span class="code-input">emerge -e --keep-going system</span>
 # <span class="code-input">emerge -e --keep-going world</span>

diff --git a/xml/hardenedfaq.xml b/xml/hardenedfaq.xml
index f17ca22..a424dfb 100644
--- a/xml/hardenedfaq.xml
+++ b/xml/hardenedfaq.xml
@@ -143,7 +143,7 @@ off and on of the toolchain. To access the specs as the end user you can use the
 You can use <c>gcc-config</c> to accomplish this:
 </p>
 <pre caption="Example gcc-config output">
-# gcc-config -l 
+# <i>gcc-config -l</i>
  [1] x86_64-pc-linux-gnu-4.4.4 *
  [2] x86_64-pc-linux-gnu-4.4.4-hardenednopie
  [3] x86_64-pc-linux-gnu-4.4.4-hardenednopiessp
@@ -151,13 +151,13 @@ You can use <c>gcc-config</c> to accomplish this:
  [5] x86_64-pc-linux-gnu-4.4.4-vanilla
  
 <comment>To turn off PIE building switch to the hardenednopie profile:</comment>
-# gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednopie
+# <i>gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednopie</i>
 <comment>To turn off SSP building switch to the hardenednossp profile:</comment>
-# gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednossp
+# <i>gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednossp</i>
 <comment>To turn off SSP and PIE building switch to the hardenednopiessp profile:</comment>
-# gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednopiessp
+# <i>gcc-config x86_64-pc-linux-gnu-4.4.4-hardenednopiessp</i>
 <comment>To turn off all hardened building switch to the vanilla profile:</comment>
-# gcc-config x86_64-pc-linux-gnu-4.4.4-vanilla
+# <i>gcc-config x86_64-pc-linux-gnu-4.4.4-vanilla</i>
 </pre>
 
 <note>
@@ -301,14 +301,14 @@ toolchain so that you have a consistent base:
 <pre caption="Switch to hardened toolchain">
 # <i>emerge --oneshot binutils gcc virtual/libc</i>
 <comment>Make sure the hardened toolchain is being used (gcc version may vary):</comment>
-# gcc-config -l 
+# <i>gcc-config -l</i>
  [1] x86_64-pc-linux-gnu-4.4.4 *
  [2] x86_64-pc-linux-gnu-4.4.4-hardenednopie
  [3] x86_64-pc-linux-gnu-4.4.4-hardenednopiessp
  [4] x86_64-pc-linux-gnu-4.4.4-hardenednossp
  [5] x86_64-pc-linux-gnu-4.4.4-vanilla
 <comment>If the hardened version isn't chosen select it</comment>
-# gcc-config x86_64-pc-linux-gnu-4.4.4
+# <i>gcc-config x86_64-pc-linux-gnu-4.4.4</i>
 <comment>Keep emerging the system</comment>
 # <i>emerge -e --keep-going system</i>
 # <i>emerge -e --keep-going world</i>



             reply	other threads:[~2011-02-18  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18  7:10 Francisco Blas Izquierdo Riera [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-17 19:52 [gentoo-commits] proj/hardened-docs:master commit in: html/, xml/ Michael Palimaka
2011-06-01 19:57 Sven Vermeulen
2011-02-06 15:43 Francisco Blas Izquierdo Riera

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=41a5e07255359938c67683a5bbf0bbf98b7376ea.klondike@gentoo \
    --to=klondike@xiscosoft.es \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@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