Not with systemd it isn't, it disappered with the (uneventful) demise of sysvinit. Systemd got rid of all that runlevel junk in favour of "targets". There's no popular DebIan or Redhat based distro that still runs with sysvinit.
That's not my experience. My headless raspberries take less than 20 seconds from power on to usable. The thing that slows things down is the GUI. Adding a new service with sysvinit is a pain. Adding that with systemd is trivial.hortimech wrote: ↑Fri Dec 21, 2018 5:51 pmIt doesn't improve the boot process, it takes longer to boot!
systemd is like the curates egg, good in parts, pity the good bits are so small
Hey! That's actually a good idea. I'll have to test this at some point. Thanks!joan wrote: ↑Sat Dec 22, 2018 12:16 pmAt boot (power-up) the GPIO are set to a particular state with their pulls. The pulls are not affected by a reboot. Choose a GPIO and change the pull to the opposite of the power-up setting. You can then determine the pull in software and thus distinguish between boot and reboot.
Code: Select all
#!/bin/bash pull=$(pigs r 27) # read GPIO 27, it defaults to pull-down on power-up. pigs pud 27 u # set pull-up on GPIO 27. if ((pull == 0)) then echo "system was booted" else echo "system was rebooted" fi