justan0th3rstud3nt
/
kali-live-build
mirror of
1
0
Fork 0
Code Issues 1 Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
504 Commits
2 Branches
42 Tags
12 MiB
Shell 100%
 
main
debian-cd
2025.1
2024.3
2024.2
2024.1
2023.4
2023.3
2023.2
2023.1
2022.4
2022.3
2022.2
2022.1
2021.4
2021.3
2021.2
2021.1
2020.4
2020.3
2020.2
2020.1
2019.4
2019.3
2019.2
2019.1
2018.4
2018.3
2018.2
2018.1
2017.2
2017.1
2016.2
2016.1
2.0
1.1.0
1.0.9
1.0.8
1.0.7
1.0.5
1.0.4
1.0.3
1.0.2
1.0.0
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '796bb62679'
${ noResults }
Go to file
Arnaud Rebillout 796bb62679
Configure default terminal according to the kali desktop package installed 
This is necessary in case more than one terminal is installed, and they
both have the same alternative priority.

For example, while installing all packages at once, sometimes apt will
resolve a dependency "x-terminal-emulator" to one of the many packages
that provide it, for example "zutty". And then it will also install the
terminal listed in the "kali-desktop-${desktop}" metapackage that is
selected, eg. "qterminal" for "kali-desktop-xfce".

Both zutty and qterminal have a alternative priority of 40 at the
moment, so if zutty gets unpacked first, it will have precendence and be
the default terminal.

It's a long-standing issue. By the past, We tried to make sure that the
default desktop terminal is installed first, by listing it early in the
dependencies of the "kali-desktop-{desktop}" metapackage, and it kind of
works with the debian-installer, but it was hard to make it work (we had
to do some changes in tasksel), and it's still brittle as it relies on
apt's dependency solving, which is apt's internal sauce and might change
(hint, apt will get a new solver soon, cf [1]).

As it turns out, it doesn't work for the live iso, somehow we still get
zutty taking precedence over qterminal, I didn't check why, it probably
has to do with how live-build constructs the apt command-line in order
to install everything.

In any case: I think our approach so far didn't work, so with this
commit, we take another approach: we set the default terminal from the
finish-install script, for both the installer iso and the live iso. That
should solve the issue for good.

[1]: https://blog.jak-linux.org/2024/05/14/solver3/
 		8 months ago
auto Enable non-free-firmware by default everywhere 2 years ago
kali-config Configure default terminal according to the kali desktop package installed 8 months ago
simple-cdd Add eatmydata to offline.downloads 10 months ago
.getopt.sh Add --help 4 years ago
.gitignore Update .gitignore because wget-log was not included 1 year ago
README.md Fix dead links 4 years ago
build.sh Add a function require_package to factorize code 9 months ago
build_all.sh Rename script into ./build.sh 10 years ago

README.md

live-build configuration for Kali ISO images

Have a look at Live Build a Custom Kali ISO for explanations on how to use this repository.