Systemd For The Ubuntu Server Gets Discussed

[phoronix]

Phoronix: Systemd For The Ubuntu Server Gets Discussed

Besides figuring out SSD caching and other features for Ubuntu Server 14.10, developers at Canonical and other stakeholders are figuring out Ubuntu Server's future with systemd in the long-term...

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

[rgloor]

canonical ....and again

again....

....canonical tried to run their own show (with their own Upstart init system) and to CONTROL ALL themself, rather than to co-work with the community on the other init systems.

....and now, since nobody else wanted to blindly adapt their upstart, they now dump it and grab the work of all the others, which were co-working in/with the community on systemd.


The same happened with the graphical subsystem.
AGAIN, they did not want to co-work on the Wayland system. A system nota bene, THEY put in the spot light by announcing to be the future canonical graphical subsystem.
But again, they were not prepared to participate in the community and started another canonical-only graphical subsystem, MIR.
So how long will it take, until the same happens to the graphical subsystem?
I guess in a few years, canonical will also drop their MIR server and take over the matured Wayland graphical subsystem, meanwhile improved by all the others from the community.
And all the effort on MIR will be flashed. Like it now is happening with Upstart.


I wished, canonical would learn from their own mistakes and returns to be a good player in the community of OSS. Participating in the community work and accept features and directions, not (purely) invented at canonical.

[TheBlackCat]

...and returns to be a good player in the community of OSS. Participating in the community work and accept features and directions, not (purely) invented at canonical.

When did they do that in the past?

[r_a_trip]

....canonical tried to run their own show (with their own Upstart init system) and to CONTROL ALL themself, rather than to co-work with the community on the other init systems.

To be fair to Canonical, Upstart predates systemd by several years. Upstart even was part of RHEL 6, before Red Hat became interested in systemd. So it's the other way around this time. Kay and Lennart looked at upstart and decided starting from scratch was a better thing to do.

Although I agree with your prediction that Canonical will switch to Wayland (once Debian decides that X11 doesn't cut it anymore). Since Mir is not only a display server, but also a compositor, I expect Canonical to refactor Mir with a Wayland back-end.

[oleid]

Kay and Lennart looked at upstart and decided starting from scratch was a better thing to do.

Not only that. At least Lennart contributed to upstart for some time, until he realized, that what they wanted to do was not possible within upstart.

[andydread]

again....

....canonical tried to run their own show (with their own Upstart init system) and to CONTROL ALL themself, rather than to co-work with the community on the other init systems.

....and now, since nobody else wanted to blindly adapt their upstart, they now dump it and grab the work of all the others, which were co-working in/with the community on systemd.


The same happened with the graphical subsystem.
AGAIN, they did not want to co-work on the Wayland system. A system nota bene, THEY put in the spot light by announcing to be the future canonical graphical subsystem.
But again, they were not prepared to participate in the community and started another canonical-only graphical subsystem, MIR.
So how long will it take, until the same happens to the graphical subsystem?
I guess in a few years, canonical will also drop their MIR server and take over the matured Wayland graphical subsystem, meanwhile improved by all the others from the community.
And all the effort on MIR will be flashed. Like it now is happening with Upstart.


I wished, canonical would learn from their own mistakes and returns to be a good player in the community of OSS. Participating in the community work and accept features and directions, not (purely) invented at canonical.

Seriously. Who appointed you spokesman/dictator for the community. And what community? Give us all a break. You dictate that people shoudn't write their own code then claim people are grabbing other people's code. Are you 12? Here's a clue. When it comes to open source, people can write what ever the hell code they want and give it away to anyone at anytime as they chose. Also people can use each other's code based on the license of such code. Claiming people should just "co-work" or whatver is great prognostication, however in real life I can't just join your project and add a bunch of features that will suit me and expect you to accept them. If that were the case their would be one distro, one DE, one kernel, one filesystem, one system init, and on and on. There are endless examples of people trying to submit features to gnome for instance and have been told to go pound sand. Or just plain old "NO" with no explanation. Just grow up already.

[blackout23]

Not only that. At least Lennart contributed to upstart for some time, until he realized, that what they wanted to do was not possible within upstart.

No they wanted to contribute but couldn't because of the CLA.

[bkor]

....canonical tried to run their own show (with their own Upstart init system) and to CONTROL ALL themself, rather than to co-work with the community on the other init systems.

Nothing wrong with Upstart when it was created. Though their insistence on the CLA was quite annoying. Fedora adopted it, as well as RHEL6 (though hardly noticeable / only the basics). Mir is IMO not the same situation.

[Stellarwind]

The need Mir now for Ubuntu phone primarily and if it starts to get traction, they'll keep working on Mir.
Jolla won't release their full source either.

[Alliancemd]

Re

again....

....canonical tried to run their own show (with their own Upstart init system) and to CONTROL ALL themself, rather than to co-work with the community on the other init systems.

....and now, since nobody else wanted to blindly adapt their upstart, they now dump it and grab the work of all the others, which were co-working in/with the community on systemd.


The same happened with the graphical subsystem.
AGAIN, they did not want to co-work on the Wayland system. A system nota bene, THEY put in the spot light by announcing to be the future canonical graphical subsystem.
But again, they were not prepared to participate in the community and started another canonical-only graphical subsystem, MIR.
So how long will it take, until the same happens to the graphical subsystem?
I guess in a few years, canonical will also drop their MIR server and take over the matured Wayland graphical subsystem, meanwhile improved by all the others from the community.
And all the effort on MIR will be flashed. Like it now is happening with Upstart.


I wished, canonical would learn from their own mistakes and returns to be a good player in the community of OSS. Participating in the community work and accept features and directions, not (purely) invented at canonical.

Upstart was started way before systemd, it was the best solution at the time... It's not like systemd was there already...
Mir is absolutely another story... Really crappy software and if they would of not received feedback from the Wayland developers they would of been sh*ting themselves right now... The input system was fked up btw, they would of worked at it for a long time and then realize that they have to rewrite everything, they are lucky they received help(advices) from the Wayland developers...