[08:07] <apw> cheater, i'd say that my experience with btrfs is that it is not production ready
[08:45] <cheater> apw: ok.
[21:29] <guite> Hi everyone, I’m trying to compile the kernel driver “btusb”. I succesfully recompiled it by doing « make drivers/bluetooth/btusb.ko » but when I try to activate it with « insmod btusb.ko » I have the following error: « insmod: ERROR: could not insert module drivers/bluetooth/btusb.ko: Invalid module format »
[21:30] <guite> the patch I applied is so tiny, I can’t understand what can be wrong with it => https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/bluetooth?id=8f0c304c693c5a9759ed6ae50d07d4590dad5ae7
[22:06] <mozmck> how do I build a linux-libc-dev package with the ubuntu build system?  I ran fakeroot debian/rules binary-indep, fakeroot debian/rules binary-perarch, and fakeroot debian/rules binary-my_custom_flavour, and it did not generate linux-libc-dev.
[22:23] <apw> mozmck, a derivative does not.make it
[22:24] <apw> mozmck, there can only be.one kernel in the archive which does because it is the one th compiler and libc build with
[22:30] <mozmck> hmm, so what does that mean practically?  I need to compile the generic flavour?
[22:36] <apw> mozmck, it means you shoulf use the lonux libc dev from the archive if you are using libc from the archive
[22:38] <mozmck> ah, ok.  I assumed it needed to be the same version as the kernel
[22:38] <mozmck> thanks
[22:42] <apw> nope, its used by things which happen long before your kernel gets built