Comment out deb-src, most end users aren't going to be building packages.
Latest image file creation changes from frangal.
A few misc cleanups of white space
Because we resize the filesystem on first boot on the rpis,
we need to figure out a way to write the UUID into fstab before
adding the support there as well.
Unfortunately, it is simply too variable to tell how long it will take
to install, instead opt for the safer kali-tools-top10 for now, and
users can throw in kali-linux-default themselves if they like.
All images are now ~14GB so a 16GB sdcard minimum is required.
Update the list of packages installed.
Attempt to install kali-linux-default on first boot... not sure how this is going to go, because systemd doesn't like things taking a long time. May have to move it to a script, but we'll test it out.
Add 2 new scripts, one for the NanoPi NEO Plus2 and the rpi0w that are "minimal" - no desktop system installed (basically the original scripts pre- package list updates.
We're never going to care about anything that is on the system during
the first build, so just force new configs in case it ever prompts
which causes the build server to error out the build.
Baracko reported ( https://bugs.kali.org/view.php?id=5581 ) that vnc connections
would fail to work until reconfiguring xfonts-base.
This also fixes issue #164 which is a replica of the bug listed above.
Due to extras pulling in the modifications to the plymouth config file,
we were getting prompted whether to overwrite it or not. There is a
bug to fix plymouth but currently upstream needs help to work on it.
Work around it for now.
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.
This was supposed to be done for convenience, however, in practice, the
image ends up getting amd64 binaries in the kernel sources, so it
doesn't work anyway.
While we don't release an rpi2 specific build, there are still people
out there that build their own because they don't want to use Nexmon.
This updates the rpi2 script to keep up with the changes for the rpi3
while leaving out nexmon/rpi3 bluetooth bits.
Also update chmod because we don't need it.
Without adding machine names to the systemd-nspawn calls, if you attempt
to build 2 armhf images in parallel, it will fail claiming a machine of
the name kali-armhf already exists. This should fix that issue.
Using systemd-nspawn allows us to build the images in parallel without
worry of unmounting /dev screwing up and then the "cleanup" in the
script rm'ing /dev and leaving systems in a weird state requiring a
reboot.
However, since some people still use systems without systemd, we leave
the mount commands in the script (but commented out) so they can
uncomment and just :%s/systemd-nspawn/chroot/
