| === gilmrex is now known as yoloeg | ||
| === gilmrex is now known as yogels | ||
| === gilmrex is now known as lemnix | ||
| === doko_ is now known as doko | ||
| === clever is now known as clever[rev] | ||
| === asac_ is now known as asac | ||
| * lamont grumbles at -m multiport apparently not liking ipv6 very much | 14:45 | |
| lamont | (iptables) | 14:45 |
|---|---|---|
| bullgard4 | What tools does Ubuntu provide to low-level query the SMBus? | 15:18 |
| amitk | bullgard4: i2c-tools? | 15:23 |
| bullgard4 | amitk: packages.ubuntu.com doesn't know anything about 'i2c-tools' for Gutsy. | 15:27 |
| amitk | bullgard4: aah.. I am on Hardy | 15:34 |
| bullgard4 | amitk: Are you going to tell me that Hardy will provide a DEB program package 'i2c-tools'? | 15:35 |
| amitk | bullgard4: run 'apt-cache search i2c' | 15:35 |
| amitk | bullgard4: I am telling you it is already available in hardy :) | 15:36 |
| bullgard4 | amitk: Excellent! Thank you very much for the good news. | 15:36 |
| bullgard4 | amitk: http://ubuntuusers.de/paste/46586/ | 15:38 |
| amitk | hmm.. I guess Gutsy didn't have libi2c-dev, python-smbus, i2c-tools, etc. But you could try to compile them from source packages from hardy | 15:40 |
| ki | ghost ride ittttt! | 17:30 |
| === fabbione is now known as thegodfather | ||
| amitk | jayc: I meant this commit: http://kernel.ubuntu.com/git?p=ume/hardy-ume.git;a=commit;h=1343698dbfde5798b17a56becd663ace088e7cbc | 18:49 |
| jayc | amitk: so, what's the right way to do it? | 19:08 |
| amitk | jayc: keep them in separate patches :) | 19:11 |
| amitk | jayc: I have fixed it now, pushing soon | 19:11 |
| jayc | amitk: ok, patch for a patch :-) | 19:12 |
| === calc_ is now known as calc | ||
| === Traxer is now known as Traxer|on | ||
| === Traxer|on is now known as Traxer | ||
| el_cubano | Hello. I am trying to build the lustre modules for the 2.6.22 kerne. However, there appear to be some changes because of the AppArmor patch which prevent the lustre modules from actually building. | 21:51 |
| el_cubano | Would someone be able to give me a pointer on how to go about removing the AppArmor patch entirely? | 21:51 |
| johanbr | Shouldn't 2.6.24-10 have appeared in the archive by now? | 22:35 |
| amitk_ | johanbr: lum/lrm still need building | 22:40 |
| alex_joni | el_cubano: you probably want apt-get source linux-source-... | 22:40 |
| alex_joni | then check the patches dir, and remove the patch you don't want | 22:40 |
| johanbr | amitk_: Oh, I see. Thanks. | 22:41 |
| === amitk_ is now known as amitk | ||
| el_cubano | alex_joni: Really? There is no patches dir when I apt-get the source. That is why I am asking for help here. | 22:46 |
| alex_joni | el_cubano: you probably did apt-get install linux-source.. | 23:03 |
| el_cubano | alex_joni: No. I did 'dget -x http://archive.ubuntu.com/ubuntu/pool/main/l/linux-source-2.6.22/linux-source-2.6.22_2.6.22-14.52.dsc' | 23:11 |
| el_cubano | BTW, I am a Debian developer. I know the difference between 'apt-get install' and 'apt-get source' | 23:11 |
| mjg59 | There is no patch system | 23:12 |
| mjg59 | It's maintained as a git tree | 23:12 |
| alex_joni | el_cubano: you should listen to mjg59 :) | 23:13 |
| mjg59 | el_cubano: You can grab it from git on kernel.ubuntu.com and then revert any of the apparmor commits | 23:15 |
| el_cubano | mjg59: Is there an easy way to see which are the app armor commits? Or do I just need to read the logs. | 23:26 |
| mjg59 | el_cubano: Probably just the logs, I'm afraid | 23:26 |
| el_cubano | mjg59: OK. Thanks. | 23:35 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!