diff options
author | Raphaël Hertzog <hertzog@debian.org> | 2015-12-08 14:41:09 +0000 |
---|---|---|
committer | Raphaël Hertzog <hertzog@debian.org> | 2015-12-08 14:41:09 +0000 |
commit | e10dcd7f5b7ac524a0c1e707c812aef5b7b2909f (patch) | |
tree | 6d1f84b32d1275174ce5acd9944c6524b1ea792a | |
parent | 1dc2756298f9de153f9dcfac6277f1b8e82d4983 (diff) | |
download | installation-guide-e10dcd7f5b7ac524a0c1e707c812aef5b7b2909f.zip |
Document priority of preseeding between initrd and kernel command line
This is related to https://bugs.debian.org/805291
-rw-r--r-- | en/appendix/preseed.xml | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/en/appendix/preseed.xml b/en/appendix/preseed.xml index 126c31679..c80af7b19 100644 --- a/en/appendix/preseed.xml +++ b/en/appendix/preseed.xml @@ -119,9 +119,12 @@ installation methods. An important difference between the preseeding methods is the point at which the preconfiguration file is loaded and processed. For initrd preseeding this is right at the start of the installation, before the first question is -even asked. For file preseeding this is after the CD or CD image has been -loaded. For network preseeding it is only after the network has been -configured. +even asked. Preseeding from the kernel command line happens just after. It is +thus possible to override configuration set in the initrd by editing the kernel +command line (either in the bootloader configuration or manually at boot time +for bootloaders that allow it). For file preseeding this is after the CD +or CD image has been loaded. For network preseeding it is only after the +network has been configured. </para><important><para> |