+# duplicated in UBUNTU
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 STRETCH
+apt-transport-https
+
PACKAGES install NONFREE
# you may want these non-free kernel drivers
firmware-bnx2 firmware-bnx2x firmware-realtek
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
+# ian: 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.
+# take effect. This is explained when you do dpkg-reconfigure resolvconf,
+# and may be fixed in future releases
PACKAGES install GRUB_PC
grub-pc cryptsetup btrfs-tools mbuffer sudo bridge-utils netcat-openbsd resolvconf lsof
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