Update of /cvsroot/leaf/doc/guide/install-bering-uclibc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv5206
Modified Files: buci-lrpkg.xml Log Message: Sdd chapters about leaf.cfg Index: buci-lrpkg.xml =================================================================== RCS file: /cvsroot/leaf/doc/guide/install-bering-uclibc/buci-lrpkg.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** buci-lrpkg.xml 17 Aug 2003 16:36:42 -0000 1.1 --- buci-lrpkg.xml 11 May 2004 09:14:07 -0000 1.2 *************** *** 12,15 **** --- 12,25 ---- </affiliation> </author> + + <author> + <firstname>Charles</firstname> + + <surname>Steinkuehler</surname> + + <affiliation> + <address><email>charles at steinkuehler.net</email></address> + </affiliation> + </author> </authorgroup> *************** *** 24,27 **** --- 34,47 ---- <revremark>Initial version</revremark> </revision> + + <revision> + <revnumber>0.2</revnumber> + + <date>2004-05-11</date> + + <authorinitials>kp</authorinitials> + + <revremark>Notes about new linuxrc and leaf.cfg in Bering-uClibc 2.2</revremark> + </revision> </revhistory> </chapterinfo> *************** *** 30,40 **** <section> ! <title>lrpkg.cfg vs. syslinux.cfg</title> ! <para>Bering uses <filename>syslinux.cfg</filename> defining the packages ! to be loaded. For larger installation <filename>lrpkg.cfg</filename> is ! recommended to avoid the 254 character limit of <filename>syslinux.cfg</filename>.</para> ! <para>Starting with version 2.0 Bering-uClibc uses <filename>lrpkg.cfg</filename> also in the standard floppy image to have one place for adding/removing packages, regardless you use a floppy with a few packages, or a large --- 50,183 ---- <section> ! <title>Objective</title> ! <para>For a long time package loading has been defined in ! <filename>syslinux.cfg</filename>. But this approach has it's ! drawbacks - it's not very flexible and the maximum kernel command line ! has a 254 characters limit.</para> ! <para>One of the first workarounds was the introduction of ! <filename>lrpkg.lrp</filename> in the Dachstein CD release by Charles ! Steinkuehler. Bering-uClibc versions 2.0 and 2.1 moved completly to the ! usage of <filename>lrpkg.lrp</filename> to define packages to load, even ! for floppies.</para> ! ! <para>But even that still isn't as flexible as it should be, ! especially working with other medias as floppy and CD aren't supported ! in a proper way.</para> ! ! <para>The latest attempt to overcome these limitations is a rewrite of ! <filename>linuxrc</filename> (responsible for accessing media and loading ! packages during boot process) and the introduction of ! <filename>leaf.cfg</filename> by Charles Steinkuehler.</para> ! ! <para>Bering-uClibc versions 2.2 and above use this new approach to ! configure package loading.</para> ! </section> ! ! <section> ! <title>Bering-uClibc 2.2 and above</title> ! ! <section> ! <title>Introduction</title> ! ! <para>The configuration is divided into two files, <filename>syslinux.cfg</filename> ! defines the place where <filename>leaf.cfg</filename> can be found ! during boot process. The packages to load and the devices to load from ! are defined in <filename>leaf.cfg</filename>.</para> ! </section> ! ! <section> ! <title>Changes in syslinux.cfg</title> ! ! <para>Opposed to all previous versions there must be neither packages ! nor devices defined in syslinux.cfg. You will have to configure the ! LEAFCFG variable instead.</para> ! ! <para>The variable has the following syntax: ! LEAFCFG=/dev/device[:filesystem]</para> ! ! <para>Any specified filesystem is tried first. If no filesystem is ! specified, or a mount using the specified filesystem fails for any ! reason, all filesystems currently enabled in the kernel (entries in ! /proc/filesystems that do not start with 'nodev') will be used ! to try to mount the configuration device.</para> ! ! <para>For a floppy it could be LEAFCFG=/dev/fd0u1680:msdos; for a ! harddisk something like LEAFCFG=/dev/hda1:msdos, for a CD-Rom it could ! be LEAFCFG=/dev/cdrom:iso9660.</para> ! </section> ! ! <section> ! <title>Configuring leaf.cfg</title> ! ! <para>Variables that may be set in <filename>leaf.cfg</filename> ! include:</para> ! ! <para>VERBOSE - (if non-null enables additional output from linuxrc</para> ! ! <para>LRP - Packages to load</para> ! ! <para>PKGPATH - Device(s) to load packages from</para> ! ! <para>syst_size - Size of root ramdisk</para> ! ! <para>tmp_size - Size of /tmp ramdisk</para> ! ! <para>log_size - Size of /var/log ramdisk</para> ! ! <para>Note that spaces, tabs, newlines, or commas may be used to ! separate entries in the LRP and PKGPATH variables.</para> ! ! <para>Below an example from the base image:</para> ! ! <screen>LRP="root config etc local modules iptables dhcpcd keyboard shorwall ulogd dnscache dropbear weblet" ! PKGPATH="/dev/fd0u1680:msdos" ! syst_size=6M ! log_size=2M</screen> ! </section> ! ! <section> ! <title>Additional capabilities of leaf.cfg</title> ! ! <para>It's still possible to use "LRP" and "PKGPATH" ! in syslinux.cfg, they can be extended in leaf.cfg by doing: ! LRP="$KCMD_LRP extrapackage" and ! PKGPATH="$KCMD_PKGPATH,/dev/mydev:newfs". </para> ! ! <para>Variables available for use in the leaf.cfg script include any ! kernel command line parameters (prefixed by KCMD_), the mount point of ! the LEAFCFG device (MNT), and available filesystems (FILESYSTEMS). See ! the linuxrc script for full details. Note that the leaf.cfg file is ! processed *BEFORE* any packages are loaded (in fact, before the package ! path and package list are finalized), so it would be possible, for ! example, to load any kernel modules or other software directly off the ! LEAFCFG= device required to read package files off of attached devices. ! It is only necessary to have support for the LEAFCFG= device either ! compiled into the kernel, or included in the /boot directory of the ! initial ramdisk.</para> ! ! <para>In addition, the leaf.cfg file is sourced as a shell script, ! allowing the potential for extention of the leafcfg scripts without ! requiring a modification of the physical boot media (ie: anything from:</para> ! ! <para>echo "Hi Mom!"</para> ! ! <para>to:</para> ! ! <para>insmod $MNT/MyWierdDevice.o --with-parameters</para> ! ! <para>insmod $MNT/NewFileSystem.o</para> ! ! <para>mknod /dev/mydevice -b 123 231</para> ! ! <para>PKGPATH="$KCMD_PKGPATH,/dev/mydev:newfs"</para> ! </section> ! </section> ! ! <section> ! <title>Bering-uClibc 2.0 and 2.1</title> ! ! <para>Bering-uClibc versions 2.0 and 2.1 use <filename>lrpkg.cfg</filename> also in the standard floppy image to have one place for adding/removing packages, regardless you use a floppy with a few packages, or a large ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ Leaf-cvs-commits mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits