Menu
▾
▴
[Devil-linux-commit] build/docs/documentation documentation.xml,1.57,1.58
|
From: Heiko Z. <smi...@us...> - 2004-04-15 23:58:43
|
Update of /cvsroot/devil-linux/build/docs/documentation In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv22658/documentation Modified Files: documentation.xml Log Message: some documentation updates for new release Index: documentation.xml =================================================================== RCS file: /cvsroot/devil-linux/build/docs/documentation/documentation.xml,v retrieving revision 1.57 retrieving revision 1.58 diff -u -d -r1.57 -r1.58 --- documentation.xml 25 Jan 2004 02:07:06 -0000 1.57 +++ documentation.xml 15 Apr 2004 23:58:34 -0000 1.58 @@ -17,7 +17,7 @@ <book> <title>Devil-Linux Documentation</title> <bookinfo> - <subtitle>This documentation is for v1.1 and above</subtitle> + <subtitle>This documentation is for v1.2 and above</subtitle> <subtitle>$Revision$ $Date$ </subtitle> <mediaobject role="online"> <imageobject> @@ -879,7 +879,7 @@ <para>Everything, except of modififying files as to be done within a chroot environment. Execute the newly created alias <command>cr</command> to change into the build system.</para> <para>Now you can go into the folder <filename>build/</filename> and just execute the command <command>make</command> to get an overview which parameters are available. A more detailed explanation will follow later.</para> <para>The first command you should execute is <command>make unpack</command>, after that you configure the build system via the command <command>make menuconfig</command>.</para> - <para>Now you can start the build process: <command>make build install iso dist</command></para> + <para>Now you can start the build process: <command>make build install prepare iso dist</command></para> <para>Once this is done, you find in the directory <command>build/dist</command> a ready to use DL version. ;-)</para> <para>When you're working on DL and want to test the ISO with e.g. VMWare, then you can skip the <command>make dist</command> part and you find a useable ISO image here: <filename>build/tmp/bootcd.iso</filename></para> <para>You can create a configuration floppy disc by invocing the command <filename>build/scripts/build-etc</filename><caution> @@ -942,30 +942,18 @@ <entry>The acutal scripts which compile, install and create DL.</entry> </row> <row> - <entry><filename>build/scripts/build</filename></entry> - <entry>Links (empty files) which define the execution order of the scripts for the <filename>make build</filename> command.The name after the number (3 digits) is the exact same name as the script in the <filename>build/script</filename> directory. Each script is called with the parameter <quote>build</quote>.</entry> - </row> - <row> <entry><filename>build/scripts/config</filename></entry> <entry>Configuration files which are needed for build process. You find here for example the initial Kernel configuration file (<filename>config_kernel</filename>).</entry> </row> <row> - <entry><filename>build/scripts/config</filename></entry> + <entry><filename>build/scripts/config</filename>uration</entry> <entry>Scripts which are used the generate the menu structure for the command: <command>make menuconfig</command>.</entry> </row> <row> - <entry><filename>build/scripts/config/help</filename></entry> + <entry><filename>build/scripts/configuration/help</filename></entry> <entry>Files which hold the help information for entries in <command>make menuconfig</command>.</entry> </row> <row> - <entry><filename>build/scripts/install</filename></entry> - <entry>Links (empty files) which define the execution order of the scripts for the <filename>make install</filename> command.The name after the number (3 digits) is the exact same name as the script in the build/script directory. Each script is called with the parameter <quote>install</quote>. This directory is also used, when you execute a <command>make menuconfig</command>, in this case the scripts are called with the parameter <quote>config</quote>.</entry> - </row> - <row> - <entry><filename>build/scripts/iso</filename></entry> - <entry>Links (empty files) which define the execution order of the scripts for the <filename>make iso</filename> command.The name after the number (3 digits) is the exact same name as the script in the build/script directory. Each script is called with the parameter <quote>iso</quote>.</entry> - </row> - <row> <entry><filename>build/scripts/lxdialog</filename></entry> <entry>Sources of the lxdialog program, will be automatically compiled when you use <filename>make menuconfig</filename></entry> </row> @@ -1016,7 +1004,7 @@ <sect2> <title>The build process</title> <para>By invoking the command <command>make build</command>, the <filename>Makefile</filename> will execute the script <filename>build/scripts/build.sh</filename> with the parameter <parameter>build</parameter>.</para> - <para>The script will now look in the folder <filename>build/scripts/build</filename> for the first build script to call, ,this will be <filename>001prepare</filename>. Now the <filename>build/tmp </filename>directory is checked, if the script was already successfully executed. The flag-file is called in this case <filename>.done_build_001_prepare</filename>. When this file doesn't exist, the script <filename>build/scripts/prepare</filename> is called with the parameter <parameter>build</parameter>, otherwise the build script will continue with the next file. After a sub-script was successfully executed ( return code 0 ), the flag file is created and the build script starts at the beginning.</para> + <para>The script will now look in the folder <filename>build/scripts/.buildorder/rc1.d</filename> for the first build script to call, ,this will be <filename>S01prepare</filename>. Now the <filename>build/tmp </filename>directory is checked, if the script was already successfully executed. The flag-file is called in this case <filename>.done_build_001_prepare</filename>. When this file doesn't exist, the script <filename>build/scripts/prepare</filename> is called with the parameter <parameter>build</parameter>, otherwise the build script will continue with the next file. After a sub-script was successfully executed ( return code 0 ), the flag file is created and the build script starts at the beginning.</para> <para>This description counts for the make commands <command>build</command>, <command>install</command> and <command>iso</command>, you just have to replace the <quote>build</quote> parts with e.g. <quote>install</quote>.</para> <tip> <para>When you test your own scripts, you can easily force a recompilation by executing e.g. <command>rm build/tmp/.done_build_123_foo</command></para> @@ -1033,18 +1021,14 @@ </note> <para>Here is a sample script:</para> <para><programlisting>&sample1;</programlisting></para> - <para>Now you have to activate that script by creating the links:</para> - <para><command>touch build/scripts/build/270ez-ipupdate</command></para> - <para><command>touch build/scripts/install/270ez-ipupdate</command></para> - <caution> - <para>The links below 100 are reserved for system preparation and libraries!</para> - </caution> - <para></para> - <para>Don't forgett to execute <command>make menuconfig</command> and enable the program you just added.</para> + <para>Now you have to activate that script by running <command moreinfo="none">make prepare</command> again.</para> + <note> + <para>Don't forgett to execute <command moreinfo="none">make menuconfig</command> and enable the program you just added.</para> + </note> </sect2> <sect2> <title>Adding Libraries</title> - <para>Libraries are the same as any other script, except that you usually don't have the <quote>install)</quote> part and so also not the link within the <filename>build/install</filename> directory. Libraries must be installed within the <quote>build)</quote>, otherwise they're not available for the other scripts. </para> + <para>Libraries are the same as any other script, except that you usually don't have the <quote>install)</quote> part. Libraries must be installed within the <quote>build)</quote>, otherwise they're not available for the other scripts. </para> </sect2> <sect2> <title>Runlevel configuration</title> @@ -1151,6 +1135,7 @@ <para><ulink url="http://www.fwbuilder.org">Firewall Builder</ulink></para> <para><ulink url="http://www.selflinux.de/">Selflinux</ulink> (German Linux tips and documentation)</para> <para><ulink url="http://www.chronox.de">Compartment site</ulink> (new maintainer)</para> + <para><ulink url="ftp://ftp.fl.priv.at/pub/devil-linux/DIALIN-HOWTO.txt">Dialin-HOWTO</ulink> for Devil-Linux</para> </appendix> <appendix> <title>HOWTO burn with Windows</title> |
