Skip to content

First boot

The system is installed and the machine has rebooted. This page is what to check before you consider the installation finished.

You reach a login prompt

If you do, the boot tree came up. Log in as the unprivileged user you created.

If you do not, jump to when the boot fails below.

Check the services

$ 66 -z tree status

This lists every tree, whether it is enabled, and what it contains. The boot tree holds the services that brought the machine up.

For a single service:

$ 66 status <service>

See Everyday commands for what to do with them.

Read the boot log

Everything printed during boot went to the catch-all logger, not to the screen:

$ 66 log system

Add -f to follow it live. If you would rather see boot messages on the console as they happen, see Boot output.

Update

# pacman -Syu

Announcements, including the upgrades that need manual intervention, are published on news.obarun.org, which offers an RSS feed. Subscribing to it is the cheapest way to avoid being surprised.

Things worth setting up now

  • A second console. By default tty@tty12 is your emergency console and root cannot log in on it. Read Consoles and tty12 before you need it.
  • The boot module. Hostname, timezone, keymap, console font, fstab handling, LVM and the rest all live in one configuration. See The boot module.
  • The shell. Obarun defaults to zsh with a configuration of its own. See Shell.
  • Your own services. Networking, a display manager, printing. See Services (66).

When the boot fails

Try, in order:

  1. Switch to tty12 with Ctrl+Alt+F12 and log in as your unprivileged user. It is enabled early precisely so that it survives a partly failed boot.
  2. Read the log with 66 log system, or 66 -z tree status to see which tree did not come up.
  3. Boot the live medium and arch-chroot into the installation to repair it.

Do not delete files under the 66 directories

When a tree or a service misbehaves, the fix is never to remove files by hand from the live or state directories. Disable the service, or remove and recreate the tree, with the 66 commands. Deleting files leaves an inconsistent state that is much harder to diagnose than the original problem.