Update of /cvsroot/leaf/doc/guide/user-bering-uclibc
In directory sc8-pr-cvs6.sourceforge.net:/tmp/cvs-serv8977
Added Files:
bucu-vmware.xml
Log Message:
Using Bering-uClibc as VMware guest
--- NEW FILE: bucu-vmware.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="bucu-vmware">
<chapterinfo>
<authorgroup>
<author>
<firstname>Andrew</firstname>
<surname>Nagy</surname>
<affiliation>
<address><email>aenagy at hotmail.com</email></address>
</affiliation>
</author>
<author>
<firstname>K.P.</firstname>
<surname>Kirchdoerfer</surname>
<affiliation>
<address><email>kapeka at users.sourceforge.net</email> </address>
</affiliation>
</author>
</authorgroup>
</chapterinfo>
<title>Running LEAF Bering-uClibc as guest system in VMware Server</title>
<section>
<title>Goal</title>
<para>Create a bootable floppy image of LEAF Bering uClibC that will work
with VMware Server 1.0.2. (This guide has been written based on LEAF
Bering-uClibc version 3.0.2). This boot floppy is a bare minimum
configuration to establish TCP/IP connectivity and therefore confirm
compatibility.</para>
<para>All other modules and tools have been removed for simplicity. This
means that there is no firewall, routing, SSH client or server, DHCP, DNS,
etc. It will be up to the user to configure or add any additional
functionality. Information on configuring or adding additional
functionality can be found on the LEAF Bering uClibC web site (<ulink
url="http://leaf.sourceforge.net/doc/index.html";>http://leaf.sourceforge.net/doc/index.html</ulink>)
on in various news groups (<ulink
url="http://www.nabble.com/LEAF---Linux-Embedded-Appliance-Firewall-f4454.html";>http://www.nabble.com/LEAF---Linux-Embedded-Appliance-Firewall-f4454.html</ulink>).
Follow the instructions for Bering uClibC 3.</para>
</section>
<section>
<title>Assumptions</title>
<para>This procedure assumes that the user is new to LEAF Bering uClibC
and may be unfamiliar with some of its subtlities. For example, the bin
âBering-uClibc_3.0.2_iso_bering-uclibc-iso.binâ file on the <ulink
url="http://sourceforge.net/project/showfiles.php?group_id=13751&amp;package_id=67534";>download
page</ulink> is actually an ISO file. Renaming the file with a .ISO
extention makes it usable as a boot media for VMware Server. Its contents
can be extracted using WinImage.</para>
<para>The entire procedure as explained here assumes that the user is
operating from Microsoft Windows. In the authorâs case Windows XP
Professional with Service Pack 2 is used. The version of Microsoft Windows
must be compatible with the VMware product being used, in this case Server
1.0.2.</para>
<para>Even though VMware Server 1.0.2 is used in this example there is no
known reason why this could not equally well in other VMware products such
as Player, Workstation or ESX Server. This solution has not been tested on
other VMware products or other virtualization solutions.</para>
<para>VMware products do not recognize floppy images or physical floppy
disks larger than 1.44 MB. Therefore the 1.68 MB floppy image available
for download is not suitable. The user will be directed to extract the
file <filename>bootdisk.ima</filename> from the ISO file
Bering-uClibc_3.0.2_iso_bering-uclibc-iso.bin as this image is already
formatted for 1.44 MB. See the procedure section on how to do this.</para>
<para>The authorâs test network consists of a DSL router with the LAN
interface configured for the subnet 192.168.1.0 and subnet mask of
255.255.255.0 and default gateway of 192.168.1.1. The reader will need to
adjust the procedure below to account for any differences where
shown.</para>
<para>Setting up or troubleshooting network connectivity of the userâs
Windows system out of scope for this document.</para>
</section>
<section>
<title>Prerequisites</title>
<para>The following prerequisites are recommended:</para>
<itemizedlist>
<listitem>
<para>Microsoft Windows - The user may consider downloading a trial
version of Windows Server 2003 from <ulink
url="http://www.microsoft.com";>http://www.microsoft.com</ulink>. This
has not been tested by the author. The version of Windows must be
compatible with VMware Server 1.0.2.</para>
<para>The Windows system must be properly configured for network
connectivity. The default gateway must be pingable.</para>
</listitem>
<listitem>
<para>VMware - The VMware Server can be downloaded from <ulink
url="http://www.vmware.com";>http://www.vmware.com</ulink>.</para>
</listitem>
<listitem>
<para>Floppy disk image editor - The author used a trial copy of
WinImage which can be downloaded from <ulink
url="http://www.winimage.com";>http://www.winimage.com</ulink>.</para>
</listitem>
<listitem>
<para>Text editor - The text editor has to be suitable for modifying
Linux/Unix text files. Microsoft WordPad might work, but was not
tested by the author. The author used PSPad for editing text files. It
is available for download from <ulink
url="http://www.pspad.com";>http://www.pspad.com</ulink>.</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Procedure</title>
<para>Download
<filename>Bering-uClibc_3.0.2_iso_bering-uclibc-iso.bin</filename> (or a
more recent version) from the LEAF Bering uClibc <ulink
url="http://sourceforge.net/project/showfiles.php?group_id=13751&amp;package_id=67534";>download
page</ulink>.</para>
<para>Download and install the necessary prerequisites.</para>
<para>Open the file
<filename>Bering-uClibc_3.0.2_iso_bering-uclibc-iso.bin</filename> with
WinImage.</para>
<para>Extract the <filename>bootdisk.ima</filename> file and save to your
working folder such as âE:\my_new_boot_diskâ. This is now the start of
the
new floppy image.</para>
<para>Extract or edit a copy of <filename>syslinux.cfg</filename> in
floppy image to look like the text below and save in work folder. Remember
to use a Linux/Unix compatible file editor such as PSPad or WordPad. The
last line starts with âdefault linux â¦â and may be wrapped as shown
below.</para>
<para><screen>display syslinux.dpy
timeout 0
append reboot=bios
default linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0
LEAFCFG=/dev/fd0:msdos boot=/dev/fd0:msdos</screen></para>
<para>Extract or edit <filename>leaf.cfg</filename> in floppy image to
look like this and save in the work directory. Remember to use a
Linux/Unix compatible file editor such as PSPad or WordPad.</para>
<para><screen>LRP="root config etc local modules"
PKGPATH=/dev/fd0:msdos
syst_size=16M
log_size=4M</screen></para>
<para>Extract the modules, <filename>config.lrp</filename>,
<filename>etc.lrp</filename>, <filename>initrd.lrp</filename>,
<filename>local.lrp</filename>, <filename>moddb.lrp</filename>,
<filename>modules.lrp</filename> and <filename>root.lrp</filename> from
the same bin/ISO file from which the initial floppy image was extracted in
step 1 and save in work folder.</para>
<para>Open the working copy of <filename>bootdisk.ima</filename> using
WinImage. Add the extracted modules plus the new
<filename>syslinux.cfg</filename> and <filename>leaf.cfg</filename>.
Overwrite files when prompted. Save and close floppy image file to work
folder.</para>
<para>Create a new floppy image using WinImage.</para>
<para>Find the module <filename>pcnet32.o</filename> on bin/ISO image and
add it to this new floppy image. Save and close this floppy to work
folder. Do not add this module to the <filename>bootdisk.ima</filename>
floppy image.</para>
<para>Create a new virtual machine in VMware Server 1.0.</para>
<para>Copy the two floppy image files to the new virtual machine
folder.</para>
<para>Configure the virtual machine for:</para>
<itemizedlist>
<listitem>
<para>CPU = one</para>
</listitem>
<listitem>
<para>RAM = 32 MB</para>
</listitem>
<listitem>
<para>NICs = 2 or more. The first NIC must be configured as
âBridgedâ
so that it has connectivity to DSL router</para>
</listitem>
<listitem>
<para>HDD = none</para>
</listitem>
<listitem>
<para>Floppy = boot floppy file <filename>bootdisk.ima</filename> in
the virtual machine folder</para>
</listitem>
<listitem>
<para>Add Floppy 2 = second floppy device to use the second floppy
image created in step 6.</para>
</listitem>
</itemizedlist>
<para>Power on the virtual machine. If the virtual machine is configured
correctly it will boot from the <filename>bootdisk.ima</filename> in the
virtual machine folder.</para>
<para>Log in as root. The tool
<filename><command>lrcfg</command></filename> will launch
automatically.</para>
<para>In <filename>lrcfg</filename> menu enter <command>3</command> for
'Packages configuration', <command>3</command> for 'modules',
<command>1</command> for 'kernel modules to load at boot' which brings up
'/etc/modules/' in the e3 editor.</para>
<para>Remove comments for <filename>crc32</filename>,
<filename>mii</filename> and <filename>pcnet32</filename>. Save and exit
editor.</para>
<para>Quit back to main lrcfg screen.</para>
<para>Enter <command>1</command> for 'Network configuration', enter
<command>1</command> for 'interfaces file'. The file
<filename>/etc/network/interfaces</filename> is opened in the e3 editor.
Make changes to match the following:</para>
<para><screen>auto eth0
iface eth0 inet static
address 192.168.1.3
# or some other IP address not in use and on the same subnet as the DSL router
netmask 255.255.255.0
# must be same as LAN subnet of DSL router
broadcast 192.168.1.255
gateway 192.168.1.1
#or whatever the default gateway is for your DSL router
auto eth1
iface eth1 inet static
#address can be changed to suite userâs requirements for private subnet
address 10.1.1.1
netmask 255.255.255.0
broadcast 10.1.1.255
# repeat for each NIC configured on the virtual machine</screen></para>
<para>Save changes and quit to go back to the main configuration
menu.</para>
<para>Enter <command>s</command> to 'Save configuration'. Enter âyâ when
prompted.</para>
<para>Exit to command prompt.</para>
<para>Mount second floppy disk which contains a copy of
<filename>pcnet32.o</filename> with the command:</para>
<para><command>mount ât msdos /dev/fd1 /mnt</command></para>
<para>Copy <filename>pcnet32.o</filename> from second floppy to
'/lib/modules' with the command:</para>
<para><command>cp /mnt/pcnet.o /lib/modules</command></para>
<para>Launch <filename><command>lrcfg</command></filename>, enter
<command>m</command> for 'Backup modules'. Enter 'y' when prompted.</para>
<para>Reboot the system with the command:</para>
<para><command>init 6</command></para>
<para>Once the system reboots log in as root again and exit from the
configuration menu. Check the configuration of the network interfaces with
the command:</para>
<para><command>ip addr show</command></para>
<para>Check connectivity to the DSL router by pinging the default gateway
with the command:</para>
<para><command>ping 192.168.1.1</command></para>
<para>If that works, you're done - enjoy running LEAF Bering-uClibc in
your VMware environment.</para>
</section>
</chapter>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
leaf-cvs-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits
