Those are never copied into live-build's config directory and actually
the "packages" file is clashing with a "packages" directory which results
in a failure of the "rm -f" call.
The netinst installer is causing too many issues for unexperienced
users that are installing without enabling the network. They are ending
up in a console and are stuck there. See https://bugs.kali.org/view.php?id=6053
and the many duplicates.
The live installer is not offering close control on what metapackage
gets installed but at least you are sure to have a usable system at the
end.
In the live-build code, netinst and netboot have the same meaning,
and it means netboot, an installer that fetches the d-i udebs over
the network. But we don't want that, we want the udeb to be available
in the ISO so that it keeps working even after a kernel update in
kali-rolling.
So that the generated /etc/network/interfaces contains "eth0" and
not any name assigned by systemd/udev since this renaming is already
disabled in the installed system.
Fixes https://bugs.kali.org/view.php?id=4090
Up to now, --proposed-updates always enabled kali-proposed-updates
when in fact it should have enabled the proposed-updates repository
of the target distribution.
* Add new --variant option to build alternative images of Kali.
* Add new --version option to decide of the name of the generated file.
* Add new --subdir option to indicate where the image must be moved.
This reverts commit 9eeb33247b.
live-build puts the preseed file in the initrd so it actually replaces
the preseed file put in place by debian-installer. That preseed
actually hardcodes the release for the need of the mini.iso but
the live image does not need such an hardcode as d-i can figure
it out by itself by analyzing the repositories on the ISO.
We want to override the apt configuration from the preseed in the
initrd because it harcodes the kali repository and we want
kali-rolling ISO to use the kali-rolling repository too!
We do it in a way that still allows the user to put his own
preseed file.
If we don't drop them, they are kept forever and never updated
as wanted. This was problematic for live.list.chroot which
doesn't have the same content depending on the --initsystem option
we use.
The usage of the pipe did hide errors from us when we were using
--verbose. We use a bashism to detect failures in pipes so update
the shebang accordingly.
Ben Wilson
Raphaël Hertzog
Steev Klimaszewski
cblack
Raphaël Hertzog
Raphaël Hertzog
Sophie Brun
Mati Aharoni (Kali Linux Developer)