[01:21] <Micksa> suspend-to-ram is working like a charm
[01:21] <Micksa> and all it right with the world once more
[01:58] <zul> jbailey: dont start hacking on the kernel? sheesh thats what i did :)
[02:18] <jbailey> I didn't say don't start there.  I said it's possible not the best place to start.
[02:18] <zul> hehe..
[02:26] <jbailey> And really, to start by doing kernel hacking requires a whole lot of drive.
[02:26] <jbailey> Someone with it will do it regardless of what I say.
[02:26] <jbailey> (Esp as I don't mean to be discouraging.  It is a daunting place to start on its own without my help)
[02:28] <zul> oh i know...
[02:28] <zul> its a rough place to start if you are just starting out
[05:50] <lamont> now to figure out if I really care about the bug
[05:51] <lamont> new oo.o2 and gcc-3.3 sigh
[05:51] <lamont> and gcc-3.4
[05:51] <lamont> that explains why it's taking forever. :=(
[05:58] <dilinger> jbailey: ping
[06:18] <fabbione> morning
[09:52] <chmj> fabbione, ping 
[09:53] <fabbione> pong
[09:55] <chmj> fabbione, is it possible to merge the last patch in kernel-debian--pre1,3--2.6.1 1.93 to the new playground ?
[09:57] <fabbione> chmj: i think so yes.. but that change needs to be reverted in that branch
[09:58] <chmj> ok, I don't know my way around baz that much
[10:01] <fabbione> chmj: ok i will try to clean up
[11:40] <jbailey> dilinger: pong =)
[11:45] <fabbione> hey jbailey 
[11:46] <jbailey> g'm Fabio
[01:17] <zul> morning
[01:18] <fabbione> hi zul
[01:19] <zul> how is the external-modules going?
[01:19] <fabbione> i didn't work on it yet
[01:19] <zul> ah
[01:19] <fabbione> doing other stuff atm
[01:20] <fabbione> looking at the new kernel-package and kernel-wedge
[01:49] <chmj> zul, where are the external-modules packages ? 
[01:49] <chmj> if there are any packages 
[01:51] <fabbione> there are no packages
[01:58] <jbailey> fabbione: *poke*
[01:59] <fabbione> jbailey: ?
[01:59] <jbailey> I think in ppc32 mode this thing has gotten farther.
[01:59] <jbailey> It's got a bunch of XMLTO lines on the screen now.
[01:59] <fabbione> jbailey: why am i not surprised? :)
[01:59] <fabbione> yeah that's it
[01:59] <fabbione> i think
[01:59] <fabbione> let it finish
[01:59] <jbailey> Will do.
[01:59] <fabbione> i will deal with it soon.. i think i know what it is
[02:00] <jbailey> I think I'm going to have a nap.  I woke up crazy early this morning because of the cats.
[02:00] <fabbione> i noticed :)
[02:00] <fabbione> thanks a lot
[02:00] <jbailey> =)
[02:18] <fabbione> speaking of which.. a nap is a really good idea
[02:19] <fabbione> zul: i did upload the new kernel-package
[02:19] <chmj> u have cats ?
[02:19] <fabbione> so you can build again
[02:19] <fabbione> chmj: no... i have a wife :P
[02:19] <chmj> who has cats I assume ? 
[02:20] <fabbione> chmj: i am not following you :)
[02:20] <fabbione> anwyay.. later
[02:20] <chmj> later 
[04:12] <jbailey> fabbione: Build finished fine.
[04:14] <dilinger> jbailey: i was just curious what you thought regarding cdbs2 testing framework stuff
[04:15] <jbailey> dilinger: When I read it, it made my brain hurt, so I went to bed. =)
[04:16] <jbailey> I'll take a look again today.
[04:16] <dilinger> jbailey: writing it made my brain hurt a little.  i should probably try and make it a bit more coherent or something ;)
[04:16] <jbailey> I wrote the original testsuite, and it's basically the one from cdbs1 ported up.
[04:16] <jbailey> I agree that it would be nice to make it a bit more generic.
[04:19] <lamont__> fabbione: ping
[04:19] <jbailey> I do occasionally run the testsuite by hand while I'm hacking, largely with debugs turned on so that I can see what's happenning.
[04:20] <dilinger> jbailey: yea, basically the abi checking stuff fits right in w/ this..
[04:20] <jbailey> Right.
[04:20] <jbailey> I need to learn a bit more about how that's happening.
[04:20] <jbailey> But if we could unify it with stuff that we're developping collectively, then that would be lovely.
[04:43] <zul> fabbione: ping
[04:54] <lamont__> "BTW, nobody should be using transport mode over the Internet anyway."
[05:16] <jbailey> context?
[05:21] <dilinger> ipsec?
[05:27] <lamont__> ipsec
[05:27] <fabbione> pong
[05:27] <lamont__> vs tunnel mode
[05:30] <fabbione> lamont__: dunno why.. but you can use tunnel mode between 2 hosts exactly as you use transport
[05:30] <fabbione> lamont__: i am pretty sure that what he sais is ok, given he is one of the Ipsex developer :)
[05:30] <fabbione> zul: pong?
[05:30] <lamont__> fabbione: ok
[05:32] <zul> fabbione: i made some changes my arch you can sync if you want
[05:32] <fabbione> zul: ok thanks
[05:35] <lamont__> fabbione: what I'd really like is a comprehensive tutorial on the subject. :-)
[05:37] <fabbione> lamont__: i remember i read all the RFC's 5 years ago... and i met who wrote them. you really don't want to go there.. do you? ;)
[05:37] <jbailey> lamont__: Step 1: Install checkpoint Step 2: Slit wrists.
[05:38] <lamont__> fabbione: all the stuff from 6 months ago is completely incorrect
[05:38] <fabbione> lamont__: probably the linux implementation sucks....
[05:38] <fabbione> i did use fbsd+racoon against an ericsson ipsec implementation at that time
[05:39] <fabbione> and it was working
[05:39] <dilinger> heh
[05:39] <dilinger> ipsex?
[05:39] <fabbione> but i didn't even attempt firewalling
[05:39] <fabbione> dilinger: yeah.. isn't ipsec sexy??
[05:39] <lamont__> fabbione: that's the thing - none of the ipsec howto's address firewalling
[05:39] <fabbione> i even wwrote ipsex several times in my test reports for ericsson...
[05:39] <fabbione> nobody bothered to correct them :)
[05:39] <dilinger> hehe, nice
[05:40] <lamont__> Jun 14 09:39:57 localhost racoon: NOTIFY: the packet is retransmitted by 10.17.72.128[500] . 
[05:40] <fabbione> lamont__: right, because ipsec and firewalling are 2 separate issues...
[05:40] <fabbione> lamont__: one to protect data/connection , one to protect the host
[05:42] <lamont__> right.
[05:43] <lamont__> many of the ipsec tutorials tell you that to make ipsec work, you need iptables -A INPUT -p esp ACCEPT
[05:43] <lamont__> which isn't necessarily so
[06:27] <lamont__> what is /dev/vcsN ?
[06:28] <zul> virtual console screen
[06:28] <lamont__> ah, ok
[06:57] <fabbione> hey thombot
[06:59] <fabbione> ok
[07:01] <thom> yo
[07:06] <lamont__> fabbione: note that you're making it harder and harder to build 2.6.12 on hoary. </grumble>
[07:21] <thom> fabbione: dude, ipw2100 is at 1.1.0 which is apparently the version we have
[07:26] <zul> for breezy?
[07:27] <fabbione> lamont__: you are not even supposed to build 2.6.12 on hoary :)
[07:27] <fabbione> thom: is it???
[07:27] <lamont__> fabbione: yeah, and?
[07:27] <fabbione> ipw2100            | 1.1.0                      | ok     | 12/04/2005   | http://ipw2100.sourceforge.net/
[07:27] <fabbione> oh yeah indeed
[07:28] <fabbione> lamont__: i know.. but there are a bunch of assholes sitting on #ubuntu-toolchain that keeps breking things... and i have to put pieces back together again
[07:28] <fabbione> ;)
[07:33] <lamont__> gcc-3.4 (>= 3.4.4-0ubuntu6) [powerpc i386]  | gcc-3.4 (= 3.4.3-9ub
[07:33] <lamont__> untu4) [i386] , gcc-3.4 [!powerpc !i386] 
[07:34] <fabbione> i didn't do it :)
[07:34] <lamont__> that's my addition in between the | and the ,
[07:34] <lamont__> and makes hoary happy again
[07:39] <zul> i hate sql
[07:43] <lamont__> zul: I've never met anyone who claimed otherwise. 
[07:46] <zul> good so im not alone
[08:44] <thom> bleah. EIP is at ieee8011_wx_get_scan
[08:50] <lamont__> fabbione: the ones doing the breaking are all here, too. :-)
[09:05] <lamont__> cache hit                             65
[09:05] <lamont__> cache miss                         17642
[09:05] <lamont__> grumble
[09:06] <thom> fabbione: right, this ipw2100 problem is a regression from 2.6.10
[09:25] <jbailey> Should the kernel be part of ubuntu-minimal?
[09:27] <fabbione> thom: it's an upstream problem. ipw2100 is using an old version of ieee$randomnumbers
[09:27] <fabbione> i remember very well that from when i did the merge
[09:27] <fabbione> so we need to wait upstream to sync
[09:27] <fabbione> both ipw2100 and 2200 have this ieee code duplication
[09:28] <fabbione> and they often go out of sync
[09:28] <fabbione> lamont__: that was the point of my comment :P
[09:29] <thom> fabbione: grah, k
[09:42] <lamont__> 6000 more misses, 20 more hits.  woot!
[10:22] <zul> fabbione: new inotify
[11:19] <jbailey> dilinger: Around?
[11:20] <dilinger> yep
[11:21] <jbailey> dilinger: cdbs2 thoughts for you.  Once we're done this testsuite and some basic docs.  What all do you think there is left before we can include it for some basic usage?  I know that the debhelper and autotools need a bunch of variables populated and help things written for them.  Is there other just basic functionality that's missing before people can at least start peeking at it for basic apps?
[11:22] <dilinger> yea, the main thing that's missing/broken is per-module pass stuff
[11:22] <dilinger> right now, if you have CDBS_MODULES := autotools, foo_CDBS_MODULES := autotools debhelper, debhelper gets run for both
[11:23] <dilinger> i think that's a bug i introduced, with the way i'm keeping track of stuff
[11:23] <dilinger> that's the main thing that's remaining
[11:23] <jbailey> Nice. =)
[11:23] <jbailey> I haven't dug through everything yet that you've done.
[11:23] <dilinger> after that, we just start porting modules
[11:23] <jbailey> My initial targets for modules are just autotools, python, ant, gnome and kde.
[11:24] <jbailey> Those are ones that I feel confident writing testscripts for.
[11:24] <dilinger> the framework is there, debian/rules help will spit out all variables, hooks, etc; i'm not too concerned about the test suite stuff, but if we decide to make it built in (w/ the way i'd prefer, test-specific hooks), it wouldn't be too hard to add in there
[11:24] <jbailey> I'm hoping to be more hardcore about features needing testcases for this so that we don't have the kind of fuckage debian had from robert in the last few months of cdbs.
[11:24] <dilinger> jbailey: that would be nice
[11:25] <dilinger> i'd certainly appreciate it if you pushed for the test stuff
[11:26] <dilinger> because i can pretty much guarantee how it'll go if i do it (first, i'll say i just want to get stuff working, so i won't concentrate on the test suite.  after stuff is working, i'll say things need enhancements before i can get to the test stuff.  finally, i'll say it's time for the test suite, and i'll get distracted and work on some other project that's bugging me)