3

I tried two different methods but could not install systemd

1st method from here, 2nd method from here

Confirmation that systemd is not installed:

edward@computer:~$ file /lib/systemd/systemd
/lib/systemd/systemd: ERROR: cannot open `/lib/systemd/systemd' (No such file or directory)

Another confirmation:

I'm following the methods proposed in https://askubuntu.com/a/420979/294611 (against this question was closed as duplicated to), yet for some reason my system doesn't boot.

  • As far as I know, systemd is not yet supported on Ubuntu. If you want to try it, boot Fedora or Arch linux. – Panther Dec 25 '14 at 17:32
  • 3
    And from - wiki.ubuntu.com/systemd#Warning.21_Experimental_code - "Warning! Experimental code systemd is under active development in Ubuntu although the rough plan would be to default to systemd during development of 15.04. If you want to help it's best to be running 15.04. (14.10 might be doable as well..)" – Panther Dec 25 '14 at 17:36
  • @bodhi.zazen there is method given in the first link I gave right ? then why cant we try it ? – Edward Torvalds Dec 25 '14 at 17:41
  • You are welcome to try it, but see the FAQ here regarding code in development see - askubuntu.com/help/on-topic "Questions that you should avoid: ... <clip> ... Issues with the next version of Ubuntu (Ubuntu+1) (More information about Alpha and Beta release issues)." systemd is experimental code at this time, ready for 15.04, which is ubuntu +1 – Panther Dec 25 '14 at 17:44
  • @bodhi.zazen if trying systemd is off-topic then why there is a method to try it out in this answer ? – Edward Torvalds Dec 25 '14 at 17:46
6

Well, I´m not sure what Canonical did. When I installed systemd on my Raring installation (as seen in comments), the binary was there. Now it isn´t anywhere, and the changelog before Utopic version 208-8ubuntu1 is useless (utopic does have the binary there), since they just imported the package from Debian, which is a blessing to Utopic users, since the method described in the answer works for them.

Trusty changelogs doesn´t either explain what could happened either. I checked the BZR repository looking for clues directly about what happened with the package. There´s a systemd.install file in the debian\ directory, yet the package itself doesn´t exist in repositories; the systemv-init package which replace /sbin/init with a link to systemd binary indeed points to /lib/systemd/systemd, which only adds to my confusion. The control file has an entry for the systemd package too. The systemd.link file also links to /lib/systemd/systemd from the /bin directory.

All evidence points that systemd package is necesary to get systemd binary, yet the package itself is not provided anywhere for trusty. This has lead me to think that Canonical decided to not provide systemd binary for releases before trusty in their repositories, which is hinted by the fact that if you build the systemd debian source package that Ubuntu provides you will get the systemd package and all necesary binaries to boot using systemd as init.

So, to solve the problem you are facing, because the binary simply isn´t there, you just need to remove the init of your kernel parameters and revert the changes you have done to your /etc/default/grub file and run sudo update-grub, in summary everything you have done in order to replace upstart with systemd. Afterwards, is your call: upgrade to utopic, leave it as it is, or build systemd package from debian sources.

For now, I would only recommend Utopic and later users to install systemd, as before that, there´s no sure fire way to install systemd and replace the init with the packages provided by Canonical/Ubuntu repositories.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.