diff options
Diffstat (limited to 'en_US.ISO8859-1/articles/vinum/article.sgml')
| -rw-r--r-- | en_US.ISO8859-1/articles/vinum/article.sgml | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/en_US.ISO8859-1/articles/vinum/article.sgml b/en_US.ISO8859-1/articles/vinum/article.sgml index 118e9a9af4..f3905df3e9 100644 --- a/en_US.ISO8859-1/articles/vinum/article.sgml +++ b/en_US.ISO8859-1/articles/vinum/article.sgml @@ -552,7 +552,7 @@ performance disk server at a very reasonable cost.</para> <para>However, you can indeed get started with - <application>Vinum</application> very simply. + <application>Vinum</application> very simply. A minimum system can be as simple as an old CPU (even a 486 is fine) and a pair of drives that are 500 MB or more. They need not be the same size or @@ -594,7 +594,7 @@ for the server against available resources and make design tradeoffs. We will plan the transition from no - <application>Vinum</application> to + <application>Vinum</application> to <application>Vinum</application> on just one spindle, to <application>Vinum</application> on two spindles.</para> @@ -1075,7 +1075,7 @@ Not to scale</literallayout> allocations as described above in <xref linkend="AssignSmall"/>. For this example on a 2 GB spindle, I will use 200,000 blocks for root, 200,265 blocks for swap, - 1,000,000 blocks for <filename>/home</filename>, and + 1,000,000 blocks for <filename>/home</filename>, and the rest of the spindle (2,724,408 blocks) for <filename>/usr</filename>. (<command>/stand/sysinstall</command> @@ -1239,7 +1239,7 @@ Not to scale</literallayout> <step> <para>We now need to install new spindle partitioning for <devicename>/dev/ad0</devicename>. - This requires that + This requires that <devicename>/dev/ad0s1b</devicename> not be in use for swapping so we have to reboot in single-user mode.</para> @@ -1575,7 +1575,7 @@ expected next file 492, got 491</screen> <application>Vinum</application> may automatically avoid failed hardware in a way that users do not notice. - You must watch for such failures and get them repaired before a + You must watch for such failures and get them repaired before a second failure results in data loss. You may see <application>Vinum</application> noting damaged objects @@ -1610,7 +1610,7 @@ expected next file 492, got 491</screen> sd name hope.p0.s0 drive UpWindow plex hope.p0 len 0</programlisting> <note> - <para>Specifying a length of <literal>0</literal> for + <para>Specifying a length of <literal>0</literal> for the <filename>hope.p0.s0</filename> subdisk asks <application>Vinum</application> to use whatever space is left available on the underlying @@ -1672,7 +1672,7 @@ expected next file 492, got 491</screen> For each scenario, there is a subsection on how to configure your server for degraded mode operation, how to recover from the failure, how to exit degraded mode, and how to simulate the failure.</para> - + <tip> <para>Make a hard copy of these instructions and leave them inside the CPU case, being careful not to interfere with ventilation.</para></tip> @@ -1812,7 +1812,7 @@ ok <userinput>boot -as</userinput></screen> <title>Simulation</title> <para>This kind of failure can be simulated by shutting down to - single-user mode and then booting as shown above in + single-user mode and then booting as shown above in <xref linkend="enter1"/>.</para> </section> </section> @@ -1876,7 +1876,7 @@ ok <userinput>boot -s</userinput></screen> <procedure> <para>We assume here that your server is up and running multi-user in - degraded mode on just + degraded mode on just <devicename>/dev/ad0</devicename> and that you have a new spindle now on <devicename>/dev/ad2</devicename> ready to go.</para> @@ -2096,7 +2096,7 @@ use strict; use FileHandle; my $config_tag1 = '$Id: article.sgml,v 1.17 2012-03-20 08:56:30 pluknet Exp $'; -# Copyright (C) 2001 Robert A. Van Valzah +# Copyright (C) 2001 Robert A. Van Valzah # # Bootstrap Vinum # |