BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Debian Question
- Subject: [Discuss] Debian Question
- From: CHRISTOP-PERRAULT at comcast.net (CHRISTOP-PERRAULT at comcast.net)
- Date: Thu, 2 Nov 2023 15:05:52 -0400 (EDT)
- In-reply-to: <9755f11c-aa76-4d3a-a58e-3ae2b24201d6@borg.org>
- References: <9755f11c-aa76-4d3a-a58e-3ae2b24201d6@borg.org>
I come from more a yum/RHEL based background and I know you can configure yum to exclude certain packages (in this case being the official kernel). This link looks like it has the Debian/apt-get answer: https://askubuntu.com/questions/99774/exclude-packages-from-apt-get-upgrade I've only done this with openjdk packages that I can't upgrade because of compatibility issues, but I'm guessing you can do the same with kernel. Chris > On 11/02/2023 2:34 PM EDT Kent Borg <kentborg at borg.org> wrote: > > > Actually a "Raspbian" question, but I think it amounts to much the same: > I have an OS installation, that came with all the usual stuff, and I > have added more stuff, as one does. One of the things I have done is > compile my own kernel. At some point there will be a kernel update, that > I won't want, instead I will likely want to compile a new kernel from > updated sources. > > What is the best way to manage this? I don't want to accidentally > install the standard kernel on top of my custom kernel, but I would like > to be prodded to compile a new kernel by the availability of a new > kernel .deb. > > Suggestions? > > > Thanks, > > -kb > > _______________________________________________ > Discuss mailing list > Discuss at lists.blu.org > http://lists.blu.org/mailman/listinfo/discuss
- References:
- [Discuss] Debian Question
- From: kentborg at borg.org (Kent Borg)
- [Discuss] Debian Question
- Prev by Date: [Discuss] Debian Question
- Next by Date: [Discuss] Debian Question
- Previous by thread: [Discuss] Debian Question
- Next by thread: [Discuss] Debian Question
- Index(es):