diff options
| -rw-r--r-- | debian/changelog | 5 | ||||
| -rw-r--r-- | en/appendix/chroot-install.xml | 63 |
2 files changed, 67 insertions, 1 deletions
diff --git a/debian/changelog b/debian/changelog index f95fa136d..858f70870 100644 --- a/debian/changelog +++ b/debian/changelog @@ -41,13 +41,16 @@ installation-guide (2007xxxx) UNRELEASED; urgency=low * Extend the documentation of apt-setup, especially the decision whether or not to use a network mirror. Document selection of services. * Document new apt-setup/services-select and related hostname preseeds. + * Add some information about creating device files in the appendix on chroot + installs; also add a note that the appendix only covers the basic steps + of a chroot install. [ Joey Hess ] * Document how to preseed partman-auto to use only available disk, no matter what it's name is. * debian/rules: call dh_md5sums. - -- Frans Pop <fjp@debian.org> Sat, 20 Oct 2007 20:52:43 +0200 + -- Frans Pop <fjp@debian.org> Sun, 21 Oct 2007 15:14:48 +0200 installation-guide (20070319) unstable; urgency=low 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> |