merge upstream, untested

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

diff --git a/fai/config/package_config/DEBIAN b/fai/config/package_config/DEBIAN
index 6e39b327a441414c6f9fb5cd6458b8f522ed8f43..1c7cc732aec8cc0772046687db15ecc123ce9847 100644 (file)
--- a/fai/config/package_config/DEBIAN
+++ b/fai/config/package_config/DEBIAN
@@ -1,5 +1,27 @@
+PACKAGES install-norec
+apt-transport-https # is only needed for stretch
+debconf-utils
+file
+less
+linuxlogo
+rsync
+openssh-client openssh-server
+time
+procinfo
+nullmailer
+eject
+locales
+console-setup kbd
+pciutils usbutils
+unattended-upgrades
+
+PACKAGES install NONFREE
+# you may want these non-free kernel drivers
+firmware-bnx2 firmware-bnx2x firmware-realtek
+firmware-linux-nonfree
+
 PACKAGES install I386
-linux-image-686-pae initramfs-tools
+linux-image-686-pae
 memtest86+
 
 PACKAGES install CHROOT
@@ -7,14 +29,42 @@ linux-image-686-pae-
 linux-image-amd64-
 
 PACKAGES install AMD64
-linux-image-amd64 initramfs-tools
+linux-image-amd64
 memtest86+
 
-PACKAGES install DHCPC
-isc-dhcp-client
+PACKAGES install ARM64
+grub-efi-arm64
+linux-image-arm64
 
+# ian: note everything after the grub package should be refactored into
+# a new class. This line is duplicated in UBUNTU
+# lsof is used in my btrfs util scritps.
+# netcat is used for proxy.
+# resolvconf because if we don't install it now we have to reboot for it to
+# take effect.
 PACKAGES install GRUB_PC
-grub-pc mdadm cryptsetup btrfs-tools sudo bridge-utils grub-legacy- lilo-
+grub-pc cryptsetup btrfs-tools mbuffer sudo bridge-utils netcat-openbsd resolvconf lsof
+
+PACKAGES install GRUB_EFI
+grub-efi cryptsetup btrfs-tools mbuffer sudo bridge-utils netcat-openbsd resolvconf lsof
+
+
+#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
+
+PACKAGES install CLOUD
+unattended-upgrades