8
Old kernels not deleted; full /boot partition (lemmy.world)
submitted 1 month ago by to c/debian@lemmy.ml
5 comments fedilink hide all child comments
 

I installed debian for a friend who is not techy. They've been accepting the updates as and when offered. Now their /boot is full. I'm assuming they need to run

apt autoremove --purge

Or similar. But is there a way you automate this? Otherwise debian with a boot partition seems to have a self destruct timer!

Advice appreciated!

all 5 comments

sorted by: hot top controversial new old
[–] 3 points 1 month ago

apt full-upgrade takes care of this

  • permalink
  • fedilink
  • source
    •
    [–] 3 points 1 month ago

    This is one of the reasons why I don't use a separate partition for /boot anymore. As I understand it, a separate /boot partition is mostly a legacy thing unless you have an encrypted root partition or some other special setup. For simple cases I recommend having /boot on the root partition to avoid issues like this.

    I think that's also the default setup used by the Debian installer if you select Guided partitioning – use entire disk. I'm not 100% sure tho.

  • permalink
  • fedilink
  • source
    •
    [–] 2 points 1 month ago (2 children)

    Would rec moving them to something more simple, akin to ElementaryOS.

    That said, /boot likely isn’t right sized for the number of versions of the kernel required by the bootloader in case of a failure. 512mb-1gb of storage is normally more than enough to handle said copies. As well, apt dist-upgrade will actually remove obsolete packages while apt upgrade does not.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •