home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
terabyteunlimited.com
/
2014.06.terabyteunlimited.com.tar
/
terabyteunlimited.com
/
iflnet-unreg.zip
/
readme.txt
< prev
Wrap
Text File
|
2007-08-07
|
15KB
|
291 lines
Image for Linux with Network 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 Network Boot Disk, which in turn includes the
Image for Linux program. The Network Boot Disk supports a wide array of storage
devices including:
- IDE hard drives and CD/DVD drives
- USB 1.1/2.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)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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 network using eth0 interface (no wireless)
- requires DHCP server availability to obtain IP address
- console login not required on boot
- root password is 'ifl' (used for SSH login)
- SSH server is started on boot
- The ISCSI initiator daemon is started on boot
- the timezone is UTC
- uses qwerty keyboard layout
- uses 80x25 as default video mode
To create the default CD/DVD boot media in Windows:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. Unzip the archive to a folder of your choice
2. Burn iflnet.iso to CD/DVD. BurnCDCC, a free utility from TeraByte
Unlimited, is ideal for this if you don't have burner software.
To create the default CD/DVD boot media in Linux:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. Unzip the archive to a directory of your choice
2. Burn iflnet.iso to CD/DVD using appropriate burner software such
as cdrecord (command line) or K3B (GUI program - recommended).
The default configuration of the disk includes the following features:
- wired network support
- support for mounting NFS and Samba shares
- Imageall (free TeraByte Unlimited helper utility for IFL)
- SSH client and server for connecting to/from other computers
- FTP client (ncftp)
- read/write, check, resize, format Linux filesystems (Ext2/3, ReiserFS)
- read/write support for NTFS (using the ntfs-3g driver)
- resize and format NTFS filesystems (ntfsresize and mkntfs)
- read/write, format, & check FAT/FAT32 filesystems
- Linux fdisk, cfdisk, sfdisk partitioning programs
- hexedit file/disk hex editor
- text editor (nano)
- bash shell
- vlock available to lock console(s) requiring root password to unlock
- ISCSI support (initiator daemon and kernel modules)
- has makeHDD script to install to hard drive partition or UFD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 2 - Working with the IFL Network Boot Disk from a Linux distribution
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The following capability is available when working with the IFL Network Boot
Disk from a Linux distribution:
- use the makeISO script to create a customized ISO file
- use the makeHDD script to install the default or a customized version to a
hard drive partition, or to a UFD
- use the makePXE script to create a set of PXE boot files for the default
version, or for a customized version
A customized version of the disk can be created by running makeISO, makeHDD,
or makePXE. But first, the contents of certain files and directories must be
modified to make it a custom version. An outline of what to edit/change/add
in order to customize the disk can be found at the end of this file.
Setting up the IFL Network Boot Disk in a Linux distribution:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IMPORTANT: To successfully work with the IFL Network Disk from a Linux
distribution, the contents of the zip file must be unzipped on a *Linux*
partition (ext2/3 or reiserfs). If a FAT/FAT32 or NTFS partition is used,
problems with file permissions and upper/lower case are likely to result.
1. Unzip the iflnet archive in a directory of your choice
2. In a terminal, change to the above directory
3. From that directory, run the command 'unzip config.zip'.
When you unzip the config.zip file, the directory will be populated with
several additional files and directories. That includes three executable
scripts; makeISO, makeHDD, and makePXE.
The makeISO script: (no command line options)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The makeISO script is used to create a customized version in ISO file format.
The ISO file will be named iflnet-custom.iso. Run the script by typing
./makeISO from the prompt as ROOT. Before running the script, follow the
procedure below for customizing the disk, or the new ISO file will just
contain the default configuration (the same as iflnet.iso). The makeISO
script has no command line options.
The makeHDD script: (type ./makeHDD to see options and usage examples)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The makeHDD script is used to install the default or a customized version to
a hard drive partition, or to a UFD (USB Flash Drive). The script requires at
least one command line parameter, which is the drive or partition to install
to. Type ./makeHDD without parameters to see the command line options, and
some usage examples.
Note: The makeHDD script is also on the default CD/DVD, and can be run from
there as well. If running makeHDD from the CD/DVD, the /c option (see below)
is not supported.
To install a customized version, follow the procedure below for customizing
the disk, and then run the script with the /c option. If the /c option is not
used, the script will install the default configuration.
The makeHDD script can install to a partition on a hard drive, OR to a
partition on a UFD, OR to an entire (unpartitioned) UFD. The script will
not install to an entire drive unless the drive is detected as being a
removable drive (such as a UFD).
To install to a partition, the following is required:
- the partition must already exist, and must be at least 20 MB in size
- 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 does not have to formatted (can be, but doesn't have to be)
- the partition can not be mounted
To install to an entire drive (usually a UFD), the following is required:
- the drive must be detected by Linux as being a removable drive.
- the drive must be at least 20 MB in size
- if the drive currently contains partitions, none can be mounted
(ALL existing partitions will be deleted)
The makeHDD script will check for the above conditions before installing,
and will exit with an error message if it detects a problem.
When installing to a FAT/FAT32 partition, makeHDD will install the syslinux
boot loader. Syslinux requires the 'mcopy' command, which means the mtools
package must be installed. If /usr/bin/mcopy is not detected on the system,
an error message will be displayed, and the script will fail. Note that the
mtools package is only required when installing to a FAT/FAT2 *partition*.
If installing to an entire drive, the script uses a FAT16 image that already
has syslinux installed.
If 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. In addition, if installing to a partition on a drive other
than HD0, the partition will not boot unless the drive is "BIOS swapped" so
that it is now HD0. This can be accomplished (for example) by using the swap
option in the BootIt NG boot manager.
The /c option: This option will install a customized version based on the
contents of config.txt, IFL.INI, the scripts directory, the wireless directory,
and the iscsi directory. If /c is not used, the default configuration will be
installed (the same as iflnet.iso). Note that if none of the above files and
directories are modified, the /c option will not have any functional effect.
The /mbr option: This option will install standard MBR code to the MBR of the
drive containing the target partition. The /mbr option is only allowed when
installing to a partition on a removable drive (a UFD). The MBR code installed
with this option is about 300 bytes, and will not overwrite the partition
table on the drive. This option is only needed if you intend to boot directly
from the drive, and it does not already contain MBR code (or you want to
replace the existing MBR code).
The /a option: This option will set the target partition active. If you intend
to boot the partition from a boot manager (such as BootIt NG), this option is
not required. It would be required if the partition 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.
The makeHDD script has some safeguards built in, hopefully to 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.
The makePXE script: (type ./makePXE to see options and usage examples)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The makePXE script will create a set of boot files in the pxe directory, which
can then be used to manually set up a PXE network boot. Please refer to the
file pxe.txt in the pxe/help directory for more information about setting up
a PXE boot.
The makePXE script has two command line options, one of which is always
required. The /d option will create the files based on the default iflnet.iso
configuration. The /c option will create the files for a customized version
based on config.txt, IFL.INI, and the wireless, scripts, and iscsi directories.
The command line options and usage information can be displayed by typing
./makePXE without any parameters.
Creating a customized version of the IFL Network Boot Disk:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When customizng the disk, the following options are available:
- can specify and use static IP address, default route, DNS
- can use alternate or additional network interface, or no network interface
- can configure wireless networking (see wireless/help/wireless.txt)
- can specify a default video mode other than 80x25
- can specify the azerty or dvorak keyboard map (default is qwerty)
- can include custom scripts in the scripts directory
- can optionally execute some or all of the scripts on boot
- can specify a timezone other than UTC
- can specify that console login is required on boot
- can set the root password
- can specify a hostname other than 'ifl'
- can disable the SSH server on boot
- can include a custom configuration for ISCSI in the iscsi directory
- can disable the ISCSI daemon on boot
- can edit and include the IFL.INI file to specify custom settings for IFL
- can enable support for mounting LVM volumes (Linux Volume Manager)
- 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 comments in
config.txt explain the options. Note that the options to require a console
login and to set the root password are configured when you run one of the
make scripts in step 6, 7, or 8 below. 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.INI (optional): If desired, edit the empty IFL.INI file in this
directory to add any custom IFL settings as defined in the IFL manual. The
IFL.INI file will be automatically included on the disk. If you have no
need for any IFL settings, you can just leave the file empty - it won't
have any effect.
3. Configure wireless (optional): See the wireless/help directory for
information on how to set up & configure that for your particular network
adapter. Note that some wireless adapters may not be supported. Also note
that some options (at least one) in config.txt will need to be configured
for wireless.
4. 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.
5. 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 issci 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.
6. To create a customized CD/DVD, run the makeISO script as described above.
7. To install the customized version to hard drive or UFD, run the makeHDD
script with the /c option as described above. The /c option must be used
to install a customized version. Otherwise it will ignore any changes made
above, and will just install the default configuration.
8. To create the customized version as a set of PXE boot files, run the makePXE
script with the /c option as described above. Then refer to the file pxe.txt
in the pxe/help directory.