After first boot
This chapter assumes the machine booted the kernel you installed, with GRUB, and reached a getty. If it did not, go back to the install chapter and check the kernel package, /etc/fstab, and grub-install.
Passwords
If you did not set hashes during setup, root and the first user are locked. From a live root you can chroot and run passwd. After a successful boot:
passwd passwd alex
Busybox passwd is on the live images. The installed shadow package provides it on the new system once base-system is in place.
Read the notes
setup writes text files under /root/:
sps-bootloader.txtif GRUB was not installed during setupsps-user.txtfor the first accountsps-init.txtfor the chosen PID 1sps-network.txt(setup does not write DHCP or static network config)sps-fstab.txtand/etc/fstabsps-services.txtwhen services were enabled
A manual install does not create those files unless you write them yourself. The same facts still apply.
Network
On a console install, bring an interface up by hand. dhcpcd is in base-system:
ip link dhcpcd eth0
On Plasma, use plasma-nm after graphical login. OpenSSH is present when you used the server profile or installed openssh.
Services
The file /etc/sps/init records which PID 1 was chosen. Known services (sshd, dbus, SDDM, NetworkManager, and others mapped by SPS) are enabled during setup unless you passed --services no. Later sget install of a mapped package enables it for that init too.
| Init | Enable a service |
|---|---|
| systemd | systemctl enable --now sshd (unit names follow the package) |
| OpenRC | rc-update add sshd default |
| s6 | symlink under /etc/s6/enabled |
| runit | symlink under /etc/runit/runsvdir/default |
| dinit | symlink under /etc/dinit.d/boot.d |
| Shepherd | Scheme files under /etc/shepherd.d |
| SysV | scripts in /etc/rc.d/init.d; enable with S* links in rc2.d through rc5.d |
Next packages
src update sget install nano pkstat
Search the package browser for names. Extra is where desktop, init, and most applications live. Core is the base system, toolchain pieces that exist as recipes, boot, filesystems, and networking. Community is a third tree. It is not on until you add git community to /etc/sps/repos.conf.
Configuration files
Files under etc are preserved when you change them. On upgrade, SPS keeps the local file. If the new package also changed its copy, the new one is written beside it as .sps-new. SPS does not merge the two.