From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] old kernels are installed during the upgrade
Date: Thu, 4 Jan 2018 00:09:08 +0200 [thread overview]
Message-ID: <c738cc65-081e-dfb6-70e7-56d43516b000@gmail.com> (raw)
In-Reply-To: <C8CD0361-4555-4619-84EA-4204C2033C80@stellar.eclipse.co.uk>
On 04/01/2018 00:02, Stroller wrote:
>
>> On 3 Jan 2018, at 21:55, Wols Lists <antlists@youngman.org.uk> wrote:
>>
>> What would be nice, would be if "emerge --depclean" had the smarts to
>> recognise that /usr/src/linux pointed to the current active kernel, and
>> didn't wipe that when it cleaned out everything else :-) That way, at
>> most you could have the current and latest kernel sources available
>> pretty easily.
>
> You've jogged a long-hibernating memory - the accidental removal of the current sources tree in an accident like this may be the exact reason why I refuse to allow kernel versions to be actively emerged.
I think that's a mountain and a molehill. You still have the image in
/boot, config in /boot or in the running kernel, libs in /lib/modules
and the bootloader is intact.
Delete the sources?
- Re-emerge them. 90 seconds.
- Re-compile using existing config. 20 minutes
So deleting the sources for the running kernel is a doh! moment. But no
biggie, and certainly not cause for changing your routine (all in my own
not at all humble opinion, of course)
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2018-01-03 22:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 11:54 [gentoo-user] old kernels are installed during the upgrade Kruglov Sergey
2018-01-02 12:03 ` Alexander Kapshuk
2018-01-02 12:42 ` Mick
2018-01-02 15:59 ` [gentoo-user] " Nikos Chantziaras
2018-01-02 19:26 ` [gentoo-user] " Stroller
2018-01-02 19:47 ` Wols Lists
2018-01-03 21:39 ` Stroller
2018-01-03 21:55 ` Wols Lists
2018-01-03 22:02 ` Stroller
2018-01-03 22:09 ` Alan McKinnon [this message]
2018-01-04 6:40 ` Wols Lists
2018-01-04 8:48 ` Alan McKinnon
2018-01-03 23:43 ` Neil Bothwick
2018-01-02 20:20 ` [gentoo-user] " Kai Krakow
2018-01-02 20:28 ` Rich Freeman
2018-01-02 22:58 ` Adam Carter
2018-01-03 20:35 ` Wols Lists
2018-01-03 20:53 ` Rich Freeman
2018-01-03 21:50 ` Neil Bothwick
2018-01-04 16:02 ` Holger Hoffstätte
2018-01-04 16:10 ` Rich Freeman
2018-01-05 2:12 ` Walter Dnes
2018-01-05 2:25 ` Rich Freeman
2018-01-05 12:34 ` Walter Dnes
2018-01-05 13:08 ` Rich Freeman
2018-01-03 21:21 ` [gentoo-user] " Stroller
2018-01-03 21:31 ` Wols Lists
2018-01-03 21:43 ` Stroller
2018-01-03 21:49 ` Dale
2018-01-03 21:48 ` Rich Freeman
2018-01-03 21:53 ` Neil Bothwick
2018-01-03 22:07 ` Stroller
2018-01-03 22:11 ` Alan McKinnon
2018-01-03 22:41 ` Stroller
2018-01-03 22:47 ` Alan McKinnon
2018-01-04 2:18 ` Stroller
2018-01-03 22:51 ` Herminio Hernandez, Jr.
2018-01-03 23:41 ` Neil Bothwick
2018-01-04 2:20 ` Stroller
2018-01-02 19:44 ` Neil Bothwick
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=c738cc65-081e-dfb6-70e7-56d43516b000@gmail.com \
--to=alan.mckinnon@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