After plugging in both USB’s and booting the desktop, I am greeted by choice menu to boot or install microOS.
This is a brand new SSD, so there is nothing to boot, my expectation is that MicroOS is automatically installed, which did not happen. Why?
Secondly, my script installs a few packages, (incl. new shell, fish), creates a user and copies over conf files.
Since installing packages with with transactional-update requires reboot to activate changes, how would I go about setting default shell for user during Combustion initalization?
My combustion script:
# combustion: network
# Set a password for root, generate the hash with "openssl passwd -6"
echo 'root:hidden' | chpasswd -e
# Install packages
transactional-update --non-interactive pkg install --no-recommends vim-small tmux fish exa btop
# Add a public ssh key and enable sshd
useradd -m -s /usr/bin/fish support
mkdir -pm700 /home/support/.ssh
cat id_ed25519.pub >> /home/support/.ssh/authorized_keys
systemctl enable sshd.service
# Change shell
chsh -s /usr/bin/fish
# Config files
cp .tmux.conf /root
cp .tmux.conf /home/support
cp .vimrc /root
cp .vimrc /home/support
cp config.fish /root/.config/fish
cp config.fish /home/support/.config/fish
# Leave a marker
echo "Configured with combustion" > /etc/issue.d/combustion
This would require removing the SSD though.
I guess one could boot with systemrescue-9.00-amd64, then dd *.raw.xz to SSD, however this requires as much work as going through the MicroOS installer manually.
Perhaps look at the pxe route? Did a quick test here via USB device that I zcated the image onto, the setup another USB with ignition files all worked except network as didn’t have the correct interface name… I need to use predictable naming…
Fixed that, didn’t take that long, less than 10 minutes for prep and boot to a running system. Ran, installed, then auto reboot and ready to go.