From: Sven Vermeulen <swift@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: lvm2.xml
Date: Fri, 23 May 2008 19:49:18 +0000 [thread overview]
Message-ID: <E1JzdGQ-0000tN-RS@stork.gentoo.org> (raw)
swift 08/05/23 19:49:18
Modified: lvm2.xml
Log:
Coding style
Revision Changes Path
1.24 xml/htdocs/doc/en/lvm2.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/lvm2.xml?rev=1.24&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/lvm2.xml?rev=1.24&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/lvm2.xml?r1=1.23&r2=1.24
Index: lvm2.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/lvm2.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- lvm2.xml 3 Nov 2007 21:14:55 -0000 1.23
+++ lvm2.xml 23 May 2008 19:49:18 -0000 1.24
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/lvm2.xml,v 1.23 2007/11/03 21:14:55 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/lvm2.xml,v 1.24 2008/05/23 19:49:18 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/lvm2.xml">
@@ -114,7 +114,7 @@
<body>
<p>
-Follow the handbook, but with the following amendments to chapter <e>4.
+Follow the handbook, but with the following amendments to chapter <e>4.
Preparing the Disks</e>:
</p>
@@ -145,11 +145,11 @@
</p>
<note>
-It is <b>not</b> recommended to put the following directories in an
-LVM2 partition: <path>/etc</path>, <path>/lib</path>, <path>/mnt</path>,
-<path>/proc</path>, <path>/sbin</path>, <path>/dev</path>, and <path>/root</path>.
-This way, you would still be able to log into your system (crippled, but
-still somewhat usable, as root) if something goes terribly wrong.
+It is <b>not</b> recommended to put the following directories in an
+LVM2 partition: <path>/etc</path>, <path>/lib</path>, <path>/mnt</path>,
+<path>/proc</path>, <path>/sbin</path>, <path>/dev</path>, and
+<path>/root</path>. This way, you would still be able to log into your system
+(crippled, but still somewhat usable, as root) if something goes terribly wrong.
</note>
<p>
--
gentoo-doc-cvs@lists.gentoo.org mailing list
next reply other threads:[~2008-05-23 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 19:49 Sven Vermeulen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-03 21:14 [gentoo-doc-cvs] cvs commit: lvm2.xml Josh Saddler
2006-04-19 21:39 Shyam Mani
2006-02-17 2:53 Lukasz Damentko
2006-02-06 17:12 Xavier Neys
2006-01-20 11:42 Xavier Neys
2005-10-03 22:49 Lukasz Damentko
2005-09-23 13:57 Xavier Neys
2005-08-16 22:30 Xavier Neys
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=E1JzdGQ-0000tN-RS@stork.gentoo.org \
--to=swift@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