/srv/irclogs.ubuntu.com/2009/02/12/#upstart.txt

nteonis it safe to say that the stuff in utils/ directory is depreciated and unmaintained?00:00
Keybukno00:13
Keybuknot at all00:13
sadmacKeybuk: anything else in libnih/upstart need some code love?00:20
Keybuksadmac: haven't merged my stuff from the last week or two back in yet00:22
sadmacKeybuk: what are we keeping for 0.10? RH is going to need init to do SELinux, and I'm wondering if that's worth doing now.00:23
Keybukwhy do you need init to do it?00:23
Keybukyou can set the policy in the initramfs00:24
sadmacthat's what we're doing now.00:24
sadmacthere's push to move it back though.00:24
KeybukI'm not going to have a "drop everything" flag day like we did 0.3->0.500:25
Keybukevery thing in 0.5 today will be in 0.10, or will be gradually changed00:25
sadmacthat's good to know.00:27
Keybuktimetable's been pushed up a bit too00:27
sadmacoh?00:27
KeybukI'm probably going to be working full-time on Upstart from a week or two's time through to June00:28
Keybukrather than later00:28
Keybukhttp://people.ubuntu.com/~scott/stig-20090208-0940.png00:29
Keybuk(my first attempt at a native Upstart boot)00:29
sadmac18s. Too slow.00:29
sadmac:D00:29
Keybukno00:29
Keybukyou're mis-reading the chart00:29
Keybukit's 8.5s00:29
sadmacyou did early login?00:30
Keybukeverything after that is me getting a terminal opening, and fumbling to stop the bootchart collector ;)00:30
sadmacoh00:30
Keybukno, that's all-up00:30
KeybukX in 3s00:30
sadmacIf the service management stuff is stable enough (and why wouldn't it be) I'm pretty sure I can write some decent dynamic ionice stuff that'd make early login work well.00:31
Keybukdefine "early login" ?00:31
sadmacpopping up gdm before we've loaded everything (in the event driven sense: before the running set has stabilized)00:32
Keybukthat's bringing up gdm once its dependencies are met00:33
Keybukmaybe that's the same thing?00:33
ion_keybuk: CoolĂ—2 (the timetable and the native boot) :-)00:33
Keybukif you installed other services like apache, they'd start up about the same time00:33
sadmacKeybuk: its that + not making gdm depend on some "the system is done booting" trigger00:33
Keybukoh, there's no such thing00:34
sadmacKeybuk: right00:34
Keybukgdm depends on d-bus, and /usr being mounted00:34
sadmacKeybuk: doing anything /but/ early login is a pain in the ass now.00:34
Keybukhal is system-bus activated00:34
Keybukand depends on acpid00:34
Keybuk(so X blocks on it)00:34
Keybukalso depends on d-bus and udev00:35
sadmacKeybuk: so the idea of this would be that upstart could be set in a kind of "background mode" such that when a new service's goal changed, it would be ioniced into the "idle" class. It would be ioniced back into the class specified by its configuration (or the default) when it reached the "started" or "stopped" states.00:36
ion_And this would be done to ~everything else than the services that lead to gdm getting started?00:38
sadmacion_: it would be turned off until gdm was started00:39
sadmacion_: the idea is "get non-interactive stuff out of the way of the user"00:39
ion_Ah00:39
nteonsadmac: I've been looking into upstart in Fedora CVS.  the devel branch doesn't seem to be building (missing dbus-devel as a BuildDep), and I was wondering if it was that or some other reason rawhide is using upstart 0.3.9 from F1000:57
nteonsadmac: (im looking to get some rawhide builds working on my OLPC XO)00:58
sadmacnteon: we aren't going to 0.5.100:58
sadmacnteon: neither is ubuntu.00:58
sadmacnteon: next release shipped by any major distro (afaik) will be 0.1000:58
nteonsadmac: good to know, thanks :)01:01
nteonI suppose I can stop trying to get my rawhide box booting with 0.5.1...01:01
sadmacheh01:06
nteonaround when is 0.10 expected to come out?01:09
sadmacnteon: in time for the next Ubuntu release... damned if I can remember all the dates01:09
sadmacshould be F12 material01:09
nteonsadmac: sounds good01:23
nteonsadmac: I'm cautiously interested in getting more involved in Fedora development, so if theres anything I can do to help with upstart packaging or patching, let me know (not that I'm intimately familiar with the codebase or anything)01:25
sadmac_Keybuk: did you go back to a custom control protocol for initctl?06:06
sadmac_Keybuk: there's no reference to dbus in initctl in trunk06:06
=== sadmac_ is now known as sadmac
mbieblsadmac: SUBDIRS = m4 intl nih nih-dbus dbus init doc po # util 08:08
mbieblutil/ in trunk isn't ported (yet) afaics08:09
keesjwhat would be the right place to increase the timeout between initctl and upstart?10:27
keesjwe lost a lot of functionality while swichting to dbus10:42
keesjwhile adding more code :p10:42
keesjand dependencies10:43
keesjI hope there will be something in return10:44
ion_More secure IPC. Upstart can determine when a service is running based on when it appears on D-Bus.10:52
keesjis there kerberdos support in dbus. otherwise i don't why it's more secure11:12
ion_More eyes looking at the networking code.11:12
ion_Especially relevant when normal users gain access to Upstart.11:13
keesjI see. 11:14
keesjI did not look at how a user is stopped from sending events yet11:14
ion_Also, the D-Bus dependency should be a non-issue in most places. For an embedded system with no need for IPC and extremely limited resources, perhaps the D-Bus code can be even disabled. If not yet, the one needing it is free to share a patch. :-)11:16
keesjmy kind of patches and ideas generaly don't get accepted in upstart.11:17
keesjBADCODE i guess11:18
Keybuksadmac2: 0.5 is the current branch14:08
KeybukI haven't ported the util stuff over yet14:09
sadmac2Keybuk: ah15:42

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!