[00:30] <jjohansen> lamont: re: fs caps?  Did you make any progress with that?
[02:15] <lamont> jjohansen: remind me?
[02:42] <jjohansen> lamont: you were asking how much a pain enabling file caps would be
[02:43] <jjohansen> lamont: I asked if a few days before feature freeze was the time to be wondering about it
[02:44] <lamont> oh.  that.
[02:44] <jjohansen> so I suppose, that means no
[02:44] <lamont> I don't remember - it was someone else backchanneling through me complaining that the machine we co-manage at a co-lo facility needs a custom kernel
[02:45] <jjohansen> hrmm, they could use AA set capability rules to achieve much the same thing
[02:46] <lamont> except that the package that they're using doesn't
[02:46] <lamont> and rebuilding the kernel is easier
[02:46] <jjohansen> heh, maybe
=== akgraner_ is now known as akgraner
=== Quintasan_ is now known as Quintasan
[10:31] <tkamppeter> Anyone can give me some help to submit a patch correctly to the vger.kernel.org mailing list?
[10:36] <smb> tkamppeter, One thing would be to run your patch through scripts/checkpatch.pl If that does not complain, this is a good sign
[10:37] <amitk> tkamppeter: also, Documentation/SubmittingPatches in the kernel tree has pointers to making the perfect patch
[10:39] <smb> tkamppeter, There is also scripts/get_maintainer.pl which would help you to find out who to cc
[11:41] <smoser> anyone here a kernel-team@lists.ubuntu.com moderator ?
[11:41] <smoser> i sent some non-spam there that needs to be approved. (ok, well *I* think its not spam)
[11:44] <tkamppeter> smb, amitk, thx.
[11:44] <amitk> smoser: done
[11:44] <smoser> thanks
[12:17] <gnomefreak> is it known that the newest kernel wont shut PC off ubuntu shuts down but PC stys on and i have to push and hold to shut it down?
[12:21]  * gnomefreak goes to file bug
=== bjf-afk is now known as bjf
[15:48]  * amitk confirms the behaviour that gnomefreak was reporting about the system now powering off with -7
[15:49] <rtg_> amitk, yeah, that was the other side effect of -7.
[15:49] <rtg_> of the KSM patch set, rather
[15:49] <amitk> s/now/not
[15:50]  * gnomefreak cant recall bug # but there is one filed on it
[15:51] <amitk> gnomefreak: please check back with -8 that rtg just uploaded (might be available tomorrow)
[15:52] <gnomefreak> amitk: ok thanks is there a deb in LP? 
[15:53] <rtg_> gnomefreak, its just been uploaded, so will take awhile
[15:53] <gnomefreak> rtg_: ok thanks again
[16:42] <Laibsch> Hi
[16:43] <Laibsch> Where do I get the source for the mainline kernels?
[16:44] <Laibsch> I doubt that the 2.2KB file http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2009-08-27/linux-source-2.6.31_2.6.31-999.200908271000_all.deb has much ;-)
[16:46] <Keybuk> Laibsch: mainline kernels are inherently the mainline kernels
[16:46] <Keybuk> ie. kernel.org git
[16:47] <Laibsch> well, but there's more to it
[16:47] <Keybuk> no, there isn't
[16:47] <Laibsch> I already compiled mainline straight from git
[16:47] <Laibsch> But it was missing the initrd part
[16:47] <Keybuk> what initrd part?
[16:48] <Laibsch> My kernel did not create an initrd
[16:48] <Keybuk> how did you make your kernel?
[16:48] <Laibsch> make-kpkg
[16:48] <Keybuk> make-kpkg --initrd? :-)
[16:49] <Keybuk> strictly speaking though, Ubuntu kernel builds don't use make-kpkg
[16:49] <Laibsch> alright, I'll retry with --initrd
[16:49] <Laibsch> sorry, if I sound stupid ;-)
[16:50] <Laibsch> I only compile kernels out of necessity
[16:50] <Laibsch> not for fun
[16:50] <Keybuk> really? I do it for fun :p
[16:50] <Keybuk> plus it keeps the house warm, and saves on gas
[17:10] <AnAnt> Hello, could someone confirm this bug please: LP 418477 ?
[17:10] <AnAnt> Launchpad bug 418477 in linux "New kernel causes losetup to hog the system" [Undecided,New] https://launchpad.net/bugs/418477
[17:10] <ubot3`> Malone bug 418477 in linux "New kernel causes losetup to hog the system" [Undecided,New] 
[17:13] <rtg_> AnAnt, -7 is killing kittens. -8.28 is in the pipeline.
[17:14] <AnAnt> rtg_: ah, thanks
[17:14] <AnAnt> killing kittens
[17:14] <AnAnt> is that somehow of saying "evil" ?
[17:15] <rtg_> AnAnt, any sane person would consider dead kittens to be evil, right?
[17:15] <AnAnt> rtg_: dead kittens are not evil
[17:15] <AnAnt> the one who kills them is !
[17:15] <rtg_> AnAnt, ah, a fine semantic difference :)
[17:15] <AnAnt> :)
[17:16] <AnAnt> ok, I need to ask a question, is this bug: LP 414795 a kernel or a pulseaudio bug ?
[17:19] <AnAnt> https://launchpad.net/bugs/414795
[17:19] <ubot3`> Malone bug 414795 in pulseaudio "PC beep no longer works in Karmic alpha4" [Undecided,New] 
[18:29] <rtg_> bjf, git://kernel.ubuntu.com/rtg/ubuntu-karmic fsl-imx51 for boot testing. You do have HW, right?
[18:42] <rtg_> ogasawara, how do I change bug duplication? I want to use bug #418781 as the master. bug #417750 is already a duplicate of 418685 and I cannot figure out how to redirect it.
[18:42] <ubot3`> Malone bug 418781 in linux "Karmic 2.6.31-7.27 KSM patchset breaks encrypted swap" [High,Fix released] https://launchpad.net/bugs/418781
[18:42] <ubot3`> Malone bug 417750 in ubuntu "[Karmic Regression] LUKS Partitions (dup-of: 418685)" [Undecided,New] https://launchpad.net/bugs/417750
[18:42] <ubot3`> Malone bug 418685 in linux "cryptsetup hangs" [High,Confirmed] https://launchpad.net/bugs/418685
[18:43] <andresmujica> rtg_: /usr/share/doc/python-launchpad-bugs/examples/move_duplicates.py 
[18:44] <rtg_> andresmujica, don't need no steenking python
[18:44] <ogasawara> rtg_: yah unfortunately, if a bug already has duplicates, you have to move those to the new master bug first (ie lp won't auto move them for you)
[18:45] <andresmujica> manually?  you must move first the dupe to the new master bug and then the old master bug move it as dupe from the new one
[18:45] <ogasawara> rtg_: I'll clean it up
[18:45] <rtg_> ogasawara, actually, that was exactly what I was trying to do
[18:46] <ogasawara> rtg_: hrm that's odd, not sure why it wouldn't have worked them.  I'll give it a try.
[18:46] <rtg_> ogasawara, it would help if I knew what button to push :)
[18:46] <bryce> lp can be fussy sometimes
[18:47] <ogasawara> rtg_: I just click on the Duplicate of bug # link under the bug title
[18:47] <rtg_> bryce, you are a master of understatement.
[18:48] <rtg_> ogasawara, which just takes me to the master (the one I don't want to use)
[18:49] <ogasawara> rtg_: hrm, it should pop up a little dialog box for you to enter the new bug#.  at least that's what it's doing here for me.
[18:49] <ogasawara> rtg_: are you on edge?
[18:49] <rtg_> ogasawara, well, we all know you _are_ special.
[18:50] <ogasawara> hehe
[18:50] <rtg_> yep, I'm always on edgwe.
[18:50] <rtg_> edge*
[18:50] <ogasawara> rtg_: I've marked em all as dups of 418781
[18:50] <rtg_> ogasawara, thanks, you're a pal
[18:51] <smb> rtg_, If you are not on edge there might be a little pen icon (yellow) beside it
[18:51] <rtg_> smb, ah! good eye.
[18:52] <smb> Me? Nah. :)
[18:52] <rtg_> I must not be programmed to notice that damned small icon
[18:52] <ogasawara> rtg_: heh, or realize is supposed to resemble a pen
[18:52] <smb> I just have to use them often
[18:52] <rtg_> ok, next time I can do this for myself.
[19:43] <superm1> mjg59, what's up with http://patchwork.kernel.org/patch/38439/ ? Is that in good order right now, or are you going to be doing more work on it?
[22:51] <mjg59> superm1: Upstream wants the filtering at the 8042 level, not the generic input level
[22:53] <superm1> mjg59, oh i see.  were you planning on reworking that then soon?
[22:58] <mjg59> Yeah, should do this week. I've been somewhat tied up organising my move.
[23:00] <superm1> mjg59, okay cool.