diff options
author | Frans Pop <elendil@planet.nl> | 2007-10-21 13:22:07 +0000 |
---|---|---|
committer | Frans Pop <elendil@planet.nl> | 2007-10-21 13:22:07 +0000 |
commit | d5f638dcdb9eaa9e7a8e1a6dbdd442697122c7c4 (patch) | |
tree | bdf8208ecbc2374922dab93c4660ac04371cb0c2 /en | |
parent | 0400121d5a90b155e4c68a5e50f5e9c9c123ef4c (diff) | |
download | installation-guide-d5f638dcdb9eaa9e7a8e1a6dbdd442697122c7c4.zip |
Updates to appendix on chroot installs:
- add disclaimer: the appendix only covers the basic steps needed to install a system
- add a section with some basic instructions about creating device files
- add an 'initrd=' line to the example lilo.conf
Thanks to Igor Stirbu for noting the issue with missing device files and grub installation.
Diffstat (limited to 'en')
-rw-r--r-- | en/appendix/chroot-install.xml | 63 |
1 files changed, 63 insertions, 0 deletions
diff --git a/en/appendix/chroot-install.xml b/en/appendix/chroot-install.xml index 98b5232a4..ae60bd3a8 100644 --- a/en/appendix/chroot-install.xml +++ b/en/appendix/chroot-install.xml @@ -27,6 +27,19 @@ media. </para> +<note><para> + +As this is a mostly manual procedure, you should bear in mind that you +will need to do a lot of basic configuration of the system yourself, +which will also require more knowledge of Debian and of Linux in general +than performing a regular installation. You cannot expect this procedure +to result in a system that is identical to a system from a regular +installation. You should also keep in mind that this procedure only +gives the basic steps to set up a system. Additional installation and/or +configuration steps may be needed. + +</para></note> + <sect2> <title>Getting Started</title> <para> @@ -203,6 +216,49 @@ compatible with the Debian base system, for example: </para> <sect3> + <title>Create device files</title> +<para> + +At this point <filename>/dev/</filename> only contains very basic device +files. For the next steps of the installation additional device files may +be needed. There are different ways to go about this and which method you +should use depends on the host system you are using for the installation, +on whether you intend to use a modular kernel or not, and on whether you +intend to use dynamic (e.g. using <classname>udev</classname>) or static +device files for the new system. + +</para><para> + +A few of the available options are: + +<itemizedlist> +<listitem><para> + +create a default set of static device files using +<informalexample><screen> +# cd /dev +# MAKEDEV generic +</screen></informalexample> + +</para></listitem> +<listitem><para> + +manually create only specific device files using <command>MAKEDEV</command> + +</para></listitem> +<listitem><para> + +bind mount /dev from your host system on top of /dev in the target system; +note that the postinst scripts of some packages may try to create device +files, so this option should only be used with care + +</para></listitem> +</itemizedlist> + +</para> + </sect3> + + <sect3> <title>Mount Partitions</title> <para> @@ -515,6 +571,12 @@ The second command will install <command>grub</command> (in this case in the MBR of <literal>hda</literal>). The last command will create a sane and working <filename>/boot/grub/menu.lst</filename>. +</para><para> + +Note that this assumes that a <filename>/dev/hda</filename> device file has +been created. There are alternative methods to install <command>grub</command>, +but those are outside the scope of this appendix. + </para><para arch="x86"> Here is a basic <filename>/etc/lilo.conf</filename> as an example: @@ -526,6 +588,7 @@ install=menu delay=20 lba32 image=/vmlinuz +initrd=/initrd.img label=Debian </screen></informalexample> |