<?xml version="1.0" encoding="UTF-8"?>
<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xl="http://www.w3.org/1999/xlink">
- <title>Installing In Virtualized Linux Environments</title>
+ <title>Installing In Virtualized <systemitem class="osname">Linux</systemitem> Environments</title>
<section xml:id="serversideinstallation-virtual">
<title>Overview</title>
- <para>This section describes the installation of Evergreen software in so-called "virtualized" software environments. Evergreen software currently runs as a native application on any of several well-known x86 (32-bit) and x86-64 (64-bit) <systemitem class="osname">Linux</systemitem> distributions including <systemitem class="osname">Ubuntu</systemitem> and <systemitem class="osname">Debian</systemitem>, but it does not run as a native application on the <systemitem class="osname">Microsoft Windows</systemitem> operating system. However, it is possible to execute Evergreen on a <systemitem class="osname">Windows</systemitem> host system by running it within a virtual Linux-guest installation, which itself executes on the <systemitem class="osname">Windows</systemitem> system. The Linux environment is fully emulated and acts (within limits) just as if it were executing on a real standalone system.</para>
- <para>This technique of emulating a Linux environment on a <systemitem class="osname">Windows</systemitem> host is a practical way to install and run an Evergreen system if it is not possible to dedicate a physical machine solely as a Linux host for Evergreen.
-There are some performance limitations to running Evergreen in a virtualized environment, so this architecture is not recommended for large scale systems. However, it is a reasonable architecture for simple experiments, as a proof of concept, or as a conference-room pilot.</para>
+ <para>This section describes the installation of Evergreen software in so-called "virtualized" software environments. Evergreen software runs as a native application on any of several well-known x86 (32-bit) and x86-64 (64-bit) <systemitem class="osname">Linux</systemitem> distributions including <systemitem class="osname">Ubuntu</systemitem> and <systemitem class="osname">Debian</systemitem> but it does not run as a native application on the <systemitem class="osname">Microsoft Windows</systemitem> operating system. However, it is possible to execute Evergreen on a <systemitem class="osname">Windows</systemitem> host system by running it within a virtual Linux-guest installation, which itself executes on the <systemitem class="osname">Windows</systemitem> system. The <systemitem class="osname">Linux</systemitem> environment is fully emulated and acts (within limits) just as if it were executing on a real standalone system.</para>
+ <para>This technique of emulating a <systemitem class="osname">Linux</systemitem> environment on a <systemitem class="osname">Windows</systemitem> host is a practical way to install and run an Evergreen system if it is not possible to dedicate a physical machine solely as a <systemitem class="osname">Linux</systemitem> host for Evergreen. This architecture is not recommended for large scale systems since there are performance limitations to running Evergreen in a virtualized environment. However, it is a reasonable architecture for smaller experimental systems, as a proof of concept, or as a conference-room pilot.</para>
<section>
<title>Installing Virtualization Software</title>
- <para>As described above, Evergreen is installed on top of an emulated Linux environment. The Linux environment, in turn, is installed on top of a software application such as <application>"VirtualBox"</application>, <application>"VMware"</application> or <application>"VirtualPC"</application> which must first be installed on the <systemitem class="osname">Windows</systemitem> system. This section contains step-by-step examples of installing each of the popular virtualization applications on a <systemitem class="osname">Windows</systemitem> host system. Following this section are further descriptions of installing Linux systems on the virtualization software, then of installing and running Evergreen within those Linux systems.</para>
+ <para>As described above, Evergreen can be installed on top of an emulated <systemitem class="osname">Linux</systemitem> environment. The <systemitem class="osname">Linux</systemitem> environment, in turn, is installed on top of a software application such as <application>"VirtualBox"</application>, <application>"VMware"</application> or <application>"VirtualPC"</application> which must first be installed on the <systemitem class="osname">Windows</systemitem> system. This section contains step-by-step examples that show installing popular virtualization applications on a <systemitem class="osname">Windows</systemitem> host system. Following this section are further descriptions of installing <systemitem class="osname">Linux</systemitem> and Evergreen systems using that virtualization software.</para>
<section xml:id="serversideinstallation-virtual-vbox-install">
<title>Installing <application>"VirtualBox"</application> Virtualization Software</title>
- <para>This section reviews the procedure for installing the <application>"VirtualBox"</application> application on <systemitem class="osname">WindowsXP Professional (SP2)</systemitem>. Follow these instructions:</para>
- <para>Download <application>VirtualBox</application> from their official website: <ulink url="http://download.virtualbox.org/virtualbox/3.2.8/VirtualBox-3.2.8-64453-Win.exe">http://download.virtualbox.org/virtualbox/3.2.8/VirtualBox-3.2.8-64453-Win.exe</ulink>, then run the executable file. Continue with the steps shown in the next five figures until the software has been successfully installed:</para>
+ <para>This section reviews installation of the <application>"VirtualBox"</application> application on <systemitem class="osname">WindowsXP Professional (SP2)</systemitem>. Download <application>VirtualBox</application> from their official website: <ulink url="http://download.virtualbox.org/virtualbox/3.2.8/VirtualBox-3.2.8-64453-Win.exe">http://download.virtualbox.org/virtualbox/3.2.8/VirtualBox-3.2.8-64453-Win.exe</ulink>, then run the executable file. Continue with the steps shown in the next five figures until the software has been successfully installed:</para>
<figure>
<title>Starting the Windows installation file</title>
<mediaobject>
</section>
<section>
<title>Installing <application>"VMware"</application> Virtualization Software</title>
- <para>This section reviews the procedure for installing the <application>"VMware"</application> application on <systemitem class="osname">WindowsXP Professional (SP2)</systemitem>.</para>
- <procedure>
- <step>
- <para>Download <application>VMware</application> from here: <ulink url="">link</ulink>, then run the executable file. Continue with the steps shown in the first ??? figures until the software has been successfully installed:</para>
- <figure>
- <title>Starting the Windows installation file</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="../media/serversideinstallation-virtual-vbox-install-1.png" scalefit="1" width="75%"/>
- </imageobject>
- </mediaobject>
- </figure>
- </step>
- <step>
- <para>After successfully installating <application>VMware</application>, start it for the first time and click <guibutton>"New"</guibutton> to begin defining a new virtual machine (VM). You must specify a name and operating system type for the new VM; in this example we decided to install <systemitem class="osname">Debian Lenny</systemitem>. You must set a reasonable memory size (we chose the default value of 384Mb). You must define a name and size for a virtual hard disk (we chose a name, and set the size to 4.0Gb). The next six figures illlustrate the steps in starting <application>VirtualBox</application> and defining the new VM:</para>
- </step>
- </procedure>
- <para>At this point, <application>VirtualBox</application> has been installed, started for the first time, and a new virtual machine (VM) has been created. This VM is the environment in which the Linux / Evergreen installation will execute. Please continue in <xref linkend="serversideinstallation-virtual-install-linux-ev"/> with the installation of the Linux / Evergreen distribution.</para>
+ <para>This section reviews installation of the <application>"VMware"</application> application on <systemitem class="osname">WindowsXP Professional (SP2)</systemitem>. Download <application>VMware</application> from their official website: <ulink url="">link</ulink>, then run the executable file. Continue with the steps shown in the figures until the software has been successfully installed:</para>
+ <figure>
+ <title>Starting the Windows installation file</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../media/serversideinstallation-virtual-vbox-install-1.png" scalefit="1" width="75%"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
<indexterm>
<primary>ZZZ-REVIEW</primary>
<secondary>ADD INFO ON VMWARE</secondary>
</indexterm>
<caution>ADD INFO ON VMWARE</caution>
+ <para>At this point, <application>VirtualBox</application> has been installed, started for the first time, and a new virtual machine (VM) has been created. This VM is the environment in which the <systemitem class="osname">Linux</systemitem> / Evergreen installation will execute. Please continue in <xref linkend="serversideinstallation-virtual-install-linux-ev"/> with the installation of the <systemitem class="osname">Linux</systemitem> / Evergreen distribution.</para>
</section>
<section>
<title>Installing <application>"VirtualPC"</application> Virtualization Software</title>
- <para>This section reviews the procedure for installing the <application>"VirtualPC"</application> application on <systemitem class="osname">WindowsXP Professional (SP2)</systemitem>.</para>
- <procedure>
- <step>
- <para>Download <application>VMware</application> from here: <ulink url="">link</ulink>, then run the executable file. Continue with the steps shown in the first ??? figures until the software has been successfully installed:</para>
- <figure>
- <title>Starting the Windows installation file</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="../media/serversideinstallation-virtual-vbox-install-1.png" scalefit="1" width="75%"/>
- </imageobject>
- </mediaobject>
- </figure>
- </step>
- <step>
- <para>After successfully installating <application>VMware</application>, start it for the first time and click <guibutton>"New"</guibutton> to begin defining a new virtual machine (VM). You must specify a name and operating system type for the new VM; in this example we decided to install <systemitem class="osname">Debian Lenny</systemitem>. You must set a reasonable memory size (we chose the default value of 512Mb). You must define a name and size for a virtual hard disk (we chose a name, and set the size to 4.0Gb). The next six figures illlustrate the steps in starting <application>VirtualBox</application> and defining the new VM:</para>
- </step>
- </procedure>
- <para>At this point, <application>VirtualBox</application> has been installed, started for the first time, and a new virtual machine (VM) has been created. This VM is the environment in which the Linux / Evergreen installation will execute. Please continue in <xref linkend="serversideinstallation-virtual-install-linux-ev"/> with the installation of the Linux / Evergreen distribution.</para>
+ <para>This section reviews installation of the <application>"VirtualPC"</application> application on <systemitem class="osname">WindowsXP Professional (SP2)</systemitem>. Download <application>VMware</application> from their official website: <ulink url="">link</ulink>, then run the executable file. Continue with the steps shown in the figures until the software has been successfully installed:</para>
+ <figure>
+ <title>Starting the Windows installation file</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../media/serversideinstallation-virtual-vbox-install-1.png" scalefit="1" width="75%"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
<indexterm>
<primary>ZZZ-REVIEW</primary>
<secondary>ADD INFO ON VIRTUALPC</secondary>
</indexterm>
<caution>ADD INFO ON VIRTUALPC</caution>
+ <para>At this point, <application>VirtualBox</application> has been installed, started for the first time, and a new virtual machine (VM) has been created. This VM is the environment in which the <systemitem class="osname">Linux</systemitem> / Evergreen installation will execute. Please continue in <xref linkend="serversideinstallation-virtual-install-linux-ev"/> with the installation of the <systemitem class="osname">Linux</systemitem> / Evergreen distribution.</para>
</section>
</section>
<section xml:id="serversideinstallation-virtual-install-linux-ev">
- <title>Installing Linux / Evergreen on Virtualization Software</title>
- <para>After the virtualization software is installed and running and a new virtual machine (VM) has been created, there are two ways to continue with installing software in this virtualized environment:</para>
+ <title>Installing <systemitem class="osname">Linux</systemitem> / Evergreen on Virtualization Software</title>
+ <para>After the virtualization software is installed and running, there are two ways to continue with installing <systemitem class="osname">Linux</systemitem> and Evergreen software in the new virtualized environment:</para>
<orderedlist>
<listitem>
- <para>Download a prebuilt software image file containing a working Linux / Evergreen system (see <xref linkend="serversideinstall-virtual-prebuilt"/> for details)</para>
+ <para>Download and install a prebuilt software image that contains a working <systemitem class="osname">Linux</systemitem> / Evergreen system (see <xref linkend="serversideinstall-virtual-prebuilt"/> for details)</para>
</listitem>
<listitem>
- <para>Manually install a Linux guest system, then manually install Evergreen on it (see <xref linkend="serversideinstall-virtual-manual"/> for details)</para>
+ <para>Manually install a <systemitem class="osname">Linux</systemitem> guest system, then manually install Evergreen on it (see <xref linkend="serversideinstall-virtual-manual"/> for details)</para>
</listitem>
</orderedlist>
- <para>See the following two sections for a review of each method.</para>
+ <para>We review each method in the following sections.</para>
<section xml:id="serversideinstall-virtual-prebuilt">
<title>Download and install a prebuilt software image</title>
- <para>You can download a prebuilt software image that, when installed in <application>"VirtualBox"</application>, <application>"VMware"</application> or <application>"VirtualPC"</application>, will emulate a Linux guest system containing a running Evergreen distribution. The image is essentially a snapshot of a hard disk from a fully configured, functional Linux system with Evergreen already installed.</para>
- <para>We recommend this approach if you wish to get Evergreen running quickly with minimal attention to configuration. After reviewing only a few configuration details you can have a working Evergreen system that integrates smoothly with the rest of your network. See <xref linkend="serversideinstall-virtual-versions"/> for a list of prebuilt software images that are currently available to download and execute:</para>
+ <para>You can download a prebuilt software image that, when installed with your virtualization software, emulates a <systemitem class="osname">Linux</systemitem> guest system containing a running Evergreen distribution. The image is essentially a snapshot of a hard disk from a fully configured, functional <systemitem class="osname">Linux</systemitem> system with Evergreen already installed.</para>
+ <para>We recommend this approach if you wish to get Evergreen running quickly with minimal attention to configuration. After reviewing only a few configuration details you can have a working Evergreen system that integrates smoothly with the rest of your network. See <xref linkend="serversideinstall-virtual-versions"/> for a list of prebuilt software images that are currently available to download and install</para>
+ <note>DISCLAIMER: The following virtual images have been contributed by members of the Evergreen community for the purposes of testing, evaluation, training, and development.</note>
<table xml:id="serversideinstall-virtual-versions">
<title>Linux / Evergreen Virtual Images</title>
<tgroup align="left" cols="4" colsep="1" rowsep="1">
<row>
<entry>Linux Version</entry>
<entry>Evergreen Version</entry>
- <entry>OpenSRF Version</entry>
- <entry>VirtualBox Image</entry>
+ <entry>Image</entry>
+ <entry>Comments</entry>
</row>
</thead>
<tbody>
<row>
- <entry>Debin lenny (5.0)</entry>
+ <entry>Debian lenny (5.0)</entry>
<entry>1.6.0.1</entry>
- <entry>1.4.x</entry>
<entry>
<ulink url="http://www.open-ils.org/~denials/Evergreen1601_DebianLenny.zip"> download </ulink>
</entry>
+ <entry>VirtualBox image</entry>
+ </row>
+ <row>
+ <entry>Ubuntu karmic koala (9.10)</entry>
+ <entry>1.6.0.0</entry>
+ <entry>
+ <ulink url="http://www.open-ils.org/~denials/Evergreen-1600-Karmic.zip"> download </ulink>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>Ubuntu hardy heron (8.04)</entry>
+ <entry>1.2.3.1</entry>
+ <entry>
+ <ulink url="http://open-ils.org/dokuwiki/doku.php?id=server:1.2:ubuntu804:readme"> download </ulink>
+ </entry>
+ <entry>VirtualBox image; no preloaded data</entry>
+ </row>
+ <row>
+ <entry>Debian etch (4.0)</entry>
+ <entry>1.2.2.3</entry>
+ <entry>
+ <ulink url="http://open-ils.org/dokuwiki/doku.php?id=vmware:debian"> download </ulink>
+ </entry>
+ <entry>VMware image; preloaded with 13,000 Gutenberg records</entry>
+ </row>
+ <row>
+ <entry>Ubuntu gutsy gibbon (7.10)</entry>
+ <entry>1.2.1.4</entry>
+ <entry>
+ <ulink url="http://www.open-ils.org/downloads/vmware/Evergreen_1.2.1.4_on_Ubuntu_7.10.zip"> download </ulink>
+ </entry>
+ <entry>VMware image</entry>
+ </row>
+ <row>
+ <entry>Gentoo</entry>
+ <entry>1.1.5</entry>
+ <entry>
+ <ulink url="http://www.open-ils.org/~denials/Evergreen_1.1.5_Gentoo_x86.zip"> download </ulink>
+ </entry>
+ <entry>VMware image</entry>
</row>
</tbody>
</tgroup>
<secondary>ADD LIST OF OTHER PREBUILT IMAGES</secondary>
</indexterm>
<caution>ADD LIST OF OTHER PREBUILT IMAGES</caution>
- <para>After successfully installing <application>VirtualBox</application> (see <xref linkend="serversideinstallation-virtual-vbox-install"/> for details), continue with the following procedure. Refer to the accompanying figures for further information:</para>
+ <para>For the following example, we have already installed the <application>VirtualBox</application> application (see <xref linkend="serversideinstallation-virtual-vbox-install"/> for details). Continue with the steps as shown; refer to the accompanying figures for further information:</para>
<procedure>
<step>Start VirtualBox for the first time and select <menuchoice><guimenu>File</guimenu><guimenuitem>VirtualBox Media Manager</guimenuitem><guimenuitem>Add</guimenuitem></menuchoice> to locate the prebuilt software image just downloaded (the example shows it was extracted from the original <literal>.ZIP</literal> file into a temporary directory <literal>C:\temp</literal>). See <xref linkend="serversideinstallation-virtual-vm-install-2"/> for details.</step>
<step>After selecting the file, click <guibutton>Open</guibutton> to import it (see <xref linkend="serversideinstallation-virtual-vm-install-3"/> for details).</step>
<step>Then click <guibutton>OK</guibutton> to save the selection and return to the VirtualBox Media Manager (see <xref linkend="serversideinstallation-virtual-vm-install-4"/> for details).</step>
<step>Click <guibutton>New</guibutton> to start the "Virtual Machine Wizard", then <guibutton>Next</guibutton> to continue and create a new virtual machine (VM) <xref linkend="serversideinstallation-virtual-vm-install-5"/>).</step>
<step>Create a new name for the VM and set the operating system type, then click <guibutton>Next</guibutton> (see <xref linkend="serversideinstallation-virtual-vm-install-6"/>).</step>
- <step>Set the memory size (we chose the default value of 384Mb), then click <guibutton>Next</guibutton> (see <xref linkend="serversideinstallation-virtual-vm-install-7"/>).</step>
+ <step>Set the memory size (we chose the default value of 512Mb), then click <guibutton>Next</guibutton> (see <xref linkend="serversideinstallation-virtual-vm-install-7"/>).</step>
<step>Edit the Virtual Hard Disk configuration settings; click the radio boxes "Boot Hard Disk" and "Use existing hard disk" and ensure that the disk name "Evergreen1601_DebianLenny.vmdk" is selected. Click <guibutton>Finish</guibutton> to finish the setup (see <xref linkend="serversideinstallation-virtual-vm-install-8"/>).</step>
+ <step>
+ <para>Install the <application>VirtualBox Guest Additions</application> (really a required upgrade to VirtualBox)</para>
+ <indexterm>
+ <primary>ZZZ-REVIEW</primary>
+ <secondary>ADD INFO ON INSTALLING VIRTUALBOX GUEST ADDITIONS</secondary>
+ </indexterm>
+ <caution>ADD INFO ON INSTALLING VIRTUALBOX GUEST ADDITIONS</caution>
+ </step>
<step>Return to VirtualBox and see the summary of the VM just created. Click <guibutton>Start</guibutton> to boot the new VM (see <xref linkend="serversideinstallation-virtual-vm-install-9"/>).</step>
- <step>See the start of the Linux boot sequence. Choose "Debian Gnu/Linux, kernel 2.6.26-2-686" from the startup menu and type <guibutton>Enter</guibutton> to start Linux and Evergreen (see <xref linkend="serversideinstallation-virtual-vm-install-11"/>). After some delay you should see the command line prompt: <literal>debian-lenny login:</literal> . Log in with username <literal>root</literal> and password <literal>evergreen</literal> to continue (see <xref linkend="serversideinstallation-virtual-vm-install-14"/>).</step>
+ <step>See the start of the <systemitem class="osname">Linux</systemitem> boot sequence. Choose "Debian Gnu/Linux, kernel 2.6.26-2-686" from the startup menu and type <guibutton>Enter</guibutton> to start <systemitem class="osname">Linux</systemitem> and Evergreen (see <xref linkend="serversideinstallation-virtual-vm-install-11"/>). After some delay you should see the command line prompt: <literal>debian-lenny login:</literal> . Log in with username <literal>root</literal> and password <literal>evergreen</literal> to continue (see <xref linkend="serversideinstallation-virtual-vm-install-14"/>).</step>
</procedure>
- <para>At this point, you have a running Linux / Evergreen system. If you need to modify the Evergren configuration in any way, first review the standard Evergreen installation instructions in <xref linkend="serversideinstallation-ubuntudebian"/>.</para>
+ <para>At this point you have a running <systemitem class="osname">Linux</systemitem> / Evergreen system. If you need to modify the Evergreen configuration in any way, review the sectons of the standard Evergreen installation instructions in <xref linkend="serversideinstallation-ubuntudebian"/> that deal with configuration.</para>
<figure xml:id="serversideinstallation-virtual-vm-install-2">
<title>Starting <application>VirtualBox</application> for the first time</title>
<mediaobject>
</mediaobject>
</figure>
<figure xml:id="serversideinstallation-virtual-vm-install-3">
- <title>Selecting the software image in "Virtual Media Manager"</title>
+ <title>Selecting the software image in Virtual Media Manager</title>
<mediaobject>
<imageobject>
<imagedata fileref="../media/serversideinstallation-virtual-vm-install-3.png" scalefit="1" width="70%"/>
</figure>
<figure xml:id="serversideinstallation-virtual-vm-install-5">
<title>Creating a new VM</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="../media/serversideinstallation-virtual-vm-install-5.png" scalefit="1" width="75%"/>
- </imageobject>
- </mediaobject>
+ <mediaobject><imageobject><imagedata fileref="../media/serversideinstallation-virtual-vm-install-5.png" scalefit="1" width="75%"/></imageobject>
+gg </mediaobject>
</figure>
<figure xml:id="serversideinstallation-virtual-vm-install-6">
<title>Setting the VM name and OS type</title>
</mediaobject>
</figure>
<figure xml:id="serversideinstallation-virtual-vm-install-9">
- <title>Finishing definiton of new VM</title>
+ <title>Finishing definition of new VM</title>
<mediaobject>
<imageobject>
<imagedata fileref="../media/serversideinstallation-virtual-vm-install-9.png" scalefit="1" width="75%"/>
</mediaobject>
</figure>
<figure xml:id="serversideinstallation-virtual-vm-install-14">
- <title>Logging in to the new VM</title>
+ <title>Logging into the new VM</title>
<mediaobject>
<imageobject>
<imagedata fileref="../media/serversideinstallation-virtual-vm-install-14.png" scalefit="1" width="75%"/>
</figure>
</section>
<section xml:id="serversideinstall-virtual-manual">
- <title>Manually install Linux and Evergreen</title>
- <para>Manually install a Linux guest system, then manually install Evergreen.</para>
- <para>We recommend this approach if you need to configure the Linux system in any special way, or if you require Evergreen to target some specific chores. This will require a detailed review of both Linux and Evergreen configuration details. You are essentially doing a normal Evergreen installation on a Linux system; it just happens that Linux is running within a virtualized environment. Refer to <xref linkend="serversideinstallation-ubuntudebian"/> for information on the normal Evergreen installation, then continue with this section.</para>
- <para>In this example, we assume that the application <application>"VirtualBox"</application> has already been installed and started:</para>
+ <title>Manually install <systemitem class="osname">Linux</systemitem> and Evergreen</title>
+ <para>You can manually install a <systemitem class="osname">Linux</systemitem> guest system and Evergreen on your virtualization software.</para>
+ <para>We recommend this approach if you need to specially configure either the <systemitem class="osname">Linux</systemitem> system or Evergreen itself. This will require a detailed review of both <systemitem class="osname">Linux</systemitem> and Evergreen configuration details. You are essentially doing a normal Evergreen installation on a <systemitem class="osname">Linux</systemitem> system; it just happens that <systemitem class="osname">Linux</systemitem> is running within a virtualized environment. Refer to <xref linkend="serversideinstallation-ubuntudebian"/> for information on the normal Evergreen installation, then continue with this section.</para>
+ <para>For the following example, we have already installed the <application>VirtualBox</application> application (see <xref linkend="serversideinstallation-virtual-vbox-install"/> for details). Continue with the steps as shown; refer to the accompanying figures for further information:</para>
<procedure>
<step>
- <para>A standard <systemitem class="osname">Ubuntu</systemitem> distribution, the so-called "Guest" operating system, is installed in the running <application>"VirtualBox"</application> environment.</para>
+ <para>Download and install a standard <systemitem class="osname">Ubuntu</systemitem> distribution in <application>"VirtualBox"</application>.</para>
+ <para>You can download a software image of a prebuilt <systemitem class="osname">Ubuntu</systemitem> distribution and immediately import it into <application>"VirtualBox"</application> , or you can download and install
+</para>
<indexterm>
<primary>ZZZ-REVIEW</primary>
<secondary>ADD DETAILS ON MANUAL INSTALLATION OF LINUX</secondary>
<caution>ADD DETAILS ON MANUAL INSTALLATION OF LINUX</caution>
</step>
<step>
- <para>The <systemitem class="osname">Ubuntu</systemitem> distribution is started ("booted") just as if it existed on a real, physical system.</para>
+ <para>Start (boot) <systemitem class="osname">Ubuntu</systemitem>.</para>
<indexterm>
<primary>ZZZ-REVIEW</primary>
- <secondary>ADD DETAILS ON MANUAL INSTALLATION OF VM LINUX BOOT SEQUENCE</secondary>
+ <secondary>ADD DETAILS ON VM LINUX BOOT SEQUENCE</secondary>
</indexterm>
- <caution>ADD DETAILS ON MANUAL INSTALLATION OF VM LINUX BOOT SEQUENCE</caution>
+ <caution>ADD DETAILS ON VM LINUX BOOT SEQUENCE</caution>
</step>
<step>
- <para>Evergreen is installed on the running <systemitem class="osname">Ubuntu</systemitem> distribution, just as if installing on a standalone system.</para>
+ <para>Install Evergreen on <systemitem class="osname">Ubuntu</systemitem>.</para>
<indexterm>
<primary>ZZZ-REVIEW</primary>
<secondary>ADD DETAILS ON MANUAL INSTALLATION OF EVERGREEN</secondary>
</procedure>
<para>At this point, the <systemitem class="osname">Windows</systemitem> system is hosting an <systemitem class="osname">Ubuntu</systemitem> system, which itself is hosting the Evergreen distribution. So far as Evergreen is concerned, it is happily executing in a standard <systemitem class="osname">Ubuntu</systemitem> environment and behaves exactly as if it were executing on a standalone <systemitem class="osname">Ubuntu</systemitem> system.</para>
<para>Of course, there are limitations to how well a virtualized <systemitem class="osname">Ubuntu</systemitem> system emulates a real one. The <application>"VirtualBox"</application> application itself consumes memory, and it contributes to the CPU load on the <systemitem class="osname">Windows</systemitem> host system. The emulated <systemitem class="osname">Ubuntu</systemitem> system will have less available memory and will execute more slowly than if it were a standalone system, therefore Evergreen itself will inherit some limitations from this overall environment.</para>
- <para>However, this technique of using a <systemitem class="osname">Windows</systemitem> host to emulate a Linux environment is a practical way to install and run an Evergreen system even if it isn't possible to dedicate a real machine solely as a Linux host for testing. This is a reasonable architecture for simple experiments, or as a proof of concept, or as a conference-room pilot.</para>
+ <para>However, this technique of using a <systemitem class="osname">Windows</systemitem> host to emulate a <systemitem class="osname">Linux</systemitem> environment is a practical way to install and run an Evergreen system even if it isn't possible to dedicate a real machine solely as a <systemitem class="osname">Linux</systemitem> host for testing. This is a reasonable architecture for simple experiments, or as a proof of concept, or as a conference-room pilot.</para>
</section>
</section>
</section>
projects / contrib / Conifer.git / commitdiff