From: Lee <ny6p01@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: Boot has no space left.
Date: Thu, 30 Jun 2022 13:29:39 -0700 [thread overview]
Message-ID: <CABpw4G87Q7xvM9wH+qTz1ZuDrVoQxvXtJNWNyT+AH=3LDoBd0w@mail.gmail.com> (raw)
In-Reply-To: <e769da87-2e73-0e18-7bf1-95818b840b69@youngman.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
The OP should read the section of the Gentoo manual on kernel install to
learn what files are installed where. Yea, but just rm the kernels and
initramfs's from /boot and you're golden. FWIW, I usually only upgrade my
kernel when it's a major revision.
On Thu, Jun 30, 2022 at 12:39 PM Wols Lists <antlists@youngman.org.uk>
wrote:
> On 30/06/2022 19:23, Michael wrote:
> > On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote:
> >> Hello,
> >>
> >> I still have the same problem, but the command worked fine.
> > The command "emerge -a --depclean" will only remove uninstall the kernel
> > packages, but will not remove files from/usr/src/, or old kernel images
> and
> > files from/boot/.
>
> As far as I'm aware, depclean only installs files it installed, so it
> leaves quite a lot of garbage lying around from kernels, including the
> /usr/src/kernel-xx-xx-xx directory and various files involved in making
> your kernel, that you've modified.
>
> Cheers,
> Wol
>
>
--
Lee 😎
<ny6p01@gmail.com>
[-- Attachment #2: Type: text/html, Size: 1631 bytes --]
next prev parent reply other threads:[~2022-06-30 20:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 16:19 [gentoo-user] Boot has no space left Guillermo García
2022-06-30 16:29 ` Dale
2022-06-30 16:47 ` Julien Roy
2022-06-30 17:11 ` Guillermo
2022-06-30 17:24 ` [gentoo-user] " Nikos Chantziaras
2022-06-30 18:15 ` Guillermo
2022-06-30 18:23 ` Michael
2022-06-30 19:38 ` Wols Lists
2022-06-30 20:29 ` Lee [this message]
2022-06-30 23:00 ` William Kenworthy
2022-06-30 23:21 ` Dale
2022-07-01 8:52 ` Wols Lists
2022-07-01 9:37 ` Dale
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='CABpw4G87Q7xvM9wH+qTz1ZuDrVoQxvXtJNWNyT+AH=3LDoBd0w@mail.gmail.com' \
--to=ny6p01@gmail.com \
--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