From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2F54F158011 for ; Thu, 14 Jul 2022 23:32:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 47CF7E104C; Thu, 14 Jul 2022 23:32:13 +0000 (UTC) Received: from mail.tzend.de (mail.tzend.de [IPv6:2a03:4000:27:4d1::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D4FA8E0FB7 for ; Thu, 14 Jul 2022 23:32:11 +0000 (UTC) Received: from ventiloplattform.tastytea.de (p200300c087225d0067d36ae3272627e3.dip0.t-ipconnect.de [IPv6:2003:c0:8722:5d00:67d3:6ae3:2726:27e3]) by mail.tzend.de (Postfix) with ESMTPSA id E01739A0070 for ; Fri, 15 Jul 2022 01:32:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tastytea.de; s=mail; t=1657841529; bh=eXzglquce+6tHdIZTG71iK8KAHDroWho7N/SayZeYGs=; h=Date:From:To:Subject:In-Reply-To:References; b=BZ++NKgEJ27YQ4egDB5dPrTeHGTAOJZ9Tn7TI1Ispin6QZhGX79oEPPxsyHk0cagu Ltd83fxgCBBXq8GBApDNVH6w5RyB/N9pmSzgMpYT13881nbeS6189yVOzDXCc821a8 s1LfkMhFX6HjxUsVKbsj95gG1EeNdn2ZW16QPEtg= Date: Fri, 15 Jul 2022 01:32:07 +0200 From: tastytea To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Boot has no space left. Message-ID: <20220715013207.2baa48b8@ventiloplattform.tastytea.de> In-Reply-To: <9f8eca31-f7b8-e6ed-2246-aef4abf3e391@youngman.org.uk> References: <1e0c9ca4-63e7-f906-3d7f-aa6800597219@gmail.com> <9f8eca31-f7b8-e6ed-2246-aef4abf3e391@youngman.org.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 72bbec0e-ed6f-46f7-bf5b-83b6fcb53bf4 X-Archives-Hash: 9ae5d5891b1386497b6ef89dadb55520 On 2022-07-15 00:21+0100 Wol wrote: > On 15/07/2022 00:01, Dale wrote: > > Guillermo Garc=C3=ADa wrote: =20 > >> > >> Hello again guys, how are you? I hope you're fine. > >> > >> I remember someone told me a program to use to remove old kernels > >> in order to get more space on /boot, i tried to search the > >> original message that the guy sent me trough this list, but i > >> cannot find it. > >> > >> Here's a screenshot of my /boot folder: > >> > >> I guess the kernel version i use is this one: > >> > >> Could someone tell me a method to remove the old kernels in order > >> to get more space in /boot? > >> > >> Thank you, and regards, > >> > >> Guillermo. > >> =20 > >=20 > >=20 > > I found it for you.=C2=A0 The package is app-admin/eclean-kernel.=C2=A0= I > > think there is a wiki page on the Gentoo website for that.=C2=A0 I > > recall it being pretty easy to use. > > =20 > Bear in mind, if the OP is running 5.15.10, that's the second oldest=20 > kernel in the list. If he's got five newer kernels there, is=20 > eclean-kernel going to assume the live kernel is out-of-date and > delete it? NOT a good idea. >=20 > The OP needs to make sure that both 5.15.41 and 5.15.48 are in his > boot menu, AND that they both work, before risking clearing out the > rest ... The current kernel is never removed by eclean-kernel. > The kernel choice algorithm is quite simple: >=20 > 1. If the kernel is currently used, don't remove it; > 2. If the kernel is referenced by a bootloader, don't remove it > (unless ``--destructive``); > 3. If auxiliary files do not map to existing kernel, remove them; > 4. If ``--all`` is used, remove the kernel; > 5. If kernel is not within *N* newest kernels (where *N* is the > argument to ``-n``), remove it. Since the grub boot menu includes all kernels in /boot by default as far as i know, it is probably necessary to run eclean-kernel with --destructive and re-generate the boot menu afterwards. Kind regards, tastytea