Changes between Version 24 and Version 25 of WikiStart


Ignore:
Timestamp:
06/07/10 12:32:04 (14 years ago)
Author:
bas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v24 v25  
    1414 * floppy disks
    1515
    16 When installing a image the target system shall be booted with a initrd which contains the needed utilities for initializing a SystemImager installation. This initrd is very basic. In most cases the SystemImager installation also uses the BOEL. This BOEL contains some necessary utilities for partitioning, formatting and Bittorrent.
     16When installing an image the target system shall be booted with a kernel/initrd which contains the needed utilities for initializing a SystemImager installation. This initrd is very basic.  When the system is booted it will fetch the [http://wiki.systemimager.org/index.php/BOEL BOEL] utilities. The BOEL utilites contains, eg:
     17 * kernel modules
     18 * partition utility
     19 * formatting utilities for ext2, ext3, xfs, ...
     20 * various protocols to get the image. 
    1721
    18 But the current inird and BOEL binaries of SystemImager is quite old. So we created Sali to replace '''only''' the kernel, initrd and BOEL. During the development we only focussed on PXE installations with rsync and/or Bittorrent. So you can't use for floppy disk or flamethrower/multicast. Also we focussed on supporting the 2.6 kernels. Because we removed floppy support we also removed the BOEL. The BOEL utilities are now implemented in the initrd.
     22Sali is created due the fact that the current initrd/kernel and BOEL utilities are outdated. The trigger was that there is no ''grub2'' support. We thought this could be easily added, but during this process we decided to upgrade all software to the newest levels. The biggest hurdle was detecting of which hardware is in the system ([http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html udev]). We believe that SALI is better in detecting which hardware is in the system then the systemimager setup.
     23
     24The focus for this project is/was:
     25 * Easily create a new kernel/initrd when a new kernel is released or one of the sofware compents is update, eg: [http://www.busybox.net busybox]. The sali initrd contains all kernel modules and software utilities.  In systemimager this software is distributes as separate packagge (BOEL binaries).
     26
     27 * PXE installations with rsync and/or Bittorent. Drop support for flamthrower/multicast and floppy disk support.
     28
     29But the current initrd and BOEL binaries of SystemImager is quite old. So we created Sali to replace '''only''' the kernel, initrd and BOEL. During the development we only focussed on PXE installations with rsync and/or Bittorrent. So you can't use for floppy disk or flamethrower/multicast. Also we focussed on supporting the 2.6 kernels. Because we removed floppy support we also removed the BOEL. The BOEL utilities are now implemented in the initrd.
    1930
    2031Also we started to increase the functionality of /etc/init.d/functions with some functions that could replace a lot of code in you Master script ( Sali supports the Master Script generated by SystemImage 4.1.6 ). For detailed overview of the changes read this [source:trunk/Changelog changelog].