public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lukasz Damentko <rane@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: lpi-101-intermediate-p3.xml
Date: Tue, 19 Jun 2007 22:10:17 +0000	[thread overview]
Message-ID: <E1I0ltx-00067S-Jk@stork.gentoo.org> (raw)

rane        07/06/19 22:10:17

  Modified:             lpi-101-intermediate-p3.xml
  Log:
  there were two identical <p>s, thanks to akroplas for spotting this

Revision  Changes    Path
1.3                  xml/htdocs/doc/en/articles/lpi-101-intermediate-p3.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/articles/lpi-101-intermediate-p3.xml?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/articles/lpi-101-intermediate-p3.xml?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/articles/lpi-101-intermediate-p3.xml?r1=1.2&r2=1.3

Index: lpi-101-intermediate-p3.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/lpi-101-intermediate-p3.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- lpi-101-intermediate-p3.xml	1 Jan 2006 11:09:38 -0000	1.2
+++ lpi-101-intermediate-p3.xml	19 Jun 2007 22:10:17 -0000	1.3
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/lpi-101-intermediate-p3.xml,v 1.2 2006/01/01 11:09:38 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/lpi-101-intermediate-p3.xml,v 1.3 2007/06/19 22:10:17 rane Exp $ -->
 
 <guide link="/doc/en/articles/lpi-101-intermediate-p3.xml" disclaimer="articles">
 <title>LPI certification 101 (release 2) exam prep, Part 3</title>
@@ -26,8 +26,8 @@
 document is an updated version of the original article, and contains
 various improvements made by the Gentoo Linux Documentation team -->
 
-<version>1.0</version>
-<date>2005-12-11</date>
+<version>1.1</version>
+<date>2007-06-20</date>
 
 <chapter>
 <title>Before You Start</title>
@@ -697,16 +697,6 @@
 root is allowed to update it or delete it.
 </p>
 
-<p>
-Above, the r means that reading (looking at the data in the file) is allowed,
-the w means that writing (modifying the file, as well as deletion) is allowed,
-and the x means that "execute" (running the program) is allowed. Putting
-together all this information, we can see that everyone is able to read the
-contents of and execute this file, but only the owner (root) is allowed to
-modify this file in any way. So, while normal users can copy this file, only
-root is allowed to update it or delete it.
-</p>
-
 </body>
 </section>
 <section>



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



             reply	other threads:[~2007-06-19 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 22:10 Lukasz Damentko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-01 11:09 [gentoo-doc-cvs] cvs commit: lpi-101-intermediate-p3.xml Lukasz Damentko

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=E1I0ltx-00067S-Jk@stork.gentoo.org \
    --to=rane@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