minor updates

[automated-distro-installer] / fai / config / package_config / DEBIAN

diff --git a/fai/config/package_config/DEBIAN b/fai/config/package_config/DEBIAN
index 9d13c310b49a5a043784f565a439047d39fa7eed..fb14b468023d2490d4f4a552d6525f55f0ce1c92 100644 (file)
--- a/fai/config/package_config/DEBIAN
+++ b/fai/config/package_config/DEBIAN
@@ -25,10 +25,25 @@ isc-dhcp-client
 # ian: note everything after the grub package should be refactored into
 # a new class.
 PACKAGES install GRUB_PC
-grub-pc cryptsetup btrfs-tools sudo bridge-utils netcat-openbsd
+grub-pc cryptsetup btrfs-tools sudo bridge-utils netcat-openbsd resolvconf
 
 PACKAGES install GRUB_EFI
-grub-efi cryptsetup btrfs-tools sudo bridge-utils netcat-openbsd
+grub-efi cryptsetup btrfs-tools sudo bridge-utils netcat-openbsd resolvconf
+
+
+#resolvconf because dpkg-reconfigure on it has this message in flidas:
+# Reboot recommended
+
+# Suppliers of name server information such as local caching name servers and interface configurers are expected to supply name server information to the resolvconf program. However, although
+# installation of the resolvconf package triggers them to supply their information, some of them fail to do so.
+
+# This bug would lead to loss of valid name server information on installation of the resolvconf package if the following workaround were not adopted: resolvconf includes the full contents of
+# the pre-installation /etc/resolv.conf in its database until reboot. This has the drawback that name server information is retained even if the associated interface is later deconfigured.
+# (This incorrect behavior is judged to be less harmful than the alternative of losing valid information.)
+
+# Until the bug in question is fixed and the workaround removed, the only way to ensure that resolvconf has fully correct name server information after the resolvconf package has been
+# installed on a running system is to reboot the system.
+
 
 PACKAGES install LVM
 lvm2