From: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Gidi Gal <gidi.gal.linux@gmail.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: How to switch between installed kernel and developed kernel
Date: Tue, 23 Mar 2021 11:16:38 -0400 [thread overview]
Message-ID: <CAFSeFg8wCxC=z4HN9O8=1wsnjH7j=iV1WO_v3=TmkCqfmT_nYg@mail.gmail.com> (raw)
In-Reply-To: <21684.1616511966@turing-police>
[-- Attachment #1.1: Type: text/plain, Size: 1402 bytes --]
On Tue, Mar 23, 2021 at 11:06 AM Valdis Klētnieks <valdis.kletnieks@vt.edu>
wrote:
> On Tue, 23 Mar 2021 00:29:10 -0400, Aruna Hewapathirane said:
>
> > Use : linux-check-removal <uname-r of your kernel to remove>
>
> That's a debian-specific thing...
>
Yep and he is running Ubuntu which is a derivative of Debian ? His .config
just told me this :-)
But valid point will keep things generic in future.
CONFIG_CC_VERSION_TEXT="gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0"
>
> > > Seriously - if you're not comfortable with that level of sysadmin
> > > procedures,
> > > maybe you shouldn't be a kernel hacker...
> >
> >
> > Do not listen to Valdis in this case as we were all newbies at one time
>
> That's not what I said.
>
> What I *said* was "if you're a newbie who's all "ZOMG I'm going to
> accidentally break it"
> maybe you shouldn't be a kernel hacker. :)
>
> So he breaks it. Then comes the fun part when he learns how to fix it :-)
> > And listen to more experienced folk like Valdis who probably knows more
> > about all the subsystems than anyone.
>
> Oh, there's people like Greg KH who know a lot more than I do. He's also
> *paid* to know a lot more than I do. :) After 4 decades in IT, I've just
> gotten
> good at debugging and knowing where to start checking for more data on
> something.
>
> Why don't any of us ever get paid ? Ouch...
[-- Attachment #1.2: Type: text/html, Size: 2245 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:17 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 [this message]
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
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='CAFSeFg8wCxC=z4HN9O8=1wsnjH7j=iV1WO_v3=TmkCqfmT_nYg@mail.gmail.com' \
--to=aruna.hewapathirane@gmail.com \
--cc=gidi.gal.linux@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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).