Upstart (software) explained

Upstart
Author:Scott James Remnant
Developer:Canonical Ltd.
Discontinued:yes
Latest Release Version:1.13.2[1]
Programming Language:C
Operating System:Linux
Genre:Init daemon
License:GPLv2

Upstart is a discontinued event-based replacement for the traditional init daemon—the method by which several Unix-like computer operating systems perform tasks when the computer is started. It was written by Scott James Remnant, a former employee of Canonical Ltd. In 2014, Upstart was placed in maintenance mode, and other init daemons, such as systemd, were recommended in place of Upstart. Ubuntu moved away from Upstart with the release of version 15.04 (Vivid Vervet) in favor of migrating to systemd. As of June 2024, there have been no updates released for Upstart since September 2014.[2]

Rationale

The traditional init process was originally only responsible for bringing the computer into a normal running state after power-on, or gracefully shutting down services prior to shutdown. As a result, the design is strictly synchronous, blocking future tasks until the current one has completed. Its tasks must also be defined in advance, as they are limited to this prep or cleanup function. This leaves it unable to handle various non-startup-tasks on a modern desktop computer elegantly, including:

Upstart's event-driven model allows it to respond to events asynchronously as they are generated.[3]

Design

Upstart operates asynchronously; it handles starting of the tasks and services during boot and stopping them during shutdown, and also supervises the tasks and services while the system is running.

Easy transition and perfect backward compatibility with sysvinit were the explicit design goals; accordingly, Upstart can run unmodified sysvinit scripts. In this way it differs from most other init replacements (beside systemd and OpenRC), which usually assume and require complete transition to run properly, and do not support a mixed environment of traditional and new startup methods.

Upstart allows for extensions to its event model through the use of initctl to input custom, single events, or event bridges to integrate many or more-complicated events.[4] By default, Upstart includes bridges for socket, dbus, udev, file, and dconf events; additionally, more bridges are possible.[5]

Adoption

Linux distributions and other operating systems based on the Linux kernel which use Upstart as the default init system:

Linux distributions that support or have supported Upstart to some extent, but moved away since or no longer use it as their default init system:

The latest release was version 1.13 on July 11, 2014. Since December 2018 the project website says that Upstart is in maintenance mode only, and recommends other init systems, such as systemd.[9]

See also

External links

Notes and References

  1. Web site: 1.13.2 "It looks lush from the side" : Series 1.x : upstart . Launchpad. 2022-01-01.
  2. Web site: Upstart: Overview.
  3. Web site: Upstart in Universe . Scott James . Remnant . Netsplit . 2006-08-26 . 2009-09-12. https://web.archive.org/web/20131113012410/http://netsplit.com/2006/08/26/upstart-in-universe/. 2013-11-13.
  4. Web site: The Upstart Cookbook: initctl emit . Canonical . 26 January 2014.
  5. Web site: The Upstart Cookbook: Bridges . Canonical . 26 January 2014.
  6. Web site: Shuttleworth . Mark . Losing graciously . 14 February 2014 . live . https://web.archive.org/web/20140322130122/http://www.markshuttleworth.com/archives/1316 . 22 March 2014 .
  7. Web site: Fedora defers systemd to F15 . 2010-09-14 . 2010-09-17 . Linux Weekly News.
  8. Web site: Deployment . . Red Hat Enterprise Linux 6: Technical Notes . 2013-12-31.
  9. Web site: Archive of upstart.ubuntu.com on Dec 30, 2018. https://web.archive.org/web/20181230204902/http://upstart.ubuntu.com/. 2018-12-30. live.