[12:53] <mdales> morning
[12:53] <mdales> what's the last moment I can have a job stop on shutdown on an ubuntu system? would it be on stopped rc0?
[13:56] <ion_> http://ircimg.org/img/15762.gif
[14:05] <quitte> hi. is upstart usable without sysvinit compatibility? is there a way to shutdown or reboot the system without sysvinit compatibility?
[15:01] <quitte> couldsomeone hit me with a cluebat? I'm looking at /etc/rc0.d/S90halt. I thought that S meant start the script. but for start this script is a noop?
[15:03] <mdales> quitte: read http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit
[15:03] <mdales> IIRC all scripts in rc0.d are sent stop, not matter what their name
[15:06] <quitte> right. thanks. I fail to see why that is done,though.
[15:07] <quitte> does ubuntu have any more scripts in event.d than the ones directly linked from the upstart.ubuntu.com page?
[15:10] <mdales> quitte: pass
[15:11] <mdales> quitte: I'm new to it all too, I just thought you mgiht find that info helpful
[15:12] <quitte> yes. it definately was. I'm new to it myself. as it seems to be quite easy to write event scripts and found upstart in experimental I thought I might finally giveit a try.
[15:12] <mdales> morning Keybuk 
[15:17] <quitte> of course I immediately got stuck. Are there any plans about handling filesystems? It'd be nice if upstart were looking for both the device and the mountpoint. and as soon as both exist mounts the filesystem.  
[15:17] <Keybuk> hey
[15:21] <Keybuk> quitte: we're still working on a lot of the ideas for that kind of thing
[15:22] <Keybuk> Upstart is still very much in development
[15:22] <mdales> but is already pretty spiffy
[15:22] <mdales> :)
[15:24] <quitte> yes. the ideas are great. unfortunately it sounds as if it wasn'T complete eough to be a full sysvinit replacemet even for embedded devices with a very limit set of services
[15:24] <Keybuk> it can replace sysvinit
[15:24] <Keybuk> but it can't yet replace sysv-rc
[15:24] <quitte> but I bet I'd have equal trouble with launchd
[15:24] <Keybuk> many people confuse the two
[15:25] <quitte> ah. I did, too
[15:25] <Keybuk> it has all of the features of the sysv init daemon
[15:25] <Keybuk> but does not yet have the ability to order the starting of tasks and services
[15:25] <Keybuk> so you still need something like sysv-rc
[15:25] <Keybuk> (ie the /etc/rc?.d directories)
[15:27] <quitte> meh. well I guess I could use a single eventfile for every filesystem until you guyscome up with a solution.
[15:28] <quitte> are subdirectories supported to group the files?
[15:29] <Keybuk> yes
[15:29] <Keybuk> you could always help with the solution ;)
[15:31] <quitte> I could make it print hello world on the screen and even make it as for your name
[15:51] <quitte> hmm. waiting for a file to exist isn't possible, yet?
[15:54] <Keybuk> right
[15:58] <quitte> :( I shouldn'T have watched the launchd techtalk. 
[16:08] <Keybuk> oh?
[16:08] <Keybuk> I haven't seen that?
[16:08] <Keybuk> is it new?
[16:11] <quitte> no. 20.7.
 15:25:33> +but does not yet have the ability to order the starting of tasks and services << i've done it ;)
[16:24] <AlexExtreme> although in a pretty hackish way
[16:24] <AlexExtreme> and no event based mounting/networking etc
[16:24] <Keybuk> how did you do it?
[16:25] <AlexExtreme> wait, do you mean just convert to a native upstart bootup without sysvinit scripts, or something else?
[16:25] <Keybuk> yes
[16:26] <AlexExtreme> yes to which one?
[16:26] <Keybuk> the first one
[16:26] <AlexExtreme> didn't you see what I did for frugalware?
[16:26] <Keybuk> no...
[16:26] <Keybuk> or I did, and I forgot
[16:27] <AlexExtreme> let me find it
[16:28] <AlexExtreme> http://ftp.frugalware.org/pub/other/upstart-jobs/upstart-jobs/
[16:28] <AlexExtreme> that's the base jobs, there's some stuff elsewhere for other packages like dbus and friends, which I can't find
[16:41] <Keybuk> you're using a single mount script?
[16:42] <AlexExtreme> yes, as far as I can tell there isn't a good way to do it better, atm
[16:42] <AlexExtreme> which is why I said it's a bit hackish
[16:47] <Keybuk> *nods*
[16:48] <AlexExtreme> but, i probably won't work on that anymore, seeing as I no longer develop for frugalware ;)
[16:49] <Keybuk> oh, how comes?
[16:50] <AlexExtreme> you forget stuff, i told you a while ago
[16:50] <AlexExtreme> i wanted to work on my own projects a bit more, plus I have a lot of school work these days, so I don't get a lot of time for other stuff
[16:53] <AlexExtreme> plus it annoyed me a little that they were so concerned about dumb little things like how the output of the bootup looked (that dodgy "initmsg" stuff in the jobs I linked before)
[16:54] <AlexExtreme> i mean, it's ok to make it look "friendly", but they were more concerned about it than it actually working...
[16:54] <AlexExtreme> anyway, </rant> ;)
[19:18] <quitte> Keybuk: I just read th states blueprint and I may have a suggstion. wouldn't it make sense to have every event result in a state? for example events.d/hostname was successfully executed resultsin a state hostname is set?
[19:20] <quitte> also if changing /etc/hostname caused an event that events.d/hostname registered for the hostname could be changed by just changing the file