JamesHunt

Differences between revisions 22 and 23
Revision 22 as of 2012-12-11 19:37:10
Size: 5678
Editor: host-92-18-11-100
Comment:
Revision 23 as of 2013-03-27 09:45:27
Size: 5783
Editor: host-92-18-40-67
Comment:
Deletions are marked like this. Additions are marked like this.
Line 24: Line 24:
   * Wrote `upstart-monitor` GUI/CLI tool.
   * Wrote `upstart-file-bridge`.
   * Landed Upstart 1.8.

Summary

My name is James Hunt, and I work for Canonical as a member of the FoundationsTeam working on Upstart and other early-boot and plumbing technologies.

Info

Specs

Contributions

Raring (19/10/2012-24/04/2013)

  • Upstart
    • Landed Stateful re-exec feature (Upstart 1.6.1).
    • Wrote spec for Enhanced User Sessions.

    • Wrote upstart-monitor GUI/CLI tool.

    • Wrote upstart-file-bridge.

    • Landed Upstart 1.8.
  • Misc
    • Wrote utfout utility, now in Debian and Ubuntu archives.

    • Wrote procenv utility, (currently in Debian New queue).

Quantal (27/04/2012-18/10/2012)

  • Upstart
    • "stateful re-exec" feature.
      • Wrote spec for Stateful Re-exec.

      • Code completed but not landed in Quantal since tests not finished.

Precise (20/10/2011-26/04/2012)

  • Upstart
    • "console log" facility allowing job output to be logged (bug 328881)

    • Default console value of "log" so all job output logged by default.

      • (has already found some long-standing bugs in other packages since errors are now visible!)
    • "initctl notify-disk-writeable" facility to allow jobs *ending* before the disk becomes writeable to be logged

      • (this even works for jobs which "start on startup").

    • User job logging
      • (totally different design to system job logging for performance and security reasons. Not yet available).
    • Enhanced Upstart test framework in NIH library.
    • Detailed Upstart Release Notes covering Oneiric->Precise and Lucid->Precise upgrades.

Oneiric (05/05/2011-13/10/2011)

Natty (25/10/2010-28/04/2011)

Significant Bugs

  • Bug 876626: A nasty security bug caused by a small behavioural change (which itself had been introduced to make the boot more robust).

  • Bug 553745: The infamous plymouth SIGSEGV bug had been open for over 2 years and took a significant amount of effort to identify the fix. With 270 duplicates, it even put launchpad under strain: if the main bug links hangs/fails (due to all those duplicates (Bug 839141)), try the text view.

  • Bug 771372: Required taking a holistic approach and seeing the real problem, not just patching the very particular problem reported.

  • Bug 829980: Required tracing the problem through Upstart's udev bridge, D-Bus, udev and the kernel. Identified fact that udev is not fully specified (precise format of data is not defined).

  • Bug 912558: Worked closely with Daviey and community members on this "Critical" bug to identify the problem (rather a bizarre one which proved difficult to track down!) and find a fix.

Applications

Contact


CategoryHomepage

JamesHunt (last edited 2015-06-11 18:58:11 by host-92-22-81-227)