From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Gidi Gal <gidi.gal.linux@gmail.com>
Cc: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>,
kernelnewbies@kernelnewbies.org
Subject: Re: How to switch between installed kernel and developed kernel
Date: Tue, 23 Mar 2021 11:05:47 -0400 [thread overview]
Message-ID: <21662.1616511947@turing-police> (raw)
In-Reply-To: <CAB+0Vomu+EaW8N6VNMFcZBB29MxnYYvD=1bF98Tf+1YgwaRi2Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1193 bytes --]
On Tue, 23 Mar 2021 16:37:13 +0200, you said:
> I gave up for now and prepared bash script for removing the files, based on
> the information in
> https://www.cyberciti.biz/faq/debian-redhat-linux-delete-kernel-command/
> (see "A note about custom compiled Linux kernel" section). In my opinion,
> if Makefile supports install, it should support uninstall as well.
Well, here's the thing.. the just-built kernel tree know what it has to install
because it was just built with that .config, and it knows what files it just
built.
But how is that 5.12-rc4 build supposed to know what to remove that belonged
to a 5.9 kernel built with a different .config that the 5.12-rc4 used, and which
potentially had more modules enabled than the current source tree? Bonus
points for knowing how to figure out if the 5.9 kernel was installed via rpm or
dpkg or opkg or 'make install', and whether the 'make install' invoked the
system-supplied /sbin/installkernel script, or the user provided a variant that
installed more/less/different files?
Especially as you noted, that it's a 3 or 4 line bash script to remove the
files. And you hopefully know what extra rpm/dkpg stuff you need to
clean up....
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-03-23 15:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 12:11 How to switch between installed kernel and developed kernel Gidi Gal
2021-03-22 12:30 ` Bernd Petrovitsch
2021-03-22 12:57 ` Valdis Klētnieks
2021-03-22 12:59 ` Bjørn Mork
2021-03-22 17:53 ` Gidi Gal
2021-03-22 21:18 ` Aruna Hewapathirane
2021-03-22 21:19 ` Aruna Hewapathirane
2021-03-22 22:01 ` Gidi Gal
2021-03-23 1:17 ` Valdis Klētnieks
2021-03-23 4:29 ` Aruna Hewapathirane
2021-03-23 15:06 ` Valdis Klētnieks
2021-03-23 15:16 ` Aruna Hewapathirane
2021-03-23 15:11 ` Gidi Gal
[not found] ` <CAB+0Vomu+EaW8N6VNMFcZBB29MxnYYvD=1bF98Tf+1YgwaRi2Q@mail.gmail.com>
2021-03-23 15:05 ` Valdis Klētnieks [this message]
2021-03-23 15:23 ` Aruna Hewapathirane
2021-03-23 8:53 ` Ahmad Fatoum
2021-03-25 15:42 ` jim.cromie
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=21662.1616511947@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=aruna.hewapathirane@gmail.com \
--cc=gidi.gal.linux@gmail.com \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).