[17:35] <Keybuk> mbiebl: of course, I keep forgetting when talking to Debian, that they're not actually programmers
[17:39] <mbiebl> w.r.t to startpar, you say?
[17:40] <mbiebl> maybe I'm just missing the context :-)
[18:15] <sadmac2> Keybuk: this weekend once I finish the tests for the state transfer patch, I'm going to try making 0.6 queue start/stop calls along with events
[18:21] <Keybuk> sadmac2: shiny
[18:22] <sadmac2> Keybuk: I try
[18:23] <sadmac2> Md: what is حَوّامتي مُمْتِلئة بِأَنْقَلَيْسون
[20:05] <Keybuk> wow
[20:05] <Keybuk> "make all" works in trunk for the first time in ages ;)
[20:07] <sadmac2> whee
[20:11] <PovAddict> you think that's rare? maybe you need to set up a buildbot
[20:13] <Keybuk> PovAddict: I'm not sure how that would help, other than flagging that it doesn't actually build
[20:43] <mbiebl> \o/
[20:43] <sadmac2>  |
[20:43] <sadmac2> / \
[20:43] <mbiebl> nice
[20:44] <sadmac2> mbiebl: why are we celebrating?
[20:44] <mbiebl> [21:05:27] <Keybuk> "make all" works in trunk for the first time in ages ;)
[20:45] <sadmac2> mbiebl: oh
[20:46] <mbiebl> Keybuk: does it only compile or actually boot ;-)
[20:47] <Keybuk> mbiebl: I haven't tested _that_ :)
[20:47] <Keybuk> I was being distracted by vim syntax highlight
[20:47] <mbiebl> oh
[20:48] <Keybuk> which doesn't work for me *cry*
[20:48] <mbiebl> are you using /etc/init/*.conf ?
[20:48] <Keybuk> I changed that bit
[20:49] <Keybuk> if I have a file loaded, how do I force vim to use upstart syntax for it
[20:49] <sadmac2> Keybuk: :source /path/to/upstart.vim methinks
[20:50] <mbiebl> set filetype=upstart
[20:50] <sadmac2> Keybuk: you're an emacs'er typically, aren't you?
[20:50] <Keybuk> yeah
[20:50] <sadmac2> Keybuk: ^^mbiebl has it right
[20:50] <Keybuk> mbiebl: I did that, and it turned off all the syntax highlighting ;)
[20:51] <mbiebl> Where did you install the upstart.syntax file into?
[20:51] <Keybuk> oh, I see
[20:51] <Keybuk> I'm an idiot
[20:51] <Keybuk> you called the file syntax_upstart.vim ;)
[20:51] <Keybuk> it needs to be upstart.vim in the syntax sub-directory
[20:51] <mbiebl> oh, yes
[20:52] <Keybuk> neat
[20:52] <mbiebl> I thought I had added that to the bug report
[20:52] <Keybuk> I probably didn't read it properly ;)
[20:54] <mbiebl> It needs a lot of polishing, but I wanted to wait with that, until the syntax format for 0.6 is finished.
[20:54] <mbiebl> It's actually a nice way to document all the keywords etc ;-)
[20:57] <mbiebl> time to run make: real	0m45.070s
[20:58] <mbiebl> time to run make check: real	10m35.532s
[20:58] <mbiebl> on my crappy laptop, i.e.
[21:02] <Keybuk> that's not bad
[21:02] <Keybuk> it passed then? :)
[21:02] <mbiebl> It did, yes
[21:04]  * sadmac2 wonders if make check is -j safe
[21:04] <Keybuk> sadmac2: don't think so
[21:05] <sadmac2> Keybuk: I'd imagine the dbus stuff would get hairy
[21:05] <Keybuk> though automake may not even allow that
[21:05] <Keybuk> it might build them in parallel but run them in series
[21:05] <Keybuk> indeed, that's exactly what it does ;)
[21:05] <Keybuk> so it's "safe" in the sense that it's ignored
[21:55] <sadmac2> Keybuk: I think in the future we shouldn't have dates in the code names. It confuses me.
[21:55] <sadmac2> I keep thinking its some other sort of information
[21:56] <Keybuk> heh
[21:56] <Keybuk> but it was the release date! :)
[21:56] <sadmac2> Keybuk: why were you John Masters?
[21:57] <sadmac2> (for who the Sega Master System is named btw. Fun fact)
[21:58] <Keybuk> do you not listen to the lkml summary podcast?
[21:59] <sadmac2> Keybuk: no. I subscribe to the list... I'm a little behind :P
[21:59] <Keybuk> pick one at random and listen for a few seconds
[21:59] <Keybuk> then you'll understand
[22:00] <sadmac2> cool
[22:00] <sadmac2> and now I go home
[22:33] <Keybuk> well, holy crap, it booted
[22:51] <mbiebl> Keybuk: can confirm
[22:51] <mbiebl> running it too ;-)
[22:51] <Keybuk> trunk?
[22:52] <mbiebl> yep
[22:52] <Keybuk> are you using the shiny new default jobs? :)
[22:52] <mbiebl> I do
[22:52] <mbiebl> runlevel handling is a bit broken
[22:53] <Keybuk> oh, what did you find?
[22:53] <mbiebl> when booted, runlevel should be "N 2"
[22:53] <mbiebl> not "S 2"
[22:53] <Keybuk> I think it should be S 2, no?
[22:53] <Keybuk> you've come from single-user mode into runlevel 2
[22:53] <mbiebl> no, don't think so
[22:54] <Keybuk> I know 0.3 said N 2
[22:54] <Keybuk> but I always thought that was a bug ;)
[22:54] <PovAddict> personally I wish Ubuntu packages used upstart events instead of init.d scripts :)
[22:54] <mbiebl> it's not like you stopped after rcS and then switched runlevel manually to 2
[22:55] <Keybuk> hmm maybe
[22:55] <mbiebl> otherwise, you have the problem that when you enter runlevel 2
[22:55] <Keybuk> just change the env RUNLEVEL= in rc-sysinit.conf
[22:55] <mbiebl> all stop links are executed
[22:55] <Keybuk> should be just
[22:55] <Keybuk> env RUNLEVEL=
[22:55] <Keybuk> ohhh
[22:55] <Keybuk> maybe it wasn't a bug then
[22:56] <mbiebl> e.g. I have apache and mysql installed, but disabled
[22:56] <mbiebl> and when entering runlevel two, those two are stopped first
[22:56] <mbiebl> before the actual boot continues
[22:57] <Keybuk> ok
[22:57] <Keybuk> I changed that
[22:57] <Keybuk> now when I boot into single-user mode first, it's
[22:57] <Keybuk> N S
[22:57] <Keybuk> (it was S S before, which I agree is a weeeee bit odd)
[22:57] <ion> ke230434  * sadmac2 wonders if make check is -j safe
[22:57] <mbiebl> N S for single user mode is correct I think
[22:57] <ion> .NOTPARALLEL: or something equivalent should be used if it’s not.
[22:58] <mbiebl> But I think, the rcS stage during boot shouldn't be considered "single user mode"
[22:58] <ion> (Now that i read further, “something equivalent” is done. :-P)
[22:58] <Keybuk> yeah, I mean with "single"
[22:58] <Keybuk> then when I go from single to multi-user (^D) I get S 2
[22:58] <mbiebl> that looks about right too
[22:59] <Keybuk> let's try booting straight into multi-user
[23:00] <Keybuk> now it's N 2
[23:00] <Keybuk> and the system boot record was still written \o/
[23:00] <mbiebl> cool
[23:01] <mbiebl> what I also find a bit weird, is that the jobs are actually named job.conf
[23:01] <Keybuk> sure
[23:01] <mbiebl> e.g. in status etc
[23:01] <mbiebl> hm
[23:01] <Keybuk> they are?
[23:01] <Keybuk> are you sure you installed the 0.6 util directory?
[23:02] <mbiebl> rc.conf stop/waiting
[23:02] <Keybuk> actually, that shouldn't make a difference
[23:02] <Keybuk> I see
[23:02] <mbiebl> etc
[23:02] <Keybuk> rc stop/waiting
[23:02] <Keybuk> which revno are you at? (upstart & libnih)
[23:02] <Keybuk> 1160 / 966 here
[23:02] <mbiebl> 1155/963
[23:03] <mbiebl> I guess it's time for an update then ;-)
[23:03] <Keybuk> oh, yeah
[23:03] <Keybuk> you're missing the revs that dealt with the .conf issue
[23:04] <Keybuk> 1161 has the rc-sysinit fix
[23:04] <mbiebl> compiling ...
[23:21] <ion> keybuk: How are you planning to handle mounting with 0.6 in karmic?
[23:21] <ion> I wish i had managed to write the mount daemon, but i haven’t.
[23:22] <Keybuk> by using a mount daemon :)
[23:22] <ion> :-)
[23:23] <ion> Any code yet?
[23:28] <Keybuk> no, that's my next thing to do really
[23:30] <mbiebl> Keybuk: noticed one more minor issue
[23:30] <mbiebl> when I use startpar, switching to runlevel 6/0 will also stop the service
[23:30] <mbiebl> which were already disabled in 2
[23:31] <mbiebl> for debugging, I added a pre-start script echo $(runlevel) end script to rc.conf
[23:31] <mbiebl> then this problem magically goes away
[23:34] <Keybuk> odd, why does it do that?
[23:35] <Keybuk> isn't echo $(runlevel) a little superfluous? :p
[23:35] <Keybuk> runlevel would be enough there <g
[23:35] <mbiebl> I actually have a simple runlevel call ;-)
[23:36] <mbiebl> just wanted to make it clear, that it's debugging output
[23:36] <mbiebl> /etc/init.d/rc uses the $runlevel and $prevlevel env variables
[23:36] <mbiebl> and passes that to startpar
[23:37] <Keybuk> it sets those from $RUNLEVEL and $PREVLEVEL though right?
[23:37] <mbiebl> checking...
[23:38] <mbiebl> runlevel=$RUNLEVEL
[23:38] <Keybuk> that should be set
[23:38] <mbiebl> previous=$PREVLEVEL
[23:38] <mbiebl> [ "$previous" = "" ] && previous=N
[23:39] <Keybuk> weird
[23:39] <Keybuk> set -x that script? :p
[23:40] <mbiebl> weird is, that simply calling runlevel magically "fixes" it
[23:41] <Keybuk> that is weird
[23:41] <Keybuk> runlevel doesn't do anything ;)
[23:49] <mbiebl> I added a runlevel to /etc/init.d/rc
[23:49] <mbiebl> (when runlevel and previous are set)
[23:49] <mbiebl> and on reboot it shows N 6 with startpar
[23:50] <mbiebl> but of course it should show 2 6
[23:51] <Keybuk> what does it show without startpar?
[23:51] <mbiebl> fwiw I also get an assertion error from this runlevel call, when it's called during rcS
[23:51] <mbiebl> without startpar it shows 2 6
[23:51] <mbiebl> weird thing is, startpar is called much later in /etc/init.d/rc
[23:51] <Keybuk> do you have a core for that?
[23:52] <Keybuk> or at least the assertion message?
[23:52] <mbiebl> Keybuk: I'll need to reboot for that and, wait a sec
[23:55] <mbiebl> runlevel:error.c:319 Assertion failed in nih_error_get: context_stack != NULL
[23:55] <mbiebl> Aborted
[23:59] <Keybuk> got a core for that?