aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/articles/remote-install/article.xml
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/articles/remote-install/article.xml')
-rw-r--r--en_US.ISO8859-1/articles/remote-install/article.xml111
1 files changed, 47 insertions, 64 deletions
diff --git a/en_US.ISO8859-1/articles/remote-install/article.xml b/en_US.ISO8859-1/articles/remote-install/article.xml
index 8c520bfa30..e0e3c1280a 100644
--- a/en_US.ISO8859-1/articles/remote-install/article.xml
+++ b/en_US.ISO8859-1/articles/remote-install/article.xml
@@ -1,22 +1,16 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
- "../../../share/xml/freebsd45.dtd">
-
-<article lang='en'>
- <articleinfo>
- <title>Remote Installation of the &os; Operating System without a
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+ "../../../share/xml/freebsd50.dtd">
+<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
+ <info><title>Remote Installation of the &os; Operating System without a
Remote Console</title>
+
- <author>
- <firstname>Daniel</firstname>
- <surname>Gerzo</surname>
- <affiliation>
+ <author><personname><firstname>Daniel</firstname><surname>Gerzo</surname></personname><affiliation>
<address><email>danger@FreeBSD.org</email></address>
- </affiliation>
- <!-- 11 April 2008 -->
- </author>
+ </affiliation></author>
- <legalnotice id="trademarks" role="trademarks">
+ <legalnotice xml:id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.general;
</legalnotice>
@@ -37,9 +31,9 @@
a collaboration with &a.mm.email; with valuable input provided by
&a.pjd.email;.</para>
</abstract>
- </articleinfo>
+ </info>
- <sect1 id="background">
+ <sect1 xml:id="background">
<title>Background</title>
<para>There are many server hosting providers in the world, but very
@@ -58,7 +52,7 @@
RAID-1 and <application>ZFS</application> capabilities.</para>
</sect1>
- <sect1 id="intro">
+ <sect1 xml:id="intro">
<title>Introduction</title>
<para>This section will summarize the purpose of this article and
@@ -68,8 +62,7 @@
<procedure>
<step>
- <para>As we have mentioned in the <link
- linkend="background">Background</link> section, many of the
+ <para>As we have mentioned in the <link linkend="background">Background</link> section, many of the
reputable server hosting companies provide some kind of rescue
system, which is booted from their <acronym>LAN</acronym> and
accessible over <application>SSH</application>. They usually
@@ -97,7 +90,7 @@
</step>
</procedure>
- <sect2 id="requirements">
+ <sect2 xml:id="requirements">
<title>Requirements</title>
<para>To continue successfully, you must:</para>
@@ -124,7 +117,7 @@
</sect2>
</sect1>
- <sect1 id="preparation">
+ <sect1 xml:id="preparation">
<title>Preparation - <application>mfsBSD</application></title>
<para>Before &os; may be installed on the target system, it is
@@ -140,8 +133,7 @@
entirely from a ramdisk. Thanks to this feature, the manipulation
of hard drives will not be limited, therefore it will be possible
to install a complete &os; operating system. The home page of
- <application>mfsBSD</application>, at <ulink
- url="http://people.freebsd.org/~mm/mfsbsd/"></ulink>, includes
+ <application>mfsBSD</application>, at <uri xlink:href="http://people.freebsd.org/~mm/mfsbsd/">http://people.freebsd.org/~mm/mfsbsd/</uri>, includes
pointers to the latest release of the toolset.</para>
<para>Please note that the internals of
@@ -156,10 +148,10 @@
<application>mfsBSD</application> scripts will reside:</para>
<screen>&prompt.root; <userinput>fetch http://people.freebsd.org/~mm/mfsbsd/mfsbsd-latest.tar.gz</userinput>
-&prompt.root; <userinput>tar xvzf mfsbsd-<replaceable>1.0-beta1</replaceable>.tar.gz</userinput>
-&prompt.root; <userinput>cd <replaceable>mfsbsd-1.0-beta1</replaceable>/</userinput></screen>
+&prompt.root; <userinput>tar xvzf mfsbsd-1.0-beta1.tar.gz</userinput>
+&prompt.root; <userinput>cd mfsbsd-1.0-beta1/</userinput></screen>
- <sect2 id="mfsbsd-config">
+ <sect2 xml:id="mfsbsd-config">
<title>Configuration of <application>mfsBSD</application></title>
<para>Before booting <application>mfsBSD</application>, a few
@@ -173,7 +165,7 @@
case.</para>
<para>Another important thing to set is the
- <username>root</username> password. This can be done by editing
+ <systemitem class="username">root</systemitem> password. This can be done by editing
the <filename>conf/rootpw.conf</filename> file. Please keep in
mind that the file will contain your password in the plain text,
thus we do not recommend to use real password here.
@@ -221,7 +213,7 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
</sect3>
</sect2>
- <sect2 id="mfsbsd-build">
+ <sect2 xml:id="mfsbsd-build">
<title>Building an <application>mfsBSD</application> image</title>
<para>The process of building an <application>mfsBSD</application>
@@ -229,26 +221,24 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
<para>The first step is to mount the &os; installation
<acronym>CD</acronym>, or the installation
- <acronym>ISO</acronym> image to <filename
- class="directory">/cdrom</filename>. For the sake of example,
+ <acronym>ISO</acronym> image to <filename>/cdrom</filename>. For the sake of example,
in this article we will assume that you have downloaded the &os;
7.0-RELEASE <acronym>ISO</acronym>. Mounting this ISO image to
- the <filename class="directory">/cdrom</filename> directory is
+ the <filename>/cdrom</filename> directory is
easy with the &man.mdconfig.8; utility:</para>
- <screen>&prompt.root; <userinput>mdconfig -a -t vnode -u 10 -f <replaceable>7.0-RELEASE-amd64-disc1.iso</replaceable></userinput>
+ <screen>&prompt.root; <userinput>mdconfig -a -t vnode -u 10 -f 7.0-RELEASE-amd64-disc1.iso</userinput>
&prompt.root; <userinput>mount_cd9660 /dev/md10 /cdrom</userinput></screen>
<para>Next, build the bootable <application>mfsBSD</application>
image:</para>
- <screen>&prompt.root; <userinput>make BASE=/cdrom/<replaceable>7.0-RELEASE</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>make BASE=/cdrom/7.0-RELEASE</userinput></screen>
<note>
<para>The above <command>make</command> command has to be run
from the top level of the <application>mfsBSD</application>
- directory tree, i.e. <filename
- class="directory">~/mfsbsd-1.0-beta1/</filename>.</para>
+ directory tree, i.e. <filename>~/mfsbsd-1.0-beta1/</filename>.</para>
</note>
</sect2>
@@ -266,7 +256,7 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
<para>To boot <application>mfsBSD</application> image properly, it
must be placed on the first (bootable) device of the given
machine. This may be accomplished using this example providing
- that <devicename>sda</devicename> is the first bootable disk
+ that <filename>sda</filename> is the first bootable disk
device:</para>
<screen>&prompt.root; <userinput>dd if=/root/disk.img of=/dev/sda bs=1m</userinput></screen>
@@ -276,11 +266,11 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
be rebooted. Watch for the machine to boot up properly with the
&man.ping.8; tool. Once it has came back on-line, it should be
possible to access it over &man.ssh.1; as user
- <username>root</username> with the configured password.</para>
+ <systemitem class="username">root</systemitem> with the configured password.</para>
</sect2>
</sect1>
- <sect1 id="installation">
+ <sect1 xml:id="installation">
<title>Installation of The &os; Operating System</title>
<para>The <application>mfsBSD</application> has been successfully
@@ -304,7 +294,7 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
<para>At the start, mark all system disks as empty. Repeat the
following command for each hard drive:</para>
- <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/<replaceable>ad0</replaceable> count=2</userinput></screen>
+ <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad0 count=2</userinput></screen>
<para>Next, create slices and label them with your preferred tool.
While it is considered easier to use
@@ -312,15 +302,12 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
probably less buggy method will be to use standard text-based
&unix; tools, such as &man.fdisk.8; and &man.bsdlabel.8;, which
will also be covered in this section. The former option is well
- documented in the <ulink
- url="&url.books.handbook;/install-steps.html">Installing &os;</ulink>
+ documented in the <link xlink:href="&url.books.handbook;/install-steps.html">Installing &os;</link>
chapter of the &os; Handbook. As it was mentioned in the
introduction, this article will present how to set up a system
with RAID-1 and <application>ZFS</application> capabilities.
Our set up will consist of a small &man.gmirror.8; mirrored
- <filename class="directory">/</filename> (root), <filename
- class="directory">/usr</filename> and <filename
- class="directory">/var</filename> file systems, and the rest of
+ <filename>/</filename> (root), <filename>/usr</filename> and <filename>/var</filename> file systems, and the rest of
the disk space will be allocated for a &man.zpool.8; mirrored
<application>ZFS</application> file system. Please note, that
the <application>ZFS</application> file system will be
@@ -332,17 +319,17 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
create a <application>UFS2</application> file system in each
mirrored partition:</para>
- <screen>&prompt.root; <userinput>fdisk -BI /dev/ad0</userinput> <co id="fdisk"/>
+ <screen>&prompt.root; <userinput>fdisk -BI /dev/ad0</userinput> <co xml:id="fdisk"/>
&prompt.root; <userinput>fdisk -BI /dev/ad1</userinput>
-&prompt.root; <userinput>bsdlabel -wB /dev/ad0s1</userinput> <co id="bsdlabel-writing"/>
+&prompt.root; <userinput>bsdlabel -wB /dev/ad0s1</userinput> <co xml:id="bsdlabel-writing"/>
&prompt.root; <userinput>bsdlabel -wB /dev/ad1s1</userinput>
-&prompt.root; <userinput>bsdlabel -e /dev/ad0s1</userinput> <co id="bsdlabel-editing"/>
-&prompt.root; <userinput>bsdlabel /dev/ad0s1 > /tmp/bsdlabel.txt &amp;&amp; bsdlabel -R /dev/ad1s1 /tmp/bsdlabel.txt</userinput> <co id="bsdlabel-restore"/>
-&prompt.root; <userinput>gmirror label root /dev/ad[01]s1a</userinput> <co id="gmirror1"/>
+&prompt.root; <userinput>bsdlabel -e /dev/ad0s1</userinput> <co xml:id="bsdlabel-editing"/>
+&prompt.root; <userinput>bsdlabel /dev/ad0s1 &gt; /tmp/bsdlabel.txt &amp;&amp; bsdlabel -R /dev/ad1s1 /tmp/bsdlabel.txt</userinput> <co xml:id="bsdlabel-restore"/>
+&prompt.root; <userinput>gmirror label root /dev/ad[01]s1a</userinput> <co xml:id="gmirror1"/>
&prompt.root; <userinput>gmirror label var /dev/ad[01]s1d</userinput>
&prompt.root; <userinput>gmirror label usr /dev/ad[01]s1e</userinput>
-&prompt.root; <userinput>gmirror label -F swap /dev/ad[01]s1b</userinput> <co id="gmirror2"/>
-&prompt.root; <userinput>newfs /dev/mirror/root</userinput> <co id="newfs"/>
+&prompt.root; <userinput>gmirror label -F swap /dev/ad[01]s1b</userinput> <co xml:id="gmirror2"/>
+&prompt.root; <userinput>newfs /dev/mirror/root</userinput> <co xml:id="newfs"/>
&prompt.root; <userinput>newfs /dev/mirror/var</userinput>
&prompt.root; <userinput>newfs /dev/mirror/usr</userinput></screen>
@@ -363,12 +350,10 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
<para>Now, manually edit the label of the given disk. Refer
to the &man.bsdlabel.8; manual page in order to find out how
to create partitions. Create partitions
- <literal>a</literal> for <filename
- class="directory">/</filename> (root) file system,
+ <literal>a</literal> for <filename>/</filename> (root) file system,
<literal>b</literal> for swap, <literal>d</literal> for
- <filename class="directory">/var</filename>,
- <literal>e</literal> for <filename
- class="directory">/usr</filename> and finally
+ <filename>/var</filename>,
+ <literal>e</literal> for <filename>/usr</filename> and finally
<literal>f</literal> which will later be used for
<application>ZFS</application>.</para>
</callout>
@@ -417,8 +402,7 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
menu. Select <guimenuitem>Options</guimenuitem> and press
<keycap>Enter</keycap>. With the help of arrow keys, move the
cursor on the <literal>Install Root</literal> item, press
- <keycap>Space</keycap> and change it to <filename
- class="directory">/mnt</filename>. Press
+ <keycap>Space</keycap> and change it to <filename>/mnt</filename>. Press
<keycap>Enter</keycap> to submit your changes and exit the
<guimenuitem>Options</guimenuitem> menu by pressing
<keycap>q</keycap>.</para>
@@ -475,7 +459,7 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
<itemizedlist>
<listitem>
<para>Copy the <literal>GENERIC</literal> kernel to the
- <filename class="directory">/boot/kernel</filename>
+ <filename>/boot/kernel</filename>
directory:</para>
<screen>&prompt.root; <userinput>cp -Rp /boot/GENERIC/* /boot/kernel</userinput></screen>
@@ -512,13 +496,13 @@ zfs_load="YES"</programlisting>
<application>ZFS</application> available on the next
boot:</para>
- <screen>&prompt.root; <userinput>echo 'zfs_enable="YES"' >> /etc/rc.conf </userinput></screen>
+ <screen>&prompt.root; <userinput>echo 'zfs_enable="YES"' &gt;&gt; /etc/rc.conf </userinput></screen>
</listitem>
<listitem>
<para>Add additional users to the system using the
&man.adduser.8; tool. Do not forget to add a user to the
- <groupname>wheel</groupname> group so you may obtain root
+ <systemitem class="groupname">wheel</systemitem> group so you may obtain root
access after the reboot.</para>
</listitem>
@@ -532,7 +516,7 @@ zfs_load="YES"</programlisting>
</sect2>
</sect1>
- <sect1 id="zfs">
+ <sect1 xml:id="zfs">
<title>ZFS</title>
<para>If your system survived the reboot, it should now be possible
@@ -556,8 +540,7 @@ zfs_load="YES"</programlisting>
&prompt.root; <userinput>zfs set mountpoint=/usr/src tank/src</userinput></screen>
<para>That's all. If you are interested in more details about
- <application>ZFS</application> on &os;, please refer to the <ulink
- url="http://wiki.freebsd.org/ZFS">ZFS</ulink> section of the &os;
+ <application>ZFS</application> on &os;, please refer to the <link xlink:href="http://wiki.freebsd.org/ZFS">ZFS</link> section of the &os;
Wiki.</para>
</sect1>
</article>