Hi David;
Am Dienstag, 21. September 2010, 11:56:36 schrieb davidMbrooke:
> Hi,
>
> For Bering-uClibc 4 the Floppy Disk image is no more so
> tools/createimage.sh is not that useful. I see that Andrew has created
> tools/geniso.sh which works great but creates a 24MB ISO image
> containing all of the Packages and all of the Modules.
>
> Personally, I want to install Bering-uClibc 4 on a CF card and others
> might want a USB disk image or a PXE boot image instead of an ISO.
>
> I am also thinking that we might want different image variants -
> cut-down in size (to fit on a small CF card maybe), or tailored to
> specific hardware (such as the ALIX machines).
The build process really needs a consolidation and improvements.
Get rid of the floppy and have something special for cd, pxe, cf card will be a
step forward.
> I am thinking about writing a replacement script (e.g. called
> "buildimage.pl") which could be controlled by XML configuration files,
> one XML file per image to be created.
>
> What are the relevant image target types?
> * CF, USB (both with SYSLINUX)
> * ISO (with ISOLINUX)
> * PXE (PXELINUX) - probably a low priority
That would be a good start. Even with a plain setup as todays geniso script.
Once one can login and configure the network, changing leaf.cfg and loading new
lrp's is an somewhat easy task.
The following comments reflects just my personal views...
> What level of control should we support via the configuration files?
> * Manage the set of LRP files installed on the disk
leaf.cfg fits the needs, anythig else seems to be a bigger project ("remote
configuration").
> * Manage the settings in isolinux.cfg / syslinux.cfg ?
That would be a valuable addition. I had to modify syslinux.cfg to boot at all
with my controller, and that's not an easy task for a user. Maybe this is
solved with the latest changes Andrew made, but I expect that we run into
similar issues from time to time.
> * Manage the contents of moddb.lrp ?
Why? Ok, maybe for choosing some NIC that is not supported out of the box...
> * Manage the contents of modules.tgz ?
Please don't do that. modules.tgz has all the modules build with the kernel
and it's the easiest way to provide those without having the user to run a
build environment.
We even provided this file seperately in the download area, so one can
download it form sourceforge, untar it on the local machine and just scp the
modules needed to the leaf box.
kp
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
