2 apt-transport-https # is only needed for stretch
8 openssh-client openssh-server
18 PACKAGES install NONFREE
19 # you may want these non-free kernel drivers
20 firmware-bnx2 firmware-bnx2x firmware-realtek
21 firmware-linux-nonfree
27 PACKAGES install CHROOT
31 PACKAGES install AMD64
35 PACKAGES install ARM64
39 # ian: note everything after the grub package should be refactored into
40 # a new class. This line is duplicated in UBUNTU
41 # lsof is used in my btrfs util scritps.
42 # netcat is used for proxy.
43 # resolvconf because if we don't install it now we have to reboot for it to
45 PACKAGES install GRUB_PC
46 grub-pc cryptsetup btrfs-tools mbuffer sudo bridge-utils netcat-openbsd resolvconf lsof
48 PACKAGES install GRUB_EFI
49 grub-efi cryptsetup btrfs-tools mbuffer sudo bridge-utils netcat-openbsd resolvconf lsof
52 #resolvconf because dpkg-reconfigure on it has this message in flidas:
55 # 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
56 # installation of the resolvconf package triggers them to supply their information, some of them fail to do so.
58 # 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
59 # 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.
60 # (This incorrect behavior is judged to be less harmful than the alternative of losing valid information.)
62 # 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
63 # installed on a running system is to reboot the system.
69 PACKAGES install CLOUD