[03:00] <WFeather> anyone here know how to disable touch in ubuntu 10.10, but still leave the digitizer active ?
[09:55] <lucent> 'fakeroot debian/rules clean' barfed when I ran it from within a directory tree that contained spaces
[09:55] <lucent> cd $HOME/"SOME DIR WITH SPACES"/src-maverick/linux-2.6.35 ; fakeroot debian/rules clean
[09:56] <lucent> bunch of errors about SOME, and errors about DIR, and WITH, and SPACES
[10:35] <apw> lucent, that i can believe, buildds would never use that format and clearly none of us do either
[10:39] <lucent> apw: so, is it a bug?
[10:40] <lucent> adding a note about that to https://help.ubuntu.com/community/Kernel/Compile would be helpful IMO if not a bug
[10:40] <lucent> wary of editing that myself 
[10:41] <apw> lucent, its most cirtainly a bug, probabally not a small job to resolve it mind if its systemic
[10:42] <apw> most of us are pretty leary of using spaces in filenames cause they are a pig to work with on the command line, so most of us would never hit it
[10:42] <lucent> okay
[10:43] <apw> cirtainly reasonable to file a bug if it affected you, we may decide its too hard to fix and fix the documentation, but if it breaks our packaging is broke
[10:44] <lucent> thanks for that, good to know what you think about it :)
[20:14] <lyhana8> hi there, am I in the right place to ask for fglrx patching?
[20:14] <lyhana8> patch is to be done on fglrx kernel module to compile again on kernels with CVE-2010-3081 fixed
[20:14] <ubot2> lyhana8: The compat_alloc_user_space functions in include/asm/compat.h files in the Linux kernel before 2.6.36-rc4-git2 on 64-bit platforms do not properly allocate the userspace memory required for the 32-bit compatibility layer, which allows local users to gain privileges by leveraging the ability of the compat_mc_getsockopt function (aka the MCAST_MSFILTER getsockopt support) to control a certain length value, related to a "stack pointer
[20:14] <lyhana8> need for ubuntu 10.04