During the VSIDO installation process, at the very end, chroot takes over and installs grub and systemd-sysv and updates apt. All of this works perfectly and I love the process. It looks like this
#!/bin/bash
chroot /TARGET grub-install --force --no-floppy "$GRUBLOC"
chroot /TARGET update-grub
chroot /TARGET apt-get update > /dev/null 2>&1
chroot /TARGET apt-get -y install systemd-sysv > /dev/null 2>&1
chroot /TARGET cp -fv /etc/skel/.fluxbox/menu1 /home/$TARGETUSER*/.fluxbox/menu
chroot /TARGET cp -fv /etc/skel/.fluxbox/startup1 /home/$TARGETUSER*/.fluxbox/startup
exit 0
Notice the last two lines that consist of the cp command to make changes to the users home directory. These lines fail in the script. However if I
sudo su
chroot /TARGET
cp -fv /etc/skel/.fluxbox/menu1 /home/$TARGETUSER*/.fluxbox/menu
chroot /TARGET cp -fv /etc/skel/.fluxbox/startup1 /home/$TARGETUSER*/.fluxbox/startup
These commands work perfectly. This is a puzzle that has me perplexed... I am sure it is a syntax issue but there is nothing logging that indicates failure
@aibo and anyone who wants to reproduce this... Right after an install while still on the LiveCD, you can chroot all you want to the /TARGET build directory
You would have to add the above lines of code to /usr/bin/remastersys-install to effectively duplicate the failure
I set up an install in a Virtual Box and then make the changes and try installations over and over... Nothing I have tried has successfully ran from the script but has run perfectly from a terminal chroot into /TARGET