X-Git-Url: https://iankelling.org/git/?a=blobdiff_plain;f=fai%2Fconfig%2Fpackage_config%2FDEBIAN;h=fb14b468023d2490d4f4a552d6525f55f0ce1c92;hb=2028560d2467b5bbb3893b00369f123c90ef7282;hp=6e39b327a441414c6f9fb5cd6458b8f522ed8f43;hpb=ac8b8899763253d9b57a1f25feb5e064a415b0d7;p=automated-distro-installer diff --git a/fai/config/package_config/DEBIAN b/fai/config/package_config/DEBIAN index 6e39b32..fb14b46 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,11 +15,39 @@ 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. PACKAGES install GRUB_PC -grub-pc mdadm cryptsetup btrfs-tools sudo bridge-utils grub-legacy- lilo- +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 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 + +PACKAGES install CLOUD +locales-all +unattended-upgrades