2 ms·

I mean systemd-analyze blame usually shows only a few services taking up 90% of the boot time (looking at you snap daemon and cloud init taking a whole 20 secon

I mean systemd-analyze blame usually shows only a few services taking up 90% of the boot time (looking at you snap daemon and cloud init taking a whole 20 seconds lmao) so turning off those yields most of the gain without any real usability hit for general use. But in practical terms if you really need boot speed, you need a Pi 5 that only takes a few seconds at worst, not a Pi 4 which uses its slow ass GPU to run the boot process for absolute maximum sluggishness possible.

arghwhat 2y ago
s/boot process/initial boot phase/ A few seconds is still very long - in automotive you’re dealing with a few hundred milliseconds from power is applied till the system is presenting an interactive GUI.
- joezydeco 2y ago
  Automotive HMIs with Linux tend to boot long, then hibernate while the car is off. The only thing that needs to come up quickly (at least in the US) is the backup camera and there tends to be hardware to inject that video quicker than the HMI can.
notpushkin 2y ago
This just prompted me to finally look into boot time on my Asahi Linux setup. Turns out Docker was eating 5 seconds (about half of the boot time!) for some reason, so I disabled it (and enabled docker.socket instead, so that it starts up automatically when I need it).
- yjftsjthsd-h 2y ago
  Is there a way to start a service but not block on it? I want to start docker with the system, but nothing should wait on it
  - ta988 2y ago
    create a .timer file in your service directory with [Timer] OnBootSec=2min https://wiki.archlinux.org/title/Systemd/Timers https://wiki.archlinux.org/title/Systemd/Timers
    - notpushkin 2y ago
      I’ll give it a try too, thanks. Edit: set delay to one minure, working just fine!