Hey guys! So this is subject to change, and I expect we'll update it frequently.
Firstly, visit the onboarding repo and follow the instructions.
You'll eventually end up with a moss binary and I'm giving @ermo permission to ghost-edit my instructions later 🙂
Assuming you've now got moss:
user@host:~/repos/onboarding
$ onboarding/create-sosroot.sh
Honestly, this is a super minimal root - with fat packages. Right now upgrade paths are not supported until announced otherwise.
Expect everything to be super rough
Boot it:
sudo systemd-nspawn --bind=/var/cache/boulder/ -D /var/lib/machines/sosroot/ -b
You'll be prompted to hit a button, enter locales and root password before you can log in:
Welcome to your new installation of Serpent OS borkytests (fstx #1)!
Please configure your system!
-- Press any key to proceed --[ OK ] Finished Flush Journal to Persistent Storage.
[ OK ] Finished Rebuild Hardware Database.
‣ Please enter system locale name or number (empty to skip, "list" to list options): 3
Selected 'en_GB.UTF-8'.
‣ Please enter system message locale name or number (empty to skip, "list" to list options): 3
Selected 'en_GB.UTF-8'.
/etc/locale.conf written.
🔐 ‣ Please enter a new root password (empty to skip): ***************
🔐 ‣ Please enter new root password again: ***************
/etc/passwd written
/etc/shadow written.
[ OK ] Finished First Boot Wizard.
Using chsh to change shell to /usr/bin/bash should look roughly like this:
sosroot login: root
Password:
# chsh
Changing shell for root.
New shell [/bin/sh]: /usr/bin/bash
Shell changed.
# exit
sosroot login: root
Password:
Last login: Sun Feb 19 16:47:42 on pts/0
root@sosroot # ~
Some quick commands:
# moss remote list
# moss remote update
# moss search -m all "fetch"
# moss install neofetch
# neofetch
Good luck!
Known issues:
Impossible to login into the nspawn container
login: PAM failure, aborting: Critical error - immediate abort
Both with passwordless root and with password.
Fixed setup instructions. Running moss remote add and moss install with sudo when setting up the nspawn container will produce the error above.
