| Description | Dear maintainers,
with the change from openvas to gvm it was time for me, to build a new livefilesystem for me. As usual I am building for amd64 and i386.
But this time, I can not complete the build, as I fell into an issue: The package lilo is no more in the repo, but required.
Could you update your preferences in git, if possible?
Second thing (there is already a bugreport existent), could you check, if the default user and password are still kali / kali in the git? At last build neither kali / kali worked, nor the default password for root in the livesystem. |
|---|
| Steps To Reproduce |
- Updated my git clone using "git pull origin master"
- Executed command the following script:
#!/bin/sh
License: GPL
Set some variables, not active yet.
architecture: i386, amd64, arm
ARCH=amd64
Distribution, you might not want to change it.
DISTRO=kali-rolling
Your preferred window-manager: lxde, kde, xfce, gnome
VARIANT=lxde
Environmet for your local proxy
PROXY=http://localhost:3142/
language, keyboard, locales everything you might not need to change
BOOTAPP="boot=live noconfig=sudo username=root hostname=kali ignore_uuid locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys"
Clean your system, not really necessarey, as the latter "./build.sh" does
this either.
lb clean
VERY IMPORTANT: Make sure, apt-cacher is started, even, if you are sure,
it is already running!
/etc/init.d/apt-cacher-ng stop && sleep 3 && /etc/init.d/apt-cacher-ng start
set your needed environment and preparations.
export http_proxy=http://localhost:3142/
lb config
This command starts the actual build. All commands are in one line.
However, this script might be improved, to use variables for better
configuration possibilities.
./build.sh --arch $ARCH --distribution $DISTRO --variant $VARIANT --verbose -- --apt-http-proxy $PROXY --bootappend-live "$BOOTAPP"
these options can be used for further commands after build
for example, if you want to burn a dvd, shutdown, whatever
Examples for my personal needs below
#/etc/init.d/apt-cacher-ng stop
Suggestions for handling the built image.
cp /home/username/live-build-config/images/*.iso /home/user/
wodim /path_to_your_live_build/live-build-config/images/your_image_name.iso
Some opportunities at unattended build run, what to do after the build succeeded.
halt -p
reboot
shutdown -h now
See attached build.log please.
This issue appeared in amd64 and i386 as well.
Thank you for any hints. |
|---|
