Bug 6865

Summary:	Upstart 1.5
Product:	Mageia	Reporter:	Anderson Carvalho <frateraec>
Component:	New RPM package request	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	Low	CC:	mageia, mageia, olav
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Anderson Carvalho 2012-07-25 03:00:49 CEST

Upstart is an event-based replacement for the /sbin/init daemon which handles starting of tasks and services during boot, stopping them during shutdown and supervising them while the system is running.

It was originally developed for the Ubuntu distribution, but is intended to be suitable for deployment in all Linux distributions as a replacement for the venerable System-V init.

Feature Highlights

Tasks and Services are started and stopped by events
Events are generated as tasks and services are started and stopped
Events may be received from any other process on the system
Services may be respawned if they die unexpectedly
Supervision and respawning of daemons which separate from their parent process
Communication with the init daemon over D-Bus

http://upstart.ubuntu.com/download/1.5/upstart-1.5.tar.gz

Release notes: https://launchpad.net/upstart/1.x/1.5

Comment 1 Sander Lepik 2012-07-25 08:35:57 CEST

We don't add new packages to stable version of Mageia. I'll change version to cauldron. But it's *very* unlikely that someone will implement it - we have no resources to support two init systems at the same time.

Priority: Normal => Low
CC: (none) => sander.lepik
Version: 2 => Cauldron
Severity: normal => enhancement

Comment 2 Anderson Carvalho 2012-07-25 12:14:49 CEST

I understand that although Mageia is growing are still few developers to contribute. However you have changed to systemd, mandriva and fedora as well, but is not yet integrated with systemd control center Mageia and I want to find alternatives. 
Mandriva still maintains a version of upstart that tested in mageia, however is an old version.
http://mirror.yandex.ru/mandriva/devel/cooker/SRPMS/contrib/release/upstart-0.6.3-1mdv2011.0.src.rpm

Mageia is more friendly distro there is, but news like systemd that are not quite ready just bring complications for the home user.

Comment 3 Olav Vitters 2012-07-25 14:29:43 CEST

This is pretty much a cannotfix/wontfix.

We've removed support for sysvinit. Various packages now rely on systemd features. Supporting another init system means loads of work, little benefit.

CC: (none) => mageia, olav

Comment 4 Olav Vitters 2012-07-25 14:34:13 CEST

Ok, seems you're just having issues with systemd.

Switching init systems because the current one has a bug just means you'll have way more bugs in the new init system.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Comment 5 Colin Guthrie 2012-07-25 14:44:27 CEST

Yup WONTFIX.

Upstart is broken by design. The problems you've mentioned regarding systemd are basically ones where problems exist in individual packages not having properly integrated native support for systemd units (e.g. the TOR example). This would be exactly the same problem with any new init system, so you do not solve anything, but instead integrate much more in the way of problems and hassle to support (e.g. we'd need to write a new backend for drakxservices to support systemd and upstart).

Besides, systemd has massive, cross-distro support including from the server, desktop and embedded circles. IMO it's purely political, not technical, reasons that Canonical still pushes on with upstart support. I believe this will eventually change once they get over themselves.

Additionally statements like "news like systemd that are not quite ready just bring complications for the home user" are equally invalid. I appreciate there are some problems but the statement would be better written as "news like a new init system that is not fully integrated in every package just bring complications for the home user". Adding another init system will make things significantly worse and make our jobs significantly harder.

So apologies for this, but I think you're making a huuuuge leap when you encounter relatively minor integration issues and feel the solution is a whole new init system....