Because the new build host is debian, we need to make sure that
the qemu binaries are copied in, systemd doesn't happen transparently yet.
Next Debian stable release should make this commit obsolete.
Also don't mkdir the usr/bin directory, we actually want it to error out
if it doesn't exist.
Disable 64bit options on most of the ext4 partitions, fix any /lib paths
to now be /usr/lib since /lib is just a symlink there (may have missed
some.) Add in missing services to "a few" boards, so they now also
regenerate their ssh keys at first boot as well.
You can use the gadget serial over USB/OTG on the 0w but since we don't
have a normal user, the device needs to be whitelisted in /etc/securetty
otherwise it will refuse the login.
Thanks to rmoriz for submitting the issue and pointing it out.
Also remove a couple make modules_prepare - it doesn't work properly
when cross compiling - you end up with amd64 binaries on the system and
external module building fails.
Issue #141 shows that bluetooth isn't working properly, so pull in
re4son's updated bluetooth package, and don't copy in our own versions
of it. Not closing the issue yet until it is tested.
The cross compiler for the rpi0w kernel compiles was still set to
arm-linux-gnueabihf- for some reason, and while the kernel does not have
a float, we should be using the correct one, so do so by making it
arm-linux-gnueabi-
Because of the firmwares using the same name, when there's a new release
of firmware-brcm80211, it overwrites the nexmon firmware which causes
nexmon to stop working (obviously.) So lets make sure to not install
it.
Debian removed dhcpcd so we can't rely on it being around to do the
right thing when we copy in a wpa_supplicant.conf file, so we need
network-manager to make networking easier on the 0w for people.
So, rpi-wiggle auto running is super awesome and great. But if you
resized the partition manually before putting it in.... rpi-wiggle would
resize the filesystem, but not correctly - it would attempt to downsize
it, or it would attempt to put the partition ending outside the bounds
of the device. Neither of those are ideal.
So for now, we comment it out, but if anyone wants to use it instead,
they can run it manually, OR they can use the kalipi-config which should
do the right thing regardless.
Since we resize the partitions on first boot, we can now reduce the size
of the image file to a much smaller 3GB of space. You can still force
it to a larger size by modifying the size variable, but there's no real
need to make it larger unless you're installing a lot of software. Keep
in mind that you need to account for both boot (~150MB) and the root
partitions when you do.
We also add re4son's new tft configurator to all the images, so once
installed, you can simply run kalipi-tft-config to set up an LCD on any
of the rpi images, as long as the script supports it.
This is an absolutely terrible way to install the kernel packages and
should never ever ever ever ever be done. But I'm doing it anyway,
because I can.
This reverts commit 5e89936845.
We can't use the kernel packages, because Debian's architecture for the
rpi/rpi0w is armel. It won't let you install them even though the
kernel package doesn't exactly matter (and we're using the rpi cross
compiler so it's technically an armhf package)
Since the icon theme was moved out of the dependencies, we move the
kali-defaults into the base install so we get all the settings files
installed even on images that don't include a desktop.
