Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Ubuntu Systemd Plans: Will Be Default By Ubuntu 16.04 LTS

  1. #1
    Join Date
    Jan 2007
    Posts
    14,358

    Default Ubuntu Systemd Plans: Will Be Default By Ubuntu 16.04 LTS

    Phoronix: Ubuntu Systemd Plans: Will Be Default By Ubuntu 16.04 LTS

    Now that Ubuntu has pledged support to systemd moving forward in place of their in-house Upstart project, developers are starting to figure out the systemd migration path...

    http://www.phoronix.com/vr.php?view=MTYyODk

  2. #2
    Join Date
    Mar 2014
    Location
    In the land of the ice and snow
    Posts
    1

    Default Nice to see Ubuntu moving things forward

    Had to chuckle a bit watching Steve Langasek discussing systemd after he had voted against it as the next Debian init. No matter what the purists say, systemd turned out to be the better init system; Upstart had potential, but development stagnated and major issues were never dealt with. Anyone know when systemd will be introduced as the default init in Ubuntu? The sooner they rip out Upstart code, the better; they can focus more on Mir and other technologies that could make Ubuntu an even better distro than it already is.

  3. #3
    Join Date
    Jan 2012
    Posts
    57

    Default

    The link to the session notes points back to the Phoronix article.

  4. #4
    Join Date
    Nov 2012
    Posts
    145

    Default

    With this and the Mir story, I guess 16.04 is the new Ubuntu pie in the sky? The date they put on anything they don't know when they can have finished?

  5. #5
    Join Date
    Sep 2008
    Location
    Vilnius, Lithuania
    Posts
    2,522

    Default

    Quote Originally Posted by carewolf View Post
    With this and the Mir story, I guess 16.04 is the new Ubuntu pie in the sky? The date they put on anything they don't know when they can have finished?
    This is "by", Mir is "in".

  6. #6
    Join Date
    Nov 2008
    Posts
    25

    Default

    Wow, this is in two years. Is it really going to take this long to migrate? I'd say a few months should be enough to get it done. And they basically have most of the work already done in Fedora and other systemd distributions.

  7. #7
    Join Date
    Sep 2008
    Location
    Vilnius, Lithuania
    Posts
    2,522

    Default

    Quote Originally Posted by smorovic View Post
    Wow, this is in two years. Is it really going to take this long to migrate? I'd say a few months should be enough to get it done. And they basically have most of the work already done in Fedora and other systemd distributions.
    Again, "by" means "at the time between now and the date mentioned", so if things go extremely well it could even be in 14.10.

  8. #8
    Join Date
    May 2010
    Posts
    159

    Default

    Quote Originally Posted by pdffs View Post
    The link to the session notes points back to the Phoronix article.
    And the link still isn't fixed. Can anyone find the oeiginal link?

  9. #9
    Join Date
    Nov 2013
    Posts
    142

    Default

    Quote Originally Posted by smorovic View Post
    Wow, this is in two years. Is it really going to take this long to migrate? I'd say a few months should be enough to get it done. And they basically have most of the work already done in Fedora and other systemd distributions.
    They're waiting for Debian to do the job, so that they can copy/paste it

  10. #10
    Join Date
    May 2013
    Posts
    477

    Default Let's just hope they get the migration path right.

    Quote Originally Posted by Spittie View Post
    They're waiting for Debian to do the job, so that they can copy/paste it
    The real issue will be figuring out the migration path for those who are not reinstalling. This probably means some way of ensuring that packages that are started by Upstart still work until they get updated. Fortunately most top level apps (seemingly ALL that I have) do not install files in /etc/init with Upstart, thus should be init system agnostic.

    It's system packages that will be the issue here, all the DE's will need to cope with this at the same time. Fortunately it seems that the display managers handle them, and once lightdm/gdm/kdm/whatever is opened by init the DE's don't seem to rely on the init system any further, I've got Cinnamon, gnome-shell, IceWM, and KDE all installed, and don't see anything in /etc/init that appears to be from any of them.

    If things get ugly, an upstart compatability job like the currents sysVinit compatability job might be a workaround, but the now global Linux transition to systemd should put pressure on system software developers to get off Upstart fast once it is deprecated.

    If they do this right, it should be possible to pin the init system when the changes begin, unpin it when the system packages that are started by init are ready, and get an upgrade that works. Certainly I would take a fresh OS snapshot (a dd copy of the root partition) just before starting an init system changeover.

    I will have to learn enough about sytemd myself to rewrite my boot message scripts that give notice in Plymouth of disk mounting events. Right now they are Upstart conf files in /etc/init. SysVinit can't do the same job as it does not respond to external events, I will need a way to write the files for systemd to detect mounting of a disk and run plymouth-message

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •