summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--hurd/ng.mdwn6
-rw-r--r--microkernel/mach/history.mdwn2
-rw-r--r--open_issues/Upstart.mdwn61
3 files changed, 65 insertions, 4 deletions
diff --git a/hurd/ng.mdwn b/hurd/ng.mdwn
index fbebb137..d9287c3d 100644
--- a/hurd/ng.mdwn
+++ b/hurd/ng.mdwn
@@ -82,9 +82,9 @@ _please move me somewhere better! [[SamMason]]_
Summaries should obey the following structure:
* if there is a consensus, it is clearly described
-* if controversial points remain, there are also described after the consenus
-* if no choice has been clearly made, all valid positions are descrbied
-* withdrawed and invalid positions (prooved wrong, unrealistic, contradictory
+* if controversial points remain, there are also described after the consensus
+* if no choice has been clearly made, all valid positions are described
+* withdrawn and invalid positions (proved wrong, unrealistic, contradictory
to some design principle, etc.) should be described only very briefly, and
developed in a separate article
diff --git a/microkernel/mach/history.mdwn b/microkernel/mach/history.mdwn
index ce455627..62bd3e34 100644
--- a/microkernel/mach/history.mdwn
+++ b/microkernel/mach/history.mdwn
@@ -72,7 +72,7 @@ IRC, freenode, #hurd, 2012-08-29:
could be https://ssl.apple.com/science/profiles/cornell
<pavlx> the old one was
http://www.apple.com/macosx/technologies/darwin.html
- <pavlx> the link to Darwin is changed i suppose that the nw one it's
+ <pavlx> the link to Darwin is changed i suppose that the new one it's
https://ssl.apple.com/science/profiles/cornell
<pavlx> and the link to Kern Programming it's
https://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/KernelProgramming/About/About.html
diff --git a/open_issues/Upstart.mdwn b/open_issues/Upstart.mdwn
new file mode 100644
index 00000000..49e48403
--- /dev/null
+++ b/open_issues/Upstart.mdwn
@@ -0,0 +1,61 @@
+[[!meta copyright="Copyright © 2013 Free Software Foundation, Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+Upstart is an event based init system that is GPL licensed, however upstream
+contributions are under a CLA that permits proprietary relicensing.
+
+As of Jan 2 2013, Debian is considering adopting Upstart as an init system on
+GNU/Linux, and on GNU/kFreeBSD when the port to kFreeBSD is finished.
+
+The following are the words of Colin Watson on the debian-ctte@lists.debian.org
+mailing list and list the requirements of a potential HURD port:
+
+>I haven't looked at this in much detail, and I suspect Dimitri hasn't
+yet although IIRC he did express some interest in doing so. But I
+haven't seen anyone else try to outline the scope of a port, so let me
+try to do so for the sake of general understanding. As far as I know,
+the hardest parts would be inotify, ptrace, and prctl
+(PR_SET_CHILD_SUBREAPER).
+
+>inotify is used to notice changes to configuration files. This is
+certainly helpful for users, but it isn't critical as "initctl
+reload-configuration" works without it. We could probably do without
+this with the aid of a dpkg trigger.
+
+>ptrace is used for "expect fork" and "expect daemon"; as I indicated in
+another post, I think it would be preferable to avoid these in Debian
+and quite possibly to compile them out. (This would mean we wouldn't be
+able to translate Ubuntu jobs quite as directly, and a number of
+important jobs would definitely need to be changed, but the conversion
+isn't usually particularly difficult.)
+
+>prctl (PR_SET_CHILD_SUBREAPER) is used to make SIGCHLD notification work
+properly when Upstart is supervising a user session. This isn't a
+required feature and could easily be compiled out until suitable kernel
+support is available (this actually seems like the sort of thing that
+could be done in the Hurd without too much difficulty, but I haven't
+looked into it). If absent, it might well impede the ability to do an
+advanced desktop port, but it wouldn't get in the way of porting the
+bulk of services.
+
+>There might also be odds and ends around the details of wait status
+handling.
+
+inotify seems to be a feature that is often used in GNU/Linux programs, and
+implementing the feature in the HURD seems like a better and more rewarding
+option than porting the code in Upstart.
+
+Although many daemons double fork, that behavior seems to be dying out, and
+one can comfortably ignore the "expect fork/daemon" functionality of Upstart
+(and compile it out).
+
+[[!inline pages=tag raw=yes feeds=no]]
+
+[[!tag open_issue_porting]]