From: Wol <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Boot has no space left.
Date: Fri, 15 Jul 2022 00:16:48 +0100 [thread overview]
Message-ID: <5cdf1260-e872-6303-d8f2-c96b9617687e@youngman.org.uk> (raw)
In-Reply-To: <1e0c9ca4-63e7-f906-3d7f-aa6800597219@gmail.com>
On 14/07/2022 23:51, Guillermo García wrote:
> 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?
>
What kernels are in your grub.cfg / boot menu. If they're not in there,
just delete them from /boot.
It's normal to have your latest kernel in the boot menu, and one backup
kernel.
So, for every kernel NOT in your boot list, cd into /boot and, as root,
do "rm -i *x.y.z*" where x.y.z is the kernel version you want to get rid
of. It'll query what files it's going to delete, but so long as it looks
sensible, say "y" and get rid of it.
It looks like you've got seven kernels there, so five sevenths space
freed up is quite a lot ...
Cheers,
Wol
next prev parent reply other threads:[~2022-07-14 23:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 22:51 [gentoo-user] Boot has no space left Guillermo García
2022-07-14 23:01 ` Dale
2022-07-14 23:21 ` Wol
2022-07-14 23:32 ` tastytea
2022-07-14 23:44 ` Dale
2022-07-14 23:16 ` Wol [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-30 16:19 Guillermo García
2022-06-30 16:29 ` Dale
2022-06-30 16:47 ` Julien Roy
2022-06-30 17:11 ` Guillermo
2022-06-27 8:35 Guillermo García
2022-06-27 10:03 ` Dale
2022-06-27 10:20 ` Michael
2022-06-27 10:26 ` tastytea
2022-06-27 17:14 ` wkuz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5cdf1260-e872-6303-d8f2-c96b9617687e@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox