Systemd discussion - during the V cycle

[QDR06VV9]

Why will it be taken away? Because you like me just jump from one developmental version to the next? We can still test the next Mate version of Wascally Wabbit.

Yep just like you I jump from cycle to cycle.
But I too run Three 14.04 LTS Os's
Plus I'm sure you have seen this already

As stated on the mailing list few months ago (https://lists.ubuntu.com/archives/ub...er/015154.html),
Ubuntu never offered a choice of init system, and won't start doing that. systemd is mandatory to be the supported ubuntu path. That's the reason
why ubuntu-standard won't depend on systemd|upstart.
Note that for some kernel reasons, the Touch image is still using upstart, but that will change in the future.

Plus This link to confirm https://lists.ubuntu.com/archives/ub...er/015154.html

I wish I could get you to try https://launchpad.net/~mamarley/+archive/ubuntu/nvidia
Try it You'll Like it

[Cavsfan]

Yep just like you I jump from cycle to cycle.
But I too run Three 14.04 LTS Os's
Plus I'm sure you have seen this already

As stated on the mailing list few months ago (https://lists.ubuntu.com/archives/ub...er/015154.html),
Ubuntu never offered a choice of init system, and won't start doing that. systemd is mandatory to be the supported ubuntu path. That's the reason
why ubuntu-standard won't depend on systemd|upstart.
Note that for some kernel reasons, the Touch image is still using upstart, but that will change in the future.

Plus This link to confirm https://lists.ubuntu.com/archives/ub...er/015154.html

I wish I could get you to try https://launchpad.net/~mamarley/+archive/ubuntu/nvidia
Try it You'll Like it

I had not seen that. All I ever heard was that upstart would be available until about 16.04 or 16.10 or something like that when they cut the cord but I guess on most of the flavors the cord was just cut.
Systemd works great here. Upstart is not worth messing with and I don't care to invest the time that it would take to get it working properly. I'll just use systemd.

I believe it's only available on vanilla Ubuntu and Xubuntu but I haven't, nor do I care to at this point peruse the manifests of all the flavors again.

My nVidia card is pretty old now and it won't hold up to the new driver versions any more.

I remember back on Lucid Lynx I was able to install the most latest driver directly from nVidia's website but not any more.

I also haven't been able to update the driver on my windows 7 install in a few years either. Every time I did I would have to roll it back.

Here's what I have on all my systems I believe it is all of them anyway.

cavsfan@cavsfan-MS-7529:~$ dpkg -l |grep nvidia
ii  nvidia-304-updates                          304.125-0ubuntu2                           amd64        NVIDIA legacy binary driver - version 304.125
ii  nvidia-libopencl1-304-updates               304.125-0ubuntu2                           amd64        NVIDIA OpenCL Driver and ICD Loader library
ii  nvidia-opencl-icd-304-updates               304.125-0ubuntu2                           amd64        NVIDIA OpenCL ICD
ii  nvidia-settings                             346.59-0ubuntu1                            amd64        Tool for configuring the NVIDIA graphics driver

I'll probably hold out a while on jumping into the next developmental version though. Will have to wait and see.

[Mateusz Stachowski]

In blueprints created for Vivid (15.04) there is this:

https://blueprints.launchpad.net/ubu...emd-transition

* Target for 16.04 LTS is to support upstart as a helper init for compatibility with locally-installed jobs

and this

https://blueprints.launchpad.net/ubu...temd-migration

automatic fallback to upstart in grub (additional boot flag/checkpoint): TODO

Besides that in the Bug #1427654 "FFE: switch system init to systemd [not touch] in 15.04" you can read:

As per https://blueprints.launchpad.net/ubu...temd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle.

https://blueprints.launchpad.net/ubu...temd-migration

Also there is the init package which is essential and depends on systemd-sysv or upstart-sysv.

http://packages.ubuntu.com/vivid/init

[Cavsfan]

Admins, could you create a thread for the w cycle?

All I had in Vivid was systemd and now I have both and I see what you all were saying about the slowness in systemd.

[slickymaster]

Admins, could you create a thread for the w cycle?

All I had in Vivid was systemd and now I have both and I see what you all were saying about the slowness in systemd.

Here you go: http://ubuntuforums.org/showthread.php?t=2277355

And being so, I'm closing this one.