Hello, iam in the making of artix install script. I start with setting variables in dialog like bootloader=“refind” and etc. but when i do artix-chroot into chroot.sh script variables are gone.
right now i have something like this:
cp ${pwd}execution/chroot.sh /mnt/mnt &&
USER="$USER" USER_PASSWORD1="$USER_PASSWORD1" USER_PASSWORD2="$USER_PASSWORD2"\
ROOT_PASSWORD1="$ROOT_PASSWORD1" ROOT_PASSWORD2="$ROOT_PASSWORD2"\
BOOTLOADER="$BOOTLOADER" SUPERUSER="$SUPERUSER" HOSTNAME="$HOSTNAME"\
LOCALE="$LOCALE" ENCRYPTION="$ENCRYPTION" ROOT="$ROOT" ESP="$ESP"\
KERNEL="$KERNEL" UCODE="$UCODE"
artix-chroot /mnt bash -c '/mnt/chroot.sh && execute_root'
But it does not really work, tried also some things like:
# create array of variables to pass to part 2
var_export=($formfactor $threadsminusone $gpu $boot $disk0 $username $userpassword $timezone $swap $intel_vaapi_driver $res_x $res_y_half)
# initiate part 2
mount --bind /root/artix-install-script /mnt/mnt
artix-chroot /mnt /mnt/chrootInstall.sh "${var_export[@]}"
and then in chroot.sh
# Importing Variables
args=("$@")
formfactor=${args[0]}
threadsminusone=${args[1]}
gpu=${args[2]}
boot=${args[3]}
disk=${args[4]}
username=${args[5]}
userpassword=${args[6]}
timezone=${args[7]}
swap=${args[8]}
intel_vaapi_driver=${args[9]}
res_x=${args[10]}
res_y_half=${args[11]}
still not they best way, kinda messy and buggy.
THANKS FOR HELP!
Careful there. You are only a half dozen abstraction layers away from reinventing NixOS.
As for your question, the best way is to put it in a file that is then read by the chroot script and delete later.
Preferably, put the variables into a temp file (e.g. using
mktemp
) and bind-mount that file somewhere into the chroot directory, so you can source it from within that environment.That way the critical information, like the passwords, at least only gets to live in volatile memory and won’t stick around on the host system after the reboot. That limits the exposure somewhat.