[00:00] <zenrox> so its just the restricted modules that are installed in the other kernel 
[00:00] <zenrox> ??
[00:13] <Kano> well the lrm manager has some stupid sideeffekts
=== doko_ is now known as doko
[01:26] <infinity> BenC: Alive, perchance?
[01:39] <yuhong> In fairness however, Windows have a mode where NX is enabled for all apps.
[01:39] <yuhong> That may catch some buffer overflows
[01:39] <yuhong> http://blogs.authentium.com/virusblog/?p=156
[01:40] <yuhong> Unfortuately, it is not set that way by default because of appcompat issues.
[01:44] <yuhong> Also there is another reason to enable PAE. More than 4G of RAM requires PAE.
[01:45] <yuhong> Though using a x86-64 kernel is better if you can, with only 4G of RAM, PAE should suffice to access the part that is over the 4G physical address space boundary.
[01:45] <yuhong> But that is secondary, the primary reason is NX.
[01:46] <yuhong> And yes, there are processors that support NX and PAE that does not support x64.
[01:46] <yuhong> Most of them have less than 4G through, so the primary reason is NX.
[01:46] <yuhong> To enable PAE, that is.
[01:47] <yuhong> Solaris have a runtime option to enable PAE, so it have NX enabled by default.
=== asac_ is now known as asac
[13:48] <reynaldo> mornings all.
[17:22] <lool> Hi folks
[17:32] <lool> exmap is currently broken in Ubuntu but works fine in Debian; it seems to be dying when parsing /proc/*/maps; should I be aware of a major difference between the kernels which my eyes can't detect?
[17:33] <lool> The parsing chokes on the getty processes which are launched by upstart instead of init
[19:26] <reynaldo> oh.
=== ivoks_ is now known as ivoks
[20:34] <lamont> BenC: wondering... you care if you have to do your own installs?
[21:21] <somerville32> There is a bug in the linux kernel that prevents xfce4-battery-plugin from compiling and I'd like to have this merge done for the next alpha because it contains important patches we'd like tested. Basically, apm_event{,info}_t are userspace types but they got hidden behind #ifdef __KERNEL__ by mistake in commit ee8e7cfe9d330d6f1ce0b9b1620d6df5d9cf6b70
[21:22] <somerville32> I was wondering if the kernel team would be willing to apply the very non-invasive patch to correct this issue in the mean time since xfce4-battery-plugin isn't the only package FTBFS because of this.
[21:23] <maks_> is upstream notified?
[21:23] <somerville32> There is a thread on fa.linux.kernel
[21:24] <somerville32> Andrew Morton commented on it on the 12th
[21:28] <rtg_> somerville32: this is in apm_bios.h ?
[21:28] <somerville32> rtg_, yup
[21:29] <rtg_> somerville32: those 2 lines just need to be moved above '#ifdef __KERNEL__' ?
[21:29] <somerville32> Correct
[21:30] <rtg_> do you think it will happen upstream during the 2.6.24-rc window?
[21:32] <somerville32> There is nothing to indicate to me that it will but I have no metric for answering that question.
[21:32] <rtg_> somerville32: develop a patch and send it to kernel-team@lists.ubuntu.com so I don't forget it.
[21:32] <somerville32> Ok
[21:33] <somerville32> Should I file a bug too?
[21:33] <rtg_> nah, seems trivial enough. especially during the development cycle.
[21:35] <somerville32> How long do you think this will take. I'd really like to be able to include xfce4-battery-plugin in Alpha 2
[21:35] <rtg_> somerville32: I'll have it in before then. probably Monday.
[21:36] <somerville32> ok, thanks
[21:48] <somerville32> Ok
[21:48] <somerville32> e-mail sent
[21:49] <_MMA_> somerville32: Forget a subject there? ;)
[21:49] <somerville32> : (
[21:50] <somerville32> Now I feel like a loser.