-
-
Notifications
You must be signed in to change notification settings - Fork 498
Booting process
MichaIng edited this page Mar 6, 2020
·
7 revisions
On the first boot of a fresh DietPi install. The systemd services are launched in the following order: 0. DietPi-FS_partition_resize: Inflate root partition and file system to 100% of available disk space
- DietPi-RAMlog: Mount tmpfs on /var/log and copy empty log files from disk
-
- DietPi-PreBoot: Detect SBC model and apply CPU governor settings
- DietPi-FirstBoot: Apply AUTO_INSTALL settings from dietpi.txt
- DietPi-Boot: Wait for network and run network time sync
- DietPi-PostBoot: Print login banner
Then, when you login /etc/bashrc.d/dietpi.bash
is executed and loads /boot/dietpi/dietpi-login
0. Load DietPi-Globals to shell session
- Print DietPi-Banner and lincense agreement prompt
- DietPi-Update
- DietPI-Software: Further firstrun setup prompts and steps are applied
The following services are launched in this order:
- DietPi-RAMlog: Mount tmpfs on /var/log and copy empty log files from disk
- DietPi-PreBoot: Detect SBC model and apply CPU governor settings
- DietPi-Boot: Wait for network and run network time sync
- DietPi-PostBoot: Check for DietPi updates, start software services, run custom user scripts and print login banner
Then, when you login /etc/bashrc.d/dietpi.bash
is executed and loads /boot/dietpi/dietpi-login
0. Load DietPi-Globals to shell session
- Print DietPi-Banner and in case start DietPi-Autostart choices
Project management
Extend
- DietPi-Software list
- DietPi TCP/UDP port usage list
- How to add a new software title
- How to create a DietPi image for Raspberry Pi
- How to create a DietPi image for VirtualBox
- How to create a DietPi image for VMware
- How to create a DietPi image for Parallels (macOS)
- How to create a DietPi image for x86_64 PCs (BIOS)
- How to create a DietPi image for x86_64 PCs (UEFI)
Knowledge Base