[11:35] <sadleder> Keybuk: hi, when and how will upstart jobs be integrated in feisty?
[11:40] <Keybuk> sadleder: there will be an alternate repository around the time feisty releases
[11:41] <sadleder> Keybuk: will the jobs be in a single package, or in their respective packages?
[11:41] <Keybuk> respective packages
[11:42] <sadleder> Keybuk: ah, ok, thx.
[11:43] <sadleder> Keybuk: btw, your work on upstart is just formidable
[11:44] <sadleder> Keybuk: so users will see those when feisty releases, but not before?
[11:46] <Keybuk> yeah, basically we missed the feisty feature freeze for it -- and want to get it right instead
[11:46] <Keybuk> "around feisty release time" is just a guess
[11:46] <sadleder> Keybuk: and what about testing?
[11:47] <Keybuk> I don't follow?
[11:47] <Keybuk> anyone who uses the repository will be testing them :)
[11:50] <sadleder> Keybuk: hmm, ok, does that mean, they won't go into feisty, but rather into feisty+1?
[11:51] <Keybuk> right
[11:51] <Keybuk> exactluy
[11:52] <sadleder> ok, now i understand
[11:53] <sadleder> so feisty will just have upstart-compat-sysv
[11:56] <Keybuk> yes
[12:39] <_ion> Good ideas from AlexExtreme at the mailing list.
[12:40] <_ion> Matthias Ulrichs' idea of list-style variables would be nice.
[12:40] <_ion> cherry?
[12:41] <Keybuk> I can find a G80-3000LSCGB-0, which is only one letter out from my current G80-3000LSMGB-0
[12:41] <Keybuk> and appears to have the right  description
[12:41] <Keybuk> keyboards
[04:08] <fatzeus> hi, i'm trying to install upstart on gentoo
[04:10] <Keybuk> fatzeus: hi
[04:10] <fatzeus> hi
[04:10] <fatzeus> i've some connection trouble...
[04:10] <fatzeus> anyway..
[04:11] <fatzeus> i see that there are some sample scrits
[04:11] <fatzeus> that you have to modify to fit your distro configuration
[04:11] <fatzeus> i've almost done...i think 
[04:11] <fatzeus> but in the inittab file i've also something like this:
[04:12] <fatzeus> rc::bootwait:/sbin/rc boot
[04:12] <fatzeus> but with the examples i don't see any like this
[04:12] <fatzeus> for example the si::sysinit:/sbin/rc sysinit in my inittab file
[04:12] <fatzeus> i think is rcS
[04:13] <fatzeus> ?
[04:16] <fatzeus> maybe add rc boot into the rcS file after rc sysiniti??
[04:21] <Keybuk> no idea, I'm not familar with Gentoo I'm afraid
[04:21] <Keybuk> certainly each line in the /etc/inittab corresponds to one file in /etc/event.d
[04:21] <fatzeus> yes...rc:bootwait
[04:22] <Keybuk> bootwait and sysinit are different I guess
[04:22] <fatzeus> is also mentioned in the man
[04:22] <fatzeus> man /etc/inittab
[04:22] <fatzeus> Further system initialization, brings up the boot runlevel
[04:22] <Keybuk> after rcS, before rc-default I guess
[04:22] <fatzeus> it doesn't say a lot...
[04:23] <Keybuk> so make a new event.d file, exec /sbin/rc bin, start on stopped rcS; and change the rc-default to be start on stopped $new_file
[04:23] <fatzeus> ok...thank i'll try this way
[04:24] <fatzeus> if i see that it's not the correct order
[04:24] <fatzeus> i've just to change after/before
[04:24] <mbiebl> fatzeus: have you replaced /sbin/init or did you install it to another location?
[04:25] <fatzeus> i placed it in /opt/upstart
[04:25] <fatzeus> as suggested...
[04:25] <mbiebl> good ;-)
[04:29] <fatzeus> uhm...
[04:29] <fatzeus> what does stop on means?
[04:33] <fatzeus> i'll try reboot...
[04:48] <Keybuk> _ion: watch delayed is merged into my branch now, and have also merged it into watch.c directly
[04:48] <Keybuk> just doing some tests, etc. before I push
[04:48] <_ion> Great
[04:50] <Keybuk> thanks for your work on that, it should prove very useful
[04:50] <Keybuk> sorry it took me a while to get to it :p
[04:52] <_ion> No problem at all
[06:13] <Keybuk> _ion: another way of looking at the whole stdint thing
[06:13] <Keybuk> the C standard already guarantees type sizes
[06:13] <Keybuk> char is "at least 8 bytes"
[06:13] <Keybuk> int is "at least 16 bytes"
[06:13] <Keybuk> long is "at least 32 bytes"
[06:13] <Keybuk> and long long is "at least 64 bytes"
[06:13] <Keybuk> so you don't need the stdint types unless you want an "exactly" restriction
[06:19] <_ion> Right
[06:20] <Keybuk> the other fun with ... applied to int8_t
[06:20] <Keybuk> it gets promoted to an ordinary int, which might 32 or 64-bytes :p
[06:20] <Keybuk> (or even 16-bytes on 286s)
[06:20] <_ion> Heh
[06:27] <concept10> hello all.  The above link (getting started is wrong)
[06:29] <Keybuk> oh yeah] 
[06:29] <Keybuk> heh
[06:29] <Keybuk> since all those are now linked on the website
[06:32] <concept10> Keybuk, what would be the equivalent to /etc/inittab?
[06:35] <Keybuk> the /etc/event.d directory
[06:36] <concept10> okay, I know that, but Im looking for the first file or script thats run
[06:45] <mbiebl> All that have a "start on startup"
[06:46] <mbiebl> startup is the first signal that upstart emits.
[06:47] <mbiebl> Keybuk: question about libnih
[06:48] <Keybuk> shoot
[06:49] <mbiebl> why are the m4 macros installed to /usr/share.
[06:49] <Keybuk> /usr/share/aclocal ?
[06:49] <mbiebl> afaik they are only needed for compiling libnih
[06:49] <mbiebl> Not for applications using libnih
[06:49] <Keybuk> compiler.m4, etc.?
[06:49] <mbiebl> yes.
[06:49] <Keybuk> they're useful for any application
[06:50] <Keybuk> so they're kind of an autoconf macro library as well
[06:50] <mbiebl> It's just, that misc is a very generic name ;-)
[06:50] <Keybuk> heh
[06:50] <Keybuk> fair point
[06:50] <Keybuk> they should be in a subdir or something, dunno if aclocal copes with that
[06:51] <Keybuk> certainly there's no reason for a package to distribute them yet
[06:51] <Keybuk> bbl