BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Debian Question
- Subject: [Discuss] Debian Question
- From: kentborg at borg.org (Kent Borg)
- Date: Sun, 5 Nov 2023 11:45:11 -0800
- In-reply-to: <9755f11c-aa76-4d3a-a58e-3ae2b24201d6@borg.org>
- References: <9755f11c-aa76-4d3a-a58e-3ae2b24201d6@borg.org>
Thanks to CHRISTOP-PERRAULT at comcast.net, dsr at randomstring.org, and richard.pieri at gmail.com. VERY valuable answers. But I'm holding off on implementing any of that, for the moment, until I better understand what packages get updated when. Don't want to block/freeze that wrong stuff. But I have updated my notes for when I am ready. Thanks again, -kb On 11/2/23 14:34, Kent Borg 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.
- Follow-Ups:
- [Discuss] Debian Question
- From: kentborg at borg.org (Kent Borg)
- [Discuss] Debian Question
- References:
- [Discuss] Debian Question
- From: kentborg at borg.org (Kent Borg)
- [Discuss] Debian Question
- Prev by Date: [Discuss] Debian Question
- Next by Date: [Discuss] Please join us for another Pre-SC Student Cluster Contest team Meetup tomorrow
- Previous by thread: [Discuss] Debian Question
- Next by thread: [Discuss] Debian Question
- Index(es):