update_a_brand_new_kernel_debian_11
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
update_a_brand_new_kernel_debian_11 [2022/02/27 20:24] – dino | update_a_brand_new_kernel_debian_11 [2024/03/12 21:23] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 46: | Line 46: | ||
</ | </ | ||
+ | Next, an easy solution is to use apt-pinning to avoid having different version branches causing your system prompting for updates from the experimental repository. Open the following file using a text editor. | ||
+ | < | ||
+ | sudo nano / | ||
+ | </ | ||
+ | |||
+ | Next, add the following. | ||
+ | |||
+ | < | ||
+ | Package: * | ||
+ | Pin: release a=bullseye | ||
+ | Pin-Priority: | ||
+ | |||
+ | Package: linux-image-amd64 | ||
+ | Pin: release a=unstable | ||
+ | Pin-Priority: | ||
+ | |||
+ | Package: * | ||
+ | Pin: release a=unstable | ||
+ | Pin-Priority: | ||
+ | </ | ||
+ | |||
+ | Save it and get out (Ctrl-O and CTRL-X). | ||
+ | |||
+ | The order goes all updates are preferenced to Bullseye with a higher score (500) than unstable (100), so you are not prompted on various packages to be updated from the unstable repository. | ||
+ | |||
+ | However, to make it easy to keep the kernel up to date when you run the apt update command for your standard Bullseye packages, the example above has set linux-image-amd64 as a high priority (1000) using the unstable repository above any other source for that package only. | ||
+ | |||
+ | Next: | ||
+ | |||
+ | < | ||
+ | sudo apt update | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | sudo apt upgrade | ||
+ | </ | ||
update_a_brand_new_kernel_debian_11.1645993479.txt.gz · Last modified: 2024/03/12 21:24 (external edit)