2 # you may want these non-free kernel drivers
3 #firmware-bnx2 firmware-bnx2x firmware-realtek
7 linux-image-686-pae initramfs-tools
10 PACKAGES install CHROOT
14 PACKAGES install AMD64
15 linux-image-amd64 initramfs-tools
18 PACKAGES install ARM64
22 PACKAGES install DHCPC
25 # ian: note everything after the grub package should be refactored into
26 # a new class. This line is duplicated in UBUNTU
27 # lsof is used in my btrfs util scritps.
28 # netcat is used for proxy.
29 # resolvconf because if we don't install it now we have to reboot for it to
31 PACKAGES install GRUB_PC
32 grub-pc cryptsetup btrfs-tools mbuffer sudo bridge-utils netcat-openbsd resolvconf lsof
34 PACKAGES install GRUB_EFI
35 grub-efi cryptsetup btrfs-tools mbuffer sudo bridge-utils netcat-openbsd resolvconf lsof
38 #resolvconf because dpkg-reconfigure on it has this message in flidas:
41 # 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
42 # installation of the resolvconf package triggers them to supply their information, some of them fail to do so.
44 # 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
45 # 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.
46 # (This incorrect behavior is judged to be less harmful than the alternative of losing valid information.)
48 # 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
49 # installed on a running system is to reboot the system.
55 PACKAGES install CLOUD