Menu
▾
▴
[Devil-linux-commit] build/docs/documentation documentation.xml,1.61,1.62
|
From: Heiko Z. <smi...@us...> - 2004-06-27 14:04:58
|
Update of /cvsroot/devil-linux/build/docs/documentation In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv32110 Modified Files: documentation.xml Log Message: added documentation for new boot process Index: documentation.xml =================================================================== RCS file: /cvsroot/devil-linux/build/docs/documentation/documentation.xml,v retrieving revision 1.61 retrieving revision 1.62 diff -u -d -r1.61 -r1.62 --- documentation.xml 24 Jun 2004 01:23:06 -0000 1.61 +++ documentation.xml 27 Jun 2004 14:04:46 -0000 1.62 @@ -130,6 +130,162 @@ </sect2> </sect1> <sect1> + <title id="boot_process">The Boot Process</title> + <sect2> + <title>The Boot Screen</title> + <para> When booting Devil-Linux a screen with a boot prompt will appear. Several boot options can be entered now which have an impact on the boot process. A short help on this topic can also be accessed at the boot prompt by pressing <keycombo> + <keycap>F1</keycap> + </keycombo>, then follow the instructions stated there. </para> + </sect2> + <sect2> + <title>DL-Specific Boot Options</title> + <para>Primarily, Devil-Linux will search for a file called <filename>etc.tar.bz2</filename> on any block device it finds in your system. These devices are :</para> + <table> + <title>List of devices scanned for config files</title> + <tgroup cols="3"> + <thead> + <row> + <entry align="center">Devices</entry> + <entry align="center">Hardware</entry> + <entry align="center">Comment</entry> + </row> + </thead> + <tbody> + <row> + <entry>/dev/ide/.../cd*</entry> + <entry>IDE CD-Roms</entry> + <entry>Your DL CD is probably among these...</entry> + </row> + <row> + <entry>/dev/scsi/.../cd*</entry> + <entry>SCSI CD-Roms</entry> + <entry>...or these devices</entry> + </row> + <row> + <entry>/dev/ide/.../part*</entry> + <entry>IDE Partitions</entry> + <entry>Partitions on your IDE hard disks</entry> + </row> + <row> + <entry>/dev/scsi/.../part*</entry> + <entry>SCSI Partitions</entry> + <entry>Partitions on your SCSI hard disks</entry> + </row> + <row> + <entry>/dev/scsi/.../disc</entry> + <entry>SCSI harddiscs</entry> + <entry>Could also be USB sticks</entry> + </row> + <row> + <entry>/dev/floppy/?</entry> + <entry>Floppy discs</entry> + <entry>/dev/floppy/0 is your first floppy drive</entry> + </row> + </tbody> + </tgroup> + </table> + <note> + <para>There are abbreviations like <filename>/dev/discs/discX/partY</filename> for partition Y (starting at 1) on disc X (starting at 0), e.g. <filename>/dev/discs/disc1/part1</filename> for <filename>/dev/hdb1</filename>.</para> + </note> + <para>You can also tune the process of scanning for a configuration archive with these parameters:</para> + <sect3> + <title>DL_config=device1:filename1,device2:filename,...</title> + <para>This parameter lets you add devices and configuration filenames to the scanning process. Supply blocks seperated by commas <quote>,</quote> of devicenames and filenames seperated by colons <quote>:</quote>. Your input will always be honored before the standard devices and standard archive <filename>etc.tar.bz2</filename>. The scanning will end as soon as the first valid archive is found.</para> + <para>The parameter will be interpreted as follows:</para> + <itemizedlist> + <listitem> + <para>The string is cut at the commas and every substring is considered (from left to right).</para> + </listitem> + <listitem> + <para>Every substring is parsed and used as followed:</para> + <itemizedlist> + <listitem> + <para>if a colon is found, the string <emphasis>before</emphasis> the colon is taken as <emphasis>devicename</emphasis>, the string <emphasis>after</emphasis> the colon as <emphasis>filename</emphasis>.</para> + <para>You need not to specify a colon if you only want to enter a devicename or filename. Empty devicenames and filenames are <emphasis>not</emphasis> an error. But if you supply the colon, be sure to place it after the devicename or before the filename.</para> + <para>The given device will then be searched for the specified filename.</para> + </listitem> + <listitem> + <para>if no colon is found, and the string contains <quote>/dev/</quote> it is handled as a device.</para> + <para>This device is then scanned for the standard archive <filename>etc.tar.bz2</filename>.</para> + </listitem> + <listitem> + <para>if no colon is found, and the string does not contain <quote>/dev/</quote> it is handled as a filename. All discovered standard devices are scanned for this file.</para> + </listitem> + </itemizedlist> + </listitem> + </itemizedlist> + <para>Beware that DL will generate an error message and two alarms for every option that was entered falsely: It is wrong for a device name not to contain <quote>/dev/</quote> and conversely wrong for the filename to contain <quote>/dev/</quote>. Even if only one specifier (device or filename) of a statement is illegal it will be discarded. These sanity checks are not complete and they never can be. Be sure to double check your input or you could damage your system.</para> + </sect3> + <sect3> + <title>DL_config_no_scan</title> + <para>If you add this parameter, scanning for the standard archive etc.tar.bz2 on the standard devices will be omitted!</para> + <para>Only supply this option, if you also specified a valid <quote>DL_config=...</quote> option or no scanning will be done at all. This would result in no config being loaded and Devil-Linux will ask you to load an empty configuration from the Devil-Linux medium. That is probably not what you want.</para> + </sect3> + </sect2> + <sect2> + <title>Boot Option Examples</title> + <sect3> + <title>Using a Backup</title> + <para>Let's say you have a floppy drive which you normally use for the configuration archive but you have another archive called <filename>backup.tar.bz2</filename> saved on a hard disk partition somewhere. You reboot to test new hardware, but booting now fails. To make use of the backup config, append this at the boot prompt: <command>DL_config=backup.tar.bz2</command></para> + <para>If your config is found, it will look like this:</para> + <screen> +Searching for configuration media +Trying to load configuration <quote>backup.tar.bz2</quote> from any device. +Checking for <quote>backup.tar.bz2</quote> on <quote>/dev/ide/host0/bus0/target1/lun0/part1</quote> ... success! +loading configuration + </screen> + <para>If not, it will looke like this:</para> + <screen> +Searching for configuration media +Trying to load configuration <quote>backup.tar.bz2</quote> from any device. +Checking for <quote>backup.tar.bz2</quote> on <quote>/dev/ide/host0/bus0/target1/lun0/part1</quote> ... file not found. +Checking for <quote>backup.tar.bz2</quote> on <quote>/dev/ide/host0/bus1/target0/lun0/part1</quote> ... mount failed. +Checking for <quote>backup.tar.bz2</quote> on <quote>/dev/ide/host0/bus0/target1/lun0/cd</quote> ... file not found. +Checking for <quote>backup.tar.bz2</quote> on <quote>/dev/floppy/0</quote> ... file not found. +Sorry, could not load your configuration. Continuing searching... +Checking for <quote>etc.tar.bz2</quote> on <quote>/dev/ide/host0/bus0/target1/lun0/part1</quote> ... file not found. +Checking for <quote>etc.tar.bz2</quote> on <quote>/dev/ide/host0/bus1/target0/lun0/part1</quote> ... mount failed. +Checking for <quote>etc.tar.bz2</quote> on <quote>/dev/ide/host0/bus0/target1/lun0/cd</quote> ... file not found. +Checking for <quote>etc.tar.bz2</quote> on <quote>/dev/floppy/0</quote> ... success! +loading configuration + </screen> + </sect3> + <sect3> + <title>Using multiple options</title> + <para>Here is an example for supplying multiple options: <command>DL_config=fail.tar.bz2,/dev/discs/disc0/part1:backup.tar.bz2,:/dev/floppy/0</command>. This results to the following list of scans:</para> + <itemizedlist> + <listitem> + <para>file <filename>fail.tar.bz2</filename> on any device</para> + </listitem> + <listitem> + <para><filename>backup.tar.bz2</filename> on first partition on first harddisk</para> + </listitem> + <listitem> + <para><command>:/dev/floppy/0</command> improper option (see above) will be skipped</para> + </listitem> + <listitem> + <para>standard scan for <filename>etc.tar.bz2</filename></para> + </listitem> + </itemizedlist> + <screen> +Searching for configuration media +Trying to load configuration <quote>fail.tar.bz2</quote> from any device. +Checking for <quote>fail.tar.bz2</quote> on <quote>/dev/ide/host0/bus0/target1/lun0/part1</quote> ... file not found. +Checking for <quote>fail.tar.bz2</quote> on <quote>/dev/ide/host0/bus1/target0/lun0/part1</quote> ... mount failed. +Checking for <quote>fail.tar.bz2</quote> on <quote>/dev/ide/host0/bus0/target1/lun0/cd</quote> ... file not found. +Checking for <quote>fail.tar.bz2</quote> on <quote>/dev/floppy/0</quote> ... file not found. +Sorry, could not load your configuration. Continuing searching... +Trying to load configuration <quote>backup.tar.bz2</quote> from device <quote>/dev/discs/disc0/part1</quote>. +Checking for <quote>backup.tar.bz2</quote> on <quote>/dev/discs/disc0/part1</quote> ... file not found. +Sorry, could not load your configuration. Continuing searching... +Improper config parameter : <quote>:/dev/floppy/0</quote>. Ignored... +Checking for <quote>etc.tar.bz2</quote> on <quote>/dev/ide/host0/bus0/target1/lun0/part1</quote> ... success! +loading configuration + </screen> + </sect3> + </sect2> + </sect1> + <sect1> <title id="general_configuration">General Configuration</title> <sect2> <title>Initial Configuration via Setup program</title> @@ -331,11 +487,11 @@ <para>Routing is defined in the network interface configuration files.</para> <para>The format for an routing entry is: <command>GATEWAY:NET/MASK</command> , i.e. <command><command></command>ROUTE="10.90.1.253:192.168.2.0/255.255.255.0"</command> </para> <para>See this example for some more details:</para> - <screen>### ROUTE="GATEWAY:NET/MASK" + <screen>### ROUTE="GATEWAY:NET/MASK" #ROUTE="10.90.1.253:192.168.2.0/255.255.255.0" -### if you don't have a gateway use: -#ROUTE=":192.168.2.0/255.255.255.0" -### for more than one route use: +### if you don't have a gateway use: +#ROUTE=":192.168.2.0/255.255.255.0" +### for more than one route use: #ROUTE="$ROUTE 10.90.1.252:192.168.3.0/255.255.255.0" # ## if you have only a host: #ROUTE="$ROUTE 10.90.1.251:172.16.3.14" </screen> @@ -371,7 +527,7 @@ <para>In order to enable harddisk support for Devil-Linux, you have to install the LVM Tools.</para> <sect2> <title>Create Partition</title> - <para>Create one partition on the harddisk you want to use using the command fdisk. The result of <command>fdisk -l</command> should look like this:<screen>Disk /dev/hdc: 16 heads, 63 sectors, 8126 cylinders + <para>Create one partition on the harddisk you want to use using the command fdisk. The result of <command>fdisk -l</command> should look like this:<screen>Disk /dev/hdc: 16 heads, 63 sectors, 8126 cylinders Units = cylinders of 1008 * 512 bytes Device Boot Start End Blocks Id System /dev/hdc1 1 8126 4095472+ 8e Linux LVM </screen></para> @@ -487,7 +643,7 @@ Device Boot Start End Blocks Id System /dev/hda1 1 79780 40209088+ fd Linux raid autodetect - + Disk /dev/hdc: 16 heads, 63 sectors, 79780 cylinders Units = cylinders of 1008 * 512 bytes |
