home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
terabyteunlimited.com
/
2014.06.terabyteunlimited.com.tar
/
terabyteunlimited.com
/
ifl_en_gui_trial.zip
/
readme.txt
< prev
next >
Wrap
Text File
|
2011-12-23
|
18KB
|
356 lines
Image for Linux with the IFL Boot Disk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Image for Linux is a Linux-based disk imaging backup and restore solution.
Licensing
~~~~~~~~~
BY COPYING, DISTRIBUTING, INSTALLING, OR USING THE ACCOMPANYING TERABYTE, INC.
("TERABYTE") SOFTWARE PRODUCT (THE "PRODUCT"), THE INDIVIDUAL OR ENTITY USING
THE PRODUCT ("USER") IS CONSENTING TO BE BOUND BY AND IS BECOMING A PARTY TO
THE TERABYTE LICENSE AGREEMENT INCLUDED WITH THE PRODUCT PACKAGE. IF USER DOES
NOT AGREE TO ALL OF THE TERMS OF THE LICENSE AGREEMENT, USER MUST NOT COPY,
DISTRIBUTE, INSTALL OR USE THE PRODUCT IN ANY MANOR. IF USER HAS RECEIVED A
SIGNED LICENSE AGREEMENT FOR THE PRODUCT DIRECTLY FROM TERABYTE THAT CONTAINS
TERMS WHICH VARY FROM THE TERMS OF THE INCLUDED LICENSE AGREEMENT, THEN THE
SIGNED LICENSE AGREEMENT GOVERNS THE USE OF THE PRODUCT.
Introduction
~~~~~~~~~~~~
This archive contains the IFL Boot Disk, which in turn includes the Image for
Linux program. The IFL Boot Disk supports a wide array of storage devices
including:
- IDE hard drives and CD/DVD drives
- USB 1.1/2.0/3.0 hard drives, flash drives, CD/DVD drives
- SATA hard drives and CD/DVD drives
- IEEE 1394 (FireWire) hard drives and CD/DVD drives
- most SCSI controllers (those supported natively by the Linux kernel)
- storage devices connected via PCMCIA interface (typically USB or IEEE 1394)
- ISCSI drives (over network connection)
- most RAID or SATA/RAID controllers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 1 - Creating and using the default configuration (iflnet.iso)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The file iflnet.iso can be burned to CD/DVD from Windows or Linux to run the
default configuration. The default configuration of the disk can be summarized
as follows:
- wired networking using eth0 and/or eth1 interfaces and dhcp
- wireless interfaces can be configured manually from the menu
- console login not required on boot
- root password is 'ifl' (used for SSH login)
- the timezone is UTC
- uses us/qwerty keyboard by default (others selectable after boot)
- uses 80x25 as default video mode
To create the default CD/DVD boot media in Windows:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. Unzip the IFL archive to a folder of your choice
2. Use the included MakeDisk program to create a CD/DVD or USB flash drive.
Note that for the registered version, burning iflnet.iso directly (with other
software such as Nero) will cause the IFL program to prompt you for the
product key each time it is started. When using MakeDisk, you will be prompted
for the product key once while creating the boot media, and then will not be
prompted for it again when using the boot media it creates.
To create the default CD/DVD boot media in Linux:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. Unzip the IFL archive to a directory of your choice
2. Run the included setup script with the command ./setup. The setup script
will prompt for the IFL product key (registered version only). See section
2 below for more information.
3. Burn the file iflnet.iso to CD/DVD using appropriate burner software such
as K3B (GUI program - recommended).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 2 - Working with the IFL Boot Disk from a Linux distribution
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If using the IFL Boot Disk from a Linux distribution, you will have the ability
to run the IFL program from there, as well as the ability to customize the disk,
install it to a hard drive or UFD, and create a set of boot files for a PXE
network boot.
Setting up the IFL directory on a Linux distribution
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IFL can be set up on a Linux distribution by following these steps:
- Extract the IFL zip archive in a directory of your choice on a Linux
partition (not FAT/FAT32 or NTFS). This ensures that no problems with
file permissions or upper/lower case will be encountered.
- Open a terminal window (such as an xterm) and change to the directory
that the archive was extracted to (the IFL directory).
- Become root
- From the IFL directory, run the command './setup' from the prompt. The
setup script will do the following:
- Prompt you to enter your product key (registered version only).
- Present a menu to optionally select Restore Disc settings for restore
discs created from the Linux distrubution.
- Offer the option to select an IFL language version other than English
- Extract the IFL program (imagel) from iflnet.iso, and set up the IFL
directory so that bootable restore discs can be created when running
the IFL program from the Linux distribution.
- Once setup has completed, the IFL program can be started by typing the
command './imagel' at the prompt.
- To create an IFL CD/DVD boot disc, burn the file iflnet.iso to CD/DVD
using the burner software of your choice (such as K3b).
- Note that the setup script can be run again to change settings, or
enter/correct the product key.
Setting up the IFL directory to create custom versions:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The file config.zip contains all items need to created custom versions of the
boot disk. This file is extracted automatically (as of LBD220EN) the first time
that the setup script is executed. This populates the IFL directory with
several additional files and directories needed to customize the disk.
When customizing the disk, the following options are available:
a) From the makeISO/HDD/PXE scripts:
- keyboard map
- video mode
- kernel boot parameters (see boot-problems.txt)
- LVM activation (see lvm.txt)
- separate restore disc settings for above (if desired)
- restore disc command line
- IFL language version (both restore disc and boot media)
- require console login
- change root password from default of 'ifl'
- configure one or more network interfaces (wired and wireless)
b) From the config.txt configuration file and various directories:
- include custom scripts in the scripts directory (see scripts.txt)
- optionally execute some or all of the scripts on boot
- specify a timezone other than UTC
- specify a hostname other than 'ifl'
- start the SSH server automatically on boot (disabled by default)
- include a custom configuration for ISCSI (see iscsi.txt)
- enable the ISCSI daemon on boot
- edit the ifl-custom.ini file to specify custom ifl.ini settings for IFL
- can enable login from a serial port (COM1 and/or COM2)
The following steps are an outline of how to customize the disk:
1. Edit config.txt (optional): If desired, edit the config.txt file in this
directory to select and configure the available options. The config.txt file
is commented to explain each option. If you do not change anything in
config.txt, the file will still be included on the disk, but will have no
effect.
2. Edit ifl-custom.ini (optional): When the setup script is run the first time,
an empty file named ifl-custom.ini will be extracted from config.zip. This
file can be edited to specify any desired ifl.ini settings for customized
boot media created with the makeISO, makeHDD, and makePXE scripts. When one
of those scripts is executed, ifl-custom.ini will be included in the boot
media, and will appear as ifl.ini in the /tbu directory. If you have no need
for any IFL settings, the file can be left empty - it won't have any effect.
Note that this file is named ifl-custom.ini to separate it from the ifl.ini
file also in the IFL directory. The settings in ifl.ini (if any) are only
for IFL when executed from the Linux distribution.
3. Set up the scripts directory (optional): If desired, populate the scripts
directory with one or more bash scripts that you want to include on the
disk. To have one or more of those scripts executed automatically on boot,
you also need to configure the RUNSCRIPTS option in config.txt. The default
is that NO scripts will be executed. It is not necessary to set permissions
on the scripts. That will be taken care of automatically.
4. Set up the iscsi directory (optional): If desired, set up the iscsi
directory as needed to work with your network and iscsi target setup.
When creating custom boot media, the ENTIRE iscsi directory will be copied
to the root file system at /etc/iscsi, and will replace the default iscsi
directory there. The iscsi directory initially contains a copy of the
default /etc/iscsi directory, so if no changes are made, building a custom
disk will have no effect on iscsi operation.
5. Set up the tbosdtfiles directory (optional): If desired, set up the
tbosdtfiles directory by adding tbosdt scripts, driver files etc. to
the directory. The tbosdtfiles directory will be included on the boot
disk in the /tbu directory.
6. Run 1 of the 3 make scripts (makeISO, makeHDD, or makePXE) to create the
custom version. Creating a custom version with makeHDD or makePXE requires
using the /c option. The makeISO script has no command line options, and
will always create a custom version. When creating a custom version, all of
the make scripts will present the following options:
Option 1: The IFL Boot Media Settings menu (keyboard, video, etc.)
Option 2: Require console login? (default = no)
Option 3: Change the root password? (default = "ifl")
Note that the makeHDD and makePXE scripts can also be used to install the
default version of the disk, based on iflnet.iso. In that case, the 3
options listed above will not be presented, and all settings will stay at
their default values.
The makeISO script: (type './makeISO' as root to create custom version)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The makeISO script creates a custom version in ISO file format, based on the
changes (if any) made in steps 1 through 5 above, and the options selected
while running the script. The ISO file will be named iflnet-custom.iso.
The makeISO script has no command line options.
The makePXE script: (type './makePXE /c' as root to create custom version)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The makePXE script will create a set of PXE boot files in the pxe directory.
These files can then be used to manually set up a PXE network boot. Please
refer to the file pxe.txt in the help directory for more information about
setting up a PXE boot.
The makePXE script can create either the default version of the disk, or a
custom version as follows:
./makePXE -> create default version based on iflnet.iso
./makePXE /c -> create custom version
The /c option will create a custom version based on the changes (if any)
made in steps 1 through 5 above, and the options selected while running
the script.
The makeHDD script: (type './makeHDD' as root to see usage and examples)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The makeHDD script will install the IFL Boot Disk to a hard drive partition,
or to a UFD (USB Flash Drive). It can be used to install either the default
version (based on iflnet.iso), or a custom version based on the changes
(if any) made in steps 1 through 5 above, and the options selected while
running the script.
The basic usage of makeHDD is as follows:
./makeHDD /dev/xyz -> install default version to /dev/xyz
./makeHDD /dev/xyz /c -> install custom version to /dev/xyz
There are 2 additional options (/a and /mbr) which are covered below. To see
usage information and examples, type './makeHDD' without parameters.
Note that the makeHDD script can also be executed from a CD/DVD created from
iflnet.iso, or from a custom CD/DVD. In that case, the /c option is not
available, and makeHDD will always install the same version (default or custom)
that it finds on the CD/DVD.
The makeHDD script can install to a partition on a hard drive, OR to a
partition on a UFD, OR to an entire UFD. An "entire UFD" means that the UFD
will no longer contain any partitions (if it did previously) once the
installation has completed.
To install to a partition, the following are required:
- the partition must already exist
- the partition must be a FAT16, FAT32, or a Linux (type 83) partition
- if it's a Linux partition, it must be a primary partition
- the partition must be at least 32 MB in size
- if FAT16 or FAT32, the mtools package must be installed
- the partition does not have to formatted, although it won't matter if it is
- the partition cannot be currently mounted
To install to an entire drive (usually a UFD), the following are required:
- the drive must be detected by Linux as being a removable drive.
- the drive must be at least 32 MB in size, but not larger than 8 GB
- the drive cannot be currently mounted
- if the drive currently contains partitions, none can be currently mounted
(ALL existing partitions will be deleted during installation)
The makeHDD script will check for the above conditions before installing,
and will exit with an error message if it detects a problem.
The command line options available for makeHDD are as follows:
The /c option: This option will install a customized version based on the
changes (if any) made in steps 1 through 5 above. If the /c option is not used,
makeHDD will install the default version of the disk, based on iflnet.iso. When
running makeHDD from the boot media, the /c option is not available, and the
version on that particular CD/DVD (whether it be the default version, or a
custom version) will always be installed.
The /mbr option: This option is available when installing to a partition. It
installs the standard MBR code to the MBR of the drive containing the target
partition. This option is needed if you intend to boot directly from the drive
(rather than use a boot manager), and it does not already contain MBR code
(or you want to replace the existing MBR code). The MBR code installed with
this option is 440 bytes, and will not overwrite the partition table on the
drive.
The /a option: This option will set the target partition active. This option is
required if the partition installed to is on the drive that you are booting
the system from, and that drive has a standard MBR installed. The standard MBR
will look for an active partition to boot. If you intend to boot the partition
from a boot manager (such as BootIt NG), this option is not required.
The makeHDD script has some safeguards built in to help prevent mistakes
like installing to the wrong drive or partition. In all cases, there will be
a confirmation screen displayed where the user must type out the word 'yes'
before going ahead with the installation. On that screen, the command line
entered, as well as the target drive/partition information will be displayed
as a visual check.
Additional Notes:
1. Installing to a Linux partition - the extlinux boot loader is used, and the
partition is formatted as ext2. Extlinux requires that the partition be a
primary partition. The partition must be at least 32 MB in size.
2. Booting from a Linux partition - the partition will not boot from a drive
other than HD0 unless the drive is "BIOS swapped" so that it becomes HD0 for
that session. This can be accomplished (for example) by using the swap option
in the BootIt NG boot manager. It can also be accomplished by changing the
BIOS boot order so that the system boots from that drive.
3. Installing to a FAT16 or FAT32 partition - the partition must be a minimum
of 32 MB. The syslinux boot loader is used. The partition can be either a
primary partition, or a volume in an extended partition. If it's a volume in
an extended partition, be sure to read note 4 below.
4. Booting from a FAT16 or FAT32 partition - the partition will not boot from a
drive other than HD0 unless the drive is "BIOS swapped" so that it becomes HD0
for that session. The exception to this is if BootIt NG is used as the boot
manager - it can boot the partition from any drive. If the partition is a
volume in an extended partition, it must be booted using a boot manager capable
of doing that, such as BootIt NG.
5. Installing to a UFD (USB Flash Drive) - a UFD can be installed to as either
a partitioned device, or as an entire drive (not partitioned).
- Installing to a partition on a UFD is the same as installing to a partition
on a hard drive. An existing partition (such as /dev/sda1) must be specified.
The /mbr option is available when installing to a partition on a UFD.
- To install to the UFD as an entire drive, the entire drive is specified (such
as /dev/sda or /dev/sdb). This can be done even if the drive currently
contains partitions, although ALL partitions will be deleted during the
installation. The makeHDD script warns about this condition twice before
installing, requiring that you type 'yes' both times to confirm.
- When installing to the entire drive, the drive cannot be larger than 8 GB
for data safety reasons.
- When installing to the entire drive, the syslinux boot loader is used, and
the device is formatted as a FAT16 file system using a prepared 32 MB image.
6. Booting from a UFD - the system BIOS must capable of booting from a USB
drive, and must be set to boot from that device. This is accomplished by
entering the BIOS setup and changing the boot order. Many systems also have a
key to press during boot which brings up a menu of devices to boot from.
Selecting the UFD from this menu will make the UFD the boot device for that
session.