Old Kernels Not Removed

Started by RunLevelZero, 2024/11/16, 01:12:47

Previous topic - Next topic

RunLevelZero

[language=english]Hello all. For some reason after autoclean and autoremove my old kernels are still there. Would someone help me out with the commands to clean this up please? It's the first time I've had this issue. Thanks in advance.[/language]

dibl

System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

RunLevelZero

Quote from: dibl on 2024/11/16, 02:16:36
# kernel-remover

Thank you. I'll do this in the morning. Appreciate the quick response.

dibl

# apt autoremove is configured in siduction to remove the oldest kernel, but leave the next oldest, so you have two kernels available after running the command.

Take a look at /etc/apt/apt.conf.d/01autoremove. You should see this:

APT
{
  NeverAutoRemove
  {
        "^firmware-linux.*";
        "^linux-firmware$";
        "^linux-image-[a-z0-9]*$";
        "^linux-image-[a-z0-9]*-[a-z0-9]*$";
  };

  VersionedKernelPackages
  {
        # kernels
        "linux-.*";
        "kfreebsd-.*";
        "gnumach-.*";
        # (out-of-tree) modules
        ".*-modules";
        ".*-kernel";
  };

  Never-MarkAuto-Sections
  {
        "metapackages";
        "tasks";
  };

  Move-Autobit-Sections
  {
        "oldlibs";
  };
};

System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

RunLevelZero

Quote from: dibl on 2024/11/16, 13:43:27
# apt autoremove is configured in siduction to remove the oldest kernel, but leave the next oldest, so you have two kernels available after running the command.

Take a look at /etc/apt/apt.conf.d/01autoremove. You should see this:

APT
{
  NeverAutoRemove
  {
        "^firmware-linux.*";
        "^linux-firmware$";
        "^linux-image-[a-z0-9]*$";
        "^linux-image-[a-z0-9]*-[a-z0-9]*$";
  };

  VersionedKernelPackages
  {
        # kernels
        "linux-.*";
        "kfreebsd-.*";
        "gnumach-.*";
        # (out-of-tree) modules
        ".*-modules";
        ".*-kernel";
  };

  Never-MarkAuto-Sections
  {
        "metapackages";
        "tasks";
  };

  Move-Autobit-Sections
  {
        "oldlibs";
  };
};


[language=english]Indeed I do see this. I will wait for your feedback before running any removal commands. I have never had this problem in the years I've used Siduction.[/language]

APT
{
  NeverAutoRemove
  {
"^firmware-linux.*";
"^linux-firmware$";
"^linux-image-[a-z0-9]*$";
"^linux-image-[a-z0-9]*-[a-z0-9]*$";
  };

  VersionedKernelPackages
  {
# kernels
"linux-.*";
"kfreebsd-.*";
"gnumach-.*";
# (out-of-tree) modules
".*-modules";
".*-kernel";
  };

  Never-MarkAuto-Sections
  {
"metapackages";
"tasks";
  };

  Move-Autobit-Sections
  {
"oldlibs";
  };
};

hendrikL


helux

Quote from: dibl on 2024/11/16, 13:43:27
... is configured in siduction to remove the oldest kernel, but leave the next oldest, so you have two kernels available after running the command...

Diese Info könnte vielleicht auch ins Handbuch.  8)

RunLevelZero

[language=english]Thanks but I do not get an error at all.[/language]
Quote from: hendrikL on 2024/11/16, 17:15:01
Do you have the same error like in this thread?
https://forum.siduction.org/index.php?topic=9509.0

RunLevelZero

[language=english]This worked perfectly thank you very much. Hopefully autoclean will now work like it has for the last 6 years for me. As always I appreciate the help and assistance.[/language]
Quote from: dibl on 2024/11/16, 02:16:36
# kernel-remover