X-Git-Url: https://iankelling.org/git/?a=blobdiff_plain;f=fai%2Fconfig%2Fpackage_config%2FDEBIAN;h=d3e19e45c6363757921450e5ef43066dac427500;hb=5f680f6bea2faae10ca8e5ccea0d08d18ccc9aa1;hp=bdec0d61b64c6c54b89a8ded58ec9c548f48475b;hpb=056eb4e90e13b2d8f7cbb8c3b875f35bf0fa207e;p=automated-distro-installer

diff --git a/fai/config/package_config/DEBIAN b/fai/config/package_config/DEBIAN
index bdec0d6..d3e19e4 100644
--- a/fai/config/package_config/DEBIAN
+++ b/fai/config/package_config/DEBIAN
@@ -1,3 +1,8 @@
+PACKAGES install
+# you may want these non-free kernel drivers
+#firmware-bnx2 firmware-bnx2x firmware-realtek
+#firmware-linux
+
 PACKAGES install I386
 linux-image-686-pae initramfs-tools
 memtest86+
@@ -10,17 +15,43 @@ PACKAGES install AMD64
 linux-image-amd64 initramfs-tools
 memtest86+
 
+PACKAGES install ARM64
+grub-efi-arm64
+linux-image-arm64
+
 PACKAGES install DHCPC
 isc-dhcp-client
 
+# 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
+grub-pc cryptsetup btrfs-tools sudo bridge-utils netcat-openbsd resolvconf lsof
 
 PACKAGES install GRUB_EFI
-grub-efi
+grub-efi cryptsetup btrfs-tools 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
 locales-all
+unattended-upgrades