How to I prevent Ubuntu from kernel version upgrade and notification?
How to I prevent Ubuntu from kernel version upgrade and notification?
I'd like to keep my system from getting or prompting me for kernel upgrades and DIST upgrades.
I do want however to get all package updates and security updates.
I have looked at several posts, but they were for package "Holds" and that is too granular for what I am wanting. I just want to prevent Ubuntu from upgrading to a new Distribution like 16.10 which caused me issues, as well as a newer Kernel which booting into recovery mode my mouse and keyboard would not work.
I would like to keep existing dist. as is, as well as get any new software package updates or security updates.
I do not want to disable all updates, but I can if that is the simplest option.
kernel updates
asked Jul 21 '17 at 18:51
Zimbarush
301313
add a comment |
How to I prevent Ubuntu from kernel version upgrade and notification?
I'd like to keep my system from getting or prompting me for kernel upgrades and DIST upgrades.
I do want however to get all package updates and security updates.
I have looked at several posts, but they were for package "Holds" and that is too granular for what I am wanting. I just want to prevent Ubuntu from upgrading to a new Distribution like 16.10 which caused me issues, as well as a newer Kernel which booting into recovery mode my mouse and keyboard would not work.
I would like to keep existing dist. as is, as well as get any new software package updates or security updates.
I do not want to disable all updates, but I can if that is the simplest option.
kernel updates
asked Jul 21 '17 at 18:51
Zimbarush
301313
Package holds is exactly what you are "wanting" for the kernel updates. For the distro upgrade, just disable it in the software properties. There are lots of questions here about both.
– mikewhatever
Jul 21 '17 at 19:52
add a comment |
How to I prevent Ubuntu from kernel version upgrade and notification?
I'd like to keep my system from getting or prompting me for kernel upgrades and DIST upgrades.
I do want however to get all package updates and security updates.
I have looked at several posts, but they were for package "Holds" and that is too granular for what I am wanting. I just want to prevent Ubuntu from upgrading to a new Distribution like 16.10 which caused me issues, as well as a newer Kernel which booting into recovery mode my mouse and keyboard would not work.
I would like to keep existing dist. as is, as well as get any new software package updates or security updates.
I do not want to disable all updates, but I can if that is the simplest option.
kernel updates
asked Jul 21 '17 at 18:51
Zimbarush
301313
How to I prevent Ubuntu from kernel version upgrade and notification?
I'd like to keep my system from getting or prompting me for kernel upgrades and DIST upgrades.
I do want however to get all package updates and security updates.
I have looked at several posts, but they were for package "Holds" and that is too granular for what I am wanting. I just want to prevent Ubuntu from upgrading to a new Distribution like 16.10 which caused me issues, as well as a newer Kernel which booting into recovery mode my mouse and keyboard would not work.
I would like to keep existing dist. as is, as well as get any new software package updates or security updates.
I do not want to disable all updates, but I can if that is the simplest option.
kernel updates
kernel updates
asked Jul 21 '17 at 18:51
Zimbarush
301313
asked Jul 21 '17 at 18:51
Zimbarush
301313
asked Jul 21 '17 at 18:51
Zimbarush
301313
asked Jul 21 '17 at 18:51
Zimbarush
301313
asked Jul 21 '17 at 18:51
Zimbarush
301313
301313
Package holds is exactly what you are "wanting" for the kernel updates. For the distro upgrade, just disable it in the software properties. There are lots of questions here about both.
– mikewhatever
Jul 21 '17 at 19:52
add a comment |
Package holds is exactly what you are "wanting" for the kernel updates. For the distro upgrade, just disable it in the software properties. There are lots of questions here about both.
– mikewhatever
Jul 21 '17 at 19:52
Package holds is exactly what you are "wanting" for the kernel updates. For the distro upgrade, just disable it in the software properties. There are lots of questions here about both.
– mikewhatever
Jul 21 '17 at 19:52
Package holds is exactly what you are "wanting" for the kernel updates. For the distro upgrade, just disable it in the software properties. There are lots of questions here about both.
– mikewhatever
Jul 21 '17 at 19:52
add a comment |
1 Answer
1
active
oldest
votes
Thank You Mikewhatever for clarifying I needed to use package hold.
I used this post as a reference and ran command :
uname -r
to find my Kernel Version.
It gave output:
4.10.0-27-generic
Then I ran command:
sudo apt-mark hold 4.10.0-27-generic
and it gave output:
linux-cloud-tools-4.10.0-27-generic set on hold.
linux-headers-4.10.0-27-generic set on hold.
linux-image-4.10.0-27-generic set on hold.
linux-image-extra-4.10.0-27-generic set on hold.
linux-signed-image-4.10.0-27-generic set on hold.
linux-tools-4.10.0-27-generic set on hold.
I believe this should be what I wanted to accomplish.
answered Jul 21 '17 at 20:36
Zimbarush
301313
Yes, it is but what you want to accomplish makes no sense and is potentially unsafe. Having the OS fully updated, kernel included, is what everybody should do. Except in very specific cases where a given software version (or kernel version in even fewer cases) is required and has to be put on hold, holding kernel and/or security updates just because is really dumb. In an internet facing machine it's quite unsafe and not only for the user that refuses updates. Keep in mind you have, as everybody else, social responsibility.
– user692175
Jul 22 '17 at 3:08
Instead of blocking the kernel upgrades, you can boot from an earlier kernel version by selecting it from the GRUB menu like this: askubuntu.com/questions/955020/ubuntu-wont-boot-kernel-error/… and wait for a kernel upgrade that satisfies all of your requirements by booting once the normal way after each new kernel upgrade.
– karel
Jan 20 at 10:30
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f938494%2fhow-to-i-prevent-ubuntu-from-kernel-version-upgrade-and-notification%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thank You Mikewhatever for clarifying I needed to use package hold.
I used this post as a reference and ran command :
uname -r
to find my Kernel Version.
It gave output:
4.10.0-27-generic
Then I ran command:
sudo apt-mark hold 4.10.0-27-generic
and it gave output:
linux-cloud-tools-4.10.0-27-generic set on hold.
linux-headers-4.10.0-27-generic set on hold.
linux-image-4.10.0-27-generic set on hold.
linux-image-extra-4.10.0-27-generic set on hold.
linux-signed-image-4.10.0-27-generic set on hold.
linux-tools-4.10.0-27-generic set on hold.
I believe this should be what I wanted to accomplish.
answered Jul 21 '17 at 20:36
Zimbarush
301313
Yes, it is but what you want to accomplish makes no sense and is potentially unsafe. Having the OS fully updated, kernel included, is what everybody should do. Except in very specific cases where a given software version (or kernel version in even fewer cases) is required and has to be put on hold, holding kernel and/or security updates just because is really dumb. In an internet facing machine it's quite unsafe and not only for the user that refuses updates. Keep in mind you have, as everybody else, social responsibility.
– user692175
Jul 22 '17 at 3:08
Instead of blocking the kernel upgrades, you can boot from an earlier kernel version by selecting it from the GRUB menu like this: askubuntu.com/questions/955020/ubuntu-wont-boot-kernel-error/… and wait for a kernel upgrade that satisfies all of your requirements by booting once the normal way after each new kernel upgrade.
– karel
Jan 20 at 10:30
add a comment |
Thank You Mikewhatever for clarifying I needed to use package hold.
I used this post as a reference and ran command :
uname -r
to find my Kernel Version.
It gave output:
4.10.0-27-generic
Then I ran command:
sudo apt-mark hold 4.10.0-27-generic
and it gave output:
linux-cloud-tools-4.10.0-27-generic set on hold.
linux-headers-4.10.0-27-generic set on hold.
linux-image-4.10.0-27-generic set on hold.
linux-image-extra-4.10.0-27-generic set on hold.
linux-signed-image-4.10.0-27-generic set on hold.
linux-tools-4.10.0-27-generic set on hold.
I believe this should be what I wanted to accomplish.
answered Jul 21 '17 at 20:36
Zimbarush
301313
Yes, it is but what you want to accomplish makes no sense and is potentially unsafe. Having the OS fully updated, kernel included, is what everybody should do. Except in very specific cases where a given software version (or kernel version in even fewer cases) is required and has to be put on hold, holding kernel and/or security updates just because is really dumb. In an internet facing machine it's quite unsafe and not only for the user that refuses updates. Keep in mind you have, as everybody else, social responsibility.
– user692175
Jul 22 '17 at 3:08
Instead of blocking the kernel upgrades, you can boot from an earlier kernel version by selecting it from the GRUB menu like this: askubuntu.com/questions/955020/ubuntu-wont-boot-kernel-error/… and wait for a kernel upgrade that satisfies all of your requirements by booting once the normal way after each new kernel upgrade.
– karel
Jan 20 at 10:30
add a comment |
Thank You Mikewhatever for clarifying I needed to use package hold.
I used this post as a reference and ran command :
uname -r
to find my Kernel Version.
It gave output:
4.10.0-27-generic
Then I ran command:
sudo apt-mark hold 4.10.0-27-generic
and it gave output:
linux-cloud-tools-4.10.0-27-generic set on hold.
linux-headers-4.10.0-27-generic set on hold.
linux-image-4.10.0-27-generic set on hold.
linux-image-extra-4.10.0-27-generic set on hold.
linux-signed-image-4.10.0-27-generic set on hold.
linux-tools-4.10.0-27-generic set on hold.
I believe this should be what I wanted to accomplish.
answered Jul 21 '17 at 20:36
Zimbarush
301313
Thank You Mikewhatever for clarifying I needed to use package hold.
I used this post as a reference and ran command :
uname -r
to find my Kernel Version.
It gave output:
4.10.0-27-generic
Then I ran command:
sudo apt-mark hold 4.10.0-27-generic
and it gave output:
linux-cloud-tools-4.10.0-27-generic set on hold.
linux-headers-4.10.0-27-generic set on hold.
linux-image-4.10.0-27-generic set on hold.
linux-image-extra-4.10.0-27-generic set on hold.
linux-signed-image-4.10.0-27-generic set on hold.
linux-tools-4.10.0-27-generic set on hold.
I believe this should be what I wanted to accomplish.
answered Jul 21 '17 at 20:36
Zimbarush
301313
answered Jul 21 '17 at 20:36
Zimbarush
301313
answered Jul 21 '17 at 20:36
Zimbarush
301313
answered Jul 21 '17 at 20:36
Zimbarush
301313
301313
Yes, it is but what you want to accomplish makes no sense and is potentially unsafe. Having the OS fully updated, kernel included, is what everybody should do. Except in very specific cases where a given software version (or kernel version in even fewer cases) is required and has to be put on hold, holding kernel and/or security updates just because is really dumb. In an internet facing machine it's quite unsafe and not only for the user that refuses updates. Keep in mind you have, as everybody else, social responsibility.
– user692175
Jul 22 '17 at 3:08
Instead of blocking the kernel upgrades, you can boot from an earlier kernel version by selecting it from the GRUB menu like this: askubuntu.com/questions/955020/ubuntu-wont-boot-kernel-error/… and wait for a kernel upgrade that satisfies all of your requirements by booting once the normal way after each new kernel upgrade.
– karel
Jan 20 at 10:30
add a comment |
Yes, it is but what you want to accomplish makes no sense and is potentially unsafe. Having the OS fully updated, kernel included, is what everybody should do. Except in very specific cases where a given software version (or kernel version in even fewer cases) is required and has to be put on hold, holding kernel and/or security updates just because is really dumb. In an internet facing machine it's quite unsafe and not only for the user that refuses updates. Keep in mind you have, as everybody else, social responsibility.
– user692175
Jul 22 '17 at 3:08
Instead of blocking the kernel upgrades, you can boot from an earlier kernel version by selecting it from the GRUB menu like this: askubuntu.com/questions/955020/ubuntu-wont-boot-kernel-error/… and wait for a kernel upgrade that satisfies all of your requirements by booting once the normal way after each new kernel upgrade.
– karel
Jan 20 at 10:30
Yes, it is but what you want to accomplish makes no sense and is potentially unsafe. Having the OS fully updated, kernel included, is what everybody should do. Except in very specific cases where a given software version (or kernel version in even fewer cases) is required and has to be put on hold, holding kernel and/or security updates just because is really dumb. In an internet facing machine it's quite unsafe and not only for the user that refuses updates. Keep in mind you have, as everybody else, social responsibility.
– user692175
Jul 22 '17 at 3:08
Yes, it is but what you want to accomplish makes no sense and is potentially unsafe. Having the OS fully updated, kernel included, is what everybody should do. Except in very specific cases where a given software version (or kernel version in even fewer cases) is required and has to be put on hold, holding kernel and/or security updates just because is really dumb. In an internet facing machine it's quite unsafe and not only for the user that refuses updates. Keep in mind you have, as everybody else, social responsibility.
– user692175
Jul 22 '17 at 3:08
Instead of blocking the kernel upgrades, you can boot from an earlier kernel version by selecting it from the GRUB menu like this: askubuntu.com/questions/955020/ubuntu-wont-boot-kernel-error/… and wait for a kernel upgrade that satisfies all of your requirements by booting once the normal way after each new kernel upgrade.
– karel
Jan 20 at 10:30
Instead of blocking the kernel upgrades, you can boot from an earlier kernel version by selecting it from the GRUB menu like this: askubuntu.com/questions/955020/ubuntu-wont-boot-kernel-error/… and wait for a kernel upgrade that satisfies all of your requirements by booting once the normal way after each new kernel upgrade.
– karel
Jan 20 at 10:30
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f938494%2fhow-to-i-prevent-ubuntu-from-kernel-version-upgrade-and-notification%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Package holds is exactly what you are "wanting" for the kernel updates. For the distro upgrade, just disable it in the software properties. There are lots of questions here about both.
– mikewhatever
Jul 21 '17 at 19:52