parabola-vmbootstrap/README
2018-02-01 12:20:31 +01:00

56 lines
2.1 KiB
Plaintext

parabola-arm-imagebuilder
=========================
this is a collection of scripts creating parabola arm images for use with qemu
with the original goal of building parabola arm packages on these machines.
Development focus has since shifted towards creating parabola-arm release
tarballs.
to create a new virtual machine, run
$> sudo ./create.sh
optionally, to create a new virtual machine with a packaging environment, run:
$> DEVSETUP=1 sudo ./create.sh
the packaging environment setup script makes use of several files and packages
present on already setup parabola development machines. if your setup is
different, you might have to modify src/stage3.sh accordingly.
Places the scripts check the host machine for configuration files are:
/etc/makepkg.conf - for PACKAGER and GPGKEY
~/.gnupg ~/.ssh ~/.gitconfig - copied verbatim to the VM
The scripts assume that the following programs are available and in $PATH:
qemu-img, qemu-system-arm
wget
parted
mkfs.vfat, mkfs.ext4, mkswap
bsdtar
scp, ssh, ssh-keygen
pacman
The scripts also assume that you like vim :)
to open a shell into the created machine, run
$> ./start.sh [path to created image]
the start.sh script assumes that you want a throwaway session, so it will start
the virtual machine in snapshot mode and drop you into an ssh session. Once you
exit that session, the machine is shutdown and changes made to the image are
discarded. This behavior can be changed using the following environment
variables:
FOREGROUND : set this to 1 to start a qemu serial connection instead of a ssh
session. Useful to capture boot output.
PERSISTENT : set this to 1 to make persistent changes to the image that are
not discarded on shutdown.
The username and password for the created image is parabola:parabola, or
root:parabola respectively. If a packaging environment is setup, the system is
configured for passwordless sudo for the parabola user and the package tree and
a build chroot are prepared. have fun. also check out the .bashrc of the
parabola user in the created virtual machine, for batch build integration based
on task-spooler.