![]() i've done this before a ton of times with no issues but then i had issues with my hard drive so i had to reinstall windows which kali is running in virtualbox so i had to reinstall that as well and every since i reinstalled it, i've had issues. What I'm doing wrong? How to add kernel modules to the ISO to achieve the proper installation process?įor some reason, when i run lb config, it doesn't generate a file, everything else that i know of gets generated. It gets stuck during the load after the pcnet32 0000:02:01.0 eth0: link up The ISO also can't be run in the live mode. This is probably due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive.Ĭontinue the install without loading kernel modules? When I start the installation from this ISO I'm getting the message: The ISO is compiling OK but is not working properly. # | NOTE: The mate desktop requires other changes to the live config. # or you can just comment everything except the package of your ![]() # kali meta-package depends on everything we want So I've made my own Custom ISO with this '' file: Also I don't need the graphics environment. I have a computer with only 4 GBytes HDD and I need only the tools for Wi-Fi. Lb config -architecture amd64 or -architecture i386 (32bit) Save the file and then open up terminal and add this : # or you can just comment everything except the packages of yourĪnd add instead replace it with this if you wnt kde ![]() # packages required to install your preferred graphical desktop # You can replace all the remaining lines with a list of the # Graphical desktops depending on the architecture Go under /root/live-build-config/config/package-lists/ and open up with your text editor (gedit,leafpad.)and Both are running Ubuntu 13.04 (1 server / 1 desktop)Īgain using the default everything directly after cloning from git. on all my ubuntu machines that i've tried to do a live build I get 2 errors from lb config. This is my output when running lb build. ![]() I am getting the same error message with the default chroot file.
0 Comments
Leave a Reply. |