+# 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
$l.4 htpc
$l.5 x2
$l.6 demohost
-#$l.7 faiserver
+$l.7 x3
$l.8 tp faiserver b8.nz
-$l.9 n5
-$l.10 so
-$l.12 fz
72.14.176.105 li
-45.33.9.11 lj
-138.68.10.24 dopub
+
# netns creation looks for next free subnet starting at 10.173, but I only
# use one, and I would keep this one as the first created.
10.173.0.2 transmission
dhcp-host=00:26:18:97:bb:16,set:frodo,$l.3,frodo
dhcp-host=10:78:d2:da:29:22,set:htpc,$l.4,htpc
dhcp-host=00:1f:16:16:39:24,set:x2,$l.5,x2
-#dhcp-host=00:c0:ca:27:e9:b2,set:x2w,$l.11,x2w
-#wireless interface
-# this is so fai can have an explicit name to use for testing,
+# This is so fai can have an explicit name to use for testing,
# or else any random machine which did a pxe boot would get
# reformatted. The mac is from doing a virt-install, cancelling it,
# and copying the generated mac, so it should be randomish.
dhcp-host=52:54:00:9c:ef:ad,set:demohost,$l.6,demohost
-#dhcp-host=52:54:00:56:09:f9,set:faiserver,$l.7,faiserver
+dhcp-host=00:1f:16:14:01:d8,set:tp,$l.7,x3
dhcp-host=80:fa:5b:1c:6e:cf,set:tp,$l.8,tp
-# this is the ip it picks by default if dhcp fails,
+
+# faiserver vm
+dhcp-host=52:54:00:56:09:f9,set:faiserver,$l.15,faiserver
+
+# This is the ip it picks by default if dhcp fails,
# so might as well use it.
# hostname is the name it uses according to telnet
dhcp-host=b4:75:0e:94:29:ca,set:switch9429ca,$l.251,switch9429ca