Safe way to upgrade systemd in Xenial?












2














Xenial (16.04) has systemd-229. Unfortunately, that version seems to still have a bug that prevents KillUserProcesses from working properly. See this bug.



So, I want to upgrade to at least 230, or even newer.



Since systemd is such a core plumbing to Ubuntu, how do I do this safely?



(edit: fixed version number)










share|improve this question
























  • Safely: You upgrade to a newer version of Ubuntu. As a bonus, most of your other software gets a version-bump, too.
    – user535733
    Oct 20 '17 at 1:34










  • @user535733 No, thanks. There's not yet any LTS version after 16.04.
    – pepoluan
    Oct 20 '17 at 1:52


















2














Xenial (16.04) has systemd-229. Unfortunately, that version seems to still have a bug that prevents KillUserProcesses from working properly. See this bug.



So, I want to upgrade to at least 230, or even newer.



Since systemd is such a core plumbing to Ubuntu, how do I do this safely?



(edit: fixed version number)










share|improve this question
























  • Safely: You upgrade to a newer version of Ubuntu. As a bonus, most of your other software gets a version-bump, too.
    – user535733
    Oct 20 '17 at 1:34










  • @user535733 No, thanks. There's not yet any LTS version after 16.04.
    – pepoluan
    Oct 20 '17 at 1:52
















2












2








2







Xenial (16.04) has systemd-229. Unfortunately, that version seems to still have a bug that prevents KillUserProcesses from working properly. See this bug.



So, I want to upgrade to at least 230, or even newer.



Since systemd is such a core plumbing to Ubuntu, how do I do this safely?



(edit: fixed version number)










share|improve this question















Xenial (16.04) has systemd-229. Unfortunately, that version seems to still have a bug that prevents KillUserProcesses from working properly. See this bug.



So, I want to upgrade to at least 230, or even newer.



Since systemd is such a core plumbing to Ubuntu, how do I do this safely?



(edit: fixed version number)







16.04 systemd






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 13 hours ago









chimeracoder

1031




1031










asked Oct 20 '17 at 1:31









pepoluan

370213




370213












  • Safely: You upgrade to a newer version of Ubuntu. As a bonus, most of your other software gets a version-bump, too.
    – user535733
    Oct 20 '17 at 1:34










  • @user535733 No, thanks. There's not yet any LTS version after 16.04.
    – pepoluan
    Oct 20 '17 at 1:52




















  • Safely: You upgrade to a newer version of Ubuntu. As a bonus, most of your other software gets a version-bump, too.
    – user535733
    Oct 20 '17 at 1:34










  • @user535733 No, thanks. There's not yet any LTS version after 16.04.
    – pepoluan
    Oct 20 '17 at 1:52


















Safely: You upgrade to a newer version of Ubuntu. As a bonus, most of your other software gets a version-bump, too.
– user535733
Oct 20 '17 at 1:34




Safely: You upgrade to a newer version of Ubuntu. As a bonus, most of your other software gets a version-bump, too.
– user535733
Oct 20 '17 at 1:34












@user535733 No, thanks. There's not yet any LTS version after 16.04.
– pepoluan
Oct 20 '17 at 1:52






@user535733 No, thanks. There's not yet any LTS version after 16.04.
– pepoluan
Oct 20 '17 at 1:52












1 Answer
1






active

oldest

votes


















3














You have five options. You will need to decide which criteria (LTS, safe, easy, fast) are more important - no option meets all of them:




  1. Wait for 18.04 LTS. This is safe, but it does not fix your problem.


  2. Install 17.04 or 17.10 (non-LTS). This is also safe, but you seem to not like this one.


  3. File a Stable Release Update request on Launchpad to get the fix backported to 16.04. This is reasonably safe - SRUs are well-tested. SRUs take time, and may be rejected entirely by the developers.


  4. Try installing a systemd package from a newer release of Ubuntu. This is almost certainly not safe at all, and risks breaking your system horribly.


  5. Learn to compile systemd, and install a newer version. This requires great skill and patience to do properly. Many, many opportunities for breakage and frustration, not safe at all unless you have years of experience with compiling and init.







share|improve this answer























  • I would NOT install 17.04 and expect to upgrade 17.10 -> 18.04 at this moment, too many changes to call "safe" by any stretch. I would consider a fresh install of 17.10 in a month anticipating an upgrade to 18.04 to be as safe as it gets with the fresh install and upgrade approach.
    – Panther
    Oct 20 '17 at 2:48












  • @bodhi.zazen agreed. Since the OP already rejected that option, I didn't spend a lot of time qualifying it, nor wandering down the slippery slope of comparative safety. That would be a whole book, eh?
    – user535733
    Oct 20 '17 at 2:55










  • agreed, but just mentioning the issues as I am guessing the OP has not done much if any research into the changes 17.10 brings.
    – Panther
    Oct 20 '17 at 3:02










  • @Panther true. There's a reason why I insisted on LTS (in this case, 16.04), because it "should be good" until 2021. I don't have to keep myself constantly up-to-date with "latest and greatest".
    – pepoluan
    Nov 10 '17 at 2:32











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f966548%2fsafe-way-to-upgrade-systemd-in-xenial%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









3














You have five options. You will need to decide which criteria (LTS, safe, easy, fast) are more important - no option meets all of them:




  1. Wait for 18.04 LTS. This is safe, but it does not fix your problem.


  2. Install 17.04 or 17.10 (non-LTS). This is also safe, but you seem to not like this one.


  3. File a Stable Release Update request on Launchpad to get the fix backported to 16.04. This is reasonably safe - SRUs are well-tested. SRUs take time, and may be rejected entirely by the developers.


  4. Try installing a systemd package from a newer release of Ubuntu. This is almost certainly not safe at all, and risks breaking your system horribly.


  5. Learn to compile systemd, and install a newer version. This requires great skill and patience to do properly. Many, many opportunities for breakage and frustration, not safe at all unless you have years of experience with compiling and init.







share|improve this answer























  • I would NOT install 17.04 and expect to upgrade 17.10 -> 18.04 at this moment, too many changes to call "safe" by any stretch. I would consider a fresh install of 17.10 in a month anticipating an upgrade to 18.04 to be as safe as it gets with the fresh install and upgrade approach.
    – Panther
    Oct 20 '17 at 2:48












  • @bodhi.zazen agreed. Since the OP already rejected that option, I didn't spend a lot of time qualifying it, nor wandering down the slippery slope of comparative safety. That would be a whole book, eh?
    – user535733
    Oct 20 '17 at 2:55










  • agreed, but just mentioning the issues as I am guessing the OP has not done much if any research into the changes 17.10 brings.
    – Panther
    Oct 20 '17 at 3:02










  • @Panther true. There's a reason why I insisted on LTS (in this case, 16.04), because it "should be good" until 2021. I don't have to keep myself constantly up-to-date with "latest and greatest".
    – pepoluan
    Nov 10 '17 at 2:32
















3














You have five options. You will need to decide which criteria (LTS, safe, easy, fast) are more important - no option meets all of them:




  1. Wait for 18.04 LTS. This is safe, but it does not fix your problem.


  2. Install 17.04 or 17.10 (non-LTS). This is also safe, but you seem to not like this one.


  3. File a Stable Release Update request on Launchpad to get the fix backported to 16.04. This is reasonably safe - SRUs are well-tested. SRUs take time, and may be rejected entirely by the developers.


  4. Try installing a systemd package from a newer release of Ubuntu. This is almost certainly not safe at all, and risks breaking your system horribly.


  5. Learn to compile systemd, and install a newer version. This requires great skill and patience to do properly. Many, many opportunities for breakage and frustration, not safe at all unless you have years of experience with compiling and init.







share|improve this answer























  • I would NOT install 17.04 and expect to upgrade 17.10 -> 18.04 at this moment, too many changes to call "safe" by any stretch. I would consider a fresh install of 17.10 in a month anticipating an upgrade to 18.04 to be as safe as it gets with the fresh install and upgrade approach.
    – Panther
    Oct 20 '17 at 2:48












  • @bodhi.zazen agreed. Since the OP already rejected that option, I didn't spend a lot of time qualifying it, nor wandering down the slippery slope of comparative safety. That would be a whole book, eh?
    – user535733
    Oct 20 '17 at 2:55










  • agreed, but just mentioning the issues as I am guessing the OP has not done much if any research into the changes 17.10 brings.
    – Panther
    Oct 20 '17 at 3:02










  • @Panther true. There's a reason why I insisted on LTS (in this case, 16.04), because it "should be good" until 2021. I don't have to keep myself constantly up-to-date with "latest and greatest".
    – pepoluan
    Nov 10 '17 at 2:32














3












3








3






You have five options. You will need to decide which criteria (LTS, safe, easy, fast) are more important - no option meets all of them:




  1. Wait for 18.04 LTS. This is safe, but it does not fix your problem.


  2. Install 17.04 or 17.10 (non-LTS). This is also safe, but you seem to not like this one.


  3. File a Stable Release Update request on Launchpad to get the fix backported to 16.04. This is reasonably safe - SRUs are well-tested. SRUs take time, and may be rejected entirely by the developers.


  4. Try installing a systemd package from a newer release of Ubuntu. This is almost certainly not safe at all, and risks breaking your system horribly.


  5. Learn to compile systemd, and install a newer version. This requires great skill and patience to do properly. Many, many opportunities for breakage and frustration, not safe at all unless you have years of experience with compiling and init.







share|improve this answer














You have five options. You will need to decide which criteria (LTS, safe, easy, fast) are more important - no option meets all of them:




  1. Wait for 18.04 LTS. This is safe, but it does not fix your problem.


  2. Install 17.04 or 17.10 (non-LTS). This is also safe, but you seem to not like this one.


  3. File a Stable Release Update request on Launchpad to get the fix backported to 16.04. This is reasonably safe - SRUs are well-tested. SRUs take time, and may be rejected entirely by the developers.


  4. Try installing a systemd package from a newer release of Ubuntu. This is almost certainly not safe at all, and risks breaking your system horribly.


  5. Learn to compile systemd, and install a newer version. This requires great skill and patience to do properly. Many, many opportunities for breakage and frustration, not safe at all unless you have years of experience with compiling and init.








share|improve this answer














share|improve this answer



share|improve this answer








edited Oct 20 '17 at 2:17









muru

1




1










answered Oct 20 '17 at 2:12









user535733

7,62722942




7,62722942












  • I would NOT install 17.04 and expect to upgrade 17.10 -> 18.04 at this moment, too many changes to call "safe" by any stretch. I would consider a fresh install of 17.10 in a month anticipating an upgrade to 18.04 to be as safe as it gets with the fresh install and upgrade approach.
    – Panther
    Oct 20 '17 at 2:48












  • @bodhi.zazen agreed. Since the OP already rejected that option, I didn't spend a lot of time qualifying it, nor wandering down the slippery slope of comparative safety. That would be a whole book, eh?
    – user535733
    Oct 20 '17 at 2:55










  • agreed, but just mentioning the issues as I am guessing the OP has not done much if any research into the changes 17.10 brings.
    – Panther
    Oct 20 '17 at 3:02










  • @Panther true. There's a reason why I insisted on LTS (in this case, 16.04), because it "should be good" until 2021. I don't have to keep myself constantly up-to-date with "latest and greatest".
    – pepoluan
    Nov 10 '17 at 2:32


















  • I would NOT install 17.04 and expect to upgrade 17.10 -> 18.04 at this moment, too many changes to call "safe" by any stretch. I would consider a fresh install of 17.10 in a month anticipating an upgrade to 18.04 to be as safe as it gets with the fresh install and upgrade approach.
    – Panther
    Oct 20 '17 at 2:48












  • @bodhi.zazen agreed. Since the OP already rejected that option, I didn't spend a lot of time qualifying it, nor wandering down the slippery slope of comparative safety. That would be a whole book, eh?
    – user535733
    Oct 20 '17 at 2:55










  • agreed, but just mentioning the issues as I am guessing the OP has not done much if any research into the changes 17.10 brings.
    – Panther
    Oct 20 '17 at 3:02










  • @Panther true. There's a reason why I insisted on LTS (in this case, 16.04), because it "should be good" until 2021. I don't have to keep myself constantly up-to-date with "latest and greatest".
    – pepoluan
    Nov 10 '17 at 2:32
















I would NOT install 17.04 and expect to upgrade 17.10 -> 18.04 at this moment, too many changes to call "safe" by any stretch. I would consider a fresh install of 17.10 in a month anticipating an upgrade to 18.04 to be as safe as it gets with the fresh install and upgrade approach.
– Panther
Oct 20 '17 at 2:48






I would NOT install 17.04 and expect to upgrade 17.10 -> 18.04 at this moment, too many changes to call "safe" by any stretch. I would consider a fresh install of 17.10 in a month anticipating an upgrade to 18.04 to be as safe as it gets with the fresh install and upgrade approach.
– Panther
Oct 20 '17 at 2:48














@bodhi.zazen agreed. Since the OP already rejected that option, I didn't spend a lot of time qualifying it, nor wandering down the slippery slope of comparative safety. That would be a whole book, eh?
– user535733
Oct 20 '17 at 2:55




@bodhi.zazen agreed. Since the OP already rejected that option, I didn't spend a lot of time qualifying it, nor wandering down the slippery slope of comparative safety. That would be a whole book, eh?
– user535733
Oct 20 '17 at 2:55












agreed, but just mentioning the issues as I am guessing the OP has not done much if any research into the changes 17.10 brings.
– Panther
Oct 20 '17 at 3:02




agreed, but just mentioning the issues as I am guessing the OP has not done much if any research into the changes 17.10 brings.
– Panther
Oct 20 '17 at 3:02












@Panther true. There's a reason why I insisted on LTS (in this case, 16.04), because it "should be good" until 2021. I don't have to keep myself constantly up-to-date with "latest and greatest".
– pepoluan
Nov 10 '17 at 2:32




@Panther true. There's a reason why I insisted on LTS (in this case, 16.04), because it "should be good" until 2021. I don't have to keep myself constantly up-to-date with "latest and greatest".
– pepoluan
Nov 10 '17 at 2:32


















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f966548%2fsafe-way-to-upgrade-systemd-in-xenial%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Questions related to Moebius Transform of Characteristic Function of the Primes

List of scandals in India

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?