Bering-uClibc 7.x - User Guide - Installing the Disk Image

Installing the Disk Image
Prev	Bering-uClibc 7.x - User Guide	Next

---

Choosing An Image File to Download

For Bering-uClibc 7.x there are several different disk image files available for download. These offer a choice of tailored variants of the same basic distribution and you should only need to download one of them - the one that best matches your requirements. The different variables are:

• The Linux kernel optimisations:
  • i486 is the most basic and most widely compatible kernel variant, suitable for Intel 486 CPUs (or better).
  • i686 is a variant which is optimised for Intel Pentium Pro CPUs (or better) and supports multiple CPUs / CPU cores.
  • geode is a variant which is optimised for AMD Geode CPUs such as are used in e.g. the PC Engines ALIX boards.
  • wrap is a variant which is optimised for WRAP boxes based on AMD SC1100 CPU e.g. PC Engines WRAP or Soekris boxes.
  • x86_64 is a variant optimised for 64bit systems e.g. PC Engines APUs, AMDs , Intels.
• The boot media type:
  • syslinux for flash drive or hard drive devices such as a USB or Compact Flash drive or a standard hard disk.
  • isolinux for CD-ROM devices (optionally in conjunction with a floppy disk SD card or USB key, for storing configuration changes).
  • pxelinux for PXE network booting.
• The console type:
  • vga for a standard VGA console.
  • ser for an RS-232 Serial console.
• The bootable images for USB:
  • Bering-uClibc_x86_ser.img
  • Bering-uClibc_x86_vga.img
  • and more to come...

If your hardware allows booting from USB, as most modern systems do, we suggest to download and install one of the .img files to a USB key using dd on Linux or the Raspberry PI Imager on Windows and Macs.

If no USB boot is possible, and if in doubt, then start with the first (most standard) option in each case - in other words the combination i486_syslinux_vga.

A special case: the Raspberry Pi(s)

There are also tarballs and (comming up ?) bootable .img files available for the family of Raspberry PIs, which are the Zero and 1,2,3, and 4. Installing these is a lot simpler than for other architectures/platforms like Intels or AMDs, which usually require preparing the boot media with a boot sector and some form of boot loader like syslinux. All PIs, in their pristine configuration, will boot from an SD card, that must simply contain some specific files, have a look here.

So for LEAF, we will simply unzip the corresponding PIn's (n=2,3,4) tarballs like Bering-uClibc_7.0.x_raspberry-rpi(n).tar.gz to a FAT32 formatted single partition SD card, nothing else, as the right files are all there. For the PI Zero and PI Zero W, use the rpi2 tarball. The last PI1 tarball is to be found in LEAF 6.2.7. simply as ...rpi.... The bootable .img files, when available, should also be copied to an SD card but using dd or the Raspberry PI Imager.

The PIs were designed to be accessed with a HDMI monitor or TV and a USB keyboard. The LEAF tarballs are built to be used that way too. The PI Zero will need a mini to standard HDMI adapter and a USB OTG micro B to A cable. Just insert the previously prepared SD card in the PI and power it up. You will get a display on your HDMI monitor just like on a VGA display and the keyboard will act like the Linux tty1 standard input device.

LEAF has been basically designed to use hardware platforms that have a minimum of 2 network interface controllers (NIC) in order to act as a router/firewall, a bridge or an access point. You should be somewhat familiar with LEAF before you try setting up a PI which basically possesses only one NIC. For this reason the detailed PIs's setups have been moved to the Advanced Topics: Setting up a Raspberry PI.

Download Location

Image file(s) should be downloaded from the LEAF files area on SourceForge: https://sourceforge.net/projects/leaf/files/Bering-uClibc/

For the quickest installation, look for the USB image files.

For the most basic standard Image variant, look for files named like Bering-uClibc_7.x.x_i486_isolinux_vga.tar.gz (ISO image to boot from CD-ROM) or Bering-uClibc_7.x.x_i486_syslinux_vga.tar.gz (Image to boot from USB-/Flash-/HD-drives).

It is advised to choose the latest available Bering-uClibc_7.x version.

Copying to the Installation Media

Simple copy for USB booting

The USB Images are delivered as .img files which must be copied to a USB key media using 'dd' on Linux or the 'Raspberry Pi Imager' on Windows and Macs.

These images contain a small system that is guaranty to boot from USB. This system is built with the minimum number of pre-configured packages to make it work as a "cable modem firewall". The goal here is to simplify the installation as much as possible mostly for new users but also for seasoned users who might not be fully aware of recent changes. It can then be used to evaluate/learn how LEAF works and eventually leads to the building of a more suitable/customized system by adding or removing specifics packages. To help the user even more, a built-in specialized script 'leafinstall' will allow the generation of a modern LEAF installation on popular medias like SD cards or USB keys. (check for hard disks on PCs or SSD on APU2s...)

• On Linux:

1. Download an image file, for instance Bering-uClibc_x86_ser.img
2. insert your USB key and check with 'dmesg', or 'fdisk -l' which device your PC assigned it to... let's assume we get: '/dev/sdb'

    cd ~/Downloads
    dd if=Bering-uClibc_x86_ser.img of=/dev/sdb bs=1M

• On Windows or Macs

1. Download the 'Raspberry Pi Imager'
2. Download the image file, again something like Bering-uClibc_x86_ser.img
3. Insert you USB key and start 'Raspberry Pi Imager'

    Click CHOOSE OS > Use custom > find /Downloads/Bering-uClibc_x86_ser.img > Open
    Click CHOOSE SD CARD > SanDisk Cruze U Media - 15.6 GB > WRITE

• Remove the flash media from the PC and proceed to the next Chapter.

Classical and still working other copy methods

These are the different ways LEAF is installed.

All of LEAF's tarballs and .img distributions, from version 7.0.1 and up, now come up with a pre-configured web browser access to eth1 at https://192.168.1.254  . It's all explained here.

Copying a syslinux Image to a Flash Media from a working Linux PC

The Images suitable for flash media (boot media type syslinux) are delivered as .tar.gz files which must be extracted onto suitably prepared flash media. The generic term "flash media" includes Compact Flash cards and USB "pen" or "thumb" drives. SD cards can also be used, but care must be taken if your target hardware has an SD card slot since Linux might then enumerate the SD card as /dev/mmcblk0 and /dev/mmcblk0p1 for the first partition. This will not be the case when this same SD card is inserted in an SD-to-USB converter in your external PC, the SD card will be seen as /dev/sdb... assuming your external PC's hard disk is already /dev/sda.

Although installing LEAF on a hard disk drive will be less reliable than on solid state devices like USB key, compact flash, SD, or SSD, the same procedure can be used. If you remember that the storage media will only be used on boot, you can always try to find a way to spin down your drive with hdparm in hdsupp.lrp, to reduce it's wear, but I have not tested this.

The structure of the files and directories within the .tar.gz file is as follows:

firmware.tgz
leaf.cfg
modules.sqfs
readme
syslinux/
  syslinux.cfg
  syslinux.dpy
  linux
*.lrp

The following steps assumes that the flash media will be prepared on a separate Linux PC system using a USB interface such as a 'Compact Flash-to-USB' or an 'SD-to-USB' adapter, and of course a straight USB key. You can't use the target system yet which will be running Bering-uClibc 7.x, has there is no way to boot it.

Preparing the Flash Media

For a standard Bering-uClibc 7.x installation, the flash media must:

• Be at least 130MB in size for a full installation.
  • By removing some of the large Packages this can be reduced significantly. 8MB is probably the absolute bare minimum.
• Have a single disk partition, which is flagged as bootable.
• Have a FAT32 file system on the boot partition. It is advised to format the disk with "-r 1024" to have enough root directory entries to install the Packages.

partition and format your media

On your external PC running Linux, insert your flash media, and run:

dmesg 
or
sudo fdisk -l

to see which device your media is assigned to, let's assume it is detected as: /dev/sdb...

in which case, start the fdisk utility to partition your media.

sudo fdisk /dev/sdb

The safest approach is to delete any existing partition on the media. To delete a partition type "d", to create a new partition type "n", choose "p" for a new primary partition, "1" for the partition number, accept the default values for First and Last Sector. To change the partition system id to W95 FAT32, choose "t" and "b". Lastly make the partition bootable, type "a" and "1" to make the first partition bootable.

You may have a look before writing the changes to your media with the command "p". It should show something like this:

Device      Boot      Start         End           Blocks      Id         System
/dev/sdb1    *         2048        524287         261120        b         W95 FAT32

Save your changes with the command "w" and leave the fdisk utility with "q".

Format the flash media:

sudo mkfs.vfat -r 1024 /dev/sdb1

Next you need to install the SYSLINUX bootloader onto the boot partition. Simply run:

sudo syslinux -i /dev/sdb1

Install the MBR code on the flash media:

dd bs=440 count=1 if=/usr/lib/syslinux/mbr/mbr.bin of=/dev/sdb

Please note /dev/sdb, this will write the Syslinux mbr code (mbr.bin) into the master boot record of the media.

Running syslinux -i results in file ldlinux.sys being created in the root of the FAT32 file system. Do not attempt to edit or move this file since that will break the SYSLINUX operation.

For Bering-uClibc 5.x the Linux kernel and the SYSLINUX configuration files have been relocated to the syslinux/ directory of the boot disk. However, file ldlinux.sys should remain in the root directory (although by using the -d directory argument to syslinux this can be moved to a different pre-existing directory on the boot disk, if desired).

Mount the media:

sudo mount /dev/sdb1 /mnt
cd /mnt

Extract your tarball: extract the contents of your tar.gz downloaded file with a command like the following

sudo tar -xvzf ~/Download/Bering-uClibc/7.0.2/Bering-uClibc_7.0.2_x86_64_syslinux_serial115200.tar.gz

Note: that this assumes the downloaded file is located in your $HOME/Download directory.

Do these extra steps if you are using the *_syslinux_vga.* images

When making the flash media from an external PC, we used the built-in PC's syslinux program. Since we don't know at this stage which syslinux version was used to generate the distribution c32 files, we have to copy hdt.c32, menu.c32, vesamenu.c32, libcom32.c32 and libutil.c32 files from the built-in syslinux program we used to create ldlinux.sys to ./syslinux directory of your mounted flash media.

For instance, in SYSLINUX 6.03 these files are in syslinux-6.03/bios/com32/hdt/hdt.c32, syslinux-6.03/bios/com32/menu/menu.c32, and syslinux-6.03/bios/com32/menu/vesamenu.c32.

They can also be found in /usr/lib/syslinux/modules/bios on Debian's...

An easy way to find these files is to:

cd /

sudo find . | grep /syslinux/modules/bios

Note: You don't have to do these extra steps if you are using the *_syslinux_serial.* images since they do not use these *.c32 files, so there will be no version conflicts.

A very important reminder here, before un-mounting your media: you should check that the variables PKGPATH=/dev/sda1:vfat in /mnt/leaf.cfg and LEAFCFG=/dev/sda1:vfat in /mnt/syslinux/syslinux.cfg will point to the correct device once inserted on your target platform. For most platform /dev/sda1 will be fine if it is the first and only media installed, but if you are using an SD card slot on your target, you might have to change sda1 to mmclbk0p1.

This all becomes irrelevant if you use leafinstall script to generate a new LEAF installation since UUIDs will be used to identify the medias. ( check 7.0.1 ??? I know 7.0.2 does it.)

Finally:

cd 
sudo umount /mnt

Remove the flash media from the Linux PC and proceed to the next Chapter.

Copying an isolinux Image to CD-ROM

The CD-ROM Images (boot media type isolinux) are delivered as .iso files which must be copied to CD-ROM media using an optical media "burning" program. Alternatively and especially for testing purposes, a Virtual PC solution (such as qemu or Virtualbox) can boot directly from a .iso file.

The structure of the files and directories within the ISO image is as follows:

firmware.tgz
isolinux/
  boot.cat
  isolinux.bin
  isolinux.cfg
  isolinux.dpy
  linux
leaf.cfg
modules.sqfs
readme
*.lrp

Install from CD-ROM to hard disk

Once you have created an ISO image file as shown above, you'll be able to boot from the ISO image. By default the Package hdsupp.lrp will be installed with all programs in place to format your already partitioned hard disk, install a bootloader and copy all files from the ISO image to the hard disk. It also makes the necessary changes to syslinux.cfg and leaf.cfg. The remaining step before reboot is eventually to toogle the bootable flag for your hard disk partition.

We assume in the following steps, that your hard disk is known as /dev/sda and you need only one partition.

Step 1: Partition your hard disk

Start the fdisk utility to partition your hard disk.

fdisk /dev/sda

To create a new partition type "n", choose "p" for a new primary partition, "1" for the partition number, accept the default values for First and Last Sector. To change the partition system id to W95 FAT32, choose "t" and "b".

You may have a look before writing the changes to your hard disk with the command "p". It should show something like this:

Device      Boot      Start         End           Blocks      Id         System
/dev/sda1             2048        524287         261120        b         W95 FAT32

Save your changes with the command "w".

Step 2: Install to hard disk

To run the installation from CD ROM to hard disk, start the LEAF configuration menu with "lrcfg". Choose "i) Install to FAT partition". It will show the available FAT partitions:

Available partitions to install LEAF:
1) /dev/sda1 - 261120 kB W95 FAT32

Select partition:

Type "1" to select your partition /dev/sda1 as installation target.

Syslinux will be installed to /dev/sda1, MBR code on /dev/sda1 will be updated.
Are you shure? (y/N)

Type "y", if you are shure and want to continue.

Format /dev/sda1? (y/N)?

Again type "y", if you are shure and want to continue. Your storage device will now be formatted.

Copy all files to storage? (y/N)?

Usually you will and respond with "y". Wait until you are requested to press any key to return.

Step 3: Toogle the bootable flag for your partition.

Last step is to toggle the bootable flag for the partition /dev/sda1. Again run fdisk.

fdisk /dev/sda

Print your partition table to screen with the command "p". It should look like this:

Device      Boot      Start         End           Blocks      Id         System
/dev/sda1    *        2048        524287         261120        b         W95 FAT32

If the asterisk is missing below the Boot row, type "a" and "1" to make the first partition bootable, and save your changes with the command "w". Otherwise leave the fdisk utility with "q".

Reboot, but be shure, that you have removed the CD from the drive before it the boot process starts.

Creating a multi-boot image with syslinux bootloader

Note1: This has only been tested with syslinux version 6.03, therefore LEAF Bering-uClibc 6.1.3 or later is required
You don't have to do all the steps in this section anymore since the same result can be obtained by running the script "leafinstall" on a working LEAF Bering-uClibc 6.1.3 or later system. The section is left here anyway as a reference.

This section describes how to create a multiboot setup with Syslinux bootloader. That way you can either have two partitions with the same setup to always have a working setup when updating the router with a new version or to have different setups side-by-side.

It is assumed that you use an ISO Image (/dev/sr0) to start with, but it will also be possible to install from an USB stick (e.g. /dev/sdb), on the condition that you install the Package hdsupp.lrp, which contains essential utilities like fdisk, syslinux, etc ... The recipe is given for a graphical display, changes needed if the LEAF router only has a serial console read the section Syslinux setup for a serial console

The disk layout will be:

/dev/sda1 - the boot partition, formatted with vfat
/dev/sda2 - the first partition with LEAF formatted with ext4
/dev/sda3 - the second partition with LEAF formatted with ext4

You need to have a syslinux bootloader on all partitions and chainload from /dev/sda1. This is a restriction by Syslinux not being able to load a kernel and initrd from another partition without chainloading.

Create, format the partitions and make /dev/sda1 bootable

We will create a boot partition on /dev/sda with 4MB of size, the two data partitions /dev/sda2 and /dev/sda3 with 200MB each.

To create the partitions run

# fdisk /dev/sda

Command (m for help): n
Select (default p): p
Partition number (1-4, default 1): 1
First sector [...]: ENTER
Last sector (...): +4M

Repeat for /dev/sda2 and /dev/sda3 but change the partition number and choose +200M instead of +4M.

Make the first partition /dev/sda1 bootable

 Command (m for help): a
 Partition number (1-3, default 3): 1

With the command p (print) you can see if everything is as expected. There should be three partitions of type "Linux", where the first is marked bootable with an asterisk.

Save your changes with w.

Format the partitions

The first (boot) partition will be formatted with vfat; the remaining data partitions with ext4. Currently extlinux does not support 64bit ext4, therefor we need to be careful with format command and disable the 64bit feature. To manually disable the "64bit" feature when creating ext4 volumes, use -O ^64bit in the mke2fs (or equivalent) command. That is, an hyphen, immediately followed by an upper-case letter "O", a space character, the caret "^" symbol, followed by "64bit" (no hyphen).

# mkfs.vfat /dev/sda1
# mkfs.ext4 -O ^64bit /dev/sda2
# mkfs.ext4 -O ^64bit /dev/sda3

Mount the data source

Before moving on you may create for your convenience a second mount point to mount the data source (here the ISO image /dev/sr0) until the following tasks are finished.

# mkdir /cdrom
# mount /dev/sr0 /cdrom

Install syslinux to the boot partition install the Master Boot Record mbr and create a boot menu

To install syslinux to /dev/sda1 mount /dev/sda1 to /mnt and create the syslinux directory:

# mount /dev/sda1 /mnt
# mkdir /mnt/syslinux

Unmount /dev/sda1 and install syslinux:

# umount /mnt
# syslinux -i /dev/sda1 -d syslinux

Next we install the Master Boot Record mbr to /dev/sda:

# dd bs=440 count=1 if=/usr/share/syslinux/mbr.bin of=/dev/sda

Finally the boot menu will be created. Again mount /dev/sda1 to /mnt and copy the necessary files from the data source mounted on /dev/cdrom. In case you use a USB stick instead of the ISO image the source will be syslinux instead isolinux

# mount /dev/sda1 /mnt
# cp /cdrom/isolinux/*.c32 /mnt/syslinux
# cp /cdrom/isolinux/leaf.jpg /mnt/syslinux
# cp /cdrom/isolinux/memtest.bin /mnt/syslinux

The boot menu will be in /mnt/syslinux/syslinux.cfg and should look like this:

# Wait for 3 seconds before booting up the default entry.
TIMEOUT 30

DEFAULT sda2

UI vesamenu.c32
MENU RESOLUTION 640 480
MENU BACKGROUND leaf.jpg

MENU HIDDEN

MENU COLOR sel 7;37;40    #ff000000 #20ff8000 all
MENU COLOR border 30;44 #00000000 #00000000 none

MENU COLOR tabmsg 31;40 #ff0000ff #00000000 none
MENU COLOR cmdmark 31;40 #ff0f0f0f #00000000 none
MENU COLOR cmdline 31;40 #ff0f0f0f #00000000 none
MENU COLOR timeout_msg 31;40 #ff0f0f0f #00000000 none
MENU COLOR timeout 31;40 #ff0000ff #00000000 none

#MENU AUTOBOOT Bering-uClibc {VERSION} Automatic boot in # second{,s}...

MENU TABMSGROW 21
MENU CMDLINEROW 21
MENU TIMEOUTROW 28
MENU HIDDENROW -1

MENU BEGIN 
LABEL sda2 
  MENU LABEL Boot LEAF Bering-uClibc from /dev/sda2
  com32 chain.c32
  append hd0 2
  
LABEL sda3
  MENU LABEL Boot LEAF Bering-uClibc from /dev/sda2
  com32 chain.c32
  append hd0 3

LABEL Hardware Test
  MENU LABEL Hardware Test
  MENU CLEAR
  KERNEL hdt.c32

LABEL memtest
 linux memtest.bin
MENU END

The boot menu can be copied from /cdrom/isolinux.cfg renamed to /mnt/syslinux/syslinux.cfg

# cp /cdrom/isolinux/isolinux.cfg /mnt/syslinux/syslinux.cfg

and edited accordingly.

Unmount /dev/sda1.

Install syslinux/extlinux to /dev/sda2 and /dev/sda3

Now it's time to make /dev/sda2 and /dev/sda3 bootable for the chainloading. Therefor the bootloader needs to be installed to the mounted partitions into /syslinux and a configuration file /syslinux/syslinux.cfg needs to be provided.

For /dev/sda2 we run:

# mount -t ext4 /dev/sda2 /mnt
# mkdir /mnt/syslinux
# extlinux -i /mnt/syslinux

Create syslinux.cfg in /mnt/syslinux with the content:

DEFAULT sda2
label sda2
kernel /linux
APPEND initrd=/initrd.lrp rw root=/dev/ram0 LEAFCFG=/dev/sda2:ext4 PKGPATH=/dev/sda2:ext4 reboot=bios usb_wait=3 intel_idle.max_cstate=0 processor.max_cstate=1 VERBOSE=1 quiet

Unmount /mnt.

Repeat this step for /dev/sda3 and replace every occurence of "sda2" with "sda3".

Install LEAF to the partitions

Mount /dev/sda2 to /mnt, copy the files from data source and disable PKGPATH in leaf.cfg.

# mount -t ext4 /dev/sda2 /mnt
# cp /cdrom/* /mnt

The PKGPATH in /mnt/leaf.cfg needs to be commented and changed to

#PKGPATH=[.../dev/sda1:vfat,...]

Important is the # sign to comment the PKGPATH, which is sourced in syslinux.cfg

Unmount /mnt and repeat this step for /dev/sda3.

Unmount /cdrom and reboot. If everything went well, you'll be able to boot from /dev/sda1 and then to either boot /dev/sda2 or /dev/sda3.

Syslinux setup for a serial console

If the LEAF router has no graphical display but serial line access, setting up is similar as described above. The relevant changes are the files necessary to get the output on the serial line. The relevant changes are the files needed for the Syslinux bootloader and the menu.

Install syslinux to the boot partition install the Master Boot Record mbr and create a boot menu

To install syslinux to /dev/sda1 mount /dev/sda1 to /mnt and create the syslinux directory:

# mount /dev/sda1 /mnt
# mkdir /mnt/syslinux

Unmount /dev/sda1 and install syslinux:

# umount /mnt
# syslinux -i /dev/sda1 -d syslinux

Next we install the Master Boot Record mbr to /dev/sda:

# dd bs=440 count=1 if=/usr/share/syslinux/mbr.bin of=/dev/sda

Finally the boot menu will be created. Again mount /dev/sda1 to /mnt and copy the necessary files from the data source mounted (usually /dev/sdb, we assume it is mounted on /mnt2, which needs to be created first). The source files will be in /mnt2/syslinux.

# mkdir /mnt2
# mount /dev/sdb1 /mnt2
# mount /dev/sda1 /mnt
# cp /mnt2/syslinux/chain.c32 /mnt/syslinux
# cp /mnt2/syslinux/libcom32.c32 /mnt/syslinux
# cp /mnt2/syslinux/libutil.c32 /mnt/syslinux
# cp /mnt2/syslinux/menu.c32 /mnt/syslinux
# cp /mnt2/syslinux/vesamenu.c32 /mnt/syslinux

The boot menu (TIMEOUT set to 20 sec) will be in /mnt/syslinux/syslinux.cfg and should look like this:

SERIAL 0 115200
DEFAULT sda2
TIMEOUT 200

UI vesamenu.c32
MENU BEGIN

MENU TITLE LEAF Bering-uClibc Boot Menu

label sda2
MENU LABEL Boot Default [sda2]
com32 chain.c32
append hd0 2

label sda3
MENU LABEL Boot Backup [sda3]
com32 chain.c32
append hd0 3
MENU END

Unmount /dev/sda1.

Install syslinux/extlinux to /dev/sda2 and /dev/sda3

Now it's time to make /dev/sda2 and /dev/sda3 bootable for the chainloading. Therefor the bootloader needs to be installed to the mounted partitions into /syslinux and a configuration file /syslinux/syslinux.cfg needs to be provided.

For /dev/sda2 we run:

# mount -t ext4 /dev/sda2 /mnt
# mkdir /mnt/syslinux
# extlinux -i /mnt/syslinux

Create syslinux.cfg in /mnt/syslinux with the content:

SERIAL 0 115200
DEFAULT sda2

label sda2
kernel /linux
APPEND initrd=/initrd.lrp rw root=/dev/ram0 LEAFCFG=/dev/sda2:ext4 PKGPATH=/dev/sda2:ext4 console=ttyS0,115200n8 reboot=bios usb_wait=3 intel_idle.max_cstate=0 processor.max_cstate=1 VERBOSE=1 quiet

Unmount /mnt.

Repeat this step for /dev/sda3 and replace every occurence of "sda2" with "sda3".

Copying a pxelinux Image to a Network Boot Server

Note: pxelinux boot support is currently under development and is not yet available in the standard Bering-uClibc 7.x downloads.

Much of the complexity of a pxelinux installation is associated with setup of the DHCP server that delivers the PXE boot filename, the TFTP server that delivers the initial boot image etc. These are not specific to Bering-uClibc 7.x and so are not covered in detail here but some guidelines and pointers to other sources of information can be found in the Network Booting Appendix.

The Images suitable for network booting (boot media type pxelinux) are delivered as .tar.gz files which must be extracted onto suitable file server(s).

The structure of the files and directories within the .tar.gz file is as follows:

tftpboot/
  bering-uclibc/
    5/
      gpxelinux.0
      pxelinux.0
      pxelinux.cfg/
        default
      pxelinux.dpy
fileserver/
  bering-uclibc/
    5/
      pxelinux/
          initrd.lrp
          linux
      firmware.tgz
      leaf.cfg
      modules.tgz
      readme
      *.lrp

File Server Protocol Selection

Bering-uClibc 7.x supports a number of different file sharing protocol options for network boot and installation (or at least it is planned to). These are:

FTP 

File Transfer Protocol, on TCP port 21

TFTP 

Trivial File Transfer Protocol, on UDP port 69

• Note that a TFTP server is essential for delivering the initial boot image, (g)pxelinux.0, and its configuration file.
• The same TFTP server can also be used for delivering the Linux kernel file (linux) and the initial RAM disk file (initrd.lrp).

HTTP 

HyperText Transport Protocol, on TCP port 80

SSH 

Secure SHell, on TCP port 22

• Note that this is not supported by (g)pxelinux.0 for delivering the Linux kernel file (linux) and the initial RAM disk files (initrd.lrp nd initmod.lrp) and hence cannot be used as the only network boot protocol.

For the purposes of this document it is assumed that TFTP will be used only to deliver (g)pxelinux.0 and pxelinux.cfg/default and that an HTTP server will be used to deliver the remainder of the files.

DHCP Server Configuration

It is assumed that you know how to configure your DHCP server for PXE booting. See the Network Booting Appendix for some Hints and Tips.

In summary, the DHCP server needs to:

• Issue an IPv4 address to the Bering-uClibc 7.x machine.
• Specify the "next server" IP address and a PXE "boot filename". Based on the structure within the pxelinux .tar.gz file this "boot filename" probably needs to be specified as: bering-uclibc/5/gpxelinux.0 since it is normally relative to the tftpboot/ level of the directory structure.

---

Prev

Up

Next