Apparently the reason my computer has been taking 2 minutes to boot was a faulty network mount

  • passepartout@feddit.de
    1·
    2 years ago

    You can use systemd-analyze blame if you want raw numbers:

    This command prints a list of all running units, ordered by the time they took to initialize. This information may be used to optimize boot-up times.

    Good way to see if your systemd also waits 2 minutes for a network connection which already exists but it can’t see it because systemd doesn’t do the networking (lxc containers on proxmox in my case) lol.

    Also see systemd-analyze.

  • jsdz@lemmy.ml
    1·
    2 years ago

    I’m pretty sure the main system startup bottleneck is me typing the disk encryption passphrase.

    • magikmw@lemm.ee
      1·
      2 years ago

      I wish to replace it with a yubikey, but I don’t even know if it’s supported.

      • Ullebe1@lemmy.ml
        1·
        2 years ago

        It is supported by systemd to use FIDO2 + pin to decrypt luks partitions with many security keys, including Yubikeys. I use it every day on my laptop.